OHM · Workflows · Multi-currency
Multi-currency
The rate applied is the rate policy says, on both sides, every time.
Currency differences are rarely a rate error. They are two entities applying different rates on different dates to the same transaction, each consistent with its own habit.
The same step, two ways
How it runs today
- The rate applied depends on who booked it and what they had to hand.
- Revaluation surprises appear at the period end.
- Two sides of an intercompany entry are rated differently and both look defensible.
- Gains and losses are explained rather than predicted.
With the team on it
- The rate is taken from policy and the correct date, not from convenience.
- Both sides of an intercompany entry are rated on the same basis before posting.
- Exposure is visible as it accumulates rather than at revaluation.
- Differences are quantified as they arise, with their cause attached.
Who runs, and what they enforce
All of them, on the same foreign-currency entry, at the same time. Not a queue.
| Agent | What it enforces |
|---|---|
| Journal Agent | Entry balanced, support attached |
| Intercompany Agent | Counterparty entity agreed |
| Reconciliation Agent | Sub-ledger agrees to the control account |
| Period Agent | Posted in the open period |
| Report Agent | Books ready to report |
Agents without a link yet are part of the team but do not have a page written up.
What lands in your ERP
Foreign-currency entries rated on a stated policy, consistently across entities, with the difference between entities explainable line by line.
Rated
The stamp on a foreign-currency entry that cleared this step. It means every check ran and passed — not that a sample did, and not that it will be reviewed later.
See this step run on your last 90 days.
One export. No connector. We come back within a working day.
$Check your savings→