A merchant statement analyzer should reconstruct last month as billed, split every line into pass-through versus markup, compute the effective rate on that as-billed base, then re-price only the models the law lets you offer. If it skips the as-billed sheet, it is quoting a story, not an audit. If it rebuilds a surcharge or dual-pricing program your state or the card brands forbid, it is selling a violation. Apply that rubric to any tool. Named vendors do not matter.
- 1Parse the as-billed month. Every fee line, sales volume, and transaction count. Do not drop PCI, batch, or statement fees.
- 2Split pass-through from markup. Interchange and network assessments versus processor margin and program extras.
- 3Compute effective rate. Total fees divided by card volume for the same period. That is the as-billed number.
- 4Re-price only legal models. Show all six models, minus any the merchant's state or brand rules forbid.
- 5Show the work. Every classification, assumption, and rebuilt model. A person can audit it.
Parse the as-billed month first
Most "savings" screens start at the destination: a round interchange-plus quote, a surcharge program, a blended rate that looks tidy. The honest order is the reverse. Prove what you paid. The as-billed sheet is every discount line, assessment, per-item, batch, PCI, gateway, and monthly extra, mapped back to the statement page it came from.
Without that sheet a comparison has no denominator. Two quotes of "2.49 percent" can mean different things: one including interchange, one excluding it, one omitting PCI, one baking it in. How to read a merchant statement is the paper version of this work. An analyzer is the same reconstruction, without transcribing by hand.
If the PDF is not a full statement (equipment invoice, 1099, truncated first page), the analyzer should stop. Guessing volume from a summary box is how audits become marketing.
Split pass-through from markup
Every card fee sits in one of three layers. Two are pass-through. One is negotiable. Mixing them is how statements stay illegible.
Interchange goes to the card-issuing bank. The networks publish the schedules. Hundreds of categories, by card product, how the card was captured, and merchant category. No processor sets it. No processor can waive it.
Assessments are the networks' own dues: small percentage and per-item charges, plus named network fees that often appear as APF, NABU, FANF, or integrity lines. Also pass-through.
Processor markup is everything else: the percentage over cost, the per-item add-on, statement fees, batch fees, PCI program fees, gateway, monthly minimums, and the long tail of "regulatory" or "compliance" lines that are not invoices from a regulator. This is the only layer anyone competes on.
An analyzer that cannot classify a line should flag it, not bury it under "discount." A PCI compliance fee is usually a processor program, not a PCI SSC bill. Treat it as markup or program cost unless the statement actually shows a network assessment. The six pricing models only become comparable after this split. Otherwise you are comparing a bundled teaser to a cost-plus markup and calling them the same rate.
Compute the as-billed effective rate
Effective rate is total fees divided by total card volume for the same period, times 100. Total fees means every processing line, including the extras. Volume is gross card sales, not net deposits.
Typical processing fees are often described as 1.5 percent to 3.5 percent of the transaction plus a per-item fee (U.S. Chamber of Commerce, 4 Jun 2026). That band is a typical range, not a target and not anyone's quoted rate. The analyzer's job is to put your month on that number line, with the layers visible.
Worked example, illustrative. A shop runs $80,000 in card volume.
| Line | Amount | Layer |
|---|---|---|
| Card volume | $80,000 | |
| Interchange | $1,360 | Pass-through |
| Assessments | $80 | Pass-through |
| Processor percentage markup | $400 | Markup |
| Per-item fees | $90 | Markup |
| Monthly extras (PCI, statement, batch) | $70 | Markup |
| Total fees | $2,000 | |
| Effective rate | 2.50% | $2,000 ÷ $80,000 |
Pass-through is $1,440 (1.80% of volume). The negotiable stack is $560 (0.70%). 2.50% sits inside the Chamber band. That does not tell you whether the 0.70% is earned or padded. It tells you where the conversation is allowed to go: not interchange, not assessments, the $560.
If an analyzer reports 2.19% by omitting the $70 of extras, it has not analyzed the statement. It has edited it.
Re-price only the models the law allows
Once the as-billed base is honest, rebuild the month under the models a merchant can actually run: interchange-plus, tiered, flat-rate, surcharge, dual pricing, and interchange optimization. None is the universal winner. Ticket size, debit mix, card-present share, and risk decide fit. Defaulting every file to interchange-plus is a fluency tell, not a finding.
Then subtract what the law does not allow.
Visa U.S. credit surcharge rules (Visa, U.S. Merchant Surcharge Q and A, 15 Feb 2024): notify the acquirer 30 days before starting; disclose at entry, at the POS, and on the receipt; cannot exceed the merchant discount rate or 3 percent, whichever is lower; never on debit or prepaid. Selecting "credit" on a debit card at the terminal does not make it surchargeable. It is still debit.
Outright state and territory bans as of 2026: Connecticut, Massachusetts, Maine, Puerto Rico. Other states cap or condition. Do not trust a 50-state graphic you did not verify line by line. Check your state attorney general and current card-brand rules before any tool shows a surcharge or dual-pricing scenario as a recommendation.
An analyzer that cannot take a merchant location and suppress illegal scenarios is not ready. Showing a 3 percent surcharge to a Boston shop is not a savings estimate. It is a compliance miss with a dollar sign.
Dual pricing and cash discount are not surcharge with the labels sanded off. If the cardholder sees a fee added at the PIN pad, brand rules treat it as a surcharge. The analyzer should still refuse the shape where the merchant's state forbids it.
What a serious analyzer will not do
A rubric is also a list of refusals.
- It will not run a processor bake-off. Criteria, not a branded scoreboard.
- It will not hide low-confidence lines or average two disagreeing reads. Ambiguous fees stay flagged.
- It will not treat a teaser qualified rate as the as-billed rate when most volume cleared mid-qualified or worse.
- It will not promise a savings percentage it cannot tie to the as-billed sheet.
Speed is not the test. A faster wrong classification is still wrong, and it travels farther.
Show the work, then let a person dispose
A rebuilt rate you cannot trace is a more confident guess. Every figure should walk back to a line on the original PDF. Every model should list its assumptions: card mix held constant, debit excluded from surcharge, extras kept or dropped. The answer six months later is the audit trail, not "trust the tool."
That is the argument in The End of Manual Statement Analysis: parse, classify, re-price across the legal models, cross-check, and keep a human on the low-confidence cases. The machine proposes. A person approves. Neither is asked to do the part they are worse at.
If you want that sequence on a real statement, run the analyzer. The first page worth keeping is the as-billed sheet. The models come after.
FAQ
How should a merchant statement analyzer work? It should rebuild last month as billed, split pass-through from markup, compute an effective rate on that base, then re-price only the models your state and the card brands allow. If it cannot show that work, treat the output as a quote, not an audit.
What does as-billed mean on a processing statement? As-billed is the month you actually paid: every discount, assessment, per-item, batch, PCI, and monthly extra, before anyone rebuilds a cheaper model. It is the denominator for every comparison that follows.
How do I tell pass-through fees from processor markup? Interchange and network assessments are pass-through. No processor sets them or can waive them. Markup is everything the processor or sales organization adds, including many PCI, statement, and batch lines. Only the markup is negotiable.
Should a statement analyzer pick one pricing model for me? No. It should show the legal models side by side on your numbers. Interchange-plus is not the default destination. Ticket size, card mix, and state law decide fit.
Can a statement analyzer tell me if surcharging is legal in my state? It can suppress models your location and brand rules do not allow, and it should. Visa requires 30-day acquirer notice, a cap at the merchant discount rate or 3 percent, and no debit or prepaid. Confirm with your state attorney general and your acquirer before you turn a program on.
What is an effective rate on a merchant statement? Total fees divided by total card volume for the same period, times 100. It is the only number that compares two processors when their statements are formatted differently.
Sources
Questions about how this applies to your business?
Talk it through