Review-first automation controls for accounting firms
How Lift helps firms reduce preparation work without handing accounting control to unreviewed posting.
Lift is designed around a simple principle: automation should remove preparation work without removing accounting control. The default goal is not unreviewed posting. The goal is to prepare review-ready accounting output so the right person can approve it faster.
What review-first means
Lift prepares the supplier/contact, dates, totals, tax/VAT treatment, account coding, line information and source attachment before the reviewer confirms the result. The reviewer starts from a prepared draft, structured output, or workflow item instead of rebuilding the accounting entry from the document.
The exact review location depends on the route: Xero drafts are checked in the Xero workflow, Business Central routes are scoped around the relevant approval path, and import-led workflows should be checked before the file is imported.
Why this matters
The risk in invoice automation is rarely just reading the wrong number. It is sending accounting data forward before the judgement has been checked against the client, the destination system and the firm's own policy.
- VAT treatment can depend on client policy
- Chart of accounts decisions can vary by business
- Dimensions, departments or tracking categories may matter
- Some documents are unclear or incomplete
- Accounting firms need auditability and control
Review-first vs direct submission
Lift supports review-first workflows by default and can support direct submission where the firm chooses that route and the destination workflow allows it. The control decision should be made by route, not assumed across every client, supplier or document type.
| Review-first | Direct submission |
|---|---|
| Best for new clients or new workflows | Only where the firm chooses it |
| Reviewer confirms before approval or posting | Best for stable, predictable workflows |
| Safer for VAT and account treatment | Should still have exception handling |
| Useful during pilot and tuning | Should not be used for unclear documents |
What should be reviewed
Review should focus on the accounting fields that determine whether the output is ready to move on, not on retyping every field from the source document.
- Supplier/contact
- Document date
- Due date
- Currency
- Totals and VAT/tax values
- Account coding
- Line descriptions
- Tracking categories / dimensions where relevant
- Source attachment
- Exception notes
What Lift should flag instead of forcing
A control-led automation route should make uncertainty visible. Where the document or agreed policy is not clear enough, Lift should flag the issue for review instead of forcing a confident result.
- Duplicate documents
- Unsupported document types
- Missing or unreadable totals
- Conflicting VAT/tax information
- Uncertain supplier matching
- Unclear currency treatment
- Documents outside agreed policy
How review-first helps pilots
A pilot should measure how much preparation work Lift removes while keeping the reviewer in control. Start with real documents, check the prepared output against the firm's normal review standard, and use corrections to decide which routes can become more automated over time.
Common questions
Why not automate everything directly?
Some workflows may become suitable for direct submission, but review-first is safer where VAT, account coding, supplier matching or dimensions require judgement.
What should reviewers check?
Reviewers should check supplier, document dates, currency, totals, VAT/tax treatment, account coding, line descriptions, dimensions where relevant, and the source attachment.
What should Lift flag instead of forcing through?
Duplicates, unsupported documents, uncertain suppliers, missing totals, conflicting tax information and unclear currency or VAT treatment should be flagged for review.
For related setup detail, read about Xero invoice automation, why VAT policy is client-specific, and the Business Central implementation checklist.