KIVENTIS · B2B KI-Enablement DACH & APAC
Invoices arriving as email PDFs stall cash flow just as much as orphaned approval chains do. How mid-sized companies bring incoming invoice checks, approval workflows and posting into their ERP landscape – without risking compliance.
In many mid-sized companies, incoming invoices still arrive as PDFs by email. The path from mailbox to posting runs through manual entry, visual checks and an approval email chain – with the result: processing times in days, missed early-payment discounts and invoices stuck in a colleague's inbox.
The pressure comes from two sides. First, the public sector: Directive 2014/55/EU on electronic invoicing in public procurement has long made e-invoicing mandatory for suppliers of public authorities, and private customers are following the pattern. Second, scaling: companies that grow without adding headcount to accounting must automate – or the volume of documents becomes expensive.
Good news for SMEs: the technological effort is manageable. Most ERP systems (SAP S/4HANA, Microsoft Dynamics 365, Mesonic WinLine, proALPHA, abas, Infor, Sage) offer native or interface-retrofittable document capture – the real work lies in the process chain behind it.
An automated incoming invoice check consists of four interlocking steps. Intake happens centrally (email parser, supplier portal or an e-invoicing standard such as XRechnung or ZUGFeRD). Recognition extracts vendor, amount, tax and line-item data – rule-based for structured formats, model-based for free PDF layouts.
The quality core is the three-way match: invoice against purchase order and goods receipt. Amount, quantity and service period are checked with defined tolerances (a percentage margin for discounts or rounding differences, for example). If everything is within tolerance, the document is automatically released for posting; if it deviates, it goes to exception handling.
The decisive design choice is the separation of check and approval. The check can be machine-driven, while approval remains a human step with a defined threshold. Mixing both destroys auditability; automating both separately gains speed without loss of control.
Approval chains via email are the silent cost driver: not traceable, not escalatable, and not substitution-proof. Rule-based workflow automation replaces them with structured approvals: amount and cost center determine the approver, absence triggers the substitution rule, and overdue items escalate automatically to the next instance.
For ERP integration there are two common paths: native workflow functions of the ERP (approval processes in SAP S/4HANA or Dynamics 365) or a middleware layer that talks to the ERP via REST and OData interfaces. The latter is often the faster route because the core systems remain untouched.
A tiered logic has proven itself in practice: small amounts below an approval threshold run fully automatically, medium amounts get one approver, high amounts a multi-step chain. Finance defines the thresholds – not IT.
Once AI-supported document capture is in play (model-based extraction from free PDFs, agents for exception cases), the training mandate under Article 4 of Regulation (EU) 2024/1689 applies: employees supervising such systems need verifiable AI literacy. For accounting this concretely means: anyone who reviews and signs off an automated posting suggestion must be able to judge when that suggestion is plausible.
On top of that, the classic bookkeeping duties apply: every document must remain traceable without gaps (GoBD principles). That means a log entry per step – intake, recognition result, check run, approval by whom and when, posting. If a station is missing, the document becomes a problem in an external audit.
The audit trail is also the best tool against errors: if every intervention is logged, mispostings can be traced back in minutes instead of days – and internal audit receives its evidence without extra work.
The business case rests on three variables: processing time per document (today: minutes to days depending on the process path), error rate (manual entry typically produces typos and misassignments) and discount frequency (how many early-payment deadlines lapse unused).
As a rule of thumb: the more manual the process is today, the faster automation pays off – companies with shared-mailbox intake and email approvals typically see break-even in months, not years. Only your own baseline delivers a solid number.
The entry point does not have to be the entire accounting department. A common PoC limits itself to a vendor group with high, structured document volume: intake, three-way match, automatic approval below the threshold, posting. That yields measurable figures for the rollout – and the team has already built the governance routine.