Controlling — FX Rate & Planning Assumption Registry
Planning needs approved FX rate sets and assumption packs. Every forecast should cite the same official inputs.
Why this is needed
- Teams mix ECB spot, budget FX, and ad-hoc sheets.
- AI forecast agents must not pull random web rates for official plans.
- Auditable assumptions improve forecast governance.
Proposed entities in EntiHub
Governance settings
| Setting | Recommended value | Why |
|---|---|---|
approvalRequired |
true |
Budget FX is a controlled finance artifact. |
historyEnabled |
true |
History for scenario comparisons. |
allowSameAuthorApproval |
false |
Maker/checker separation for sensitive changes. |
deletedRetentionDays |
90 (or higher) |
Soft-delete retention for auditability. |
Entity definition (YAML sketch)
name: fx_rate_set
displayName: FX rate set
domain: Finance
description: FX rate set
version: "1.0.0"
approvalRequired: true
historyEnabled: true
deletedRetentionDays: 90
displayRefColumn: set_code
uniqueConstraints:
- name: uq_fx_rate_set_set_code
columns: [set_code]
columns:
- name: set_code
dataType: string
nullable: false
maxLength: 32
- name: name
dataType: string
nullable: false
maxLength: 128
- name: purpose
dataType: string
nullable: false
maxLength: 32
- name: status
dataType: string
nullable: false
maxLength: 16
- name: effective_from
dataType: date
nullable: false
YAML sketches
Sketches highlight the important fields and governance flags. Trim or extend columns to match your domain. See Setup Entity for the full YAML reference.
Sample data
| set_code | name | purpose | status | effective_from |
|---|---|---|---|---|
| BUDGET_FX_2026_V2 | Budget FX 2026 v2 | budget | approved | 2026-01-01 |
| FCST_FX_2026_Q3 | Forecast FX Q3 | forecast | approved | 2026-07-01 |
Benefits for the company
- All planning models share one FX set code.
- Scenario assumptions are explicit.
- AI agents cite EntiHub for official plans.