Multi-Currency AR is where ERP discipline either begins or breaks.
Handle Multi-Currency Invoice and FX Cash Application looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Multi-currency invoices are correctly converted; FX gains/losses are accurately reported; AR is fully closed in both transaction and functional currencies.
The control flow a finance team actually needs.
Step 1
Every AR Invoice Store Amount Minor And...
Step 2
Functional Currency Amount At Invoice...
Step 3
FX Rate Be Fetched From The Configured...
Step 4
FX Gain/Loss Journal Entry Be...
Step 5
FX Rates Never Use Float64
The ERP surface involved.
Module
Multi-Currency AR
Actors
AR Clerk, FX Rate Engine, Customer
Tier
Tier 1
Finance area
Accounts Receivable & Order-to-Cash
Region lens
US and UK finance teams
Publication date
March 21, 2026
Every AR invoice must store amount_minor and currency_code; functional currency amount at invoice date must also be stored for FX computation; FX rate must be fetched from the configured rate source (manual, ECB, provider API) and stored as NUMERIC(20,10); FX gain/loss journal entry must be auto-generated on cash application; FX rates must never use float64 (precision loss); period-end unrealized FX revaluation must be separately supported; non-functional: FX rate fetch and entry creation < 2 seconds.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Every AR invoice must store amount_minor and currency_code | Given an invoice in GBP for a USD-functional-currency entity, with spot rate stored at invoice date |
| Control 2 | functional currency amount at invoice date must also be stored for FX computation | when a GBP payment is applied at a different spot rate on the payment date |
| Control 3 | FX rate must be fetched from the configured rate source (manual, ECB, provider API) and stored as NUMERIC(20,10 | then system converts payment to USD at payment-date rate, computes FX gain/loss as (USD at payment rate - USD at invoice rate), posts FX gain/loss GL entry, and closes the GBP AR balance |
| Control 4 | FX gain/loss journal entry must be auto-generated on cash application | negative) when fx_rate is provided as a float64 value then 422 FX_RATE_MUST_BE_STRING_DECIMAL is returned. |
| Control 5 | FX rates must never use float64 (precision loss | Multi-currency invoices are correctly converted; FX gains/losses are accurately reported; AR is fully closed in both transaction and functional currencies. |
| Control 6 | period-end unrealized FX revaluation must be separately supported | Multi-currency invoices are correctly converted; FX gains/losses are accurately reported; AR is fully closed in both transaction and functional currencies. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | Entity functional currency is USD; a UK customer is invoiced in GBP; invoice is posted at the spot exchange rate on invoice date (DR AR GBP, CR Revenue USD at spot rate); customer pays in GBP 30 days later at a different spot rate; cash application converts the GBP payment to USD at the payment-date rate; the system computes the FX gain or loss as the difference between the USD amount recorded at invoice date and the USD amount at payment date; a journal entry posts the FX gain/loss to the FX income/expense account; the AR balance in GBP is fully closed. |
| Control rules | Every AR invoice must store amount_minor and currency_code; functional currency amount at invoice date must also be stored for FX computation; FX rate must be fetched from the configured rate source (manual, ECB, provider API) and stored as NUMERIC(20,10); FX gain/loss journal entry must be auto-generated on cash application; FX rates must never use float64 (precision loss); period-end unrealized FX revaluation must be separately supported; non-functional: FX rate fetch and entry creation < 2 seconds. |
| Acceptance proof | Given an invoice in GBP for a USD-functional-currency entity, with spot rate stored at invoice date; when a GBP payment is applied at a different spot rate on the payment date; then system converts payment to USD at payment-date rate, computes FX gain/loss as (USD at payment rate - USD at invoice rate), posts FX gain/loss GL entry, and closes the GBP AR balance; (negative) when fx_rate is provided as a float64 value then 422 FX_RATE_MUST_BE_STRING_DECIMAL is returned. |
| Data record | |
| System event | |
| Lifecycle state | invoice closes when GBP AR balance = 0; FX entry posts atomically with payment application; unrealized revaluation is a separate periodic process. |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`fx_rate` { currency_from: char(3), currency_to: char(3), effective_date: date, rate: string(NUMERIC 20,10), source: enum }; `sales_invoice` includes: invoice_currency_code: char(3), invoice_amount_minor: int64, functional_currency_code: char(3), functional_amount_minor: int64, fx_rate_at_invoice: string; `fx_gain_loss_entry` { invoice_id: invoice_*, payment_id: pay_*, gain_loss_minor: int64, currency_code: char(3), journal_entry_id: je_* }; (reference, product may differ).API and events
`POST /v1/fx-rates` { currency_from, currency_to, effective_date, rate: string } -> 201; `POST /v1/customer-payments/{id}/apply` accepts fx_rate as string decimal; emits `ar.fx_gain_loss.posted`; rate stored as NUMERIC not float.State transitions
invoice closes when GBP AR balance = 0; FX entry posts atomically with payment application; unrealized revaluation is a separate periodic process.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.