Reconciliation

Overview

Why a successful payment may not match the books

A customer order, a crypto transfer and a payout are recorded by different systems for different purposes. The store records a $200 sale. The blockchain records token movements, perhaps split across two transactions. The payment provider records which movements it accepted for that invoice. Later the treasury ledger records net proceeds. Reconciliation means comparing these records and explaining every difference, not merely checking whether two grand totals look similar. Without it, duplicate credits, missing transfers or unnoticed fees can hide inside a large daily balance.

How the underlying system works

An effective reconciliation process starts by defining which ledgers are compared and at what cut-off time. It matches by stable references such as invoice ID, provider track ID, transaction hash, asset, network, amount and time. Because one invoice can have several transfers and one settlement can cover many invoices, a simple one-row-to-one-row join may fail.

Differences should be categorized: network confirmation delay, exchange-rate timing, fee deductions, missing callbacks, unsupported assets, partial payments or duplicate entries. Each exception needs an owner, deadline, supporting evidence and resolution record. Reconciliation becomes more valuable when it runs routinely and feeds improvements to monitoring and product design.

Work from individual records to totals

Take order ORD-18 for $200. Find its invoice or track ID and the payment record that references it. Confirm the asset, network, actual receipt and accepted value. Next, find the provider ledger entry and any fee or conversion adjustments. Finally, trace the amount included in a merchant withdrawal, where applicable. Repeat this for each payment, then compare totals for the same reporting period. If one invoice was paid through two transfers or one payout includes a hundred invoices, use a many-to-one mapping table rather than forcing mismatched IDs into one column.

What to do when entries disagree

An unmatched item should remain visible with a reason: not yet confirmed, wrong network, late payment, unknown incoming transfer, refund pending, conversion adjustment or unreconciled payout. Someone must own its investigation and resolution. Do not silently label a difference “blockchain fees” unless a source record supports that explanation. Choose a consistent valuation timestamp for reporting and distinguish token quantity from a fiat-denominated sales amount. Sound reconciliation enables support, accounting and audit teams to explain where value went without trusting a dashboard screenshot.

Further reading and related concepts

Reference documents: OxaPay — Payment History, OxaPay — Payout History.

Related glossary topics: Transaction Reconciliation, Settlement Reconciliation, Three-Way Reconciliation.