Match the records. Surface the differences. Resolve with confidence.
Bring financial records from relevant systems into a structured reconciliation workflow. Compare transaction and settlement data, identify mismatches, and help operations teams focus on the exceptions that need attention.
Reconciliation
Monitor matching performance and manage reconciliation runs.
Total transactions
57,085
Processed records in filtered runs
Matched
55,554
Successfully matched records
Unreconciled
1,531
Records requiring investigation
Average match rate
97.0%
Across completed runs
Dataset totals scoped to the selected runs
Metrics update with your search and filters.
Reconciliation runs
Review execution history and matching outcomes.
| Run ID | Source pair | Status | Matched | Unmatched | Details |
|---|---|---|---|---|---|
| RUN-20260930-052-way reconciliation · Sep 2026 | Bank correction file ↔ Ledger | Failed | n/a | n/a | |
| RUN-20260930-042-way reconciliation · Sep 2026 | Supplemental bank file ↔ Ledger | Processing | n/a | n/a | |
| RUN-20260930-032-way reconciliation · Sep 2026 | Bank statement ↔ Payment ledger | Completed | 1,608 | 57 | |
| RUN-20260930-022-way reconciliation · Sep 2026 | Card settlement file ↔ Ledger | Needs review | 9,214 | 311 | |
| RUN-20260930-013-way reconciliation · Sep 2026 | UPI switch ↔ CBS ↔ Bank statement | Completed | 22,104 | 410 | |
| RUN-20260831-022-way reconciliation · Aug 2026 | Bank statement ↔ Payment ledger | Completed | 11,950 | 402 | |
| RUN-20260831-012-way reconciliation · Aug 2026 | POS settlement ↔ Ledger | Completed | 10,678 | 351 |
How it works
Five stages take records from separate systems to a clear list of what matched and what needs attention.
- 1
Ingest records
Import or connect the transaction, settlement, bank, POS, or other agreed source data.
- 2
Normalize the data
Map relevant fields into the reconciliation model configured for the customer.
- 3
Apply matching rules
Compare records using the agreed matching criteria.
- 4
Review exceptions
Surface unmatched records, amount differences, duplicate candidates, or other configured exceptions.
- 5
Resolve and report
Support investigation and tracking, then review reconciliation results and remaining items.
Overview
Reconciliation means comparing records from payment systems, banks, POS systems, settlement reports and internal finance platforms.
Differences in identifiers, formats, timing, and transaction status make this work difficult to manage manually. Eterna-X Reconciliation is designed to bring relevant records together, compare them using agreed matching logic, and organize unmatched or inconsistent items for investigation. The exact sources, matching rules, and workflows depend on the implementation.
The problems it addresses
Formats and identifiers differ
Each source describes the same transaction in its own way, which makes direct comparison unreliable.
Manual matching does not scale
Line-by-line comparison in spreadsheets consumes time that should be spent on the items that are actually wrong.
Exceptions lose their trail
Once a mismatch is found, its source references and follow-up are easily scattered across emails and files.
Inside the workflow
A workspace built around the exceptions.
Matched records step aside. Unmatched items, amount differences and duplicate candidates are laid out for review.
- TXN 48201BNK 77120
- TXN 48202BNK 77121
- TXN 48213BNK 77134
- TXN 48219
- TXN 48222BNK 77140
Matching rules
Reference, amount, date
Key capabilities
What Reconciliation brings to your operations.
Multi-source data intake
Bring in supported records from configured files, systems, or integrations.
Configurable matching
Compare records using agreed identifiers and fields, such as transaction references, amounts, dates, or other available attributes.
Matched and unmatched records
Separate records that meet configured matching criteria from records that require further review.
Exception management
Organize discrepancies and unmatched items so teams can investigate, assign, and track follow-up where supported by the configured workflow.
Reconciliation reporting
Provide structured views of reconciliation outcomes and outstanding exceptions based on available data.
Traceable investigation
Keep source references and reconciliation outcomes connected to support review and follow-up, subject to product configuration.
Business value
What changes for your teams.
Designed for
- Banks and financial institutions
- Finance and reconciliation teams
- Payment operations teams
- Retail and merchant operations
- Organizations managing financial records across multiple systems
Reduce dependence on scattered manual comparison processes.
Make mismatches easier to identify and investigate.
Improve visibility into matched, unmatched, and pending records.
Standardize reconciliation workflows across supported data sources.
Help teams maintain a clearer audit and investigation trail, depending on configuration.
Use cases
Where Reconciliation fits.
- Use case 01
Bank and payment reconciliation
Compare payment transaction records with bank or payment-provider reports.
- Use case 02
POS and retail reconciliation
Compare POS transaction data with settlement or financial records from relevant providers.
- Use case 03
Cash and collection reconciliation
Compare recorded collections with available financial or operational reports.
- Use case 04
Settlement reconciliation
Compare expected settlement information with settlement records received from relevant systems.
- Use case 05
Multi-system financial operations
Bring records from separate platforms into a common workflow for comparison and exception review.
Connected products
Reconciliation works with the rest of Eterna-X.
Each product area hands its records to the next, so teams keep the same transaction context from start to finish.
FAQ
Questions teams ask.
Can matching rules be adapted to our data?
Yes. Matching compares records using agreed identifiers and fields, such as transaction references, amounts and dates. The rules are configured for each implementation.
Which sources can be reconciled?
Transaction, settlement, bank, POS and other agreed source data can be imported or connected. The supported sources are confirmed during implementation.
What happens to records that do not match?
They are separated from matched records and organized as exceptions, such as unmatched items, amount differences or duplicate candidates, so teams can investigate and track follow-up.
Turn reconciliation exceptions into actionable work.
Share your data sources, reconciliation reports, and matching requirements with Eterna-X to discuss a suitable workflow.
