Reference data & settings

Reference data is the configuration the whole platform reads (branches, currencies, calendars, transaction codes, code lists) plus products, pricing and the institution's own identity. Getting it right is what lets Cortex run a new jurisdiction or product without a code change.

Where: the Reference Data group, plus Products & Pricing and Platform Operations.

How reference data behaves

Registries share one pattern: a table with a detail drawer, and one form for both create and edit. Across the board, reference and configuration data is:

• Effective-dated: changes apply from a date, and history is preserved.
• Maker-checker: sensitive changes are authorised by a second person.
• Per-institution: each tenant and jurisdiction has its own.
• Live: no core redeploy to add a transaction code, a charge rule or a calendar.

The registries

Registry	Holds
Servicing institution	Your own bank's identity: BIC, clearing code, address.
Financial institutions	Counterparty banks and their settlement accounts.
Mobile networks	Operators and MSISDN prefixes, for mobile-money routing.
Account number formats	How account numbers are composed per product class.
Branches	The branch master (with safe code rename).
Transaction codes	The transaction-code master: categories, posting templates, value-dating.
Calendars	Business calendars and holidays, with roll conventions.
Currencies	The currency master and decimal scales.
Code lists	Reusable lists: genders, ID types, occupations, day-book categories, document types.

System settings holds numbering strategies, default accounts and integration toggles.

Products & pricing

The Products & Pricing group configures what you sell and what it costs:

• Products: the catalogue (deposit, loan, card products). View with product:read, edit with product:manage.
• Charges: fee and charge definitions (pricing:charge-manage).
• Charge applicability: segment-scoped rules for when a charge applies (pricing:applicability-manage).
• Commissions: commission configuration, eligibility, beneficiaries and accruals (commission:config-manage, commission:settle).

Platform operations

The Platform Operations group is mostly System Administrator territory:

• Tenants: provisioning institutions (platform/default-tenant only).
• Notifications: the notification log and templates.
• Events: the event outbox.
• Migration, bulk import from a legacy core: staged CSV with a four-eyes commit.

Key terms

Effective dating

A change carries a date it takes effect from, so past postings keep using the rule that was in force at the time.

Transaction code

A coded transaction type carrying its posting template, value-dating rule, charge rules and channel scope: the unit that lets new transaction types be configured, not coded.

Code list

A reusable, hierarchical list of values (ID types, occupations, day-book categories) referenced across screens.

Roles that do this work

Task	Permission	Typical role
Read reference data	reference:read	Operations Officer
Manage reference data	reference:manage	System Administrator
Manage products	product:manage	Product Manager
Manage charges / pricing	pricing:charge-manage	Product Manager
Provision tenants	tenant:read	System Administrator