Deal-ID matching + exception detection + working-paper generation — sales commission reconciliation in under 30 seconds per batch.
| Sales Rep | Deal ID | Customer | Inv. Amt (₹) | Rate % | Claimed (₹) |
|---|---|---|---|---|---|
| Acme Applicant | DL-2026-0499 | Acme Corp Ltd | 12,00,000 | 8% | 96,000 |
| Acme Applicant | DL-2026-0501 | Acme Corp Engg | 8,50,000 | 10% | 85,000 |
| Acme Applicant | DL-2026-0533 | Acme Corp Pvt Ltd | 6,00,000 | 8% | 48,000 |
At most mid-market companies, sales commission reconciliation is a manual, spreadsheet-driven process that consumes two to four analyst-days every quarter — and consistently misses at least one of the four classic exception classes before the payout run.
A finance analyst downloads the commission claim sheet, opens the sales register separately, and matches 50–300 deal IDs row by row — verifying rate, base, collection status, and deal existence one at a time. With a quarterly payroll cut-off that does not move, the analyst often runs out of time before completing all four checks.
A sales rep filing a claim at 10% on deal DL-2026-0501 may genuinely believe their slab is 10%, while the sales operations register records 8% — a ₹17,000 discrepancy on an ₹8,50,000 deal. Without an automated rate cross-check against policy_rate per deal, this passes to the payout run unchallenged.
A rep who claims commission on gross invoice amount of ₹6,00,000 for a deal where the register records a ₹2,00,000 customer return overstates their eligible base by 50%. Equally, paying commission on a deal with collection_status = Not Collected violates the standard commission policy and triggers a clawback when the payment fails.
A claim for deal DL-2026-9999 (₹3,20,000 at 8% = ₹25,600) that has no matching row in the sales register under any deal ID requires an explicit VLOOKUP-miss check. A filter-based manual review that focuses only on matched rows will never surface this gap — and the ghost deal proceeds to payment.
The typical quarterly overpayment exposure for a 150-deal portfolio at an average commission value of ₹50,000 per deal, where even one systematic rate mismatch or ghost deal goes undetected. Clawback proceedings and corrective TDS filings under Section 201(1A) of the Income Tax Act compound the cost well beyond the original overpayment.
Sales commission expense touches four distinct regulatory obligations — capitalisation under contract-cost standards, TDS compliance under the Income Tax Act, audit-documentation requirements, and internal-control evidence for COSO-aligned programs. A reconciliation gap in any of these creates exposure that outlasts the quarter in which it arises.
Incremental costs of obtaining a contract — including field-sales commissions — must be recognised as an asset and amortised over the expected benefit period if that period exceeds one year. Accurate per-deal commission records are the prerequisite for correctly computing the asset base and the subsequent amortisation schedule under this paragraph.
Channel-partner commissions exceeding ₹15,000 in a financial year attract TDS at 5% under Section 194H. An overstated commission payout inflates the deductible base; an understated payout triggers interest and penalty on short deduction under Section 201(1A). The reconciled approved amount — not the claimed amount — is the correct TDS base.
For US-incorporated entities or subsidiaries filing under US GAAP, ASC 340-40 (Other Assets and Deferred Costs — Contracts with Customers) mirrors Ind AS 115 Para 91 — requiring capitalisation of incremental contract-acquisition costs with the same one-year practical expedient. A clean deal-level reconciliation is the shared prerequisite for both standards.
Internal auditors reviewing commission payouts apply risk-based sampling under ICAI SA 530 and look specifically for rate inflation, base inflation, pre-collection payouts, and fictitious deals. A reconciliation working paper that cannot trace each approved amount to a matched deal ID with a documented exception disposition will result in a qualified finding and may prompt expanded external confirmations under ICAI SA 505.
Seven deterministic passes from raw commission claim and sales register to a signed-off approval working paper — in under 30 seconds per quarterly batch of up to 300 deal rows.
Accepts the commission claim sheet and the booked sales register uploaded together as Excel files. Cadel classifies each file automatically by detecting column headers — no labelling required. The claim sheet is identified by Rep Name, Deal ID, and Claimed columns; the register by Returns, Net Eligible Base, and Collection Status.
Every row is extracted from both documents into a structured format: rep_name, deal_id, customer, invoice_amount, commission_rate, and commission_claimed from the claim sheet; deal_id, returns_amount, net_eligible_base, collection_status, and policy_rate from the sales register.
Each commission-claim row is matched to a sales-register row by Deal ID (e.g., DL-2026-0501) using an exact, case-insensitive match after trimming whitespace. Unmatched claim-side Deal IDs are immediately flagged as Ghost Deals and isolated from all subsequent arithmetic — preventing a silent pass-through to the payout queue.
For each matched deal, the workflow reads net_eligible_base from the sales register — the gross invoice amount minus any recorded customer returns — as the approved commission base. Where the claim sheet uses the gross figure, the gap is calculated and surfaced as a Base Mismatch exception with the exact overstatement amount.
The workflow reads policy_rate from the sales register — not from the claim sheet — and recomputes the approved commission as net_eligible_base × policy_rate ÷ 100. Any difference between the claimed rate and the policy rate raises a Rate Mismatch exception with the disputed overage in rupees, e.g., ₹17,000 on deal DL-2026-0501.
For each matched deal, the workflow reads collection_status from the sales register. Where the value is not Collected, an Uncollected Deal exception is raised and the entire claimed amount is moved to the pending column — consistent with the standard commission policy that pays only on confirmed cash collection, not on invoicing.
The workflow produces a per-rep, per-deal working paper showing claimed amount, recomputed approved amount, exception type (Rate Mismatch / Base Mismatch / Uncollected / Ghost), and disputed amount. The working paper is exportable to Excel and provides the ICAI SA 230 documentation chain an auditor needs to clear commission expense without expanding confirmations under SA 505.
Six synthetic test scenarios covering every failure mode seen in real-world commission data. Each produces a deterministic outcome a controller or auditor can verify in seconds against the working paper.
collection_status = Not Collected.Two consolidated files covering one full commission period (Feb-2026). Upload them together — they share Deal IDs, so most rows reconcile cleanly and a handful seed each of the four exception classes.
33 deals reconcile end-to-end. The remaining 9 rows carry seeded rate mismatches, base/returns mismatches, uncollected deals, ghost deals, and one combined exception — each a separate test of the reconciliation engine.
The source of truth against which claims are validated. Two claim-side Deal IDs are deliberately absent here, surfacing as ghost deals. The net_eligible_base column already nets out the ₹2,00,000 return on DL-2026-0533.
Running the workflow across the consolidated demo pair — commission_claim.xlsx (42 deal rows) reconciled against sales_register.xlsx (40 rows) for Feb-2026 — produces five deterministic checks per matched deal pair. Two checks pass on single-file upload without the paired register: Entries List Non-Empty confirms the file has extractable rows, and Claimed Equals Recomputed verifies internal arithmetic (a clean deal claiming ₹96,000 = ₹12,00,000 × 8% passes immediately). The three cross-register checks — Rate Matches Policy, Base Matches Net Eligible, and Collection Required — execute once both files are present.
Of the 42 claimed deals, 33 reconcile end to end and nine carry seeded exceptions: two rate mismatches (including DL-2026-0501 with a ₹17,000 overage), two base/returns mismatches (including DL-2026-0533 with a ₹16,000 overage), two uncollected deals (including DL-2026-0567 with ₹36,000 deferred), two ghost deals, and one combined rate-and-base break. Total disputed amount across all nine exceptions: approximately ₹1.4 lakh on a total claimed batch of ₹21 lakh.
The most instructive exception class is the ghost deal: a claim for Deal ID DL-2026-9999 with no matching row anywhere in the register returns a Deal ID Exists failure. Because there is no approved amount to compute, the entire ₹25,600 claimed is moved to the disputed column and the working paper flags the item for escalation to sales operations and internal audit. A filter-based manual review that processes only matched rows will never surface this; only an explicit lookup-miss check — or Cadel's automated ghost-deal isolation — catches it before the payout run.
A sales commission reconciliation cycle that previously consumed two to four analyst-days per quarter — matching deal IDs, verifying policy rates, checking collection status, and hunting for returns adjustments across two spreadsheets — completes in under 30 seconds on Cadel. All four exception classes are detected deterministically on every run; no exception is skipped because the analyst ran out of time before the payroll cut-off.
Manual review catches whichever exception class the analyst checks for; it rarely checks all four simultaneously under time pressure. Cadel evaluates rate, base, collection status, and deal existence as parallel, independent checks — so a deal with both a rate mismatch and a base mismatch surfaces both flags, not just the first one that trips the reviewer.
The approved commission — not the claimed amount — is the correct base for TDS deduction under Section 194H. An automated working paper that separates approved from disputed per rep gives the payroll or accounts-payable team the exact per-partner deductible amount without a separate manual calculation, reducing interest exposure under Section 201(1A).
The working paper produced per run is timestamped, exportable to Excel, and traces each approved amount to a matched deal ID with the exception disposition documented. This satisfies ICAI SA 230 documentation requirements and the COSO 2013 control-activity evidence an internal or statutory auditor needs to clear commission expense without expanding confirmations under SA 505.
The questions finance controllers and internal auditors ask before deploying commission reconciliation automation.
Two files for the same period — the commission claim sheet (Sales Rep, Deal ID, Customer, Invoice Amount, Rate, Claimed) and the booked sales register (Deal ID, Customer, Invoice Amount, Returns, Net Eligible Base, Collection Status, Policy Rate). Cadel classifies each file automatically, so you can drop them together.
Every commission-claim row is matched to a sales-register row by Deal ID (e.g. DL-2026-0503). A claim Deal ID with no row in the register is flagged as a ghost deal; a register Deal ID with no claim is surfaced as register-only so nothing is silently dropped.
Each matched deal runs five deterministic checks — Deal Id Exists, Rate Matches Policy, Base Matches Net Eligible, Collection Required, and Claimed Equals Recomputed. Anything that fails appears in the Exceptions view with the field-level delta that tripped it (rate mismatch, base/returns mismatch, uncollected deal, or ghost deal).
Under Ind AS 115 (Revenue from Contracts with Customers) and its US GAAP equivalent ASC 340-40, incremental costs of obtaining a contract — including sales commissions — must be capitalised and amortised over the expected benefit period (subject to the one-year practical expedient). A clean, auditable reconciliation between the claim sheet and the register is the prerequisite for determining that expense base correctly.
For each Deal ID the working paper records the claimed amount, the recomputed amount (net eligible base × policy rate), the exception class if any, and the approved-versus-disputed split per rep. It is timestamped and exportable to Excel, providing the documentation chain expected under ICAI SA 230 (Audit Documentation) and the COSO 2013 control-activity evidence an internal or statutory auditor looks for.
The workflow uses the single policy rate stored per deal in the register’s Policy Rate column. Tiered or accelerator slabs (e.g. 8% up to ₹10,00,000, 10% above) should be pre-resolved by sales operations into a blended or split rate before upload; native tiered-rate computation is a planned enhancement. Until then the disputed column correctly flags any claim that does not match the single rate on file.
No. The exception checks are deterministic against the data as submitted, so if the claim sheet and the register are altered to show the same fabricated figure the arithmetic will reconcile. Detecting that pattern needs an independent source (bank receipts, GST e-invoices, GSTR-1), which is a separate forensic procedure under ICAI SA 240.
Yes — export the full reconciliation table and the per-rep approval working paper to Excel from the Inbox toolbar once the run completes.