A checklist for bookkeeping foundations: seven documents that matter more than software

The tool that improves a small set of books the most is almost never software. It is a page of writing that tells whoever is coding today what the person coding last March decided.

Software moves data, but it cannot say which account a courier charge belongs in, whether the annual renewal has been spread yet, or why the holding account has a balance.

Those answers live in seven small documents. A business that keeps them can survive a change of system, a change of bookkeeper, and a year-end review. A business without them cannot, whatever it is running.

What to take away

1. The account definitions note

One line per account, saying what belongs in it and, where two accounts compete, which one wins.

Without it, coding is a memory test, and the same kind of cost lands in three places depending on who touched it. The report then shows a trend that is really a change of habit. With it, a new person codes correctly on day one and a disagreement becomes a question about the note rather than an argument.

Write it as sentences, not labels. "Courier and postage: outbound delivery of goods to customers. Delivery of stock inbound goes to purchases, because it is part of what the stock cost." That second clause is the whole value of the document.

2. The recurring schedule

A single list of everything that has to be posted in a period without a document arriving to prompt it.

Prepayments releasing a slice each month. Accruals to reverse. Deferred income to release as it is delivered. The periodic charge on things bought to keep, where your accountant has set the policy, which starts from the line the federal guide to business expense resources draws between a cost and a capital outlay. Loan repayments to split between principal and interest.

Each row carries the amount, the periods it covers, what is left, and where the underlying paper is filed. This is the schedule that stops a year of subscription income landing in December, and it is the first thing to disappear when a bookkeeper leaves.

3. The reconciliation file

Not the fact that an account reconciled. The list of differences, with a reason beside each one, kept for every period.

Its real job is comparison across months. An unpresented payment that appears in the file three months running is not outstanding, it is an error, and only the file makes that visible. A reconciliation stored as a tick in a box tells you nothing next month.

4. The open questions log

Every transaction somebody was unsure about, with the document attached, the question written out in full, and the name of the person it is going to.

Two columns matter more than the rest: the date it was raised and the date it was answered. When a log measures that gap in months, it describes a real problem. It usually explains whatever sits in the holding account.

The recurring failures worth logging are set out in the mistakes that damage a small set of books.

5. The month-end checklist

Written down, in order, with a name against each line.

The reason to write it rather than remember it is that the useful checks are the boring ones, and the boring ones are what get skipped when the month is busy. A checklist also makes the work handoverable: someone covering for a fortnight can do it, which is not true of a routine that lives in one head.

Keep it short enough to finish. A list of forty items gets abandoned in week two; a list of eight gets done every month for years.

6. The chart change log

Every account added, merged, renamed or retired, with the date and the reason.

This document explains the April discontinuity in a comparative report, so without it someone next year will think a cost doubled when two accounts were merged.

The log costs one line per change, but rebuilding that information from the ledger costs a day. Put the design decisions behind those changes with your chart of accounts.

7. The reference convention

How documents are named and where they live, so that the reference on an entry actually finds the paper.

Any convention works if it is followed. Date first, then a type code, then the counterparty, then the document number: it sorts usefully and survives being read over the phone.

The federal guidance on what records a business keeps lists what must be findable. The convention exists so that list is retrievable, not theoretical. Filing by whatever the supplier called the attachment does not work.

Judging a package by whether it can hold these

Read a feature list with the seven documents in your hand and the questions get sharper.

None of that is exotic, and a package that cannot do it is asking you to keep the artifacts somewhere else, which is a workable answer as long as it is a deliberate one. The wider question of what to demand from a system before committing is covered in the guide to accounting software.

If you only have an hour

Write the account definitions note, from last year's own report. Take each line, say what belongs in it, and note where you had to think. The places where you had to think are exactly where coding has been inconsistent, and you will find two or three of them.

Then start the open questions log with whatever is in the holding account today. Those two documents alone will change the next year-end conversation from a reconstruction into a review. The method they support is set out in the bookkeeping foundations guide.

Common questions