General Ledger / Multi-Currency is where ERP discipline either begins or breaks.
Multi-Currency Transaction Posting with FX Conversion 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: Every foreign-currency transaction has a permanently recorded exchange rate, both currency columns are accurate, the functional-currency trial balance balances, and FX gain/loss is computable at period end.
The control flow a finance team actually needs.
Step 1
Store Transaction Amount In Original...
Step 2
FX Rate Recorded Immutably Per Line
Step 3
All ISO 4217 Currencies
Step 4
No Float Arithmetic On Any Money Path
Step 5
Daily Spot Rate Feed Integration With...
The ERP surface involved.
Module
General Ledger / Multi-Currency
Actors
Accountant, AP/AR System, FX Rate Service, GL System
Tier
Tier 1
Finance area
Financial Accounting & General Ledger
Region lens
US and UK finance teams
Publication date
March 3, 2026
store transaction amount in original currency (amount_minor + currency_code) and functional-currency equivalent; FX rate recorded immutably per line at time of posting; support all ISO 4217 currencies including 0-decimal (JPY) and 3-decimal (BHD, KWD, OMR); no float arithmetic on any money path; daily spot rate feed integration with fallback to manual entry; FX rate change log; functional currency defined per entity, not per org
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 | store transaction amount in original currency (amount_minor + currency_code) and functional-currency equivalent | Given a USD-functional entity and a EUR invoice with an FX rate recorded for the transaction date |
| Control 2 | FX rate recorded immutably per line at time of posting | when the accountant posts the transaction |
| Control 3 | support all ISO 4217 currencies including 0-decimal (JPY) and 3-decimal (BHD, KWD, OMR | then both amount_minor + currency_code (EUR) and functional_amount_minor + functional_currency_code (USD) are persisted on the journal line, and the FX rate is immutably stored |
| Control 4 | no float arithmetic on any money path | |
| Control 5 | daily spot rate feed integration with fallback to manual entry | Every foreign-currency transaction has a permanently recorded exchange rate, both currency columns are accurate, the functional-currency trial balance balances, and FX gain/loss is computable at period end. |
| Control 6 | FX rate change log | Every foreign-currency transaction has a permanently recorded exchange rate, both currency columns are accurate, the functional-currency trial balance balances, and FX gain/loss is computable at period end. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | |
| Control rules | store transaction amount in original currency (amount_minor + currency_code) and functional-currency equivalent; FX rate recorded immutably per line at time of posting; support all ISO 4217 currencies including 0-decimal (JPY) and 3-decimal (BHD, KWD, OMR); no float arithmetic on any money path; daily spot rate feed integration with fallback to manual entry; FX rate change log; functional currency defined per entity, not per org |
| Acceptance proof | |
| Data record | |
| System event | |
| Lifecycle state | FX rate record is immutable once posted to a journal line; manual rate entry requires controller approval before posting; rate override logged in audit trail. |
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
`journal_entry_lines` { id: string, journal_entry_id: string, external_id: string, coa_account_id: string, amount_minor: int64, currency_code: char(3), functional_amount_minor: int64, functional_currency_code: char(3), fx_rate: string, fx_rate_source: string, fx_rate_date: date }; `fx_rates` { id: string, from_currency: char(3), to_currency: char(3), rate: string, rate_date: date, source: string }; (reference, product may differ).API and events
`POST /v1/fx-rates` { from_currency, to_currency, rate, rate_date, source } -> 201 { id }; `GET /v1/fx-rates?from_currency=EUR&to_currency=USD&rate_date=2024-01-31`; `POST /v1/journal-entries` includes functional_amount_minor auto-computed from rate; emits `gl.fx_rate.applied` event; idempotent via `external_id`.State transitions
FX rate record is immutable once posted to a journal line; manual rate entry requires controller approval before posting; rate override logged in audit trail.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.