Platform Overview
The reconciliation engine for cross-border payment complexity
Four-way matching across authorization, capture, settlement, and bank credit — with market-specific exception logic for 30+ local rails.
Three modules. One coherent view.
Reconciliation Engine
Authorization × capture × settlement × bank credit — all four legs matched in a single pass, with configurable tolerance rules per corridor and per PSP. Handles partial captures, split settlements, multi-leg FX conversion, and normalization across heterogeneous settlement file formats.
Exception Management
Unmatched and mismatched transactions surface in a prioritized queue, ranked by dollar amount at risk. Each exception is pre-classified: FX rate variance, settlement timing gap, missing bank credit, duplicate capture, or acquirer fee mismatch. Your team works a short list of items that matter — not a raw data dump.
Reporting & Analytics
Authorized → captured → settled → credited waterfall by corridor. PSP comparison reports show variance in settlement timing and FX conversion across providers. Leakage attribution tracks where revenue is lost over time. Export to GL in CSV or ISO 20022 format on demand or on a scheduled cadence.
Four-way matching at transaction level
Most reconciliation tools check two legs — authorization against settlement. That misses the capture gap (partial captures, late captures) and the bank credit gap (settlement credited to wrong account, split into multiple credits, or delayed outside the expected window). Txnworks closes all four legs in a single pass, with corridor-specific tolerance rules that reflect how local rails actually behave.
- Auth × Capture: configurable ±0.5%–2% tolerance for rounding
- Capture × Settlement: partial capture detection and multi-leg netting
- Settlement × Bank Credit: timing window + amount matching within tolerance
- Corridor-specific rules: Pix real-time vs GPN batch end-of-day handled natively
Built for local rails, not just card networks
Card network reconciliation is a solved problem. The hard cases are local rails — where settlement windows vary by day of week, file formats aren't documented, and FX rate references differ from anything the ECB publishes. Txnworks has pre-built settlement rules for the corridors where that complexity is highest.
See Txnworks on your corridors
Tell us which corridors you operate and which PSPs you run. We'll confirm connector availability and estimate the exception volume your setup is likely generating — before your first session.