Thred
All posts

Reading an invoice is the easy part. Checking it is the work

Software that reads invoices is common. Software that proves the line items, VAT and totals are right before anything is booked is rarer. Here is what that checking involves.

Manoj Tutika7 min read

Working on this yourself? Talk to Mark, our co-founder. We’re here to solve it with you.

Book a demo
On this page

Invoice extraction turns a PDF or photo into structured data: supplier, dates, line items, VAT rates and totals. Reading those fields is now a solved problem for most invoices. The real work is checking that the fields agree with each other, meet the invoice rules and map to the right VAT code and account before anything reaches your ledger.

If you run finance for a growing company, or process purchase invoices for a portfolio of clients at an accounting firm, you have probably seen tools that "read" invoices with impressive accuracy. Then you still review every booking, because a 98% accurate reader on 400 invoices a month leaves you eight wrong ones and no idea which eight. This post is about closing that gap.

What does invoice extraction actually produce?

A good extraction is not a bag of text fields. It is a small record with a fixed shape, so every invoice can be checked the same way. In finance terms it has four parts.

  • Header. Supplier name and address, supplier VAT number, your company as customer, invoice number, invoice date, supply date and currency.
  • Lines. For each line, the description, quantity, unit price excluding VAT, line net amount and VAT rate.
  • VAT summary. Per VAT rate, the taxable amount and the VAT amount, as printed on the invoice.
  • Totals and payment. Total excluding VAT, total VAT, total payable, due date and the IBAN to pay.

That shape matters because the parts overlap. The lines imply the VAT summary, and the VAT summary implies the totals. When three parts of the same document describe the same money, you can test them against each other without ever opening the PDF. That is the trick that makes review scale.

The figure shows what that record looks like to the software and the rules it has to pass. You do not need to read code to follow it. Every check on the right is something an experienced bookkeeper does in their head when an invoice looks off.

Which checks should pass before an invoice is booked?

We group the checks into four layers. Each catches a different kind of mistake, and none of them needs judgement, so they can run on every single invoice.

1. Arithmetic inside the document

  • Quantity times unit price equals the line net, for every line.
  • The line nets for each VAT rate add up to the taxable amount for that rate in the VAT summary.
  • Taxable amount times the rate equals the VAT amount for that rate, within the rounding the supplier used.
  • Total net plus total VAT equals the total payable.

Rounding needs a stated policy rather than a fudge factor. Some suppliers round VAT per line, others once per rate. A difference of a cent per line is normal, a difference of €4.20 is a reading error. Allow the first, flag the second.

2. Legal content of the invoice

The EU VAT Directive (Article 226) sets out what a VAT invoice has to contain, and the Belastingdienst publishes the same list for Dutch businesses. It includes a sequential invoice number, the supplier's VAT number, the date of supply, the taxable amount and VAT per rate, and, for a reverse-charge invoice, your VAT number and a reverse-charge mention. In the UK, HMRC's VAT Notice 700/21 sets out the equivalent for a full VAT invoice.

Missing content is not a reading problem, but it is a booking problem. If the supplier's VAT number is absent, the invoice may not support reclaiming the input VAT. Software should notice that and ask for a corrected invoice, instead of quietly booking the VAT as deductible. Check with your accountant on how strictly to treat each missing element.

3. Consistency with what you already know

  • The supplier exists in your administration, and the VAT number on the invoice matches the one on file.
  • The IBAN on the invoice matches the supplier's known bank account. A changed IBAN is the classic invoice fraud signal and should always reach a person.
  • This supplier has not already sent an invoice with this number. Normalise first, so "INV-0042" and "inv 42" count as the same.
  • The amount is in line with this supplier's history. A cleaning company that bills €640 every month and suddenly bills €6,400 is worth a question.

4. Plausibility of the VAT treatment

  • The rate exists in the supplier's country. In the Netherlands that is 21%, 9% or 0%.
  • A supplier in another EU country charging no VAT, with a reverse-charge mention, points to reverse charge on your side.
  • A credit note has negative amounts and refers to the original invoice.

Only when all four layers pass does the invoice go straight through. Anything else goes to a person with the specific failed check attached, not a vague "low confidence" flag.

A worked example that fails one check

Here is an illustrative purchase invoice from an office supplier, Kantoorhuis Utrecht B.V., to a Dutch company. It has three lines at two VAT rates.

  • Office chair, 4 × €245.00 = €980.00 at 21%
  • Desk lamp, 6 × €38.50 = €231.00 at 21%
  • Coffee beans 1 kg, 10 × €18.40 = €184.00 at 9%

The VAT summary on the invoice reads €1,211.00 taxable at 21% with €254.31 VAT, and €184.00 taxable at 9% with €16.56 VAT. Total excluding VAT is €1,395.00, total VAT €270.87 and total payable €1,665.87.

Now suppose the scan is slightly smudged and the reader takes the quantity of desk lamps as 5. Every field still looks plausible on its own. But 5 × €38.50 is €192.50, not the €231.00 printed on the line, and the 21% lines would then add up to €1,172.50 instead of the €1,211.00 in the VAT summary. Two checks fail, both pointing at the same line. The fix is obvious, and nobody had to compare the PDF with the booking field by field.

That is the difference between reading and checking. A reader that is right 98% of the time still needs a human on every invoice. A reader plus checks tells you exactly which invoices, and which line, need you.

Why the VAT rate is not the VAT code

Extraction gives you a rate. Your ledger needs a VAT code, and the two are not the same thing. The code carries the rate, but also the direction (purchase or sale), whether the VAT is deductible, and which box of the VAT return it lands in.

On the invoice above, the two 21% lines take your input VAT code for the standard rate and the coffee line takes the input code for the reduced rate. All three feed box 5b of the Dutch return, the input VAT you reclaim. Same supplier, two codes.

Change the supplier and the picture changes. A software company in Ireland invoicing your Dutch BV for a subscription charges no VAT and states that reverse charge applies. The extracted rate is 0%, but booking it with a 0% code would be wrong. It needs a reverse-charge code that reports the service in box 4b and, usually, the same VAT as deductible in 5b. A supplier outside the EU, say in the UK, lands in 4a instead. The PDF looks almost identical in each case. The supplier's country, the customer VAT number and the reverse-charge text are what decide it. If you are unsure how a specific supply should be reported, check with your accountant.

This is where the line items earn their keep. One invoice can carry lines that belong on different accounts with different codes. The chairs might be office equipment or, above your capitalisation threshold, a fixed asset. The coffee is canteen costs. Booking the invoice as one total to one account throws that information away, and someone has to rebuild it at year-end.

Where should software decide, and where should a person?

Our view at Thred is simple. A model is good at reading messy documents and at proposing an account from a description and the supplier's history. Arithmetic, legal content and duplicate checks are rules, and rules should be run as rules, every time, not left to a model's impression.

So the order is fixed. The agent reads, the checks verify, and only then does it propose a booking with the account, VAT code and the evidence for each line. When the checks pass and the supplier and booking pattern are familiar, it books. When a check fails, or the supplier is new, or the IBAN changed, it asks you a specific question and waits.

In Thred Layer, that is how the Bookkeeper agent handles documents sent to your administration's document address, on top of the accounting software you already use. Every booking links back to its source document, so your accountant can open any journal line and see the invoice behind it.

What changes once invoices arrive structured?

More invoices will arrive as structured data rather than PDFs. Peppol and the European standard for e-invoices (EN 16931) are already common in public procurement, and the EU's VAT in the Digital Age package makes structured e-invoicing the default for cross-border B2B trade within the EU from 2030.

Structured invoices remove the reading step. They do not remove the checking step. A UBL file can still carry a wrong line total, an old IBAN, a duplicate number or a VAT treatment that does not fit your situation. The four layers above apply unchanged. Teams that build their review around checks rather than reading will find the move to e-invoicing uneventful.

What this means for your team

If you are a finance lead, the useful question about any invoice tool is not "how accurate is the reading?" but "which checks run before a booking, and what do I see when one fails?" If you run an accounting firm, the same question decides whether your team reviews 30 exceptions a day across all clients or skims 600 bookings hoping to spot the bad ones.

Reading got cheap. Checking is where the hours, and the errors, still are. See how agents handle it on top of your existing ledger on Thred Layer page, or how firms use the same approach across clients on Accounting Firms.

Book a demo to see an invoice go from inbox to checked booking.

Frequently asked questions

What should be extracted from a purchase invoice?

The supplier and its VAT number, invoice number, invoice and supply dates, currency, each line with quantity, unit price, net amount and VAT rate, the VAT summary per rate, the totals and the bank account to pay. Capturing all of them lets the parts be checked against each other.

How do you check that extracted invoice data is correct?

Run arithmetic checks inside the document: quantity times price per line, line totals per VAT rate against the VAT summary, and net plus VAT against the total payable. Then compare the supplier's VAT number and IBAN with your records and check the invoice number has not been booked before.

Is the VAT rate on an invoice the same as the VAT code in my ledger?

No. The VAT code also records the direction, deductibility and the VAT return box. An EU supplier's reverse-charge invoice shows 0% VAT, but in the Netherlands it needs a reverse-charge code reported in box 4b, usually with the same VAT reclaimed in 5b.

What must a VAT invoice contain in the Netherlands?

The Belastingdienst list follows the EU VAT Directive and includes a sequential invoice number, invoice date, the supplier's VAT number, names and addresses, the date of supply, a description and quantity, the taxable amount and VAT per rate, and for reverse charge your VAT number and a reverse-charge mention. Check with your accountant for special cases.

Do e-invoices remove the need for validation?

They remove the reading step but not the checking step. A structured invoice in UBL or Peppol format can still have a wrong total, a changed IBAN, a duplicate number or a VAT treatment that does not fit your situation.

Sources

  1. Council Directive 2006/112/EC on the common system of VAT (EUR-Lex)
  2. Factuureisen (Belastingdienst)
  3. Record keeping for VAT (VAT Notice 700/21), HMRC
  4. VAT in the Digital Age (European Commission)
  5. Peppol BIS Billing 3.0

Read next

Where Thred comes in

Thred Layer

Finance agents running on top of your existing ledger. You set the rules, approve the work and handle the exceptions. No migration.

Keep reading

Finance, handled.

Book a demo, or request a callback and we will call you.

Book a demo