Residual software vs sales commission software: why CaptivateIQ and QuotaPath do not fit an ISO
Sales commission software pays a rep once when a deal closes, on data pulled from a CRM, measured against a quota. Payments residuals pay an agent every month for as long as a merchant keeps processing, on data that arrives as processor report files with no CRM involved, split by income type, shared between agents, and subject to overrides and deductions. The general tools can be bent to it with custom imports and formulas, but the processor files, the multi-row merchants, the per-merchant history and the agent portal are things they were not built for. Residual software such as SplitRun starts from the processor's file, which is where the work actually is.
Search for commission software and you find a large, mature category: CaptivateIQ, QuotaPath, Spiff, Xactly and a dozen more. They are good products, used by thousands of sales teams. An ISO owner looking at them for residuals will find a demo that looks close and a setup that never quite works. This page explains why, without pretending the general tools are bad. They are built for a different job.
We make SplitRun, which is residual software, so read this knowing which side we are on. Facts about CaptivateIQ and QuotaPath were taken from their own websites on September 28, 2026, and linked so you can check them.
Two different jobs
| Sales commission software | Residual software | |
|---|---|---|
| What is paid | A commission on a deal, once, when it closes | A share of a merchant's profit, every month, for as long as the merchant processes |
| Where the data comes from | The CRM: opportunities, closed-won amounts, quotas | Processor report files: one per processor per month, each with its own layout |
| The unit of work | A deal and a rep | A merchant, on a processor, in a month, with an agent |
| What varies the payout | Attainment against quota, accelerators, SPIFs | The base (before or after the processor's split), income type, shared merchants, overrides, deductions, rates that change on a date |
| Who else is paid on it | Sometimes a manager on team attainment | An upline on an override, a referral partner on a share, the house on the rest |
| What the rep sees | Their deals, their attainment, their payout | Their merchants, what each produced this month and last, and their statement |
| What history is for | Audit and disputes | Attrition, concentration, processor profitability, the value of the book |
| Examples | CaptivateIQ, QuotaPath, Spiff, Xactly | SplitRun, Fullcast, the residuals module inside an ISO CRM |
What the general tools are actually built for
CaptivateIQ describes itself as a leader in sales performance management, with incentive compensation management, sales and capacity planning, quota setting, territory management, bonuses and MBOs, and a calculation engine it calls SmartGrid. It is aimed at compensation professionals, finance, revenue operations and sales management in mid-market and enterprise companies. Pricing is a custom quote, described as per-seat with a one-time setup fee. See CaptivateIQ.
QuotaPath describes itself as sales commission tracking software with an AI revenue strategist: build compensation plans, automate commissions, pay them out, plus comp plan design, benchmarking, capacity and territory planning. It connects to CRMs, ERPs and accounting systems, and to Rippling for payroll. Its published plans are $35 or $50 per user per month plus a $525 or $800 monthly platform fee covering the first five users, billed annually. See QuotaPath pricing.
Neither site mentions payments, residuals, ISOs or merchant services. That is not a criticism. It is the point. Their whole design starts from a CRM record of a deal, and an ISO's month starts from a spreadsheet the processor emailed.
Where the fit breaks
The input is a file, not a CRM
A residual month begins when Fiserv, Global Payments, TSYS or Elavon sends a workbook. One has a tab per month with headers on the second row. One has several rows per merchant. One reports profit before the processor's split and one after. None of that lives in a CRM, and the general tools assume it does. You can import a CSV into most of them, but every month someone has to turn three processor files into the flat shape the tool wants, and that is the work you were trying to get rid of. What that work looks like is in How to read a First Data residual report.
The payout recurs, and it is per merchant
A commission tool thinks in deals: a deal closes, a rule fires, a payout is created. A residual is not an event. It is a stream, per merchant, that continues until the merchant leaves, and every month the amount is different. The question an agent asks is not "did I get paid on this deal" but "why is this merchant lower than last month". Answering that needs every merchant's history side by side, which is the natural shape of residual software and an awkward one for deal-based tools.
The rules are ISO rules
Splits by income type. A base that might be Total Profit, the ISO's share, or what remains after deductions. Shared merchants where two agents split one account. Overrides to an upline as a percentage of commission or as points on the base. Deductions that come before or after the split. Rates that change on a date and must not touch earlier months. Each of these can be built as a custom formula in a general tool. All of them together, across several processors, is a system someone has to maintain, and it lives in one person's head. The structures are in ISO commission split structures explained.
The agent's view is a merchant list, not a leaderboard
Sales commission tools show reps their attainment against quota because that is what motivates a quota-carrying rep. An ISO agent has no quota. They have a book, and what they want to see is their merchants, what each produced, what they earned on each, and last month beside it. They should not see commission rates or other agents' numbers. That is a different screen, built around a different question. See Agent commission transparency.
The history means something else
In a sales tool, history is for audit. In an ISO, history is the business: which merchants are fading, how concentrated the book is, which processor makes money, and what the book would fetch from a buyer. None of those questions can be asked of deal data. They need every merchant, every processor, every month, in one place. See Merchant attrition warning signs and the merchant portfolio valuation calculator.
When a general commission tool is the right call
- You pay one-time bonuses on activations or boarding, not residuals, and your data is already in a CRM.
- You are a large company with a sales compensation team, an existing SPM contract, and an integration budget. Bending an enterprise tool to residuals is possible with enough professional services.
- Residuals are a tiny part of what you pay. If most of the money is quota-based commission and a residual line is a footnote, one tool for everything may be worth the compromise.
For an ISO whose income is residuals, none of these usually apply.
What residual software does instead
SplitRun starts from the processor's file. It reads the reports you already receive, keeps each as its own data source with its own layout and currency, sums the multi-row files per merchant, applies splits, shared merchants, overrides and deductions with effective dates, and produces a statement and a portal login for every agent. On top of the calculation it shows attrition, concentration and processor profitability from the same data. Pricing is flat and public, from $49 a month, on the pricing page. There is no CRM to connect and nothing else in the office changes.
If you want to see how it compares with the other tools built for ISOs rather than for sales teams, start with ISO residual management software compared.
Frequently asked questions
Can I use CaptivateIQ or QuotaPath for merchant services residuals? You can import residual data into them and build custom rules, but they are designed around deals closed in a CRM and paid once. Residuals are a monthly stream per merchant that arrives as processor files with their own layouts, so the import and the rules become a monthly maintenance job rather than a setup.
What is the difference between commission software and residual software? Commission software pays a rep on a deal when it closes, measured against a quota, on CRM data. Residual software pays an agent every month on each merchant's profit, from processor report files, with splits by income type, shared merchants, overrides and deductions, and it keeps the per-merchant history that shows attrition and concentration.
How much does sales commission software cost? It varies widely. QuotaPath publishes plans at $35 or $50 per user per month plus a $525 or $800 monthly platform fee, billed annually. CaptivateIQ quotes per seat with a setup fee and does not publish numbers. SplitRun is $49, $149 or $299 a month plus usage above plan limits, with no per-agent seat fee inside the plan limits.
Does an ISO need a CRM to run residuals? No. Residual calculation works from the processor's reports and the agent agreements. A CRM helps with selling and boarding, and the two can be bought separately.
What should an ISO look for in residual software? It reads your processors' actual files, reproduces payouts you already know are right, carries effective dates on rates and overrides, traces every statement line to the source report, gives agents their own view, locks a month once paid, and shows what the book is doing over time.
Is SplitRun a sales commission tool? No. SplitRun does residual and commission calculation for payments ISOs, agent statements, an agent portal and portfolio analytics. It does not do quotas, territories, deal-based commissions or sales planning.
See what your agents would receive each month.
View the sample report