Bitta Commission guide
Participant and manager statements
Generate immutable participant statements from frozen settlements, approve and make them available in Business Central, track acceptance and payment, produce manager statements, and archive delivered statements.
status: verified applies-to: 1.1.2.0rev: 1
A commission statement is a frozen, hashed snapshot of what one participant earned, what became eligible, what was held or recovered, and what was selected for payment in one settlement. Statements are generated from frozen settlements, approved, and then made available to the participant inside Business Central. Managers get a separate manager statement that summarizes their team.
The statement card shows the frozen amounts, performance values and confirmation dates.
Statements are generated from the lines of frozen settlements.
Before you start
- The settlement you want to report on must be Frozen. See Settlements and pay groups.
- To generate, submit and deliver statements you need scope over the participant: a Manager and descendants scope that includes them, or a Finance (all participants) scope. See Roles and permissions.
- Statement approval always runs through an approval policy. Create one active policy with the document type Statement in Commission Approval Policies. Without it, Submit for approval is refused with BAA-WFL-POLICY. See Approvals and notifications.
- Optionally set the confirmation and dispute windows in Commission Workflow Setup (see below).
Generate and deliver a participant statement
- Open Commission Statements and choose Generate statement.
- Generate Commission Statement lists the lines of frozen settlements for participants you can administer. Select a line for the participant and choose OK. Generation includes all lines of that participant in the settlement, not only the line you selected.
- The new statement opens on the Commission Statement card with the status Generated. Review the amounts and choose Snapshot lines to check the individual lines.
- Choose Submit for approval. The statement becomes Approval Pending and is assigned to the approver of the policy.
- The approver opens the statement, from the card or from Commission Approval Work Queue, and chooses Approve statement or Reject statement. Both ask for a Decision Reason Code and an optional comment. The person who submitted cannot approve. A rejected statement returns to Generated.
- On the approved statement, choose Make available in Business Central. The statement becomes Delivered, a copy is written to the Delivered Statement Archive, and the participant receives a Statement Delivered notification.
NOTE
Make available in Business Central records that the statement can be read in the Business Central client by users with scope to the participant. It does not send an email or publish the statement to an external portal.
What happens after delivery
| Action | Who | What it does |
|---|---|---|
| Accept statement | The participant, or a user with scope to them | Confirms the exact delivered statement. Available when the Disputes module is on. A disputed statement can be accepted once every dispute against it is decided. |
| Submit dispute, Save dispute draft | The participant | Opens a review case against the delivered statement. See Disputes and holds. |
| Record as paid | A user who administers the participant | Records that every settlement behind the statement is paid. Refused with BAA-STM-PAID-001 while any payable amount is still open, and with BAA-STM-DISPUTE-001 while a dispute awaits a decision. |
| Archive statement | A user who administers the participant | Archives a statement that is Accepted, Paid, Superseded or Corrected. |
If Statement Acceptance Days is set, the workflow deadline job records a delivered statement as accepted when the period passes without an open dispute. The card shows the dates in Confirm by and Dispute by.
Corrected statements
If you generate a statement again for the same participant and period, the app creates a new version with the next Version No. and links it to its Predecessor Statement ID. When the new version is delivered, the earlier one becomes Superseded. If the earlier version was already Paid, it becomes Corrected instead: its payment stands and the new version carries the difference.
Statement statuses
| Status | Meaning |
|---|---|
| Generated | The snapshot exists and can be submitted. |
| Approval Pending | Waiting for the assigned approver. |
| Approved | Ready to be made available. |
| Delivered | Available to the participant. |
| Disputed | At least one dispute was submitted against it. |
| Accepted | Confirmed by the participant, or recorded as accepted after the confirmation window. |
| Paid | Every settlement behind it is paid. |
| Superseded, Corrected | Replaced by a later delivered version. |
| Archived | Its lifecycle is complete. |
Read the statement
The Commission Statement card groups the frozen values:
| Group | Fields |
|---|---|
| Commission result | Earning Amount, Eligible Amount, Held Amount, Recovery Amount, Settled Amount, Currency Code, and the frozen exchange-rate date and factor. |
| Performance and balances | Quota Amount, Attainment Percent, Draw Balance, Draw Recovered Amount, YTD Earning Amount and YTD Settled Amount. Year-to-date values use the latest statement version of each period of the year. |
| Immutable evidence | Statement Hash, Line Count, Generated At, Approved At, Delivered At and the delivery channel and result. |
| Participant confirmation | Confirm by, Dispute by, Accepted At and Disputed At. |
Snapshot lines lists each line with the plan, component and measure labels, quantity, rate, amount and a Plain Explanation taken from the calculation trace, for example "a base of 10,000 at a rate of 0.05 earned 500". Open a line to see its source evidence: the source fact, earning, eligibility, balance and settlement line it came from.
Other actions on the card:
- Print statement prints the Commission Statement report in the participant's statement language. The language comes from the participant, or from the country/region policy when the participant has none. It does not change the statement hash.
- Download snapshot downloads the deterministic JSON rendering of the statement.
- Archived copies shows the copies archived at delivery.
- The Comments FactBox holds comments on the statement. Comments never change the statement hash.
Manager statements
A manager statement summarizes the latest participant statements of a manager's team for one period.
- Open Manager Commission Statements and choose Generate manager statement.
- On Generate Manager Statement, select the Manager and the Period and choose OK.
- Review the Manager Commission Statement: team totals (settled, eligible, held, recovery and earning amounts), Open Dispute Count, Pending Approval Count, and one line per team member with the statement number, status and version included.
- Choose Make available in Business Central to deliver it. A copy is archived.
The team is made of the members of the teams the manager leads and the participants below the manager in the manager's hierarchy. Generating again creates a new version linked to the previous one. Print statement and Download snapshot work as for participant statements.
Archive delivered statements
The Delivered Statement Archive keeps a copy of every participant and manager statement at the moment it was made available, with the Statement Hash and Snapshot Hash. Choose Download copy to retrieve one.
For long-term retention, open Commission Statement Archives and choose Archive Statements. Enter Months to Keep (24 by default). The app writes an archive manifest that covers every statement delivered before that cutoff, whatever its status is now. The statements stay in place and are not deleted. Each manifest records the covered date range, the row count, a control amount and a hash chain over the frozen snapshots. Choose Verify Manifest at any time to recompute the chain and compare it. Manifests also appear in the Commission Archive Register.
TIP
In Commission Workflow Setup, Register retention policies registers comments, the notification log and the statement archive with the standard Business Central Retention Policies.
Workflow setup for statements
| Field in Commission Workflow Setup | What it does |
|---|---|
| Statement Acceptance Days | Days after delivery for the participant to confirm. Zero means statements are never accepted automatically. |
| Statement Dispute Days | Days after delivery during which a dispute can be submitted. Zero means no deadline. |
How it works behind the scenes
- A statement and its lines are immutable. Each status change is checked against the exact State Version No. and Statement Hash, so an action on a stale copy is refused.
- Every lifecycle step (submit, approve, reject, deliver, accept, paid, archive) is appended to the approval ledger with the user and time.
- Integrity is verified again before every transition. A mismatch stops the action with BAA-STM-INTEGRITY-001.