Payment Reconciliation
What Is Payment Reconciliation?
Payment reconciliation is the financial process of matching transaction records from multiple systems—payment processor logs, bank settlement files, and internal order data—to verify that every authorised transaction was correctly settled at the right amount, with no missing entries or unauthorised charges. In regulated environments, reconciliation is both a compliance requirement and a revenue assurance mechanism that directly protects the income statement.
The Reconciliation Process in Detail
Data Sources and the Normalisation Problem
Reconciliation draws from three primary data layers: transaction logs from the payment processor (every authorisation, capture, void, and refund event); settlement files from the acquiring bank, typically delivered as ISO 20022 XML or proprietary CSV on a T+1 or T+2 schedule; and internal order records from the merchant's ERP or OMS. Each layer uses different transaction identifiers, timestamps, and fee structures. In a multi-acquirer setup, the number of settlement file schemas to parse multiplies with every new provider added.
Matching Logic and Exception Handling
A reconciliation engine Links records across layers using composite matching keys: merchant order reference, processor transaction ID, amount, currency, and settlement date. Exceptions—amounts that do not match, transactions present in one layer but absent in another, or settlements with unexpected fee deductions—are flagged for manual review. Rising exception rates are a leading indicator of integration health issues or PSP schema changes.
Chargebacks and the Full Transaction Lifecycle
A transaction that settled correctly but was subsequently reversed via chargeback affects the net settlement amount and must be tracked through its complete lifecycle: authorisation → capture → settlement → dispute notification → chargeback → final net. Robust reconciliation integrates pre-dispute alerts (Ethoca, Verifi) alongside formal chargeback notifications to produce accurate financial accounts.
Common Pain Points Without Automated Reconciliation
Manual reconciliation across three or more PSPs is error-prone, time-consuming, and a consistent bottleneck for finance teams.
PSPs use inconsistent field names and file formats, requiring custom parsers that break when providers update their reporting schemas.
Disputes and refunds create out-of-band settlement events that break simple two-way matching logic.
How Hellgate Pulse Automates Reconciliation
Pulse, Hellgate's observability and event management layer, normalises settlement and transaction data across all PSPs connected via Link into a single, unified event schema. Finance teams receive one consolidated ledger view regardless of how many acquirers are in the routing stack—replacing manual, per-PSP file imports with an automated, real-time data pipeline.
The Pulse Transaction Reconciliation API exposes this normalised data programmatically, enabling direct integration with SAP, NetSuite, Dynamics, or custom BI tools. Dispute and chargeback lifecycle events are included in the same event stream, ensuring the full transaction lifecycle is captured in one place.