Core banking
Deposits · Lending · Payments · Cards · Teller · Treasury · Trade finance · Agent banking
Enterprise (ERP)
Payables · Receivables · Procurement · Sales · Inventory · Payroll · Fixed assets · Planning
AI-native enterprise operating platform
Core banking, the back office, and AI (deposits, payments, cards, treasury, GL, payables, receivables, inventory, payroll), all posting to a single immutable double-entry journal. No subsystems to reconcile after the fact: one institution keeps one set of books.
| REF | ACCOUNT | DEBIT | CREDIT |
|---|---|---|---|
| JOURNAL BALANCED | 0.00 | 0.00 | |
40+ business modules
70 capabilities, one system
319 documented API operations
ISO 20022 native payments
Double-entry to the cent
The architecture
Not a bundle of separate apps bolted together, but one platform. Shared services like sign-in, approvals and audit sit beneath a shared finance engine (the ledger, tax and FX), and every part of the business plugs into both. Switch a capability on and it works with all of it from day one. Nothing to re-integrate.
Deposits · Lending · Payments · Cards · Teller · Treasury · Trade finance · Agent banking
Payables · Receivables · Procurement · Sales · Inventory · Payroll · Fixed assets · Planning
Ledger · Chart of accounts · Posting engine · Dimensions · Periods · FX · Tax · Consolidation · Financial reporting
Identity & access · AI & agents · Approvals & workflow · Documents · Notifications · Audit · Scheduling · Reference data · Integration
A customer's card payment and a supplier invoice land in the same set of books, under the same accounting rules, tagged to the same branches and cost centres. That's what "one ledger" means in practice: nothing to reconcile between systems, because there's only ever one.
The breadth
Forty-plus business modules, from deposits to payroll, that snap together into exactly the product you need. Turn one on and it's there; leave it out and it isn't. No half-finished features, and no paying for capabilities you don't use.
Current, savings and wallet products, interest accrual, statements, holds, mandates, standing orders.
Origination, disbursement, schedules, collateral registers, arrears, commissions.
ISO 20022 messaging, funds transfer, bill pay, the switch, and clearing across domestic and cross-border rails.
Issuing, card billing, prepaid, and the dispute lifecycle end to end.
Deals, FX, nostro reconciliation, trade finance, and wealth portfolios.
Teller, cash logistics, agent banking, end-of-day, onboarding, KYC/CDD, and party (CIF).
Sales, billing, credit control and receivables, on the same ledger your bank runs.
Procurement, suppliers, contracts, and payables with three-way match.
Items, warehousing, movements, and standard / landed costing.
HR, payroll runs, fixed assets, depreciation, and projects.
Budgeting, forecasting and commitments, with actuals from the very same journal.
Sanctions/PEP screening, risk rating, transaction monitoring, maker-checker on every sensitive action.
Intelligence
The AI works from the same books your auditors do: reading documents, explaining figures, flagging anomalies and answering questions from real data, always included. The step up is autonomy: agents that don't just advise, but act.
# an agent quotes, then commits: idempotent, signed, audited
POST /api/v1/mcp/tools/transfers.commit
authorization: Bearer $AGENT_TOKEN
idempotency-key: agent-2026-000418
x-step-up: verified
x-signature: ed25519:…
{ "previewId": "…", "amount": {"amount":"250.00","currency":"USD"} }
# the outcome is a DecisionRecord: evidence, tier and principal, retained
One codebase, many products
The same modules assemble into different products. Serve a 20-person company, or run a full bank and its own back office, all from one codebase. No separate versions to maintain, and no forks drifting apart over time.
General ledger, payables, receivables, cash and tax: the essentials, running lean. Right-sized for a small business, without the enterprise weight.
The full back office: procure-to-pay, order-to-cash, inventory, payroll, assets and planning on the shared ledger.
Run a full bank, or a bank and its own back office together. The bank's own books sit alongside the businesses it serves, each kept completely separate.
One system, many institutions. Every institution's data lives in its own separate database (kept apart physically, not just by a setting), and each gets exactly the edition it pays for. There's no shared space where one institution could ever see another's data.
Built to be built on
One REST API, 319 documented operations, money movement that's safe to retry, and standard OAuth2 for service access. The rules that keep modules independent are enforced automatically, so what your team builds against locally is exactly what runs in production.
Open the developer portal# authenticate a service client
TOKEN=$(curl -su "$CLIENT:$SECRET" -d grant_type=client_credentials \
https://auth.cortexbanking.com/oauth2/token | jq -r .access_token)
# move money: idempotent, balanced, audited
curl -X POST https://api.cortexbanking.com/api/v1/transfers \
-H "authorization: Bearer $TOKEN" \
-H "idempotency-key: tr-2026-000418" \
-d '{"from":"ACC000000000031","to":"ACC000000000007",
"amount":{"amount":"250.00","currency":"USD"}}'
Read the documentation, browse 319 API operations, or sign in to the console.