Training a project bookkeeper in the first month
A practical first-month plan for teaching a new project bookkeeper to record transactions, handle questions and prepare donor reports.
A new project bookkeeper may receive a bank statement, a cash box, paper receipts and a reporting template, then be expected to produce reliable figures. If nobody explains the project rules or reviews the early work, mistakes can become part of the routine.
The first month should be a supervised learning period, not an immediate handover. The aim is to show how each transaction moves from approval to payment, recording and reporting. The plan below can be adapted for a volunteer, administrator or finance assistant who has little formal accounting training.
Start by defining the job and its limits
Before teaching software or spreadsheets, explain what the bookkeeper is responsible for. Write the main duties on one page. These may include entering transactions, maintaining a cashbook, checking that documents are present, preparing a draft report and raising questions. Keep the wording practical.
Also explain what the bookkeeper must not decide alone. A bookkeeper should not approve their own payment, change a budget without authority, invent missing details or sign on behalf of another person. If a manager approves spending, that responsibility remains with the manager even when the bookkeeper enters the transaction.
Give the new person the documents that govern the work. These normally include the approved budget, donor reporting format, account codes, project dates, bank details, payment approval rules and any limits on particular costs. Do not assume that a budget heading such as “community mobilisation” is self-explanatory. Show which real activities belong there and which do not.
Agree who will answer different questions. The project manager may confirm whether an activity happened. The authorised signatory may explain a payment. A finance supervisor may decide which account code to use. A clear route for questions prevents the bookkeeper from guessing when a document is unclear.
- List the records the bookkeeper will maintain.
- Name the person who approves transactions.
- Name the person who reviews the bookkeeping.
- State when the first draft report is due.
- Confirm where confidential records must be kept.
Use the first week to follow real transactions
During the first week, choose several completed transactions and follow each one from beginning to end. Use different examples, such as a bank transfer, a cash purchase, a staff advance and a payment to a supplier. The purpose is to understand the project’s transaction trail before entering new data.
For each example, ask the bookkeeper to identify the request, approval, proof of payment, evidence of what was bought and the budget heading. A receipt alone may show that money was spent, but it may not show who approved the spending or why it was needed for the project.
For example, suppose the project paid 240 in local currency for meeting-room hire. The file contains an approved request, the venue invoice, proof of bank payment and a signed attendance list. Ask the bookkeeper to explain the connection between these papers. Then compare this with a 240 payment that has only a handwritten note. The amount is the same, but the second transaction needs questions before it can be treated as complete.
Introduce the idea of a clear audit trail in ordinary language. Another person should be able to start with a line in the report and find the related entry, payment and supporting documents. They should also be able to start with a bank payment and find where it appears in the books and donor report.
Let the new bookkeeper write down uncertainties. Questions are useful during training. Quietly filling gaps with assumptions is not.
- What was purchased or paid for?
- Why was it needed for the project?
- Who approved it?
- How was it paid?
- Which budget line and reporting period apply?
Practise entries under supervision in week two
In the second week, let the bookkeeper enter a small batch of current transactions while a reviewer remains available. Provide a blank or training copy if an error in the live file would be difficult to reverse. The bookkeeper should enter the date, reference, description, payee, amount, payment method and account code.
Teach descriptions that will still make sense months later. “Transport” is weak. “Minibus hire for village training on 12 May” is more useful. A good description does not replace supporting evidence, but it helps reviewers understand the entry and locate the correct papers.
Use round-number exercises to teach coding. Suppose the budget has three headings: training materials, local travel and venue hire. A supplier invoice contains notebooks for 300 and room hire for 500. The payment total is 800. The bookkeeper should not place the whole amount under whichever heading appears first. Show how to record two lines that add back to the single payment, while keeping the common payment reference.
Also cover corrections. If an amount or code is wrong, the bookkeeper should follow the agreed correction method. They should not hide the original entry, overwrite approved records without explanation or alter supporting documents. A spreadsheet correction may need a note. A bound cashbook may require a single line through the error, with the correction initialled according to local procedure.
Review the practice entries together. Ask the bookkeeper to explain each choice rather than simply pointing out errors. This reveals whether the rule is understood or whether the right answer was reached by chance.
- Check that transaction dates come from a defined source.
- Use one reference system consistently.
- Separate mixed-cost payments where required.
- Record the actual payment method.
- Keep a visible explanation for corrections.
Build judgement through questions in week three
Bookkeeping is not only data entry. The new person must learn when to stop and ask. During week three, use examples where the answer is not obvious. Include a receipt dated outside the project period, a payment with no approval, an unclear business name, a personal mobile-money account used for a project purchase, or an amount that differs from the approved request.
Do not teach the bookkeeper to repair weak evidence by creating documents after the event. A note written later can explain what happened, but it should be honestly dated and approved by the appropriate person. It must not pretend to be an original receipt or earlier authorisation.
Give the bookkeeper a simple query log. Each line can include the transaction reference, issue, person asked, date raised, response and current status. This separates unresolved items from ordinary entries and gives the supervisor a practical list to follow up.
For example, a withdrawal of 1,000 is recorded for an outreach activity. Documents explain 920 of spending, while 80 is said to have been returned. The bookkeeper should ask where the returned money was recorded and who received it. They should not change one receipt to 1,000 or enter the unexplained 80 as miscellaneous expenditure.
Teach respectful questioning. “Please confirm the purpose of payment B014 and provide the approval” is clearer than “This payment is wrong.” The bookkeeper’s role is to identify what is missing or inconsistent. The responsible manager then provides information, takes corrective action or decides how the item should be treated.
- Does the transaction fall within the project period?
- Is the purpose connected to the approved activity?
- Is the amount supported and approved?
- Do the payment record and documents agree?
- Is any balance, refund or advance still outstanding?
Use week four for a supervised draft report
In the fourth week, ask the bookkeeper to prepare a draft for a short reporting period. Use the actual donor template if possible, but mark the report as draft. The task should include transferring totals from the accounting record, applying the correct budget headings and listing unresolved questions.
Ask for a short explanation of the figures. If the report shows 3,500 for training, the bookkeeper should be able to identify the entries making up that total and explain where they came from. They should not type a figure into the report merely because it looks similar to the budget.
The reviewer should test selected lines in both directions. Start with several report lines and trace them back to the records. Then start with several recorded payments and confirm where they appear in the draft. This is a training review, so discuss the reason for every correction.
Finish the month with a written feedback meeting. Identify what the bookkeeper can now do without help, what still requires review and what has not yet been taught. Reporting may involve exchange rates, payroll, shared costs, tax deductions or partner expenditure. Do not give responsibility for these areas merely because the first month has ended.
Set a review arrangement for the next reporting cycle. A new bookkeeper may prepare entries independently while another person reviews corrections, unusual costs and the draft donor report. Access to the bank account, accounting file and physical cash should still follow proper separation of duties.
- Keep the first report clearly marked as draft until approved.
- Record corrections and explain why they were needed.
- Retain a list of open questions with named owners.
- Agree which tasks still require prior review.
- Schedule a follow-up after the next reporting cycle.
Questions
Should a new bookkeeper enter old transactions in the first month?
Only with supervision and a clear purpose. A small set of past transactions can be useful for practice because the final treatment is already known. Avoid handing over a large backlog before the person understands the project, account codes and evidence requirements. Backlog pressure can encourage guessing and make errors harder to identify.
What if the organisation has no written finance procedures?
Start with a short project-specific instruction sheet. Record who approves spending, which records are required, how references are assigned, where files are stored and who reviews reports. The sheet does not replace a full policy, but it gives the new bookkeeper consistent instructions while management develops or approves broader procedures.
How often should the new bookkeeper’s work be reviewed?
Review small batches frequently at first rather than waiting for the end of the month. The appropriate timing depends on transaction volume and risk. Reduce supervision only when entries are consistently explained, supported and correctly coded. Donor reporting should still receive an independent review.
What should happen when the bookkeeper finds a missing receipt?
The bookkeeper should record the question and ask the responsible person for the original evidence or an honest explanation. They should follow the organisation’s policy for missing documents and donor rules. They must not create a false receipt, copy an unrelated document or describe an unsupported amount as something else.
A good first month combines explanation, supervised practice, questions and a carefully reviewed draft report. The bookkeeper should finish with clear duties, known limits and a route for raising concerns, not just access to a spreadsheet. Where it fits the organisation’s process, Honest Record can assist with matching transactions and documents and checking the resulting records, while approval and judgement remain with responsible people.
Honest Record reads the statement and receipts, matches them, applies your fund's rules and verifies every row before the Excel exists. Free 14-day trial, no card.
Upload your first month free See a sample report