Treasury / Multi-Currency is where ERP discipline either begins or breaks.
Missing or Stale FX Rate Fallback and Quarantine 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: No transaction is ever posted with a fabricated or wrong FX rate; rate gaps are made visible and resolve cleanly; functional-currency values are always backed by a real, dated quote.
The control flow a finance team actually needs.
Step 1
Never Default A Missing Rate To 1.0 Or...
Step 2
Defined Fallback = Last-Known Rate...
Step 3
Quarantined Transactions Are Queryable...
Step 4
FX Rate Stored As Decimal/String, Never...
Step 5
Rate Source + Rate Date Recorded On The...
The ERP surface involved.
Module
Treasury / Multi-Currency
Actors
FX Rate Service, Posting Service, Treasury, GL System
Tier
Tier 2
Finance area
Cross-Cutting Edge Cases & Failure Modes
Region lens
US and UK finance teams
Publication date
June 30, 2026
never default a missing rate to 1.0 or silently substitute; defined fallback = last-known rate within a configurable max-staleness window, else quarantine; quarantined transactions are queryable and auto-resolve when the rate posts; FX rate stored as decimal/string, never float; rate source + rate date recorded on the posted line; staleness beyond threshold alerts treasury; weekend/holiday calendar handled per currency; re-revaluation if a provisional rate is later corrected.
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 | never default a missing rate to 1.0 or silently substitute | Given a currency pair with no rate available on the required value date but a prior rate within the configured staleness window |
| Control 2 | defined fallback = last-known rate within a configurable max-staleness window, else quarantine | when a transaction requiring that rate is submitted |
| Control 3 | quarantined transactions are queryable and auto-resolve when the rate posts | then the system applies the last-known rate within the staleness window, records rate_source and rate_date on the posted line, and alerts treasury |
| Control 4 | FX rate stored as decimal/string, never float | when the staleness window is exceeded |
| Control 5 | rate source + rate date recorded on the posted line | |
| Control 6 | staleness beyond threshold alerts treasury | No transaction is ever posted with a fabricated or wrong FX rate; rate gaps are made visible and resolve cleanly; functional-currency values are always backed by a real, dated quote. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | A transaction requires an FX rate for a currency pair on a date for which the rate feed has not yet delivered a quote (feed outage, weekend/holiday, exotic pair). Rather than silently defaulting to 1.0 or an arbitrary stale value, the system applies a defined fallback policy - use the most recent prior rate within an allowed staleness window, or quarantine the transaction as pending-rate and post once the rate arrives - and never fabricates a rate. Transactions held for rate are visible and resolve automatically when the feed catches up. |
| Control rules | never default a missing rate to 1.0 or silently substitute; defined fallback = last-known rate within a configurable max-staleness window, else quarantine; quarantined transactions are queryable and auto-resolve when the rate posts; FX rate stored as decimal/string, never float; rate source + rate date recorded on the posted line; staleness beyond threshold alerts treasury; weekend/holiday calendar handled per currency; re-revaluation if a provisional rate is later corrected. |
| Acceptance proof | |
| Data record | |
| System event | |
| Lifecycle state | |
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` { id: string, from_currency: char(3), to_currency: char(3), rate: string, rate_date: date, source: string, created_at: timestamp }; `quarantined_transaction` { id: string, transaction_id: string, required_currency_pair: string, required_date: date, status: enum, resolved_at: timestamp, external_id: string }; (reference, product may differ).API and events
`GET /v1/fx-rates?from_currency=&to_currency=&at_date=` -> 200 { rate, rate_date, source } or 404 `fx_rate_missing`; `GET /v1/quarantined-transactions` -> list; `POST /v1/fx-rates` { from_currency, to_currency, rate, rate_date, source } -> 201; emits `fx_rate.posted` which triggers auto-resolution of matching quarantined transactions.State transitions
`PENDING_RATE -> RATE_RESOLVED -> POSTED`; guard: never substitutes 1.0 for missing rate; rate stored as decimal string not float; staleness-exceeded transitions to `PENDING_RATE`; auto-resolves on `fx_rate.posted` event for matching pair/date.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.