This critique originates from scholars analyzing distributed ledger technology.

They argues that traditional double-entry bookkeeping is an outdated artifact and warns that using blockchain to record “debits and credits” represents a profound architectural mismatch.

The systemic reasoning behind why modern corporate architectures should abandon double-entry—and why forcing it onto a blockchain is a mistake—can be understood through several core principles.

1. Why Accounting Should Abandon Double-Entry Bookkeeping

Double-entry accounting, codified by Friar Luca Pacioli in 1494, was not invented because it was a perfect model of economic reality. It emerged because 15th-century merchants lacked computers. In essence, it is a human-optimized error-detection mechanism.

In a computerized and distributed era, enterprises should move beyond double-entry for three key reasons.

A. Double-Entry Records “Artifacts,” Not Reality

When a sale occurs, the underlying economic reality consists of:

• An Event (the transfer of a product or service)
• A Resource (inventory, cash, or another economic asset)
• Two Agents (the buyer and the seller)

Double-entry accounting immediately translates this rich, multidimensional reality into artificial accounting constructs such as:

• Debits
• Credits
• Accounts Receivable
• Ledger Accounts

According to the REA perspective, these are accounting artifacts rather than real-world economic phenomena. They do not exist in the physical transaction itself; they are abstractions used to represent it.

B. Severe Information Loss: The “Apples to Oranges” Problem

To force transactions into balanced journal entries, double-entry accounting reduces multidimensional business activities into a single monetary dimension.

For example, if a company purchases 500 tons of steel, a traditional accounting system might simply record:

• $100,000 Debit
• $100,000 Credit

Critical business information such as:

• Quantity
• Quality
• Location
• Time
• Counterparty

is typically stored outside the accounting ledger in separate operational systems.

The REA model preserves these dimensions directly within its economic event structure, offering a more complete representation of business reality.

C. The Silo Problem

Double-entry accounting relies on a specialized vocabulary of debits, credits, accounts, and journal entries. As a result, financial systems become isolated from operational systems throughout the enterprise.

For example:

• Manufacturing Execution Systems (MES) speak in parts, processes, and production cycles.
• Supply Chain Management (SCM) systems speak in locations, shipments, and fulfillment activities.
• Accounting Systems speak in debits and credits.

Organizations must then build complex reconciliation mechanisms to continuously translate between operational reality and financial representations. REA eliminates much of this translation burden by modeling the underlying economic activities directly.

2. Why Blockchain and “Debits/Credits” Are a Mismatch

When blockchain technology emerged, many organizations attempted to use distributed ledgers to store traditional accounting entries such as debits and credits.

Many shared-ledger theorists regard this as an engineering regression rather than a genuine innovation.

A. Blockchain Already Solves the Error-Checking Problem

Historically, the primary purpose of double-entry bookkeeping was to provide a mathematical consistency check:

Debits = Credits

This balancing mechanism helped detect:

• Data-entry mistakes
• Clerical errors
• Certain forms of fraud

Blockchain systems already provide integrity through:

• Cryptographic signatures
• Distributed consensus
• Append-only records
• Network validation mechanisms

If a system already guarantees that only validated transactions become part of the immutable record, then layering double-entry validation on top becomes redundant. It amounts to applying an error-checking mechanism to infrastructure that already performs integrity verification at a deeper mathematical level.

B. True Triple-Entry Accounting Is Event-Based, Not Ledger-Based

When people discuss Triple-Entry Accounting, the most influential interpretations—associated with Ian Grigg and aligned with REA concepts—do not involve adding a third ledger.

Instead, the blockchain itself becomes the shared economic event.

[ Agent A (Seller) ] ───┐
                        ▼
           ┌─────────────────────────┐
           │ BLOCKCHAIN EVENT RECEIPT│
           │   Shared Economic Event │
           └─────────────────────────┘
                        ▲
[ Agent B (Buyer) ] ────┘

In this model:

• The seller signs the event.
• The buyer signs the same event.
• The blockchain stores a single shared economic fact.

Rather than maintaining separate accounting entries in private databases, both parties agree on one immutable transaction record.

From this shared event, each participant can generate whatever financial, operational, regulatory, or analytical views they require.

The blockchain records the actual economic activity, while accounting balances become downstream calculations derived from that trusted event.

Key Concept: Record the Fact, Derive the Accounting

Under an REA-oriented architecture, the blockchain should store:

• Resources
• Events
• Agents
• Relationships among them

It should not primarily store:

• Debits
• Credits
• Journal entries
• T-accounts

The distributed ledger becomes the authoritative source of economic truth, while accounting statements are dynamically generated from that underlying reality.

Summary

Accounting systems should capture business activities as they occur in the real world rather than translating them into artificial accounting abstractions.

• Abandon double-entry as the primary data model because modern databases can store rich, multidimensional economic events directly.
• Keep debits and credits off the blockchain because distributed ledgers already provide mathematical integrity and validation.
• Record Resources, Events, and Agents instead, allowing financial statements and balances to be derived dynamically from authenticated economic facts.

In this view, blockchain should function as an immutable record of shared economic reality, while accounting becomes a projection generated from that reality rather than the reality itself.