Ingenuity. Skill. Financial Control.

Multi-Currency GRNI Across Three Functional Currencies

Multi-currency GRNI can quietly erode confidence in inventory valuation and month-end reporting because timing differences and FX movement rarely line up. As a CFO, you don’t need more “reports”—instead, you need numbers that reconcile cleanly, stand up to audit scrutiny, and remain consistent across statutory and management views.

That’s precisely why we built a capability at the intersection of operational reality and financial control.

When you receive inventory in a transaction currency, FX rates can move between receipt and supplier payment. So we designed the process to recognise FX movement correctly across three functional currencies. At the same time, we ensure multi-currency GRNI revalues correctly in each book.

Multi-Currency GRNI Across Three Functional Currencies

Why Multi-Currency GRNI Breaks Down Between Receipt and Payment

Under IFRS, IAS 21 explains how entities account for foreign currency transactions and exchange differences. Additionally, IAS 2 establishes the principles for inventory measurement. Therefore, when receipt timing, settlement timing, and FX movement don’t align, Finance must manage both inventory valuation and exchange differences carefully.

Moreover, when determining the relevant “transaction date” for exchange rates in specific scenarios, IFRIC 22 can provide useful additional context.

In real operations, the timeline usually looks like this:

• You received the inventory today.
• Then you post the invoice later.
• Next, you pay the supplier later still.
• Meanwhile, FX rates move between those dates.

Once you run multiple functional currencies, the complexity rises quickly. For example:

• The same transaction must produce consistent results in three currency views.
• You must recognise FX gain/loss at the right point, not weeks later at close.
• Additionally, GRNI must revalue per book, not just in the primary view.

If you enter a multi-currency GRNI incorrectly, GRNI won’t clear cleanly. As a result, inventory valuation varies by ledger view, and month-end turns into a cycle of manual journals and tie-outs.

What We Built: System-Native Multi-Currency GRNI Handling (with Controls)

We built this capability to integrate seamlessly with the ERP, not as a spreadsheet patch. As a result, it remains predictable, supportable, and repeatable.

Specifically, our solution:

• Recognises the gain/loss between receipt and payment correctly across three functional currencies.
• Post the right G/L differences between the transaction currency and each functional currency.
• Keeps multi-currency GRNI revaluation correct in each book, so every view stays internally consistent.

Crucially, we align the approach with ERP posting logic. Consequently, Finance teams can rely on the process without resorting to “close-only fixes”.

For more information on how we combine functional and technical delivery, see our perspective on the functional and technical edge.

Controls for Multi-Currency GRNI: “Correct” Isn’t Enough

Accuracy matters. However, issues of control matter just as much. So we wrapped the accounting in governance:

• First, we route journals through a review step before posting.
• Then, we restrict posting and confirmation by security role, so only authorised users can confirm FX-sensitive journals.

Controls for Multi-Currency GRNI: “Correct” Isn’t Enough

CFO Outcomes: Lower Close Risk, Stronger Auditability, Better Margin Confidence

1. Reduced close risk and manual effort, because GRNI clears and revalues correctly per book.
2. A stronger audit posture, as the process produces clearer evidence trails and consistent logic.
3. More reliable inventory and margin reporting, because each functional currency view stays stable and is explainable.

If you’re dealing with complex ERP finance processes, explore our Epicor functional services and broader services pages.

Finally, if multi-currency inventory and GRNI revaluation create noise in your close, we can help you stabilise it with a controlled, system-native approach.
Contact Us.