Reconciling invoices with delivery notes: the practical guide to stop overpaying

The most expensive mistake in accounts payable does not show up in the annual audit. It shows up line by line, invoice by invoice, over twelve months without anyone noticing. A missing box on every delivery. A shrinkage assumed as natural loss when it never actually reached the warehouse. A delivery note signed by the driver without counting.

Invoice-delivery note reconciliation - also called invoice-GR matching or two-way matching on goods receipt - closes that gap. This guide explains how it is done, what tools you need and the mistakes most finance teams make when they try to implement it by hand.

What invoice-delivery note reconciliation is

Reconciling an invoice with its delivery note means verifying that what the supplier charges matches what was actually delivered. It is a two-document check: the supplier invoice and the goods receipt - also called delivery note - signed by the warehouse.

The match is not done on totals. It is done line by line. Every reference appearing on the invoice has to be on the delivery note with the same quantity. If the delivery note records 480 units of a product and the invoice charges for 500, there are 20 units the company is about to pay for without having received them.

In companies with a formal purchase order (PO), this match extends to the PO and is called three-way matching. In companies that buy without a written PO - still most SMEs - the delivery note is the only witness between the invoice and reality. That is why invoice-delivery note reconciliation is the minimum viable control for any company receiving goods.

What this is not

Not bank reconciliation. Bank reconciliation crosses bank transactions with accounting. It happens after payment. Invoice-delivery note reconciliation happens before: its goal is to decide whether to pay, not to confirm that you paid.

Not counting the package at receipt. Counting boxes at the loading dock is necessary, but not enough. The packaging can be right and the contents wrong: 20 boxes ordered, 20 boxes received, but two of them with half the units. Without a per-line count, that difference reaches the invoice and nobody sees it.

Not checking the total. As with three-way matching, comparing invoice total against delivery note total - when the latter includes one - is a bare-minimum control. Cross-line offsets can make two totals match even though each reference is off.

Why the delivery note is the document most often ignored

The PO is checked because it is signed beforehand. The invoice is checked because it has to be paid. The delivery note is signed in five seconds on a loading dock, often without counting and without comparison against the PO. By the time it reaches finance - if it does - it is already signed and there is no way to dispute it with the supplier.

The Institute of Finance & Management (IOFM) study puts the discrepancy rate between what is invoiced and what is received at around 5-8% of total purchase volume in companies with no formal matching process. Most of those discrepancies are quantities. They are not fraud: they are honest errors from loading, picking or unreported breakage. But the company pays for them anyway.

For a company moving two million euros a year in purchases, that 5-8% is between 100,000 and 160,000 euros a year of invoiced goods that never arrived or did not arrive in the invoiced quantity. Most of it gets absorbed as warehouse shrinkage and is never reclaimed.

A well-managed delivery note is the only antidote to that bleed. It does not require changing the ERP, renegotiating with suppliers or rolling out a complex warehouse management system. It requires receipt discipline and an invoice-matching process when the invoice arrives.

The two documents: delivery note and invoice

1. The delivery note: the truth received

The delivery note is the document that accompanies the goods and certifies what left the supplier and what arrived at the warehouse. In Spain it is not a mandatory tax document - the Invoicing Order RD 1619/2012 regulates invoices, not delivery notes - but it is the standard support to record goods receipt.

A good delivery note includes: delivery note number, delivery date, supplier and recipient details, related PO number (if any), lines with description and quantity, and signature of the receiver. If it also includes line prices, even better for matching. But the critical field is quantity.

The delivery note can arrive in several forms: paper signed at the dock, PDF attached to an email, EDI XML file or manual entry in the ERP by warehouse staff. ininvoice accepts the first three formats with no transcription.

2. The supplier invoice: what gets charged

The invoice arrives after the delivery note - sometimes the same day, sometimes weeks later - by mail, email or supplier portal. It includes lines with description, quantity, unit price, taxes and total. It is the document that triggers the payment obligation.

To reconcile, the invoice has to link with the corresponding delivery note. Ideally the invoice cites the delivery note number. In practice many invoices do not: they aggregate several deliveries into a single monthly invoice or simply omit it. In that case, the matching system has to link by supplier, date and line descriptions, which is called fuzzy matching.

When the invoice is electronic - FacturaE in XML format or Peppol BIS - the data comes structured from the source. The match against the delivery note is more precise because it does not depend on OCR. The progressive rollout of Verifactu and mandatory e-invoicing in Spain will mean more invoices arriving already structured. Full guide on how to receive e-invoices in 2026 without breaking the AP flow.

How line-by-line matching works

Invoice-delivery note matching focuses on quantity variance. When the delivery note includes price, price is also cross-checked. When it does not, price variance is handled by the invoice-PO cross-check in companies that have a formal PO.

Quantity variance formula

qty_variance = (invoice_qty - delivery_note_qty) * po_unit_price

When there is no PO, the invoice price is used as the reference. When there is a PO, the PO price is used to avoid amplifying price errors inside the quantity calculation.

Example: order to a hospitality supplier

Delivery note of 12 March, receipt confirmed by the head chef:

Line	Product	Quantity received
1	Extra virgin olive oil (5L jug)	20 units
2	Crushed tomato (3kg can)	48 units
3	Coarse sea salt (25kg bag)	4 units

Invoice of 18 March, received by email:

Line	Product	Quantity invoiced	Unit price	Line total
1	Extra virgin olive oil (5L jug)	20 units	32.00 EUR	640.00 EUR
2	Crushed tomato (3kg can)	50 units	4.80 EUR	240.00 EUR
3	Coarse sea salt (25kg bag)	4 units	9.50 EUR	38.00 EUR

Line-by-line match result:

Line	Quantity variance	Status
1	(20 - 20) x 32.00 = 0.00 EUR	Reconciled
2	(50 - 48) x 4.80 = +9.60 EUR	Quantity exception
3	(4 - 4) x 9.50 = 0.00 EUR	Reconciled

The detected overpayment is 9.60 EUR on a single invoice. Sounds small. But the same supplier delivers three times a week to twelve sites. If that two-box difference repeats on 30% of deliveries, the annual aggregate is over 4,000 EUR with no one perceiving it as a problem.

What tolerance to apply to the invoice-delivery note match

Not every difference between invoice and delivery note justifies blocking payment. A 0.02 EUR difference costs more to investigate than to absorb. That is why tolerances are configured: thresholds below which the variance is accepted and the line is marked as reconciled.

The industry standard, per IOFM, applies tolerances in OR mode - accept if it meets the percentage OR the absolute criterion. The default tolerance in ininvoice is 2% or 1.50 EUR per line. Each company can adjust it per supplier, per category or globally.

Purchase type	Quantity % tolerance	Abs. tolerance
Bulk material (liquids, aggregates, kg)	3-5%	1.50 EUR
Discrete-unit product	0% (exact quantity)	1 unit
Perishables with shrinkage	5-8%	3.00 EUR
Critical, high unit value material	0%	0.50 EUR

The logic behind each threshold matters. Discrete quantities (boxes, units, pallets) do not allow percentage tolerance: either they arrive or they do not. Bulk does, since 3-5% allowance for shrinkage or rounding when loading the truck makes sense. In perishables - hospitality, food distribution - in-transit shrinkage is common and shows up on delivery notes with quantity slightly below the agreed PO.

What must never happen is for the tolerance to be the result of having no policy. If the company accepts 5% without knowing it, it is gifting 5% on every purchase without having made that decision. Tolerance is a conscious, documented, periodically reviewed decision.

Critical cases: partial deliveries, returns and shrinkage

Partial deliveries

The supplier ships the order in two trucks: 600 units on Monday, 400 on Friday. Two different delivery notes arrive. The invoice may come for all 1,000 units together or for each delivery separately.

The correct match adds the two delivery notes and compares the total with the invoice. If only one delivery note is matched against the full invoice, it looks like 400 units are missing when in reality they arrived on another delivery. ininvoice automatically detects partial deliveries by supplier and PO and aggregates quantities before matching.

Returns and credit notes

The warehouse receives 100 units, rejects 10 as damaged and signs the delivery note for 90. The supplier invoices the original 100 and issues a credit note for the 10 returned. The invoice-delivery note match has to link the credit note to the original invoice to reflect the correct net quantity.

When the credit note arrives before the match, everything reconciles. When the credit note arrives late - sometimes weeks later - the initial invoice generates an exception and is held until the credit note offsets the difference. This prevents paying gross and reclaiming later.

Declared shrinkage

Some sectors work with assumed shrinkage: the driver unloads 20 boxes, the delivery note records 19 because one broke in transit and the supplier also invoices for 19. This reconciles on the delivery note but not on the PO. If there is a PO, it goes to three-way matching; if not, it is accepted as an authorized partial receipt.

Missing delivery note

The invoice arrives and there is no delivery note on file. The usual cause is that the warehouse received the goods but did not pass the paper to finance. The invoice stays in pending-delivery-note status. If the configured deadline is exceeded - typically 5 business days - an alert is sent to the receiving team to locate the physical document or record receipt manually.

Common mistakes in SMEs

1. Signing delivery notes without counting. The driver arrives in a hurry, the operator signs without opening the boxes. Three weeks later inventory shows units are missing. With no verified-quantity delivery note, there is no possible claim against the supplier.

2. Archiving delivery notes in a warehouse box. Paper delivery notes pile up in the warehouse and never reach finance. When an invoice without a corresponding delivery note shows up, there is no way to match it. Delivery notes have to be digitized or recorded at the time of receipt.

3. Not recording partial receipts. 600 of the 1,000 ordered units arrive. The warehouse does not record the partial delivery note because they are waiting for the complete one. When the invoice for the 1,000 arrives, there is no record to match the first delivery against, and the calculated variance is wrong. Each partial delivery note has to be recorded on the day it arrives.

4. Only checking the delivery note total. The delivery note total and the invoice total match. The team assumes it is fine. But the delivery note has 50 units of product A and 30 of B, while the invoice has 40 of A and 40 of B. Totals match, lines do not.

5. Mixing delivery notes from several POs. The supplier groups deliveries from two different POs into one delivery note to save a trip. The invoice breaks it down by PO. If the system does not split correctly, quantities cross to the wrong PO and false exceptions are generated. The fix is to require delivery notes per PO or a PO identifier field on each line.

6. Excel as the delivery note archive. It works for low volume and a disciplined team. With 300 invoices a month, several receivers and vacations rotating, the file desynchronizes, versions overwrite each other and searches take minutes. The migration off Excel is one of the most profitable steps an AP team can take.

How ininvoice automates invoice-delivery note reconciliation

[Image: ininvoice reconciliation panel showing invoice and delivery note crossed line by line - coming soon]

ininvoice automates invoice-delivery note matching from the arrival of either document at your inbox. The process has four phases:

Phase 1: ingestion. ininvoice connects to Gmail or Outlook and scans the inboxes every 30 minutes. When an email arrives with an invoice or delivery note attached, it is captured. It also accepts manual upload and forwarding from other company mailboxes.

Phase 2: classification and extraction. A classification model decides whether the document is an invoice, delivery note, PO or other. The OCR engine extracts the data line by line: description, quantity, price when available, dates and references. Accuracy on standard documents is 95-98%; the rest is flagged with low confidence for manual review.

Phase 3: invoice-delivery note linking. If the invoice cites the delivery note number, linking is direct. If not, ininvoice uses fuzzy matching on supplier, delivery date, product descriptions and quantities to find the delivery note - or delivery notes - that correspond. When confidence is not enough, it proposes candidates for human confirmation.

Phase 4: reconciliation and exceptions. Once documents are linked, the variance formula is applied line by line with the configured tolerance. Reconciled lines are auto-matched. Those that exceed tolerance generate an exception. Each invoice gets a risk score combining variances, supplier age, possible duplicates and unusual patterns. The highest-risk invoices go first for review.

Exceptions are routed to the right owner: quantity variances go to receiving or warehouse; missing delivery notes to logistics; detected duplicates are auto-blocked and finance is notified. More detail in the exception management guide for accounts payable.

ininvoice is not an ERP and does not replace the accounting system. It acts as a reconciliation layer between the supplier inbox and the ERP. Approved data is exported to Holded, Sage, A3 and other systems as clean accounting entries.

The cost of not reconciling invoice with delivery note

The cost is measured on three fronts: overpayments, team time and regulatory risk.

Overpayments. According to IOFM data, the discrepancy rate between invoice and receipt is between 5% and 8% of purchase volume in companies without automated matching. For a company moving 2 million euros a year, that is between 100,000 and 160,000 EUR of goods invoiced but never delivered or delivered short. Most of it is absorbed as warehouse shrinkage and never reclaimed from the supplier.

Team time. The American Productivity & Quality Center (APQC) puts manual AP department productivity at 6,082 invoices per employee per year. With automation, it rises to 23,333. The difference, at an average labor cost in Spain, equates to a meaningful per-invoice saving. On a volume of 300 invoices a month, that is thousands of EUR in annual savings on staff time alone.

Regulatory risk. The Immediate Information Supply system (SII) requires received invoices to be reported to the AEAT within four days of being booked. If the matching process is slow, the risk of late reporting goes up. With Verifactu and mandatory e-invoicing rolling in, deadlines tighten and invoice-receipt mismatches become more visible to the regulator. Consult your tax adviser on the specific implications of your situation.

Implementing invoice-delivery note matching without changing ERP

The rollout does not require migrating ERP or renegotiating supplier contracts. It requires three elements in order:

1. Disciplined receiving. Each delivery has to generate a record with verified quantities. It can be a signed delivery note, a manual entry in the system or an email confirmation from receiving. Signing without counting is the first thing to fix.
2. Invoice channelling. All supplier invoices arrive at the same inbox - typically invoices@company.com. If they arrive at ten different addresses, there is no way to process them centrally.
3. Matching tool. A system that reads both document types, links them and applies the variance formulas with the configured tolerance. It can be an ERP module, a dedicated system or ininvoice as a layer between the inbox and the existing ERP.

The most underrated step is the first. Without disciplined receiving, no tool can compensate for missing data. The most common failure: the delivery note arrives signed but with contents unchecked, which makes the document formal but unreliable.

Once the data is in order, the tool does the work. ininvoice connects to the inbox and starts processing invoices and delivery notes from day one. Historical PO loading - when applicable - is done via CSV or API. Plug and play.

For companies that already have SAP, Microsoft Dynamics or a large ERP with an AP module, matching can live inside the ERP. But implementing and configuring that module takes months and a consultant team. For SMEs and mid-market companies, a specialized plug-and-play SaaS tool is usually the practical option. You can compare options in the touchless AP guide.

11 frequently asked questions about invoice-delivery note reconciliation

What happens if the invoice arrives before the delivery note?

The invoice stays in pending-delivery-note status. It is not rejected or sent back to the supplier. When the delivery note confirms the receipt, the system resumes matching automatically. If the delivery note does not arrive within the configured period, ininvoice alerts the receiving team to locate it.

Does it work with paper delivery notes?

Yes. Paper delivery notes are digitized with a phone or a scanner and uploaded to the system. ininvoice extracts the data line by line with the same accuracy as a digitally generated PDF, as long as image quality is acceptable. Ideally, ask the supplier for a PDF delivery note when possible.

What tolerance is applied by default?

The default tolerance in ininvoice is 2% or 1.50 EUR per line (OR mode). Each company can configure it per supplier, per product category or globally. For perishables or bulk material the percentage usually goes up. For discrete units it stays at zero or very low.

What about partial deliveries?

Each partial delivery note is recorded and linked to the corresponding PO or supplier. The system aggregates quantities across all linked delivery notes before matching with the invoice, so a delivery in two trucks does not generate a false variance for the pending quantity.

What if the delivery note does not include prices?

Invoice-delivery note matching focuses on quantities. When the delivery note does not include prices - which is common - price verification depends on the invoice-PO match if there is a formal PO. If there is no PO, the only price reference is the supplier's historical, which is informative but not conclusive.

How is this different from three-way matching?

Three-way matching crosses three documents: PO, delivery note and invoice. Invoice-delivery note reconciliation crosses two: delivery note and invoice. It is the minimum control when there is no formal PO, and the first practical step for companies that do not yet have a written PO process.

Does it detect duplicate invoices?

Yes. ininvoice cross-checks invoice number, supplier tax ID, amount and date range (+/-30 days). If two invoices coincide, the second is auto-blocked. More in the duplicate detection guide.

Is invoice-delivery note reconciliation a legal requirement?

There is no specific Spanish regulation that requires it. But internal control frameworks, external audits and compliance requirements treat it as a standard practice. Any auditor expects to see it in companies with meaningful physical-goods purchase volume.

Does it work with FacturaE and Verifactu?

Yes. Invoices in FacturaE (XML) and Verifactu-compliant invoices arrive already structured. ininvoice reads them directly with no OCR and the match against the delivery note is more precise because quantity and price data are guaranteed from the source.

Does it integrate with Holded, Sage or A3?

ininvoice exports reconciled invoice data in formats compatible with Holded, Sage 50/200 and A3 ERP. It does not compete with the ERP: it sits in front of it. Native integrations are in development.

How long does activation take?

Plug and play. Connect the inbox and it starts working. There is no implementation project, no mandatory training and no setup fee. The first invoices are processed from day one. Historical PO loading - when applicable - is done via CSV or API and does not block the start of processing.