5 Common Ways Processors Underpay Agents

Systematic Beats Random

When ISO agents discover they were underpaid, the story is rarely one villain merchant or one bad month. It is the same calculation error repeated across dozens or hundreds of accounts. Processors run complex rate engines. ISOs migrate platforms. Merchants change products. Configuration drifts.

The patterns below appear across many processor environments. Discussing them is not an accusation against any specific company. It is practical education about where contract math and report math diverge. Each pattern is recoverable when you bring Schedule A evidence.

Pattern 1: Rev-Share Applied to Gross Instead of Net

What Happens

Your Schedule A grants a percentage of net interchange (income minus interchange expenses on that merchant). The report calculates your share on gross income before expenses.

Why It Happens

Rate engine defaults, legacy table mappings after acquisitions, or ambiguous Schedule A language interpreted in the processor's favor.

How to Spot It

Consistent negative variance on interchange lines proportional to expense ratio. If expenses are roughly 40% of income, you see a predictable shortfall near 40% of what you expected on gross-base math.

Example

Net interchange $750, Schedule A 50%, expected $375. Paid $525 (50% of $1,050 gross income). Variance: -$150 per merchant per month.

Recovery Approach

Document net-base requirement from Schedule A. Show merchant-level math. Aggregate across affected MIDs. Processors often issue true-up credits when pattern is clear.

Learn the underlying math in how residual splits and revenue share work.

Pattern 2: Stale Rate Tables After Platform Migration

What happens: Portfolio moves to a new processing platform. Internal rate tables reset to defaults. Merchants should retain boarding-tier rates per contract, but the engine applies current defaults instead.

Why it happens: Migration cutover prioritizes transaction processing over residual rate mapping. Mapping backlog persists for months.

Fingerprint: Variance begins the migration month. Affected merchants often share the same boarding era or product type. Line items may appear under new category codes.

Example: 140 merchants migrated in August. From September forward, PIN debit pays 30% instead of contracted 40% on 89 of those MIDs. Monthly portfolio impact: $890 estimated.

Recovery: Provide pre-migration report sample showing correct rate. List affected MIDs. Request rate table correction plus retroactive credit for defined lookback period (contract-dependent).

Pattern 3: Fee Lines Mapped to Non-Rev-Shareable Buckets

What happens: Monthly fees, PCI fees, or gateway fees appear on the report but map internally to categories with 0% agent rev-share, despite your Schedule A granting 80% or 100% on those fees.

Why it happens: Fee SKU changes, bundled product codes, or default ISO house-retain rules applied before agent split.

Fingerprint: Small per-merchant variance on fee lines, high merchant penetration. Interchange reconciles clean while fee income underperforms.

Example: Statement fee $10, Schedule A 80%, expected $8. Paid $0 on 620 active MIDs. Monthly gap: $4,960.

Recovery: Map fee SKU to Schedule A row. Show executed rate. Processors re-map categories in configuration rather than disputing individual merchants one by one.

Pattern 4: Boarding Tier or Effective Date Mismatch

What happens: Merchants boarded under legacy tier rates pay current-tier rates (or vice versa). Schedule A cutoff dates do not match processor system cutoffs.

Why it happens: Manual boarding date entry errors, timezone cutoffs, amended Schedule A not loaded into rate engine.

Fingerprint: Variance isolated to merchants boarded near tier boundary dates. Same line item type, two implied rate clusters matching two Schedule A tiers.

Example: Cutoff January 1, 2022. Merchants boarded November through December 2021 should be legacy 50%. Report pays 45% on 34 MIDs. Average interchange net $380, variance ~$19 per MID monthly: ~$646.

Recovery: Export boarding dates from CRM. Match against processor records. Cite Schedule A tier table with cutoff. Request tier correction in rate engine.

See what is a Schedule A and why it determines your pay for tier documentation tips.

Pattern 5: Missing or Suppressed Line Items

What happens: Merchants generate income the report never attributes to your agent code: interchange sub-categories, LTE revenue, cash discount program income, or adjustment-suppressed rows.

Why it happens: Agent hierarchy mapping errors, MID linked to wrong ISO code, product enrolled under house master MID.

Fingerprint: Merchant shows volume in gateway portal but zero or thin residual rows. Comparison to peer merchants with similar volume shows material income gap.

Example: Restaurant MID doing $95,000 monthly volume shows $12 agent residual total while similar MIDs in same cohort average $140. Investigation reveals interchange sub-category routed to house code.

Recovery: Identify missing categories via portal versus report comparison. Prove merchant belongs to your book (boarding docs, agent code assignment). Request re-mapping and restatement.

How to Scan Your Portfolio for These Patterns

You do not need to find patterns manually across thousands of rows:

1. Reconcile report to Schedule A line by line
2. Group exceptions by line item type
3. Sort by total variance dollars
4. Count merchant penetration per pattern
5. Prioritize patterns affecting 20+ MIDs or $500+ monthly

Patterns with high penetration are processor tickets. One-off rows may still matter but escalate differently.

If you wonder whether you are affected, start with am I being paid my full residuals?.

Raising Patterns Without Burning Relationships

ISO and processor relationships are long-term. Effective escalation is professional, documented, and aggregated:

• Lead with total impact and merchant count
• Attach Schedule A citation and three sample MIDs
• Request configuration fix plus credit timeline
• Track promised credits against future reports

Accusatory language about intent slows resolution. Math language speeds it up.

Audit Monthly, Not Once

These patterns often run for months before discovery. A single annual audit finds historical credits but allows ongoing drift between audits. Monthly reconciliation catches migration cutover errors in the first cycle.

Follow how to audit your residuals step by step to build the habit.

Pattern 6 (Bonus): Rounding and Aggregation at Portfolio Level

Some processors round per merchant before summing; others sum then round at portfolio level. Cent-level drift per MID is normal. Dollar-level drift across many MIDs on the same line item type is not rounding. It is a configuration signal.

When interchange lines reconcile within $0.02 per merchant but fee lines show $3 to $8 gaps, you are not dealing with rounding. You are dealing with fee mapping or gross-base application.

Building a Pattern Library for Your Book

Maintain a simple log when you find issues:

| Month | Pattern | MIDs | Variance | Ticket | Credit received | |---|---|---|---|---|---| | Mar 2026 | PIN debit 30% not 40% | 67 | -$743 | PROC-8821 | Pending |

Over 12 months this log becomes diligence gold if you sell the book. It also prevents re-opening solved issues when a new analyst reviews your account.

Share aggregate impact first when opening tickets. Processors prioritize fixes that affect hundreds of merchants over isolated rows that look like rounding noise.

When a pattern affects fewer than ten MIDs, still document it. Small patterns sometimes foreshadow a migration issue that will spread next cycle.

Surface Every Pattern In Your Next Report

Manual spot-checks miss systematic variance. Automated reconciliation groups exceptions by line item and shows penetration across your book.

Residual Genius flags gross-base errors, tier mismatches, and fee mapping gaps automatically. Upload a CSV or Excel export in a supported processor layout. First audit free.

Start your free audit and see which patterns appear in your portfolio.