How the money actually moves in a payments ISO: residuals, splits, overrides and deductions, explained with real numbers. Written from the month-end work we do with ISOs in the United States and Canada.
The five files in a Paysafe residual package, which one holds the profit, which one holds the rates, why the merchant detail file has thirty rows per merchant, and the checks that keep a Paysafe month honest.
Read →Plain definitions of the words used in payments residuals, from Schedule A and buy rate to override, upline, attrition and buyout, with the arithmetic where it matters and links to the guide that goes deeper.
Read →How an ISO with residuals from two or more processors builds one reliable month from files that disagree on layout, profit, timing and merchant identity, why a processor's own portal cannot do it, and the checks that catch the errors.
Read →How to model a change to agent splits, tiers or overrides against real past months, what to look for in the result, and how to roll it out without a dispute.
Read →How residuals work for Canadian ISOs and agents, which processors they come from, what Interac and the interchange rules do to the numbers, and how to run a book that earns in both Canadian and US dollars.
Read →The six signals in a monthly residual report that show a merchant is leaving before the residual disappears, a simple rule for flagging them, and what to do in the month you still have.
Read →What the residual data shows about where an ISO's profit actually comes from, why the processor's file makes the count wrong, and how to measure concentration in your own portfolio in an hour.
Read →What breaks in an ISO's back office at ten, thirty and a hundred agents, why month-end grows faster than the book does, and how to add agents and processors without adding a person to run residuals.
Read →Why comparing residual reports from two processors is harder than it looks, the four definitions of profit that make the numbers lie, and a method for finding out which processor actually makes your office money.
Read →What a payments ISO should put on an agent's residual statement, what to leave off, how a portal changes the monthly conversation, and how to roll it out without starting arguments.
Read →The five steps from a merchant's processing volume to what the agent, the manager and the ISO each keep, with every number shown.
Read →A column-by-column walk through the residual workbooks First Data sends ISOs, where the profit number is, how the Clover rental and app reports differ, and the traps that cause wrong payouts.
Read →The six ways payments ISOs pay their agents, from flat splits and tiers to bonuses, sub-agent overrides and shared merchants, with a worked number for each and where each one goes wrong.
Read →When a residual spreadsheet is still fine, the signs an ISO has outgrown it, the errors spreadsheets hide, and how to move to software without risking a payday.
Read →Free calculator for what a buyer would pay for a book of residuals, from published multiples by attrition band, and what the book pays if kept instead.
Open →Free calculator for what the agent, the upline and the house each keep on one merchant, on any of the three common split bases.
Open →Sales commission platforms such as CaptivateIQ and QuotaPath are built for quotas, deals and closed-won revenue from a CRM. Payments residuals are a recurring stream per merchant that arrives as processor reports. This page explains where the two kinds of software part ways, and what an ISO actually needs.
Read →Twill is an AI-led operating system for the whole ISO, priced as a percentage of processing volume. SplitRun does residuals and portfolio analytics only, at a flat public price. Which fits depends on whether you want a platform or a fix for month-end.
Read →Fullcast and SplitRun are the two residual-focused tools an ISO is likely to shortlist. Both replace the month-end spreadsheet. SplitRun is the simpler, more modern one, with public pricing, a portal for every agent, and analytics that tell you what the residuals mean.
Read →ISOhub is a merchant services CRM with residuals as one module. SplitRun is modern, residual-only software that gets month-end right without a migration, with public pricing, a portal for every agent, and analytics that show what the book is doing.
Read →The software payments ISOs actually use for residuals, from full CRM platforms to residual-only tools to Excel, with what each is best for and whether its pricing is public.
Read →NMI Merchant Central, formerly IRIS CRM, is a full payments CRM. An honest look at when it is the right choice, and when an ISO that only needs residuals done properly is better served by SplitRun.
Read →Already using SplitRun? The Help center covers the product step by step, and What's new lists each month's updates.