Behind baseline, but still recoverable if integration capacity is addressed now.
- 1Integration build is 28 days behind, with 129 of 340 critical integrations unassigned.
- 2Current critical-path forecast pushes go-live to Jun–Jul 2027, versus the approved Mar 2027 baseline.
- 3The immediate decision is whether to approve $4–6M external integration capacity this week.
Schedule outlook
Integration build delay is driving the variance. Recovery remains possible if additional capacity is approved now.
Critical pathZero or negative float from Discovery & Vendor Selection to Go-Live — Mar 2027
Every stage shown has zero or negative float, so delay passes straight through to the end date. Full detail on the Critical Path tab.
Delivery roadmapAs at 27 Apr 2026
APRA CPS 234 notification required 6 months pre-cutover
Decisions required
Integration capacity shortfall threatens the Sep 2026 SIT start and Mar 2027 go-live
Requested: Approve engagement of an external integration specialist (Deloitte, Accenture, or a Temenos T24 specialist) to close the 129 unassigned integration tasks under a fixed-scope contract.
Recommended: Approve this week, before the September SIT start date becomes unrecoverable.
If not decided: Integration build completes Dec 2026 — 3 months past SIT start — putting the Mar 2027 go-live and APRA notification out of reach
Proactive APRA engagement strategy requires endorsement ahead of the CPS 234 deadline
Requested: Endorse proactively briefing APRA on the current delay and mitigation plan, rather than waiting for the formal September notification.
Recommended: Endorse early engagement this month — proactive disclosure preserves room to negotiate the notification timeline.
If not decided: Notification arrives without prior context, removing any opportunity to negotiate timeline flexibility and increasing enforcement exposure
What could change the outcome
The top risks that could move this outlook. A preview of the full Risk Analysis tab.
129 critical integrations remain unassigned.
Current schedule compression threatens the Sep 2026 notification window.
340K anomalies remain to be triaged.
Workstream health
| Workstream | Complete | Position | Status |
|---|---|---|---|
| Integration Build | 38% | 28d behind | At risk |
| Data Migration | 25% | 6wk exposure | Watch |
| Testing | 3% | Sep start at risk | At risk |
| Regulatory | 30% | Sep deadline | Watch |
- Dependency links aren't supplied — critical path is therefore directional, not calculated from formal schedule logic.
- CBM.5.3 (CPS 234 milestone) has a 182-day duration configured, which looks unusual for a notification lodgement event.
- The export gives System Integration Testing (CBM.4.2) four different finish dates: 31 Oct 2026 planned, Nov 2026 on the Schedule tab, Dec 2026 in that row's comment, and Feb 2027 on the Critical Path tab. Cherry reports them as found and has not chosen between them. Details on the Critical Path tab.
- 1Phase 1 is complete.
- 2Phase 2 is understaffed on the integration build, the single largest driver of schedule exposure.
- 3Phase 3 hasn't started substantively and depends entirely on integration recovery — the parallel run date is fixed by regulation, so upstream delay compresses the remaining phases rather than extending the project.
PhasesSelect a phase to expand
ScheduleAs at 27 Apr 2026
| WBS | Task | % | Start | Finish | Forecast | Owner | Status | Comments | |
|---|---|---|---|---|---|---|---|---|---|
| CBM | NEXUS BANK — CORE BANKING MIGRATION | 36% | 05 Jan 2025 | 31 Mar 2027 | At risk | S. Okafor | In Progress | AMBER overall. 28d behind baseline (integration build). APRA notification Sep 2026 at risk. 129 integrations unassigned after 3 resignations Q1. Parallel run non-negotiable 3 months pre-cutover. | |
| CBM.1 | Phase 1 — Discovery, Architecture & Vendor Selection | 100% | 05 Jan 2025 | 30 Jun 2025 | 30 Jun 2025 ✓ | S. Okafor / Deloitte | Done | All discovery complete on schedule. Temenos T24 selected. 1,247 integrations catalogued. | |
| CBM.1.1 | Current state assessment — 1,247 integrations catalogued | 100% | 05 Jan 2025 | 31 Mar 2025 | 28 Mar 2025 ✓ | V. Chakraborty | Done | 340 classified critical path. 50 classified decommission. 857 standard migration. | |
| CBM.1.2 | Target architecture design — Temenos T24 on Azure | 100% | 01 Feb 2025 | 30 Apr 2025 | 02 May 2025 ✓ | Deloitte / V. Chakraborty | Done | Approved by architecture board. 2 days late due to security review — no impact. | |
| CBM.1.3 | Vendor evaluation & Temenos T24 selection | 100% | 01 Mar 2025 | 30 Jun 2025 | 15 Jun 2025 ✓ | Procurement / Board | Done | Contract signed 15 Jun 2025. Deloitte Digital engaged as SI partner. | |
| CBM.1.4 | APRA initial project notification (CPS 234) | 100% | 15 Jan 2025 | 22 Jan 2025 | 22 Jan 2025 ✓ | M. Andersen / K. Barrett | Done | CPS 234 compliance assessment complete. Next touchpoint: pre-cutover notification, due Sep 2026. | |
| CBM.2 | Phase 2 — Build, Configure & Integration | 44% | 01 Jul 2025 | 30 Sep 2026 | Tracking Dec 2026 | V. Chakraborty / Deloitte | In Progress | 129 of 340 critical integrations unassigned. 3 senior engineers resigned Q1 — backfill 6–8 weeks to productivity. | |
| CBM.2.1 | Temenos T24 core platform configuration | 72% | 01 Jul 2025 | 31 Jul 2026 | Tracking Aug 2026 | Temenos / Deloitte | In Progress | Deposits 90%, business banking 85%. Loans 60% — complex interest calcs causing delays. | |
| CBM.2.1.1 | Retail banking product configuration | 100% | 01 Jul 2025 | 30 Sep 2025 | 30 Sep 2025 ✓ | Deloitte / Temenos | Done | Transaction accounts, savings, term deposits — configured and unit tested. | |
| CBM.2.1.2 | Business banking product configuration | 85% | 01 Oct 2025 | 15 Feb 2026 | Tracking Feb 2026 | Deloitte / Temenos | In Progress | Business accounts and overdrafts complete. Trade finance in final review. | |
| CBM.2.1.3 | Loans & mortgage configuration — complex interest calcs | 60% | 01 Nov 2025 | 30 Apr 2026 | Tracking Jun 2026 | Deloitte / Temenos | Delayed | Variable rate mortgage logic more complex than estimated. Escalated to Temenos HQ. 6-week delay expected. | |
| CBM.2.2 | Integration build — 340 critical path integrations | 38% | 01 Jul 2025 | 30 Sep 2026 | Tracking Dec 2026 | V. Chakraborty + team | Behind — 28d | 129 of 340 have NO assigned developer. 3 senior engineers (L. Obi, T. Ferreira, A. Park) resigned Q1. External specialist engagement recommended immediately. | |
| CBM.2.2.1 | Core banking API layer — T24 REST APIs | 100% | 01 Jul 2025 | 31 Oct 2025 | 28 Oct 2025 ✓ | V. Chakraborty / L. Obi (resigned) | Done | L. Obi resigned post-completion — knowledge transfer only partially done. | |
| CBM.2.2.2 | Internet banking portal integration | 100% | 01 Oct 2025 | 15 Feb 2026 | 12 Feb 2026 ✓ | Digital team | Done | Performance tested to 50,000 concurrent users. | |
| CBM.2.2.3 | Mobile banking app integration (iOS & Android) | 75% | 01 Feb 2026 | 30 Jun 2026 | Tracking Jul 2026 | Digital / T. Ferreira (resigned) | In Progress | T. Ferreira was mobile lead — resigned 15 Mar. Handover incomplete. 3-week delay expected. | |
| CBM.2.2.4 | Payment systems — NPP, BPAY, SWIFT, Direct Debit | 45% | 01 Mar 2026 | 31 Aug 2026 | Tracking Sep 2026 | V. Chakraborty | In Progress | NPP complete. BPAY 60%. SWIFT 30% — complex correspondent banking. On critical path to SIT. | |
| CBM.2.2.5 | Third-party integrations (129 of 340 UNASSIGNED) | 8% | 01 Sep 2025 | 30 Sep 2026 | Tracking Dec 2026 | VACANT (129 tasks) | Understaffed | A. Park (resigned) owned these. Current velocity: complete Jan 2027. Needs 4–6 FTE external, ~$4–6M, board approval required. | |
| CBM.2.2.6 | Branch & ATM network integration | 30% | 01 Apr 2026 | 31 Jul 2026 | Tracking on plan | Branch Ops / IT | In Progress | 42 branches, 180 ATMs. Branch 40% on standard T24 teller interface. ATM 15% — Diebold Nixdorf. | |
| CBM.2.2.7 | APRA regulatory reporting feeds | 0% | 01 Jun 2026 | 30 Sep 2026 | Unassigned — no resource | UNASSIGNED | Not Started | Mandatory — APRA requires uninterrupted reporting. Not ready before go-live is a regulatory breach. Escalate immediately. | |
| CBM.3 | Phase 3 — Customer Data Migration (2.1M records) | 25% | 01 Jul 2025 | 31 Mar 2027 | Complex — 340K anomalies | A. Osei / Temenos | In Progress | 340,000 anomalies requiring remediation before migration. Additional 6 weeks estimated. | |
| CBM.3.1 | Data catalogue & schema mapping — legacy to T24 | 100% | 01 Jul 2025 | 30 Sep 2025 | 25 Sep 2025 ✓ | A. Osei / Temenos | Done | 847 data entities mapped from legacy to T24 schema. | |
| CBM.3.2 | Data quality audit — 2.1M records | 100% | 01 Sep 2025 | 15 Dec 2025 | 18 Dec 2025 ✓ | A. Osei / Temenos | Done | 340,000 anomalies — 180K duplicate/linked, 95K dormant, 65K outdated beneficiary data. | |
| CBM.3.3 | Anomaly triage & remediation plan | 60% | 01 Jan 2026 | 15 May 2026 | Tracking May 2026 | A. Osei / Legal | In Progress | Dormant account strategy agreed with legal. Duplicate remediation complex — needs customer outreach. | |
| CBM.3.4 | Duplicate account remediation (180K accounts) | 20% | 01 Feb 2026 | 31 Jul 2026 | Tracking Sep 2026 | A. Osei / Branch Ops | In Progress | Customer-linked duplicates require manual review. 6-week schedule risk to migration dry run. | |
| CBM.3.5 | Migration dry run 1 — full data set | 0% | 01 Aug 2026 | 10 Aug 2026 | At risk — may slip Sep | A. Osei / Temenos | Not Started | Requires all anomaly remediation complete. Slip risk if CBM.3.4 delayed. | |
| CBM.3.6 | Migration dress rehearsal — simulated cutover | 0% | 01 Nov 2026 | 07 Nov 2026 | TBC | A. Osei / All teams | Not Started | Full weekend cutover simulation. Target: complete in 62-hour window. | |
| CBM.4 | Phase 4 — Testing & Parallel Run | 3% | 01 Sep 2026 | 31 Mar 2027 | At risk if CBM.2.2 slips | L. Ferreira / Business teams | Planning | 3-month parallel run non-negotiable. Working backward: SIT Sep, UAT Oct–Nov, Parallel Dec–Mar, Go-live Mar 2027. | |
| CBM.4.1 | Test strategy, plan & environment setup | 40% | 01 Mar 2026 | 31 May 2026 | Tracking plan | L. Ferreira | In Progress | SIT environment being provisioned on Azure. Test data approach agreed. | |
| CBM.4.2 | System Integration Testing (SIT) — all 340 integrations | 0% | 01 Sep 2026 | 31 Oct 2026 | At risk — Nov 2026 | L. Ferreira / V. Chakraborty | At Risk | Cannot start until all 340 integrations complete. Current trajectory: Dec 2026 — 3 months after SIT target. | |
| CBM.4.3 | User Acceptance Testing — business users | 0% | 01 Nov 2026 | 15 Dec 2026 | At risk | Business teams / L. Ferreira | Not Started | 6-week minimum — cannot compress for a project of this complexity. | |
| CBM.4.4 | Parallel run — old and new systems simultaneously (3 months) | 0% | 01 Dec 2026 | 28 Feb 2027 | At risk | All teams — major resource commitment | Not Started | NON-NEGOTIABLE — APRA and internal risk policy. Both systems run simultaneously for 3 months. | |
| CBM.5 | Regulatory & Compliance — APRA CPS 234 | 30% | 05 Jan 2025 | 30 Jun 2027 | APRA notification at risk | M. Andersen / K. Barrett | APRA regulated | Pre-cutover notification NOT lodged. Sep 2026 deadline at risk. Board members carry personal liability. | |
| CBM.5.1 | APRA initial notification — project commencement | 100% | 15 Jan 2025 | 22 Jan 2025 | 22 Jan 2025 ✓ | M. Andersen | Done | APRA notified. CPS 234 compliance framework engaged. Quarterly reporting commenced. | |
| CBM.5.2 | Quarterly APRA progress reporting (ongoing) | 75% | 01 Apr 2025 | 31 Mar 2027 | Q1 2026 lodged ✓ | M. Andersen | Ongoing | Q2 2026 report due Jul 2026. Reports have not disclosed integration delays — recommend disclosing proactively. | |
| CBM.5.3 | CPS 234 pre-cutover notification — NOT LODGED — Sep 2026 deadline | 0% | Must lodge: Sep 2026 | Sep 2026 | AT RISK | M. Andersen / Board | Not Lodged | 6-month minimum pre-notification for Mar 2027 go-live. BOARD: personal liability applies. Engage APRA proactively NOW. | |
| CBM.5.4 | Proactive APRA delay briefing — RECOMMENDED IMMEDIATELY | 0% | IMMEDIATE | ASAP | Not scheduled | M. Andersen / CEO | Not Done | APRA responds better to proactive disclosure. Brief APRA relationship manager. CEO and CRO to attend. | |
| CBM.5.5 | Customer regulatory communications — 2.1M customers — NOT STARTED | 0% | Should start: May 2026 | Jul 2026 | 7 weeks late to start | K. Barrett / Comms team | Not Started | Comms plan requires 8 weeks. Must start by Jul 2026 for Dec parallel run comms. Comms team unaware this is assigned to them. | |
| CBM.6 | Phase 5 — Cutover & Hypercare | 0% | 15 Mar 2027 | 30 Jun 2027 | — | S. Okafor / All teams | Not Started | Weekend cutover. 72-hour production window. All 2.1M customers. Rollback maintained 90 days. | |
| CBM.6.1 | Cutover planning & weekend war room setup | 0% | 01 Jan 2027 | 15 Feb 2027 | — | S. Okafor / All leads | Not Started | Go/no-go criteria, rollback triggers, comms tree, war room roster, vendor on-call (Temenos, Deloitte). | |
| CBM.M1 | ◆ GO-LIVE — Core Banking Migration | — | 15 Mar 2027 | 15 Mar 2027 | At risk — integration delays | All teams / APRA | Target | TARGET AT RISK. Integration delays + resignations + APRA notification risk + parallel run requirement = immediate intervention needed. |
40 rows from the Nexus Bank demonstration schedule (Smartsheet export). Finish dates in red are past plan or forecast beyond plan.
Observed = read directly from the schedule export. Calculated = derived from export values. Modelled = a scenario, not a forecast. Recommended = Cherry's proposal.
APRA CPS 234 notification — Sep 2026 deadline at risk from integration delays
APRA's CPS 234 standard requires notification of material information asset changes well before implementation, and the current integration delay is compressing that runway.
For a March 2027 go-live, notification must be lodged by September 2026. The current 28-day integration delay means the project will not have sufficient testing confidence to lodge a credible notification in time, exposing Nexus Bank board members to personal liability under APRA enforcement powers.
129 critical integrations unassigned — 3 senior engineers departed Q1
Of 340 integrations on the critical path, a significant share have no developer assigned, and three senior integration engineers resigned in Q1 citing workload.
The backfill has produced 2 new hires currently onboarding, who will not be productive for 6–8 weeks. At current velocity the integration build will not complete until December 2026 — three months after the SIT start date — making UAT and parallel run impossible before March 2027.
3-month parallel run is non-negotiable — compresses every upstream phase
APRA and Nexus Bank's own risk framework require a minimum parallel run of old and new systems before decommissioning the legacy platform, and that requirement is non-negotiable.
Working backward from the March 2027 go-live: parallel run must start by December 2026, UAT must be complete by November 2026, and SIT must start by September 2026. The current trajectory misses the September SIT start date by approximately 10 weeks.
Customer data migration — 2.1M records, data quality assessment revealed 340K anomalies
The customer data migration audit identified data quality anomalies across duplicate accounts, outdated beneficiary details, and dormant accounts with unreconciled balances.
The migration team has a plan but it requires 6 additional weeks beyond the current timeline to resolve 340,000 anomalous records before cutover — migrating anomalous financial data into a new system during a cutover is not permissible.
Customer communications plan not started — 2.1M customers need 8 weeks notice
The cutover will affect every Nexus Bank customer, and the customer communication plan covering downtime, branch hours, and dispute resolution has not been drafted.
Banking regulations require customers to be notified of material system changes. The communications team estimates 8 weeks to develop, approve, and deploy — this work needs to start by July 2026 to be ready for the December parallel run communications.
Regulatory deadline is fixed. All actions below are calibrated to protect the APRA notification date and March 2027 go-live. Actions 1 and 2 depend on an executive decision — see Decisions Required on the Executive Overview.
Observed = read directly from the schedule export. Calculated = derived from export values. Modelled = a scenario, not a forecast. Recommended = Cherry's proposal.
Engage external integration specialists immediately — close the 129-task gap within 60 days
The integration build gap cannot be closed with internal hires alone in the available time.
Engage a specialist integration consultancy — Deloitte, Accenture, or a Temenos T24 specialist — under a fixed-scope contract to complete the 129 unassigned integrations. This will cost approximately $4–6M but protects a $340M project and avoids regulatory breach. Owner proceeds on approval of Decision 1.
Engage APRA proactively — inform them of the delay and your mitigation plan now
Do not wait until September to surface the timeline risk with APRA.
Engage the APRA relationship manager this month with a transparent briefing on the current position, the cause of the delay, and the specific mitigation actions underway. Early engagement may create space to negotiate the notification timeline if mitigation is demonstrably underway. Owner proceeds on endorsement of Decision 2.
Start customer communications planning now — do not wait for UAT
The comms team needs 8 weeks, and that clock has not started.
July 2026 is the latest start — 10 weeks from today. Brief the communications lead this week on the cutover timeline, parallel run window, and customer impact scope. Regulatory comms require legal review, ASIC alignment, and executive approval, all of which take time that doesn't exist if you start in July.
Triage the 340K data anomalies — classify and scope the remediation this week
Not all anomalies carry equal risk, and right now they're being treated as one undifferentiated problem.
Triage the 340,000 flagged records by category and impact: dormant accounts with zero balance can be handled post-migration, duplicate accounts with active transactions cannot. A triage classification this week converts an unknown into a quantified risk with a concrete plan.
Address engineer retention — exit interview findings must be acted on now
Three senior engineers left in Q1, and the exit interviews almost certainly identified root causes — workload, management, compensation, or culture.
Act on those findings publicly and demonstrably this month. Losing two more senior integration engineers in the next 6 months would make the March 2027 go-live effectively impossible. Retention is cheaper than replacement at this stage of a project.
Integration Build — 340 Critical IntegrationsLead: V. Chakraborty · Partner: Temenos · 3 vacancies · 129 unassigned
| Task | Start | Finish | Owner | % | Status | |
|---|---|---|---|---|---|---|
| Core banking API layer (T24) | Jul 2025 | Oct 2025 | V. Chakraborty | 100% | Done | |
| Internet banking portal | Oct 2025 | Feb 2026 | Digital team | 100% | Done | |
| Mobile banking app integration | Feb 2026 | Jun 2026 | Digital team | 75% | In progress | |
| Payment systems (NPP, BPAY, SWIFT) | Mar 2026 | Aug 2026 | V. Chakraborty | 45% | In progress | |
| Third-party integrations (129 unassigned) | Ongoing | Sep 2026 | VACANT | 8% | Understaffed | |
| Branch & ATM network | Apr 2026 | Jul 2026 | Ops team | 30% | In progress | |
| Regulatory reporting feeds (APRA) | Jun 2026 | Sep 2026 | V. Chakraborty | 0% | Not started |
Customer Data Migration — 2.1M RecordsLead: A. Osei · Data Quality: 340K anomalies identified · Migration partner: Temenos
| Task | Start | Finish | Owner | % | Status | |
|---|---|---|---|---|---|---|
| Data catalogue & schema mapping | Jul 2025 | Sep 2025 | A. Osei | 100% | Done | |
| Data quality audit — 2.1M records | Sep 2025 | Dec 2025 | Temenos | 100% | Done — 340K issues | |
| Anomaly triage & classification | Jan 2026 | May 2026 | A. Osei | 60% | In progress | |
| Duplicate account remediation | Feb 2026 | Jul 2026 | A. Osei | 20% | Complex | |
| Migration dry run 1 | Aug 2026 | Aug 2026 | Temenos | 0% | Not started | |
| Migration dress rehearsal | Nov 2026 | Nov 2026 | A. Osei | 0% | Not started | |
| ◆ Production migration — cutover weekend | Mar 2027 | Mar 2027 | All teams | 0% | Go-live |
Testing & Parallel RunTest Manager: L. Ferreira · SIT · UAT · 3-month parallel run required
| Task | Start | Finish | Owner | % | Status | |
|---|---|---|---|---|---|---|
| Test strategy & plan | Mar 2026 | May 2026 | L. Ferreira | 40% | In progress | |
| SIT environment setup | Jun 2026 | Aug 2026 | IT team | 5% | Early stage | |
| System Integration Testing (SIT) | Sep 2026 | Oct 2026 | L. Ferreira | 0% | At risk | |
| User Acceptance Testing (UAT) | Oct 2026 | Nov 2026 | Business teams | 0% | Not started | |
| Parallel run — both systems running | Dec 2026 | Mar 2027 | All teams | 0% | 3 months req. | |
| ◆ Go-live — cutover weekend | Mar 2027 | Mar 2027 | Project | 0% | Target |
Regulatory & ComplianceCRO: M. Andersen · APRA relationship · Legal: K. Barrett · Board accountability
| Task | Start | Finish | Owner | % | Status | |
|---|---|---|---|---|---|---|
| APRA initial project notification | Jan 2025 | Jan 2025 | M. Andersen | 100% | Done | |
| CPS 234 compliance assessment | Apr 2025 | Jun 2025 | K. Barrett | 100% | Done | |
| Quarterly APRA progress reporting | Jan 2025 | Ongoing | M. Andersen | 75% | Ongoing | |
| CPS 234 pre-cutover notification | Aug 2026 | Sep 2026 | M. Andersen | 0% | At risk | |
| Proactive APRA delay briefing | NOW | This month | M. Andersen | 0% | Not done | |
| Customer regulatory communications | Jul 2026 | Mar 2027 | K. Barrett | 0% | Not started | |
| Post go-live APRA report | Mar 2027 | Jun 2027 | M. Andersen | 0% | Not started |
Critical pathFrom the schedule export
The critical path runs unbroken through Integration Build → APRA Regulatory Feeds → SIT → UAT → Parallel Run → Go-Live. Every stage carries zero total float. The integration build is already 28 days behind with 129 tasks unassigned — meaning the critical path is actively degrading. Every day without external resourcing is a day added to the Mar 2027 go-live date, with no mechanism for recovery downstream.
Sequence: 7 stages, read left to right and top to bottom. Critical activities are counted separately, as the longest path covers more tasks than the stages shown.
Critical path sequence
Where the schedule disagrees with itselfObserved in the export, not resolved
System Integration Testing (CBM.4.2) is shown with four different finish dates. The export does not say which one governs, and without dependency links Cherry cannot calculate it.
| Where it appears | Finish date shown | What it says |
|---|---|---|
| Schedule tab, planned finish | 31 Oct 2026 | The baseline date. |
| Schedule tab, forecast column | Nov 2026 | "At risk — Nov 2026". |
| Schedule tab, row comment | Dec 2026 | "Current trajectory: Dec 2026 — 3 months after SIT target." |
| Critical Path tab, forecast | Feb 2027 | Forecast against the same planned finish of 31 Oct 2026. |
Observed in the export, not resolved. The decision card's "Dec 2026" is the integration build completing, not a SIT date. Worth confirming with the Test Manager which SIT date the project is working to; every date after SIT (UAT, parallel run, go-live) moves with it.
Critical task detail
| WBS | Task | Duration | Planned finish | Forecast | Owner |
|---|---|---|---|---|---|
| CBM.2.2 | Integration build — 340 critical integrations | 336d | 30 Sep 2026 | Dec 2026 | V. Chakraborty |
| CBM.2.2.5 | Third-party integrations — 129 of 340 UNASSIGNED Alert | 280d | 30 Sep 2026 | Jan 2027 | VACANT |
| CBM.2.2.4 | Payment systems — NPP, BPAY, SWIFT, Direct Debit | 168d | 31 Aug 2026 | Sep 2026 | V. Chakraborty |
| CBM.2.2.7 | APRA regulatory reporting feeds — NOT STARTED, NO OWNER Alert | 63d | 30 Sep 2026 | Unknown | UNASSIGNED |
| CBM.4.2 | System Integration Testing — all 340 integrations | 42d | 31 Oct 2026 | Feb 2027 | L. Ferreira |
| CBM.4.3 | User Acceptance Testing — all business units (6wk minimum) | 42d | 15 Dec 2026 | Mar 2027 | Business teams |
| CBM.4.4 | Parallel run — old + new systems (APRA mandated, non-negotiable) | 84d | 28 Feb 2027 | May 2027 | All teams |
| REG-003 | CPS 234 pre-cutover APRA notification — NOT LODGED Alert | 182d | Sep 2026 | AT RISK | M. Andersen / Board |
| CBM.M1 | ◆ GO-LIVE — Core Banking Migration | — | 15 Mar 2027 | Jun–Jul 2027 | S. Okafor / All |
Showing 9 of the 18 critical activities.
Near-critical tasks
Mobile banking app — iOS & Android~3 weeks float
T. Ferreira resigned — handover incomplete. iOS 75%, Android 60%. New dev onboarding adds further delay risk.
Loans & mortgage config — complex interest calcs~6 weeks float (shrinking)
6-week delay from Temenos HQ escalation. Float consumed — near-critical for SIT data completeness.
Duplicate account remediation (180K accounts)~6 weeks float
20% complete. Manual process slower than automated. 6-week risk to Aug 2026 dry run, which precedes SIT.
Customer communications — 2.1M customers7 weeks late to start
8-week plan + legal/ASIC approval required. Not started. Comms team not yet briefed.
Migration dry run 1 — full data setSlip risk to Sep 2026
Requires all anomaly remediation complete. Sep slip collides with SIT start — no buffer.
APRA Q2 2026 quarterly report — delay disclosureDue Jul 2026
Integration delays not yet disclosed. Proactive disclosure in Q2 report reduces enforcement risk.
Float distribution
Nexus Bank is a fictional organisation and project, built to show how Cherry reads a project schedule export. It does not describe a real bank, and no real project team has used or endorsed Cherry for it.