Double-entry bookkeeping

Concept

In FY2024, Infosys reported ₹1,53,670 crore in revenue. Every rupee of that started life as a journal entry: a debit on one line, a credit on another. No transaction was ever recorded once. Each one touched at least two accounts, always in equal and opposite amounts. Accountants have worked this way since 1494, when Luca Pacioli first wrote it down, and the system has not meaningfully changed since. It survived five centuries not because tradition is sticky, but because it is the only recording method that makes large-scale fraud structurally hard. Every entry that inflates one number must deflate another somewhere else. When auditors review a set of books, they are not just checking whether the arithmetic adds up. They are checking whether both sides of every transaction correspond to something that actually happened.

This is double-entry bookkeeping: the engine under yesterday's accounting equation. The equation tells you what the balance sheet must look like at any point. Double-entry is the rule that keeps it there, transaction by transaction.

The rule itself is short. Every transaction is recorded as a debit in at least one account and a credit in at least one other. Total debits must always equal total credits. Two sentences. The application of those sentences runs through every financial statement ever produced.

One thing to clear up immediately: the words "debit" and "credit" do not mean what everyday usage implies. When your bank sends a credit to your account, money arrived. In accounting, that mapping breaks down. Think of it as positional instead.

Debits increase assets and expenses. Debits decrease liabilities, equity, and revenue. Credits increase liabilities, equity, and revenue. Credits decrease assets and expenses.

It has nothing to do with good or bad. It mirrors where things sit in the accounting equation. Assets are on the left, so they grow on the left (debit) side. Liabilities and equity are on the right, so they grow on the right (credit) side. That logic is consistent and holds without exception once you stop fighting it.

Consider a typical SaaS transaction. A gaming company signs a ₹50 lakh annual subscription, paid upfront. Two entries go in simultaneously:

Debit: Cash ₹50 lakh. Cash is an asset. It went up. Assets increase with a debit. Credit: Deferred Revenue ₹50 lakh. Deferred revenue is a liability, money owed as future service. Liabilities increase with a credit.

Total debits: ₹50 lakh. Total credits: ₹50 lakh. Balanced.

Nothing has touched the income statement yet. The vendor collected cash and created an obligation. A month in, they deliver one month of service:

Debit: Deferred Revenue ₹4.17 lakh. The liability shrinks as the obligation is fulfilled. Liabilities decrease with a debit. Credit: Revenue ₹4.17 lakh. Revenue increases with a credit.

This repeats every month for twelve months. By the end, deferred revenue is zero, ₹50 lakh sits on the income statement as earned revenue, and the equation held at every step.

Byju's corrupted exactly this cycle. Rather than parking the contract value in deferred revenue and recognizing it over 36 months, the company sent the credit straight to revenue on day one. The debit to cash was real. The credit to revenue was not; it should have gone to a liability. The equation balanced numerically, but the second entry was wrong. That ran for three fiscal years before Deloitte reversed ₹1,156 crore of it.

The reason double-entry makes this kind of thing hard to sustain is that every fabricated entry needs a counterpart to keep the equation whole. That counterpart either reflects reality or it has to be fabricated too. Doing that consistently, across thousands of transactions, over multiple years, is genuinely difficult. Auditors are specifically trained to find entries where the counterpart does not match an economic reality. Deloitte found them.

There is a second thing double-entry gives you that gets mentioned less: a complete trail. Every account in the general ledger carries a running history of every debit and credit that touched it. An auditor can trace any balance backwards through every transaction that built it. Forensic accountants use this to reconstruct what happened even after records have been altered, because erasing one side of a transaction leaves a gap on the other side that is hard to hide.

Practically: when you look at the accounts receivable balance on a renewal customer's balance sheet, it represents debits not yet offset by cash. A large, growing receivables number at a company you are about to renew can mean they book revenue aggressively but collect slowly. That tells you something real about their cash position and, downstream, their capacity to keep paying their SaaS vendors. The balance sheet is evidence. Double-entry is what makes it admissible.

Example: Infosys unbilled revenue, FY2024

Infosys reported ₹9,659 crore in unbilled revenue on its FY2024 balance sheet. Unbilled revenue is an asset, services delivered but not yet invoiced. In double-entry terms, when Infosys delivers work before sending the invoice, it records:

Debit: Unbilled Revenue, so the asset goes up. Credit: Revenue, on the income statement.

When the invoice is finally raised and the client pays:

Debit: Cash. Credit: Unbilled Revenue, so the asset comes back down.

The income statement saw the revenue when the work was done, not when the cash arrived. This is accrual accounting in action. The double-entry system allows Infosys to report accurately against the timing of delivery rather than the timing of payment. Their revenue figure reflects what they actually produced, not what cleared their bank account that quarter.

A $22 billion company like Infosys carrying ₹9,659 crore in unbilled revenue is normal and expected. A startup carrying unbilled revenue that dwarfs its cash balance is a flag worth investigating.

Go deeper, optional

• Infosys FY2024 standalone financial statements. Pages 8 to 12 show the real balance sheet. Look for the unbilled revenue and deferred revenue line items.
• Double-entry bookkeeping on Wikipedia. The history section is worth 5 minutes. Luca Pacioli codified this in 1494 and the system has not changed since.

Cross-module note

This connects to Module 5, Statistics and Decision Science: when you run an experiment and measure its impact on revenue, you need to know whether the revenue metric you are looking at is cash collected, invoiced, or recognized. Double-entry is what determines which number you are actually seeing.

Reflection, 2 to 3 minutes

Think about a SaaS company you know well: your employer, a vendor you use, or any subscription business. Write 2 or 3 lines.

• When a customer signs an annual deal and pays upfront, which two accounts move first in the vendor's books?
• If a customer delays payment by 60 days after signing, where does that show up on the balance sheet?
• What does a large, growing accounts receivable balance tell you about how aggressively a company recognizes revenue?

Appendix

Why does accounting use a two-sided system instead of just recording things once?

Single-entry bookkeeping, recording each transaction as one line, existed before double-entry and still shows up in simple personal finance apps. The problem is that it gives you no internal check. If you record "received ₹50 lakh" and nothing else, there is no way to know, from the books alone, whether that money is sitting in cash, already spent, or owed to someone. Errors and manipulation are easy to hide because there is nothing forcing the numbers to be consistent.

Double-entry forces every transaction to answer two questions simultaneously: what changed, and what caused it? When a company collects ₹50 lakh from a customer upfront, the books must record both that cash went up and that an obligation was created. If someone tries to pocket the cash without recording it, the books fall out of balance. If someone tries to inflate revenue, they need to create a fake counterpart entry somewhere else, which an auditor will look for.

The deeper reason the system survived five centuries is that it mirrors economic reality. Every transaction in a business is an exchange: you give something and receive something, or you create an obligation by receiving something you have not yet earned. Double-entry captures both sides of that exchange, which is why it produces a self-consistent picture of the business. A balance sheet where assets equal liabilities plus equity is not a coincidence or a rule imposed from outside. It is the natural result of recording every exchange as an exchange.

What is the general ledger and how does it relate to double-entry?

Every debit and credit entry goes into a specific account in the general ledger. The general ledger is the complete record of every account a company maintains: cash, accounts receivable, deferred revenue, retained earnings, and hundreds more depending on the size of the business. Each account has a running balance updated by the entries that flow into it.

The financial statements are summaries of the general ledger. The balance sheet takes every asset account and adds them up, takes every liability and equity account and adds those up, and presents both totals. The income statement takes every revenue and expense account and shows the net. Because every journal entry touched the ledger correctly, the summaries balance automatically.

When an auditor reviews a company's books, they are largely checking that the general ledger entries correspond to real transactions, meaning real invoices, real contracts, real bank statements, and that the entries were made to the correct accounts. Byju's entries were numerically balanced. The auditors' issue was that the accounts chosen for the credits were wrong. Revenue was credited instead of deferred revenue. The ledger balanced, but it lied.