Multi-Currency & Multi-Entity Reconciliation

Global finance teams often reconcile the same transaction across multiple currencies, legal entities, bank accounts, and reporting systems. That creates extra work at month-end and makes it harder to spot exchange-rate differences, settlement gaps, intercompany entries, and entity-level mismatches.

Cointab helps finance teams manage multi-currency and multi-entity reconciliation with a structured workflow. Users upload or receive Side A and Side B data, map required fields, normalize values where needed, run reconciliation, review exceptions, and download audit-ready reports.

Why multi-currency and multi-entity reconciliation becomes complex

When finance data spans countries or subsidiaries, the same transaction can appear differently in each system. A sale may be recorded in one currency, settled in another, and booked in a third base currency at the entity level.

Common challenges include:

• Exchange-rate differences between booking time and settlement time
• Separate bank statements, ledgers, and reports for each entity
• Different chart-of-account structures or reference formats across subsidiaries
• Delayed settlement or cross-border payout timing
• Intercompany transfers that require netting or contra-style matching
• Manual Excel-based comparisons that are difficult to audit and reuse

The result is often a long reconciliation cycle with repeated file checks, unclear exceptions, and more time spent explaining differences than resolving them.

How Cointab structures multi-entity reconciliation

Cointab uses a Side A and Side B model so finance teams can compare the records they expect to be correct with the records received from banks, marketplaces, PSPs, vendors, customers, or other external sources.

Side A: your internal records

Side A can include:

• Books or ledger data
• ERP exports
• Internal sales reports
• Subsidiary-wise transaction files
• Receivables or payables data
• Internal settlement working files

Side B: external records

Side B can include:

• Bank statements
• Payment gateway reports
• Marketplace settlement files
• Vendor statements
• Customer statements
• PSP payout reports
• Other external transaction records

This structure makes it easier to reconcile at the entity level, the currency level, or both.

Normalise amounts and identifiers before matching

Multi-currency reconciliation often requires more than simple row-to-row comparison. Cointab lets users map the fields that matter, such as:

• Transaction date
• Amount
• Currency
• Entity or subsidiary code
• Order ID, invoice number, UTR, settlement ID, or another identifier

Where a comparison needs cleaning or transformation, users can create derived columns. These calculated fields can help normalize currency amounts, standardize IDs, or prepare data for matching.

For example, a team can create a derived column for:

• Base-currency amount
• Clean transaction reference
• Net amount after fees
• Entity-specific reporting amount
• Normalized identifier for matching

AI can help generate Excel-style formulas for these derived columns, which is useful when the logic is clear but manual formula writing is time-consuming.

Reconcile across entities, currencies, and reporting periods

Cointab supports flexible reconciliation setups for recurring finance workflows. Teams can use a popular reconciliation template or create a custom workflow for their own structure.

This is useful for:

• Bank vs books reconciliation across multiple subsidiaries
• Subsidiary ledger vs consolidated reporting checks
• Marketplace settlement reconciliation by entity
• Payment gateway reconciliation across regions or currencies
• Vendor and customer statement reconciliation where amounts are reported differently on each side
• Intercompany transaction reconciliation

Once configured, the same reconciliation can be reused for future periods, reducing repeat setup work during monthly or quarterly close.

Review matched, partially matched, unmatched, and skipped records

Cointab separates the reconciliation outcome into clear categories so finance teams can focus on exceptions instead of reviewing every row manually.

• Fully matched: identifiers and amounts match according to the reconciliation logic
• Partially matched: identifiers match, but amounts differ
• Unmatched: records exist on one side but not the other
• Skipped: rows were excluded because they were incomplete, invalid, duplicate, or otherwise unusable

This level of visibility is especially important in multi-entity reconciliation, where differences may come from timing, currency conversion, deductions, fees, refunds, or data quality issues.

AI-assisted review for difficult open items

After structured matching runs, Cointab can use AI to analyse remaining open transactions where deterministic rules are not enough.

AI support can help finance teams with:

• Unstructured or inconsistent references
• Slightly different descriptions across systems
• Missing identifiers
• Complex grouping or netting scenarios
• Reason analysis for unresolved items

The system remains conservative. If the evidence is not strong enough, the item should stay unmatched rather than being forced into a weak match.

Audit-ready reporting for global finance teams

Once reconciliation is complete, users can review a report dashboard that shows summary totals and transaction-level detail. Teams can filter by period, reconciliation, or run history and download Excel reports for internal review, audit, or partner follow-up.

The report view helps teams understand:

• What matched fully
• What only partially matched
• What remains open
• What was skipped and why
• Which entity or currency is affected

Cointab also supports manual match for exceptions that need business review. If a file was missed, users can upload it under the same reconciliation and refresh the report, which is useful when late bank, marketplace, or partner files arrive after the initial run.

Reuse and automate recurring reconciliation workflows

Multi-currency and multi-entity reconciliation is rarely a one-time task. Finance teams usually repeat the same workflow every month, quarter, or year.

Cointab supports reuse so teams do not need to rebuild the setup each time. Users can run reconciliation manually or automate data flow through email, SFTP, or API-based input. Output can also be delivered back to internal systems through email, SFTP, or API.

This makes it easier to keep reconciliation part of the finance operating rhythm rather than treating it as a separate spreadsheet exercise.

Team workspaces for shared finance operations

Cointab supports team-based workspaces, so controllers, accountants, analysts, and reconciliation managers can work from one shared environment instead of passing files around. Roles, permissions, shared history, and audit logs help keep the process controlled and reviewable.

For global businesses, this means multiple entities can follow a common reconciliation method while still retaining visibility into run history, files used, and exception handling.

Built for recurring close, not one-off file checks

Cointab is designed for finance teams that need a repeatable reconciliation workflow across currencies and entities. The platform helps reduce manual spreadsheet work, improve consistency, and make open items easier to investigate.

That makes it useful for teams that need dependable reconciliation reporting across subsidiaries, regions, and payment flows without rebuilding the process every period.