User guide¶
This guide covers the admin console: the workspace bank and back-office staff use to run the institution. It is organised the way the console is: by what people do.
If you are new, read Inside the console first. It explains the navigation, the two-dimensional access model (permissions and approval tiers), maker-checker, and the handful of layout patterns every screen reuses. Once you know those, every other page is faster to follow.
The banking modules¶
- Customers & KYC: onboarding, the customer file (CIF), CDD tiers, KYC upgrades, screening.
- Accounts & deposits: opening and servicing deposit accounts, holds, statements, reversals, products.
- Lending & collateral: loan origination, servicing, repayment, collateral and provisioning.
- Payments & transfers: the money path: transfers, the payments hub, rails, clearing, ISO 20022.
- Cards & disputes: debit and credit cards, prepaid, the switch, and the chargeback lifecycle.
- Teller & branch cash: the teller console, tills and vaults, blind cash proofs, cash logistics.
- Ledger & day book: the chart of accounts, posting journals, and reading the day book.
- Day & period close: end-of-day, start-of-day, reporting and regulatory returns.
- Approvals & maker-checker: the four-eyes queue that gates every sensitive action.
- Users, roles & access: accounts, roles, permissions, approval policy and the audit trail.
- Reference data & settings: branches, currencies, calendars, code lists, products and pricing.
What you can see and do¶
Two independent controls decide what appears in your console:
| Control | Set by | Effect |
|---|---|---|
| Capability | Your institution's edition (the deployment) | Whether a module exists at all. Banking-only deployments hide the ERP sections. |
| Permission | Your role | Whether you can open a screen or run an action. Missing a permission hides the item. |
On top of that, sensitive actions carry an approval tier. See Approvals. Being able to capture an action (for example, post a large journal) is separate from being allowed to authorise it.
The complete PDF reference¶
Every screen is also documented, screen by screen and field by field, in a single downloadable document:
Download the Cortex admin portal user guide (PDF)
The curated pages in this section are the recommended starting point; the PDF is the exhaustive back-reference.
Where the platform is honest about its edges
A few capabilities described in internal design notes are not yet wired end to end. Where that is true, this guide says so plainly rather than implying more than the software does. Look for "Not yet built" call-outs.