Lyron
Finance

Accounts Payable with Automatic Three-Way Match

Every supplier invoice is held against the purchase order and the goods receipt before anyone looks at it. What lines up goes through; only the line that does not reaches a person – with all three documents side by side.

Context

Reading the invoice is the easy part

Extracting an invoice is the simplest step in the whole process. Supplier, invoice number, net amount, tax, payment terms – it is all printed on the document, and with ZUGFeRD or XRechnung it is machine-readable inside it. The question that actually costs time comes next: is any of it correct? Answering it requires two documents the invoice does not bring with it.

The counter-evidence sits elsewhere – the purchase order with buying, the goods receipt at the loading bay, in the warehouse or on site. Both are created at different moments, by different people, and often beside the system: reordered by phone, delivery note left in the van, quantity signed off on a clipboard. Even when everything exists, the lines rarely align: 20 metres of cable ordered, one drum delivered, 20.4 metres plus a drum deposit invoiced. Add part deliveries, collective invoices covering three orders, and alloy, energy or small-quantity surcharges nobody ordered.

So the bottleneck is not data capture but clarification – and clarification runs against the clock. Accounting asks buying, buying asks the supplier, the site manager is on site, and the early-payment discount expires in four days. That is why we build the matching logic and the tolerances first, not the form: whatever sits inside the agreed limits needs no approval at all. Whatever sits outside goes to exactly one person, who can see immediately which line fails and why.

For that match to start reliably, the vendor must already be approved. Supplier onboarding automation first collects master data and evidence, separates sensitive review steps and hands only the approved record to the ERP.

Use cases

Which invoices are worth automating

We start with the invoice type that occurs most often and has the clearest comparison data. Further types later use the same queue and the same rules.

Most common starting point

Material invoices with an order reference

The most common starting point: order and goods receipt exist in the system, and matching runs line by line against your tolerances.

Order numberPart deliveryPrice deviationTolerance

Material for sites and projects

Goods go straight to site and the delivery note is signed and photographed there. The invoice is matched to a project and job number rather than an order.

Project numberDelivery note photoSite manager

Recurring invoices without an order

Electricity, leasing, telephone, rent, insurance: there is no goods receipt here. The check runs against the contract, the previous month and the expected interval.

Contract numberMonth-on-monthRecurring entry

Interim and final applications

Each interim application is held against the amount invoiced so far and the reported stage of completion, with retention shown separately.

Cumulative totalStage of worksRetention

Subcontractor invoices

Reverse charge under section 13b, the exemption certificate under section 48b and its expiry date: if one of them is missing, nothing is approved, it is reported.

Reverse chargeExemptionValid until

Small amounts and ad-hoc purchases

Below a value limit you set, checking costs more than the mistake it prevents. Those documents pass with a coding suggestion and are sampled rather than reviewed.

Value limitSamplingCoding
Example

Three documents side by side, line by line

One invoice with four lines, held against the purchase order and the delivery note. Two lines go through, two do not.

Purchase order BE-2026-0413 6 Jul 2026 · Buying · Reinhardt Stahlbau GmbH
Delivery note LS-88214 17 Jul 2026 · Goods-in bay 2 · signed
Invoice R-2026-4471 21 Jul 2026 · €4,328.80 net · 2 % discount until 31 Jul
LineOrderDelivery noteInvoiceResult
10Steel beam IPE 200, 6 mItem 44-1180 40 pcs · €68.50 40 pcs 40 pcs · €68.50 matches
20Welding wire G3Si1, 15 kgItem 71-0442 12 pcs · €42.00 12 pcs 12 pcs · €42.90+ €0.90 per unit, + €10.80 in total price + 2.1 %
30Grating 1000 × 300Item 22-9007 24 pcs · €57.00 18 pcs6 pcs outstanding, due 4 Aug 18 pcs · €57.00 matches, part delivery
40Freight chargeno item number not ordered €48.00 approval needed

Tolerance per line: at most 2 % and at most €25. Both limits have to hold. Freight and surcharges without an order reference always go for approval.

checked, goes through approval needed deviation, invoice held
Invoice held. Line 20 goes to buying as a price deviation, line 40 to the cost centre owner. Lines 10 and 30 are checked and stay checked – but the invoice is still only posted as a whole. Deadline in view: the early-payment discount expires on 31 July.

Matching rarely fails at reading the invoice. It fails at the column nobody in the business keeps up to date.

Example data from a steel fabricator. The 2 % limit is a common starting value; the tolerance that applies to you is a decision for buying, not for the software.

How it works

From the mailbox to the payment proposal

  • Bring intake together

    Invoices from the central mailbox, from uploads and from supplier portals enter the same queue. PDF, scan, ZUGFeRD and XRechnung are treated alike, and the original document stays untouched.

  • Extract and assign

    Header and line data are captured as structured values. We identify the supplier by VAT number, IBAN and creditor number rather than by name, and pull the order number from the subject line, the body text and the line items.

  • Match against order and goods receipt

    Quantity, unit and price of every line are held against the purchase order and the goods receipt, with part deliveries and open quantities carried forward. In parallel, duplicates are checked by invoice number, creditor, amount and date.

  • Send only deviations for approval

    Lines inside the tolerance count as checked. Everything else is routed by cost centre, amount and project to the responsible person – with reminders, a named deputy and escalation once the deadline passes.

  • Hand over with the deadline attached

    Document, checked lines, coding suggestion and audit trail move on to DATEV, the ERP or the archive. The payment proposal carries the early-payment date, not just the due date.

Impact

What changes day to day

Today

  • Invoices sit in four mailboxes and one shared folder
  • Accounting collects order and delivery note by hand
  • Approvals run by email, with no deputy and no deadline
  • The early-payment discount lapses while one line is queried
  • Duplicates surface in the payment run, sometimes not at all

With automatic matching

  • Every invoice arrives through one queue and is numbered
  • Order, delivery note and invoice sit next to each other
  • Only deviations go out, to one named person
  • The payment proposal knows the discount date and days left
  • Duplicates are caught and held before the handover
Limits

Where matching does not help

Four points we settle before quoting. The first is a reason not to buy this yet:

  • Without purchase orders and recorded goods receipts there is no three-way match. If you order by phone and file the delivery note in a folder, the best we can give you is a well-sorted distribution to approvers – and €2,490 is not worth paying for that. Where orders are not captured systematically, purchase requisitions are the project that comes first.
  • Coding and input tax stay a professional judgement. We suggest account, cost centre and tax code from how the supplier was treated in the past and write the suggestion into the target system. Responsibility stays with your accounting team and your tax adviser. Reverse charge, intra-community acquisition or the line between expense and fixed asset are not decided automatically.
  • Extraction is good, not flawless. Structured formats are read in full; a creased scan with a handwritten note is not. We therefore work with confidence thresholds: anything below goes for visual checking instead of quietly running on with wrong values. Anyone expecting zero manual work will be disappointed – what is realistic is that the exceptions become few and visible.
  • No software can force a fast approval. We build in reminders, deputies and escalation, but if an approval has taken two weeks for years, automation only moves where the waiting happens. What helps is a binding deputy rule and a value limit below which nobody has to approve at all. Both are management decisions, not settings in a system.
Systems

Fits your accounting stack

DATEVSAPDynamics 365LexofficesevDeskMicrosoft 365SharePointZUGFeRD & XRechnungn8n
Scope and price

Scope and price

The entry price covers one intake queue, one match against one order system and one approval path. What moves the price, we say before the quote.

from €2,490 one-off
  • One central queue for a mailbox plus uploads and portal exports
  • Header and line extraction, including ZUGFeRD and XRechnung
  • Supplier identification by VAT number, IBAN and creditor number
  • Duplicate checking before every handover to the target system
  • Three-way match against one order and goods receipt system
  • One approval path by amount and cost centre, with a named deputy
  • Documented rule set, handover session and 30 days of support

What increases the price

  • Several legal entities with their own charts of accounts
  • A second source system for orders or goods receipts
  • Project references, interim applications and retention in construction
  • Coding suggestions learned from past supplier behaviour
  • Connecting an audit-proof archive or migrating historic documents

Several legal entities with their own charts of accounts, project references and interim applications typically sit well above this. We quote the binding fixed price after the intro call.

All prices excl. VAT · operation and further development optionally via a support package

Included

What you get

  • Production intake route

    Set up from mailbox to handover and signed off with your own real invoices

  • Documented rule set

    Tolerances, value limits, approval paths and exceptions – traceable and changeable later

  • Audit trail per invoice

    Which line was compared with what, who approved when, and what was handed over

  • Training for accounting and buying

    How deviations are worked through and what happens when an approver is away

Questions & answers

Frequently asked questions about invoice intake

Then a three-way match is not possible, and we say so before quoting. What still makes sense is a two-way check against the contract or the previous month, plus a governed approval path – but that is a smaller project. If you intend to start capturing orders, we begin there and add the matching later on the same route.
Structured formats such as ZUGFeRD and XRechnung are read completely, and clean PDF invoices almost as well. With scans it depends on quality: a straight pass through the scanner is fine, a folded fax with a handwritten note is not. Every value gets a confidence score and anything below the threshold goes for visual checking. After four weeks in production we know which suppliers generate manual work permanently.
No, and that is deliberate. Posting, reporting and archiving stay where they happen today. This automation takes over the stretch before that: intake, extraction, matching, approval and a complete handover. Your tax adviser works with the same documents as before, but receives them checked and with an audit trail.
Before every handover we compare against invoices already recorded: creditor, invoice number, amount and date. Suspected duplicates are held rather than passed on twice. The most common case is not a real duplicate but the same invoice arriving twice – as a PDF by email and later from the portal. That is exactly what one central queue catches, because both copies get the same internal number.
Your accounting team. We provide a suggestion based on how the supplier was treated before and label it as a suggestion. Unclear cases are not guessed; they are presented with the document and the comparison data. Tax edge cases stay explicitly with you and your tax adviser.
We deliver the preconditions: unaltered original documents, a complete record of every check and approval, and a permanent link between document and posting. The audit-proof archive itself is a separate system that we connect rather than replace. Which retention periods and process documentation apply to you is confirmed by your tax adviser; we provide the technical basis for it.

Do you know where your most expensive invoice is right now?

In the free intro call we work through ten real invoices with the order and the delivery note beside them. Afterwards you know how many would have gone through without a query, and what tolerance that would take.

Book a free intro call
Practical guide

Where accounts payable automation creates value in everyday work

Supplier invoices are captured centrally, extracted, validated against rules, approved and handed completely to accounting or ERP.

Three concrete operating scenarios to compare with your own process.
01

Unify invoice intake

Documents from inbox, portal and upload enter one shared intake route.

02

Prepare validation

Totals, supplier, purchase order and duplicates are checked before approval.

03

Complete accounting handoff

Original document, data, approval and validation status move to the target system together.

A strong fit when …

Documents, amounts and approvals follow explicit rules; exceptions must remain visible instead of being decided silently.

  • You handle recurring supplier invoices using repeatable rules.
  • The intake, target system and accountable business role can be named clearly.
  • Exceptions are allowed to remain visible and move to people deliberately.
Transparent potential estimate

Estimate time savings with your own volume

The calculator uses 11 minutes today and 3 minutes after automation as fixed example assumptions. It does not replace process analysis.

Illustrative estimate based on the visible assumptions — not a guarantee.

69.3Hours per month
832Hours per year
Additional measures after launch Cycle time Exception rate On-time handoffs
Frequently asked questions

What decision-makers should know before starting

How does accounts payable automation work in practice?
An invoice arrives by email, upload, portal or API. The workflow then validates the required data, runs approved steps and routes exceptions to the responsible person with context.
Which systems can be connected?
Typical integrations include DATEV, SAP, Dynamics 365, SharePoint, ERP. The decisive factors are a stable interface and clearly defined ownership of each data field, not a specific tool.
Which tasks deliberately stay with the team?
Unclear coding, purchase-order discrepancies, suspected duplicates and tax exceptions stay with accounting.
How is the automation introduced?
We document validation rules, approval limits and target systems, test with anonymised documents and release the workflow in stages. A tightly scoped first process typically takes 3–6 weeks; scope, interfaces and approvals determine the actual plan.
How can the benefit be measured?
Before implementation we record volume and current handling time. After launch we also compare Cycle time, Exception rate, On-time handoffs. The calculator on this page is a transparent estimate, not a promise.
Content reviewed on 26 July 2026 About Lyron AI