Notification orchestration
|
|
| ID |
MOD-063 |
| System |
SD07 |
| Repo |
bank-platform |
| Build status |
Deployed |
| Deployed |
Yes |
| Last commit |
bbdfbac46a1b5cf6dc25b4c7cd428a8daa669d03 |
Notification orchestration is the decisioning layer between platform events and customer communications. Rather than individual modules sending their own messages, all outbound communications are routed through this module, which applies preference rules, channel selection logic, regulatory timing constraints, and deduplication before dispatch.
The module subscribes to domain events from the EventBridge governance layer (MOD-043) and to workflow transition events from the orchestration engine (MOD-062). For each event it evaluates whether a notification is required, what content to use, and which channel to use given the customer's stored preferences (CAP-104). Delivery is delegated to the appropriate channel infrastructure (push, SMS, SMTP) but the decision, content, and outcome are always logged here.
Provides the audit trail required for regulatory disclosure obligations — compliance can demonstrate that a required disclosure was sent, when, to which address, and whether it was delivered.
Module dependencies
Depends on
| Module |
Title |
Required? |
Contract |
Reason |
| MOD-043 |
EventBridge domain event governance |
Required |
— |
Notification decisions are triggered by domain events published on the EventBridge governance buses. |
| MOD-062 |
Workflow orchestration engine |
Required |
— |
Workflow transition events are a primary source of notification triggers from the orchestration engine. |
| MOD-009 |
eIDV & document verification |
Optional |
contract/api/ |
KYC acceptance status consumed to trigger post-onboarding welcome communications. |
| MOD-153 |
Customer acceptance engine |
Optional |
contract/events/ |
Adverse action events from the KYC adverse action filter trigger mandatory regulatory communications to the customer. |
| MOD-104 |
AWS shared infrastructure bootstrap |
Required |
— |
AWS shared infrastructure provisioned by MOD-104 (EventBridge buses, S3, KMS, Kinesis, Cognito) is required before this module can be deployed. |
Required by
| Module |
Title |
As |
Contract |
| MOD-053 |
Case & complaint management module |
Hard dependency |
— |
| MOD-114 |
Direct debit mandate management |
Hard dependency |
— |
| MOD-116 |
Mortgage servicing engine |
Optional enhancement |
— |
| MOD-117 |
Overdraft management engine |
Optional enhancement |
— |
| MOD-119 |
BPAY payment integration |
Hard dependency |
— |
| MOD-120 |
PayID and Osko integration |
Hard dependency |
— |
| MOD-121 |
Construction loan drawdown engine |
Hard dependency |
— |
| MOD-122 |
NZ faster payments and A2A integration |
Hard dependency |
— |
| MOD-124 |
Physical card issuance and bureau integration |
Hard dependency |
— |
| MOD-125 |
Joint account management |
Hard dependency |
— |
| MOD-127 |
Product configuration panel |
Hard dependency |
— |
| MOD-130 |
Notice account management |
Hard dependency |
— |
| MOD-131 |
Mutual governance and AGM administration |
Hard dependency |
— |
| MOD-132 |
Loan restructure and variation workflow |
Hard dependency |
— |
| MOD-135 |
Batch payment and payroll file processing |
Hard dependency |
— |
| MOD-136 |
BPAY biller registration and inbound BPAY |
Hard dependency |
— |
| MOD-137 |
Agency banking adapter |
Hard dependency |
— |
| MOD-143 |
Open Bank Resolution pre-positioning |
Hard dependency |
— |
| MOD-145 |
Payment hold & friction engine |
Hard dependency |
— |
| MOD-153 |
Customer acceptance engine |
Optional enhancement |
— |
Policies satisfied
| Policy |
Title |
Mode |
How |
| CON-001 |
Customer Fairness & Conduct Policy |
AUTO |
Ensures all required regulatory disclosures and event-driven communications are sent to the customer at the correct time. |
| GOV-003 |
Three Lines of Defence Policy |
LOG |
All customer communications are logged with content, channel, timestamp, and delivery status for audit purposes. |
Capabilities satisfied
| Capability |
Title |
Mode |
How |
| CAP-103 |
Notification triggering |
AUTO |
Listens to domain events from MOD-043 and workflow transitions from MOD-062 and decides which communications to trigger. |
| CAP-104 |
Channel selection & preference |
AUTO |
Selects the delivery channel (push, SMS, email) for each notification based on the customer's stored preferences and the notification type. |
| CAP-105 |
Communication audit trail |
LOG |
Records every outbound communication — content, channel, timestamp, delivery status — in an immutable audit trail. |
Part of SD07 — Data Platform & Governance Infrastructure
Compiled 2026-05-22 from source/entities/modules/MOD-063.yaml