Skip to content

Getting started

Sign in

Staff sign in to the admin console with the username and password issued by your administrator. What you see is shaped by two things:

  • Your role decides which modules and actions you can use. If a screen you expect is missing, ask your administrator to review your permissions.
  • Your institution's edition decides which capabilities exist at all. A banking-only deployment never shows the back-office (ERP) sections, and vice versa.

Customers sign in to the customer portal. Sensitive actions (transfers, payments) ask for a one-time code. That is step-up authorisation, and it is expected.

Find your way around

The console is organised by what people do, not by which system a feature lives in. A few things are worth knowing on day one:

  • The left navigation is grouped (Customer Ops, Deposits, Payments & Clearing, and so on). Groups you have no access to simply do not appear.
  • Press ⌘K / Ctrl-K to jump anywhere, and to search customers and accounts by name or number. It is the fastest way to move around.
  • The header shows the current business date, the environment (DEV / UAT / PROD), your role, and your branch. Live badges flag work waiting for you: pending approvals, an end-of-day run in progress.
  • The home dashboard is a work queue: what needs you right now (approvals to decide, screening hits, failed payments, your open till), plus quick actions for your role.

See Inside the console for the full tour, including the two-dimensional access model (permissions and approval tiers) that governs everything you can do.

Your first flow

The golden path every new operator should walk once. It touches onboarding, accounts, payments, maker-checker and the ledger: the spine of the whole platform.

  1. Open a customer. Customer Ops → Onboarding. Work through the stepper, completing the KYC checklist for the customer's CDD tier. Each step saves as you go, so Back and Next never lose data.
  2. Open an account. From the customer's page, open a deposit account on a product. The account number's branch code records where it was opened.
  3. Post a transfer. Payments → new transfer. If the amount is over your auto-limit, the console says it has been sent to Approvals. A second operator authorises it. That is maker-checker.
  4. Read the journal. General Ledger & Finance → Journals → Entries. Find the transfer: a balanced debit and credit pair, stamped with a day-book category. Every movement in Cortex ends here, in one ledger.

Where to go next