If you're the only finance person at a charity in England and Wales, the audit threshold has gone up, and your trustees may well have read that as good news. For financial years ending on or after 30 September 2026, a statutory audit is required above £1.5m of income, up from £1m, or above £500,000 of income where gross assets are over £5m (gov.uk, September 2026). A charity at £1.3m that was audited last year will usually move to independent examination. It's easy for a board to read that as less work. But for the person who keys in every card payment, chases every receipt and splits every cost across grants, the month is still just as packed.
If you're in that position, this article looks at what the law still asks you to record, why that work lands on one person, and which parts of it a system can handle.
What the law asks you to record
Threshold changes decide who checks your accounts, but what you have to keep is unchanged. SORP 2026, which applies to accounting periods beginning on or after 1 January 2026 for charities preparing accruals accounts, adds disclosures, and at £1.3m you are most likely in its middle tier, which covers income between £500,000 and £15m. Both rest on the same day-to-day record, and a charity that has just left audit has less outside testing behind that record than last year.
Section 130 of the Charities Act 2011 requires trustees to keep accounting records that show and explain all the charity's transactions and disclose its financial position at any time with reasonable accuracy. Those records must show from day to day every sum received and spent, and what each one was for (Charities Act 2011, section 130). The duty applies at every size, whether the charity is audited, examined or neither.
Most of the admin sits in "what each one was for". A £38 payment at a cash-and-carry is easy to record as an amount; recording its purpose means knowing whether it was stock for the community café, snacks for a youth session, or both, and which grant, if any, should carry it. That information lives with the person who made the purchase, often on a shared debit card, and it is easily forgotten.
When the record is built at month end from a bank statement and an envelope of receipts, you are working out the purpose of each payment after the fact. It can still be accurate, but it depends on memory and on how many follow-up messages project leads answer. With restricted grants the gaps surface later, when a funder report or the year-end fund note needs a split nobody captured at the time.
Why the usual fixes still land on one person
The usual responses all route back through you:
• Leaning on the examiner or auditor. They review or test the records you hand them, and the duty to create and keep those records stays with the trustees under section 130.
• A better spreadsheet. A tab per funder makes reporting easier, but it is still filled in after the event, by the same person, and nobody else sees an entry before it lands.
• Asking staff to be more careful with receipts. Someone still has to chase, so you become collector, coder and checker at once.
The third point also matters beyond workload. The Charity Commission's guidance on internal financial controls asks that more than one person is involved in every financial transaction, with a different person authorising it from the one who made it (Charity Commission, Internal financial controls for charities, CC8, section 2.7). A finance function of one that also signs off its own entries has nobody else checking its work.
What a system can carry, and what stays with you
The better approach is to move the record to the moment of spend. The person who bought the stock attaches the receipt and picks the fund or project before the item can go anywhere, someone other than you approves it, and it reaches the ledger with its history attached.
That splits the work in two. A system can carry:
• capturing the receipt from the spender's phone or inbox and matching it to the payment
• requiring a fund or project code before a payment or invoice moves on
• routing approval to a budget holder or trustee who isn't you
• keeping a record of who did what, attached to each item
You and your examiner or auditor keep:
• fund accounting and the restricted-fund note
• income, donations and Gift Aid
• the accounts, SORP disclosures and trustees' report
• the examination or audit itself
Moss covers the first list. Receipts sent from a phone or by email are matched to Moss card payments and read for the amount, date and supplier. The fund or project code is set by the spender or by a rule, and the cost centre or cost carrier field can be made mandatory, so a payment can't go for approval until it carries one. Approval rules can route by amount or cost centre and stop anyone approving their own spend, and each item exports to your accounting system with its audit log attached.
The second list stays with you, because Moss handles spend but does not handle income, the accounts or the examiner's report.
What month end looks like
Once receipts are captured when the money is spent, a fund code is required before anything goes for approval, and someone other than you does the approving, month end changes shape. You open the ledger to find the café's cash-and-carry payments already coded to café stock or the youth grant, each with a receipt and the name of whoever approved it. Missing receipts and queried codes form a short exceptions list, which is all you review, and the examiner's sample comes back with the documents already attached to each line.






