Multi-Unit Merchant Statement Audit Checklist: Effective Rate by MID and Location

What a multi-unit merchant statement audit is (and isn’t)

A multi-unit merchant statement audit is a document review across every merchant ID (MID) and location in the portfolio. It produces two things: a ranked effective-rate view of the fleet and a fee-layer decomposition of each statement, so finance can see which sites cost more to accept cards and why.

It is not a guest-pricing project, a processor bake-off as the first step, or a rewrite of front-of-house POS procedures. It is the statement-review step of the broader program on the restaurant payment processing optimization hub.

Configuration fixes — MCC coding, debit routing, enhanced transaction data, and downgrade causes — belong to the interchange optimization guide. This checklist shows where to look first; that guide explains what to change.

Why blended rates fail at 20+ units

Franchisee groups and PE-backed portfolio operators rarely run one clean merchant setup. Growth brings multiple LLCs, multiple MIDs per brand, and acquired stores that arrive on legacy contracts, legacy terminals, and whatever boarding choices the previous owner made.

A single blended fleet rate averages the well-configured stores with the expensive ones. It hides duplicated monthly fees, MCCs that differ by entity, markup tiers that vary by MID, and minimums firing on low-volume accounts. The number looks reasonable precisely because the outliers are diluted.

Controllers, CFOs, and VPs of operations need a location × MID × month view before any negotiation or configuration work begins.

How to calculate effective rate by MID and location

Effective rate is total processing fees divided by total card volume for the same period, calculated per MID. Where one location runs more than one MID, calculate each MID first, then roll them up to the location by summing fees and summing volume.

The numerator includes every fee line on the statement for that period: interchange, assessments, processor markup, authorization and per-item fees, batch fees, gateway fees, PCI charges, monthly minimums, statement fees, equipment rental, chargeback and retrieval fees, and any adjustments billed as processing.

The denominator is card volume for the same MID and the same period. Exclude cash and other non-card tender.

Do not average monthly percentages; months carry different volume, so a simple average over-weights slow months. Sum fees across the lookback window, sum volume across the same window, then divide. Use consecutive months — Basis Point Hospitality’s payments review commonly starts from six months of statements — so one-time charges don’t distort the result.

Build the working sheet with one row per MID per month: location, MID, month, card volume, total fees, effective rate, interchange, assessments, markup, ancillary fees, and notes.

Reading each statement: fee layers and pricing models

Every statement breaks into four layers. Interchange is set by the card networks and passed through; it is not negotiated as a rate, but what you pay within the schedule depends on how transactions qualify. Assessments are network fees and are largely fixed. Processor markup is the negotiable margin layer. Ancillary fees — PCI, minimums, batch, authorization, gateway, equipment, and statement fees — are small per store and material across a fleet. The merchant services fees guide covers how to read a merchant statement line by line.

The pricing model determines how much of that split you can see. Interchange-plus statements show pass-through costs and markup separately, which is why the payments hub treats it as the auditable model at multi-unit volume. Tiered or bundled statements let the processor define qualified, mid-qualified, and non-qualified buckets, so true cost sits inside categories you do not control. Flat-rate statements are simple to read but hide markup movement entirely. No model is crowned cheapest here; the audit comes first.

Then sort the fleet by effective rate, worst first. For each outlier, ask whether the gap is structural (card or channel mix) or actionable (markup, ancillary fees, or coding). Decomposition answers that; a blended quote cannot.

The portfolio checklist: what to confirm for every MID

Run these items for each MID and location, record the answer in the working sheet, then sort the fleet by effective rate.

1. Statements on hand for the full lookback window — six months where possible, with the exact window confirmed at the start — for every MID and entity, including acquired stores.

2. Effective rate calculated as total fees divided by card volume for the same period, summed across months rather than averaged.

3. Fee layers split into interchange, assessments, processor markup, and ancillary fees.

4. Pricing model identified (interchange-plus, tiered, flat, or other), and whether markup is visible on the statement.

5. PCI non-compliance or non-validation fees noted, including whether they recur month after month.

6. Monthly minimums or low-volume penalties flagged wherever they fire.

7. Batch, authorization, per-item, statement, gateway, and tokenization fees listed and checked for duplicates across MIDs.

8. Downgrade, non-qualified, or mid-qualified activity identified, with a downgrade report by reason code and location requested.

9. Card-present and card-not-present mix recorded, and channels confirmed as boarded and flagged correctly.

10. MCC verified per entity rather than assumed brand-wide.

11. Duplicate or orphaned MIDs, duplicate monthly fees, and equipment rental on hardware the group already owns identified.

12. Month-over-month rate creep checked where there is no matching change in mix.

13. Chargeback, retrieval, and adjustment fees separated from the underlying dispute losses.

14. A baseline saved before any change, so later recovery can be shown against the same method.

Where portfolio cost hides in the line items

PCI and non-compliance fees. Recurring non-validation charges often persist on acquired or low-volume stores. List them by MID and note whether they cluster on one entity or acquisition.

Monthly minimums. Minimums fire when a MID’s volume dips: seasonal sites, second MIDs for a separate channel, closed dayparts. If a low-volume MID keeps triggering one, ask whether that MID needs to exist.

Batch, authorization, and per-item fees. Per-transaction charges weigh more when tickets are small or transaction counts are high. Batch and settlement fees also duplicate across MIDs that could settle together.

Downgrades. On tiered statements, processor-defined buckets hide real cost. On any model, late batching, missing data, tip-after-authorization timing, and keyed fallback surface as expensive qualification. Flag the lines, request a downgrade report by reason code and location, and take causes and fixes to the interchange optimization guide.

Channel mix. Counter and drive-thru sales are card-present; app, online, and phone orders are card-not-present and qualify differently. A mis-flagged channel inflates cost with no change in sales. Marketplace volume usually sits in remittances, not on the merchant statement — review it through the third-party delivery commission audit.

MCC coding and duplicates. Verify the MCC on each statement and entity; acquisition fleets often carry mixed codes, and the wrong code places transactions on the wrong interchange schedule. Look for stores with more than one active MID, MIDs orphaned after a remodel or ownership change, gateway or tokenization fees that duplicate processor charges, and equipment rental on owned terminals.

Rate creep. Compare each MID against itself across months. If markup, the ancillary fee list, or the effective rate stepped up without a corresponding shift in card or channel mix, that MID goes on the review list.

Suggested sequence before anyone renegotiates

1. Collect statements for every MID and entity, including acquired stores, for the agreed lookback.

2. Calculate effective rate per MID and location, then rank the fleet.

3. Decompose each statement into interchange, assessments, markup, and ancillary fees.

4. Run the checklist items, noting duplicates, PCI charges, minimums, equipment rental, and channel flags.

5. Request a downgrade report by reason code and location where available.

6. Save the baseline before any configuration change or commercial conversation.

7. Only then fix qualification and configuration issues and address markup and fees. Many groups can do this inside the existing processor relationship once pricing is transparent; switching processors is a conclusion the analysis may reach, not the starting assumption.

What this checklist does not change

Guest checkout, menu, recipes, staffing models, schedules, and service standards stay the same by default; the work stays in statements, MID setup, and fee layers.

Guest-facing pricing, such as cash discounting or surcharging, is a separate decision and is not required to improve effective rate; see the cash discount vs surcharging decision framework.

Basis Point Hospitality runs this review free to the operator at every stage; the vendors and programs we bring in compensate us. To see effective-rate spread across your locations, bring recent statements for every merchant ID to a free diagnostic.

Continue the review