FX risk data reconciliation is the routine of proving that the numbers behind your currency exposure agree with each other: forecast and booked exposures, hedge trades, bank settlements, exchange rates and the general ledger. If they agree, the exposure you report to the board is the exposure you really carry. If they do not, every hedge ratio, Value at Risk figure and variance explanation rests on data nobody has checked. This guide shows a UK finance team what to match, how often, in what order, and how to deal with the breaks you will find.
TL;DR
- Reconcile four layers: exposures, hedge trades, cash settlements and ledger entries, all against one documented set of exchange rates.
- Classify every break (timing, fees, rate, data error) before you adjust anything. Not every difference is an FX difference.
- Reconcile cash and positions daily where volumes justify it, and escalate unexplained items to senior management promptly.
- Automate imports, rate rules and matching, but keep a human sign-off and an audit trail from source document to ledger.
- Unreconciled data leads to misstated accounts, missed under-funding, unexpected overdraft charges and undetected errors or fraud.
Table of Contents
- What FX risk data reconciliation means for a UK business
- Which records you need to reconcile
- A step-by-step process
- Common mismatches and how to resolve them
- Controls, responsibilities and frequency
- What automation can and cannot do
- What happens when FX data is not reconciled
- Our perspective: reconcile the risk data, not only the ledger
- Bringing exposure data into one place
- FAQ
- Sources
What FX risk data reconciliation means for a UK business
Most explanations of FX reconciliation focus on the accounting side: foreign-currency balances in the ledger must agree with source records, and rate adjustments must be applied correctly. That is necessary, but for a company managing currency risk it is only half the picture. Risk reconciliation asks a second question: does the exposure data used to make hedging decisions agree with the accounting and cash data?
Think of two views of the same business. The accounting view records what has happened, in sterling, under your reporting framework. The risk view records what could still happen: forecast sales in euros, supplier invoices in dollars, intercompany loans in Swedish krona. Reconciliation is the bridge between them. It is also what lets you explain why reported performance differs from performance at a constant rate, which is the question a finance director gets asked in most board packs.
Two definitions help keep the scope clear:
- Reconciliation of records. Your books and records are consistent with those of your counterparties and reflect trade events such as amendments. The Federal Reserve Bank of New York describes portfolio reconciliation in exactly these terms.
- Reconciliation of rates and valuations. The rates used for exposure, hedge valuation and accounting come from approved, documented sources, so that differences between them are explainable rather than accidental.
If you want the accounting mechanics in more depth, our guide to currency exchange accounting covers translation and revaluation, and advanced accounting for FX risk goes into multinational structures.
Which records you need to reconcile
A workable programme reconciles each layer to the next, not everything to everything. The table sets out the layers, what they are matched against and the typical owner.
| Layer | What it contains | Reconcile against | Typical owner |
|---|---|---|---|
| Exposure data | Forecast and booked currency flows, balance sheet items, intercompany positions | ERP and subledgers (receivables, payables, loans) | Treasury or FP&A |
| Hedge trades | Forwards, swaps, options: amounts, dates, rates, counterparties | Dealer or bank confirmations and statements | Treasury middle or back office |
| Cash settlements | Expected and actual payments and receipts by currency | Bank statements and standing settlement instructions | Treasury operations |
| Rates | Spot, average and period-end rates used in each system | One approved, time-stamped rate source | Treasury and financial control |
| Ledger | Transactions, realised and unrealised gains and losses | Source transactions, subledgers and bank records | Financial control |
The UK accounting backdrop
Whatever the risk system says, the ledger follows your reporting framework. Under FRS 102, ICAEW guidance states that foreign-currency transactions are translated into the functional currency at the spot rate on the transaction date, and that an average rate such as a weekly or monthly one is acceptable only where it reasonably approximates the actual rate. The guidance applies to the version of FRS 102 effective from 1 January 2026. Your reconciliation must therefore test not just whether a rate was applied, but whether the rate method is one your framework allows.
For tax, HMRC's Corporate Finance Manual notes that companies accounting in sterling translate foreign-currency payments, receipts, assets and liabilities into sterling, and that its staff generally accept the rate used in the accounts for direct taxes if it is applied consistently. Consistency is the reconciliation point: a rate policy that changes between entities or periods creates differences you will spend time explaining.
A step-by-step process
The sequence below suits a mid-sized UK group with a few currencies and a monthly close. Smaller teams can run the same steps with fewer items and a lighter cadence.
- Fix the rate source and the cut-off. Choose one approved provider of spot and period-end rates, record the time of day used, and archive each published set. Differences in rate source are one of the commonest reasons two systems disagree.
- Import and validate the data. Pull exposures from the ERP, trades from your dealing records and cash from bank files. Check for duplicates, missing currencies, stale rates and rejected records at load, not at the end.
- Match exposures to the ledger. Confirm that open receivables, payables, loans and balance sheet items in each currency agree to the subledgers and the general ledger, in both currency and sterling terms.
- Match hedges to confirmations. Compare each trade's amount, value date, rate and counterparty to the bank or dealer confirmation. Check that amendments and early settlements are reflected on both sides.
- Match cash to expectations. Compare expected and actual settlements by currency and date. Confirm that accounts are properly funded for the next value dates.
- Recalculate the FX gains and losses. Recompute realised gains at settlement and unrealised gains at the reporting date from source data, and compare them with the ledger.
- Classify and resolve breaks. Assign each unmatched item a cause and an owner (see below) and clear it before the period closes where possible.
- Sign off and archive. A reviewer independent of the preparer signs the reconciliation. Keep the evidence, the rates and the explanations together.
Several of these steps overlap with a general close routine. A month-end close checklist for small teams is a good place to see how daily reconciliations and discrepancy escalation fit into the wider calendar, and the FX steps above slot in alongside the bank and subledger reconciliations you already do.
Common mismatches and how to resolve them
The discipline that saves the most time is classifying a break before fixing it. Calling every difference an FX difference sends people looking at rates when the real cause is a missing invoice. These are the categories we see most often in finance team practice:
- Timing. The trade date, value date and posting date fall on different days or in different periods. The amounts agree, but not on the same date. Resolve by checking dates on the confirmation, bank record and ledger entry.
- Rates. Two systems used different sources, different times of day, or an average rate where a spot rate was required. Resolve by comparing against the archived rate set and the rate policy.
- Fees and charges. Bank charges, intermediary deductions or spreads reduce the amount received. Resolve by tracing the bank record and posting the cost to the right account rather than leaving a residual in FX gains and losses.
- Data errors. Duplicate imports, wrong currency codes, mistyped amounts, missing transactions. Resolve at source and correct the feed so it does not recur.
- Cross-entity differences. Intercompany balances disagree because the two entities used different cut-offs, rates or accrual treatment. Resolve with one agreed rate, one cut-off and a named owner for each counterparty pair.
Two habits deserve a mention. First, do not reconcile to zero by plugging the difference into an FX line: that hides the cause and makes the next break harder to see. Second, write down the resolution. If the same break recurs every quarter, the process or the data feed is wrong, not the number.
Reconciling variance in reported results
If your management accounts use a fixed budget rate while statutory accounts use actual rates, the gap between the two is an FX variance that needs its own bridge. Build it by driver: translation of foreign operations, transaction gains and losses, and the effect of hedging. The bridge should foot to both sets of figures, with every line traceable to a rate and a balance. Our guide to FX position valuation for multinationals shows how valuation choices feed into that bridge.
Controls, responsibilities and frequency
How often to reconcile depends on volume, instrument type and regulatory status, but the principles are stable. The Foreign Exchange Committee's guidance on operational risks in foreign exchange points to separation of front and back office, daily reconciliation of the general ledger to operations, strict validation of standing settlement instructions, and informing senior management of significant accounting discrepancies so controls can be reviewed and updated. Although written for market participants, the logic carries over to a corporate treasury.
On the risk side, the Hong Kong Monetary Authority's FX risk management guidance expects positions to be revalued regularly with independent verification of rates, and irregularities such as a large number of offsetting transactions to be reported promptly to senior management and investigated. It is not UK regulation, but it states a control standard that auditors and lenders will recognise.
A practical allocation of responsibilities:
- Preparer: a treasury operations or financial control analyst who runs the matching.
- Reviewer: someone who did not prepare it and who does not trade or approve the hedges.
- Escalation: a defined threshold and timeline after which the treasurer or finance director is told, with a record of the decision.
- Owner of rates: one named person responsible for publishing the approved rate set on time.
If you report derivatives under UK EMIR
Most corporates that hedge with simple forwards will still fall under UK EMIR reporting obligations in some way, even where reporting is delegated to the bank, so check your status. For reporting entities, the FCA's UK EMIR Q&A says arrangements must make sure reconciliation breaks are resolved as soon as practicably possible, with controls proportionate to the nature, scale and complexity of the business. The revised requirements took effect on 30 September 2024. The Bank of England notes that relevant UK firms report derivatives transactions daily, including foreign-exchange derivatives. If this applies to you, your trade records need to agree with what has been reported, and our piece on FX trade audit trails explains how to capture the required fields.
What automation can and cannot do
Manual reconciliation in spreadsheets works until the volume of currencies, entities and trades grows. Then the failure points are predictable: copy-and-paste errors, out-of-date rates, versions of the file nobody can trace. Automation helps in four places:
- Import. Transactions flow from the ERP and banks without re-keying. See our note on ERP integration for FX for setup choices that keep the audit trail intact.
- Rules. Rates, rounding and translation rules are applied the same way every time.
- Matching. Items that agree are cleared automatically, so people spend their time on exceptions.
- Evidence. Each ledger movement can be traced back to its source, rate, rule and approver.
What automation does not do is replace judgement. The team should still review exceptions, and should monitor a short list of indicators: stale or late rates, duplicate imports, rejected or blocked uploads, and FX-only variance by cause. Automated checklists should support professional accounting review, not bypass it.
Bank-side reconciliation is the other half of the picture for international teams. Our overview of banking reconciliation for international finance teams and the guide to streamlining FX reporting are good next reads.
What happens when FX data is not reconciled
The consequences are concrete rather than theoretical. According to the Foreign Exchange Committee, failing to reconcile can lead to inaccurate financial reporting, restatements and reputational damage, and operationally to under-funding that nobody notices, unauthorised overdraft charges, and trade capture errors or fraud that go undetected. The New York Fed's reconciliation guidance adds that comparing expected and actual cash movements is a primary defence for detecting fraudulent activity and ensuring accounts are properly funded.
For hedging, the damage is quieter. If exposure data misses an entity, double-counts an intercompany loan or uses a stale rate, the hedge ratio you report is wrong. You may be over-hedged on one currency and exposed on another without knowing. Any Value at Risk figure calculated on that data inherits the error.
Our perspective: reconcile the risk data, not only the ledger
We build CorpHedge for finance teams who need to see currency exposure in one place, and the same lesson comes up again and again: the hedging decision is only as good as the data behind it. Many companies reconcile their ledger carefully and never test whether the exposure report agrees with it. We think that is backwards. The exposure report is what drives the trades, so it deserves at least the same scrutiny.
Our advice is simple. Decide who owns each data layer. Use one set of rates. Treat every break as information about a process, not as a one-off to be cleared. And keep the audit trail short enough that someone outside the team can follow it in an afternoon. Automation should serve that goal: fewer manual touches, clearer evidence, and more time for the people who understand the business to spend on the exceptions.
— Bartas
Bringing exposure data into one place
If your exposures, hedges and rates sit in different files, reconciliation will always be a monthly scramble. The CorpHedge platform tracks currency positions, runs hedging strategy simulations and Value at Risk analysis, and produces portfolio reports from live market data. It also offers integrations, including with Corpay. If you want to see how it works before deciding, the product tour is the quickest route.
For teams who want to build the skills in-house, our FX hedging course is a one-off purchase at €220. We are also expanding to Poland and Sweden, so teams with subsidiaries there can reach us as well. Local accounting and reporting rules differ by country, so reconcile each entity under its own framework.
FAQ
How often should we reconcile FX data?
Cash and trade positions are best reconciled daily if you transact regularly, in line with the daily general ledger reconciliation the Foreign Exchange Committee describes for market participants. Exposure to ledger reconciliations usually run monthly at close, with a lighter check mid-month in volatile periods. Increase the frequency if you see repeated breaks.
Who should own FX reconciliation?
The preparer should be someone in treasury operations or financial control, and the reviewer should be independent of dealing and of the person who prepared it. Senior management should receive unresolved or unusual items promptly. Document these roles so they survive staff changes.
Is a spreadsheet enough?
For a handful of currencies and trades, a well-controlled spreadsheet can work, provided rates are archived, versions are tracked and a reviewer signs off. As entities, currencies and trade counts grow, manual matching becomes slow and error-prone, and automated imports and matching rules pay for themselves.
Do UK businesses have to reconcile hedge trades with their bank?
UK accounting standards do not prescribe a single method, but reliable accounts and audit readiness require that your records agree with counterparty confirmations. If you are a UK EMIR reporting entity, the FCA expects reconciliation breaks to be resolved as soon as practicably possible. Check your status with your bank or adviser.
Sources
- Federal Reserve Bank of New York: Foreign Exchange Transactions (2016)
- Foreign Exchange Committee: Management of Operational Risks in Foreign Exchange
- ICAEW: Foreign currency translation under FRS 102
- HMRC Corporate Finance Manual CFM12070
- HKMA: Foreign Exchange Risk Management
- FCA: UK EMIR reporting questions and answers
- Bank of England: Trade Repository Data Collections