# How to separate invoice, tax, ledger and reporting currencies Give each conversion a purpose before assigning a rate. The invoice currency determines the customer's obligation. The accounting currency measures the receivable in the ledger. Tax rules determine the currency and conversion used for reporting tax. Group presentation can require another conversion after those calculations are complete. **Diagram:** Assign a purpose, date and source to each exchange rate. Illustrative purposes. An accounting rate, a tax-conversion rule and a consolidation rate can legitimately differ. These amounts do not always remain equal when translated at today's rate. A sound implementation preserves the original obligation and explains later differences rather than overwriting history until reports agree. This guide works one synthetic UK sale through invoice posting, a partial payment, month-end revaluation and final settlement. Use the [currency policy and reconciliation worksheet](#template) to repeat the exercise with your own transaction types. The arithmetic illustrates the stated assumptions; it is not a live Business Central test. ## Name the currencies and their owners For each entity, distinguish the contract and invoice currency, functional accounting currency, tax reporting currency, bank account currency and group presentation currency. Two roles may use the same currency without becoming the same decision. IAS 21 distinguishes foreign-currency transactions from translation into a presentation currency. Functional currency reflects the entity's primary economic environment; selecting a convenient dashboard currency does not determine it. [IFRS Foundation, IAS 21 overview](https://www.ifrs.org/issued-standards/list-of-standards/ias-21-the-effects-of-changes-in-foreign-exchange-rates/). The controller approves the accounting policy. The tax owner approves tax conversion and required invoice information. Treasury provides settlement and bank-rate evidence. The application owner implements those approved rules and keeps rate feeds from changing historical records unexpectedly. Record every rate as a sentence with units. "GBP 0.80 for USD 1" tells the operator to multiply a dollar amount by 0.80 to obtain pounds. A bare value of 0.80 leaves the direction ambiguous. ## Keep the tax rate policy separate from the accounting feed HMRC's VAT valuation guidance specifies permitted approaches for converting foreign currency into sterling, including the UK market selling rate at the time of supply and identified alternatives. A rate used for management reporting is not automatically the selected VAT conversion method. [HMRC, VAT valuation rules](https://www.gov.uk/guidance/vat-tertiary-legislation/valuation). UK foreign-currency invoice guidance also addresses the sterling VAT information required on relevant invoices. The tax owner should approve the invoice output as well as the return calculation. [HMRC, foreign-currency transactions and VAT](https://www.gov.uk/guidance/foreign-currency-transactions-vat-and-tour-operators). In the policy register, give each conversion its rate source, date rule, quotation direction, rounding rule and fallback. Keep the tax point and accounting recognition date in separate fields even when they coincide in the first test. The example uses the same 0.80 rate for initial accounting and VAT conversion. This simplifies the opening journal without implying that every business must use one rate source for both. A design requiring different rates needs its own approved journal and reconciliation treatment. ## Set the worked example's assumptions A UK seller uses GBP as its functional and ledger currency. It issues a USD invoice for a completed domestic taxable sale on 1 October. For this exercise the transaction is standard rated at 20%, and the tax point, recognition date and invoice date coincide. The invoice is USD 10,000 net plus USD 2,000 VAT, making USD 12,000 due. The approved issue-date conversion is GBP 0.80 per USD 1. No cash-accounting VAT scheme, credit loss, hedge, advance payment, bank fee or tax adjustment applies. The seller has not yet remitted the VAT by the example's final settlement date. The customer pays USD 6,000 on 20 October when the rate is 0.82. The seller immediately converts the receipt to GBP. The remaining receivable is outstanding at 31 October, when the closing rate is 0.85. The final USD 6,000 arrives on 10 November at 0.83 and is also immediately converted to GBP. October's receivable revaluation remains posted into November. If your implementation reverses revaluation instead, the journal sequence will differ, although the cumulative result must reconcile. All rates and dates here are invented, and amounts are rounded to two decimals only for display. ## Post the sale and establish the tax amount Convert the invoice's USD 12,000 gross amount at 0.80 to obtain a GBP 9,600 receivable. Revenue is GBP 8,000 and output VAT is GBP 1,600. The opening journal debits receivables 9,600, credits revenue 8,000 and credits output VAT 1,600. The USD receivable remains 12,000. Keep both the document amount and the GBP accounting amount with the source invoice and rate reference. At this point the isolated transaction balances: the 9,600 asset equals the 1,600 tax liability plus the 8,000 pretax profit contribution. These are transaction-level checks, not a complete company's financial statements. The approved VAT reporting amount is 1,600 under the example's assumptions. Later exchange movements on the customer's receivable do not, by themselves, create another supply or change that sterling tax amount. A credit, correction or other tax event would require a separate decision. ## Apply the partial payment before revaluing the balance The first USD 6,000 payment produces GBP 4,920 cash at 0.82. It settles half the original receivable, whose historic GBP carrying amount is 4,800. Record a 120 realised exchange gain. The payment journal therefore debits cash 4,920, credits receivables 4,800 and credits exchange gain 120. The remaining document balance is USD 6,000, carried at GBP 4,800 before the month-end revaluation. Use the actual application of the payment to identify the settled amount. An imported bank receipt that has not been allocated to the invoice is not enough evidence that the receivable has been settled in the subledger. For ordinary monetary items, IAS 21's published requirements use the closing rate at period end and address exchange differences on settlement and retranslation. Apply the relevant exceptions separately where the transaction involves hedging or other special circumstances. [IAS 21, published monetary-item requirements](https://www.ifrs.org/content/dam/ifrs/publications/pdf-standards/english/2022/issued/part-a/ias-21-the-effects-of-changes-in-foreign-exchange-rates.pdf?bypass=on). At 31 October, the remaining USD 6,000 is worth GBP 5,100 at 0.85. Increase receivables by 300 and credit an unrealised exchange gain of 300. Do not revalue the already settled USD 6,000 as though it remained open. ## Reconcile October and the final settlement October closes with cash of 4,920 and receivables of 5,100, making assets of 10,020 for this isolated example. The output VAT liability is 1,600. Revenue of 8,000 plus realised gain of 120 plus unrealised gain of 300 gives an 8,420 pretax profit contribution. Liability plus profit equals assets: 1,600 plus 8,420 equals 10,020. In November the final USD 6,000 converts to GBP 4,980. The outstanding receivable is carried at 5,100 following October's retained revaluation. Debit cash 4,980 and exchange loss 120, then credit receivables 5,100. The customer now owes zero in both currencies. Total GBP cash received is 4,920 plus 4,980, or 9,900. Relative to the original GBP 9,600 receivable, cumulative exchange gain is 300. The period journals reconcile to the same amount: 120 plus 300 minus 120 equals 300. The final isolated position is cash of 9,900, VAT payable of 1,600 and cumulative pretax profit contribution of 8,300. Again, 1,600 plus 8,300 equals 9,900. No exchange movement has been mislabelled as additional sales or additional sterling output VAT. ## Translate reporting values without creating a new accounting basis Suppose the group presents a USD package at October close. Translating the GBP 5,100 receivable at 0.85 produces USD 6,000, matching the amount still owed. Translating the GBP 4,920 cash at the same closing rate produces USD 5,788.24; the cash is GBP cash because the original dollars were sold on receipt. Those balance-sheet illustrations do not constitute a complete group translation. Income, expenses, equity and resulting translation differences need the approved presentation-currency process. Do not translate the whole trial balance at one rate and call the resulting equality a complete IAS 21 calculation. Business Central documents local currency and an additional reporting currency on general-ledger and other entries, including VAT entries. It also provides exchange-adjustment settings for those entries. This describes Business Central's documented currency mechanism, not a second GAAP book or a guarantee of a country's tax treatment. [Microsoft, additional reporting currency](https://learn.microsoft.com/en-us/dynamics365/business-central/finance-how-setup-additional-currencies). Microsoft separately documents currency records, exchange rates, rounding and gain/loss accounts. Before deployment, demonstrate the chosen settings in the exact Business Central release, deployment and localisation used by the entity. Do not copy an untested menu sequence from a different version. [Microsoft, currency setup](https://learn.microsoft.com/en-us/dynamics365/business-central/finance-set-up-currencies). ## Recover from an inverted rate or an incorrect VAT adjustment If an import divides USD 12,000 by 0.80, it records GBP 15,000 instead of GBP 9,600. The entry may still balance if every line uses the same wrong formula. Compare to the approved unit statement and control total; a balanced journal is insufficient. Stop the import, quarantine the affected batch and identify whether invoices or returns have already been issued. The controller approves the accounting correction and the tax owner decides whether issued documents or filings require correction. Reverse and repost through the supported process, retaining links to the original batch. A different failure appears when an exchange-adjustment routine changes the original GBP VAT payable simply because the USD receivable moved. Compare VAT entries and return totals before and after the routine. The tax owner must distinguish legitimate reporting-currency changes from an unintended change to the statutory sterling amount. Do not disable all currency adjustments as a blanket fix. Correct the relevant account, currency role or configuration, then rerun both the receivable and VAT reconciliations. ## Complete the operating handover Approve the process only when: - Every currency role and rate policy has an identified owner. - Quotation direction and rounding pass a known-value calculation. - The original invoice and sterling VAT amount remain traceable. - Partial settlements reduce the correct document and carrying balance. - Revaluation includes only the applicable open population. - The final settlement produces zero open balance and the correct cumulative gain or loss. - Reporting-currency differences remain distinguishable from statutory tax and accounting-basis adjustments. - Failed imports and issued-document corrections have a rehearsed owner-led recovery path. Retain the completed worksheet, rate evidence, journals, payment applications and before/after reports. Use [localization acceptance tests](https://erplocalization.com/guides/erp-localization-acceptance-tests/) for the wider test pack, and [parallel books](https://erplocalization.com/guides/parallel-books-local-gaap-group-reporting/) when accounting policies, rather than currency alone, differ. Source verification date: 17 October 2026. The archived IAS 21 passage supports the illustrated monetary-item mechanics; full current-standard and jurisdictional applicability review remains part of the entity's accounting policy approval. ## Worksheet: Currency policy and reconciliation worksheet Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment. Show the worksheet Use with [the invoice, tax, ledger and reporting currencies guide](https://erplocalization.com/guides/invoice-tax-ledger-reporting-currencies/). Keep this worksheet with the rate evidence and journal exports. Inputs are intentionally blank; the worked reference values are fictional. ### Assign currency roles and rate rules - Entity and reporting framework: - Transaction/invoice currency: - Functional/ledger currency: - Tax reporting currency: - Bank account and settlement currency: - Group presentation currency: - ERP family, edition, deployment, localisation and release/build: - Controller, tax owner, treasury owner and application owner: Repeat the following for initial accounting, tax conversion, settlement, closing revaluation and group translation. - Conversion purpose: - Rate as a unit statement, e.g. GBP 0.80 per USD 1: - Approved source and evidence location: - Applicable date rule: - Multiply/divide formula: - Rounding precision and residual treatment: - Fallback and approving owner: - Historical-rate preservation: ### Preserve the event chain - Invoice reference and original currency amounts: - Accounting recognition date: - Tax point and tax-conversion decision: - Issue-date journal reference: - Payment reference, bank receipt and invoice application: - Revaluation batch and open population: - Revaluation retained or reversed in the following period: - Final settlement reference: - Tax report and reporting-currency output references: ### Synthetic reference case Assume GBP functional currency, a completed UK domestic sale, a 20% VAT charge, coincident invoice/recognition/tax-point dates, no cash VAT scheme, fees, hedge or impairment. Receipts are immediately converted to GBP. October's revaluation remains posted into November. VAT has not yet been remitted at final settlement. - 1 October: USD 10,000 net + USD 2,000 VAT = USD 12,000 due. - Issue rate: GBP 0.80 per USD 1. - Opening receivable: GBP 9,600; revenue: GBP 8,000; output VAT: GBP 1,600. - 20 October: USD 6,000 paid at 0.82 = GBP 4,920 cash. - Historic carrying value settled: GBP 4,800; realised gain: GBP 120. - 31 October: remaining USD 6,000 × 0.85 = GBP 5,100. - Revaluation gain: GBP 5,100 - GBP 4,800 = GBP 300. - October check: assets 4,920 + 5,100 = 10,020; liability plus pretax profit 1,600 + 8,420 = 10,020. - 10 November: USD 6,000 × 0.83 = GBP 4,980 cash. - Final settlement loss: GBP 5,100 - GBP 4,980 = GBP 120. - Lifetime cash: GBP 9,900; lifetime FX gain: 120 + 300 - 120 = 300. - Final check: GBP 9,900 cash = GBP 1,600 VAT liability + GBP 8,300 pretax profit contribution. At October's 0.85 closing rate, translating the GBP receivable produces USD 6,000 and translating the GBP cash produces USD 5,788.24. These are balance-sheet line illustrations, not a complete group translation or a second accounting book. ### Negative test and approval The wrong operation USD 12,000 ÷ 0.80 gives GBP 15,000. A balanced import using that formula is still wrong. Check the original statutory GBP VAT amount separately after any currency-adjustment job. - Known-value test and actual result: - Open-document reconciliation result: - VAT before/after comparison: - Duplicate/reversal treatment: - Correction batch and issued-document review: - Accounting acceptance: - Tax acceptance: - Reporting acceptance: - Evidence location and retention owner: ## Related on this site - [Country pages](https://erplocalization.com/countries/): key facts with sources - [E-invoicing matrix](https://erplocalization.com/e-invoicing/): country × ERP support - [All guides](https://erplocalization.com/guides/) Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17. Related: [Glossary](https://erplocalization.com/glossary/) – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more). --- Canonical: https://erplocalization.com/guides/invoice-tax-ledger-reporting-currencies/ · Last updated: 2026-10-17 · Informational only; not tax, legal or implementation advice. Featured placements are paid or promotional and do not affect the compliance data. Data: CC BY-NC 4.0 (commercial use needs a licence: https://erplocalization.com/data-licence/), attribution "ERP Localization (erplocalization.com)".