A Payment Agent's Guide to Reconciling and Recovering Residual Discrepancies

Recovery Starts with Verification, Not Accusation

Payment agents who discover residual discrepancies face a choice in how they respond. The adversarial path, assuming bad faith, escalating aggressively, threatening, damages relationships and often produces worse outcomes than the variance itself. The professional path, verify, document, raise through proper channels, reconcile, protects both the relationship and the revenue.

This guide is the professional path.

Residual Genius is built on a neutral premise: your Schedule A is the source of truth, the processor report is the claim, and reconciliation surfaces differences worth human review. We do not frame variance as proof of wrongdoing. We frame it as a question that contract language and arithmetic can answer. What you do with the answer is your business. How you ask the question determines whether the conversation is productive.

Phase One: Verify

Verification means comparing what you were paid against what your contract says you should have been paid, completely, line by line, merchant by merchant. Not spot-checking your top five accounts. Not glancing at the portfolio total. A full reconciliation for the reporting period.

What Verification Requires

• Your current effective Schedule A with all rate versions and effective dates
• The processor residual report for the period being audited
• A merchant roster with boarding dates aligned to the report
• A reconciliation method that calculates expected residual per line item and compares to actual

What Verification Produces

A list of exceptions: merchants and line items where expected residual differs from actual residual by a material amount. Each exception should include the calculation, net income, rev-share percentage, expected amount, actual amount, variance direction and magnitude.

Exceptions are not accusations. They are arithmetic results that warrant review. Some will be explainable, rounding, timing differences, merchants on legacy rate tables you forgot about. Others will point to configuration differences between your contract and the processor's system that deserve a conversation.

How Residual Genius Handles Verification

Upload your Schedule A and your residual report. The engine reconciles every line item against the correct rate version for each merchant. You receive an exception report grouped by line item type, with merchant penetration and total variance impact. Work that rarely gets finished manually at full portfolio scope runs in minutes.

Our guide on how to check processor payments walks through the verification mindset in more detail.

Phase Two: Document

Documentation transforms arithmetic into evidence. When you raise a variance with your processor representative or ISO operations contact, the quality of your documentation determines whether the conversation moves forward or stalls.

What to Document for Each Material Exception

Merchant identification, MID, DBA name, agent code, boarding date. Unambiguous reference to the account in question.

Reporting period, The exact board month or date range covered by the residual report line.

Line item category, The specific fee or income type showing variance, interchange, PIN debit, monthly fee, gateway, etc.

Contract reference, The Schedule A rate and version that applies to this merchant. Quote the relevant language: "Schedule A v3, effective 2024-01-01, interchange net rev-share: 50%."

Expected calculation, Show the math. (Example: net interchange income $6,200 × 50% rev-share = $3,100 expected.)

Actual amount, What the report shows you were paid on that line item for that merchant in that period.

Variance, The difference, stated clearly. (Example: expected $3,100, actual $2,480, variance -$620.)

Pattern context, If the same variance appears across multiple merchants on the same line item, note the count and total impact from your audit output. (Example phrasing: "Interchange net variance on [N] merchants, total impact -$[X] for [period]." Use your actual reconciled numbers, do not estimate.)

What Not to Document

Do not characterize variance as theft, fraud, or intentional underpayment, especially not when referencing a named processor or ISO. The documentation should state facts: contract rate, expected calculation, actual payment, difference. Let the numbers speak.

Do not fabricate impact estimates or invent case studies. Use the numbers from your reconciliation. If you do not know the total historical impact, say "variance identified for [period]" rather than guessing at multi-year totals.

Do not cc half your organization before you have had a direct conversation with your processor contact. Documentation is for alignment, not ammunition.

Phase Three: Raise Through Proper Channels

Raising a finding is a professional communication, not a dispute. The goal is alignment, ensuring the processor's configuration matches your contract, not winning a fight.

Who to Contact

Start with your direct processor representative or ISO operations contact, the person who manages your agent relationship. They have access to configuration systems, rate tables, and escalation paths that you do not.

If your relationship runs through an ISO hierarchy, raise findings to your ISO first. They may resolve configuration issues internally or escalate to the processor on your behalf.

How to Frame the Conversation

Lead with the contract, not the accusation. Examples of productive framing:

• "Our Schedule A specifies 50% of net interchange. The March report appears to apply rev-share to gross on [N] merchants. Can we review the configuration?"
• "We identified variance on gateway fees for merchants boarded after [date]. The report may be using a prior rate table. Can we confirm which version is active?"
• "Several merchants are missing from the April residual report. Can we verify their agent code assignment?"

This framing assumes good faith. It invites collaboration. It produces better outcomes than "you underpaid me", which puts the other party on defense before anyone has looked at the data.

What to Bring to the Conversation

• The exception report with documented calculations
• The relevant Schedule A version
• Specific merchant examples, three to five representative MIDs, not the entire portfolio
• The total impact for the period, stated factually
• A clear ask: "Can we align the configuration to match our Schedule A?" or "Can we review the rate table applied to these merchants?"

What to Expect

Processors and ISOs respond to well-documented variance differently:

• Configuration correction, A common positive outcome. The processor or ISO identifies a configuration difference, aligns it to your Schedule A, and may issue a retroactive adjustment for affected periods.
• Contract clarification, Sometimes the variance reveals ambiguous contract language. Both parties interpret the Schedule A differently. The resolution is a contract clarification or amendment, not a configuration fix.
• Explanation, Sometimes the processor explains why the report matches their reading of the agreement and your expected calculation did not, a boarding-date tier you overlooked, an expense treatment you misread, a minimum that overrode the percentage. Useful even when no adjustment is issued.
• No immediate resolution, Some findings take time. Rate table migrations, system updates, and multi-department reviews do not happen overnight. Document the open item and follow up.

None of these outcomes require adversarial framing. All of them benefit from the documentation you prepared in phase two.

Phase Four: Reconcile

Reconciliation in this context means closing the loop, confirming that raised findings were addressed and that subsequent reports reflect the corrected configuration.

After a Configuration Correction

When the processor corrects a rate table or configuration issue, upload the next month's residual report and re-run your audit. Verify that the previously flagged exceptions are resolved. Document the correction for your records.

If retroactive adjustments were issued, reconcile those separately against the periods they cover. Confirm the adjustment amounts match the variance you originally documented.

After a Contract Clarification

If the resolution was a contract interpretation rather than a configuration fix, update your Schedule A reference in your reconciliation tool to reflect the agreed interpretation. Re-run prior periods if the clarification affects historical calculations.

Building the Habit

Recovery is not a one-time event. It is a monthly practice:

1. Verify the current period's report against your Schedule A
2. Document new exceptions
3. Raise material findings through proper channels
4. Track open items from prior periods
5. Reconcile corrections in subsequent reports

Agents who run this cycle monthly maintain alignment between their contract and their residuals. Agents who run it once a year discover compounding variance that is harder to unwind and harder to explain.

Professional Principles for the Recovery Process

Your Contract Is the Source of Truth

Every conversation starts with what your Schedule A says. Not what you think is fair. Not what another agent earns. Not what industry forums suggest. Your contract.

Variance Is a Question, Not a Verdict

A discrepancy means the numbers do not match. It does not mean someone acted in bad faith. Approach every finding as a question worth answering, not a crime worth prosecuting.

Relationships Matter More Than Any Single Period

The payment processing industry is smaller than it looks. Agents who handle variance professionally build trust with processor representatives. That trust pays dividends across years of portfolio growth. Agents who burn relationships over a single period's variance often lose more than they recover.

Automate Verification, Humanize the Conversation

The mechanical work, calculating expected residual for thousands of line items, should be automated. The professional work, interpreting findings, framing conversations, deciding what to raise, should be human. Residual Genius handles the first so you can focus on the second.

Document Everything, Escalate Selectively

Not every variance warrants a processor conversation. Rounding differences, immaterial amounts, and known timing quirks can be dismissed. Material systematic patterns across many merchants warrant documentation and a conversation. Judgment about what to raise is yours. Completeness of verification is what automation provides.

The Outcome Agents Actually Want

The goal is not to win a fight. The goal is to earn what your contract specifies, consistently, every month, across your entire portfolio. That requires knowing when the numbers diverge and having the professional process to align them.

Verify. Document. Raise. Reconcile. Repeat monthly.

Residual Genius automates verification and documentation. You bring the professional judgment to raising and reconciling. Together, that is how payment agents recover residual discrepancies without damaging the relationships their business depends on.

Start your free residual audit, verify your latest report against your Schedule A and build the documentation you need for your next processor conversation.