Two-Step Commission Approvals
Commission disputes rarely start with dishonesty. They start with a split agreed in a WhatsApp message, recorded in a spreadsheet, and remembered differently by two people three months later.
AqarQore · Updated 30 August 2026 · 8 min read
What it does
Every closed deal passes through two independent signoffs before money moves: sales director confirms the deal and split, then accounting confirms the payment. Neither step can be skipped or performed by the other party, commissions are calculated on approval, and payout batches are protected against duplicate submission.
Why disputes happen
Ask any brokerage owner about commission disputes and you will hear the same story shape. A deal closed months ago. A split that was agreed informally. An agent who remembers 60/40 and an accounts team working from 50/50. Nobody is lying — the record simply never existed in a form that could settle it.
Three failure modes account for most of it:
- The split lives in a message. Agreed over WhatsApp, never written to the deal record. Perfectly clear at the time, unrecoverable later.
- The spreadsheet is editable. Someone corrects a figure in good faith. There is no history, so the original number is simply gone.
- Approval was informal. A manager said yes in a corridor. When it is questioned, there is nothing to point at.
The commercial cost is not the disputed amount. It is that your best agents — the ones producing the largest commissions — start checking every payout, and eventually start taking calls from competitors. Payout trust is a retention issue disguised as an accounting issue.
What “enforced” actually means
Most CRMs offer an approval workflow. The question that separates a control from a formality is whether the rule can be bypassed.
| A workflow | An enforced control | |
|---|---|---|
| Where the rule lives | The user interface | The server |
| Can an admin skip a step? | Usually yes | No |
| Can an approved figure be edited? | Often silently | No — a correction is a new, logged event |
| Evidence it happened | A status field | Immutable record: who, what, when |
| Under pressure at month-end | Someone finds a way around it | The rule holds |
This is a specific question worth putting to every vendor: can a user with full administrative rights mark a deal approved without the approval occurring? If the honest answer is yes, the workflow documents intentions rather than enforcing them.
The two-step chain
Step one — sales director
Confirms the deal is genuinely closed and that the commercial terms are right: sale price, commission rate, split between agents, any co-broke or referral arrangement. This is a commercial judgement, and it belongs with the person accountable for the sales floor.
Step two — accounting
Confirms the financial execution: that the figure reconciles, that funds have been received where that is a precondition, and that the payout enters the correct batch. This is a financial control, and it belongs with finance.
Why separation matters
Splitting these is the entire point. One person agreeing a number and releasing the payment is a single point of failure — for error as much as for anything worse. Two independent confirmations means a mistake has to survive two different people looking at it from two different angles.
Preventing double payouts
Duplicate payments happen under a predictable set of conditions: month-end, a slow connection, someone unsure whether the first submission registered, and a second click.
The protection is idempotency — submitting the same payout batch twice results in one payment, not two. The second submission is recognised as a repeat of the first rather than a new instruction. It is unglamorous engineering that quietly prevents an expensive and embarrassing class of error.
The audit trail
Every approval should record four things, and they should not be editable afterwards.
| Recorded | Answers |
|---|---|
| Who approved | Which named user, at which step |
| What was approved | Amount, split, deal reference |
| When | Timestamp, not just a date |
| What changed | Prior values, if a correction was issued |
This is also what makes downstream finance work tractable. Clean, approved, attributable commission data is what an invoicing or ERP system needs to raise an invoice without reconstruction — a point covered in more depth in the Saudi compliance guide.
What to ask a vendor
- Can an administrator bypass an approval step? Ask for a demonstration, not an assurance.
- Can an approved commission figure be edited without a visible trace?
- What happens if a payout batch is submitted twice?
- Are tiered rates, co-broke splits and referral fees supported natively?
- How does approved commission data reach our accounting system?
- Can an agent see their own approved commissions without asking finance?
That last one matters more than it looks. Most disputes begin as uncertainty. Agents who can see their own approved numbers stop needing to ask.
Frequently asked questions
What is a two-step commission approval?+
A closed deal moves through two independent signoffs before any payout: the sales director confirms the deal terms and split, then accounting confirms the payment. Neither can complete the other's step, and neither can skip it. Separating who agrees the number from who pays it is the control.
Why do commission disputes happen?+
Almost always because the agreed split was recorded informally — a WhatsApp message, a verbal agreement, a spreadsheet cell someone later edited. When the payout differs from what the agent remembers, there is no authoritative record to settle it, so it becomes an argument about memory.
What does "enforced" mean in this context?+
That the rule is applied server-side and cannot be bypassed, including by an administrator. If someone with the right permissions can mark a deal approved without the approval actually happening, the workflow is documentation rather than a control. Ask vendors this specific question.
How are double payouts prevented?+
Through idempotency protection on payout batches: submitting the same batch twice produces one payment, not two. This matters most under exactly the conditions that cause it — month-end, someone unsure whether the first submission went through, clicking again.
Does this handle ZATCA e-invoicing?+
Not directly — a CRM does not issue tax invoices. What it provides is approved commission data with amount, split, deal reference, approver identity and timestamp, so your invoicing or ERP system can raise a compliant invoice from a reliable source instead of a reconstructed spreadsheet.
Can commission splits vary per deal?+
They should. Real brokerages run tiered rates, co-broke splits, referral fees and team overrides. The requirement is that whatever structure applies is recorded on the deal at approval time, not recalculated later from memory.