How to Read Your Schedule A (and Verify It Against Your Residuals)

Your Schedule A Is the Contract. the Report Is the Claim.

Every payment agent has signed an ISO processing agreement. Attached to that agreement, sometimes as an exhibit, sometimes as a separate document, sometimes buried in an email from 2019, is a Schedule A. Also called a residual schedule, rate schedule, or compensation schedule, this document is the single most important reference for verifying whether your monthly residual report is correct.

If you cannot read your Schedule A confidently, you cannot reconcile your residuals confidently. Full stop.

Residual Genius uses your Schedule A as the source of truth, not industry averages, not processor defaults. We calculate what your contract specifies and show where the report diverges.

What a Schedule A Actually Contains

Schedule As vary in format. Some are clean spreadsheets with labeled columns. Others are scanned PDFs with handwritten annotations. A few are prose paragraphs that require interpretation. Despite the format differences, nearly every Schedule A addresses the same core elements.

Agent Identification and Hierarchy

The top of a Schedule A typically identifies the agent or ISO by name, agent code, and sometimes hierarchy position, whether you are a direct ISO, a sub-agent, or a referred partner. This matters because residual calculations can differ by hierarchy level. A sub-agent's Schedule A may show a split where the house retains a portion before your rev-share applies.

Verify that the agent code on your residual report matches the agent code on your Schedule A. A mismatch here means you may be looking at residuals for a different book of business entirely.

Rev-Share Percentages by Line Item

The heart of the Schedule A is the rate table: a list of line item categories and the rev-share percentage you earn on each. Common categories include:

• Interchange income, your share of interchange revenue after expenses
• PIN debit, often a separate rate from signature debit and credit
• Monthly fees, statement fees, PCI fees, minimum fees, account fees
• Transaction fees, per-transaction authorization, AVS, batch fees
• Equipment revenue, terminal lease or purchase income
• Gateway and value-added services, ecommerce gateway, tokenization, fraud tools

Each category should have an explicit percentage. If your Schedule A says "50% of net interchange income" and the report pays you on gross interchange before expense deduction, that is a reconcilable variance, not a guess, a math problem with a contract answer.

Boarding-Date Tiers and Effective Dates

Most Schedule As are not one flat rate forever. They include effective dates, the date from which a rate table version applies, and sometimes boarding-date tiers that grant different rates depending on when a merchant was boarded.

A typical structure: merchants boarded before a stated cutoff earn one interchange rate; merchants boarded after earn another. Or: a promotional rate for the first year after boarding, reverting to standard rates thereafter. Your executed Schedule A defines the actual dates and percentages, do not assume generic cutoffs.

When you reconcile, you need to know which rate version applies to each merchant for the reporting period. Applying the current Schedule A to a merchant still on a legacy rate table produces false exceptions. Ignoring tier logic produces missed variance. Version-aware matching is non-negotiable for accurate reconciliation.

ACH and Funding Rates

Some Schedule As specify ACH funding rates, what you earn (or pay) on the movement of funds from the processor to the merchant's bank account. These are often expressed as a per-deposit fee or a basis-point charge. They appear as separate line items on the residual report and reconcile independently from interchange rev-share.

Agents frequently overlook ACH lines because interchange dominates the conversation. On large portfolios, ACH variance across hundreds of merchants adds up. Check your Schedule A for ACH-specific language and reconcile those lines explicitly.

Expense Treatment and Pass-Through Language

Your Schedule A may include language about how expenses are treated, which costs are pass-through to the merchant, which are absorbed by the processor, and which affect your rev-share base. This language is often the most ambiguous section of the document.

Phrases like "net of applicable network fees" or "after processor cost recovery" require interpretation. When reconciliation surfaces variance on expense-heavy line items, the Schedule A's expense language is where you look for the contractual answer. Our article on expense pass-throughs and rev-share allocation walks through the mechanics in detail.

How to Read Rev-Share Percentages In Context

A percentage on your Schedule A is never just a number. It is a number applied to a base, during a period, for a specific merchant, under a specific rate version. Reading it in isolation is how agents get reconciliation wrong.

"Of Net" Versus "of Gross"

This is the most consequential distinction in residual accounting. Net means income minus associated expenses on that line item before your rev-share applies. Gross means the full income amount before expense deduction.

Example (illustrative math, not a real merchant): Schedule A grants fifty percent of net interchange. Interchange income is $10,000 and interchange expenses are $4,000, net is $6,000, expected residual $3,000. If the report pays fifty percent of $10,000 gross instead, actual is $5,000 and variance is $2,000 on that line alone.

Multiply that across a portfolio and the scale of calculation-base variance becomes obvious.

Split Arrangements and House Retains

Some Schedule As show your rev-share as a percentage of a sub-agent split rather than a percentage of the processor's gross. A structure where the house retains twenty percent and you earn fifty percent of the remainder is not the same as earning fifty percent outright. Read the hierarchy language carefully before applying percentages.

Minimums, Maximums, and Caps

Occasional Schedule As include minimum monthly residual guarantees or maximum caps on certain line items. These override the standard percentage calculation when triggered. A merchant with very low volume might hit a minimum that pays more than the percentage would yield. A high-volume merchant might hit a cap that pays less. Reconciliation logic must account for these thresholds when they exist in your contract.

Verifying Your Schedule A Against the Residual Report

Reading the Schedule A is step one. Verifying it against what you were actually paid is step two, and this is where most agents stop, because manual verification at scale is brutal.

The Merchant-By-Merchant Walkthrough

Pick one merchant, ideally a mid-volume account with several line item types. On the residual report, identify every line item for that merchant: interchange income, interchange expense, PIN debit, monthly fees, transaction fees. For each line item:

1. Find the matching category on your Schedule A
2. Confirm the rev-share percentage and the rate version effective for that merchant's boarding date
3. Calculate expected residual: net income × rev-share percentage
4. Compare to the actual residual paid on the report
5. Record the variance, if any

Do this for five merchants and you will learn more about your portfolio than a year of glancing at totals. Do it for five hundred merchants by hand and you will run out of month.

What to Look for on the First Pass

On your first structured reconciliation pass, focus on these high-signal checks:

• Interchange net versus gross, Is rev-share applied to net income on interchange lines?
• Fee categories you did not negotiate, Line items on the report with no corresponding Schedule A category may be pass-throughs you accepted, or categories worth asking about
• Merchants with zero residual on active accounts, An active merchant with volume but zero agent residual warrants investigation
• Rate consistency across similar merchants, Merchants boarded in the same period with the same pricing should show consistent rev-share application; divergence suggests configuration differences worth reviewing
• Expense lines that affect your base, Are expenses being deducted before your rev-share calculation in a way your contract supports?

Documenting What You Find

Professional reconciliation produces a paper trail. For each variance you identify, document:

• Merchant MID and reporting period
• Line item category
• Schedule A rate and version applied
• Your expected calculation with the formula shown
• Actual amount from the report
• Variance amount and direction

This documentation is what you bring to a processor conversation, not accusations, but alignment requests backed by contract language and arithmetic. The Schedule A reconciliation landing page describes how Residual Genius structures this output automatically.

Common Schedule A Problems Agents Discover During Reconciliation

The Schedule A You Have Is Not the Schedule A In Effect

ISO agreements get amended. Rate changes get negotiated verbally and formalized months later. The Schedule A in your filing cabinet may not match the rate table active in the processor's system. Reconciliation surfaces this misalignment as systematic variance, every merchant, same direction, same line item.

When this happens, the resolution is administrative: obtain the current effective Schedule A from your ISO operations contact and update your reconciliation baseline.

Ambiguous Category Mapping

Your Schedule A says "Gateway Services: 70%." The report shows separate lines for "Gateway Monthly," "Gateway Per Transaction," and "E-Commerce Access Fee." Are all three gateway services? Reasonable people disagree. Reconciliation flags the variance; the conversation with your processor clarifies the mapping.

Missing Merchants on Legacy Rate Tables

Merchants boarded before a Schedule A amendment may still be on prior rates for some line items even after the amendment took effect. Processor systems do not always migrate every merchant to the new table automatically. Reconciliation at the merchant level reveals who is on which version.

Building a Reconciliation Habit Around Your Schedule A

Agents who reconcile monthly catch drift early. Agents who reconcile annually discover compounding variance that is harder to unwind. The Schedule A does not change every month, but the portfolio does, new merchants, closed accounts, rate amendments, platform migrations.

A practical monthly workflow:

1. Confirm you have the current effective Schedule A on file
2. Upload the processor residual report
3. Reconcile line by line against the Schedule A
4. Review exceptions, classify material variances, dismiss noise
5. Document findings and raise alignment questions through proper channels

This workflow takes minutes with automated reconciliation. Manual line-by-line work at portfolio scale rarely finishes completely each month.

Your Contract. Your Numbers. Your Decision.

The Schedule A is not a historical artifact. It is a living reference that governs every dollar you earn on every merchant in your portfolio. Reading it carefully and verifying it against your residuals is the most valuable operational habit a payment agent can develop.

Residual Genius reads your Schedule A the same way you would, line item by line item, version by version, merchant by merchant, and shows you where the report diverges. We hold the mirror. You hold the contract. Together, that is reconciliation.

Start your free audit, upload your Schedule A and your latest residual report. See the variance in minutes, not days.