In plain words
A remittance app charges a fee and also earns a spread on the exchange rate it gives the customer. It must decide whether it is a principal, controlling the transfer and bearing settlement and FX risk, or an agent relying on a partner to deliver. A principal recognizes the fee and the FX spread as revenue when the transfer completes; an agent recognizes only its net commission.
Why it matters
A remittance provider must determine whether it controls the transfer service before it is provided to the end customer (acting as principal, recognizing gross remittance fee and FX spread as revenue) or merely facilitates transfer through a correspondent bank or payout partner (acting as agent, recognizing only a net commission), and separately must determine whether the FX spread embedded in the exchange rate offered to the customer is itself revenue; burying FX spread inside a single all-in fee without disaggregation hides a material and separately-risky revenue source from users.
Diagnostic questions
Does the entity bear fulfillment responsibility to the beneficiary itself, or does a correspondent bank/payout partner bear that responsibility while the entity merely arranges the transfer? Does the entity set the exchange rate offered to the customer and bear FX/settlement risk, or does it pass through a rate set by a partner? Is the FX spread separately quantified (customer rate less the entity's own cost rate) from the flat transaction fee in both pricing and disclosure?
Recognition
1) Map the full remittance flow and identify who bears fulfillment responsibility to the beneficiary (the entity itself, or a correspondent bank/payout partner). 2) Assess who bears FX risk and settlement risk on the transaction, and who has discretion in setting the exchange rate offered to the customer. 3) Conclude principal (control over the transfer service, recognize gross fee plus FX spread) or agent (recognize only net commission) based on these indicators holistically, consistent with the general principal/agent framework. 4) Separately quantify the FX spread as the difference between the customer rate and the entity's own cost rate for the underlying conversion at the transaction date. 5) Recognize revenue at the point the remittance service performance obligation is satisfied (typically on successful transfer/payout confirmation). 6) Apply the conclusion consistently across similar corridors and partner arrangements, documenting any differences.
Measurement
Measure FX spread revenue as the difference between the exchange rate applied to the customer and the entity's own cost rate for the underlying currency conversion at the transaction date; ensure consistency between the principal/agent conclusion and how FX risk is actually managed and reported internally; where the entity hedges its FX exposure on remittance flows, assess whether hedge accounting under IFRS 9 is applied and disclosed appropriately.
Presentation & disclosure
Disclose: the principal versus agent judgment and its basis; a disaggregation of remittance revenue into flat transaction fees and FX spread/margin where both are separately meaningful to users; the entity's FX risk management approach for remittance flows; and consistency of the gross/net conclusion across corridors, explaining any exceptions.
Common mistakes
- Defaulting to gross (principal) presentation because the entity is customer-facing, without assessing who bears fulfillment and FX risk
- burying FX spread revenue within a single '
- transaction fee'
- revenue line without disaggregation
- inconsistent principal/agent conclusions across similar corridors or partner arrangements without documented rationale
- failing to separately track the entity'
- s own cost rate for conversion, making it impossible to isolate and audit the FX spread
- not reassessing the conclusion when a corridor moves from an owned-infrastructure model to a third-party payout partner model.
Simple example
A remittance app charges a customer a flat SAR 20 fee and applies an exchange rate that embeds a further SAR 15 spread on a SAR 5,000 remittance (the entity's own cost rate would have converted the equivalent foreign currency amount for SAR 15 less); having assessed that it bears settlement and FX risk and controls the payout, it recognizes SAR 35 of gross revenue (SAR 20 fee plus SAR 15 FX spread) rather than a net commission. Journal entries: (1) On accepting funds from the customer: Dr Cash 5,000 / Cr Payable to correspondent/payout partner (at entity's cost rate, i.e., SAR 4,965 equivalent) 4,965 / Cr Revenue, remittance fee 20 / Cr Revenue, FX spread 15. (2) On settling with the correspondent bank: Dr Payable to correspondent/payout partner 4,965 / Cr Cash 4,965.
Professional judgment
The principal versus agent conclusion for multi-party remittance networks, and separating FX spread from flat fees when priced as a single all-in rate to the customer, both require careful judgment and consistent application across corridors. Grey areas include: corridors where a local payout partner sets the final leg exchange rate independently, potentially shifting FX risk (and therefore the principal/agent conclusion) away from the entity for that specific leg; how to attribute FX spread when multiple currency conversions occur in a single remittance (e.g., SAR to USD to a third local currency); and whether a published 'mid-market rate plus disclosed margin' pricing model changes the substance of the FX spread versus an opaque embedded-margin model.
Source basis
IFRS 15 · Revenue from Contracts with Customers
Paragraph references
Verified against the official standard texts used in the IFRS Expert skill.
Related issues
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.