Problem statement
Global fund administrators manage funds domiciled across APAC, EMEA, and Americas jurisdictions. Each fund has different NAV cut-off times, market holidays, and settlement calendars. Asset Atrium must process each fund according to its domicile rules while sharing a single platform instance.
Core concepts
- Processing zone: a named zone aligned to a regulatory domicile (for example, APAC-HK, EMEA-LUX, EMEA-IE, AMER-US).
- Fund-to-zone association: each fund/sub-fund is assigned a processing zone that defines NAV cut-off and business day boundaries.
- Zone-based batch segmentation: the Asset Atrium Scheduler runs NAV batches per zone with zone-specific valuation dates and pricing sources.
- Transfer agent deadlines: subscription/redemption cut-off times are zone-specific and drive dealing calendar logic.
flowchart LR
FUND[Fund / Sub-Fund] --> ZONE[Processing Zone]
ZONE --> CAL[Market Calendar - exchange holidays]
ZONE --> CUT[NAV Cut-Off Time]
CAL --> BIZ[Business Date D]
subgraph AT_Batch[Asset Atrium Batch]
PRICE[Pricing Ingestion]
VAL[NAV Calculation]
PUB[NAV Publication to TA]
end
BIZ --> AT_Batch
AT_Batch --> OUT[Official NAV per zone]
Zone configuration
- APAC-HK: Hong Kong / Singapore funds — NAV cut-off 16:00 HKT, HKEX + SGX calendars, Bloomberg BVAL APAC snap
- EMEA-LUX: Luxembourg UCITS funds — NAV cut-off 18:00 CET, Euronext + LSE calendars, BVAL EU snap
- EMEA-IE: Ireland-domiciled funds — NAV cut-off 17:00 GMT, ISE calendar, BVAL EU snap
- AMER-US: US registered funds — NAV cut-off 16:00 ET, NYSE + NASDAQ calendars, BVAL US snap
- AMER-CAY: Cayman hedge funds — NAV cut-off flexible (monthly), composite calendar
D+1 trade acceptance
Asset Atrium supports forward-dated order entry where a fund's zone has already rolled to D+1 but other zones remain on D. The platform validates:
- Trade date against the fund's zone calendar (holidays, weekends, market closures).
- Settlement date projection using the correct T+n convention for the instrument's settlement market.
- Downstream consistency: allocation, confirmation, and settlement instruction generation all reference the same business date.
Database configuration
Zone configuration is stored in Asset Atrium's Oracle schema with the following reference data:
- Zone master table: zone code, description, base timezone, NAV cut-off time
- Fund-zone mapping: fund ID → zone code (many-to-one)
- Calendar sets: zone code → market calendar IDs (composite calendar support)
- Pricing source rules: zone code → pricing vendor + snap time
The key differentiator is not "knowing time zones" — it's how Asset Atrium coordinates zones, calendars, pricing sources, and batch windows into a deterministic, auditable NAV production pipeline.