Institutions operating across jurisdictions inherit a reconciliation problem most domestic-only firms never have to solve: the same transaction can be true and correctly reported in two regulatory regimes that disagree about what "correct" means.
Currency conversion timing, fiscal-year alignment, and differing chart-of-accounts conventions are the obvious friction points. The harder ones are definitional: what counts as a reportable related-party transaction under one regime may not meet the threshold under another; what one regulator treats as a single consolidated entity, another treats as several. None of this is a data quality problem in the conventional sense — the underlying numbers can be perfectly accurate and still fail to reconcile cleanly across regimes.
Most reconciliation failures we see in practice trace back to the same root cause: a single source system feeding multiple regulatory reports without an explicit mapping layer documenting how each regime's definitions translate from the underlying data. When that mapping lives in someone's head rather than in a controlled document, every personnel change becomes a reconciliation risk.
The break point is almost always at a boundary: between subsidiaries reporting under different local GAAP variants and a parent consolidating under IFRS; between a banking entity's BCBS 239 risk-data aggregation obligations and a separate jurisdiction's local liquidity reporting; between transfer-pricing documentation built for one tax authority and the financial statement disclosures expected by another. Each boundary needs its own documented reconciliation logic — not a single global spreadsheet that quietly drifts out of sync with whichever regime changed its rules most recently.
Reconciliation is not a finance-team problem with a documentation afterthought. It is a documentation problem that happens to surface in the finance team's numbers.
Cross-border reconciliation problems are usually documentation architecture problems wearing a finance-team disguise. Fixing the mapping layer fixes more reconciliation breaks than fixing the data ever will.