Fines, fees and adjustments on a payment statement are easy to miss because each one is small. Added up over the life of an account, and especially over its last six months, they can be a claim in their own right, so every line should be traceable to a clause and a document.

Three kinds of deduction come up repeatedly, and there is a step-by-step way to check them in a spreadsheet. The examples below are illustrative, not drawn from any specific provider or file.

Scheme fines passed on without supporting documents

Illustrative example. A merchant’s statement shows a deduction of €14,000 labelled “Scheme non-compliance assessment: Q2”. The merchant asks what it relates to. The answer: a card scheme fined the institution in connection with the merchant’s traffic, and the agreement allows the fine to be passed on. No further explanation is given.

Pass-through clauses are real and common. But passing on a fine involves several steps, and each can be checked: the scheme’s actual notice to the institution, the amount the scheme actually charged, the share genuinely caused by your traffic rather than spread across many merchants, and the contractual basis for passing it on at all. Some agreements allow pass-through only of fines caused by the merchant’s breach, which is narrower than fines connected to the merchant’s traffic.

What to ask for, in writing: the scheme notice, the calculation that allocates the amount to you, and the clause relied on. An institution that has these documents can produce them. If the reply simply repeats the label (“this was a scheme assessment”), keep that reply in your file.

Chargeback figures that don’t match the scheme data

Illustrative example. A merchant’s own dispute records show 412 chargebacks in a quarter, of which 161 were successfully contested and reversed. The statements for the same quarter show 412 chargeback debits and 118 reversal credits. Forty-three reversals exist in the scheme’s records and not in the merchant’s bank account.

Chargeback accounting has many legitimate moving parts: timing differences, currency conversion, and scheme fees netted against reversals. That is exactly why errors here go unnoticed. The merchant sees a stream of debits and credits, has no practical way to pair them one by one, and trusts the net figure.

This check takes more work than the first, but it is mechanical. Put your dispute records (from the portal you exported on day one; see the 30-day checklist) on one side and the statement entries on the other, and pair them by case reference. The gaps left after honest pairing are the claim. A related problem, scheme recoveries that never appear at all, is covered in a separate article because the evidence works differently.

Fees that appear when the account is closed

Illustrative example. A terminated merchant’s final statement shows entries never seen in four years: “account closure administration: €2,500”, “extended monitoring fee: €450/month, 6 months”, “compliance file retention: €1,200”.

Closure fees tend to appear at termination for a practical reason. The institution knows the relationship is over, the merchant is busy dealing with the termination, and the amounts can be taken from money the institution already holds. Deducting is easier than invoicing. Each fee raises the same two questions as a passed-on fine: which clause, and where is the underlying cost? At closure the answers are often thinnest, because these fees may not be priced anywhere in the agreement.

A variant deserves its own attention: fees that were always in the agreement but never charged before. Take a dormant clause, say a monthly “non-compliance surcharge” for missing PCI attestation, that is suddenly applied in the final quarter. If the condition existed for four years, why did charging start when the relationship ended? Charging that starts at termination does not automatically defeat the clause, but it belongs in the ledger, with its date, because the timing is part of the evidence.

How to check a settlement file

You do not need forensic software for a first pass. You need the exports, a spreadsheet and a method.

1. Separate the streams. A settlement file mixes at least four flows: gross settled volume, processing fees, chargeback activity, and “other” (fines, assessments, adjustments, reserves). Tag every line as one of the four. Deductions worth questioning are almost always in the last two.

2. Set a baseline for fees. Take a normal month from the middle of the relationship and work out the effective rate you actually paid. Then work it out for every other month. Changes in that rate have dates, and each date has an explanation: a repricing you agreed to, or one you didn’t.

3. List every “other” line. Each entry that is neither volume nor a standard processing fee goes into the deduction ledger: date, amount, label, the clause that supposedly allows it, and whether you have ever seen supporting documents. Sort by size and start with the largest ten.

4. Match the chargeback pairs. Pair debits with reversals by case reference, as in the second example above. Keep anything you cannot match in its own list rather than forcing a match.

5. Check the exchange rates. Where settlement and deductions are in different currencies, check which rate was applied and whether the agreement specifies one. A margin taken on every converted deduction is itself a deduction: small on each line, but repeated across thousands.

6. Date the changes. Deduction claims are clearest where the pattern changes visibly: after a termination notice, after a risk-review letter, or after you first complained. Plot the “other” stream over time. A flat line that bends at a meaningful date says more than any description of it. Keep your working: the spreadsheet, the source exports and how you paired entries. An amount that shows how it was calculated stands up to checking; a bare total invites questions.

This is reconciliation work, and it is where we start on a file: we rebuild the amounts, because a deduction claim depends on the reconciliation before it depends on anything else. The amount that comes out of steps 1 to 6 also decides whether the file is worth pursuing at all. The spreadsheet often corrects first impressions in both directions, lowering the entries that felt outrageous and raising the small ones repeated every month.

What deductions can add up to

Each deduction on its own is usually too small to be worth a fight. Over the final year of a terminated relationship, the total can be a real sum. A deduction ledger also supports the rest of the file: a record of unsupported deductions is relevant when the same institution explains why it is still holding a reserve.

If your ledger has entries you cannot match to any clause, attach it with the statements to the quick check; whether we take it on is decided after we review your documents.

This article is for information purposes only and does not constitute legal advice.