How to Read Your Residual Report (Line by Line)

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

Every month you receive a residual report: a CSV export, PDF summary, or portal download from your processor or ISO. That document claims you earned a specific amount based on specific calculations applied to each merchant in your portfolio. Reading it line by line is how you verify the claim before accepting the deposit.

Most agents skim the summary total. Experienced operators read the detail. The summary tells you what hit your account. The detail tells you whether that number matches your contract.

Report Header Fields

Before you touch merchant rows, confirm the header metadata:

Agent or ISO Code

Your report should filter to your agent code. A code mismatch means you may be viewing another agent's residuals or a consolidated roll-up that includes sub-agent splits you cannot reconcile at this level. Cross-check against your Schedule A and onboarding paperwork.

Reporting Period

Residuals run on calendar months in most programs, but funding may lag. A report labeled "March 2026" should include March activity. Verify the period column on merchant rows matches. Straggler transactions from prior months sometimes appear as adjustment lines.

Rate Table or Schedule A Version

Some processors stamp a rate table version on the report. If your Schedule A was amended in February, March forward should reference the new version for merchants past the effective date. Legacy merchants may remain on prior tiers per boarding-date rules.

Merchant-Level Rows: What Each Column Means

Detail reports typically repeat one row per merchant per line item (or one row per merchant with nested line items in portal views). Standard columns:

MID and DBA

Merchant ID (MID) is the unique account identifier. DBA (doing business as) is the trade name. Always reconcile by MID, not DBA. DBAs change after acquisitions and rebrands.

Line Item Description and Category Code

Descriptions like "IC Income," "PIN Debit Net," "Stmt Fee," or "PCI Non-Compliance" map to Schedule A categories. Processors use internal codes; build a mapping table once and reuse it monthly. Unmapped codes are reconciliation gaps.

Volume (When Present)

Volume columns show transaction counts or dollar volume. Volume itself rarely determines your residual directly except in tiered split programs. Volume helps you sanity-check: a merchant whose volume dropped 80% but whose interchange income stayed flat deserves investigation.

Income, Expense, and Net

The core reconciliation trio:

• Income: gross revenue on that line item
• Expense: associated costs the processor allocates to that line item
• Net: income minus expense (may be pre-calculated or implicit)

Your Schedule A rev-share usually applies to net. Confirm the report uses net as the base before applying your percentage.

Rev-Share Percentage

When shown, this is the processor's claim about which rate they applied. Compare directly to your Schedule A. If the column is blank, derive implied rate: agent residual divided by net (when net is positive).

Agent Residual or Payout Amount

The dollars attributed to you for that line item. This is the number you verify.

Reading Interchange Lines

Interchange is usually split into at least two rows: interchange income and interchange expense. Some reports net them into one row. Others show income and expense separately and expect you to compute net.

Example row set for MID ending 2290:

| Description | Income | Expense | Net | Rate | Paid | |---|---|---|---|---|---| | IC Income | $1,450 | $620 | $830 | 50% | $415 |

Expected: 50% of $830 = $415. Match. No exception.

If paid shows $725, implied rate is 87% of net or gross-base math. Flag it.

PIN debit and assessment lines follow the same logic with different Schedule A rates. See how residual splits and revenue share work for split math.

Reading Fee Lines

Monthly fees reconcile differently from interchange because expenses are often zero:

| Description | Income | Expense | Net | Schedule A | Expected | Paid | |---|---|---|---|---|---|---| | Statement Fee | $10 | $0 | $10 | 80% | $8 | $5 |

Variance: $3. Possible causes: wrong fee split (50% applied instead of 80%), fee categorized under a non-rev-shareable bucket, or house retain applied twice.

PCI fees, regulatory fees, and minimum fees each need their own Schedule A mapping. Agents frequently miss PCI lines because they are small per merchant. Across 900 MIDs, $2 per month per merchant is $1,800 monthly.

Adjustments, Chargebacks, and Holdbacks

Reports include non-merchant rows:

• Portfolio adjustments from prior period corrections
• Chargeback debits allocated to agent residuals
• Reserve or holdback releases
• Bonus or override true-ups

Read adjustment descriptions carefully. A credit labeled "Q4 2025 IC true-up" explains a lump sum. A debit without description requires a ticket. Track adjustments in a separate ledger so base merchant reconciliation stays clean.

Summary Sections: Trust but Verify

Summary tabs show totals by category and merchant count. Use them as checksums, not proof:

1. Sum detail rows for interchange net residuals
2. Compare to summary interchange total
3. Investigate any gap

Summary-only reports (no MID detail) limit reconciliation depth. Request detail exports if your agreement entitles you to them. Without detail, you can only verify category totals, not merchant-level drift.

Red Flags While Reading Line by Line

Watch for these while scanning detail:

• Same line item, same implied rate error across many MIDs (systematic)
• Merchants with zero income rows but active volume (missing line items)
• Merchants boarded before a tier cutoff paying post-cutoff rates (or reverse)
• New gateway or LTE line items you do not recognize after a platform migration
• Negative agent residuals on fee lines where Schedule A grants positive rev-share

Systematic patterns belong in a processor escalation with aggregated variance dollars. Our article on five common ways processors underpay agents catalogs the patterns agents report most often.

Building a Monthly Read Routine

Experienced agents follow a consistent sequence:

1. Confirm agent code and period
2. Spot-check five merchants manually (one high-volume, one low-volume, one new board, one legacy tier, one with gateway)
3. Run automated reconciliation for the full portfolio
4. Triage exceptions above dollar threshold
5. Group by line item type
6. Open tickets for systematic issues
7. Archive report and exception log

Manual spot-checks calibrate your intuition. Automation scales the work.

From Reading to Auditing

Reading the report tells you what the processor claims. Auditing tells you whether the claim matches contract. The step from reading to auditing is applying Schedule A math to every material line.

Follow our step-by-step residual audit guide when you are ready to formalize the process.

Export Formats: CSV, Excel, and Portal Downloads

Processors export residuals in different shapes. CSV files may use quoted fields with embedded commas. Excel exports sometimes split income and expense across tabs. Portal downloads may cap row counts unless you request full detail.

When importing into audit tooling, preserve original files unmodified. Normalization happens inside the audit engine, not by hand-editing source files. Hand edits destroy evidence if you escalate.

If your export truncates at 10,000 rows and your book is larger, request a full extract from processor support before concluding no exceptions exist.

Reconcile Your Next Report Automatically

Line-by-line reading is essential. At portfolio scale, you also need tooling that applies your Schedule A to every row and surfaces exceptions ranked by impact.

Residual Genius accepts validated CSV and Excel layouts from supported processors, maps your Schedule A once, and produces a full exception report in minutes. Your first audit is free.

Start your free audit and see exactly where your report diverges from contract.