Auditing Payment Fees: Five Places You Are Probably Being Overcharged

Auditing Payment Fees: Five Places You Are Probably Being Overcharged

Most teams reconcile a payment statement with one action: compare the month's total fees against "volume times contracted rate" and let it go if the gap is small.

That approach misses the real risk. A contracted rate is an application rule, not an execution result. The same transaction can be priced very differently depending on whether it was classified as cross-border, whether currency conversion occurred, which card type it used, how refunds are treated, and whether the tier triggered on cumulative volume. A total that matches only proves the arithmetic; it does not prove every item used the rule it should have.

Overcharges almost always appear in rule application, not in multiplication.

1. Separate two levels of reconciliation

Level one: total check. Verify that statement totals roughly match volume against the fee structure. This catches obvious errors such as a missed refund or an outright wrong rate tier.

Level two: per-item rule check. Sample transactions, recompute the fee that should have been charged under the contract, and compare with what was actually deducted. Only this level catches systematic overcharging of a particular transaction type.

Level two does not need full coverage. Use stratified sampling by type: cross-border cards, domestic cards, different schemes, with and without refunds, large and small tickets, with a fixed sample per stratum. If one stratum shows a persistent one-directional gap, the rule application is broken there, and that stratum can then be checked in full.

2. Five frequent overcharge patterns

2.1 Domestic transactions charged a cross-border fee

The most common pattern. Whether a cross-border fee applies depends on whether the issuer's country and the acquiring entity's country differ - not on currency, and not on where the consumer is located.

There are three typical misclassifications: judging by currency (charged in dollars so treated as cross-border), judging by IP (consumer visits from abroad so treated as cross-border), and judging by billing address. None of these is the scheme's basis for determining cross-border status.

How to detect it: take every transaction charged a cross-border fee in the period and check issuer country against acquiring entity country. Same-country transactions charged the fee are recoverable.

2.2 Currency conversion applied twice

When transaction currency differs from settlement currency, conversion occurs. The problem is that conversion can happen at two points: the acquirer's conversion and the scheme network's conversion. Charging both is double counting.

There is a variant too: local acquiring already clears in local currency, so in principle no conversion should occur, yet a conversion fee still appears on the statement. This is frequent in cross-border business and the amounts are not trivial.

How to detect it: for transactions with a currency difference, check whether both an acquirer conversion fee and a network conversion fee appear; for local acquiring, check whether any conversion fee line appears at all.

2.3 Refunds that do not return the fee, and refunds charged again

Refund fee treatment follows one of two conventions: the fee is not returned (the original fee stands and the refund is not charged again), or the fee is returned proportionally. Both are acceptable, but must match the contract.

Overcharges appear in three forms: the contract says the fee is returned but the statement keeps it; the contract says it is not returned yet the refund transaction is charged a separate "refund processing fee"; or a partial refund is charged on the full amount without proportional adjustment.

How to detect it: keep a dedicated refund cross-check table, compare contract clauses against statement lines, and focus on whether "refund count times per-refund fee" matches the contract and whether partial refunds were adjusted proportionally.

2.4 Tiers that never trigger on cumulative volume

Tiered pricing - a lower rate once monthly volume reaches a band - is most often mis-executed by testing per transaction instead of cumulatively, by not accumulating across months, or by not applying the lower tier the following month.

A subtler failure: the tier is calculated separately by scheme, card type and region, while the statement aggregates everything, so the best tier is never actually reached.

How to detect it: check three things - the tier basis (per item, monthly cumulative, or per group), the effective date after triggering, and whether the statement prices in segments. Ask the acquirer for segmented pricing detail rather than a single total.

2.5 Fixed and dispute fees counted twice

Per-item fixed fees (for example a flat authorization fee) overlap easily with dispute processing fees, case fees and representment fees. Typical cases: a chargeback is charged a "case fee", then a further "representment fee" after the merchant wins, when the contract allows only one; or the same chargeback is counted once as a processing fee and again as an assessment fee.

How to detect it: group every dispute-related fee line by dispute ID and check whether the total per dispute exceeds the contractual cap.

3. An auditable cross-check table

The table does not need to be elaborate, but the fields do need to be sufficient.

The critical requirement is that the recomputed fee be traceable to a contract clause number. Without that column, reconciliation degenerates into "I think it should be this way", which cannot be argued with an acquirer.

4. Recovering what was taken

Step one: fix the evidence. Turn the difference into a list: transaction ID, date, amount, amount due, amount charged, and the contract clause relied on. Item-level traceability persuades; totals do not.

Step two: raise it through the channel. Start with the account manager and copy the finance contact; where scheme rules are involved (cross-border classification, for instance), ask for the determination basis rather than a conclusion.

Step three: separate recoverable from non-recoverable. Most contracts set a look-back window for fee disputes (accepting only the last several months, for example), and anything outside it is normally lost. Check also whether the contract says "the acquirer's system records prevail", which shifts the burden of proof.

Step four: turn the finding into process. Recovering once is not success; writing the checks into the monthly routine is. At the next renewal, close the ambiguous clauses: basis for cross-border determination, the point at which conversion is charged, refund fee rules, tier basis and effective timing, and caps on dispute-related fees.

5. A quarterly checklist

Do six things every quarter: check cross-border fee applicability against issuer and acquiring entity country; check for duplicated currency conversion; check refund fees against the contract; check whether tiers triggered cumulatively with segmented detail; check for duplicated dispute fees; and check that reserve percentages match the contract.

These six cover the large majority of recoverable overcharges. Afterwards, record the difference ratio in a ledger - the trend of that ratio says more about the working relationship with your acquirer than any single recovery.

For how the fee structure is built see payment gateway rate comparison; for overall reconciliation practice see payment reconciliation and settlement statements; for automation see automating payment reconciliation; for how reserves affect cost see rolling reserves and float. More payment options are listed under the payment category.

Source: 16IDC original. Fee application rules, dispute look-back windows and statement bases follow the acquirer contract and the schemes' currently published rules.