How to Audit Your Residuals (Step by Step)

What a Residual Audit Actually Is

A residual audit is not a vibe check on your deposit. It is a structured comparison between what your Schedule A says you should earn and what your residual report says you were paid, calculated line item by line item, merchant by merchant.

The output is an exception report: a list of variances where paid is less than expected (or sometimes more, which also warrants review). Exceptions backed by contract math are the evidence you use to recover underpayment and fix processor configuration.

This guide walks through the audit workflow agents use monthly. You can execute it manually for a small book or with automation for scale.

Step 1: Gather Your Source Documents

Before opening a spreadsheet, collect:

| Document | Purpose | |---|---| | Executed Schedule A (all amendments) | Rate table, tiers, effective dates | | Detail residual report for target month | Paid amounts by MID and line item | | Merchant roster with boarding dates | Tier assignment | | Prior audit exception log (if any) | Track recurring issues and credits |

Confirm the report agent code matches your Schedule A. Confirm reporting period matches the month you intend to audit.

If you only have a summary report without MID detail, request a detail export before proceeding. Summary-level audits cannot catch merchant-level drift.

Step 2: Build Your Line Item Mapping Table

Processors use internal codes. Your Schedule A uses category names. Create a mapping once:

| Report code / description | Schedule A category | Rev-share rate | Net or gross base | |---|---|---|---| | IC Income | Net interchange | 50% | Net | | PIN DB Net | PIN debit | 40% | Net | | Stmt Fee | Monthly fees | 80% | Net | | PCI NC | PCI non-compliance | 0% | N/A |

Unmapped codes are audit gaps. Research unmapped rows before assuming zero pay is correct.

Our residual report reading guide explains common column layouts.

Step 3: Tag Merchants with Boarding Tiers

For each MID, record boarding date and assigned tier per Schedule A:

• Legacy tier: boarded before cutoff, higher interchange rate
• Current tier: boarded on or after cutoff

When Schedule A has multiple amendments, tag which version applies to each merchant for the audit month.

Tier errors are a top source of systematic variance. See five common ways processors underpay agents.

Step 4: Compute Expected Pay per Line Item

For each merchant row in the detail report:

Expected Pay Formula

1. Identify net income (income minus expense, or pre-calculated net column)
2. Look up Schedule A rate for that line item category
3. Apply house retain if your contract specifies split-before-agent-share
4. Calculate: expected = net times rate (adjust for retains)
5. Record expected alongside paid from report

Worked Examples

Example: MID ending 5512, interchange net $620, legacy tier 50%, no house retain. Expected: $310. Paid: $310. Variance: $0.

Example with variance: Same MID, PIN debit net $90, tier rate 40%. Expected: $36. Paid: $27. Variance: -$9.

Use consistent rounding rules (cent-level) and document them. Processors round differently; immaterial cent drift is normal, dollar drift is not.

Step 5: Apply Your Materiality Threshold

Not every cent requires action. Define thresholds:

• Line item threshold: many agents use $5 or $10 negative variance
• Merchant threshold: total negative variance per MID per month (e.g., $25)
• Portfolio review: always inspect top 20 merchants by volume

Below-threshold exceptions can be logged but not escalated. Above-threshold exceptions enter the dispute pipeline.

Step 6: Group Exceptions Into Patterns

Sort exceptions by line item type and count merchant penetration:

| Line item | Affected MIDs | Total monthly variance | |---|---|---| | PIN debit | 67 | -$743 | | Statement fee | 412 | -$3,296 | | Interchange | 8 | -$1,120 |

High penetration on one line item type signals systematic configuration error. Low penetration may be merchant-specific mapping issues.

Pattern grouping is how you turn 800 spreadsheet rows into three processor tickets that actually get resolved.

Step 7: Validate Against Schedule A Language

For top patterns, re-read Schedule A sections governing:

• Net versus gross base definitions
• Expense pass-through treatment
• Fee categories included or excluded
• Override expiration dates

If Schedule A language is ambiguous, note the ambiguity in your log. Escalation may require ISO legal or processor operations clarification before credits post.

What is a Schedule A and why it determines your pay covers document fundamentals.

Step 8: Document and Escalate

For each escalation package include:

1. Pattern description (one paragraph)
2. Schedule A excerpt with rate and effective date
3. Aggregate variance dollars and MID count
4. Three sample merchant calculations (expected vs paid)
5. Requested remedy: configuration fix and credit period

Professional, math-forward tickets resolve faster than emotional complaints.

Track ticket IDs and promised credit months. Verify credits on future reports. Processors sometimes fix forward without retro credit unless you ask.

Step 9: Archive and Compare Month Over Month

Store each audit:

• Source report file
• Exception export
• Escalation correspondence
• Credits received

Compare exception counts month over month. Rising counts after migration events are expected until fixed. Flat portfolio with rising exceptions signals new drift.

Step 10: Automate at Scale

Manual audits teach the mechanics. They do not scale past roughly 50 to 75 MIDs without error and fatigue. Automation applies your Schedule A mapping to every row consistently, every month, in minutes.

Agents who automate audit monthly catch migration errors in cycle one instead of cycle six.

How Often to Audit

| Portfolio size | Recommended cadence | |---|---| | Under 50 MIDs | Monthly manual or automated | | 50 to 200 MIDs | Monthly automated | | 200+ MIDs | Monthly automated plus quarterly deep review |

Annual audit alone is insufficient. Drift compounds quietly.

Tools and Templates That Help

You do not need expensive software to start, but you do need consistency:

• Mapping tab: report code to Schedule A category (update when new SKUs appear)
• Merchant tab: MID, DBA, boarding date, tier, status
• Audit tab: expected, paid, variance formulas per row
• Escalation tab: ticket ID, pattern, sample MIDs, promised credit month

Spreadsheets work to roughly 75 MIDs. Beyond that, formula errors and version drift in shared files create their own risk. Automation applies the same mapping logic every month without fatigue.

Common Audit Mistakes to Avoid

| Mistake | Fix | |---|---| | Auditing against marketing rates | Use executed Schedule A only | | Ignoring positive variance | Investigate; may indicate cap or error | | One merchant proves "all good" | Spot-check plus full portfolio scan | | Closing ticket after forward fix | Confirm retro terms in writing | | Skipping fee lines | Audit all material categories |

Treat your audit log as a living document, not a one-time spreadsheet you delete after a credit posts. Future you (or a buyer) will need the trail.

Run Your First Audit Today

You now have the workflow. The only remaining step is executing it against your latest report.

Residual Genius automates steps 2 through 6: Schedule A mapping, tier logic, expected pay calculation, and ranked exception output. Upload a CSV or Excel export in a supported processor layout. First audit free.

Start your free audit and see your exception report in minutes.