For MSPs · November 2026

MSP QBR Checklist: Reviewing Card Processing Fees

A client’s card processing statement shows what the systems you manage cost the business each month. Here’s how to turn those findings into an action list for your quarterly business review.

By Gary Rutledge · Updated · 5 min read

A quarterly business review works when it shows the client something they couldn't see on their own. Uptime reports and patch counts confirm the systems are running. They rarely surprise anyone. A client's card processing statement can, and it shows what several of the systems you already manage are costing the business every month.

Much of what a business overpays for card processing comes from setup rather than the rate: how sales are entered, when batches close, what data goes with a business card sale, how a failed recurring charge is retried. Those are your systems. This guide covers how to bring the processing statement into an assessment or QBR: what to ask for, what to look for, how to present it, and how to keep it from turning into a sales pitch.

Key takeaways

  • The processing statement is a technology report as much as a financial one. Downgrades, retry fees and compliance fees usually trace back to configuration.
  • Ask for permission and for one to twelve recent statements. One shows the pricing; a year shows the annual fees and the trend.
  • Sort every finding by who fixes it: your team, the processor, or the owner in a negotiation.
  • Present three findings, not thirty, each with its monthly cost and its fix.
  • Check again after the fix. The next statement shows whether it worked.

Why the statement belongs in a QBR

Most owners read their processing statement for one number, the total, and file the rest. Nobody's job is to read the detail. Meanwhile the statement records, line by line, the cost of decisions made in systems you manage: the point-of-sale configuration, the payment gateway, the web store's checkout, the billing software, the batch schedule.

That makes it unusually good QBR material. It's specific to this client, it's in dollars, and it often contains a fix the client didn't know existed. A finding like "your online orders are billed at a higher rate because the checkout isn't sending address verification" is a ticket your team can close, with a saving the owner will see on the next statement.

What to ask for

For a first review, use the line-by-line guide to reading a merchant statement to locate the pricing summary, fees, and notices.

What to look for

Group what you find by who can fix it. It keeps the review useful, and it keeps your team's work separate from anything that belongs to the processor or the owner.

Your team can fix:

The processor should explain or fix: fees that don't match the agreement, network fees billed above what the networks charge, and services the client no longer uses.

The owner negotiates: the markup, monthly and annual fees, and the terms of the agreement.

The technology fixes are covered in more detail in seven card processing costs your IT team can address.

How to present it

Keep it to one page in the QBR deck:

  1. What the client paid for card processing over the period, and how much of it was the card networks' cost versus the processor's price.
  2. The three findings that cost the most each month, each in dollars, with the system it traces to and the fix.
  3. Who does what next: the tickets your team will open, the questions for the processor, and anything for the owner to raise at renewal.

Leave the full line-by-line detail as an appendix for whoever wants it. Owners act on three clear findings; they file a list of thirty.

Keeping it from becoming a sales pitch

If your firm also resells processing, say so up front, and lead with the fixes rather than a rate quote. A review that ends in "switch to us" reads as a sales call, and the owner will weigh every finding accordingly. A review that ends in three fixes, two of them done by your team, earns the trust that makes any later conversation easier.

Don't promise a figure before the statements are read. What a statement supports varies widely between processors and pricing models, and some questions can only be answered by documents the statement doesn't include.

The cadence

Where Statement Forensics fits

Statement Forensics audits processing statements line by line, and gives you the material for that QBR page. Every figure is reconciled to the statement's own printed totals. The audit separates the card networks' cost from the processor's price, names downgrades with their likely causes, counts network fees for retries and authorizations, and checks debit lines network by network. You get two reports: one for your team with every working figure, and one in plain English for the client. Statements are deleted when the reports are delivered.

We don't sell processing, have no processor, ISO or platform affiliation, and take no residuals or referral fees from processors. To see it on one client, send a recent statement, with the client's permission, to audit@statementforensics.com, or ask for the sample report first. There's more in the MSP brief.

See a sample audit report for your QBR

Frequently asked questions

Why should an MSP look at a client's card processing statement?

Because much of what a business overpays for card processing comes from configuration: late batches, missing data on business card sales, checkouts without address verification, aggressive retries and missing recurring-payment references. Those are systems an MSP already manages.

How many statements does a review need?

One recent statement shows the pricing and most of the fees. Twelve months adds annual fees, price increases and seasonal patterns, which makes it the better baseline.

Is it safe to collect clients' processing statements?

Get the client's permission, and handle the statements like any other sensitive record: they carry merchant numbers, deposit account details and sales. Keep them only as long as the review needs them.

What if the review finds the pricing itself is high?

Give the owner the finding and the questions to ask. The markup and fees are set by the client's agreement, so the owner raises them with the processor, ideally with the line-by-line evidence in hand.

About the authorGary Rutledge built Statement Forensics after 35 years in banking risk, processing, acquiring and payment facilitator operations. Beech Edwards LLC has no processor, ISO or platform affiliation, takes no residuals or referral fees, and has nothing to sell you after the report.

Find out what you’re really paying to accept cards.

Independent, plain-English statement audits. No processing sold, nothing to switch you to. Statements are deleted on delivery.

Request an audit