Why your back office needs double-entry, not a spreadsheet
25 September 2026 · Müşavir
Most small teams start with a spreadsheet: one row per payment, a column for income, a column for expense. It works right up to the first hard question.
The questions a list cannot answer
- A customer paid 12.000 TL against three invoices. Which one is still open?
- You collected a government fee on behalf of a customer. Is that revenue?
- A supplier invoice arrived in euro. What is the VAT you can deduct this month?
- Your accountant says the balance sheet is off by 4.300 TL. Where?
Each of these needs two facts per transaction, not one: what changed, and against what. That is what double-entry gives you.
What balancing actually buys you
When every invoice, payment and expense writes a journal entry where debits equal credits:
- Customer balances become derived, not typed. Nobody maintains a “still owes” column by hand.
- Transit money stays out of your profit. A government fee you collect and pay on sits in a liability account; it never inflates revenue.
- VAT reports are a query, not a reconstruction. Collected VAT and deductible VAT are separate accounts, so the monthly figure is already there.
- Errors localise. If a total is wrong, the unbalanced entry tells you which record to look at.
The part people skip
Double-entry is only useful if it happens automatically. If someone has to remember to post a journal entry after issuing an invoice, it will be skipped in the week you are busiest; and the ledger you are supposed to trust becomes the thing you have to check.
So the rule we follow: no financial action without its entry. Issue an invoice, the entry is written. Record a payment, the entry is written. Delete a draft, nothing was written in the first place.
That is the difference between having accounting records and having a spreadsheet that resembles them.