Commission tracking that lives next to the deal, not on a separate invoice.
Model tiered rates, accelerators, SPIFFs, kickers, splits, draws, and clawbacks inside Strkr. Reps see a live earnings tile. Managers approve statements. Finance exports a GL journal. Disputes have an audit trail. No separate Spiff or CaptivateIQ seat, no CSV round-trip, no month-end reconciliation panic.
What commission tracking should actually do in 2026
The gap between the spreadsheet and the sales floor.
Every sales org that pays commissions has the same bruise. Deals close in the CRM. Rates and splits live in a sales-comp spreadsheet nobody wants to open. Attainment is approximated at the end of the quarter. Reps dispute statements by DM. Finance reconciles against the ledger by hand. The whole motion is a monthly fire drill that burns a sales ops lead, a finance analyst, and a controller for the first two weeks of every month. The useful question is which parts of that mess a credible commission system should remove. In 2026, the bar is a specific list of workloads: plan modeling with tiered rates and accelerators, deal-level attribution with splits and overrides, real-time attainment visibility for reps, draw and recoverable-draw accounting, clawback rules on refunded or churned revenue, a dispute workflow with evidence attachments, signed commission statements, and a clean GL export. The checklist below is the one every revenue leader should walk every vendor through before signing. Strkr ships all nine inside the CRM, so the deal, the credit, the rep, and the statement never leave the same system.
Plan modeling
Tiered rates, accelerators, decelerators, caps.
Build a plan with base rate, tiered rates by attainment band, accelerators above 100 percent of quota, decelerators on strategic discount depth, and hard or soft caps. The plan editor is a form, not a spreadsheet macro. Each band is a row, each row has a floor, a ceiling, and a rate, and the preview panel shows a worked example at 60, 100, and 140 percent of quota. Finance approves the plan once. The engine applies it to every deal from that day forward.
Deal-level attribution
Splits, overrides, team credit, SPIFFs.
A deal can credit one rep, two reps at 60/40, a rep plus a sales engineer at a flat override, and a manager at a team-override rate on top of all of it. Add a SPIFF for the quarter. Add a kicker for a new-logo bonus. The deal page shows every credit line as a stacked bar, labeled, with the rate and the dollar amount. Nothing is hidden in a formula. Every rep whose number is affected can see exactly why.
Real-time attainment
Reps see a live earnings tile.
The rep home page shows quota, attainment, next tier threshold, and projected commission at close for every open opportunity. Close a deal and the earnings tile moves inside sixty seconds. No month-end surprise. No "I thought I was at 112 percent." The tile is sourced from the same deal data the manager sees, so the two numbers are always the same number, and the "my commission says one thing, the dashboard says another" conversation ends.
Draws and recoverable draws
Guaranteed pay with the right ledger.
New reps on a six-month recoverable draw get the draw credited each pay period and the earned commission applied against the balance until the draw is paid down. The ledger shows the running balance, the recovery rate per period, and the projected date the rep goes "above draw." Non-recoverable draws and hybrid plans are first-class. Finance never has to rebuild the arithmetic in a side spreadsheet because the engine already models the two most common draw structures and a dozen variants.
Clawbacks
Refund, churn, chargeback - commission adjusts.
A customer refunds inside the clawback window and the engine debits the earlier credit, writes a negative line on the rep's next statement, and tags the deal with the clawback reason. The rule set covers full refund, partial refund, cancel inside first 90 days, and churn under contract. Each rule has a window, a scope, and a formula. Reps know the terms up front because the plan document shows the clawback section, and finance has an audit trail that explains every negative adjustment.
Dispute workflow
A rep flag turns into an audit trail.
A rep opens a line item on their statement and clicks Dispute. They attach a note, point to a deal, and the dispute lands in the sales ops queue. The ops lead sees the deal data, the plan rule, and the computed amount side by side, approves or adjusts, and the statement reflects the resolution. Every dispute has an owner, a status, a decision, and a timestamp. The DM-based dispute motion that costs managers two days a quarter disappears.
Signed statements
Monthly statement, e-signed by the rep.
At the end of each period the engine generates a statement per rep: deals credited, splits applied, SPIFFs earned, clawbacks taken, draw activity, net payable. The rep reviews, acknowledges, and e-signs the statement. The signed PDF stores on the rep's profile and in the dispute history. Finance has a clean "the rep agreed to this number" artifact for every pay period, which protects both sides when a dispute surfaces three months later.
GL export
A single journal entry for finance.
At period close the engine emits a GL-ready journal entry: a row per rep, a row per cost center, a row per account code, totals matching the statements to the penny. Export to CSV or push into the accounting system. The ERP-reconciliation step collapses from a week of hand-reconciling to a copy-paste. No more "finance and sales ops are off by $413 and nobody can find the deal."
Audit trail
Every edit, every override, every signoff.
Every plan edit, deal-credit change, split override, manual adjustment, dispute decision, and statement signoff writes to the activity log with actor, timestamp, before, and after. SOX-leaning companies can run a one-query audit instead of a six-week engagement. Every number on every statement traces back to a specific decision by a specific user on a specific day, with the authorizing permission attached.
How Strkr commissions runs inside the CRM
Native plan engine, native deal data, native permissions.
Spiff, CaptivateIQ, Everstage, Palette, Varicent and QuotaPath all solve the commission problem by sitting next to the CRM, pulling deal data, running the math on their side, and sending the output back as a statement. The pattern works, but it imposes a second system of record, a second permission model, a second audit trail, and a second seat line. Strkr runs the commission engine inside the same Postgres and the same permission model as the pipeline. The deal, the credit, the rate, and the statement are rows in the same database. The upshot is that nothing about the commission system is a parallel universe. There is no sync lag between the CRM and the comp tool. There is no "the CRM says the deal closed on the 29th, the comp tool thinks it was the 1st" discrepancy that pushes a $14,000 line into the wrong period. There is no second vendor contract, no second data processing agreement, and no second security review.
One system of record
The deal and the credit live in the same row.
A closed deal has credit lines on it, inline, in the same record. The credit is not a nightly-sync approximation. It updates the moment the deal closes, the stage flips, the amount changes, or the owner reassigns. Reconciliation between the pipeline and the comp tool stops being a task because there are not two tools to reconcile.
Permission-aware
A rep can only see their own statement.
Commission data inherits the full permission model. Reps see their own numbers. Managers see their teams. VPs see their orgs. Finance sees everything. The field-level access model keeps draw details out of a rep's view of a peer's statement. No bypass, no shadow service account, no "someone forwarded me a comp sheet by mistake" story.
Audit log unified
One query covers the whole trail.
Every commission edit is in the same activity log as every pipeline edit. A SOX auditor runs one query across one log. A dispute decision shows next to the deal stage change that drove it. The "I need to pull records from two systems and timestamp-align them" pain disappears entirely, which also removes a frequent source of audit findings.
Confidence surfaced
Projected is labeled projected.
The rep tile distinguishes earned commission (closed-won, inside the plan period) from projected commission (open pipe weighted by probability). The two numbers are different colors. Reps know which part of the number they can bank. Managers know which part is still soft. Finance sees only the earned column in the GL. The clarity prevents the single most common comp dispute: "I thought this deal counted."
Human in the loop
Nothing pays out without manager approval.
Statements generate automatically, but they do not finalize until the manager reviews and approves. The manager sees the engine's computation, can override any line with a reason code, and signs off before the statement sends to the rep. The pattern is "the system does the math, the human owns the number." Overrides are rare, logged, and tied to a reason, so patterns in override activity become a diagnostic signal.
Tenant-isolated
Your comp plan is not benchmarked across tenants.
Plans and rates are tenant-scoped. Nothing is pooled across tenants to inform a benchmark report. The customer-trust bar every sales leader asks about ("my plan is not training data for a competitor's AI") is met by default. Security review becomes a one-paragraph attestation instead of a six-page questionnaire about the comp subsystem.
Field-grounded
Every statement line cites its source deal.
A statement row for $4,120 of commission links to the deal, the rate band that applied, the split percentage, and the policy document that defined the structure. The reasoning is retrieved from live records, not an approximation. A rep clicks through to the source of every claim. "Why is this number this number" becomes a thirty-second answer instead of a half-day investigation.
Latency budget
The rep tile is instant, period close is minutes.
The live earnings tile is recomputed on every deal change and renders inside two hundred milliseconds. Statement generation for a full tenant runs in minutes, not hours. Nothing in the comp flow ever feels like it is waiting on a nightly batch, because nothing is a nightly batch. The month-end "we are rebuilding statements, do not touch anything" window shrinks from days to the time it takes to pour coffee.
Plan versioning
Mid-year plan changes without a rewrite.
A plan is a versioned object. A mid-year change creates a new version with an effective date. Deals closed before the effective date compute on the old version. Deals closed after compute on the new version. The engine handles the splice. Nobody has to rewrite the quarter or exclude the first six deals of September from the new rate card.
Commission feature maturity, an honest look
Demos that photograph well versus features that survive quarter-end.
Every comp vendor demo includes a clean statement screen and a slider that moves attainment from 80 to 160 percent. Fewer demos show what happens when a rep splits two deals, one of which refunds, while on a recoverable draw during a mid-year plan change. The honest grading of commission features is a maturity curve. Here is how the common claims hold up on the way from the keynote to a production pay cycle.
Tiered rates
Mature when the tier logic is visible.
A plan with four tiers is a table. A plan with four tiers plus a preview panel that shows the rep exactly what the next deal would earn is actually mature. Strkr ships the preview. Several competitor products ship the tiers and leave the rep to guess the marginal rate at the next threshold. A plan a rep cannot simulate is a plan they will dispute, and disputed plans fail the one job a comp system has.
Accelerators
Mature when retroactive math is right.
The hard part is retroactive accelerators: when a rep crosses 100 percent of quota, every dollar earned before that point also accelerates. The arithmetic is simple on paper and famously wrong in spreadsheets. Strkr computes the retroactive accelerator in a single pass and shows the uplift on the statement as a dedicated line. Finance can tie out every dollar.
Clawbacks
Mature when the window and scope are rules, not notes.
A clawback policy that reads "if the customer refunds within 90 days" is a note. A clawback policy that is a rule with a window, a scope, a formula, and an evidence trail is a system. Strkr ships the rule shape. Clawbacks fire on refunds, cancellations, and churn-under-contract events automatically, with the negative statement line pre-labeled with the triggering event.
Splits
Mature when the UI is the plan.
Splits typed into a comment field are a disaster. Splits selected from a per-deal picker that validates the percentages sum to 100 and writes a credit line per rep is the production shape. Strkr ships the picker. Several competitors require the sales ops lead to key splits into a spreadsheet after the deal closes, which guarantees the splits are wrong by the end of the quarter.
Draws
Mature when the recovery ledger is live.
A draw tracked on a spreadsheet is a liability. A draw tracked as a ledger inside the comp system with running balance, recovery rate, and projected recovery date is a product. Strkr ships the ledger. Reps on draw can see exactly where they stand without opening a ticket with sales ops. Finance can see the aggregate outstanding draw across the floor as a single number.
Dispute workflow
Mature when the resolution is an auditable record.
A dispute resolved by Slack DM is a landmine. A dispute resolved by an owned record with an attached note, a decision, and a timestamp is defensible. Strkr ships the workflow. The six-month-later "I never agreed to that number" conversation becomes a one-click lookup of the signed statement and the resolved dispute thread.
Statements
Mature when the rep e-signs.
A statement sent as PDF is a document. A statement e-signed by the rep and stored on their profile is a defensible artifact. Strkr ships the e-signature step. The audit, the dispute workflow, and the exit-interview "comp wasn't clear" claim all collapse because the rep acknowledged the number in writing, every month, for every pay period.
GL export
Mature when it ties to the ERP by cost center.
A commission export that lists reps and totals is a report. An export that structures by GL account, cost center, department, and legal entity is a journal entry. Strkr ships the structured export. The month-end reconciliation collapses from a two-day exercise to a controlled file hand-off.
The compensation-vendor trap
How specialists turn commission tracking into a line item.
The sales compensation vendor problem is not the sticker. It is the structure. Per-payee pricing, custom-implementation fees, data-sync lag, duplicate audit trails, and the perpetual two-system reconciliation turn a feature that should ship with the CRM into a six-figure annual spend that touches finance, sales ops, and IT in equal measure. The Strkr pattern is the opposite shape. Commission tracking ships inside the CRM. There is no per-payee commission SKU. There is no six-week implementation. There is no second system to reconcile. The seat price is the comp-system price.
Spiff
A per-payee charge on top of the CRM.
Spiff (now Salesforce Spiff) lists on a per-payee basis, typically $75-$120 per payee per month depending on volume, with implementation professional services on top. A 60-rep sales floor is budgeting $55K-$85K a year in commission tooling before the CRM license. For teams at that scale, native tracking inside the CRM consolidates the spend into the seat price.
CaptivateIQ
Powerful, pricey, long to stand up.
CaptivateIQ is the enterprise reference for complex comp. The capability is excellent. The TCO is six figures annually for a mid-market team, implementation runs 8-16 weeks, and admin-time is a half-FTE role on an ongoing basis. For teams whose plans are not nine levels of override deep, the capability is overbuilt and the price reflects it.
Everstage
Challenger pricing, same architectural shape.
Everstage prices more aggressively than Spiff and ships faster than CaptivateIQ, but it is still a parallel system that pulls from the CRM, computes on its side, and sends statements back. The sync lag, the duplicate audit trail, and the second vendor contract are structural, not pricing issues. The architectural cost does not go away when the price does.
Palette and QuotaPath
SMB-friendly, limited at scale.
Palette and QuotaPath both target the SMB and lower-mid-market segment with cleaner UIs and friendlier pricing than the enterprise crowd. For a 10-rep team on a simple plan, either works. For a 40-rep team with splits, draws, and clawbacks, the limits show up fast and the migration path to a bigger system is painful.
Varicent
Legacy enterprise, built for 1,000+ payees.
Varicent is the vendor you buy when you have 1,000+ payees and six-tier override structures. For teams under 500 reps, the implementation burden and admin footprint are massive overkill. The relevant comparison for mid-market Strkr buyers is not Varicent, which is a different market entirely.
Spreadsheet
The default that burns a sales ops lead.
The honest competitor for most sub-100-rep teams is a quarterly comp spreadsheet maintained by sales ops. The cost is not the spreadsheet license. The cost is the fifteen hours a month a sales ops lead spends reconciling, plus the disputes, plus the finance rework. Native tracking replaces that cost with a sunk feature inside the CRM subscription.
HubSpot and Pipedrive
Weak native comp - they lean on partners.
HubSpot and Pipedrive both have minimal native commission capability and officially recommend an integration partner for comp. The partner integration is a second vendor, a second contract, a second sync layer, and a second seat line. The commission promise inside the CRM is a feature footprint, not just a pricing comparison.
Three Strkr commission patterns in production
What commission tracking looks like on a real sales floor.
The demo video shows a slider and a statement screen. The product in production looks like three specific patterns a revenue team runs every month. These are not aspirational screenshots. These are the three Strkr commission uses that save teams the most time per quarter by a wide margin, as reported by customers who moved off Spiff or CaptivateIQ in the last twelve months.
Live earnings tile
Reps check attainment, not spreadsheets.
Every rep home page shows quota, attainment, next tier threshold, projected commission at close, and earned commission inside the current period. The tile updates on every pipeline change. Reps stop pinging sales ops for status, stop maintaining personal shadow spreadsheets, and stop disputing the end-of-month number because they watched it the whole time. Teams report "where am I at" questions dropping to near zero in the first month after rollout.
Statement signoff loop
Close, generate, review, approve, e-sign, pay.
The engine generates statements on the first of the month. The manager reviews each statement in a single queue, approves or overrides line items with a reason code, and sends. The rep receives, reviews, acknowledges, and e-signs. The signed PDF stores on the profile and feeds the GL export. The end-to-end cycle collapses from a two-week scramble to a two-day flow with every step owned by the right role.
Clawback and dispute flow
A refund fires a clawback, a dispute goes to ops.
A customer refunds inside the clawback window. The engine debits the earlier credit automatically and writes a negative line on the next statement, tagged with the refund event. The rep sees the deduction, disagrees, and clicks Dispute. The dispute lands in the sales ops queue with the deal, the plan rule, and the computed amount in a single view. Ops approves, adjusts, or escalates. The decision writes to the activity log. The entire motion that used to take four Slack threads, three managers, and two days of back-and-forth collapses into a single auditable record.
Native sales commission tracking. No separate Spiff or CaptivateIQ seat.
Starter includes flat and tiered plans, deal-level attribution, splits, and the live rep earnings tile. Pro adds accelerators, SPIFFs, kickers, draws, and clawbacks. Scale adds the dispute workflow, signed statements, and the GL journal export. Enterprise adds plan versioning, multi-entity cost-center support, and the full SOX-leaning audit trail. The seat price is the comp-system price, every tier, every month, no per-payee surcharge. Model your current plan inside Strkr and ship your first signed statement before quarter end.
Does commission tracking cost extra, or is it included in the seat price?
It is included. Commission tracking ships inside Strkr with no per-payee surcharge. Starter includes flat and tiered plans, deal-level attribution, splits, and the live rep earnings tile. Pro adds accelerators, SPIFFs, kickers, draws, and clawbacks. Scale adds the dispute workflow, signed commission statements, and the GL journal export. Enterprise adds plan versioning, multi-entity cost-center support, and the full SOX-leaning audit trail. There is no "commission module" line item, no per-payee charge on top of the seat, and no professional-services engagement required to turn it on.
How does Strkr commission tracking compare to Spiff and CaptivateIQ?
Spiff (now part of Salesforce) and CaptivateIQ both solve the commission problem well as external specialists that sit next to the CRM. Spiff lists on a per-payee basis, typically $75-$120 per payee per month, which puts a 60-rep sales floor at $55K-$85K a year in commission tooling on top of the CRM subscription. CaptivateIQ is the enterprise reference with excellent capability but TCO north of six figures annually for a mid-market team and implementations that run 8-16 weeks. The Strkr pattern is a native commission engine inside the CRM. For teams under 500 reps, that consolidates the spend into the seat price, eliminates the sync layer between the pipeline and the comp tool, and removes the second audit trail. For teams north of 500 reps with nine-level override structures, a dedicated specialist may still be the right call, and Strkr integrates with both via standard APIs.
Can Strkr handle tiered rates, accelerators, splits, and draws?
Yes. The plan editor supports base rates, tiered rates by attainment band, retroactive accelerators above quota, decelerators on strategic discount depth, hard and soft caps, SPIFFs and kickers, deal-level splits (two or more reps on the same deal with validated percentages), manager and team overrides, recoverable and non-recoverable draws with a running recovery ledger, and clawback rules on refund, cancellation, and churn-under-contract events. The plan preview panel shows a worked example at any attainment level you type in, so reps and managers can simulate the next deal before closing it.
How do commission disputes work?
A rep opens their statement, clicks Dispute on a specific line item, writes a note, and attaches any relevant evidence. The dispute lands in the sales ops queue with the deal, the plan rule that applied, and the computed amount in a single view. Sales ops approves, adjusts, or escalates with a reason code. The decision writes to the activity log with actor, timestamp, before, and after. The resolution reflects on the next statement, and the dispute history stores against the rep's profile. The DM-based dispute motion that costs managers two days a quarter disappears because every dispute has an owner, a status, a decision, and an auditable record.
Does the statement generate a signed artifact for finance?
Yes. At the end of each pay period, the engine generates a statement per rep showing deals credited, splits applied, SPIFFs earned, clawbacks taken, draw activity, and net payable. The manager reviews and approves. The rep reviews, acknowledges, and e-signs. The signed PDF stores on the rep profile and in the dispute history as a defensible artifact. Finance has a clean "the rep agreed to this number" record for every pay period, which protects both sides when a question surfaces three months later. The signed statement feeds the GL export, so the number the rep acknowledged, the number on the statement, and the number in the ERP journal are the same number across all three systems.
How does the GL export work?
At period close the engine emits a GL-ready journal entry structured by rep, cost center, department, GL account code, and legal entity. The totals tie to the signed statements to the penny. Export as CSV, or push into the accounting system via the integration layer. The ERP-reconciliation step collapses from a week of hand-reconciling across two systems to a controlled file hand-off from sales ops to finance. For multi-entity companies, the export respects the legal-entity split so the right commissions book to the right books of record, and no cross-entity cleanup entries are needed at quarter close.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
We use cookies.
Essential cookies keep the site working. If you accept, we also enable Google Analytics
so we can see which pages help and which don't. Reject to opt out entirely. Details in our
Privacy Policy.
