Reconciliations
On this page
Manage and automate your reconciliations in the Reconciliations module of the Admin.
The Reconciliations module allows you to centralize transaction reconciliation, ensuring transparency and precision in payment management.
The order reconciliation process allows you to verify that transactions processed through different acquirers and processors match the amounts settled in their accounts.
The optional Reconciliation Agent extends this operating model by normalizing financial evidence, classifying exceptions, and recommending the next investigation step. Matching does not by itself authorize an accounting entry, refund, provider adjustment, or write-off.
Currently, many merchants face reconciliation challenges due to:
- Fragmented and unstructured information from different acquirers and processors.
- Manual errors in information cross-referencing.
- Difficulty detecting discrepancies in amounts or dates.
- Lack of visibility over order and settlement statuses.
How it works#
The DEUNA reconciliations module centralizes and automates the reconciliation process, allowing you to:
- Upload your own data sources such as your sales reports or processed transactions.
- Connect with acquirer reports to extract and standardize settlement information. DEUNA handles the technological management to integrate each acquirer into the process.
- Parameterize reconciliation keys and tolerances to apply in the reconciliation process for each source.
- Generate reconciliation reports on each information source.
- Identify discrepancies in amounts, dates and payment statuses.
Define sources, grain, and ownership
| Source | Representative evidence | Typical owner |
|---|---|---|
| Merchant commerce | Order, invoice, amount, currency, customer reference | Commerce or finance |
| DEUNA and processor | Authorization, capture, refund, processor response, transaction reference | Payments |
| Acquirer settlement | Batch, gross and net amount, fee, settlement and value dates | Treasury or finance |
| Bank or payout | Deposit, remittance reference, payout, bank value date | Treasury |
| Post-payment operations | Dispute, reserve, adjustment, resolution | Risk or operations |
Define the record grain, expected delivery cadence, immutable matching keys, currency and sign convention, timezone, tolerance, late-arrival window, and operational owner for every source before automating results.
Reconciliation results#
The reconciliation process in DEUNA compares transactions from different data sources, such as merchant reports and acquirer settlements.
Each order can have different classifications according to the process result.
To determine if a transaction has been reconciled correctly or presents differences, the system follows these steps:
- Identification of matching transactions: Records are searched for matches in key attributes such as:
- ID
- Card data
- Amount
- Date.
- Application of tolerances: If there are small differences in amounts or dates, predefined tolerance rules determine whether the transaction can be reconciled without differences or requires manual review.
The following table describes the possible reconciliation states and sub-states:
| State | Sub-state | Description |
|---|---|---|
| Not reconciled | Pending | The transaction has not been found in both data sources or presents differences outside the tolerance range. |
| Reconciled | No differences | The transaction has been successfully reconciled or has differences within acceptable parameters. |
| Reconciled | Amount difference | The transaction matched between different data sources, but presents a discrepancy between the amounts of each record outside the established tolerance. |
| Reconciled | Date difference | The transaction matched between different data sources, but presents a discrepancy between the transaction dates of each record outside the established tolerance. |
Admin users can apply advanced filters to visualize only relevant transactions and download customized reports for more detailed analysis.
Data source
Manage your reconciliation data source in your store in the Admin.
Each source must have an agreed file or connection contract, delivery schedule, field mapping, matching policy, and owner. Reprocess a source only after confirming whether the previous run produced a partial or conclusive result.
Settlements
Access all the information provided by the Settlements acquirers and review settlement reports.