Invoice Verification
Invoice verification is the systematic check of incoming supplier invoices for factual, arithmetic, and formal accuracy before they are approved for payment and posted.
Invoice verification is the control process by which a company checks every incoming supplier invoice before it is approved for payment and posted in accounting. The check covers whether the invoice is factually justified (was the service actually performed?), arithmetically correct (are prices, quantities, and totals right?), and formally proper (does it meet the mandatory legal details?). Only once the invoice has passed the check does a payment obligation arise, which the company then settles.
The core of invoice verification in purchasing is the reconciliation of three documents: the purchase order, the goods receipt or proof of service, and the invoice. This "three-way match" ensures that only what was actually ordered and delivered gets paid. In ERP and inventory management systems, this reconciliation runs largely automatically, so only discrepancies have to be handled manually.
At a glance
- Check of incoming invoices for factual, arithmetic, and formal accuracy
- The heart of the process is the three-way match: purchase order ↔ goods receipt ↔ invoice
- Protects against overpayment, incorrect postings, fraud, and input-tax risks
- Largely automated in ERP systems; only discrepancies enter the manual clarification process
- The mandatory details under Section 14 UStG are a prerequisite for input-tax deduction
What invoice verification covers
Invoice verification is traditionally divided into three checking dimensions that every incoming invoice must pass. They complement one another: only once all three have been passed is an invoice considered verified and ready for payment.
Only a fully verified invoice is approved for payment (payment release) and recorded as a liability in accounts payable. If a checking step is not passed, the invoice goes into clarification – for example as a query to the supplier or as an internal coordination with purchasing.
Factual check
The factual check establishes whether the invoiced service was actually delivered in the stated quantity and quality. The basis is the purchase order and the goods receipt or a proof of service. It also checks whether agreed terms, discounts, and payment periods have been observed. As a rule, only someone who initiated the order or can professionally assess the service may approve the factual check.
Arithmetic and formal check
The arithmetic check verifies all calculations: unit prices, quantities, subtotals, cash discount, VAT, and the final amount. The formal check ensures that the invoice contains all the mandatory legal details under Section 14 UStG – complete addresses, tax number or VAT ID, invoice date, sequential invoice number, description of the service, and the tax shown. If mandatory details are missing, the input-tax deduction is at risk.
How invoice verification works
In practice, invoice verification follows a fixed workflow. After the invoice is received – increasingly electronically as an e-invoice in the XRechnung or ZUGFeRD format – the document is captured and assigned to a purchase order. The automatic three-way match against order data and goods receipt then takes place.
If all line items match within defined tolerances, the invoice is approved automatically. If it deviates – for example due to quantity differences, price discrepancies, or a missing goods receipt – it is routed to the responsible party for manual clarification. Only after approval is it posted and the payment run initiated, taking cash-discount deadlines into account.
Three-way match
The three-way match compares three documents line by line: the purchase order (what was ordered?), the goods receipt (what was delivered?), and the invoice (what is being charged?). Only when item, quantity, and price agree across all three documents is the invoice considered confirmed. For pure services without a goods receipt, a proof of service or the orderer's approval takes its place – this is then called a two-way match.
Why invoice verification matters
Without consistent invoice verification, a company will sooner or later pay too much: for goods that were never delivered, for duplicate invoices, for wrong prices, or for manipulated documents. The check is therefore a central internal control against financial losses and fraud. At the same time, it safeguards data quality in accounting, because only correctly assigned amounts are posted to the right general-ledger accounts and cost centers.
For tax purposes, the formal check is decisive: only an invoice with all mandatory details under Section 14 UStG entitles the company to deduct input tax. Faulty invoices quickly lead to back payments in a tax audit. Proper invoice verification and audit-proof archiving are also part of the GoBD requirements for the traceability of business transactions.
Invoice verification in the ERP system
Modern ERP and inventory management systems map invoice verification as an end-to-end digital process. Because the purchase order, goods receipt, and accounts payable all sit on one data foundation, the system can carry out the three-way match automatically and approve matching invoices without manual intervention ("touchless posting"). Definable tolerance limits set the point at which a deviation still sends an invoice into manual review.
In addition, digital approval workflows handle the routing of disputed invoices to the right people, while an audit trail logs every checking and approval step in an audit-proof way. Incoming e-invoices in the XRechnung or ZUGFeRD format can be read in as structured data, so no data has to be keyed in manually. Systems such as the solutions linked below cover this process from invoice receipt to posting – often supplemented by OCR recognition for paper and PDF invoices.
DACH specifics and compliance
In the German-speaking region, invoice verification is closely interlocked with tax and commercial-law requirements. In Germany, Section 14 UStG governs the mandatory details of an invoice; the GoBD additionally require proper, unalterable, and traceable processing – from capture through checking to audit-proof retention during the statutory retention period – for invoices as accounting documents, eight years since 2025 (previously ten).
Since 2025, the e-invoicing obligation has applied step by step to domestic B2B transactions in Germany, making structured formats such as XRechnung and ZUGFeRD the norm and easing automated checking. Austria and Switzerland have their own sets of rules, for example the QR invoice as the Swiss standard for payment parts. Anyone purchasing internationally must also check input-tax deduction on intra-Community supplies and the correct VAT ID of the business partners.
Example
Practical example: price discrepancy in wholesale
A mid-sized wholesaler orders 500 cartons from a supplier at 12.00 euros each. The goods receipt posts 480 delivered cartons – 20 were not delivered. A few days later, the invoice arrives for the full 500 cartons at 12.50 euros each.
The ERP system runs the three-way match automatically and immediately detects two discrepancies: a quantity difference (500 charged versus 480 delivered) and a price difference (12.50 instead of the agreed 12.00 euros). Instead of approving the invoice, the system routes it into manual clarification with the buyer. The buyer complains to the supplier and receives a corrected invoice for 480 cartons at 12.00 euros. Without this check, the company would have paid 490 euros too much – on a single order alone.
Frequently asked questions
Matching ERP systems
Related services
Sources
Questions about Invoice Verification in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.