Review is the step that disappears
Your firm has a rule: a senior looks at every VAT return before it goes. In a quiet week the rule holds. In the week before the seventh, with twenty returns due, it bends. A bookkeeper asks 'is it OK if I just file it, it looks fine?' and the senior, buried in their own work, says yes.
Most of the time it is fine. Now and then a return goes out with a duplicated bill, a supplier coded to the wrong VAT rate, or a large payment that should have been queried. You find out when the client's accountant asks, or worse.
Why reviews are hard to keep up
A proper review means opening the client file, running reports, comparing with last quarter and scanning for anything unusual. That takes time for each client, and it is mostly spent confirming that normal things are normal. The unusual items, which are the point of the review, are buried in the noise.
There is also no gate. The ledger lets a return be submitted by anyone with access. Whether review happened lives in someone's memory or a tick in a spreadsheet, so under pressure it is the first thing to give.
What skipped or rushed review costs
Errors that reach HMRC or the client are expensive to correct and damaging to trust. Reviewers who try to check everything become the bottleneck and work late before every deadline. And without a record of who reviewed what, you cannot show a client, an insurer or your own team how the firm makes sure work is right.
| Check a reviewer does by eye | What a machine can do first |
|---|---|
| Compare VAT figures with last quarter | Flag boxes that moved beyond your tolerance |
| Look for duplicate bills | Match same supplier, amount and date range |
| Scan VAT rates by supplier | Compare with that supplier's usual rate |
| Check suspense and uncoded items | Report any balance above zero |
| Spot unusual large payments | List items above a threshold for that client |
How we build a review queue for your firm
- When a bookkeeper marks a client ready for review, the system reads the ledger through the Xero or QuickBooks API and runs a set of checks you define.
- The reviewer sees a short page per client: the figures, the movement against previous periods, and only the items that tripped a check, each linked to the transaction in the ledger.
- The reviewer can clear each flag, send it back to the bookkeeper with a comment, or raise a query to the client.
- Sign-off is recorded with the reviewer's name, the time and the checks that passed. Your practice tool's job status updates from it.
- A deadline view shows every return due in the coming days with its review state, so the reviewer can plan the week rather than react on the last day.
- Where a return is filed without sign-off, the system notices on its next read and raises it with the manager.
The checks are yours. We start from the ones your reviewers already do by eye and add or remove them as you learn what catches real problems. Nothing here gives tax advice; the system shows facts and your people judge them.
Review that keeps pace with deadlines
Reviewers spend their time on the handful of items that deserve it instead of re-running reports. Bookkeepers get specific feedback on specific transactions, which teaches faster than a general 'be more careful'. The firm has a record of review for every return, and the pressure week feels less like a gamble.
Is review slipping in your firm?
- Returns sometimes go out with no senior look under deadline pressure.
- Reviewers are the bottleneck in the last days before filing.
- Errors are found by the client's accountant after the fact.
- You have no record of who reviewed which return.
- Review feedback to bookkeepers is general rather than specific.