Skip to content

All best practices

CS-063mixed

Commonwealth Bank of Australia

Core Banking Modernisation: replacement of legacy core banking systems with SAP (2008–2013)

Region
Oceania
Country
Australia
Industry
Commercial Banking
Functions
IT, ERP & Digital, Operations & Service Delivery, Customer Experience & Support, Strategy, Corporate Development & Transformation Office, Finance & FP&A
Topics
Legacy ERP and fragmented systems block execution; Cross-functional processes are slow and broken; Technology spending is growing without business returns; Customer churn and dissatisfaction are accelerating
Starting situation
New initiative
Period
2008–2013
Last verified
1 November 2026

Executive summary

In April 2008 the Commonwealth Bank of Australia (CBA) launched Core Banking Modernisation, a programme to replace core systems that had run for over 45 years with SAP's banking software, implemented with Accenture, at a forecast of around $580 million over four years [C01]. The bank migrated in stages: customer records first, then retail deposits, business deposits and finally lending [C09, C11, C22].

The three numbers that matter: the $580 million forecast of 2008 [C01]; the revised total of about $1.1 billion in February 2011, with the timetable extended by at least nine months [C11, C12]; and completion reported in the 2013 profit announcement, after $368 million and $200 million of programme spending in the final two years [C21, C22].

Outcome: classed mixed. The bank reported the replacement complete and the platform remained its core 16 years after installation [C22, C24]. But the cost estimate nearly doubled and delivery ran past the four-year plan, which §4.3 treats as a documented shortfall, although CBA said the business case was unchanged and an analyst attributed the rise to wider scope rather than overrun [C11, C14].

The one lesson, as the KB reads it: stage a core replacement so that each release is proved before the next migration, and treat a scope-driven budget rise as a decision for the board to re-approve, not a variance to absorb.

Outcome: mixed

Documented shortfalls or reversals sit alongside documented gains. For example: an initial failure later recovered, or a strategic goal met while a major adverse event in the same programme was recorded.

Basis of the outcome

Documented gains: CBA reported the programme completed in FY2013 with deposit, transaction and lending accounts migrated (S18), product and process simplification (S16), and the platform still the bank's core in 2026 (S20) — all company-reported. Documented shortfalls against the stated plan: the forecast of about $580m over four years (S01) rose to about $1.1bn with at least nine months added (S08, S09), and completion came in the year to June 2013 rather than 2012. CBA said the business case was unchanged and an analyst attributed the rise to scope (S08, S10). Under the outcome criteria the class is mixed. The programme's own shortfalls against its stated plan remain at the end of the period: the cost nearly doubled, delivery ran about a year past the four-year plan, and whether Phase II was completed is not established. These are outcomes of the programme itself, not adverse events outside it, so success is not available; CBA's statement that the rise was scope-driven explains the shortfall but does not remove it.

Key figures

PhaseFigureValueWhenVerification
BeforeForecast cost and duration≈$580m over 4 years28 Apr 2008company_reported
BeforeAge of legacy core systemsover 45 years (1960s–2000s)Apr 2008company_reported
BeforeCash NPAT$4,733mFY2008company_reported
DuringFirst budget increase+A$150m (subsidiaries, risk and finance systems)2009press_reported
DuringRevised total cost≈$1.1bn ('Total cost now ~$1.1b')Feb 2011company_reported
DuringSchedule extensionat least 9 monthsFeb 2011press_reported
DuringRetail accounts migrated10 millionFeb 2011company_reported
DuringCustomisation of SAP product<7%Mar 2011press_reported
DuringProgramme spend in year$368m (FY12); $200m (FY13)FY2012–FY2013regulatory_filing_unaudited
DuringProducts on sale (deposit/transaction)16 → 9May 2012company_reported
AfterStatus'completed the six-year implementation'FY2013regulatory_filing_unaudited
AfterExpense-to-income ratio45.5% (FY11) → 45.0% (FY13)FY2011–FY2013regulatory_filing_unaudited
AfterPlatform in use16m active accounts; moved to cloud in 18 monthsMar 2026company_reported
company_reported
A company statement, press release or investor presentation that no one has independently checked.
press_reported
A journalist's own reporting.
regulatory_filing_unaudited
Text in an 8-K, 6-K or 10-Q, which is filed with a regulator but not audited.

Sources

  1. S01 Core Banking Modernisation (media release) · Commonwealth Bank of Australia, Commonwealth Bank of Australia (ASX), 2008-04-28 · accessed 2026-11-01
  2. S02 Core Banking Modernisation: market briefing · Commonwealth Bank of Australia, Commonwealth Bank of Australia (ASX), 2008-04-28 · accessed 2026-11-01
  3. S03 Shareholder Review 2008 · Commonwealth Bank of Australia, Commonwealth Bank of Australia, 2008-08 (year ended 30 June 2008) · accessed 2026-11-01
  4. S04 Core Renewal Down Under · not stated, American Banker (Bank Technology News), 2009-10-01 · accessed 2026-11-01
  5. S05 CBA adds A$150m to core banking upgrade budget · not stated, Finextra, 2009-08 (inferred: refers to the full-year results briefing and to plans outlined 'last April') · accessed 2026-11-01
  6. S06 CBA hails core banking milestones · Renai LeMay, Delimiter, 2010-02-10 · accessed 2026-11-01
  7. S07 CommBank IT spend blows out past $1 billion · Renai LeMay, Delimiter, 2010-08-11 · accessed 2026-11-01
  8. S08 2011 half year results: analyst pack · Commonwealth Bank of Australia, Commonwealth Bank of Australia (ASX), 2011-02-09 · accessed 2026-11-01
  9. S09 CBA core project balloons to $1.1 billion · not stated, iTWire, 2011-02-09 · accessed 2026-11-01
  10. S10 Analysts unfazed by CommBank's extra $370m dollop · Marina Freri, Delimiter, 2011-02-17 · accessed 2026-11-01
  11. S11 CBA core revamp strips 30% costs · not stated, iTWire, 2011-03-14 · accessed 2026-11-01
  12. S12 CBA's happy Harte: We're years ahead · Renai LeMay, iTWire, 2011-03-14 · accessed 2026-11-01
  13. S13 Customers already getting benefit of SAP implementation: CBA · Freya Purnell, InsideSAP, 2011-03-17 · accessed 2026-11-01
  14. S14 2011 Full year profit announcement · Commonwealth Bank of Australia, Commonwealth Bank of Australia (ASX), 2011-08-10 · accessed 2026-11-01
  15. S15 CBA core banking overhaul enters final furlong · not stated, Finextra, 2012-02 (inferred: reports first-half results and Ian Narev as CEO) · accessed 2026-11-01
  16. S16 Technology Update · Commonwealth Bank of Australia, Commonwealth Bank of Australia (ASX), 2012-05-25 · accessed 2026-11-01
  17. S17 2012 Annual Results: Profit Announcement · Commonwealth Bank of Australia, Commonwealth Bank of Australia (ASX), 2012-08-15 · accessed 2026-11-01
  18. S18 2013 Profit Announcement · Commonwealth Bank of Australia, Commonwealth Bank of Australia (ASX), 2013-08 (year ended 30 June 2013) · accessed 2026-11-01
  19. S19 ANZ CIO: Core banking system 'not a hindrance' · George Nott, Computerworld (Australia), 2016-07-02 · accessed 2026-11-01
  20. S20 Align, focus and believe: Lessons from Commonwealth Bank's core banking transformation · Commonwealth Bank of Australia, Commonwealth Bank of Australia (Newsroom), 2026-03-19 · accessed 2026-11-01

Researched and fact-checked knowledgebase · Knowledgebase built 5 November 2026 · Last verified 1 November 2026

Practices, their evidence grades and case summaries are public. Full case studies are available in AXIOM to subscribers and AXIOM Discover participants.