Skip to content
EMPOBase
en

Double-entry bookkeeping explained for program staff

By the EMPOBase team · · 4 min read

Short answer

Double-entry bookkeeping records every transaction twice: once where the money came from or what it bought, and once where it went. Total debits always equal total credits, so errors show up fast. Program staff do not need to post entries. They need to know how to read a ledger line, spot a wrong project code, and ask the right question when a number looks off.

Key points

  • Every transaction has two sides, and the two sides must be equal.
  • A debit is not good or bad; it is the left side of an entry, and its effect depends on the account type.
  • Program staff mostly need to read ledger lines, not write them.
  • Most project-level errors come from a wrong project, grant or budget line code on the entry.

Why should program staff care about bookkeeping?

You manage a project, and the project spends money. Finance records that spending in a ledger. When the ledger and your own records disagree, someone has to work out why. That conversation goes faster when you understand how the ledger is built.

You do not need an accounting qualification. You need five ideas: accounts, debits, credits, balance, and codes. This article covers each in plain words.

What does “double-entry” mean?

Every transaction has two effects. If you buy a laptop for 800 with cash, two things happen: you have a laptop, and you have 800 less cash. Double-entry bookkeeping writes both effects down.

  • One line is a debit.
  • One line is a credit.
  • The debit total must equal the credit total.

That last rule is the point. If someone types 800 on one side and 80 on the other, the entry does not balance, and the error is visible right away. Single-entry systems, such as a simple cash list, cannot do this check.

What are debits and credits?

A debit is an entry on the left side of an account. A credit is an entry on the right side. Neither word means “good” or “bad”, and neither means “money in” or “money out” on its own.

What each does depends on the type of account:

Account typeExampleA debitA credit
AssetBank, equipmentIncreasesDecreases
ExpenseTravel, salariesIncreasesDecreases
LiabilityAmounts owed to suppliersDecreasesIncreases
IncomeGrant incomeDecreasesIncreases
Fund or equityRestricted fund balanceDecreasesIncreases

A simple memory aid: assets and expenses grow with debits. Everything else grows with credits.

How does a real NGO transaction look?

Say your project pays 1,200 for a training venue, and the money leaves the bank account.

  1. Debit Training costs (an expense) by 1,200.
  2. Credit Bank (an asset) by 1,200.

Debits equal credits. The expense went up, the bank balance went down.

Now say a donor sends 50,000 for a grant:

  1. Debit Bank by 50,000 (the asset grew).
  2. Credit Grant income, or a restricted fund, by 50,000.

In an NGO, the second line often carries more detail than in a business. It can name the grant and the fund, so the restricted money stays visible. Our article on restricted and unrestricted funds explains why that matters.

How do you read a ledger line?

A ledger line usually shows the same few things. Learn to scan for them:

  1. Date. Which period does it fall in?
  2. Account. What kind of cost or income is it?
  3. Debit or credit amount. Which side, and how much?
  4. Project, grant and budget line. Which part of your work does it charge?
  5. Description or reference. What was it for, and which document backs it up?

For program staff, line 4 is the most important. A cost with a correct account but the wrong project code still lands in the wrong place. Your budget vs actual report will then look wrong, even though every entry balanced.

What mistakes should you watch for?

The balance rule catches typing errors. It cannot catch a wrong decision. These are the errors a program manager is best placed to spot:

  • Wrong project or grant code. A cost charged to a neighbouring project.
  • Wrong budget line. Travel booked as equipment, so one line looks overspent and another looks underspent.
  • Wrong period. A February cost posted in March.
  • Missing cost. You know a purchase happened, but no entry exists yet.
  • Duplicate. The same invoice entered twice.

When you spot one, send the finance team the date, the amount and the code you expected. Do not ask them to “fix the budget”. Ask what the entry says and why.

How do corrections work?

Good books do not erase posted entries. They add a new entry that reverses the old one, then post the right entry. The trail stays complete: anyone can see the original, the reversal and the correction. This is why finance staff ask you for a reason, not just a new number.

Where EMPOBase fits

EMPOBase’s General Ledger is a double-entry ledger. It rejects any journal where debits and credits are not equal. Each line can carry a project, a grant, a grant budget line and a fund, so one entry feeds the ledger, budget vs actual and restricted-fund tracking together. Closed periods are protected, and corrections use reversal entries. The ledger is built for projects, grants and restricted funds. It is not statutory accounting, so keep your statutory books with your accountant. You can read more in the documentation or ask for a walk-through.

Questions people ask

Is a debit always an increase?

No. A debit increases asset and expense accounts and decreases income, liability and fund accounts. A credit does the opposite. That is why the account type matters more than the word.

Why does finance reject an entry that is off by a small amount?

Because the books only work if both sides match. Even a small gap means a line is missing or mistyped, and the cause can be larger than the gap.

Do I need to learn this to manage a grant?

You need the basics. If you can read a ledger line and see which project, grant and budget line it charges, you can check your own spending and ask better questions of the finance team.