Contract vs. Statement: The Comparison Nobody Has Time to Do

There is a document that says what you agreed to pay. There is another that says what you paid. In most businesses these two have never been in the same room.

It is not negligence. The merchant agreement is a 20-page schedule written in the vendor's vocabulary, the statement is a 14-column table written in a different vocabulary, and reconciling them means matching perhaps 40 charge codes against perhaps 30 contract terms that use other names for the same thing. It is a day of work for a person who knows what they are looking at, repeated monthly, forever. So it never happens, and every vendor pricing model quietly assumes it never happens.

The four ways a statement departs from its contract

1. The rate that simply is not the rate

The agreement says 0.25 percent plus 10 cents. The statement bills 0.32 percent plus 12 cents. There is no story here and no interpretation required. It is the least common of the four and the easiest to win, because there is nothing to argue about once both documents are on the table.

2. The charge that has no contract term at all

Far more common. A line appears with a name that sounds official and appears nowhere in the agreement: a technology fee, a network access fee, a service enhancement charge. It survives because contracts protect the prices they name and say nothing about prices that did not exist when they were signed. The processing-industry catalog of these is in The Junk Fees Hiding on Your Processing Statement.

3. The pass-through that is not passing straight through

Your agreement says interchange and assessments are billed at cost. The statement bills them at cost plus a shave. This is the hardest to see by eye, because it requires knowing the published network rate for each category and comparing it to what appeared on your bill. It is also frequently the largest single number in an audit, precisely because it is invisible.

4. The tier or discount that lapsed

Volume tiers, promotional rates and negotiated discounts carry dates. Vendors remember those dates. When a tier lapses, nothing on the statement announces it. The line looks identical, the rate is different, and the change is a number in the middle of a column that has never been read.

What a machine comparison actually does

Both documents go in. The comparison normalizes the vocabulary first, because the same charge is called three things across an agreement, a schedule A and a statement, and a naive string match finds nothing. Then, per charge, it lines up the contracted term against the billed amount and reports one of four states: matches, differs, no contract term found, no charge found.

Rounding is where the money hides

A rate difference of 0.02 percent is invisible on a statement and rounds to nothing on a line. On 4 million dollars of annual volume it is 800 dollars, and there are usually several of them.

This is why drift has to be compared at full precision rather than at the two decimal places a statement prints. A comparison that rounds before it compares will report agreement on every line that is quietly wrong, which is the exact set of lines the exercise exists to find. Small differences are reported as small differences, with the annualized figure beside them, and the reader decides whether an 800 dollar line is worth an email.

Doing it by hand, if you would rather

The comparison is mechanical, and a determined person with a spreadsheet can run it. The sequence:

1. Pull the pricing schedule out of the agreement, including every amendment. Amendments are where the surprises live.
2. List every charge on one recent statement, with its rate, its per-item amount and its total.
3. Match them by meaning, not by name, and write down the ones that will not match.
4. For each pass-through category, compare the billed rate against the current published network table.
5. Annualize every difference before deciding what is worth raising. Monthly numbers make everything look trivial.

Then do it again next month, because a single comparison fixes a moment and the drift resumes immediately. That is the argument for continuous monitoring rather than an annual project.

Frequently asked questions

I cannot find my merchant agreement. Is the comparison dead?

No. Your processor is obliged to provide a copy, and asking for it is itself informative. In the meantime a statement can be benchmarked against fair-market bands without any contract at all, which is the ordinary audit path.

Can I claim money back for past overcharges?

Sometimes. Many agreements carry a fee-dispute window, often measured in months rather than years, and charges that contradict the contract's own pricing terms are the strongest case. Documented drift is more commonly used as leverage for forward repricing, which is faster and does not require anyone to admit anything.

What if the vendor says the increase was announced?

It probably was, in a statement message or a terms update email. That is the model, not an accident. An announced increase you never agreed to is still a repricing conversation, and having the before-and-after numbers is what turns it into one.

How many statements do I need?

One is enough for a benchmark audit. Two or more of the same vendor is what turns it into a drift analysis, because the comparison can then show what moved rather than only what is high.