Help Center / Revenue Compliance

Multi-Currency Revenue Recognition

Multinational companies must handle revenue recognition across different currencies and tax regimes. Light stores every amount in three currencies and holds the original exchange rate across a release schedule, so revenue is recognised according to your accounting policies.

What is this page about

This page covers how Light handles currency in revenue recognition: the three currency perspectives it stores, which rate a release schedule uses, how FX revaluation works at period end, and how realised, unrealised and translation movements are kept apart. Read it if you recognise revenue in a currency other than your entity's own.

On this page

  • Multi-currency framework
  • Revenue recognition with FX rates
  • Override FX rates
  • Revenue recognition on transactions with rate changes
  • Handling FX revaluations
  • Multi-entity consolidation with deferred revenue
  • Currency translation differences
  • Reporting multi-currency deferred revenue
  • Best practices for multinational revenue recognition
  • Related articles

Multi-currency framework

Light operates with three currency perspectives:

Transaction currency: The currency of the original business transaction. If you invoice a customer in EUR, that's your transaction currency.

Local currency: The functional currency of the legal entity. A UK subsidiary operates in GBP, a German subsidiary in EUR.

Group currency: The consolidation currency for your entire organisation (often USD or EUR for multinational groups).

When you create a revenue transaction, Light automatically calculates and stores amounts in all three currencies, applying appropriate exchange rates at the transaction date (the valuation date).

Revenue recognition with FX rates

When revenue is recognised under a release template, each periodic release uses the FX rate from the original transaction date. This preserves the economically-agreed revenue amount while converting correctly for local and group reporting.

Example: You invoice a US customer for USD 12,000 on January 1 with a 12-month deferred revenue release (GBP entity, group USD):

  • Transaction currency: USD 12,000
  • Local (GBP) amount on Jan 1: GBP 9,500 at 1.2632 rate
  • Group (USD) amount: USD 12,000

Each month, Light releases USD 1,000 and GBP 791.67, maintaining the original exchange rate throughout the 12 months. This prevents distortions from changing FX rates between months.

Good to know: Light uses the valuation date (typically transaction date) for initial rate determination, then applies that rate consistently across all release periods.

Override FX rates

If your company locks rates internally, using monthly average rates rather than spot rates for example, you can supply your own rate for a document. Set the local currency or group currency rate override on the document, and Light uses your rate in place of its default lookup for that document.

You set this override through Light's API rather than on a screen in the app. See API access and custom integrations for how to authenticate and post documents.

Revenue recognition on transactions with rate changes

For long-duration recognition periods, you may experience significant FX volatility. Light preserves the original FX rate locked at transaction inception, ensuring:

  • Revenue amounts remain economically consistent
  • Variance analysis can isolate FX impacts from operational changes
  • Multi-month releases don't create artificial timing mismatches

If you need to adjust for subsequent FX movements, use the FX revaluation period task, which creates separate FX revaluation (FX) documents rather than modifying the original revenue release.

Handling FX revaluations

An FX revaluation document (FX type) records unrealised gains or losses from currency fluctuations. When held-to-maturity revenue or payables experience FX changes, FX documents systematically adjust reporting values.

FX revaluation documents are generated automatically by the FX revaluation task when closing an accounting period:

  1. Navigate to Accounting → Accounting periods
  2. Run the FX revaluation task for the period and the entities you are closing, using Run revaluations
  3. Light revalues open receivables and payables, accruals, and balances on accounts with Entity revaluation settings set to Revalue, and records a currency translation adjustment (CTA) for group currency
  4. Light automatically creates offsetting entries to P&L (unrealised gains and losses)

Generated FX documents appear in the task's Document revaluation section, and each one opens on its own page for review. To reverse one, use Void.

Multi-entity consolidation with deferred revenue

When deferred revenue spans multiple legal entities, each entity records its portion in its local currency. During consolidation:

  • Intercompany eliminations remove entries between entities
  • FX translation differences appear in other comprehensive income (OCI)
  • Deferred revenue remains correctly stated in both local and group currencies

Light automatically handles these consolidation mechanics, ensuring your consolidated P&L and balance sheet correctly present multinational deferred revenue.

Currency translation differences

Month-to-month FX fluctuations can create translation differences (especially for balance sheet items like deferred revenue). Light segregates:

  • Realised FX gains and losses: from actual transactions settled at different rates, posted to separate FX gain and FX loss accounts
  • Unrealised FX gains and losses: from balance sheet remeasurement at period-end rates
  • Translation differences: from consolidating foreign subsidiaries at current rates

This segregation is essential for IFRS and GAAP compliance, separating economic FX impacts from accounting translation mechanics.

Tip: Light posts realised gains, realised losses, unrealised movements, and translation adjustments to separate system accounts, which keeps variance analysis straightforward.

Reporting multi-currency deferred revenue

Your balance sheet reports deferred revenue in local and group currencies. Light's reporting engine:

  • Shows deferred revenue liability in each entity's functional currency
  • Translates balances to group currency at period-end rates
  • Separately identifies FX translation impacts

Every ledger line stores transaction, local, and group currency amounts, so any of the three can be reported on, but a P&L is an aggregate across many transactions in potentially different currencies, so it's presented in local or group currency, not in a single "transaction currency" view.

Best practices for multinational revenue recognition

Lock rates consistently: Decide whether to use spot rates, monthly average rates, or forward rates, then apply consistently across all entities.

Separate FX movements: Let the FX revaluation task record unrealised gains and losses in FX documents rather than adjusting revenue recognition, maintaining audit trail clarity.

Document rate source: Maintain a schedule of which rates were used for which transactions to support audit procedures.

Test translations: Review the FX revaluation output at each period end to check that translation differences fall within expected ranges.

Was this article helpful?

Book a demo