Keep one approved exchange-rate register for reporting

Define which calculation needs the rate before selecting a number. Transaction recording, period-end remeasurement, and translation of financial statements can require different inputs. Ask the accountant to approve the convention under the company's reporting framework. A payment-provider conversion rate, treasury budget rate, and financial-reporting rate should not be treated as interchangeable without analysis.

IAS 21 addresses foreign-currency transactions and translation into functional or presentation currencies. Its central questions include which rates to use and how to report exchange effects. Keep the entity's approved functional and presentation currencies with the rate register so users understand the calculation they are performing.

Every rate should identify the base currency and quote currency in words as well as codes. State whether the calculation multiplies or divides. Preserve the source's notation and date. A plausible rate can be used backward without producing an obvious spreadsheet error, especially when both currencies trade near parity.

For a hypothetical rate of 1 euro = 1.10 U.S. dollars, €10,000 converts to $11,000 by multiplication. A separately stated rate of 1 U.S. dollar = 0.90909 euros expresses approximately the inverse. Do not round the inverse repeatedly across schedules. Agree sufficient calculation precision and apply presentation rounding only at the reporting stage.

Save the rate source, retrieval date, relevant market date, and approved method for averages or other required measures. Identify how the policy handles nonbusiness days and unavailable rates. The accountant should approve the convention; preparers should not choose whichever nearby date makes an account reconcile more closely.

Where a source provides several rate types, record the selected type and why it fits the accounting policy. Do not rely on a screenshot without the currency pair or timestamp. If a rate is supplied by a group team, retain the approved file version and any later corrections. Local preparers need to know whether a replacement rate requires refreshing previously submitted calculations.

Select a known amount and independently calculate its converted value. Compare the result across the trial balance translation, relevant disclosures, and supporting schedules. Investigate differences caused by rate direction, date, precision, or currency labels. A rate register is only useful if the downstream models use its approved inputs.

Separate a legitimate accounting difference from a configuration error. Different statement components may require different rate conventions under the approved framework. Do not force every line to the closing rate merely to simplify comparison. Keep an account-to-rate-purpose mapping and have the accountant review it when new balances or transactions appear.

If a rate is corrected, identify the affected currencies, periods, schedules, and reports. Retain the earlier rate file and explain the change. Recalculate the affected outputs and have the reviewer assess whether already distributed information needs replacement. A silently updated shared cell can change many reports without leaving a clear adjustment record.

Archive the approved register with the close and keep future-period updates separate. The next reviewer should be able to reproduce a historical translation using the historical inputs. Document any exception where an approved rate could not be applied and leave the accounting assessment with the responsible reviewer, especially where exchangeability or unusual market conditions complicate the choice.