Skip to content

Platform boundary

This page defines what is inside the platform and what sits outside it — in both Track 1 (direct bank) and Track 2 (SaaS to licensed institutions).

The boundary matters commercially: it defines what tenants get from the platform and what they bring themselves. It matters architecturally: it defines the integration surface between the platform and external systems.

What the platform delivers

The platform delivers technical solutions across all eight system domains. In Track 1 the bank uses these systems to satisfy its own regulatory obligations. In Track 2 tenants use these same systems — via licensed SaaS — to satisfy their own obligations.

System domain What it delivers Relevant obligations
SD01 Core Banking Ledger, accounts, balances, accruals, interest Banking GL, capital base
SD02 KYC Platform eIDV, CDD, sanctions screening, KYC review AML/CFT, KYC, privacy
SD03 AML Monitoring Typology engine, ML scoring, case management, regulatory reports AML/CFT reporting
SD04 Payments Payment validation, fraud, FX, IFTI/CMIR Payment scheme obligations
SD05 Credit Affordability, credit scoring, pre-approval, ECL Responsible lending, credit risk
SD06 Risk Platform Capital ratios, LCR/NSFR, IRRBB, stress testing, prudential returns Capital, liquidity, regulatory reporting
SD07 Data Platform CDC pipeline, RBAC, audit trail, secrets management Data governance, security
SD08 App Customer onboarding, consent, disclosure, complaints, back office Conduct, privacy, customer obligations

The banking ledger boundary

SD01 (Core Banking) generates the consolidated banking ledger — the authoritative record of every deposit, loan, payment, accrual, and fee. This is the platform's primary financial output.

What is inside the platform: - All banking ledger entries (debits, credits, interest, fees) - Real-time account balances - Daily accruals and interest calculations - Multi-currency positions (NZD, AUD)

What is outside the platform: - The bank's/tenant's non-banking general ledger (corporate overhead, salaries, rent) - Statutory financial statements (company profit and loss, balance sheet for regulatory filing) - Management accounts and board reporting packs - Consolidation across entities if the institution has subsidiaries

In Track 2 deployments the banking ledger feeds into the tenant's ERP via an integration layer. The ERP combines the banking ledger with the institution's own corporate overhead entries to produce its consolidated company accounts. The platform does not own or generate those consolidated accounts.

This is consistent with ADR-006: the ERP sits at the periphery, receiving ledger data from the platform, not the other way around.

What is outside the platform

Human resources and payroll

Neither the bank (Track 1) nor SaaS tenants (Track 2) manage HR and payroll through the platform. These are delivered through external HR systems (HRIS, payroll platforms). The platform does not include:

  • Employee records or org structure
  • Payroll calculation or payment
  • Leave management
  • Performance management
  • Learning management / training delivery

The People & Culture domain (D11) and all PPL-NNN policies document the obligations that must be met through external tooling.

Corporate governance administration

The platform delivers the technical infrastructure for governance — immutable audit trail (MOD-047), system decision log (MOD-048), role-scoped access control (MOD-052). These provide the evidentiary foundation for governance compliance.

The platform does not deliver:

  • Board charter or board administration
  • Risk committee governance
  • Fit and proper vetting processes
  • Executive accountability frameworks (e.g., FAR)
  • Regulatory engagement and correspondence

These are human, administrative, and legal processes that apply in both tracks. GOV-001, GOV-004, and GOV-005 are marked External accordingly.

Statutory and company-level financial reporting

The platform generates banking ledger data and regulatory financial returns (prudential reports, capital adequacy disclosures, AML financial intelligence reports). It does not generate the institution's statutory financial accounts.

REP-004 (Financial Statements Policy) covers the statutory reporting obligation, which is managed in the ERP/accounting platform external to this system.

Integration surface

In Track 2 deployments, tenants connect the platform to their external systems through a defined integration layer:

Platform output Tenant system Integration type
Banking ledger entries ERP / accounting platform Scheduled feed or API
Regulatory reports Regulator portals Direct submission or file export
Customer events CRM (if separate) EventBridge events
HR system feeds (background check triggers) HR platform Webhook or API

The platform publishes events via Amazon EventBridge (SD07, ADR-029 (superseded by ADR-051 — see ADR-051 for current EventBridge bus naming convention)). Tenants consume these events to drive their own downstream processes.