Our Blog

Monthly Statement Example for Merchants

June 2nd, 2026

A lot of business owners do not look closely at their processing statement until the total feels wrong. Usually that happens after a busy month, when sales were strong but the deposit still came in lighter than expected. A good monthly statement example can help you see where the money actually went and whether your processor is charging fairly.

For restaurants, bars, breweries, and retail stores, this matters more than most providers admit. Card volume is high, ticket sizes vary, and small rate changes can add up fast over a month. If your statement is hard to read, that is not a small annoyance. It is a cost-control problem.

What a monthly statement example should show you

A processing statement is supposed to explain three things clearly: how much you processed, what fees were charged, and what you actually kept. That sounds simple, but many statements bury key numbers under processor jargon, tier labels, and line items that make comparison difficult.

A useful monthly statement example breaks the page into a few basic sections. You will usually see gross card sales, chargebacks or refunds, interchange and assessment costs, processor markup, monthly account fees, and net deposits. Depending on the provider, you may also see PCI fees, batch fees, gateway charges, statement fees, equipment charges, or annual fees divided into monthly line items.

The goal is not to memorize every code on the statement. The goal is to know which charges are fixed, which are variable, and which ones deserve a second look.

A simple monthly statement example

Let’s say a neighborhood restaurant processes $85,000 in card sales for the month. Out of that total, $62,000 is credit card volume and $23,000 is debit card volume. The statement might show interchange and card brand assessments totaling $1,615, processor markup totaling $510, monthly and account-related fees totaling $145, and chargeback or refund-related costs of $30.

That puts total fees at $2,300 for the month. The effective rate, which is total fees divided by total processed volume, comes out to about 2.71%.

At first glance, 2.71% may or may not be a problem. It depends on the card mix, the type of pricing plan, whether a lot of rewards cards were used, and whether the business is keyed-in, in-person, or split between both. A full-service restaurant with a lot of premium credit cards will usually land higher than a quick-service counter operation with lower average tickets and more debit use.

That is why a monthly statement example only becomes useful when you know how to question the numbers behind it.

The sections that deserve the most attention

Sales volume and deposit totals

Start with total card volume and compare it to what hit your bank account. Your statement may show gross sales, then subtract fees before deposit, or it may deposit gross funds and pull fees later. Either model can work, but it needs to be consistent. If deposits are hard to reconcile, your accounting team wastes time every month, and the confusion can hide billing issues.

Interchange and assessments

These are the wholesale costs tied to card types and card brand rules. In most cases, your provider does not control these rates directly. What they do control is how clearly they pass them through and how much markup they add on top.

If your statement shows interchange in a transparent way, that is a better sign than a statement that hides everything inside vague buckets like qualified, mid-qualified, and non-qualified. Tiered pricing is not always wrong, but it is much harder to audit.

Processor markup

This is where many merchants overpay. Markup can appear as a percentage, a per-transaction fee, or both. It can also be buried across several lines, such as authorization fees, transaction fees, service fees, and platform fees. If you cannot identify the processor’s actual margin, you cannot judge whether the deal is competitive.

Monthly fixed fees

These are the charges that keep showing up whether you process one transaction or ten thousand. Common examples include PCI compliance fees, gateway fees, account fees, statement fees, POS support charges, and noncompliance fees. Some are legitimate. Some are outdated. Some are small enough to ignore individually but expensive in total.

Red flags inside a monthly statement example

One red flag is a statement that gets longer every few months because new fees quietly appear. Another is a low quoted rate that does not match the effective rate you are actually paying. If you were sold on 1.79% but your statement consistently lands above 3%, something needs to be reviewed.

Watch for duplicate charges as well. A business may be paying for a gateway through one provider, support through another, and equipment services through a third without realizing there is overlap. That is common when a merchant has switched systems over time and no one cleaned up the billing stack.

Another issue is unexplained rate increases. Some processors raise markup without much notice, especially after an introductory period. If your sales volume stayed stable and card mix did not shift much, but total fees climbed anyway, your statement should tell you why. If it does not, that is a problem.

Why effective rate can help – and where it falls short

The effective rate is one of the fastest ways to evaluate a statement. You take total fees and divide them by total card volume. It gives you a simple percentage that is easy to compare month to month.

But effective rate is not the whole story. A business that runs mostly debit transactions should generally expect a lower rate than one that takes a heavy mix of rewards and corporate cards. A brewery with strong in-person EMV volume may look very different from a catering business that keys in cards for events. If someone compares those businesses with one flat target rate, the analysis gets sloppy.

That is why the right question is not just, what is my effective rate? It is also, does this rate make sense for my card mix, my operation, and my pricing plan?

What restaurant and bar owners should check first

Hospitality operators often have statement issues that are easy to miss because the business is moving too fast. Tip adjustment workflows, pre-authorizations, bar tabs, and occasional keyed transactions can all affect qualification and fees. If your POS and payment setup are not aligned, you can end up paying more without realizing the source.

For example, outdated terminals, poor batching habits, or unnecessary manual entry can increase costs. So can a POS system that was never set up correctly for your environment. This is one reason statement analysis should not happen in isolation. Sometimes the fee issue is really a workflow issue.

For Denver-area operators especially, local support matters here. If there is a problem with the setup, you need someone who can look at the statement, the POS configuration, and the day-to-day process together instead of blaming one piece at a time.

How to review your own statement without getting buried in details

Start with three months, not just one. A single statement can be distorted by seasonality, a holiday rush, a chargeback spike, or a one-time fee. Three months gives you a cleaner view.

Then pull out five numbers: total volume, total fees, effective rate, total fixed monthly charges, and processor markup if it is visible. If markup is not visible, that alone tells you something about transparency.

Next, circle any line items you do not recognize. If your provider cannot explain a fee in plain English, that is a warning sign. The same goes for pricing labels that sound polished but do not tell you what you are actually paying.

Finally, compare the statement to how your business really operates. If almost all of your sales are card present and dipped or tapped, but the fees suggest a lot of higher-risk volume, there may be a setup problem or a pricing issue worth fixing.

When a statement review usually saves the most money

The biggest savings usually show up when a merchant has been with the same processor for years, has layered technology from multiple vendors, or accepted the original pricing without a later review. That is especially true for growing businesses. What made sense at one location with modest volume may not fit a multi-lane retail store or a busy bar anymore.

A proper review can uncover overpriced markup, unnecessary monthly fees, poor POS-payment integration, or an account structure that no longer matches the business. Rocky Mountain Credit Card Processing often sees this with hospitality operators who were sold a system quickly but never got the hands-on review needed after the business changed.

A statement should not feel like a puzzle your provider hopes you never solve. It should tell a clear story about your costs and give you confidence that your setup still fits your business.

If you have been looking at the same charges month after month and assuming they must be normal, that is usually the right time to ask better questions. A good monthly statement example is useful, but your own statement tells the real story – and that story is worth reading before another expensive month rolls by.