Free Merchant Statement Review

How a merchant statement review works

A useful merchant statement review turns a dense monthly report into a set of decision-ready questions. It starts with what is actually visible: sales volume, transaction count, card-present versus keyed or online activity, deposits, chargebacks, and the fee lines shown for that period. It then separates those observations from items that cannot be responsibly assumed without the merchant agreement, equipment paperwork, or the processor’s written answer.

ProcessRite’s role is to help a business organize the statement, identify the questions that matter, and connect the fee picture to the checkout workflow. It is not a promise of savings, a processor quote, legal advice, or a substitute for reading a contract. Final pricing, account approval, equipment terms, funding timing, and any change decision are determined by the applicable provider and the merchant’s agreement.

What to bring to a review

• A recent complete merchant statement, including fee-detail pages rather than only the first summary page.
• Approximate monthly card volume, transaction count, and average ticket.
• How customers pay: countertop, mobile, keyed, invoice, recurring, ecommerce, delivery, or phone.
• The processor agreement, equipment lease or purchase paperwork, and any gateway or POS invoices if available.
• Questions about deposits, support, device issues, refunds, chargebacks, or reporting.

Understanding the fee layers without oversimplifying them

Merchant statements can combine several kinds of charges. A fee label alone does not prove whether a charge is appropriate or avoidable; the right interpretation depends on the account, card mix, payment channel, agreement, and services actually in use. Still, grouping charges helps prevent an owner from comparing only an advertised percentage while missing fixed, software, equipment, or operational costs.

PCI DSS is a security standard maintained by the PCI Security Standards Council. A merchant that outsources payment processing still has responsibilities to protect its own environment and validate compliance as applicable; the exact requirements depend on how payment data is handled. For primary guidance, consult the PCI SSC merchant resources and your acquiring bank or payment provider rather than relying on a statement label alone.

Effective rate: a useful starting ratio, not a verdict

Effective rate is a simple way to see the month’s total processing-related charges relative to the card sales reported for that month:

Effective rate = total processing-related charges ÷ gross card sales × 100

This ratio helps an owner ask better questions because it puts a dollar total beside the volume processed. It does not by itself tell you whether an account is expensive, whether a fee is improper, or what a different provider will charge. Card mix, debit versus credit usage, rewards cards, keyed or online transactions, surcharge or cash-discount programs, refunds, disputes, and non-processing services can all change the result.

Hypothetical example — not a quote or savings claim

Imagine a business processed $40,000 in gross card sales in a month. Its statement shows $1,120 in transaction-related, service, and other processing charges that the owner has chosen to include in the review. The arithmetic is $1,120 ÷ $40,000 × 100 = 2.80%. The next step is not to declare 2.80% good or bad. It is to identify what made up the $1,120: card mix, interchange/network items, provider margin, per-transaction charges, monthly platform fees, equipment, and exception items.

Use a consistent definition when comparing months. If one month includes a one-time chargeback fee or a new-device purchase and another does not, note that difference instead of treating the ratios as like-for-like. A comparison becomes meaningful only when the activity and included costs are clearly documented.

Common statement terms worth translating

A practical statement-comparison method

Compare periods and proposals in a worksheet, not from a single headline rate. Start by matching like periods and documenting assumptions. A restaurant with tips and online orders, a contractor invoicing from the field, and a retail store with mostly tap transactions should not expect identical statement patterns.

1. Match the operating period. Record dates, gross card sales, transaction count, refunds, disputes, and unusual events.
2. Separate transaction costs from services. Keep interchange/network, provider pricing, equipment, software, and exception items in distinguishable categories.
3. Map costs to workflows. Connect the statement to POS terminals, online checkout, invoicing, recurring billing, tips, delivery integrations, and staff permissions.
4. Read the agreement beside the statement. Highlight pricing descriptions, term length, cancellation language, equipment ownership, and support commitments that need clarification.
5. Ask for written answers. A phone explanation can be helpful; a written breakdown is easier to compare and preserve.

For broader setup questions, see ProcessRite’s credit card processing guidance, the merchant services consultation, and the switching checklist. These are related decisions, but a statement review should remain anchored to the business’s own current documents and workflow.

What the statement can answer — and what still needs confirmation

A monthly statement is evidence of a period of activity, but it is not the whole account history. Treat it as one document in a small decision file. This distinction helps a merchant avoid two common mistakes: assuming every visible fee can be removed, or accepting a new proposal without knowing whether it includes the services the business depends on.

When a number or term remains unclear, use a precise question: “Please identify this fee, the document that governs it, whether it is recurring or event-based, and whether it would change if our current workflow stayed the same.” Keep the response with the documents you compare. That is more useful than relying on a verbal assurance or trying to infer a contract from one line item.

A low-risk review sequence

1. Make a secure copy of the current statement and agreement.
2. List every place payment data enters the business: terminal, phone, invoice, ecommerce, subscription, or integration.
3. Reconcile volume and transaction counts to an operating report for the same period.
4. Mark unfamiliar fees and ask for a written explanation before deciding whether they are relevant or avoidable.
5. Only then compare a replacement proposal on the same usage assumptions and build a transition checklist.

Red flags to investigate and questions to ask before switching

A red flag is a reason to investigate, not proof of wrongdoing. Statements are complex, and an unfamiliar label may have a valid explanation. The risk is making a major change before the business understands the current account, the replacement proposal, and the operational dependencies.

• A total that cannot be reconciled to the statement period’s sales volume and transaction activity.
• Recurring equipment, software, or service charges the business cannot identify or no longer uses.
• Pricing language or fee categories that are not clear in the agreement or provider documentation.
• A proposal that emphasizes one rate while leaving out per-item, monthly, equipment, gateway, support, or exception costs.
• Pressure to change without reviewing POS integrations, online checkout, invoices, subscriptions, deposits, or staff workflow.
• Unclear ownership or return terms for terminals, accessories, or leased equipment.

Ask these questions before changing processors

1. Which payment channels will be affected on day one?
2. What happens to existing terminals, POS settings, online checkout, invoices, recurring payments, gift cards, and reporting?
3. What pricing model, fees, term, equipment terms, and support obligations are documented in writing?
4. What should the business expect for onboarding, testing, settlement, refunds, and dispute workflow?
5. Who is responsible for account setup, hardware configuration, staff training, and escalation if something fails?
6. What information needs to be preserved before a transition, and what timeline avoids a checkout interruption?

If a business is considering a Clover setup, product capabilities and compatibility should be confirmed against Clover’s official product FAQs and the chosen provider’s current offer. Hardware or platform features should never be assumed from a merchant statement.

Merchant statement review FAQs

Can a statement review guarantee lower processing costs?

No. A review can make the current fee picture and questions clearer. It cannot guarantee pricing, approval, savings, funding, contract outcomes, or another provider’s terms.

Should I send an unredacted statement?

Only share business-level information necessary for the review. Do not send cardholder data, bank login credentials, full bank-account numbers, Social Security numbers, or passwords through the website form. If a document contains sensitive information, remove or redact it before sharing.

Why do two processors quote different rates?

Quotes may use different pricing structures and may include different payment channels, transaction assumptions, fixed fees, equipment, software, and contract terms. Ask each provider to show the full scope in writing and compare like-for-like assumptions.

What is the best next step if I cannot read my statement?

Gather the complete recent statement, agreement, and a short description of how the business takes payments. Use the existing review form below to request a practical discussion. ProcessRite can help organize the questions before the business signs, switches, or changes equipment.