In plain words
Fintechs offering multi-currency wallets and cross-border transfers hold balances in foreign currencies. First, each entity determines its functional currency, the currency of its main economic environment. Then monetary items, such as cash, settlement payables and wallet liabilities, are retranslated at the closing rate on each reporting date, with exchange gains or losses in profit or loss. Non-monetary items carried at cost stay at the historical rate.
Why it matters
Fintechs offering multi-currency wallets, cross-border remittance and international scheme settlement carry monetary assets and liabilities in foreign currencies that must be retranslated at each reporting date, generating FX gains/losses that can be significant relative to thin payment margins; misidentifying functional currency or failing to retranslate wallet liabilities can materially misstate both the balance sheet and reported FX volatility in profit or loss.
Diagnostic questions
What is the functional currency of each group entity, determined by the primary economic environment driving pricing and costs, rather than the currency of invoicing alone? Are foreign-currency monetary items (settlement receivables/payables, wallet balances) retranslated at the closing rate at each reporting date, with exchange differences taken to profit or loss? Is any FX hedge relationship formally documented under IFRS 9 rather than relied upon informally?
Recognition
1) Determine the functional currency of each group entity based on the primary economic environment (the currency that mainly influences pricing and costs), not simply the currency of invoicing. 2) Classify each foreign-currency balance as monetary (cash, settlement receivables/payables, wallet liabilities) or non-monetary. 3) Retranslate monetary items at the closing rate at each reporting date. 4) Translate non-monetary items at the historical (transaction-date) rate and do not retranslate for subsequent FX movements. 5) Recognize exchange differences on monetary items in profit or loss unless they qualify for net investment hedge treatment on a foreign operation. 6) Document any hedge relationship under IFRS 9 hedge accounting if the entity manages FX risk through derivatives, and reassess functional currency if the primary economic environment changes (e.g., a new dominant revenue currency).
Measurement
Determine functional currency first (SAR for most KSA operations) before applying translation; use transaction-date rates for non-monetary items and closing rates for monetary items; consider whether a specific hedge relationship is documented for FX risk management under IFRS 9; measure any net investment hedge effectiveness and recognize the effective portion in OCI, with the ineffective portion in profit or loss.
Presentation & disclosure
Disclose: the functional currency determination basis for each significant group entity; net FX gains/losses recognized in profit or loss and where presented (operating versus finance); the entity's FX risk management policy and any hedging activity; and the currencies to which the entity has material exposure through wallets, remittance corridors, or scheme settlement.
Common mistakes
- Assuming functional currency equals the currency most invoices are issued in rather than analyzing the primary economic environment
- failing to retranslate multi-currency wallet liabilities at period end
- netting FX gains and losses across unrelated currency exposures without proper basis
- applying a single group-wide functional currency to all subsidiaries without a separate assessment for each
- forgetting that the SAR/USD peg does not eliminate FX risk on other currency pairs relevant to remittance corridors (EUR, GBP, EGP, PKR, etc.).
Simple example
A remittance fintech holds a USD 2,000,000 settlement payable to a correspondent bank; it was initially recognized at SAR 7.50/USD (SAR 15,000,000) and at period end the rate is SAR 7.53/USD. Journal entry at initial recognition: Dr Cash (received from customers) 15,000,000 / Cr Settlement payable, correspondent bank (USD) 15,000,000. At period end, retranslation entry: Dr FX loss (P&L) 60,000 / Cr Settlement payable, correspondent bank (USD) 60,000, bringing the payable to SAR 15,060,000 (USD 2,000,000 x 7.53). This is an unrealized loss recognized in profit or loss because the payable remains a monetary liability outstanding at period end.
Professional judgment
Functional currency determination for a multi-jurisdiction fintech group with mixed revenue and cost currencies can require significant judgment beyond the default assumption of local currency. Grey areas include: a KSA entity whose pricing is USD-linked and whose major cost base (e.g., cloud infrastructure, card scheme fees) is USD-denominated, which may point toward USD as functional currency despite SAR being the currency of the local operating environment; how to treat a holding company with no independent operations of its own; and whether the SAR/USD peg's stability should reduce the perceived urgency of FX risk management disclosures (it should not, given continued exposure to non-USD-linked currencies).
Source basis
IAS 21 · The Effects of Changes in Foreign Exchange Rates
Paragraph references
Verified against the official standard texts used in the IFRS Expert skill.
Related issues
- IFRS 15Principal vs agent in payment flows
- Professional JudgmentClient money segregation and balance sheet treatment
- IFRS 9Settlement receivables and float
- IAS 37Chargebacks and fraud loss provisions
- IFRS 9BNPL portfolio classification and expected credit losses
- IFRS 15Interchange and MDR revenue recognition
Educational and navigation content only. Not professional advice. Does not reproduce official IFRS/IAS text. Consult the authoritative standards and qualified professionals; professional judgment may still be required.
