Card Fees Hide in the Rate You Never Requoted

For many businesses, card processing is the cost that gets checked once, at signup, and then left alone for years. The contract rate stays in a drawer while the actual bill changes underneath it: a processor raises a markup, a card mix shifts toward rewards and commercial cards, a gateway or PCI fee appears, and suddenly the effective rate is well above the rate the business thought it agreed to.

The leak is rarely one dramatic overcharge. It is a stack of smaller ones. Interchange-plus pricing can be blurred by tiered billing. Monthly minimums can survive after volume grows. Duplicate statement, batch, and reporting fees can sit on different lines with similar names. A refund does not always return the original processing fee, and downgrades triggered by missing level 2 or level 3 data can quietly push business and purchasing card transactions into more expensive categories.

A useful audit starts with the effective rate, not the headline rate: total processing cost for a month divided by total card volume. Then compare that figure across locations, terminals, and online checkout, because one outlier often points to a setup error rather than a market rate. Check assessment fees for padding, look for PCI, IRS reporting, and equipment charges that were never in the agreement, and test a sample of commercial card transactions to see whether enhanced data is actually being passed.

That line-by-line comparison is part of what ERPSav is built to do. As a product of CloudVerg, ERPSav runs 15 rules-based recovery engines across nine leak categories, from duplicate supplier payments and lease overcharges to utility and telecom errors, parcel charges, SaaS waste, chargebacks, sales tax overcharges, warranty claims, and padded card processing fees. For businesses in the US, Canada, the UK, Ireland, Australia, and New Zealand, the 14-day free trial includes every module and requires no card, making a first statement audit a low-risk place to start.