Processor underpayment
Detect processor underpayment before it compounds
Underpayment rarely appears as a single obvious error. It shows up as small negative variances on the same fee type across many merchants, month after month, until someone reconciles against Schedule A.
Your first audit is free
- One free audit on any processor format
- Map your Schedule A once, then reconcile every line item
- Then $147/mo Agent unless you cancel before your first charge
Underpayment hides in line items, not headlines
Agents who only compare this month's net deposit to last month's deposit miss structural underpayment. The total can move with volume while specific categories consistently pay below contract.
- Rev-share applied to the wrong base (gross vs net) reduces pay without changing report layout.
- Fees billed but excluded from your residual base may never reach your Schedule A math.
- Post-migration merchants may sit on default tiers until someone audits against the active contract.
- Without pattern detection, underpayment is discovered late or not at all.
How Residual Genius surfaces underpayment patterns
The audit engine flags material negative variance per line item, then groups exceptions by fee category so you see portfolio-wide patterns instead of isolated rows.
Compute contract-correct expected pay
Expected residual uses your Schedule A rev-share on net, matching how your agreement defines the residual base.
Group variance by line item type
Repeated underpayment on the same category across merchants signals configuration or mapping issues worth escalating.
Quantify total recoverable impact
Confirmed underpayment totals give you a documented starting point for alignment conversations.
Residual Genius, independent residual auditing for ISO agents.
Frequently asked questions
- What counts as processor underpayment in an audit?
- When actual residual on a line item is materially below expected residual computed from your Schedule A for that merchant and period.
- Will this accuse my processor of wrongdoing?
- No. The output is a factual comparison between your contract terms and the report you received. You decide how to use documented variance.
- Can underpayment be a mapping issue instead of pay error?
- Yes. That is why reconciliation groups patterns. A systematic mapping mismatch looks different from a one-off merchant anomaly.
Ready to reconcile your next report?
No upfront payment. Start your first audit free, then $147/mo. Cancel anytime in one click.
Audit your first report free