Processing purchase invoices automatically: how to stay in control

How do you process purchase invoices automatically while keeping a grip on postings, VAT and exceptions? The workflow, the checks and a setup checklist for firms.

The short answer

Automatic processing of purchase invoices works when you let software handle the repeatable steps and explicitly leave the assessment of exceptions to a person. Recognising the supplier, the amounts and the VAT, matching against an earlier posting and preparing a suggestion: that is work software does better and faster than an employee processing a hundred invoices a day. Deciding whether a mixed cost is deductible, whether a new supplier is legitimate, or whether a deviating VAT rate is justified: that remains a matter of judgement.

The gain is therefore not less control, but less data entry. Confuse those two and the work simply moves: from typing to repairing.

What automatic processing actually does

The term covers four different things, and it helps to look at them separately.

Document recognition extracts data from a PDF or photo: supplier, invoice number, date, amounts, VAT amounts per rate. Modern recognition also reads tables and can distinguish between the invoice total, the subtotal and the amount payable.

Matching compares the invoice with what you already know: does this supplier exist, has this invoice been processed before, which ledger account was used previously, is there a purchase order or a contract.

The posting suggestion combines those two into a draft: ledger account, VAT code, cost centre, possibly a split across several lines.

Posting is the step in which the suggestion becomes an entry. This is where the question belongs of when that may happen automatically and when it may not.

The five steps in the purchase flow

1. Submission

The fewer channels, the less searching. A fixed email address per administration that suppliers and the client send to, plus an app for receipts, covers most situations. Agree that the client does not forward documents with comments in the email body, because that information gets lost: comments belong with the document.

2. Recognition

The software reads the document. Crucial for quality: recognising VAT per rate. A receipt mixing 9% and 21%, deposits or packaging at the zero rate, and rounding differences of a cent are the places where things go wrong. During setup, check how the software resolves this and what happens when the VAT lines do not add up to the invoice total.

3. Matching

The invoice is linked to a supplier and to its history. Watch for two pitfalls. The first is the supplier name that is spelled differently on every invoice, which gives you duplicate supplier accounts. The second is the mirror image: different suppliers with nearly identical names ending up under one account.

4. Suggesting

Now the draft suggestion appears. A usable suggestion shows what it is based on: previous postings for this supplier, a rule the firm has set up, or a recognised pattern. Without that reasoning you cannot check a suggestion, only believe it.

5. Reviewing and posting

Here your setup determines what happens. Invoices that meet fixed conditions can go through automatically. Anything that deviates goes to an employee, with the deviation visible at the top.

Where it goes wrong in practice

Which checks you build in

Automation without stopping points produces silent errors. These six checks belong in every setup.

• Amount check. The sum of the lines must equal the invoice total, within a margin you define yourself.
• VAT check. Per rate, the VAT amount must match the net amount. For deviations larger than a few cents: review.
• Duplicate check. On supplier, invoice number, date and amount combined, not on one of them.
• New supplier. A first invoice from an unknown supplier always passes a person.
• Threshold amount. Above an amount chosen by the firm, always review, even for a known supplier.
• Deviation from the pattern. An amount that differs sharply from earlier invoices from the same supplier, or a different ledger account than usual.

VAT exceptions you never post blindly

In these situations the risk of an incorrect return is greater than the time saved by automatic posting:

• invoices with foreign VAT, and the question whether it is an intra-Community acquisition or a cost incurred abroad;
• reverse-charged VAT, for example in construction;
• the margin scheme, for example when buying second-hand goods;
• mixed costs with a partially deductible element;
• prepayments and deposits without an underlying supply;
• invoices without a valid VAT identification number where you do claim a deduction.

To reconcile these items with the return, it helps to record who performed the assessment. See also Audit trail: what an accounting firm must be able to demonstrate.

Setup checklist

1. One submission channel per administration, with a fixed email address and an app for receipts.
2. Recorded rules per client: which suppliers post to which account, with which VAT code.
3. A threshold amount above which every invoice is reviewed.
4. Duplicate checking switched on for the combination of fields.
5. An alias list for supplier names, so name variants do not create new supplier accounts.
6. An exception list of VAT situations that always pass a person.
7. Recording per entry: source, suggestion, who reviewed it, what was changed.
8. A monthly sample of automatically posted invoices, even when nothing has been flagged.
9. An agreement with the client about submission deadlines and about what you do with unclear receipts.
10. An evaluation after three months: which exceptions occurred so often that a rule can be added?

What it delivers, and what it does not

A realistic result: less entry time per invoice, less back and forth with the client about missing documents, and consistent quality because the same checks are always performed. What it does not deliver: less need for expertise. The work that remains is precisely the harder part, and that calls for people who know why an entry is correct.

A good measure of the quality of your setup is the number of corrections after the monthly close. If that stays high, your stopping points are in the wrong place. See Setting up the monthly close for the checks that belong there.

Dividing roles within the team

Automation changes who does what, and that goes wrong if you do not make it explicit. Three roles are enough for most firms.

The processor handles the daily flow: resolving exceptions, requesting missing documents, reviewing suggestions that fall outside the fixed rules. This is work in which someone quickly learns to spot patterns.

The configurator maintains the rules per client: which supplier posts to which account, which threshold amounts apply, which exceptions always pass a person. Without an owner those rules quietly go out of date and the number of exceptions grows.

The reviewer samples automatically processed items and judges whether the setup still fits the client. This is the role that is dropped first in busy months, which is exactly why it belongs in the planning rather than in whatever time is left.

Measuring whether it improves

Without figures, the discussion about automation remains a matter of intuition. Four simple measures suffice, provided you establish them once before making the change.

Measure one month before the switch and three months after. That is enough to see whether time genuinely shifts rather than moving into repair work.

Next step

See how Giroo Administration substantiates posting suggestions, which checks are enabled by default and where processing stops as soon as there is doubt.

Content reviewed: July 2026.

Related articles

• Bookkeeping for beginners: the complete guide
• Records retention obligation: what, how long and how?
• Recording private use of a company car: benefit in kind, mileage log and VAT in 2026

Back to the knowledge base