
Pixabay via Pexels
Most UK recruitment agencies run commission out of a billings spreadsheet that started life as a back-of-envelope job and was never killed off. It works — until the desk doubles, a placement gets rebated three months after the consultant was paid, or a contractor's margin is restated and the row formula silently breaks. At that point you are not looking for a 'better spreadsheet'. You are looking for recruitment commission software that understands how UK agencies actually bill.
TL;DR
Recruitment commission software is sales commission tooling built (or configurable enough) to handle the way agencies actually earn — split billings, perm fees with rebate periods, contract margins that move week to week, threshold/cost-of-sale models, and desk splits. When evaluating vendors, the five things that matter most are: (1) perm and contract logic in one place, (2) threshold tiers and accelerators that recalculate cleanly, (3) rebate and clawback handling tied to the placement, not the pay run, (4) desk splits and manager overrides as first-class objects, and (5) a clean export into your finance system — Xero in most cases. Anything else is a 'nice to have'.
Why a billings spreadsheet eventually breaks for recruitment
A recruitment commission spreadsheet usually breaks for a specific, predictable reason: the model assumes a placement is a single event with a single number. In practice, a perm placement under the Conduct of Employment Agencies and Employment Businesses Regulations 2003 is a number that can move — your terms with the hirer will usually specify circumstances where refunds and rebates are payable, and the consultant's commission has to follow the money that was actually retained, not the headline invoice.
Contract is worse. A contractor's weekly margin depends on the assignment rate, the pay rate, employer NICs, the apprenticeship levy if you are over threshold, holiday pay accrual, and — if the engagement is inside IR35 — whether your agency is the deemed employer for off-payroll purposes. None of that lives cleanly in a column. A spreadsheet that bills a £450/day contractor at a flat 20% margin will quietly mis-state consultant commission the moment any of those inputs change.
In practice, this is also where most clawback fights start. The root cause is almost always Finance paying commission on the gross signing-day or invoice-day value before the deal's rebate, opt-out or restatement window has closed. By the time the rebate hits, the consultant has spent the money and the correction is what does the cultural damage — not the original error.
If your commission model treats a placement as a single number, your software is going to lie to you the first time a rebate hits.
What does good recruitment commission software actually need to do?
At a minimum, recruitment commission software has to model the four things a generic SaaS commission tool usually fudges: perm fee logic, contract margin logic, splits, and rebate-driven clawbacks. Here is what each of those means in practice.
Perm fees with threshold tiers (cost of sale)
Most UK perm desks run a threshold model: the consultant earns nothing until they cover their cost of sale (often a multiple of base salary, or a quarterly £-billings figure), then a rising percentage of net billings above that. Good software lets you set the threshold as a value or a formula, recalculates the tier the moment a placement is restated, and shows the consultant exactly which £ of billings tipped them into the next bracket. For more on how to set those bands, see our guide to recruitment commission threshold tiers.
Contract margins, week by week
For contract, the software needs to compute commission on margin — charge rate minus pay rate minus on-costs — not on revenue. It should pull the inputs from your back office or timesheet system, recompute when a timesheet is amended, and handle rate uplifts and umbrella vs PAYE contractors. If the engagement is inside IR35, the off-payroll working rules for agencies typically make the agency the deemed employer when it pays a PSC directly, which means the margin (and therefore the commission base) is net of employer NICs and the apprenticeship levy. The tool needs to handle that mechanically, not via a sidecar spreadsheet.
Rebate clawbacks tied to the placement, not the pay run
This is the single biggest reason agencies move off spreadsheets. A perm rebate — a candidate who leaves inside the guarantee period — has to (a) reduce the fee actually retained, (b) recalculate the consultant's threshold position for that period, and (c) generate a clawback that either deducts from a future month or is written off, depending on policy. If your software cannot link the rebate back to the original placement record and replay the maths, you will end up doing it by hand. Our recruitment commission clawback and rebate guide goes deeper into how to structure the policy itself.
Desk splits and manager overrides as objects, not rows
A shared placement — a 360 consultant on the candidate side, a BD lead on the client side, plus a team leader override — should be modelled as a placement with three commission rows against it, each with its own percentage and approval status. If splits are a free-text column in a spreadsheet, every quarter-end becomes a forensic exercise. See recruitment desk splits and shared commission for the design patterns.
Clean export to Xero (or whatever you actually use)
The last mile is payroll. The software should produce a per-employee total, broken down by placement, and push it into Xero as either a bill or a pay item — without re-keying. We've covered the Xero commission integration in more detail; the principle is that the audit trail should survive the handover to Finance.
Recruitment commission software vs the billings spreadsheet: side by side
| Capability | Billings spreadsheet | Purpose-built commission software |
|---|---|---|
| Perm threshold recalculation when a fee is restated | Manual; often missed | Automatic; full replay |
| Contract margin pulled from timesheets | Re-keyed weekly | Live from back office |
| Rebate clawback tied to original placement | Free-text note | Linked record, auto-deduct |
| Desk splits and overrides | Extra columns | First-class objects with approvals |
| Consultant self-serve visibility | Emailed PDF, if that | Real-time dashboard |
| Audit trail for a disputed payout | 'Check git history of the file' | Versioned, per-row, per-change |
| Xero export | CSV someone hand-fixes | API-level push, reconciled |
What about contract complexity at the top end?
Once a single contract placement crosses roughly £100k of expected gross margin — long assignments, multi-year MSP deals, statement-of-work engagements — it stops behaving like a clean billings row. Custom rate cards, opt-outs, security reviews and rebate carve-outs appear, and that is precisely where commission errors hide. Comp logic that works on a £10k 14-day SMB perm placement does not survive a £350k multi-threaded contract book. If your agency lives in that space, the software needs to support per-placement overrides without forcing you off-piste into a spreadsheet 'just for this one'.
A worked example: where the spreadsheet quietly breaks
Take a perm consultant on a 20% threshold model. Cost of sale is £20,000 per quarter; they earn 15% of net billings above that, rising to 25% above £40,000.
- Month 1: they bill a £12,000 fee. No commission yet — under threshold.
- Month 2: they bill £18,000 and £14,000. Cumulative £44,000. Commission base: £24,000 ( £20,000 at 15% = £3,000; £4,000 at 25% = £1,000). Payable: £4,000.
- Month 3: the £14,000 placement rebates 50% — candidate left in week six. Retained fee drops to £7,000. Cumulative billings restate to £37,000. New commission base: £17,000 at 15% = £2,550.
The consultant was paid £4,000 and should have been paid £2,550. That £1,450 clawback was almost certainly created by paying commission on the gross signing-day fee before the rebate window had closed. A manager's job — and the job of the software — is to sanity-check the payout against the real contract terms before payroll runs, because once the wrong number lands in a pay packet, the correction is what corrodes trust. For the framing on that, see commission errors and trust.
If your standard hirer terms include a rebate period (sliding-scale refund if the candidate leaves within 8 / 12 / 26 weeks), commission should be calculated on the value you actually expect to retain, not the invoice value on day one. Either delay the payout until the rebate window closes, accrue against an expected-rebate rate, or pay against a provision you can claw back cleanly.
How should we shortlist recruitment commission software?
- Write down your actual plan in prose first. Threshold value, accelerator points, split rules, rebate policy, override percentages. If you cannot write it in a page, no software will save you.
- Stress-test each vendor against perm + contract together. Most generic SaaS commission tools handle perm fine and contract badly, or vice versa. Ask for a demo against your real plan, with a rebate event mid-quarter.
- Check the back-office and Xero integrations specifically. A weekly CSV upload is not an integration. You want API-level sync with your CRM/back-office and a reconciled push to Xero.
- Audit trail and consultant visibility. Can a consultant see how their number was built, in real time, without asking RevOps? Disputes are a visibility problem more than a maths problem.
- Implementation timeline and migration plan. Be realistic — see our commission software implementation timeline and migration guide.
Frequently Asked Questions
Is recruitment commission software different from generic sales commission software?
It has to handle two things generic tooling often fudges: contract margin (charge rate minus pay rate minus on-costs, recomputed weekly) and rebate-driven clawbacks tied to a specific placement. If a vendor's only model is 'closed-won deal × percentage', it will struggle on a recruitment desk.
Do we need separate software for perm and contract desks?
No — and you actively don't want two systems if the same consultants ever bill both. Use one platform that models perm fees and contract margins as different placement types against the same consultant record, so threshold and split logic compose cleanly across the desk.
How does IR35 affect the commission base for contract placements?
Where the agency is the deemed employer under the off-payroll working rules — typically when paying a PSC directly for a medium/large client — employer NICs and apprenticeship levy come out of the agency's margin before commission is calculated. Your software should compute commission on the post-on-costs margin, not on the gross charge rate. HMRC's off-payroll working rules for agencies set out who the deemed employer is in each labour-supply chain.
What about Key Information Documents and worker terms — do they affect commission?
Key Information Documents are a statutory requirement under the 2019 amendment to the Conduct Regulations and exist for the worker, not for your consultants. They don't change your internal commission model — but they do anchor the rate, deductions and umbrella arrangements that feed into your contract margin calculation, so they're worth cross-referencing when you set up a placement.
Should consultants see their commission in real time?
Yes. The single biggest driver of commission disputes isn't the maths being wrong occasionally — it's a correction landing in a pay packet with no warning. A live view of placements, threshold progress, pending rebates and expected payout prevents far more disputes than any cleverer plan structure ever will.
Ready to fix your commission process?
See your own comp plan running in Commit. 20 minutes, no slides.