How Schedule A Drives Residual Reconciliation

Schedule A Is the Source of Truth

The Schedule A (or residual schedule) attached to your ISO processing agreement lists rev-share percentages by line item type, interchange, PIN debit, monthly fees, equipment, and dozens of processor-specific categories. Every residual audit ultimately asks one question: did the processor pay according to this table?

If your Schedule A lives in a PDF, a scanned contract, or a spreadsheet maintained by someone who left three years ago, you are not alone. Most agents audit against memory and spot checks. That is how systematic underpayments hide for quarters.

Effective Dates and Version Drift

Processors reprice merchants. ISOs negotiate new splits. A Schedule A effective January 1 does not govern December board dates, and overlapping versions are a frequent source of reconciliation noise. A serious audit engine resolves which rate version applies to each reporting period and flags merchants with no matching version instead of silently defaulting.

Residual Genius ingests Schedule A from PDF, screenshot, or spreadsheet and stores versioned rates so each upload reconciles against the right contract snapshot.

From Schedule A to Expected Residual

Expected residual is computed from net income on each line item multiplied by your contracted rev-share, not from raw volume or transaction count. Rows where income equals expense produce zero net and zero expected residual; flagging those as underpayments is a classic spreadsheet error.

Once expected residual is established per line item, variance against the processor's actual payout identifies exceptions worth confirming, and systematic groups worth escalating to the processor.