TL;DR
- Define the commissionable event before selecting integration tooling: booking, invoice, collected cash and recognised revenue produce different earnings.
- QuotaPath and CaptivateIQ are relevant calculation/administration candidates. Neither removes the need to reconcile source events, amendments, refunds and crediting policy.
- Preserve event IDs, source versions and adjustment entries. Replaying an integration must not create another commission payment.
- For 1,000 deal lines and 20 disputed splits, reconcile counts and value, then resolve ownership exceptions before locking the payout period.
Choose what earns commission
A CRM opportunity closes for £100,000, the first invoice is £25,000 and the customer pays £20,000 after a credit. Each system can be correct while showing a different amount. The compensation policy must decide which event and amount earn commission.
Define booking, invoice, collection and revenue separately. A booking-based plan may create earnings before cash arrives. A collection-based plan may defer them. A hybrid plan may have several components. No connector should make that policy implicitly by choosing the easiest available field.
Also specify currency conversion, product eligibility, crediting date, cancellations, refunds, amendments and employee treatment. Approved plan rules should be versioned with the payout period. A rule changed in November should not silently rewrite an approved October payout.
This guide covers the data contract and reconciliation. The forecasting-platform comparison concerns pipeline and forecast visibility, which is a different source of truth from an approved compensation ledger.
The systems have different responsibilities
| Layer | Owns | Should not silently decide |
|---|---|---|
| CRM | Opportunity, selling ownership and commercial context | Whether an invoice was actually paid |
| Billing/payment system | Invoice, payment, credit and refund events | Seller split or compensation plan eligibility |
| Integration | Reliable delivery, mapping and replay | Commercial policy or authorised split changes |
| Commission platform | Versioned calculation, review and earnings workflow | Which conflicting source amount is true without a defined rule |
| Finance/payroll | Approved payout and accounting reconciliation | Recalculate an undocumented commercial exception |
Keep source event time, received time and payout period separate. A refund can arrive after the original earning period closes. The policy decides its treatment; the integration must preserve enough information to apply it.
QuotaPath for visible earnings administration
QuotaPath's public offering presents commission tracking, calculation and earnings workflows. It is a sensible candidate where sales and operations need to understand how a plan translates deal activity into earnings.
The buying advantage is visibility for reps and administrators. A clear earning line can reduce disputes caused by unexplained totals. It should link to the underlying deal/event and show the rule rather than merely present a final number.
Choose it where its plan model and workflow fit the compensation programme. It is a weaker answer if source identity and amendment handling are unresolved. Its pricing page is the current scoping route. Public signup and plan material can differ in context, so no unqualified entry amount is used here. Obtain the selected plan, users, integrations, payout functions, contract term and support. A calculated earning is not automatically authorised for payroll.
CaptivateIQ for configurable compensation operations
CaptivateIQ's current platform describes incentive compensation management. It deserves evaluation when compensation operations requires configurable calculations, data handling and administration across a more complex programme.
The useful demonstration starts with your plan and source events: a multi-line booking, split credit, later amendment and refund. Inspect the resulting earning entries and how an administrator explains them. A clean demonstration of one standard deal does not establish the harder reconciliation behaviour.
Choose it when plan complexity and operating scope justify dedicated administration. It is less compelling for a small simple plan already managed safely in an existing system. No current scope-comparable public quote was established. Price participants, administrators, integrations, implementation and support together. Configuration capability does not substitute for an approved compensation policy or independent finance control.
A reconciliation contract for 1000 lines
For the proposed 1,000 deal lines, assign durable opportunity, contract, invoice-line and source-event identifiers where applicable. A human-readable deal name is not an adequate join key. Preserve product, amount, currency, effective date, seller credit and source version.
Build an event ledger before calculating earnings. The integration should record an event once, acknowledge delivery and support controlled replay. Stripe's webhook documentation notes issues such as duplicate delivery and event ordering; those are useful examples of why payment integrations need idempotency rather than assume arrival order is the business sequence.
Reconcile both count and value. A missing £100,000 line and an extra £100 line can make row count appear correct while value is wrong. Compare source totals by currency, period and event type. Do not sum GBP and USD as if they were one unit.
Useful exception states include missing source event, unmatched contract, duplicate event, conflicting version, invalid split and unsupported currency treatment. Give each an owner. A pipeline that logs exceptions but still includes them in automatic payout has not established a control.
The RevOps CRM setup playbook helps define durable CRM ownership and identifiers. The CRM activity-sync guide covers a lower-stakes integration pattern; compensation needs additional financial reconciliation.
Handle amendments and refunds as events
Suppose an illustrative £100,000 booking earns 10%, or £10,000, under an approved booking-based plan. A later £20,000 cancellation may produce a £2,000 reversal if the plan's clawback policy applies. A collection-based plan could behave differently. These are policy examples, not legal advice or universal commission rules.
Preserve the original earning and add an adjustment referencing it. Overwriting the booking to £80,000 makes historical approvals harder to explain. If the period is locked, route the adjustment according to policy rather than silently alter an already exported payroll file.
Amendments need version and effective date. A £30,000 expansion should not accidentally reprocess the entire £130,000 contract as a new sale. Distinguish incremental value from replaced line items. Test whether the source emits a changed snapshot, an explicit delta or both.
Refunds can arrive late or in several parts. Reconcile their relationship to the original invoice and earning. A replayed refund should not reverse the same commission twice. Keep authorised manual corrections as explicit ledger entries with actor and reason.
Resolve 20 disputed splits
The proposed 20 disputed splits represent 2% of 1,000 deal lines, but their value may be much larger or smaller than 2% of compensation. Report line count and financial exposure separately.
For a hypothetical £10,000 earning split 60/40, the two credits are £6,000 and £4,000. A confirmed change to 50/50 requires a £1,000 reduction for the first seller and a £1,000 increase for the second. The total remains £10,000. Reconciliation should catch a correction that adds £1,000 without the offset.
Require the authorised owner to approve the split and effective date. Preserve the original claim, evidence and decision. Do not let an integration treat the latest CRM owner as the seller who earned every historical line; territory reassignment and staff changes can make that wrong.
Where a dispute is unresolved at cutoff, follow the documented policy for holding or paying undisputed amounts. The system should make that state visible to finance and the affected rep rather than hide it in a technical error queue.
Budget controls before automating payouts
Assume each of 20 disputes takes 30 minutes to investigate: ten hours. Add four hours for period reconciliation and two hours for approval/export checks. At an assumed £50 loaded hourly cost, the 16-hour period cost is £800 before software and integration.
If automation reduces dispute preparation but the underlying policy remains disputed, savings may be small. Do not assign the entire disputed earning value as a benefit of software; resolving who receives £10,000 does not save the company £10,000.
Run a shadow period against the existing approved calculation. Compare counts, value, split totals, amendments and refunds, then inspect the resulting payroll output. Use a controlled replay to verify that the second run does not add earnings or reversals. Record differences and resolve them before automatic payment.
Choose QuotaPath or CaptivateIQ around plan fit and operations, then buy integration scope that preserves the evidence contract. The RevOps platform guide covers the surrounding revenue estate. The decisive control here is a reconciled, approved ledger, not the number of connected systems.
FAQ
Should CRM or billing determine the commission amount?
The approved plan determines that. CRM may supply booking value and seller context; billing supplies invoice, collection and refund evidence. State the authoritative source for each plan component rather than choose one system for every field.
Can we just recalculate the whole month after a refund?
Recalculation can help analysis, but approved and paid periods need a controlled adjustment policy. Preserve the original earning and show the reversal or correction explicitly. Otherwise finance and reps may see a changed historical total without an explanation.
What makes a commission integration idempotent?
A repeated source event produces the same ledger result without another earning or reversal. Use durable identifiers and version rules, and test replay and duplicate delivery. A successful API response alone does not prove this property.
Do calculated commissions belong directly in payroll?
Only after the defined reconciliation and approval controls pass. Keep calculation, authorisation and payment states separate. An administrator should be able to explain the exact source and rule behind every exported payout line.
