Foreign Currency Transactions IAS 21: Entries Guide
Record imports, export receivables, and month-end exchange differences without losing the IFRS logic behind the numbers.
What are foreign currency transactions IAS 21?
Foreign currency transactions IAS 21 are everyday business events that happen in one currency while the company keeps its books in another. A Saudi company may buy equipment in euros, invoice a customer in pounds, pay a software subscription in dollars, or hold a vendor balance that will be settled outside SAR. The accounting question is simple but easy to mishandle: what amount goes into the books today, and what changes when the exchange rate moves before settlement?
Under [IFRS](/glossary#ifrs), IAS 21 separates two ideas. First, record the transaction in the entity's functional currency using the spot exchange rate on the transaction date. For many Saudi operating companies, that functional currency is SAR because cash flows, pricing, payroll, and financing are mainly in Saudi riyals. Second, remeasure monetary balances at each reporting date using the closing rate. The exchange difference normally goes to profit or loss, which means it affects the [income statement](/learn/income-statement-explained), while the foreign-currency receivable or payable remains on the [balance sheet](/learn/balance-sheet-guide) at its updated SAR amount.
This is why foreign currency accounting is not just a treasury topic. It touches purchasing, sales, month-end close, audit support, and exam questions. The trick is to follow the sequence: identify the functional currency, translate the original transaction, decide whether the remaining item is monetary, remeasure at close if required, then record settlement. Once that sequence is clear, the journal entries become much less mysterious.
How do foreign currency transactions IAS 21 entries work?
Foreign currency transactions IAS 21 entries work best when you treat the exchange rate as part of the measurement step, not as a note added after the [journal entry](/glossary#journal-entry) is posted. The transaction document may say EUR 40,000, but the ledger must carry a SAR value. That SAR value is what flows into inventory, revenue, expenses, receivables, payables, and cash.
A clean entry usually answers four questions before anyone touches the accounting system:
- What is the foreign currency amount?
- What was the spot rate on the transaction date?
- Is the open balance monetary or non-monetary after initial recognition?
- What rate applies at the reporting date or settlement date?
The first entry records the asset, expense, revenue, receivable, or payable at the transaction-date rate. Later entries update only the monetary balance and recognize the exchange gain or loss. This is similar to the discipline in [how to record journal entries](/learn/how-to-record-journal-entries): the debit and credit must still explain the economic event, not just force the trial balance to agree.
The common exam shortcut is to memorize the table. The better work habit is to ask what still needs to be settled in cash. If cash will be received or paid in a foreign currency, IAS 21 normally treats that open balance as monetary and updates it at the closing rate.
Which exchange rate should you use under IAS 21?
IAS 21 uses different exchange rates because not every balance represents the same kind of measurement. A monetary item is a right to receive, or an obligation to deliver, a fixed or determinable number of currency units. Trade receivables, trade payables, bank loans, cash balances, and interest payable are common examples. These items are retranslated at the closing rate because the amount of SAR needed to settle or collect them has changed.
A non-monetary item is different. Inventory bought in euros and carried at historical cost is not retranslated every month just because the euro moved. Property, plant and equipment carried at cost follows the same idea. The asset was measured at the exchange rate on the transaction date, then tested or depreciated under the relevant standard. If a non-monetary item is carried at fair value, however, the rate used is normally the rate when that fair value was measured.
This classification matters inside the [general ledger](/glossary#general-ledger). If the accountant remeasures every foreign invoice line without separating monetary and non-monetary balances, the ledger will show movements that IAS 21 does not require. In practice, many teams maintain a foreign currency subledger for open receivables, open payables, and foreign bank accounts, then reconcile the SAR ledger to that subledger during close.
Worked example: importing inventory from Germany
Assume Najd Electronics Trading in Riyadh imports inventory from a German supplier for EUR 40,000 on 5 March. The invoice is payable in 45 days. The company's functional currency is SAR. On 5 March, the spot rate is 4.10 SAR for one euro, so the purchase is recorded at SAR 164,000. Ignore VAT and customs duty so the foreign currency mechanics stay visible.
The inventory is a non-monetary asset carried at cost, so it stays at SAR 164,000 unless another standard requires a write-down. The [accounts payable](/glossary#accounts-payable-ap) is monetary because the company must pay EUR 40,000. At 31 March, assume the closing rate is 4.18. The payable must now be shown at EUR 40,000 x 4.18 = SAR 167,200. The difference is SAR 3,200, an exchange loss, because the company needs more SAR to settle the same euro obligation.
On 19 April, Najd pays the supplier when the rate is 4.15. Cash paid is SAR 166,000. The payable before settlement is SAR 167,200, so the company records a SAR 1,200 exchange gain at settlement.
The key learning point is that the exchange loss at month end and the exchange gain at settlement are not corrections to inventory. They are consequences of carrying a monetary payable between the transaction date, reporting date, and settlement date.
Worked example: foreign customer receivable
Now assume Eastern Training Solutions provides an online IFRS course to a customer in the United Kingdom for GBP 20,000 on 10 May. The service has been delivered, the revenue recognition criteria are satisfied, and the invoice will be collected later. The spot rate on 10 May is 4.70 SAR for one pound, so the invoice is recorded at SAR 94,000.
The [accounts receivable](/glossary#accounts-receivable-ar) is a monetary item because the customer will pay GBP 20,000. At 31 May, the closing rate is 4.76. The receivable is now measured at GBP 20,000 x 4.76 = SAR 95,200. Because the pound strengthened against the riyal, the company expects to collect more SAR value than it initially recorded. That creates a SAR 1,200 exchange gain.
On 12 June, the customer pays when the rate is 4.72. Cash received is SAR 94,400. The receivable was sitting at SAR 95,200 after the month-end remeasurement, so the company records a SAR 800 exchange loss at settlement.
Notice the pattern: the revenue remains SAR 94,000 because that was the transaction-date translated amount. The exchange gain and loss are separate finance or operating line items depending on the company's presentation policy. Students often try to change revenue after collection, but IAS 21 does not use settlement-date exchange rates to rewrite the original sale.
How do you remeasure balances at month end?
Month-end remeasurement is where foreign currency transactions become a control issue. The accounting team needs a list of all open foreign-currency monetary balances, the original foreign amount, the carrying SAR amount before remeasurement, and the closing rate. Without that list, the adjustment becomes guesswork and the [trial balance](/learn/trial-balance-guide) may still balance while carrying the wrong SAR values.
A practical close file usually includes these columns:
- Vendor or customer name
- Invoice number or bank account
- Foreign currency amount outstanding
- Original SAR carrying amount
- Closing exchange rate
- Required SAR carrying amount
- Exchange gain or loss
- Link to the rate source or bank statement
For Saudi teams, the rate source should be documented consistently. If the group policy says to use bank spot rates, central bank rates, or a treasury-approved rate table, the close file should follow that policy every period. For currencies tightly linked to SAR, such as USD under the long-standing riyal-dollar peg, the movement may be small. The accountant should still document the rate used instead of assuming no movement.
The actual entry is posted after comparing the current SAR carrying amount with the required SAR amount. If a payable increases, debit exchange loss and credit payable. If a receivable increases, debit receivable and credit exchange gain. Then the remeasured balances should tie back to the foreign currency subledger. This is exactly why a [month-end close checklist](/learn/month-end-close-checklist) should include foreign currency remeasurement before financial statement review, not after the CFO has already signed off the numbers.
Common mistakes to watch for
The most common mistake is remeasuring the wrong thing. Inventory, equipment, and prepaid expenses are often connected to foreign invoices, but they are not automatically retranslated after initial recognition. The open payable is remeasured. The non-monetary asset carried at cost is usually not. Mixing those two ideas can overstate or understate gross profit, depreciation, and exchange differences.
A second mistake is using average rates for transactions that need spot rates. IAS 21 allows an average rate as a practical approximation when rates do not fluctuate significantly, but it should not be used blindly for a large one-off purchase, a volatile currency, or a transaction near period end. If the exam gives a spot rate, use it. If the close file has invoice dates and daily rates, use the policy-approved source.
A third mistake is netting gains and losses too early. Management may review a net exchange difference, but the working paper should still show which balances created gains and which created losses. Auditors and reviewers need to trace the movement from each open receivable, payable, or bank account.
A fourth mistake is treating settlement differences as corrections to the original transaction. The German inventory purchase example did not change inventory when the euro moved. The UK receivable example did not change revenue when cash arrived. The exchange difference explains the change in the SAR value of a monetary balance between dates.
Finally, do not ignore presentation. IAS 21 tells you how to translate and recognize exchange differences, but the company must also apply a consistent presentation policy. Some operating exchange differences may appear in operating profit; financing-related exchange differences may sit near finance income or cost. Consistency and clear notes matter, especially when foreign currency balances are material.
Practice foreign currency entries before close
Foreign currency entries become easy only after you practice the sequence several times: transaction date, reporting date, settlement date. Start with a payable, then a receivable, then a foreign bank account. For each case, write the foreign amount, the exchange rate, the SAR carrying amount, and the gain or loss. Do not jump straight to the final answer; make the movement visible.
A strong practice question should force you to decide whether the item is monetary, which rate applies, and whether the exchange movement is a gain or a loss. It should also ask you to explain why the asset or revenue is not changed after initial recognition. That explanation is what separates a student who memorized a debit-credit pattern from an accountant who understands IAS 21.
On Accountery, build this into your practice routine by recording the original invoice, posting the month-end remeasurement, and then settling the balance. Review the feedback as if you were checking a close file: Is the rate date correct? Is the balance monetary? Does the gain or loss direction make sense? Does the final payable or receivable clear to zero? Once you can answer those questions calmly, foreign currency transactions become a normal part of the close rather than a late-night reconciliation problem.