DevelopmentIntermediate

COBOL

Business-oriented language designed in 1959 that still runs critical billing, payroll and accounting processes in many organizations.

Pronunciation

/ˈkoʊ.bɒl/
"KOH-bol"

What is it

COBOL (Common Business-Oriented Language) is a programming language built for business applications: financial calculations, customer records, payroll, billing. Its syntax reads like written English, with the goal of making code readable even to non-technical people.

For a manager, the simplest way to see it: COBOL is the silent engine behind many processes that “have always worked” — the nightly accounting close, policy settlement, or interest calculation that nobody dares to touch.

A Bit of History

  • In 1959 the CODASYL committee (Committee on Data Systems Languages) was formed, bringing together manufacturers, users, and academia to design a common business language.
  • The language borrowed ideas from FLOW-MATIC, Grace Hopper’s language: long variable names, English words for commands, and separation between data descriptions and instructions.
  • COBOL is still a living standard: the current version is ISO/IEC 1989:2023.

What a COBOL Program Looks Like

A COBOL program is organized into four divisions:

IDENTIFICATION DIVISION.
PROGRAM-ID. CALC-INTEREST.
DATA DIVISION.
WORKING-STORAGE SECTION.
01 BALANCE      PIC 9(9)V99 VALUE 150000.00.
01 RATE         PIC V9999   VALUE .0125.
01 INTEREST     PIC 9(9)V99.
PROCEDURE DIVISION.
    COMPUTE INTEREST = BALANCE * RATE
    DISPLAY "INTEREST: " INTEREST
    STOP RUN.
Division Purpose
IDENTIFICATION Program name and metadata
ENVIRONMENT File and machine configuration (omitted in the example)
DATA Fixed-format data structures (PIC)
PROCEDURE The business logic

Its strengths are exact decimal arithmetic and batch processing of large record volumes. Much enterprise COBOL runs on mainframes, alongside transaction managers and jobs scheduled with JCL.

Why It Matters Today

COBOL isn’t “bad” because it’s old. The real problem is usually the context around it:

  • Concentrated knowledge: business rules live in the code and in the heads of a few people, many close to retirement
  • Hard integration: exposing that logic to a mobile app or web portal requires extra layers, such as APIs
  • Slow change cycles: manual testing and infrequent deployments
  • Outdated documentation: the code is the only source of truth

In Latin America, it’s not unusual to find COBOL cores in banks, insurers, credit unions, and public agencies that automated decades ago. For those organizations the question isn’t “COBOL, yes or no?” but how to modernize without stopping operations.

Common Mistakes When Modernizing COBOL

❌ Rewriting everything at once (“big bang”) → Months of work with no value delivered and a high-risk final cutover

❌ Line-by-line translation to another language → You get “COBOL written in C#”, carrying the same technical debt

❌ Ignoring batch → Nightly processes and their dependencies are often the most delicate part

❌ Not extracting business rules before migrating → Undocumented calculations get lost

✅ Best practices:

  • Inventory programs, copybooks, batch jobs, and data dependencies
  • Document business rules (AI now helps read and summarize legacy code, always with human validation)
  • Build characterization tests that compare old vs. new results
  • Migrate in slices with the Strangler Fig pattern

Practical Example (illustrative)

An insurer calculates premiums in a COBOL program that runs every night. Instead of rewriting it entirely:

  1. The premium calculation is exposed as a REST API that calls the existing program
  2. The new Angular web portal consumes that API
  3. The calculation is reimplemented in .NET and run in parallel with COBOL, comparing results over several cycles
  4. Once the results match, traffic moves to the new service and the COBOL program is retired

Operations never stop and every step is reversible.

Have a COBOL core you need to modernize? At Nextsoft we support these projects together with specialized strategic partners: the partner carries out the migration and Nextsoft delivers new modules, integrations, frontend and QA. Explore the legacy system modernization service or let’s talk.

To compare options and plan a phased modernization, download the free playbook COBOL in 2026: modernization options without stopping operations (PDF).

Additional Resources:

Related articles

All terms