Multi-currency consolidation and FX translation logic
Currency translation is arithmetic with policy attached: which rate, which date, which account class, which entity. It is the wrong place for probabilistic output.
Octopus AI applies translation deterministically using the customer's configured rate sources and policy, and records the inputs used for each translated figure.
The language layer explains a translated result. It never derives one.
Questions and answers
How are FX rates applied?
Deterministically, from the customer's configured rate source, according to the customer's translation policy by account class and period. The rate used is recorded with the resulting figure.
How are rate revisions handled?
Rate sources are versioned. When a rate changes, affected results are recomputed and the adjustment is documented, so the prior figure remains explainable.
Can an AI system explain an FX movement?
Yes, once the movement is computed. The system separates the translation effect from the underlying operational movement and asks the responsible owner for commentary on the operational part.
Is FX exposure tracked as well as translated?
Yes. Multi-currency exposure tracking, hedging-opportunity identification, and FX impact reporting are part of the FX workflow, with the same deterministic and approval-gated controls.
Proof
- Reference client: $523K total contract value over 3 years.
- Approximately 430 analyst hours saved.
- Forecast cycle cut from about 60 hours to under 6 hours (90% faster).
- Error rate below 0.1%.
- 2,500+ autonomous tasks completed in month one.