AI invoice data extraction for accountants and their clients
Stop retyping invoices. AI reads scanned PDFs, photos, and any invoice format you receive – extracting every field that matters, exported straight to your accounting software. ZUGFeRD, XRechnung, Peppol/UBL, and ISDOC e-invoices supported natively, free.

You receive an invoice. An accountant, a junior, or a client opens it, reads it, and types the same fields into accounting software that the supplier already typed when they made the invoice. Number, date, due date, amount, VAT, supplier, variable symbol, IBAN. Twenty-something fields. Times every invoice. Times every client. Every month.
That’s the work most accountants and bookkeepers still do every day. Verifical takes it away.
The problem with manual invoice data entry
Manual data entry isn’t just slow. It’s where most bookkeeping errors come from. A misread VAT rate. A transposed invoice number. A wrong IBAN that takes a week to surface, when a payment bounces back. Every error has to be found, corrected, and re-exported. Usually by the same person who did the original entry, on a different day, under deadline.
Most accountants we talk to spend two to five hours per client per month just typing invoice data into their accounting software. For a firm with twenty SME clients, that’s a full working week, every month, spent moving data from one place to another. No analysis, no advice, no value the client would pay extra for.
There are three problems with how this is usually solved today:
- Generic OCR tools read characters but don’t understand invoices. They get the right number out of the right box on a known template, then break the moment the supplier changes layout.
- AI extraction tools (Dext, Hubdoc, Klippa, Rossum, and others) work well, but most are built for accounts payable inside a single company. They’re not designed for the accountant-client setup, where documents move between two parties and need to land in Pohoda, not NetSuite.
- Structured e-invoicing standards (Peppol/UBL across the EU, ISDOC in Czechia and Slovakia) already contain the invoice data in clean, structured form. But most extraction tools treat these files like any other PDF and run them through OCR anyway, charging for AI on data that didn’t need it.
Verifical was built to solve all three.
How Verifical reads invoices
When a document arrives in Verifical – whether the client uploaded it, a supplier sent it through the supplier portal, or it came in by email – Verifical reads it and extracts the data automatically.
For most invoices, Verifical uses AI that reads documents the way a person would: by understanding what each field actually means, not by matching positions on a template. There’s no template to build, no training period, and no setup for new suppliers. The first invoice from a brand-new supplier is read just as well as the thousandth from a known one. Layouts can change, languages can change, formats can change – the AI handles it. It works for scanned PDFs, photographs, regular PDFs from any accounting software and other formats.
This is the heart of what Verifical does, and it’s where the time savings come from. Most of the invoices a typical SME receives still arrive as PDFs or images. The job of turning those into clean, exportable data – which used to take an accountant hours per client per month – is what AI takes off the table.
For the smaller subset of invoices that arrive as structured e-invoice files (Peppol/UBL, ISDOC), Verifical reads them directly from the XML, no AI needed because the data is already structured. This makes those invoices essentially free to process. As EU mandates expand and more suppliers move to structured e-invoicing, more of your invoices will flow through this path automatically. See incoming e-invoices for the full list of supported formats.
This combined approach matters more than it sounds. A typical SME has a mix of suppliers: some send e-invoices because they’re on a modern invoicing platform, most send PDFs from their accounting software, some still send phone photos of paper receipts. With Verifical, all of them land in the same place, ready to export.
What gets extracted
Verifical extracts every field that matters for bookkeeping. The list currently includes:
- Invoice number
- Issue date, tax point date, due date
- Total amount, net amount
- VAT amount, VAT rate
- Currency
- Supplier name, supplier address
- Supplier company ID, supplier VAT ID
- Variable symbol, constant symbol. specific symbol.
- Bank account, IBAN, SWIFT/BIC
- Purchase order number
- And other fields
These are the fields that actually matter for SME bookkeeping. They cover everything an accountant needs to record the invoice in accounting software, reconcile against payments, and meet VAT reporting requirements.
What Verifical doesn’t extract today: line-item detail. For typical SME bookkeeping, header-level data is what gets recorded in the accounting system anyway. Line items are mostly useful for larger AP teams running three-way matching. They’re on the roadmap but not in the current release.
What happens after extraction
Extracting data isn’t much use if you still have to retype it somewhere else. Once Verifical reads an invoice, the data goes straight to the accountant’s chosen export format:
- Generic CSV. Configurable column mapping, works with any system that accepts CSV imports.
- Pohoda XML. The most common Czech accounting software. Verifical produces a Pohoda-compatible XML that imports cleanly, no manual edits required.
- DATEV (Germany and Austria) – coming soon.
- Xero (UK) – coming soon.
- QuickBooks – coming soon.
This is the part that closes the loop. The document arrives, the data gets read, the export file is ready, and the accountant imports it into their accounting software. End to end, no retyping.
See the full list and details on the export to accounting software page.
Built for the accountant-client relationship
This is the real difference between Verifical and most extraction tools on the market.
Dext, Hubdoc, Rossum, Klippa, and Tipalti are built for accounts payable inside a single company. One company has invoices, the same company processes them. The user is the AP clerk.
Verifical is built for the relationship between an accountant and their clients. Documents start at the client (or the client’s suppliers), get reviewed and extracted, and end up in the accountant’s accounting software. The accountant has many clients. Each client has many suppliers. The whole platform is designed around that, with strict separation between companies, status tracking per client, and a delivery trail both sides can see.
If you run an accounting practice serving SMEs in Europe, this is the difference between a tool that fits your workflow and one that fights it. More on this on the page accountants.
Frequently asked questions
How accurate is the AI extraction?
Very accurate on real-world invoices. Clear scans, native PDFs, and well-lit phone photos extract reliably across all relevant fields. Phone photos of crumpled receipts are less reliable, like with any AI tool. Verifical highlights low-confidence fields so you can review them before export. For invoices that arrive as structured e-invoices (Peppol/UBL or ISDOC), the data is read directly from the XML, so accuracy on those is 100% by definition.
What document formats does Verifical accept?
PDF (both native and scanned), ZUGFeRD and Factur-X (PDF with embedded XML), XRechnung (CII or UBL syntax), Peppol/UBL XML, ISDOC and ISDOCX, and image formats (JPG, PNG) for photographed invoices. Email attachments in any of these formats are processed automatically when sent to the company’s Verifical email address.
What languages does the AI handle?
English, German, Spanish, French, Italian, Czech, Slovak, Polish and other European invoices extract reliably. The underlying model (Azure OpenAI) is multilingual, so unusual cases generally still produce a usable result.
Does Verifical extract line items?
Not yet. The fields extracted today are header-level – what you need to record the invoice in accounting software, run VAT reports, and reconcile payments for typical SME bookkeeping. Line-item extraction is on the roadmap.
Is the data stored in the EU?
Yes. Documents are stored on AWS and Hetzner Object Storage, both in Germany. AI extraction runs through Azure OpenAI in EU data centers. No data leaves the EU at any point. This is a deliberate choice and the reason Verifical uses Azure OpenAI rather than OpenAI directly or other providers.
What does it cost per document?
Pricing is by plan, not per document. Each plan covers a monthly volume of documents – AI extractions and structured e-invoice parsing both included – with no per-page surprises. Structured e-invoices (Peppol/UBL, ISDOC) don’t count toward AI usage, so as more of your suppliers move to e-invoicing, your plan effectively goes further.
Verifical is a secure document exchange platform
built for accountants and their clients.
AI invoice data extraction with native Peppol/UBL and ISDOC support is part of every plan.
Start your free trial today. 45 days free, no credit card required.
For accountants
Streamline your document workflow and stop chasing files. AI reads your documents, and exports to your accounting software.
For clients
Stop printing, driving, and emailing. Upload documents, track payments, and access your archive anytime – all from your desk.
