
COBOL
60-year-old programming language running ~70% of global financial transactions; IBM's core modernisation consulting moat.
Last refreshed: 23 April 2026 · Appears in 1 active topic
If AI can refactor COBOL, does IBM's most profitable consulting niche disappear?
Timeline for COBOL
Mentioned in: IBM beat sold on consulting miss
AI: Jobs, Power & MoneyMentioned in: Snap cuts 16%, AI writes the code
AI: Jobs, Power & Money- How much COBOL code is still in use today?
- Estimates put around 220 billion lines of COBOL in active production, running approximately 70–80% of global financial transactions, primarily at banks, insurers, and government agencies.
- Can AI replace COBOL programmers?
- IBM's watsonx Code Assistant uses AI to accelerate COBOL modernisation and refactoring, delivering 45% developer productivity gains. It does not eliminate COBOL expertise but compresses the labour hours required per project.Source: IBM Q1 2026 earnings
- Why do banks still use COBOL?
- COBOL's decimal arithmetic precision, batch-processing capability, and decades of tested production code make it extremely difficult to replace without risk of introducing errors in financial calculations.
- Who invented COBOL?
- COBOL was designed by a US DoD consortium in 1959, with principal credit given to Grace Hopper's earlier FLOW-MATIC language. It was standardised in 1960.
Background
COBOL — Common Business-Oriented Language — returned to technology headlines in April 2026 as IBM disclosed that its watsonx Code Assistant had built its productivity-gain case almost entirely on COBOL modernisation work: the tool helps consultants refactor and document the estimated 220bn lines of COBOL still running in production at banks, insurers, government agencies, and financial market infrastructure globally. The disclosure reframed watsonx not as a greenfield coding tool but as a COBOL-to-modern-stack migration engine — which in turn reframed the consulting miss story as a question about whether AI accelerates or eliminates IBM's most profitable service line.
COBOL was designed by a US Department of Defence-convened consortium in 1959, with principal credit given to Grace Hopper's earlier work on FLOW-MATIC, the first English-language programming language. The language was standardised by 1960 and adopted rapidly by the financial sector because of its readability, decimal arithmetic precision, and suitability for batch-processing transaction records. Estimated to run 70–80% of the world's financial transactions — including ATM withdrawals, card payments, and clearing house settlements — COBOL is invisible to end users but structural to global finance. The original developer population is ageing out; the skills shortage has been severe since the 2010s.
The COBOL problem is where AI's near-term consulting opportunity and its long-term consulting threat converge most sharply. IBM charges premium rates for COBOL modernisation because few developers understand it; watsonx Code Assistant's ability to accelerate that work is both the source of the productivity gains IBM reported and the mechanism by which those gains could commoditise the service. Every hour of AI-assisted COBOL refactoring is an hour of high-margin consulting labour that no longer needs to be billed.