Am I Being Paid My Full Residuals? How to Tell

The Uncomfortable Question Every Agent Asks Eventually

You boarded merchants all quarter. Volume looks healthy. The deposit hits your account and it feels... light. Not dramatically wrong. Just slightly off, month after month. You tell yourself processors are complicated. You move on.

Six months later you reconcile properly and find $4,200 in recoverable variance you never knew existed. The question "Am I being paid my full residuals?" has a factual answer. It is not a vibe. It is math compared to your Schedule A.

Sign One: Your Deposit Grows Slower Than Your Portfolio

Track two numbers monthly:

1. Active MID count (merchants producing residuals)
2. Net residual deposit (after known adjustments)

If MID count grows 15% over six months but residuals grow 4%, something is diluting pay. Causes include:

• New merchants on lower tier rates while attrition removes high-tier legacy accounts
• Systematic underpayment on new boards not visible in summary totals
• Increased house retain after an ISO contract renegotiation you did not notice

Portfolio growth and residual growth should correlate roughly, not perfectly, but persistent divergence warrants audit.

Sign Two: You Have Never Reconciled Against Schedule A

If your verification method is "the deposit arrived and the ISO is reputable," you do not yet know whether you are paid in full. Reputation and accuracy are different variables.

Full verification means: for each material line item, expected pay = Schedule A rate applied to the correct base, compared to reported pay. Unexplained negative variance means you were not paid in full on that line.

If you have not done this, start with how to read your residual report line by line.

Sign Three: Implied Rev-Share Rates Do Not Match Contract

Pick ten random merchants. For each interchange line, divide agent residual by net income. The result should match your Schedule A rate (after accounting for house retains).

Example: Schedule A says 50% of net interchange. Net is $400. Paid is $280. Implied rate: 70% of expected, not 50%. You are short $120 on that line.

If seven of ten merchants show the same implied rate gap on PIN debit, you likely have a systematic issue, not random noise. See five common ways processors underpay agents.

Sign Four: Fee Income Underperforms Interchange

Many agents earn strong interchange rev-share but leave fee income on the table. Schedule A might grant 80% on monthly fees while the report pays 50% or zero.

Quick test: sum all statement fee net income across the portfolio. Multiply by your Schedule A fee rate. Compare to sum of fee residuals paid. A 20-point gap on $6,000 monthly fee income is $1,200 per month.

Fee lines are small per merchant but aggregate fast. Agents who only audit interchange miss this bucket.

Sign Five: Post-Migration Deposits Changed Shape

Platform migrations, portfolio sales, and processor acquisitions often reset rate tables to defaults. Deposits may not drop immediately because legacy merchants still pay correctly while new line item codes mis-map.

If your deposit composition changed (more interchange, less fees, or new adjustment lines) after a migration event, audit within 60 days. Drift compounds silently otherwise.

Sign Six: You Cannot Explain a Specific Merchant

Pick your highest-volume merchant. Manually reconcile every line item for the latest month. If you cannot reproduce the processor's payout from Schedule A math, you lack visibility into your largest account.

High-volume merchants drive portfolio economics. If math fails there, assume it fails elsewhere at smaller scale.

How to Verify: The Three-Document Method

Gather three documents:

Documents You Need

1. Executed Schedule A (with effective dates and boarding tiers)
2. Detail residual report for the month
3. Your merchant list with boarding dates and status

Merchant-Level Reconciliation Loop

For each merchant above your variance threshold:

1. Map line items to Schedule A categories
2. Confirm net base
3. Apply correct tier rate for boarding date
4. Compute expected residual
5. Compare to paid
6. Log variance with MID, line item, expected, paid, delta

Repeat at portfolio scale manually until you hit fatigue. Then automate.

Our step-by-step audit guide formalizes this workflow.

What "Full Residuals" Does Not Mean

Verification is not about demanding more than contract. It is about receiving exactly what contract specifies. Switzerland neutrality matters here: processors make configuration errors, apply stale rate tables, and mis-map line items without ill intent. Your job is to identify variance and raise it with evidence.

"Full residuals" also does not mean every merchant is profitable. Negative residuals on high-loss accounts happen legitimately. You are verifying calculation correctness, not guaranteeing positive income on every MID.

When to Escalate to Your ISO or Processor

Escalate when you have:

• Documented variance above your materiality threshold (many agents use $25+ per line or $100+ per merchant)
• Systematic pattern across multiple MIDs
• Schedule A citation with effective date
• Expected versus paid calculation shown clearly

One-off $3 variances may not justify a ticket. $3 times 400 merchants is $1,200 monthly.

Processors respond to pattern evidence. Lead with aggregated impact, then attach merchant-level samples.

Monthly Verification Habit

Agents who catch underpayment early share one habit: monthly reconciliation, not annual panic. Monthly catches drift before it spans quarters. It also builds a paper trail if relationship dynamics change.

Set a calendar block after each residual cycle:

1. Download detail report
2. Run reconciliation
3. Review top exceptions
4. File tickets for systematic issues
5. Confirm prior credits posted

Ten minutes of summary review is not enough. Thirty to sixty minutes with tooling scales better than eight hours in spreadsheets.

Quick Self-Test Before You Call Your ISO

Answer these five questions honestly:

1. Can you locate your executed Schedule A in under two minutes?
2. Can you manually reconcile your largest merchant against it?
3. Do you know your portfolio's average implied interchange rate this month?
4. Did your last deposit change shape after a processor migration?
5. Have you ever received a credit labeled "rate correction"?

If you answered no to three or more, assume you have unverified income until an audit proves otherwise. That is not an insult. It is the default state for agents who sell well and reconcile rarely.

What Recovery Looks Like In Practice

When agents document systematic variance, outcomes typically include:

• Forward correction: rate engine fixed for future cycles
• Retroactive credit: lump sum or multi-month true-up for defined lookback
• Merchant-level restatement: individual MID corrections when issue was mapping, not rate table

Credits appear as adjustment lines on future reports. Track them against your exception log. Processors sometimes fix forward without retro payment unless you ask with evidence.

Average recovery timelines range from one to three residual cycles for configuration fixes, longer when sponsor bank approval is required at ISO level.

Document every conversation. Processors rotate account managers; your ticket history becomes the institutional memory that prevents re-litigation of the same pattern six months later.

Get a Definitive Answer on Your Next Deposit

You should not wonder whether you are paid in full. You should know.

Residual Genius reconciles your report against your Schedule A and shows every line where paid diverges from expected. Upload a CSV or Excel export in a supported processor layout. First audit free.

Start your free audit and see exactly what your last deposit should have been.