The Complete Guide to Multi-Currency Accounting

Multi-currency accounting is the practice of recording transactions that are denominated in a currency other than your business's functional (base) currency, and converting them to the functional currency for reporting. A UK business with a EUR functional currency that invoices a US client in USD has a multi-currency transaction: the invoice is raised and paid in USD, but the books must reflect it in EUR.

The complexity is not the arithmetic — it is the timing. The exchange rate on the invoice date, the payment date, and any month-end revaluation date may all differ, and each difference creates a gain or loss that must be recorded. Get the rates or the timing wrong and your P&L, balance sheet, and VAT can all be distorted.

Your functional (base) currency is the currency of the primary economic environment in which your business operates — usually the currency of the country where you are based and where most of your costs are incurred. All foreign-currency transactions are converted into this currency for bookkeeping and reporting. Choosing the functional currency is an accounting judgement, not a daily preference; once set, it stays unless the business fundamentally changes.

Most small businesses have an obvious functional currency: the currency of the country where they are registered, employ staff, and pay rent. The complication arises when a business is registered in one country but trades predominantly in another — in that case the functional currency may differ from the registration currency, and professional advice is worth taking.

The general rule for each foreign-currency transaction is: use the exchange rate on the transaction date (the invoice date for a sale or bill, the payment date for a cash movement). For practical purposes, many small businesses use a rate from a reliable published source (their bank, a central bank, or an API like ECB orxe.com) on or close to the date.

At each month-end, any open foreign-currency balances (unpaid invoices, foreign-currency bank accounts) are revalued at the month-end rate, and the difference is posted as an exchange gain or loss. This is what keeps the balance sheet honest — an unpaid USD invoice on a EUR books will distort the numbers if the rate moves 5% and nobody revalues.

When you raise a sales invoice in a foreign currency, you record it in that currency and also in your functional currency at the invoice-date rate. When the customer pays — possibly weeks later, at a different rate — you record the cash in the foreign currency and recognise the exchange difference (gain or loss) between the invoiced functional-currency amount and the paid functional-currency amount. The same logic applies in reverse to supplier bills you receive in a foreign currency.

The practical pain is capture: a supplier invoice in USD with line items, tax, and totals in USD must be read correctly, converted at the right rate, and coded to the right category — all before you can match the eventual payment. AI invoice filing at {price} per processed invoice captures the foreign-currency fields accurately (supplier, invoice number, date, line items, totals, currency, tax), so the conversion and coding starts from correct data.

Exchange gains and losses arise in two ways. Realised: when an invoice is paid at a different rate than it was invoiced, the difference is a realised gain or loss and hits the P&L. Unrealised: at each reporting date, open foreign-currency balances are revalued to the closing rate, and the movement is an unrealised gain or loss — typically posted to the P&L or to a reserve depending on your accounting framework.

For most small businesses the practical workflow is: at month-end, run a revaluation report that lists every open foreign-currency balance, apply the month-end rate, post the differences to an exchange gain/loss account. Most accounting software automates this; the work is checking that the rates used are sensible and that no balance has been missed.

Foreign-currency transactions complicate VAT/sales-tax because the tax authority usually wants the tax reported in the local currency, at a specified rate (often the invoice-date rate or the VAT return period rate, depending on the jurisdiction). Get this wrong and the VAT reclaim or output tax is misstated, which can trigger penalties.

The safe approach for small businesses is: capture the foreign-currency invoice accurately (currency, amount, tax), convert at the rate your tax authority specifies, and keep both the foreign and functional currency figures on record so the calculation is auditable. AI invoice capture at {price} per invoice records both the original currency and the converted amount, which makes the VAT position defensible.

The bottleneck in multi-currency bookkeeping is accurate capture of the foreign-currency invoice itself: the supplier name, invoice number, date, line items, currency symbol, tax amount, and totals all need to be read correctly before any conversion happens. A misread currency or a transposed total propagates errors through conversion, VAT, and the eventual gain/loss calculation.

AI invoice filing at {price} per processed invoice reads foreign-currency invoices accurately — including the currency, the line items in that currency, and the tax — and files them with the original document archived for audit. Your accountant still chooses the rate, performs the revaluation, and signs off the gain/loss; AI just makes sure the starting data is right.

Using the wrong date for the exchange rate (e.g. payment date when invoice date was required, or vice versa). Forgetting to revalue open foreign-currency balances at month-end. Recording foreign-currency transactions directly in the functional currency without keeping the original — which makes audit and revaluation impossible. Misreading the currency on a supplier invoice (USD vs CAD, EUR vs GBP). Mixing personal and business foreign-currency transactions on the same account.

Most of these are capture or process errors, not arithmetic. Accurate capture of the foreign-currency invoice at {price} each, plus a disciplined month-end revaluation, removes the majority of them.