Systems and records
Sales commission dispute dataset: the rules and evidence a task needs
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
A commission dispute task needs the signed compensation plan version in force when credit was earned, the crediting, timing and adjustment rules it sets, CRM change history for owner, amount, stage and close date, the executed customer contract and amendments, recorded approvals, and later invoicing, cancellation or payment evidence. The answer cites the controlling clause and facts, not the CRM's current value.
License terms
Sales commission dispute
Key takeaways
- The signed plan version in force on the earning date is the rulebook; the CRM supplies dated facts.
- Current CRM values reflect later edits, so tasks need field history with the source of each change.
- Executed contracts and authorized approvals outrank CRM fields, emails and chat.
- Good tasks reward naming unknowns and routing plan silence to the plan owner.
- Individual pay amounts are not needed to test rule application and should stay out of the data.
What rules and evidence belong in a sales commission dispute task?
A commission dispute task needs the rule and the facts as they stood when credit was earned: the signed compensation plan version and any amendment in force, the crediting, timing and adjustment rules it sets, the CRM change history for owner, amount, stage and close date, the customer contract and its amendments, recorded approvals for exceptions, and later evidence such as invoicing, cancellation or nonpayment. The correct answer cites the controlling term, not the CRM's current value.
Disputes are rule questions because the law often requires the rule to be written down. California Labor Code section 2751 requires that when an employee's pay involves commissions for work in the state, the contract be in writing and set out the method by which commissions are computed and paid, and that the employer give the employee a signed copy and obtain a signed receipt. New York's Department of Labor says a commissioned salesperson's agreement must be in writing, signed by both sides, and describe how wages, salary, drawing accounts and commissions are calculated.
That written plan is the rulebook a task is built around. The CRM, billing system and contract repository supply the facts. A good task forces a model to read both and reconcile them, which is the work revenue operations and finance teams actually do when a rep disputes a statement.
The same structure applies to rules that are not commissions in the legal sense, such as spiffs, accelerators and team bonuses, as long as a written document states them. What matters for the task is that the rule can be quoted, dated and tied to a version a reviewer can open.
Why the CRM's current value is rarely the right answer
The CRM shows what a deal looks like today, after reassignments, amount edits and stage changes; a commission is usually earned on what was true at a particular moment. The task therefore needs the history, not the snapshot.
Salesforce adds an entry to an opportunity's stage history whenever a user changes the Amount, Probability, Stage or Close Date fields, and admins do not choose those fields. Other fields, including the ones that often matter most in a dispute such as owner, territory or a split field, are only tracked if an admin selected them for field history, which allows up to 20 fields per object and keeps data for up to 18 months unless Field Audit Trail is used.
HubSpot shows each prior value of a record property with its date and the source of the change, such as a manual edit, an import or a workflow, and lets admins export a property's history. The source matters in a dispute: an owner change made by a territory workflow and one typed by a manager carry different weight under most plans.
If history for a disputed field was never tracked, or has aged out, the case may still be usable, but the task must say which fact is unknown and the answer key must reward a model that notices it.
Export the history before building cases, not when a buyer asks. Retention windows keep moving forward, and a dispute from last year can lose its deciding owner change while the brief is still in review.
What kinds of commission disputes make usable tasks?
Most disputes fall into a handful of patterns, and each needs a specific rule from the plan and a specific record to settle it. Covering several patterns keeps a task set from teaching one shortcut.
Find candidates where disputes already leave a trail: statement inquiry tickets, manual adjustments in the compensation tool, split requests, and exception approvals. A dispute that was raised, investigated and resolved with a written reason is the best raw material, because the resolution note shows which clause the team relied on. Treat that note as a hypothesis, though, not the answer key; reviewers rebuild the answer from the plan and the records and record any case where the historical resolution was wrong.
| Dispute pattern | Plan rule needed | Deciding evidence | Typical trap |
|---|---|---|---|
| Split or shared credit | Crediting and split rules, including who approves splits | Split approval record, opportunity team history | Reading the current owner as the sole earner |
| Owner or territory change before close | Reassignment and territory rules, effective dates | Owner field history with source and timestamp | Using the owner at payment time |
| Timing of when credit is earned | Earning event: signature, booking, invoice or cash receipt | Contract signature date, invoice and payment records | Treating close date as the earning event |
| Amount changed after close | Adjustment and true-up rules | Executed amendment, amount history | Crediting the pre-amendment amount or ignoring a downsell |
| Cancellation or nonpayment | Chargeback or adjustment terms in the written plan | Cancellation notice, accounts receivable status | Applying a recovery the plan does not state |
| Draw reconciliation | Draw and settlement terms | Draw ledger reference and plan clause | Assuming a draw is repayable without a written term |
| Plan changed mid-period | Plan version effective dates and acknowledgment | Signed acknowledgment of each version | Applying the new plan to deals earned under the old one |
The compensation rule task brief, field by field
The task brief is the asset: a fixed set of fields that turns one dispute into a question with a provable answer. Each field names its source, and a field that cannot be sourced is marked unknown so the answer key can reward a model that says so.
At a glance
The compensation rule task brief, field by field
Have a revenue operations lead and someone who knows the plan's legal and contractual context review each brief before it is used. The brief records who reviewed it and against which plan version.
Keep the brief self-contained. A model working the task should find every clause and record it needs inside the brief, with record IDs that point back to the source for audit. Anything the model would have to look up elsewhere either belongs in the brief or should be listed as unknown, so the task measures reasoning over the evidence rather than access to systems.
| Field | Contents | Source | Check before use |
|---|---|---|---|
| dispute_question | The exact question, such as who earns credit and in which period | Rep's dispute ticket or statement query | One question per task |
| plan_version | Plan document version, effective dates, signed acknowledgment | Compensation plan repository, HR system | Version in force on the earning date |
| rule_clauses | The clauses that decide the question, quoted by section | Plan document | Clause text matches the version above |
| account_entities | Account, parent, subsidiaries and opportunity IDs | CRM | Entity hierarchy as of the earning date |
| field_history | Owner, amount, stage, close date and split changes with source | CRM history exports | Coverage for the disputed period confirmed |
| customer_contract | Signed order form or agreement and amendments, with dates | Contract repository, e-signature records | Executed versions only |
| approvals | Split, exception and reassignment approvals with approver role | Approval tool, CRM approval history | Approver had authority under the plan |
| downstream_events | Invoices, payments, cancellations, credits | Billing and accounts receivable | Linked by contract or account ID |
| answer_key | Decision, controlling clause, controlling facts, unknowns | Reviewer | Two reviewers agree |
| exclusions | Fields withheld or generalized, such as rates and individual earnings | Preparation log | No individual pay amounts remain |
Which record wins when the plan, the CRM and the contract disagree?
The signed plan version controls the rule, the executed customer contract controls what was sold, and recorded approvals control exceptions; CRM fields are evidence of timing and ownership only when their history supports them. Write this ranking into the task so the model is tested on applying it.
Two conflicts deserve special handling. When two plan versions both claim the earning date, usually because an acknowledgment was signed late, the case needs the effective-date clause and the acknowledgment record, and if neither settles it the answer is escalation. When the CRM history shows a change made by an integration or workflow, check the configuration that drove it; an automated owner change that the plan does not recognize as a reassignment can still be the wrong basis for credit.
- Signed compensation plan and acknowledged amendments in force on the earning date.
- Executed customer agreement and amendments, for what was sold, when and on what terms.
- Recorded approvals by someone the plan authorizes, for splits, reassignments and exceptions.
- Billing and payment records, for earning events tied to invoice or cash.
- CRM field history with its change source, for ownership and timing.
- Current CRM values, emails and chat, as context only.
Worked example (illustrative): a deal reassigned two weeks before close
All facts in this example are invented for illustration. A rep works an opportunity for five months. Two weeks before the customer signs, a territory realignment workflow reassigns the account to a second rep, and the opportunity owner changes with it. The second rep sends the final proposal. The customer signs, is invoiced the following week and pays within 30 days.
The plan in force says credit follows the owner on the signature date, except that a rep who held an opportunity for at least 90 days and lost it through a territory realignment within 30 days of signature shares credit equally with the new owner, provided sales operations approves the split. A sales operations manager approved the split in the approval tool on the day of signature.
Answer key: credit is shared equally, because the signed plan's realignment clause applies, the field history shows the owner change came from the territory workflow 14 days before signature, the first rep held the opportunity well past the 90-day threshold, and the approval exists and predates the earning event. The CRM's current owner, the second rep alone, is the trap.
Exception, built as a second task: the same facts, but the owner change was a manual edit by the second rep's manager with no realignment record, and no split approval exists. Under the same plan, credit goes to the owner on the signature date, and the dispute goes to the escalation path the plan names. A model that applies the realignment clause anyway has inferred a fact the records do not show.
A third variant tests timing. The customer cancels within the plan's adjustment window and the invoice is credited. The answer turns on whether the written plan states an adjustment for cancellation; if it does not, the correct answer says the plan is silent and routes the question to the plan owner rather than inventing a recovery.
Scoring a commission answer on reasoning, not arithmetic alone
Score the reasoning first: the right clause, the right facts and the right handling of unknowns. Arithmetic matters, but a correct number reached through the wrong clause will fail on the next case.
Grade with the brief's answer key, not with the historical payment. Past statements sometimes reflect a manager's discretion, an error later corrected, or a settlement of the dispute, and none of those is the rule. Where the historical outcome and the answer key differ, keep the case and note the difference, because it is exactly the situation a model will meet in production.
| Dimension | Credit for | Common failure | What the grader checks |
|---|---|---|---|
| Controlling rule | Citing the clause in the plan version in force | Using a later plan or a summary slide | plan_version and rule_clauses |
| Controlling facts | Citing dated history and executed documents | Reading current CRM values | field_history and customer_contract |
| Authority | Checking that approvals came from an authorized role | Accepting any approval | approvals |
| Unknowns | Naming facts the records cannot establish | Filling gaps with plausible assumptions | answer_key unknowns |
| Escalation | Routing plan silence or conflict to the plan owner | Inventing a rule | answer_key decision |
Where payroll and accounting records fill the gaps
Payroll and accounting often hold the records that settle timing and amount questions after the CRM has moved on, and they keep them on their own schedules. Under the Fair Labor Standards Act recordkeeping rules, employers preserve payroll records for at least three years, and records on which wage computations are based, such as wage rate tables and records of additions to or deductions from wages, for two years.
Accounting adds another trail. Under the revenue recognition standard, an entity recognizes as an asset the incremental costs of obtaining a contract that it expects to recover, a category that commonly includes sales commissions, with a practical expedient to expense them when the amortization period is one year or less. Where commissions are capitalized, finance may keep a schedule tying each commission to a contract, which is useful evidence for linking a credit to a deal.
Use these records to establish dates and links, not to carry pay amounts into a dataset. Individual compensation is sensitive employee information, and the task does not need it to test whether a model applies the right rule.
Commission disputes to leave out of a task set
Leave out disputes that cannot be settled from records, and those where using the records would create a problem bigger than the task is worth.
De-identification has limits on small sales teams. Replacing names with surrogates does not help when only one rep covered a territory in a given quarter, so generalize territories and periods, or drop the case, when the combination of facts would point to a single person.
- Disputes that became wage claims, arbitration or litigation, or are under a legal hold.
- Plans that leave crediting to management discretion with no recorded reason, so no answer key is provable.
- Cases that only make sense with individual earnings, rates or quota attainment visible.
- Disputes whose deciding approval happened in a meeting with no record.
- Customer contracts whose confidentiality terms bar this use, until counsel clears them.
- Small teams where a de-identified case would still point to one person.
Can revenue records be licensed together with their governing terms?
Companies that keep signed plan versions, CRM history and linked billing records hold the kind of rules-and-evidence material these tasks need, and that combination rarely appears in public data. When a revenue team licenses records of this kind as AI datasets through SourceX, the rights review, contract work, preparation and delivery are handled within that engagement.
No data upload is needed for the opening company assessment. Compensation amounts, employee identities and particular customers can be excluded or de-identified from the outset, since the company settles scope and terms in a signed agreement before anything is delivered.
Frequently asked questions
What should a compensation rule task brief include?
It should hold the dispute question, the plan version and the clauses that decide it, account and opportunity IDs, CRM field history with change sources, the executed customer contract, approvals, downstream billing events, an answer key and an exclusion record. Each field names its source, and unsourceable facts are marked unknown.
Which signed term or later outcome can contradict the CRM's apparent answer?
An executed amendment can change what was sold, a split approval can change who earns credit, and a cancellation or nonpayment can change whether credit stands under the plan's adjustment terms. The CRM's current owner and amount reflect later edits, so the history and the signed documents decide.
Do commission plans have to be in writing?
In some states, yes. California requires a written contract that sets out how commissions are computed and paid, with a signed copy given to the employee, and New York requires a signed written agreement for commissioned salespeople. Requirements vary, so counsel should confirm the rules that apply.
Can a commission dispute dataset include what reps were actually paid?
It should not need to. The task tests whether a model applies the right rule to the right facts, which works with amounts generalized or removed. Individual pay is sensitive employee information and is better left in payroll.
When should a commission dispute go to a person instead of a model?
When the plan is silent or ambiguous on the question, when two plan versions or approvals conflict, or when the deciding fact is missing from the records. A good task rewards a model for recognizing those cases and routing them to the plan owner.
Sources
- California Labor Code section 2751 requires that when an employee's pay involves commissions for work in the state, the contract be in writing, set out how commissions are computed and paid, and that the employer provide a signed copy and obtain a signed receipt. Source
- New York's Department of Labor says a commissioned salesperson's agreement must be written and signed by both parties, describe how wages, salary, drawing accounts and commissions are calculated, and state any draw repayment terms for a draw to be recoverable. Source
- Salesforce adds an entry to an opportunity's stage history whenever Amount, Probability, Stage or Close Date changes, and admins cannot select which of those fields are tracked. Source
- Salesforce standard field history tracking allows up to 20 fields per object and retains history for up to 18 months unless Field Audit Trail is used. Source
- HubSpot shows each prior value of a record property with its date and change source, and property history can be exported. Source
- The U.S. Department of Labor says employers preserve payroll records for at least three years and records on which wage computations are based, such as wage rate tables, for two years. Source
- FASB's revenue standard update says an entity recognizes as an asset the incremental costs of obtaining a contract it expects to recover, and may expense them when the amortization period is one year or less. Source
See if your company qualifies
A short company assessment. No data uploads are needed.