Business Centre

Summary
Detail
See also

Summary

A business centre is an FpML-coded identifier for a financial trading location's holiday calendar and, more operationally, its rates centre – the EOD market-data snapshot a book revalues against. It is not itself an organisational-hierarchy node: it is a property that a business unit or a book can carry, inherited down the business-unit tree by default and overridable at any node – see Business Unit for that hierarchy. Carrying a business centre is distinct from actually running an end-of-day process against it: a unit may be assigned one purely for inheritance or reporting purposes, independent of whether that unit is configured to run its own EOD. A business centre's code is FpML-standard and coding-scheme-scoped but unique per tenant regardless of scheme. It has no relationship to a cost centre – an unrelated, purely accounting property tracked on the book itself – nor to aggregation currency, the reporting-rollup property a node in the same tree separately carries.

Detail

The FpML business centre scheme

Business centre codes follow the FpML businessCenterScheme (FpML Business Center Scheme): a 4-character code that is either the real geographical location whose calendar governs bad-business-day adjustment (e.g. USNY for New York, GBLO for London), or an FpML-format rate-publication calendar code used for fixing-day offsets. FpML's own description of the scheme draws exactly this distinction: the geographical codes are "implicitly locatable and used for identifying a bad business day for the purpose of payment and rate calculation day adjustments", while the rate-publication codes "are used in the context of the fixing day offsets" – two different jobs sharing the same 4-character code shape. A code is scoped to a coding scheme (FPML_BUSINESS_CENTER for the standard FpML set, NONE for platform-internal centres such as a system-wide "World" centre) but is unique per tenant regardless of which scheme it was sourced from – two schemes cannot register the same code for one tenant.

Holiday calendars: a consumer, not the definition

A holiday calendar – together with trading hours, DST rules, and a default cut-off timezone – is reference data attached to a business centre, not the concept's definition. Date rolling and the underlying business-day / settlement-day distinction both operate against the holiday calendar(s) named by one or more business centre codes; resolving a code to its actual holiday set is a downstream (pricing/analytics) concern, not something the identifier itself stores.

As a rates centre: the EOD-rates property of the business-unit tree

A business centre's more operationally significant role is as a rates centre: a location qualifier attached to a book's revaluation, treated as a first-class dimension alongside currency pair and tenor. The same currency pair can carry different official spot rates in different trading locations – GBP/USD London versus GBP/USD New York – because each business centre applies its own approved rates for its own end-of-day run; a book's rates centre code determines which snapshot it uses. This property attaches naturally to the business-unit tree rather than to the business centre entity itself: see Business Unit for how a business centre assigned to a unit is inherited by its books and descendant units by default. Which units actually run their own end-of-day process against their assigned centre, as opposed to merely inheriting or reporting one, is a separate configuration question – see Business Unit for that distinction. Book groups and rates centres covers the resulting book-level mechanics in full: every book sharing a rates centre revalues consistently, rates-centre-owned books roll up into book groups for consolidated reporting, and centre ownership doubles as an access-control boundary.

Distinct from cost centre and from aggregation currency

A business centre has no relationship to a cost centre, an unrelated accounting property tracked directly on a book – see Business Unit§"Cost centre" and Book and the ledger for that axis in full. Nor does it determine aggregation currency, the currency a business-unit-tree node rolls its figures up in for reporting – a business centre keeps EOD pricing location-specific, while aggregation currency is what lets already-priced figures be summed meaningfully once they leave that location.