Agent commission transparency: what to show your agents, and what not to
Agents trust their residuals when they can see, for every merchant they own, what the merchant produced and what they were paid, on the same day each month, with last month beside it. Show each agent their own merchants, amounts, adjustments and history. Do not show other agents' numbers, the house margin, or another person's override. Publish only after the month is checked and locked, so a number an agent has seen never changes without explanation.
An agent's residual is their income, and in most ISOs they receive it as a single number, or a PDF they cannot question without phoning the owner. Everything they cannot see, they have to take on trust. Most do, until the first month a number falls and nobody can quickly say why.
Transparency is not showing everyone everything. It is deciding what each person is entitled to see and then showing it the same way every month. This guide covers what belongs on an agent's statement, what should stay off it, and how to introduce it.
Why it is worth the effort
- Fewer disputes, and shorter ones. Most residual disputes are questions, not accusations: why is this lower, where did that merchant go. If the statement answers them, the call never happens.
- Agents stay. A rep choosing between two offices compares splits, and also whether they believe they will actually be paid correctly. A clear statement is evidence.
- Agents catch your errors. Nobody knows a portfolio better than the person who sold it. An agent who can see their merchant list will tell you about a missing account within days.
- Attrition gets noticed sooner. An agent who sees a merchant's residual drop by half has a reason to call that merchant this week.
- The owner gets time back. Every explanation delivered by a statement is one not delivered by you.
What every agent statement should show
| On the statement | Why it matters |
|---|---|
| The period, and the date it was published | Removes any doubt about which month this is |
| Every merchant the agent is paid on, by name and merchant ID | Lets the agent spot a missing or wrongly assigned account |
| What each merchant produced that month | The starting point of their pay |
| What the agent earned on each merchant | The line they actually care about |
| Income type for each line: processing, equipment, software | Explains why two similar merchants pay differently |
| Shared merchants, marked as shared, with the agent's share | Avoids "why is this one half what I expected" |
| Override earnings, listed separately from their own production | Keeps a manager's two kinds of income distinct |
| Adjustments and deductions, each with a reason | An unexplained minus sign is where trust goes |
| The total, and last month's total beside it | The first thing they look for |
Two further things turn a statement into something an agent relies on:
- History. Every past month, available in the same place, so the agent can answer their own trend questions.
- Merchant status. Closed accounts and merchants that have stopped processing, flagged, so a fall in pay has a visible cause.
What to leave off
Openness about an agent's own numbers does not require openness about anyone else's.
| Keep off an agent's view | Reason |
|---|---|
| Other agents' merchants and earnings | It is their income, not a team statistic |
| The house margin | Your business, and it invites renegotiation every month |
| What an upline earns on them | Overrides are usually funded by the house and are the upline's private income |
| Your buy rates and processor agreement | Commercial terms between you and the processor |
| Merchants they are not paid on | Including accounts they sold and later transferred, unless a tail applies |
| Work in progress | A number that later changes does more harm than a number that arrives two days later |
Should agents see their commission rate?
Offices disagree on this, and both positions are reasonable. Some print the split on every line so the arithmetic can be checked by hand. Others show what each merchant produced and what the agent was paid, and leave the rate in the agent's agreement, which the agent already holds. The second approach is common where different agents have different deals and statements are likely to be passed around.
Whichever you choose, do it on purpose and apply it to everyone. What matters is that the agent can trace their pay to their merchants, and that the amounts agree with the agreement they signed.
Statement or portal?
A PDF statement is the minimum. It is a record, it can be filed, and it works for agents who want nothing more than a document each month.
An agent portal is a login where the agent sees their own statements, their merchants and their history. It is better when agents have more than a handful of merchants, because they can look things up without asking, and because there is one current version instead of attachments in an inbox.
Most offices end up with both: the portal as the source, and a PDF emailed when the month is published.
The practical requirements are the same either way:
- An agent must only ever be able to reach their own data. This has to be enforced by the system, not by who you remember to send which file.
- Agents see a month only after it has been checked and published.
- A published month does not change silently. If a correction is needed, it appears as a correction, with a reason.
Publish on a schedule, and lock what you publish
Much of what agents experience as secrecy is really lateness and revision.
- Pick a date and keep it. "Statements are published by the 25th" is worth more than any amount of detail delivered unpredictably. If a processor's file arrives late, say so on the day, rather than going quiet.
- Check before publishing, not after. Tie totals back to the processor's reports, look for merchants with no agent, and compare each agent's total with last month. A guide to the checks is in How to calculate ISO residuals.
- Lock the month once it is published. Later changes to rates or assignments should affect future months, not rewrite past ones.
- Handle corrections in the open. If you overpaid or underpaid, show it as a dated adjustment in a later month, with the reason. Quietly changing a past statement is the fastest way to lose the trust you were building.
How to roll it out
- Get the numbers right first. Run two or three months internally and reconcile them to what you actually paid. Transparency built on wrong numbers is worse than none.
- Decide the policy. What agents see, what they do not, and whether rates are shown. Write it down.
- Start with one or two agents you trust. Ask them what is confusing. Their questions are the ones everyone else will have.
- Tell everyone before it arrives. A short note: what they will receive, when, what it includes, and who to ask.
- Expect a burst of questions in the first month. Agents are seeing detail for the first time and will find things: a merchant they thought was theirs, a closed account nobody mentioned. Most of these are old issues surfacing, not new errors. Fix them, and the second month is quiet.
- Keep the schedule. Consistency is what turns a statement into trust.
Frequently asked questions
What should an agent residual statement include? The period and publish date, every merchant the agent is paid on with what it produced and what the agent earned, the income type of each line, shared merchants and the agent's share, overrides listed separately, adjustments with reasons, and the total beside last month's.
Should ISO agents see their commission rates on the statement? It is a policy choice. Some offices print the rate on each line, others show the amounts and leave the rate in the signed agreement. Both work, provided the policy is applied to every agent and the amounts agree with the agreement.
What should agents not be able to see? Other agents' merchants and earnings, the house margin, what an upline earns on them, the ISO's buy rates and processor terms, and any month that has not been checked and published.
Does an agent portal reduce residual disputes? In practice it shortens them. Most disputes begin as a question about a missing merchant or a lower total, and an agent who can see their merchant list, each merchant's amount and last month's figures can usually answer it without a call.
When should residual statements be published? On a fixed date each month, after the processor files have arrived and the month has been checked. A reliable date matters more than an early one.
How does SplitRun handle this? In SplitRun, each agent gets a statement and a portal login that shows only their own merchants and earnings, for months the office has locked and published. Commission rates are not shown to agents. Statements can be emailed on publish, and later corrections appear as corrections. See Lock and publish, Users and roles and the sample agent report.
See what your agents would receive each month.
View the sample report