Localization and Currency

Backlog field	Value
Story ID	CTRL-007
Epic	Cross Cutting Controls
Story type	Usability/accounting control
Review status	Draft - business analyst and business owner review required
Source evidence	Culture files, language service, localized names, currency conversion, stored local amounts
Last source review	2026-07-10

As a bilingual finance user, I want consistent Arabic/English identity and currency conversion so that entry, print, export, and accounting remain understandable and reconcilable.

Machine IDs/codes are language-independent. Required localized fields are validated per feature. Posted documents store their currency rate/local amounts. Base-currency rate is 1; missing effective rates block posting.