Card scheme reconciliation is the process of matching transaction data from card networks such as Visa, Mastercard and American Express with your internal systems. You track each transaction across its full lifecycle, from authorisation through clearing to final settlement, to confirm every record aligns. You compare multiple sources, including authorisation logs, clearing files from schemes and settlement reports. Where they match, funds, fees and transaction counts are confirmed correct. Where they don't, you have a break to investigate. It's the foundation of accurate financial reporting in any card payment environment.

Discrepancies occur when transaction data doesn't align between card schemes, processors and your internal systems, usually because of differences in timing, processing logic or data quality across the payment lifecycle. Common causes include delays between authorisation, clearing and settlement; missing or duplicated transactions in scheme files; inconsistent reference data such as transaction IDs or timestamps; and currency conversion or cross-border processing differences. Without structured matching rules and exception workflows, those gaps stay unresolved.

Authorised payments may fail to clear, duplicates may enter settlement files, and differences between your records and scheme data go unnoticed. Fee errors are the expensive one: interchange and scheme assessments apply across thousands or millions of transactions, so a small error compounds into significant revenue leakage. Schemes also operate strict timelines, so without reconciliation against scheme files you risk missing dispute stages, accepting invalid claims, or reporting incorrect outcomes.

They're the periodic data submissions card networks require from institutions involved in payment processing. QMR is the Quarterly Mastercard Report; GOC is Visa's Global Operating Certificate. Both cover transaction volumes, types and values over the period, along with cardholder activity, interchange fees, currency conversions and other transaction metrics.

Any entity that processes, accepts or facilitates card transactions. That includes banks and credit unions, payment processors, acquiring banks and merchant account providers, payment gateways, independent sales organisations and merchants.

Penalties vary with the severity and frequency of the error, and range from financial penalties and fines through to sanctions and, in serious cases, suspension from the network. That's why validating the data before filing matters as much as assembling it.

T140 is a data format used in Mastercard QMR reporting. It defines the structure of transaction data exchanged between financial institutions, processors and the network, covering metrics such as transaction amounts, merchant details and cardholder information.

Frequently, and throughout the settlement cycle rather than at the end of it. Reconciling as data arrives means issues surface early instead of accumulating across a reporting period and turning up in a quarterly submission.

Volume and complexity are the problem. Scheme data arrives in several formats across multiple regions, and a spreadsheet can't apply consistent matching logic across all of it or flag exceptions as they appear. It also leaves no audit trail, which matters when you're defending a fee challenge or a rejected submission.

Processor reporting tells you what your processor believes happened. Reconciliation tells you whether that matches the scheme files, your bank and your own ledger, and whether the fees you were charged were correct. The value is in the comparison, which is precisely what a single source can't give you.