24 · 代理盈亏 · 优惠与净利润 · PRD

作者 Luke　版本 v1.7　日期 2026-09-16　状态 待开发评审　平台 BRAND_A & BRAND_B　类 R

需求编号 24　英文 slug agentPnlNetIncome　模板基准 prd

模板调整说明：沿用 prd 的元信息、L0 四件、规则正文、折叠附录与视觉清单；以中英文 ImageGen 资讯图取代未渲染的 Mermaid，并把重复说明收敛到唯一章节。本需求没有 Client 交付物。

L0 · 快速掌握

① 一句话需求

Backoffice ▸ ReportManagement ▸ 代理盈亏 在 公司盈亏金额 后新增：

GGR Margin → 优惠 → 净利润

全表 18 → 21 列。页面、六项筛选、下钻入口与分页器不变；新增三列在每层下钻重新计算，并自动进入既有导出。

② 术语写死表

③ 全局红线表

④ 适用范围与不做边界

L1 · 完整规格

1. 实现导航

1. BO 送出现有报表类型、日期区间与其余四项筛选。
2. 投注／结算流水按结算时间计算既有 15 列。
3. 账变流水按领取／入账时间读取统一 Promo 类型组，只聚合会员。
4. 计算 GGR Margin = 公司盈亏金额 ÷ 投注额。
5. 计算 净利润 = 公司盈亏金额 − 优惠。
6. 每次「查看下级」都按该层代理及其团队范围重新计算新增三列。
7. 21 列全为 0 才丢弃该行；其余回传 BO。

2. 取数口径

2.1 时间口径

2.1.1　已发放但会员尚未领取的奖励不计入。设计上，日报的净利润允许同时包含结算时间与领取／入账时间；不得把 Promo 回溯分摊到投注日（G3）。

2.2 范围口径

2.2.1　账号后来被冻结、封禁或停用，不影响期间内已入账记录。449 属会员邀请会员，不另加代理过滤。

2.3 字段、Promo 类型组与算法

现行 23 项基线

自动纳入规则

2.3.1　报表不得硬编码上述编号，必须读取统一的 Promo 账变类型组。新增或启用的类型同时满足以下条件时，由主数据加入该组，报表自动纳入，不再修改查询逻辑：

1. 性质是会员活动奖金（含人工补发）或 VIP 奖励；
2. 是正向入账；
3. 对应功能已启用，且记入会员。

明确排除 7 项

2.3.2　类型组中若出现负值，该笔剔除并记录「优惠为负、已剔除」运行日志；不得用负数冲减 Promo。type=96 尚无完成的账变类型，现阶段不纳入。

2.4 计算顺序

2.4.1　每天 05:00 计算前一日：先完成 VIP 升降级，再跑返水。两批完成后才读取当日完整 Promo。

2.5 与其他报表的差异

2.5.1　三张表回答的问题不同，数字不必强行相等。

3. 页面与展示

3.1 栏位顺序

… 用户盈亏金额 → 公司盈亏金额 → GGR Margin → 优惠 → 净利润 → 实体站 → 用户线路 → 操作

3.2 格式与配色

3.2.1　金额用千分位与 2 位小数；Margin 用百分比与 2 位小数。Margin 允许低于 −100%，不夹到 0；公司盈亏金额 = 0 时显示 0.00%。

3.3 下钻、零值行、导出与相邻报表

3.3.1

• 21 列全为 0 才隐藏；只有 Promo 不为 0 的行必须显示。
• 每层「查看下级」都以该层代理及其团队范围重新计算新增三列，不沿用上层汇总值；下钻入口与分页器维持既有行为。
• Export 导出当前查询的全部命中结果，不是当前页；包含新增三列，排除「用户线路」与「操作」。
• 「累计有效活跃会员」独立报表的栏位、计算、权限、导出与入口均不变。
• 23 项基线与 7 项排除均消费既有账变主数据；本需求不新建账变类型。

4. 权限

不新增权限点。新增三列随代理盈亏既有查看权限出现；无权限时入口不显示，后端仍须拒绝请求。导出沿用既有行为。

5. 提示语

本需求不新增提示语。纯展示栏位没有自己的错误或空态；沿用代理盈亏既有提示：

6. 待确认项

无。Promo 自动纳入规则已于 2026-09-16 确认。

文档版本：v1.7 | 日期: 2026-09-16 | 作者: Luke | 文档状态：待开发评审

24 · Agent P&L · Promo and Company Net Income · PRD

Requirement ID 24　Slug agentPnlNetIncome　Author Luke　Version v1.7　Date 2026-09-16　Status Pending Development Review　Platforms BRAND_A & BRAND_B　Class R　Template Base prd

Template adjustment: Keep the prd metadata, four-part L0, rule body, collapsed appendices, and visual inventory. Replace the unrendered Mermaid source with a dedicated English ImageGen infographic and remove repeated explanations. No Client deliverable is required.

L0 · Quick read

① One-sentence requirement

Add three columns after Company GGR in Backoffice ▸ ReportManagement ▸ Agent P&L:

GGR Margin → Promo → Company Net Income

The table grows from 18 to 21 columns. Keep the page, six filters, drill-down entry, and paginator unchanged. Recalculate all three new columns at every drill-down level and include them in the existing export.

② Locked terminology

③ Global guardrails

④ Scope and exclusions

1. Implementation guide

1. BO submits the existing ReportType, DateRange, and four other filters.
2. Wager and settlement records produce the existing 15 columns by settlement time.
3. Reward transactions produce Promo by claim/posting time from the shared Promo group, members only.
4. Calculate GGR Margin = Company GGR ÷ Bet Amount.
5. Calculate Company Net Income = Company GGR − Promo.
6. For every “View Subordinates” level, recalculate the three new columns for that level's agent-team scope.
7. Drop a row only when all 21 columns are zero; return all other rows.

2. Data scope and calculations

2.1 Time basis

An issued but unclaimed reward contributes zero. Daily Net Income intentionally combines settlement-time GGR and claim/posting-time Promo; do not back-allocate Promo to wager dates.

2.2 Population scope

Later account freezes, bans, or deactivation do not remove a transaction posted during the period. Type 449 is member-to-member referral reward and needs no additional agent filter.

2.3 Fields, Promo group, and formulas

Current 23-type audit baseline

Automatic inclusion rule

The report must read one shared Promo transaction-type group, not hardcode the IDs above. Add a new or enabled type to the group, and therefore to the report without query-code changes, only when all conditions hold:

1. It is a member campaign reward, including a manual promo credit, or a VIP reward.
2. It is a positive entry.
3. The corresponding function is enabled and the entry is posted to a member.

Seven explicit exclusions

If a negative value reaches the Promo group, exclude that record and log “negative Promo excluded”; never net it against Promo. Campaign type=96 has no completed transaction type and remains excluded.

2.4 Batch order

At 05:00 each day, process the previous day. Complete VIP level changes before cashback, and read daily Promo only after both batches finish.

2.5 Expected differences from other reports

These reports answer different questions; their Promo totals need not match.

3. Page and display

3.1 Column order

… Player GGR → Company GGR → GGR Margin → Promo → Company Net Income → Gaming Venue → Line → Operation

3.2 Format and color

Amounts use thousands separators and 2 decimals. Margin uses a percentage with 2 decimals, may be below −100%, and is not clamped. When Company GGR is zero, display 0.00%.

3.3 Drill-down, zero rows, export, and adjacent report

• Hide a row only when all 21 columns are zero. A Promo-only row must remain visible.
• At every “View Subordinates” level, recalculate the three new columns for that level's agent-team scope; never reuse the parent aggregate. Keep the drill-down entry and paginator behavior unchanged.
• Export the complete matching result set, not only the current page. Include all three new columns; exclude Line and Operation.
• Cumulative Valid Active Players keeps its columns, formulas, permissions, export, and entry point unchanged.
• The 23-type baseline and 7 exclusions consume existing transaction-type master data; this requirement creates no transaction type.

4. Permissions

Add no permission point. The columns follow the existing Agent P&L view permission; hide the entry and reject the request when unauthorized. Export keeps its existing behavior.

5. Messages

This requirement introduces no message. Use the existing Agent P&L no-data copy:

6. Open points

None. The Promo auto-inclusion rule was confirmed on 2026-09-16.

Document version: v1.7 | Date: 2026-09-16 | Author: Luke | Status: Pending Development Review