Merchant Statement vs. Processing Proposal: Why They Are Not an Apples-to-Apples Comparison
Expert Verified & Fact-Checked
From the Desk of: Chris DuPont, founder of Merchant Statement Analysis, with 17+ years of merchant processing experience.
The Focus: A current merchant statement and a new processing proposal use different structures and assumptions. Learn why direct line-by-line comparison can produce the wrong conclusion
Our Approach: Separates historical processing volume, transaction count and average ticket, card mix/qualification, and the proposed pricing model and fixed fees so the reader can distinguish transaction or account changes from processor pricing changes without assuming that every unusual line item is an error.
A merchant statement shows what happened last month.
A processing proposal shows what someone says would happen under new pricing.
Those documents are related.
They are not built for the same purpose.
A Statement Shows History; a Proposal Shows an Offer
The merchant statement contains actual activity.
It may show:
- volume
- transaction count
- interchange categories
- network fees
- processor charges
- fixed monthly fees
A proposal may show only:
- markup
- transaction fee
- monthly fee
- estimated savings
Comparing the two line by line can be difficult because the categories may not match.
The Categories May Not Line Up
A current processor may bundle several charges into one line.
A proposal may separate them.
Or the reverse can happen.
That means a fee missing from the proposal may not truly be "free."
It may simply be included somewhere else.
The same issue applies when comparing tiered pricing with interchange-plus.
The structures are fundamentally different.
Pass-Through Costs Can Be Presented Differently
A proposal may show processor markup separately while assuming interchange and network costs will pass through.
The current statement may bundle more of those costs together.
If someone compares only the visible processor markup, the proposed pricing can look dramatically cheaper even though both accounts still carry underlying card costs.
Savings Claims Depend on Assumptions
A savings estimate usually assumes the merchant's activity remains similar.
That means assumptions about:
- volume
- transaction count
- card mix
- payment channel
- refunds
- average ticket
matter.
If those variables change materially, the actual savings can change too.
Card Mix Must Be Carried Across Fairly
This is one of the most important parts of statement-based proposal analysis.
If the current statement contains expensive commercial cards, those cards do not disappear simply because a new processor quotes lower markup.
A fair proposal should carry the merchant's activity profile forward.
Otherwise, the estimate can confuse underlying cost with processor savings.
Why Professional Quote Analysis Requires Translation
The real work is not matching identical fee names.
It is translating:
current statement economics
into:
proposed pricing economics
using consistent assumptions.
In statement reviews, this is where simplistic comparisons often go wrong.
A well-designed proposal can still be based on weak assumptions.
Put the Quote Against the Same Merchant
A Strong Proposal Shows Its Assumptions
A savings proposal becomes more credible when the merchant can tell what was carried forward from the current statement.
Why This Matters to an ISO or Agent
A proposal is strongest when the savings story can be explained in plain language.
Questions a Merchant Should Be Able to Answer From the Proposal
A useful proposal should make several points clear without requiring the merchant to reverse-engineer the math:
What to Look at Next
When those pieces do not line up, that is when a statement deserves closer review.
MSA can evaluate the account in context and show where the cost is actually coming from.
How to Read This Issue in Context
For Merchant Statement vs Processing Proposal, a credit card processing fees comparison is strongest when the merchant’s historical activity is held as constant as possible while the pricing variables that changed are isolated. Start by comparing historical processing volume with transaction count and average ticket. Then review card mix/qualification and the proposed pricing model and fixed fees to determine whether the result is being driven by merchant activity, pass-through cost, processor pricing, or another service.
For Merchant Statement vs Processing Proposal, a multi-period view is usually stronger than a one-month snapshot. If the statement shows a change in historical processing volume while there is no meaningful change in the proposed pricing model and fixed fees, the explanation points in a different direction than a month where the merchant’s activity is stable but the pricing line changes. That distinction keeps the review tied to evidence rather than to a quick assumption.
A Practical Statement Checklist
- For Merchant Statement vs Processing Proposal, compare historical processing volume across the relevant statement periods.
- Separate transaction count and average ticket from charges that are billed on a different basis.
- Check whether card mix/qualification changed enough to explain the movement being reviewed.
- Identify the statement label and billing basis for the proposed pricing model and fixed fees, and confirm whether the statement provides enough detail to classify it confidently.
What This Does Not Prove
Nothing about Merchant Statement vs Processing Proposal should be diagnosed from one unusual line item alone. Compare historical processing volume, transaction count and average ticket, card mix/qualification, and the proposed pricing model and fixed fees first. If the relationship still does not make sense, verify the processor’s definitions, agreement terms, applicable network rules, and the merchant’s operating details before calling the account overpriced.
Treat Merchant Statement vs Processing Proposal as a reconciliation exercise, not a guessing exercise. If the statement cannot show why a charge appears or why a number moved, preserve that uncertainty and seek the supporting agreement, processor detail, or another statement period.
How This Affects a Quote or Review
A review of Merchant Statement vs Processing Proposal becomes actionable only when the same logic reaches the proposal. Control for historical processing volume and card mix/qualification, and distinguish the proposed pricing model and fixed fees from transaction count and average ticket. That keeps normal merchant activity from being credited to—or blamed on—the proposed pricing.
For Merchant Statement vs Processing Proposal, use actual historical activity, show every material assumption, and reconcile the comparison back to the statement totals before presenting a savings conclusion.
Primary Sources to Check
Rates, network rules, and compliance requirements can change. Verify the current primary documentation before publication and before relying on a specific rule or amount.
