Start with the currency basis, not the bank account
Multi-currency bookkeeping becomes unreliable when the original invoice, the accounting entry and the bank settlement are treated as the same amount. They represent different stages. A customer can pay the exact dollars owed while the euro value changes. A provider can deduct a fee without changing the customer’s contractual debt. Good records preserve these distinctions throughout the transaction.
Under IAS 21, functional currency reflects the primary economic environment of the business. Incorporation in Cyprus does not settle that assessment by itself. Presentation currency is a separate matter. Document the accountant’s assessment before choosing the software’s base currency; the examples here assume a euro functional currency.
This guide concerns ordinary invoices, bank accounts and period-end controls. Group consolidation, hedging, restricted currencies and complex financial instruments need additional analysis. A trading platform’s account label is not sufficient evidence of accounting classification. Establish what the company owns, owes or trades before applying a routine designed for customer invoices.
Keep the information needed to reconstruct each transaction
For every invoice retain the document currency, original amount, recognition date, due date, counterparty and reference. Alongside these, keep the translated value, rate, rate convention and source. Where the invoice date differs from the date the transaction qualifies for accounting recognition, record the reason and supporting evidence rather than silently using whichever date the import supplied.
Store the settlement reference separately. One invoice may have several receipts, and one bank receipt may cover several invoices. A usable allocation schedule shows how much of the original currency debt each payment clears. It also distinguishes credit notes, discounts, withholding, disputed balances and processing deductions. These are not interchangeable explanations for a short receipt.
Keep both currency columns when exporting reports. An export containing only euros can conceal an unpaid dollar balance, while an export containing only dollars cannot explain the ledger. The receivables guide covers allocation and collection controls. Here, the additional task is maintaining the connection between original units and their accounting values.
Make the rate convention explicit
A rate of EUR 0.90 per USD means multiply dollars by 0.90 to obtain euros. A quotation expressed as dollars per euro requires division instead. Put the convention in the column heading, not just in a preparer’s memory. Before importing a rate table, test one known transaction and review whether an unusually large or small result indicates inversion.
Define who approves rate sources and how missing dates are handled. Retain dated evidence or an accessible system record. The ECB reference-rate page is an information source, not a promise of a rate available from a bank; the ECB discourages using those rates for transaction purposes. Actual conversion proceeds and provider charges therefore need their own evidence.
Agree the appropriate accounting rate policy with the accountant. An average should not be accepted merely because software offers it: determine whether it reasonably approximates relevant transaction-date rates. Significant movements or a concentrated large transaction may make a broad average unsuitable. Keep any override, its reason and approval visible so another person can reproduce the calculation.
Worked example: invoice, conversion and fee
Assume an ordinary USD 10,000 service invoice is recognised when the applicable rate is EUR 0.90 per USD. Ignore VAT and other taxes for this illustration. The initial receivable and revenue are €9,000. The customer later pays the full USD 10,000 and the provider converts it at EUR 0.92 per USD, producing €9,200 before a separately identified €30 fee.
| Stage | Calculation | Euro amount |
|---|---|---|
| Initial invoice recognition | USD 10,000 × 0.90 | €9,000 receivable |
| Gross conversion on settlement | USD 10,000 × 0.92 | €9,200 |
| Exchange movement | €9,200 − €9,000 | €200 gain |
| Separately charged fee | Provider statement | €30 expense |
| Net euro cash received | €9,200 − €30 | €9,170 |
In this simplified example, debit euro cash €9,170 and the fee expense €30, credit the receivable €9,000 and the exchange gain €200. Debits and credits both total €9,200. Posting €9,170 as new sales would duplicate revenue; posting only a €170 exchange gain would hide the separately documented fee. The customer’s invoice is fully settled.
The example assumes no intervening reporting-date retranslation. If one occurred, settlement must take account of the carrying amount already recorded. It also assumes the fee is separately stated. Do not invent a fee by treating every difference from a public reference rate as a bank charge. Preserve the provider’s actual conversion statement and contractual charges.
Retranslate eligible open balances without duplicating gains
Ordinary foreign-currency monetary balances generally use the closing rate at a reporting date under IAS 21. Historical-cost non-monetary items follow a different rule. The standard’s transaction and closing-rate principles explain why revaluing every foreign-currency purchase indiscriminately is wrong. Review classification before running a bulk software routine.
Return to the USD 10,000 receivable, initially €9,000. Suppose it remains unpaid at a reporting date when the appropriate rate is EUR 0.91 per USD. Its translated balance becomes €9,100, with a €100 exchange gain under these assumptions. If it then settles at €9,200 gross, the additional gain from that carrying amount is €100, not another €200.
The lifetime gain is €200. Software may reverse a closing adjustment and calculate settlement from the original entry, or maintain the adjusted carrying amount. Understand which method your system uses. Review the combined entries across both periods. Mixing methods or manually repeating an automatic revaluation can overstate the result while the bank account still appears reconciled.
Handle partial payments in original currency
Assume the same USD 10,000 invoice was initially recorded at €9,000, but only USD 4,000 is settled at EUR 0.92 per USD, with no fee and no earlier retranslation. The settlement is €3,680. It clears €3,600 of the original receivable and generates an €80 gain. The unpaid debt remains USD 6,000, initially represented by €5,400.
At a later reporting date with a rate of EUR 0.91 per USD, those remaining USD 6,000 translate to €5,460, a further €60 gain in this example. Keep the €80 settlement difference and €60 retranslation identifiable. A single unexplained adjustment of €140 tells the reviewer less about what was paid and what remains exposed to currency movement.
Do not leave a small euro residual on a fully paid foreign invoice simply because different rates were used. Equally, do not write off a genuine unpaid foreign amount as an exchange difference. Match original-currency allocations first, investigate credit notes or deductions next, and only then determine the exchange entry from the supported accounting values.
Reconcile each currency account in two stages
First reconcile the units on each bank or wallet statement to the matching ledger: dollars to dollars, pounds to pounds. Investigate missing receipts, duplicated imports, charges and transfers. A euro-only comparison can conceal an original-currency error because an exchange adjustment happens to offset it. The bank reconciliation routine remains the foundation.
Then explain the functional-currency carrying amount using opening value, translated transactions and closing adjustments. If a customer pays into a dollar account, settlement of the invoice does not mean those dollars were converted into euros. The dollar cash balance remains a separate item requiring its own subsequent accounting. Avoid recording an imaginary conversion that never occurred.
For transfers between the company’s own accounts, connect both statement references. A USD account outflow and a euro account inflow are not a new purchase and a new sale. Use a controlled transfer or clearing process, account for supported conversion differences and fees, and investigate any unmatched balance rather than leaving it indefinitely in suspense.
Use a currency-specific closing checklist
| Control | Evidence | Question to resolve |
|---|---|---|
| Original units reconcile | Bank and subledger reports | Are differences genuine timing items or missing entries? |
| Open items are complete | Receivable and payable lists | Were paid invoices wrongly left open? |
| Rates are supportable | Dated rate record and policy | Is the direction and date correct? |
| Revaluation is controlled | Journal and prior-period bridge | Has an automatic entry been duplicated? |
| Charges remain visible | Provider statements | Are fees confused with exchange movements? |
Assign responsibility for preparing and reviewing the schedule. Include account, original balance, applicable rate, expected translated amount, ledger amount and proposed difference. Investigate material or unusual movements before posting. A large gain can arise from an inverted rate just as easily as from an economic change; a plausible overall profit is not validation.
Make the schedule part of the monthly close. Keep the final approved version and journal references. If a late invoice changes an earlier period, assess the related exchange entries together rather than adjusting only the invoice. A controlled reopening should leave a trail explaining what changed and why.
Keep accounting, income tax and VAT decisions separate
Cyprus income-tax treatment does not automatically follow the ledger’s exchange account. Section 8(24) of the Income Tax Law exempts qualifying exchange gains arising from rate fluctuations, with an exception for currency trading and specific provisions concerning that activity. Classification and the applicable facts matter; a foreign customer invoice does not by itself make the company a currency trader.
Preserve the accounting result and prepare a separate tax reconciliation identifying relevant gains, losses and the legal basis for adjustments. Do not delete genuine ledger entries to obtain a desired taxable figure. Where derivatives, treasury activities or currency trading are involved, obtain a specific assessment rather than extending an ordinary trade-invoice example to those arrangements.
VAT conversion and invoice requirements must also be checked for the relevant supply. The date and evidence required for a tax purpose should not be assumed from a bookkeeping software default. Retain the applicable invoice and tax calculation alongside the ledger bridge. The VAT invoice guide addresses document requirements separately.
Explain currency effects in management reporting
Show trading performance and material exchange movements clearly in the management accounts. Explain whether a movement relates to settled transactions, open balances or cash held. A retranslation gain may increase accounting profit without providing extra euros to pay salaries. Decision-makers need that distinction when assessing margins and liquidity.
For the cash forecast, state the assumed collection currency, timing and conversion rate. Test an adverse rate scenario for significant expected receipts or payments. Do not present today’s reference rate as a guaranteed future conversion. The objective is to expose sensitivity and funding needs, not to predict the currency market.
Investigate rounding and manual overrides
Agree the rate precision and rounding settings across invoicing, imports and the general ledger. Translating individual lines and rounding each line can differ slightly from translating the document total. Keep the source amounts and identify that mechanism before classifying a small residual. Do not use a broad rounding account to absorb missing payments, wrong currencies or repeated import errors.
When a manual override is necessary, retain the original rate, replacement rate, calculation, reason and approver. Review recurring overrides by provider or user. If a feed repeatedly selects the wrong currency or date, correct the mapping and assess affected transactions instead of making a fresh unexplained adjustment every month. Limit changes to approved periods and document any consequential revaluation correction.
Build a file another bookkeeper can continue
Keep the functional-currency assessment, rate policy, invoice register, original-currency allocations, provider statements, bank reconciliations, closing schedules and tax bridge together. Record which revaluation entries reverse and which remain in the ledger. A replacement preparer should be able to follow one transaction from invoice to settlement without reconstructing undocumented conventions.
Before changing software, test an open invoice, a partial payment, a foreign bank balance and a cross-currency transfer. Confirm that the migration preserves original units as well as translated amounts. Agree opening balances and retain the old reports. Correct configuration at the start is more reliable than repeatedly clearing unexplained differences after every import.