What is double-entry bookkeeping?
Double-entry bookkeeping is the system in which every financial transaction is recorded twice — once as a debit and once as a credit, in different accounts, with the totals equal. Codified by Luca Pacioli in 1494 (“Summa de Arithmetica”), it is the foundation of all modern accounting under IFRS and US GAAP. The discipline produces self-balancing books that make errors detectable.
The mechanics
Every transaction has at least one debit and one credit, and the two must equal. The accounting equation must always hold:
Assets = Liabilities + Equity
Examples:
- Customer pays $1,000 cash for service: Debit Cash $1,000; Credit Revenue $1,000.
- Buy equipment for $10,000 on credit: Debit Equipment $10,000; Credit Accounts Payable $10,000.
- Pay $5,000 salary: Debit Salary Expense $5,000; Credit Cash $5,000.
Debit/credit conventions
- Assets: debit increases, credit decreases.
- Liabilities: credit increases, debit decreases.
- Equity: credit increases, debit decreases.
- Revenue: credit increases, debit decreases.
- Expenses: debit increases, credit decreases.
Why double-entry matters
- Error detection: if total debits do not equal total credits, an entry is wrong — caught immediately by the trial balance.
- Audit trail: every change in one account has a counter-entry in another, producing a complete economic narrative.
- Statement integration: the same set of journal entries produces the balance sheet, income statement and cash flow statement consistently.
Double-entry vs. single-entry
Single-entry (essentially a cheque register) tracks only cash in and out. It cannot produce a balance sheet, cannot detect missing transactions, and is not GAAP/IFRS-compliant. Single-entry is fine for personal budgeting; double-entry is required for any business that takes on credit, prepays, accrues, or has investors.
Do: implement double-entry from day one via a modern GL system; never let cash-only spreadsheets become the source of truth.
Don’t: assume double-entry comes free with software — chart-of-accounts design and the discipline to record every transaction promptly is what makes the system trustworthy.