Understanding Expense Pass-Throughs and Rev-Share Allocation

The Line Items Agents Skip, and Should Not

Interchange income gets the attention. Monthly volume gets the attention. The headline rev-share percentage on your Schedule A gets the attention. Expense pass-throughs get ignored, until reconciliation surfaces variance that does not make sense any other way.

Expense pass-throughs are costs the processor incurs and reflects on the residual statement: interchange assessments, network fees, PCI compliance charges, regulatory fees, statement fees, and dozens of processor-specific categories. They appear as expense lines, negative numbers, debits, or deductions, on the merchant's residual detail. How they interact with your rev-share calculation is where much of the complexity in residual accounting lives.

This article explains the mechanics neutrally. No accusations, no assumptions about intent, just how pass-through costs flow through a residual statement and why allocation differences between your contract and the processor's configuration create reconciliation gaps worth checking.

What an Expense Pass-Through Actually Is

When a merchant processes transactions, costs accrue, interchange paid to card networks, assessment fees, PCI compliance costs, statement production, and other processor-incurred expenses. Processors handle these costs differently depending on the merchant's pricing structure and the ISO agreement.

In a pass-through model, the expense is billed to the merchant. It appears on the residual statement as an expense line that reduces the merchant's net. The merchant pays the cost; the processor collects it.

In an absorbed model, the processor pays the cost and does not pass it through to the merchant. The expense may still appear on the statement for transparency but does not reduce the merchant's net payout.

Your Schedule A may specify which model applies to which expense categories, or it may be silent, leaving interpretation to industry convention and processor configuration. Silence in the contract is a common source of reconciliation variance.

How Pass-Throughs Interact with Rev-Share

Rev-share is a percentage applied to a base. The critical question for every expense line is: does this expense reduce the base before my rev-share percentage is applied, or does it not?

Scenario A: Expense Reduces Net Before Rev-Share

(Illustrative numbers.) Interchange income: $10,000. Interchange expense (network assessments passed through): $3,500. Net interchange: $6,500. Schedule A: fifty percent of net interchange. Expected residual: $3,250.

This is the most common structure. Expenses that are true pass-throughs reduce the income base before rev-share applies. You earn rev-share on what is left after the merchant's costs are deducted.

Scenario B: Expense Does Not Affect Rev-Share Base

(Illustrative numbers.) Interchange income: $10,000. PCI non-compliance fee: $19.95 on the statement. Schedule A: fifty percent of net interchange, with PCI fees pass-through only and excluded from the rev-share base on interchange.

Expected residual on interchange: $5,000, fifty percent of $10,000, because the PCI fee should not reduce that base. If the report deducts PCI from interchange net before applying rev-share, expected drops to $4,990.01. Small on one MID; material across a portfolio with many PCI lines.

Scenario C: Expense with Its Own Rev-Share

Some Schedule As grant rev-share on expense lines, e.g., fifty percent of a monthly statement fee passed through to the merchant. Reconcile these as their own categories; do not net them into interchange math.

Allocation Methods That Create Variance

Even when both parties agree on the general model, expenses reduce net before rev-share, the specific allocation method can differ.

Merchant-Level Versus Portfolio-Level Allocation

Some expenses are incurred at the portfolio level but allocated to individual merchants on the statement. A processor-wide network assessment might be split across all merchants equally, by volume, or by transaction count. Your contract may not specify the allocation method. The processor uses their default. Your reconciliation assumes a different default. Variance appears on every merchant.

This is a contract-interpretation difference, not malice. Reconciliation makes it visible. A conversation with your processor representative clarifies which allocation method the system uses.

Expense Timing and Cutoff

An expense incurred in one board month may appear on the next month's statement depending on processor cutoff rules. Reconciling March residuals against March expenses when the processor posts some expenses in April creates apparent variance that resolves in the following period. Monthly reconciliation with period-matched data reduces false exceptions from timing differences.

Gross Expense Versus Net Expense Presentation

Some reports show expenses as gross amounts before any processor markup. Others show the all-in pass-through including processor margin. Your Schedule A rev-share on expense lines may apply to one presentation but the report reflects the other. The variance is a presentation difference worth documenting.

Common Pass-Through Categories and What to Check

Interchange Assessments and Network Fees

These are the largest expense pass-throughs on most statements. They reduce interchange income to net interchange income before rev-share applies, in the standard model. Verify that your reconciliation calculates expected residual on net interchange, not gross, and that the expense lines on the report match the income lines they offset.

PCI Compliance Fees

PCI fees appear on nearly every merchant statement, compliance fees, non-compliance penalties, scanning charges. Your Schedule A may or may not address whether PCI fees affect your rev-share base. If it does not, reconciliation will surface variance when the processor deducts PCI from net before applying your percentage. The resolution is contract clarification, not confrontation.

Statement and Account Fees

Monthly statement fees, annual fees, minimum fees, and account maintenance charges are often pass-through with their own rev-share percentages on the Schedule A. Reconcile these as separate line item categories, do not lump them into interchange net.

Regulatory and Assessment Fees

Card brand assessments, NAPF fees, FANF fees, and regulatory surcharges vary by network and merchant category. They appear under different names on different processor reports. Mapping these to your Schedule A categories is a reconciliation prerequisite. Unmapped expense lines produce either false exceptions or missed variance.

Equipment and Gateway Costs

Terminal lease fees, gateway monthly charges, and equipment insurance pass-throughs often have dedicated rev-share rates on the Schedule A, sometimes different from interchange rates. Reconcile equipment and gateway expense lines against their specific Schedule A categories, not against interchange.

Why Pass-Through Reconciliation Breaks In Spreadsheets

Manual reconciliation in spreadsheets typically handles interchange income and expense as a single net column, income minus expense, times rev-share percentage. This works when every expense reduces the rev-share base uniformly. It fails when:

• Some expenses are pass-through only and do not affect the rev-share base
• Expense lines have their own rev-share percentages separate from income lines
• Expenses are portfolio-allocated and the allocation method differs from your assumption
• Expense categories on the report do not map cleanly to Schedule A categories

Each of these scenarios requires line-item-level reconciliation with category-specific rules, exactly what an automated audit engine applies per line item based on your Schedule A configuration.

The Neutral Framing Agents Should Use

When pass-through variance surfaces in reconciliation, the professional framing is:

"Our Schedule A specifies that rev-share on interchange applies to net income after pass-through expenses. The report appears to deduct [specific expense category] from the base before applying our percentage. Can we confirm the configuration matches our agreement?"

Not: "You are stealing my rev-share by deducting expenses you should not deduct."

The first framing opens a configuration review. The second closes it. Residual Genius produces the arithmetic for the first framing. You deliver it.

Pass-Throughs Are Where Contracts Get Ambiguous

The most experienced agents will tell you, if you can find one who reconciles thoroughly, that pass-through treatment is where Schedule A language is most often ambiguous. Contracts written years ago may not address fee categories that did not exist when the agreement was signed. Processor systems evolve faster than contract language.

Reconciliation does not resolve ambiguity. It surfaces the financial impact of ambiguity so you can resolve it, through contract clarification, configuration alignment, or informed acceptance of the processor's interpretation.

That is the neutral truth: pass-through mechanics are complex, contract language is often incomplete, and agents who reconcile pass-through lines explicitly catch variance that agents who reconcile only interchange totals never see.

Check Your Pass-Through Lines

If you have never reconciled expense pass-throughs separately from interchange income, your next audit will likely surface findings. That is not a crisis, it is visibility you did not have before.

Upload your Schedule A and your latest residual report. Reconcile every line, income and expense, against the correct rev-share rules for each category. See where pass-through allocation creates variance worth reviewing.

Our Schedule A reconciliation page describes the full workflow. Our guide on common sources of residual discrepancies places pass-through variance in the broader context of reconciliation mechanics.

Start your free residual audit, reconcile income and expense lines against your Schedule A in minutes. You decide what the variance means.