Yes. An AI agent can calculate sales commissions and bonuses, provided the plan is written down as rules it can read and the deal data comes from the system of record. It prepares each statement at depth 2. A person who neither earns under the plan nor owns the deals approves the figures before anything reaches payroll.
What decides whether the agent can do it?
The deciding factor is the plan document, not the agent. Commission plans are often a mix of written rules, spreadsheet formulas and side agreements. An agent can apply rules. It cannot apply a promise nobody recorded.
So the first condition is that the plan exists as a single, approved version: rates, quota, accelerators above quota, split rules for shared deals, caps, and clawback terms for cancelled or unpaid contracts. The second is that deal values come from the contract and billing records, not from the pipeline field a salesperson typed in. The third is that the agent knows the trigger. A plan that pays on signature behaves differently from one that pays on cash collected, which is why collection timing, measured by days sales outstanding, can move a payout from one period to the next.
What may the agent prepare, and what stays with a person?
| Task | The agent | Stays with a person |
|---|---|---|
| Pulling closed deals | Reads signed contracts and billing records for the period | Deciding a deal counts when the records disagree |
| Applying the plan | Calculates base commission, accelerators and caps line by line | Interpreting a rule the plan does not cover |
| Split credit | Applies the recorded split | Resolving a dispute between two salespeople |
| Clawbacks | Identifies cancelled or unpaid deals inside the clawback window | Waiving a clawback |
| Discretionary bonuses | Lists the inputs the manager asked for | The bonus amount itself |
| Statements | Drafts one statement per person with every line referenced | Approving the total and sending it to payroll |
A bonus "at management discretion" is a judgement about a person's performance. The agent can assemble attainment, team results and the pool, but the number is a manager's decision, recorded as theirs.
Which step keeps the separation of duties?
Approval. The person who approves the commission run must not be paid under it and must not be the person who entered the deal data. A sales director approving their own team's payouts, when their own bonus depends on team attainment, is the conflict auditors look for.
The agent sits on the preparer's side of that line. It never approves its own statement or posts the payroll input. Every line of its draft references the contract, invoice and plan clause used, so the approver can test any line without redoing the work.
There is one more boundary. Commission expense often has to be spread over the contract term in the accounts rather than booked when paid. The agent can draft that schedule, but the accounting judgement sits with the people who handle revenue recognition terms in sales contracts.
An illustrative example
Take a software company with a quarterly plan. One salesperson closes three deals worth 40,000, 25,000 and 15,000 against a quota of 60,000. The plan pays a base rate up to quota and a higher rate above it.
The agent reads the three contracts and the billing records. It finds that the 15,000 deal was cancelled in its second month, inside the plan's clawback window, so it removes it and recalculates attainment at 65,000 rather than 80,000. It also finds that the 25,000 deal is recorded as a 50/50 split with a colleague, which the salesperson's own pipeline entry does not show.
The draft statement shows each deal, the rate applied, the split, the clawback and the plan clause behind each. The salesperson disputes the split. The agent does not decide it. It holds that line, routes the dispute to the sales operations lead, and sends the rest to the finance approver, who signs off the undisputed amount for payroll.
What controls make it safe?
- One approved plan version. The agent reads the plan from the policy library, and a change to the plan is itself an approved event.
- Deal values from records. Contract and invoice values outrank pipeline entries. Where they differ, the agent reports the difference instead of picking one.
- An independent approver. Named in advance, not paid by the plan, and recorded against each run.
- Line-level references. Every amount points to the contract, invoice and clause behind it.
- Disputes held, not resolved. A disputed line is held with the dispute attached; the rest of the run proceeds.
- Conduct checks. Plans that pay heavily on volume can push mis-selling. Pairing the calculation with reviews of sales calls for conduct risk lets you see whether high earners are also high-risk sellers.
The wider set of finance controls is in AI agents for finance: books you can audit.
Questions people ask
Can the agent explain a statement to a salesperson who queries it?
Yes, at depth 1 or 2. It can walk through each line and the clause behind it. It should not promise a correction; a change to an approved statement goes back through the approver.
What about plans that change mid-quarter?
The agent applies each plan version to the dates it covered, provided both versions and their effective dates are recorded. If the change was agreed informally, the agent flags the gap and a person records the decision first.
Should commission data be visible to the agent at all?
Only for the people and periods it is calculating. Pay data is sensitive, so the agent's access should be scoped to the commission run and its reads recorded like any other access.