Blog

Are ISO Agents Being Paid Correctly? Residual Calculation Audit Framework

Most ISO agents can’t verify if their monthly residual checks match what their contracts actually promise. Industry audits reveal discrepancies in 9 out of 10 portfolios examined. Here are five warning signs you’re being underpaid, and the step-by-step framework to prove it.

Residual income is the whole point of building a merchant portfolio.

But the monthly deposit hitting your bank account is not proof that the math is right.

For most ISO agents, the gap between what was promised and what was paid goes undetected, not because agents are careless, but because residual reporting systems are rarely designed for transparency.

Most ISO Agents Cannot Verify Their Own Pay

The standard residual portal shows what was paid, not what was owed.

That distinction matters more than most agents realize.

Without the ability to independently reconstruct the calculation, starting from merchant processing volume, subtracting Schedule A costs, and applying the agreed split, there is no way to confirm accuracy.

Trust fills the gap, and trust is not an audit.

This problem is industry wide.

At RedFynn Technologies, we have reviewed hundreds of agent portfolios over our extensive operating history, and we consistently find discrepancies in 9 out of 10 portfolios examined, ranging from padded interchange to basis points overcharged at the merchant level.

When agents cannot recalculate their own compensation from first principles, underpayment has a structural advantage.

What Paid Correctly Actually Means

Being paid correctly goes beyond the split percentage on a Schedule A.

It means the net residual deposited each month reflects the actual economics agreed to at sign up.

Split Percentage vs. Net Residual Reality

A headline split of 70% sounds strong until you examine the base it is applied to.

ISOs typically calculate an agent’s share against net margin, the revenue remaining after deducting network charges, per item fees, BIN sponsorship costs, and equipment related expenses.

By the time those deductions are applied, the profit pool can be significantly smaller than gross processing volume suggests.

Current Schedule A deals commonly show splits between 70 and 80% for pure lifetime residual structures, but agreements bundling upfront bonuses or free equipment typically land in the 50 to 60% range, reflecting that the economics are always balanced somewhere.

How Hidden Costs Quietly Erode Your Share

Beyond the known Schedule A deductions, a second layer of costs operates below the surface.

PCI non compliance fees, statement fees, batch fees, monthly minimum fees, annual or regulatory fees, and equipment lease or early termination fees all reduce the net margin before your percentage is ever applied.

Processors or acquirers can introduce new fees or adjust existing ones without direct notice to you, compressing residuals on merchants whose processing behavior has not changed at all.

5 Red Flags You Are Being Underpaid

Certain patterns consistently appear across legal cases, industry forums, and portfolio audits when agents are receiving less than their contract entitles them to.

Volume Grows, Residuals Do Not

This is the most common signal.

A portfolio adding new merchants or growing existing account volumes should produce proportionally growing residuals.

When that relationship breaks down, when a book grows but the monthly deposit stays flat or declines, it typically means the ISO is applying volume based throttles, adjusting splits tied to production thresholds, or reducing margins on existing accounts without disclosure.

Unexplained Deductions and New Fees

Residual reports that include deduction line items referencing network charges, PCI compliance, chargeback reserves, or platform fees without merchant level detail are a warning sign.

Processors can introduce new cost categories that flow directly into the deduction pool, shrinking the net margin from which your split is calculated.

When you cannot trace a deduction to a specific merchant or a specific contractual basis, the burden of proof effectively shifts, and most agents lack the documentation to push back.

Residuals Stop or Drop After a Status Change

Sharp residual drops following any kind of status change, including termination, ownership transfer, or contract renewal, warrant close scrutiny.

Agreements can quietly cut off residuals after departure or breach, even on accounts you originally sourced.

Chargebacks or Risk Reserves Withheld Without Explanation

Broad risk fees or chargeback reserve withholdings applied against commissions without clear written justification are a red flag.

You should be able to trace every reserve deduction to a specific merchant event and a specific contractual clause.

Override Splits Taken Without Documented Disclosure

An upline taking a slice of residuals without clearly documenting the percentage and the pool it is drawn from is a structural transparency failure.

Undisclosed override arrangements are among the harder discrepancies to detect without merchant level reporting.

The Residual Audit Framework: 5 Steps

Auditing residuals does not require a CPA.

It requires a repeatable process applied consistently across your merchant book.

Step 1: Map Your Schedule A Economics

Start with the contract.

List every cost component in the Schedule A: basis points over interchange, per item fees, monthly fees, and any special deductions tied to pricing programs like cash discount or surcharge.

This becomes the benchmark against which every payout is tested.

Residual auditing is a reconciliation exercise, comparing what the processor’s payout report shows against what the Schedule A contract dictates, line by line and merchant by merchant.

Step 2: Sample Your Merchant Portfolio

Spot checking two or three merchants is not enough for a book of any real size.

Pull a cross section: new accounts, long tenured accounts, different verticals, and merchants across different volume tiers.

Collect three to six months of merchant statements alongside the corresponding residual reports.

Merchant level detail is the only way discrepancies become visible at scale, since aggregate reporting hides the individual account anomalies where errors tend to live.

Step 3: Calculate the True Profit Spread

For each sampled merchant, calculate the total processing fees collected in a given month.

Subtract the applicable Schedule A costs to arrive at the true net profit for that account.

Your residual for that merchant should equal your split percentage applied to that net figure, not to gross volume, and not to some other baseline.

Common sources of discrepancy at this step include revenue share base differences, incorrect rate tier application, and expense allocation that does not match the original contract terms.

Step 4: Document Discrepancies, Not Feelings

A structured spreadsheet with one row per merchant, tracking volume, merchant fees collected, Schedule A cost, calculated net profit, expected residual, and actual residual paid, transforms a vague concern into a concrete evidence base.

Without this documentation, any conversation with your ISO relies on memory instead of data.

With it, you can cite specific merchants and specific months.

That distinction separates a complaint from a legitimate dispute, and if the matter escalates to a payments attorney, documented discrepancies are the foundation of any claim.

Step 5: Review and Repeat Monthly

A single audit is a snapshot.

Residual erosion often happens gradually, a new fee category added here, a rate tier adjustment there.

Running the same reconciliation process each month creates a running record that makes incremental changes visible before they compound into significant underpayment.

Agents who audit consistently are also better positioned to catch errors early, when correction is straightforward rather than contentious.

Contract Clauses That Control Your Pay

The contract determines what correct means.

Many of the most damaging underpayment situations are technically permitted under vague or one sided agreement language that agents signed without fully understanding.

Residual Definition and Reporting Rights

ISO agreements should explicitly define residuals, whether the split is calculated on gross revenue share, net after all ISO costs, or some intermediate figure, and should grant you explicit audit rights.

This means documented access to merchant level performance data, written notification before fee adjustments take effect, and the ability to verify calculations within a defined window.

Agreements that lack these protections leave you entirely dependent on the ISO’s self reporting.

Termination, Clawbacks, and Survival Provisions

ISO contracts frequently include broad termination provisions that allow residual payments to cease across a wide range of triggers, including termination without cause.

Clawback clauses can require you to return previously paid residuals if a merchant churns, generates excessive chargebacks, or closes early.

If you are building a long term income stream, specifically negotiate survivorship provisions ensuring that residuals continue post termination, post death, or after contract expiration.

Limitation of liability clauses that cap an ISO’s exposure to a few months of prior residuals can also severely constrain your ability to recover meaningful damages if underpayment is proven.

When Disputes Go Legal

Residual disputes are among the most complex and contentious issues in electronic payments.

They escalate to litigation more often than most agents expect, and the outcomes can be significant.

A U.S. District Court for the Northern District of Ohio ordered Electronic Merchant Systems to pay over $5.4 million in breach of contract damages to a sales agent in a residual and contract interpretation dispute, a result that shows these claims are real, enforceable, and financially material.

The stakes are high enough that payment specialist attorneys consistently advise agents to have ISO agreements reviewed before signing, not after a dispute has already developed.

Auditable Residuals Are a Partner Right, Not a Perk

Transparency in residual reporting is a fundamental expectation of any legitimate ISO partnership.

An agent who cannot verify their own pay cannot protect their own business.

The practical standard is clear: you should have access to merchant level detail, explicit audit rights written into your agreement, and a partner that proactively reconciles calculations rather than waiting for complaints.

That standard exists, and some programs meet it.

The first step is knowing what to look for, then running the numbers to find out where you stand.

At RedFynn Technologies, we built proactive monthly residual audits into our partner program because we believe payment accuracy is a baseline obligation, not an optional service.

Our dedicated back office team reconciles agent compensation against Schedule A terms every month, so you never have to wonder whether you are being paid correctly.

If you want to work with a partner built around fully auditable residual reports and transparent compensation, reach out to RedFynn Technologies today.

Learn more athttps://redfynn.com/