Insights on Crypto Payments, Infrastructure, and Operations

Swap Reconciliation

Payment Infrastructure & Operations

Pronunciation: SWAHP rek-un-sil-ee-AY-shun

Definition

Swap reconciliation verifies that an asset or currency swap was quoted, executed, settled, and recorded correctly across orders, fills, balances, fees, rates, and counterparties. It explains differences between expected and realized exchange outcomes. Swap Reconciliation requires named ownership and auditable controls for matching evidence, cutoff control, and exception resolution. The process begins with the approved swap request , including input asset and amount, output asset, quoted rate, tolerance, route, and expiry.

Overview

How it works and where it fits

Swap reconciliation verifies that an asset or currency swap was quoted, executed, settled, and recorded correctly across orders, fills, balances, fees, rates, and counterparties. It explains differences between expected and realized exchange outcomes. Reconciliation confirms conservation of value within the defined accounting method and assigns every residual amount.

It then compares actual fills, execution prices, fees, transferred quantities, settlement movements, and ledger entries. The system should retain each fill and conversion step rather than replacing them with one calculated average without source evidence. Teams should design for missing records, false matches, wrong cutoffs, inconsistent currencies, hidden exceptions, and unsupported manual corrections. The operating record should identify the source population, counterpart data, matching rule, cutoff, amount or value, tolerance, exception reason, owner, and resolution evidence. Controls should keep original source records immutable, use stable match keys, explain many-to-one or one-to-many relationships, and route unresolved differences to an aged exception queue.

Swap Reconciliation should remain distinct from Reconciliation and Reconciliation Exception, because each can represent a different stage, record, control, or financial outcome.

Partial fills, multiple venues, rounding, network fees, slippage, failed legs, and delayed settlement can produce legitimate differences. Important failure modes include missing records, duplicate matches, timing differences, hidden fees, currency mismatches, stale files, and adjustments that force balances to agree without explaining the cause.

Wallet-to-Ledger Reconciliation; Withdrawal State; Withdrawal Approval

Example

A treasury executes a swap sending 1 ETH and receiving 2,400 USDC. The final on-chain events show 2,393 USDC delivered after slippage and execution cost. Posting the quote of 2,400 would create an unexplained difference; accounting must use observed execution, fees and applicable valuation rules.

Comparison

Match the submitted swap instruction to actual transaction receipt and each asset movement. Router contracts can create several transfer events in one transaction. Separate approval, execution, reverted execution and settlement. Include network gas and any protocol fees; never infer final swap delivery merely from a displayed quote.

Key Takeaway

Account for actual on-chain swap execution, not merely quoted proceeds.

Sources

  1. Principles for Financial Market Infrastructures — BIS CPMI-IOSCO (2026-08-01)
  2. Conceptual Framework for Financial Reporting — IFRS Foundation (2026-08-01)