# IFRIC 22 Advance Payments: Foreign Currency Entries

> Apply IFRIC 22 advance payments rules with Saudi business examples. Track deposit rates, record delivery entries and separate exchange gains from revenue.

- Canonical page: https://accountery.app/learn/ifric-22-foreign-currency-advance-payments
- Language: English (en)
- Category: journal-entries
- Estimated reading time: 11 minutes
- Published: 2026-11-19
- Updated: 2026-11-19

## How do IFRIC 22 advance payments affect exchange rates?

IFRIC 22 advance payments create a practical question: a Saudi business pays a foreign supplier today and receives the goods later, so which day's exchange rate belongs in the cost? Start by identifying what the payment gives the business. A right to receive goods or services normally produces a non-monetary prepayment. Its historical exchange rate follows the prepaid portion into the related asset or expense when that item is recognised.

This matters whenever a contract has more than one payment date. A single purchase can contain several historical rates and a separate monetary balance. Treating the whole invoice as one foreign-currency payable can create an exchange loss that does not belong to the advance. A useful working paper therefore follows each payment from the bank record to the balance it creates and finally to delivery or service consumption.

The [IFRS Foundation's IFRIC 22 overview](https://www.ifrs.org/issued-standards/list-of-standards/ifric-22-foreign-currency-transactions-and-advance-consideration/) confirms that the interpretation addresses advance consideration paid or received in a foreign currency. This article concentrates on ordinary goods and service contracts measured at historical cost. It uses fictional Saudi businesses, assumed euro rates and the Saudi riyal as functional currency. The rates are teaching assumptions, not market quotations.

For the broader mechanics of initial recognition and settlement, read the [IAS 21 foreign-currency guide](/learn/foreign-currency-transactions-ias-21). Here the focus is narrower: preserving the rate attached to each advance, allocating it to the correct delivery, and keeping later exchange differences on unpaid balances separate. Taxes, bank charges, financing components, hedging and impairment are excluded from the numerical examples so that every difference can be traced to its cause.

## Which IFRIC 22 advance payments are non-monetary?

Read the contract before choosing a rate. A supplier advance that will be settled by delivering specified goods normally represents a non-monetary asset. A customer advance that will be settled by supplying goods normally represents a non-monetary contract liability. By contrast, a deposit carrying a right to repayment of a fixed amount of currency can be monetary. The account name “deposit” does not settle that question.

Write down the actual right or obligation in one sentence. For example: “The supplier must deliver the equipment covered by this payment.” Then check cancellation terms, refund provisions and whether those terms change the substance of the balance. A general statement that all advances are non-monetary is too broad. If the terms create a monetary balance, apply the relevant IAS 21 requirements instead of mechanically carrying forward a historical prepayment rate.

Paragraphs 8 and 9 of IFRIC 22 attach the rate to the date the non-monetary advance is initially recognised, with a separate date for each advance. The [equivalent text published by the Australian standard-setter](https://standards.aasb.gov.au/int-22-may-2019) reproduces that consensus; its Australian-specific provisions are separate from the IFRIC requirements discussed here.

The interpretation does not determine when equipment qualifies for recognition or when a seller has earned revenue. Those decisions come from the relevant accounting standard. Its scope also excludes certain initial fair-value measurements, and it need not be applied to income taxes or the specified insurance and reinsurance contracts. Keep these boundaries in view when reviewing unusual arrangements. A familiar payment schedule does not make every underlying transaction an ordinary historical-cost purchase.

## Build a rate schedule before posting the entry

Prepare one row for each advance and another for any amount first recognised on delivery. Record the contract reference, foreign-currency amount, recognition date, rate expressed as riyals per euro, resulting riyal amount and the delivery to which it relates. Use a consistent rate direction: multiply euros by riyals per euro. An inverse quotation needs conversion before it enters the same worksheet.

A [journal entry](/glossary#journal-entry) should then be the result of the schedule. On payment, debit the non-monetary supplier advance and credit cash. On delivery, transfer the relevant advance balance into the recognised asset or expense. Any unpaid portion becomes a separate monetary liability using its own initial recognition rate. The receipt of an invoice alone does not override the facts establishing recognition.

For multiple advances, retain the separate layers even if your software displays a combined supplier balance. A weighted effective rate may describe the total after the calculation, but it should not replace evidence for each layer. Where an advance covers several deliveries, document how it relates to those deliveries using the contract and the applicable accounting requirements. An arbitrary first-in-first-out allocation can shift cost or revenue between periods.

At month end, reconcile three things: foreign-currency amounts still outstanding, the carrying amount of the non-monetary advance, and any monetary receivable or payable. A zero balance on the original purchase order does not prove that all ledger accounts cleared correctly. Keep the original rate evidence and the delivery confirmation together so a reviewer can reproduce the calculation without rebuilding the entire contract history.

## Worked example: two advances for a machine

Nakhil Packaging, a fictional Dammam manufacturer, buys a machine for EUR 50,000. The contract requires two non-refundable advances that give rights to the machine, with the remaining amount payable after delivery. Assume the machine qualifies for recognition on 1 September, no earlier payable has arisen for the unpaid portion, and there are no other capitalisable costs. All entries below are in SAR.

| Event | Euros | SAR per euro | Riyal amount |
|---|---|---|---|
| Advance on 1 July | 15,000 | 4.00 | 60,000 |
| Advance on 1 August | 10,000 | 4.10 | 41,000 |
| Unpaid portion on 1 September | 25,000 | 4.20 | 105,000 |

On 1 July, debit supplier advances 60,000 and credit cash 60,000. On 1 August, debit supplier advances 41,000 and credit cash 41,000. The combined advance is now SAR 101,000. It remains at that historical amount for exchange-rate purposes even though the euro rate changes before delivery.

On 1 September, the machine's purchase-price component is 60,000 + 41,000 + 105,000 = **SAR 206,000**. Debit machinery 206,000, credit supplier advances 101,000 and credit [trade payables](/glossary#accounts-payable-ap) 105,000. The entry balances, both advance layers clear, and the remaining EUR 25,000 is visible as a monetary liability.

Suppose Nakhil pays the balance on 15 September at 4.25, with no intervening reporting date. Cash paid is SAR 106,250. Debit the payable 105,000, debit exchange loss 1,250 and credit cash 106,250. The later exchange loss does not increase the machine's purchase-price component in this ordinary unhedged example. Total cash paid, SAR 207,250, reconciles to machinery of SAR 206,000 plus the SAR 1,250 exchange loss. Depreciation and other subsequent accounting are separate steps.

## Worked example: a customer advance and later collection

Sahil Design, a fictional Riyadh studio, agrees to deliver one completed design package for EUR 20,000. The customer pays EUR 8,000 in advance on 1 October when the assumed rate is 4.00. The remaining EUR 12,000 becomes an unconditional receivable when the package is transferred on 1 November at 4.15. Assume the contract meets the relevant revenue criteria, there is one performance obligation satisfied at that point, and the advance is a non-monetary contract liability.

On 1 October, Sahil debits cash SAR 32,000 and credits the contract liability SAR 32,000. Receiving this cash does not itself complete the service. The liability records the obligation to deliver the package. Review the [revenue-recognition guide](/learn/ifrs-revenue-recognition) if the distinction between receiving cash and satisfying the performance obligation needs another example.

At delivery, the advance contributes SAR 32,000 to revenue, and the remaining consideration contributes 12,000 × 4.15 = SAR 49,800. Debit the contract liability 32,000, debit trade receivables 49,800 and credit revenue **SAR 81,800**. Translating the full EUR 20,000 at 4.15 would produce SAR 83,000 and overstate revenue by SAR 1,200 under these assumptions.

The customer pays on 20 November at 4.10, with no intervening reporting date. Debit cash SAR 49,200, debit exchange loss SAR 600 and credit trade receivables SAR 49,800. Total receipts are SAR 81,200, which reconcile to revenue of SAR 81,800 less the exchange loss of SAR 600.

This keeps [revenue recognition](/glossary#revenue-recognition) separate from the later monetary settlement. The historical advance layer is exhausted at delivery; only the remaining receivable is exposed to subsequent exchange-rate changes. If there were several performance obligations or delivery dates, first establish the appropriate allocation and recognition pattern under the revenue standard before building the currency schedule.

## What changes when a reporting date falls between events?

Suppose Nakhil reports on 31 August, before receiving the machine. Its two supplier advances total SAR 101,000. A different closing euro rate does not, by itself, create an exchange adjustment on those non-monetary historical-cost advances. The workpaper should still record whether delivery remains expected and whether another accounting assessment is needed; no exchange retranslation does not mean the balance is exempt from all review.

Now change the timing of Sahil's collection. Assume the EUR 12,000 receivable remains unpaid at a reporting date, when the closing rate is 4.12. Its translated balance becomes SAR 49,440. Compared with the original SAR 49,800, the company records an exchange loss of SAR 360. If it subsequently collects at 4.10, the additional loss is SAR 240. Together the two losses equal the same SAR 600 total in the earlier example.

This timing exercise shows why a settlement entry must start from the current carrying amount. Posting the full SAR 600 again after recording SAR 360 at the reporting date would double-count part of the loss. The same discipline applies to a supplier payable: identify what has already been recognised before calculating the next movement.

Foreign-currency cash retained in a bank account is also a separate monetary asset. The examples assume conversion into or out of riyals at the stated transaction rates. If the business retains euros instead, prepare a separate bank retranslation schedule. A non-monetary customer advance does not protect the associated cash balance from exchange differences. These are different balances with different settlement characteristics.

## Common mistakes and the evidence that resolves them

The most frequent error is using the delivery rate for the entire price. Resolve it by splitting the contract into amounts already represented by non-monetary advances and amounts first recognised on delivery. In the machinery example, the supporting evidence is the two payment confirmations and the delivery document, with their respective rates.

Another error is including every foreign-currency account in an automated month-end revaluation. Review account configuration and the nature of each balance. A supplier can have both an advance and an unpaid invoice. The supplier name is the same, but the balances require separate treatment. Investigate a combined control-account total before assuming it represents a single monetary item.

A third error is letting exchange movements alter previously recognised revenue. Once the performance obligation in the example is satisfied, subsequent collection differences relate to the receivable. Keep the original revenue calculation in the file and reconcile later receipts to that figure through exchange gains or losses.

Finally, do not substitute a payment date for a recognition judgment without checking the facts. A refundable cash deposit, a prior unconditional amount due, a fair-value measurement or a financing arrangement may require a different analysis. The [IFRS Foundation's IAS 21 overview](https://www.ifrs.org/issued-standards/list-of-standards/ias-21-the-effects-of-changes-in-foreign-exchange-rates/) provides the wider currency framework. For a real file, record the contractual terms and the applicable standard alongside your conclusion. The goal is a calculation another accountant can follow, with clear reasons for every date and rate.

## Practise the sequence from payment to settlement

Work through the two cases on a blank sheet before looking at the answers. Start with the foreign-currency timeline, classify each balance, and write the recognition date beside each amount. Then calculate the riyal layers and post the entries. Check that the advances clear only when the related goods or services are recognised and that monetary balances clear only when they are settled or otherwise derecognised.

For a second attempt, change one assumption at a time. Increase the first machinery advance and reduce the unpaid portion by the same euro amount. Recalculate the purchase-price component and explain why the exposure after delivery changes. Next, introduce a reporting date before collection in the design case and separate the exchange loss between the two periods. These variations test the reasoning behind the entry rather than recall of a total.

Finish with three controls: debits equal credits, total euro payments equal the contract price, and riyal cash reconciles to the asset or revenue plus or minus the relevant exchange differences. If one control fails, locate the first date on which your schedule diverges instead of adding a balancing figure.

Use Accountery's accounting practice exercises to rehearse the underlying entry and reconciliation skills alongside your course materials. Keep a short error note stating which balance you misclassified, which rate you selected and what evidence would have changed your decision. That note gives your next practice session a precise purpose and helps you explain the treatment in a review discussion.

---

Educational content from Accountery. Verify current standards, regulations, and authoritative sources before professional use.
