Residual income is the reason an ISO is a business rather than a job. Every merchant you place keeps paying every month, and a book of them is an asset. Yet most owners we talk to could not say, to the pound, what a given merchant earned them last month or how much of it went to the agent who sold it. The money arrives in a file from the acquirer, gets reconciled in a spreadsheet, and somewhere in between some of it leaks.
This guide covers how the money reaches you, why the spreadsheet loses some of it, and what month-end looks like when it runs on one system — for the ISO doing the paying and the acquirer doing the sending.
Where the money comes from
When a merchant takes a card payment, the fee they pay is shared out before any of it reaches you. Part goes to the card issuer, part to the card scheme, and what is left is the acquirer’s margin — the only part anybody negotiates, and the part your residual comes out of.
How much of that margin is yours depends on your agreement with the acquirer. Some agreements give you a buy rate and let you keep everything you price above it; others pay you a share of the margin on each merchant. Fixed charges — terminal rental, compliance fees, monthly minimums — usually follow their own rules, and different acquirers treat them differently. The upshot is that every merchant on your book earns you a slightly different amount each month, and the only place that amount is written down is the acquirer’s file.
The file, and the spreadsheet after it
Each month each acquirer sends a report: every merchant ID on your book, its turnover, the fees charged, and your share. Elavon, Worldpay, AIB Merchant Services, Cardstream and Clover each send theirs in their own layout — different columns, different names for the same thing, some as multi-tab spreadsheets, some as flat files. They all arrive at once.
Then the real month-end starts. Most ISOs do not sell everything themselves: agents, introducers and sub-ISOs bring merchants in, and each has a deal. So every merchant in every file has to be matched to the partner who placed it, that partner’s terms applied, the result summed, a statement produced, and the money paid — usually by the twentieth. For four hundred merchants across five acquirers and a dozen partners on different terms, that is a spreadsheet only one person understands, and a week of that person’s month.
Why it leaks
The spreadsheet is not wrong in any single cell. It leaks in the gaps between cells.
A merchant appears in an acquirer’s file with nobody against it, and is either quietly kept or quietly unpaid. A merchant who closed in March is still on April’s payaway, so a partner is being paid out of the ISO’s own pocket. An acquirer changes something — a cost, a fee, a repricing — and the margin on a merchant drops without anyone noticing because the total still looks plausible. Fixed charges get shared on the wrong terms because the sheet has one column for “split”. Adjustments and clawbacks in the file never make it to the partner’s statement, so the ISO carries them alone. And whether a partner is VAT-registered changes what their statement should say, which a sheet that treats everyone the same gets wrong for half of them.
Each of these is small per merchant. Across a book they are the difference between the residual line you think you have and the one you actually have — and, just as damaging, they are the difference between partners who trust their statements and partners who ring every month.
What month-end looks like on one system
On the Commission Reporting module, month-end is a sequence of screens rather than a spreadsheet.
The partner register holds every agent, introducer and sub-ISO with their terms — processing and fixed charges separately, VAT status recorded — and every merchant ID is assigned to the partner who placed it. Assignment happens once, when the merchant boards, not every month.
The residual files come in as they are. Each acquirer’s file is imported in its own layout — Elavon, Worldpay, AIB, Cardstream and Clover are read directly — and the platform matches every line to the merchant record it already holds. Nothing is retyped.
The exceptions are shown, not found. Merchants in a file with no partner assigned, merchants being paid away after they have closed, margins that moved against last month, adjustments that need passing on: each is a list on screen for someone to look at, rather than a thing to notice by luck in row 340.
The statements go out branded. Each partner gets a statement in your livery showing what they earned and on which merchants, produced from the same figures the payaway was calculated from, so the number on the statement is the number in the bank.
For a typical ISO that is around 12.5 hours a month and £3,750 a year back — and, more to the point, a residual figure the owner can trust and partners who stop ringing.
Why acquirers care
The acquirer sending the file has an interest in what happens to it next.
A channel whose residuals run through a register is a channel whose partners are paid correctly, whose disputes are rare and whose records exist when a question comes — from a partner, from an auditor, from the acquirer’s own compliance team. When an acquirer’s ISOs run on the platform, the residual data they send lands on the same merchant record that holds the quote, the proposal and the boarding application, so the acquirer’s view of its channel is not a quarterly review and a spreadsheet but a live picture of what is on its book and how it got there.
That is why the platform is worth showing to an acquirer as well as to an ISO: it is one audited system for the channel, and the residual file is one of the things it audits.
Where to start
If quoting is the side of the business you are wrestling with first, how a merchant statement gets read in three minutes is the companion to this piece. For month-end, the Commission Reporting calculator will put your own hours on it.
Or see it directly: start the 30-day trial, load the demo data, and open the payaway screens with a full month already in them. Nothing to install, no card.