Payment reconciliation: why reports never match

Payment reconciliation: why your report never matches the acquirer

The dashboard shows R$ 1 million sold. The bank shows another number. The acquirer (Brazil's card settlement provider) brings a different schedule. And finance's spreadsheet has yet another version. That gap does not necessarily mean error: sale, approval, settlement, fees, refunds, chargebacks, splits, and anticipation happen at different times. Payment reconciliation is the process of linking those events until the company knows what it sold, what it is owed, what it received, and why each difference occurred.

Billing is not settlement

An approved sale enters commercial reporting before it becomes available cash. Card, Pix, and other methods have different schedules.

Reports must clarify which date and status are being used.

Fees break gross comparisons

Platform fees, acquirer costs, anticipation, and other charges may be deducted at different times.

Compare gross, fees, and net in separate columns.

Refunds and chargebacks arrive later

Yesterday's sale may be adjusted weeks later. That changes net revenue without erasing the original order.

Keep an event history instead of overwriting the past.

Split multiplies entries

In co-production and affiliate models, a single sale can generate payouts to different participants.

Reconciliation must show the split base and destination of each amount.

Automation depends on identifiers

Order, transaction, customer, and payout must share keys that allow matching. APIs and webhooks help when events are idempotent and monitored.

The biggest savings come when exceptions become a small queue, not the closing rule.

How to bring this into operations

Document the full transaction flow from checkout start through approval, settlement, possible refund, and reconciliation. Mark which systems receive events and who owns exceptions. This simple map surfaces dependencies that usually appear only when volume grows or a campaign scales suddenly.

Read by cohort and source whenever possible. Ticket, payment method, installments, product, campaign, and affiliate can produce different economics. A healthy average approval or chargeback rate can hide a segment that destroys margin and pushes CPA up.

Metrics worth tracking with the decision

Track attempts, approval, checkout conversion, AOV, refunds, chargebacks, net value, and payout timing. Connect those numbers to media CPA and ROAS. The goal is not the highest isolated metric but turning purchase intent into net revenue with controlled risk and cash flow.

The takeaway

Good reconciliation turns multiple reports into one financial story. It explains differences by status, fee, timing, and event.

When finance can trace each sale to receipt, cash and scaling decisions become far more reliable.

Why doesn't my dashboard match the bank?

Because sale, approval, settlement, fees, and reversals can occur on different dates and bases.

Does Pix make reconciliation easier?

It may settle faster, but correct transaction and order identification is still required.

What to automate first?

Matching by identifier, event import, and handling recurring exceptions.

Card, Bizum, or bank transfer: which payment method your ticket prefers

Choosing the right online payment methods for your digital store is not a minor technical decision. It is a commercial decision that directly affects conversion rate, average order value, and customer satisfaction. In Spain, the payments landscape has changed dramatically in recent years with the rise of Bizum, the consolidation of cards, and the persistence of bank transfers in certain segments.

SEPA direct debit and recurring payments: the subscription that does not depend on cards

If your business runs on a subscription model, you probably rely on credit cards to charge every month. The problem is that cards expire, get lost, get blocked, and get cancelled. Every time that happens, your system tries to charge, fails, and you lose a subscriber who had no intention of cancelling.