What is Unrealized FX Gain/Loss Revaluation at Period End?

Unrealized FX Gain/Loss Revaluation at Period End is an ERP workflow guide for Financial Accounting & General Ledger. It focuses on General Ledger / FX Revaluation.

What should a finance team verify before implementation?

Given an entity with open foreign-currency AR/AP/bank balances and a period-end spot rate loaded; when the controller triggers the FX revaluation run; then unrealized gain/loss journal entries are posted to the designated P&L accounts with offsetting BS entries, and a reversal entry dated the first day of the next period is auto-created; (negative) when the period-end rate has not been loaded then POST /revaluation returns 422 "fx_rate.period_end_rate_missing".

Unrealized FX Gain/Loss Revaluation at Period End

General Ledger / FX Revaluation is where ERP discipline either begins or breaks.

Unrealized FX Gain/Loss Revaluation at Period End 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: Period-end GL balances reflect current exchange rates, unrealized FX gain/loss is correctly classified in P&L, and the auto-reversal ensures the effect is removed at the start of the next period.

The control flow a finance team actually needs.

Workflow map for this ERP process, including exception handling and audit evidence.

Step 1

Revalue All Open Monetary Balances By...

Step 2

Use Period-End Spot Rate, Transmitted...

Step 3

Post Unrealized Gain/Loss To...

Step 4

Auto-Create Reversal Entry Dated First...

Step 5

Batch Processing With Preview

The ERP surface involved.

Module

General Ledger / FX Revaluation

Actors

Controller, 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

revalue all open monetary balances by currency pair; use period-end spot rate (stored as NUMERIC(20,10), transmitted as string); post unrealized gain/loss to configurable GL accounts; auto-create reversal entry dated first day of next period; batch processing with preview before commit; support partial revaluation (exclude specific accounts); revaluation journal tagged as system-generated for audit differentiation; no float on FX computation path

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	revalue all open monetary balances by currency pair	Given an entity with open foreign-currency AR/AP/bank balances and a period-end spot rate loaded
Control 2	use period-end spot rate (stored as NUMERIC(20,10), transmitted as string	when the controller triggers the FX revaluation run
Control 3	post unrealized gain/loss to configurable GL accounts	then unrealized gain/loss journal entries are posted to the designated P&L accounts with offsetting BS entries, and a reversal entry dated the first day of the next period is auto-created
Control 4	auto-create reversal entry dated first day of next period	`negative) when the period-end rate has not been loaded then POST /revaluation returns 422 "fx_rate.period_end_rate_missing".`
Control 5	batch processing with preview before commit	Period-end GL balances reflect current exchange rates, unrealized FX gain/loss is correctly classified in P&L, and the auto-reversal ensures the effect is removed at the start of the next period.
Control 6	support partial revaluation (exclude specific accounts	Period-end GL balances reflect current exchange rates, unrealized FX gain/loss is correctly classified in P&L, and the auto-reversal ensures the effect is removed at the start of the next period.

Audit evidence is a chain, not a folder.

Evidence layer	What should be preserved
Business event	At period end, the controller triggers the FX revaluation run for all open monetary balances denominated in foreign currencies (AR, AP, bank accounts, intercompany balances). The system fetches the period-end spot rate for each currency, recomputes the functional-currency equivalent of each open balance, and compares it to the carrying value on the GL. The difference is posted as an unrealized FX gain or loss to the designated P&L accounts, with offsetting entries to the balance sheet accounts. The revaluation journal is tagged as system-generated and reversible; the system auto-creates the reversal at the start of the next period. The controller reviews and approves the batch before final posting.
Control rules	revalue all open monetary balances by currency pair; use period-end spot rate (stored as NUMERIC(20,10), transmitted as string); post unrealized gain/loss to configurable GL accounts; auto-create reversal entry dated first day of next period; batch processing with preview before commit; support partial revaluation (exclude specific accounts); revaluation journal tagged as system-generated for audit differentiation; no float on FX computation path
Acceptance proof	`Given an entity with open foreign-currency AR/AP/bank balances and a period-end spot rate loaded; when the controller triggers the FX revaluation run; then unrealized gain/loss journal entries are posted to the designated P&L accounts with offsetting BS entries, and a reversal entry dated the first day of the next period is auto-created; (negative) when the period-end rate has not been loaded then POST /revaluation returns 422 "fx_rate.period_end_rate_missing".`
Data record	`fx_revaluation_runs { id: string, external_id: string, entity_id: string, period_id: string, status: enum(PREVIEW,POSTED,REVERSED), posted_by: string, posted_at: timestamptz }; fx_revaluation_lines { id: string, run_id: string, coa_account_id: string, currency_code: char(3), carrying_amount_minor: int64, revalued_amount_minor: int64, gain_loss_minor: int64, functional_currency_code: char(3) }; (reference, product may differ).`
System event	`POST /v1/fx-revaluations/preview { entity_id, period_id } -> 200 { lines:[{account, gain_loss_minor, currency_code}] }; POST /v1/fx-revaluations { entity_id, period_id, approved_by } -> 201 { id, reversal_entry_id, status: POSTED }; GET /v1/fx-revaluations/{id}; emits gl.fx_revaluation.posted and gl.fx_revaluation.reversal_scheduled events; idempotent via external_id.`
Lifecycle state	`PREVIEW -> POSTED; auto-transition POSTED -> REVERSAL_SCHEDULED; reversal auto-posts on first day of next period yielding REVERSED; guard: re-run replaces prior run's journals for same period.`

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_revaluation_runs` { id: string, external_id: string, entity_id: string, period_id: string, status: enum(PREVIEW,POSTED,REVERSED), posted_by: string, posted_at: timestamptz }; `fx_revaluation_lines` { id: string, run_id: string, coa_account_id: string, currency_code: char(3), carrying_amount_minor: int64, revalued_amount_minor: int64, gain_loss_minor: int64, functional_currency_code: char(3) }; (reference, product may differ).

API and events

`POST /v1/fx-revaluations/preview` { entity_id, period_id } -> 200 { lines:[{account, gain_loss_minor, currency_code}] }; `POST /v1/fx-revaluations` { entity_id, period_id, approved_by } -> 201 { id, reversal_entry_id, status: POSTED }; `GET /v1/fx-revaluations/{id}`; emits `gl.fx_revaluation.posted` and `gl.fx_revaluation.reversal_scheduled` events; idempotent via `external_id`.

State transitions

`PREVIEW -> POSTED`; auto-transition `POSTED -> REVERSAL_SCHEDULED`; reversal auto-posts on first day of next period yielding `REVERSED`; guard: re-run replaces prior run's journals for same period.

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.

Back to ERP use cases