How to Read a Merchant Processing Statement

By Raied Muheisen | Reviewed June 18, 2026

A merchant processing statement is the best place to begin when a business wants to understand card costs, evaluate a proposal, or investigate an unexpected change. It is also easy to misread. Statements combine sales activity, interchange or pricing categories, processor markup, network charges, monthly fees, adjustments, chargebacks, and services that may be billed under unfamiliar names.

This guide explains a repeatable statement-review process. It does not assume that one pricing model is automatically best, and it does not reduce the analysis to a single “effective rate.” The purpose is to connect every meaningful charge to the transactions, service, contract, or exception that caused it.

What to collect before you start

Use at least three representative statements; twelve months is better for a seasonal business. Collect separate invoices for the POS software, gateway, equipment, security program, ecommerce platform, or third-party applications. Find the merchant agreement, fee schedule, recent pricing notices, and equipment agreement. A statement can only show charges that appear on that statement.

Record the business name, merchant account or location, statement period, processing volume, transaction count, refunds, chargebacks, average ticket, and payment channels. Remove or securely obscure sensitive account and cardholder information before sharing a statement for analysis.

Step 1: reconcile sales and deposits

Compare gross card sales with the POS or order system. Then account for refunds, voids, chargebacks, tips, adjustments, and timing differences. Compare the statement’s net activity with bank deposits. Some providers deduct fees daily; others deposit gross sales and debit fees monthly. Weekend, holiday, cutoff, and batch timing can place a transaction in a different deposit or statement period.

Do not begin a pricing comparison until the activity reconciles closely enough to explain differences. A missing batch, duplicate transaction, delayed refund, reserve, or adjustment can look like a pricing problem when it is actually an operational issue.

Step 2: identify the pricing presentation

An interchange-plus statement may show interchange categories and network costs separately from the processor’s percentage and per-item markup. A flat-rate statement may present a combined percentage and transaction charge with fewer underlying details. A tiered statement may group transactions into qualified, mid-qualified, and non-qualified categories. Subscription models may combine a monthly membership with transaction charges.

The statement format does not guarantee the commercial model is transparent. Look for the actual markup, fee schedule, and rules in the agreement. Two statements described as interchange-plus can still differ in markup, monthly charges, pass-through treatment, and additional services.

Step 3: separate costs into useful groups

Transaction-dependent costs

These change with sales volume, transaction count, card, entry method, channel, ticket size, and other transaction characteristics. Depending on the pricing model, the statement may show interchange, network assessments, processor percentage markup, per-item authorization or transaction charges, debit fees, keyed or card-not-present costs, and cross-border charges.

Account and monthly costs

Common examples include account, statement, platform, gateway, PCI program, security, customer service, minimum, reporting, or monthly software charges. The name matters less than the written description and whether the service is required. Annual fees may appear in only one month, which is why a full-year review matters.

Exception and event costs

Chargebacks, retrieval requests, ACH returns, rejected batches, voice authorizations, address verification, tokenization, account updates, expedited funding, and special support can generate separate costs. Review frequency as well as price. Repeated exception fees may reveal a workflow or fraud-control problem worth fixing.

Costs billed elsewhere

POS applications, ecommerce plugins, terminal leases, device protection, online ordering, loyalty, gift cards, and specialized gateways may be billed by another company. Include them when comparing the complete payment system, even if they are not processor revenue.

Step 4: calculate—but do not worship—the effective rate

A common calculation is total processing-related fees divided by processed card sales. For example, $1,000 in relevant fees divided by $40,000 in card sales equals 2.5 percent. This is a useful high-level indicator when the numerator and denominator are consistent.

It is not a universal measure of provider markup. Interchange and network costs vary with card and transaction characteristics. Per-item fees affect a low-ticket business differently from a high-ticket business. Annual charges can distort one month. Refunds change the denominator, and separate invoices may be omitted. Use the effective rate to spot trends and compare modeled total cost—not to declare that every difference is negotiable processor profit.

Step 5: find the processor-controlled markup

On a clear interchange-plus statement, identify the processor percentage markup and per-item markup, then add monthly and additional provider fees. On flat-rate pricing, the provider’s margin is embedded in the combined rate, so it cannot be isolated from the statement in the same way. On tiered pricing, qualification rules can materially affect cost and may be difficult to reconstruct without detail.

Ask the provider to mark every charge it controls and every charge it describes as pass-through. Request the source and formula for each. If a fee name is ambiguous, obtain the contractual description rather than accepting an informal explanation.

Step 6: compare multiple months

Create a worksheet with one row per month and columns for volume, transaction count, average ticket, refunds, chargebacks, total fees, effective rate, monthly fees, annual or event fees, and notes. Add channel mix if available. A change in rate may be explained by more keyed transactions, different card mix, lower average ticket, or an annual fee. It may also reveal a markup change or new charge.

Compare the statement against price-change notices and the agreement’s amendment provisions. Ask when a new fee began, whether it is optional, and what service it covers. Save the written response.

How to model a competing proposal

Give each provider the same statement data and transaction profile. Require the estimate to include every percentage, per-item fee, monthly charge, annual fee, gateway, software, equipment obligation, and implementation cost. Ask the provider to show a line-by-line calculation for an actual month.

If the proposal uses interchange-plus, do not compare only the markup with the current total rate. Add the underlying costs and all provider fees. If it uses flat-rate pricing, apply the correct rate to each channel and include subscriptions and exceptions. Compare a normal month, a peak month, and the full first-year total.

Questions every statement review should answer

• Do processed sales, refunds, and deposits reconcile?
• Which fees vary with volume and which are fixed?
• Which charges are processor-controlled, pass-through, third-party, or unclear?
• Are annual, minimum, security, or software fees included in the comparison?
• Did pricing or transaction mix change?
• Are exception fees signaling an operational problem?
• Can a competing proposal reproduce the calculation using the same activity?
• Do the statement, fee schedule, and agreement agree?

Common statement-review mistakes

• Using only one month and missing annual or seasonal effects.
• Dividing fees by gross sales without accounting for refunds or excluded activity.
• Comparing a processor markup with a total bundled rate.
• Ignoring per-item charges in a high-transaction business.
• Leaving software, gateway, or equipment invoices out of total cost.
• Assuming every network or interchange-related line is negotiable markup.
• Sharing an unredacted statement with sensitive information.
• Accepting projected savings that cannot be reproduced from written terms.

Frequently asked questions

What is a good effective processing rate?

There is no universal target. The result depends on transaction mix, card types, average ticket, channels, services, and pricing model. Compare like periods and investigate the components.

Why did the effective rate rise when sales fell?

Fixed monthly fees and per-item charges become a larger percentage of lower volume. Card mix, ticket size, refunds, and annual charges may also change the result.

Can a statement reveal the contract term?

Usually not completely. Review the merchant agreement, program guide, amendments, and equipment documents for term, renewal, and cancellation obligations.

Should PCI-related fees be ignored because every merchant has security duties?

No. Merchants have payment-data responsibilities, but provider program fees, noncompliance charges, and services should still be understood and compared. Use the official PCI SSC merchant resources for authoritative guidance.

What is the fastest way to compare two statements?

Reconcile activity, group costs consistently, calculate total cost and effective rate, identify fixed and transaction-dependent fees, and model the same month under both written schedules.

Bottom line

A merchant statement becomes useful when every major number is connected to a transaction, contract term, service, or exception. Reconcile first, group fees consistently, examine multiple months, and make every competing provider calculate the same real activity. A savings claim that cannot be reproduced is marketing, not analysis.

Next, read How to Choose a Merchant Services Provider, visit the Comparisons hub, and review how RitePicks handles commercial relationships.

Turning the review into an operating control

A statement review should not occur only when a salesperson promises savings. Assign one person to save statements and related invoices, reconcile deposits, record pricing notices, and investigate unexplained changes. Use a consistent monthly worksheet so a new fee or shift in transaction mix becomes visible. Document the resolution and retain the supporting email, contract section, or credit.

Connect findings to operations. High keyed-entry volume may indicate a broken terminal or staff workaround. Repeated chargebacks may require clearer descriptors, delivery evidence, cancellation procedures, or fraud controls. Frequent batch problems may point to training or connectivity. Rising gateway charges may reflect duplicate services. The statement is therefore both a cost record and a signal about payment workflow.

Controls for multiple locations

For multiple merchant accounts, use the same chart of fee categories and reconcile each location separately before combining totals. Confirm that pricing, software, and equipment billed at the corporate level are allocated consistently. Compare locations only after accounting for ticket size, channel, card mix, and volume; otherwise a genuine operating difference may be mistaken for provider pricing.

What to document after a provider review

Keep the model used for every proposal, the transaction assumptions, complete fee schedules, equipment terms, contract versions, implementation promises, and the person who supplied each answer. Add renewal and notice dates to a calendar. If the business changes providers, compare the first three live statements with the approved model and investigate variances immediately rather than waiting until the end of the contract.

Statement review worksheet

Continue with the processing-fee guide and the provider evaluation checklist.