Short answer: Automating invoice processing means incoming bills are read, checked, approved and posted with minimal manual work. At 1,500 invoices a year, a mid-sized company typically saves a four- to five-figure sum. Germany’s e-invoicing rules make the rebuild mandatory anyway.
Accounts payable is the most underestimated process in a mid-sized company. Invoices arrive by email, by post, as a PDF attachment and, increasingly, as a structured file no human can read. Then begins a chain of forwarding, chasing, signing and retyping that costs five to ten minutes per document and appears on no cost centre. At the same time the legal requirements are tightening: anyone who has not converted by 2028 will have to. This article shows how both fit together.
What the law requires, and from when
Since 1 January 2025, an invoice only counts as an electronic invoice in Germany if it is issued, transmitted and received in a structured electronic format that allows electronic processing. That wording sits in section 14 of the German VAT Act. A PDF attached to an email is therefore no longer an e-invoice but an “other invoice”. The format has to follow the European standard for electronic invoicing under Directive 2014/55/EU; the Federal Ministry of Finance names the EN 16931 series, XRechnung and ZUGFeRD from version 2.0.1 in its FAQ, excluding the MINIMUM and BASIC-WL profiles.
The distinction that matters is between receiving and issuing. Domestic companies have had to be able to receive since the start of 2025. For issuing, transitional rules apply, set out in section 27 (38) of the German VAT Act.
| Period | Receiving invoices | Issuing invoices (domestic B2B) | Who is affected |
|---|---|---|---|
| from 01/01/2025 | must be able to receive e-invoices | paper and other electronic formats still allowed | all domestic companies |
| until 31/12/2026 | unchanged obligation | paper or non-conforming formats still possible | all issuers |
| until 31/12/2027 | unchanged obligation | paper or non-conforming formats only where prior-year turnover is at most EUR 800,000; EDI extended as well | smaller companies and EDI users |
| from 01/01/2028 | unchanged obligation | structured e-invoice without exception | all domestic B2B transactions |
Two limits are easy to miss: invoices to private individuals are outside the obligation, and small amounts benefit from simplifications. Also note that 2027 and 2028 are inferred dates. The statute states when the transitional periods end, not when the duty begins.
The process in five stations
Automated accounts payable is not one tool but five stations. Automating only one of them moves the bottleneck instead of removing it.
- Capture. Every document arrives through a single entrance: a dedicated mailbox, an upload folder for scanned paper, an interface for portal invoices. As long as some invoices land in a personal inbox, nothing downstream works.
- Extraction. Structured formats are read directly. PDFs and scans go through text recognition, and a model pulls out invoice number, date, supplier, net, tax, gross and line items. Modern systems exceed 95 percent accuracy on known suppliers and drop noticeably on unfamiliar layouts.
- Checking. Matching against purchase order and goods receipt, duplicate detection, tax-rate plausibility, bank details against master data. This is where the security gain sits: the most common fraud case in mid-sized companies is a changed IBAN on an otherwise correct invoice.
- Approval. Rule-based by amount, cost centre and deputy rules, approved with one click from email or app, with an audit trail.
- Posting and archiving. Handover to the finance system or the tax adviser, plus audit-proof storage.
The three middle stations are what AI genuinely changes. Capture and archiving are classic software problems. If you want to build the same kind of chain for outbound documents, see our article on automating quotes in four steps.
Three routes that work in mid-sized companies
| Route | Typical cost | Implementation effort | Fits when … | Limits |
|---|---|---|---|---|
| Module inside your existing ERP or accounting system | often included in maintenance, or a paid add-on | low to medium | you run a well-maintained ERP with few exceptions | recognition quality is tied to one vendor |
| Specialised document capture platform | base fee plus per-document price, commonly EUR 0.15 to 0.40 | medium | many suppliers, varied layouts, multi-step approvals | an extra processor and an interface to build |
| Custom flow on an automation platform with a language model | platform licence plus token cost, usually under EUR 100 a month | high | company-specific checking logic across several systems | somebody has to own the running system |
The third route is both underrated and overrated. It is strong when your checking logic is specific, for example when invoices are matched against project budgets held in a separate system. It is weak when nobody in-house owns day-to-day operation. Our piece on AI automation use cases for SMEs puts the platform choice in context.
A worked example: 1,800 incoming invoices a year
A distribution business with 35 staff receives around 1,800 incoming invoices a year, roughly seven per working day. The internal administrative rate is EUR 45 per hour.
- Today: 7 minutes per document to open, forward, chase, code and file. That is 12,600 minutes, or 210 hours a year – EUR 9,450.
- Automated: 1.5 minutes per document for review and approval. That is 2,700 minutes, or 45 hours – EUR 2,025.
- Tool cost: EUR 0.25 per document gives EUR 450, plus a base fee of EUR 39 a month, so EUR 468. Total EUR 918.
- New running cost: EUR 2,943 instead of EUR 9,450. Saving: EUR 6,507 a year.
Budget a one-off EUR 3,000 for setup, interfaces and training. At a monthly saving of about EUR 542, that is recovered in roughly five and a half months. Two effects are not in the calculation and often matter more than the time: fewer lost early-payment discounts and a much better view of open liabilities at month end.
One honest caveat: the 1.5 minutes per document only apply once supplier master data is clean and recognition has been trained. In the first eight to twelve weeks you will sit closer to three or four minutes. Judging the project after four weeks gives you the wrong answer.
Rebuild accounts payable without replacing your system
We consolidate your intake channels, set up extraction, checking and approval, and hand over cleanly to finance or your tax adviser – with the e-invoicing deadlines in mind.
Where AI helps, and where it gets in the way
It helps with reading unstructured documents, assigning unknown suppliers, proposing cost centre and account from past postings, and flagging anomalies: a duplicate invoice number, an unusual amount, changed bank details.
It gets in the way when it posts without supervision. A language model produces a plausible coding even when it has misread the invoice. So: AI proposes, rules decide, a human approves – at least above a defined amount. Every automatic posting needs a log showing which model version made which suggestion. That is not bureaucracy; it is what keeps your books auditable.
First results in four weeks
- Week 1 – count. How many invoices arrive through which channel? Which suppliers make up 80 percent of the volume? Those two numbers decide the tool.
- Week 2 – consolidate the entrance. One central mailbox, one scanner rule, one clear instruction to suppliers about where to send invoices. This step alone brings noticeable calm.
- Week 3 – test extraction. Run 100 real documents through your preferred system and measure accuracy per field. Your invoices, not the vendor demo.
- Week 4 – map approvals. Who approves up to what amount, who deputises for whom? These rules are where projects fail, not text recognition.
For more processes with a similar payoff, see five processes small teams should automate. If you would rather not run the result yourself, we operate it for you as a managed service.
Frequently asked questions
Is a PDF by email still enough?
Not without qualification. Since 2025 a PDF no longer counts as an e-invoice under German VAT law but as an “other invoice”, which the recipient has to agree to. For issuing, it remains permissible until the end of 2026 or the end of 2027 depending on turnover. From 2028 it is over.
What is the difference between XRechnung and ZUGFeRD?
XRechnung is pure XML and unreadable without software. ZUGFeRD is a hybrid: a PDF with the structured data embedded. Both meet the requirements according to the Federal Ministry of Finance FAQ, though ZUGFeRD only from version 2.0.1 and not in the MINIMUM and BASIC-WL profiles.
Do I need a new ERP system for this?
Usually not. First check whether your existing system has a capture and approval module – often it is licensed but not switched on. Replacing the system is the most expensive answer to a problem that an interface usually solves.
What about data protection?
Incoming invoices contain business data and regularly personal data too, such as contact names. You need a processing agreement with the provider, an entry in your record of processing activities, and clarity on whether your documents are used for model training. Our GDPR practice guide covers the detail.
Is it worth it at 300 invoices a year?
Rarely on time saved alone. At small volumes the driver is the obligation: you have to be able to process e-invoices regardless. In that case the tax adviser’s portal or your accounting software is often enough, without an extra platform.
Next step
We look at your accounts payable process, count the channels and run the numbers with your data before recommending any tool. Start with our AI check or read about our automation services.
