Automate supplier invoice approval: from PO and delivery note matching to a person's sign-off

Approving an invoice is not signing a piece of paper. It is validating that what was invoiced matches what was ordered and what was received, that the amount is within tolerance, that the right owner signs off and that everything is recorded with traceability. When this flow is manual, a company with 500 monthly invoices spends between 80 and 140 hours/month on approvals alone. When it is automated, those hours move to exceptions, which are the minority.

This guide describes how to make the transition without turning admin into a six-month project, what amount thresholds are sustainable, what is kept in the audit trail and what ROI to expect. It is written from the payer side, not the issuer.

What does automating invoice approval mean?

"Automating approval" is not a single act, but a sequence of layers that get replaced one by one. It pays to distinguish levels because most companies confuse the first one with the complete solution.

Level 0: Manual approval over email

The invoice arrives in the inbox. Someone prints it or forwards it. They request a physical signature or email approval. They take it to accounting. If the amount is high, they take it to management too. The approver opens the PO PDF in another folder, compares mentally, signs. Average time per invoice: 12 to 25 minutes. Error rate: high. Traceability: zero.

Level 1: Approval over a structured email flow

Shared mailboxes or mail labels, rules that move messages. Still manual but the invoice does not get lost. The owner confirms by email. Average time: 8 to 15 minutes. Traceability: partial (emails are archived, but unstructured).

Level 2: Approval inside the ERP module

The ERP (Holded, Sage, A3, Contasol) receives the invoice as an attachment and lets you mark "approved". There is an internal validation flow with notifications. Substantial improvement but everything upstream is left out: email ingestion, line extraction, PO and delivery note matching. Average time: 5 to 10 minutes. Traceability: good inside the ERP.

Level 3: Automatic matching, approval by a person

A dedicated layer between the inbox and the ERP. It ingests the invoice, parses its lines, runs three-way matching pre-tax against PO and delivery note, holds only the exceptions with their reason, marks matching invoices as ready for a person to approve and exports approved invoices to the ERP. The owner only checks what requires their judgment. Average time: 30 seconds per reconciled invoice, 3 to 5 minutes per exception. Traceability: complete, immutable, exportable.

The really significant jump is from Level 1-2 to Level 3. That is the jump this guide describes.

The 4 bottlenecks in the manual process

Before designing the automated flow, it is worth identifying what is being replaced. In any company, four bottlenecks appear with similar frequency.

1. Data re-keying

The operator opens the PDF, reads invoice number, date, amount, taxable base, VAT, and types them into the ERP. On invoices with multiple lines (typical in distribution, retail, construction), re-keying multiplies. Human error rate: 1 to 3% on critical fields. The cost is not just time: every typing error drags into bank reconciliation.

2. Looking up the matching PO

The invoice arrives referencing the PO by number - except when it does not. In practice, between 20 and 40% of invoices do not include the PO number or include it with a typo. The operator searches the ERP by supplier, approximate date, amount. Average time: 3 to 7 minutes per search. And when there are several open POs with the same supplier, the search turns into an investigation.

3. Variance resolution

When the invoice does not reconcile with the PO, the operator notices a difference in the total. What they cannot tell at a glance is why. Is it the quantity? The unit price? The VAT? A misapplied withholding? Decomposing the variance requires line-by-line comparison, and that is only feasible manually when the invoice has few lines. On 30 or 50-line invoices it gets approved "because the difference is small". And that is where overpayments slip through.

4. Approval chasing

The invoice waits for sign-off. The owner is on a trip, on site, on a customer visit. The admin asks by email, by WhatsApp, by call. A week passes. By the time the signature arrives, no one remembers which PO it was. The end-to-end approval cycle in a typical company is 6 to 14 days. The legal B2B payment term in Spain is 30 days from receipt of the goods or services, extendable by agreement to a maximum of 60 (Law 3/2004, art. 4); a significant share of the delay is internal, not treasury-driven.

The four bottlenecks are what any automation system has to solve simultaneously. Solving only one does not improve the aggregate flow; it shifts it.

Automated workflow step by step

The end-to-end flow has six phases. Each replaces one of the manual steps and connects to the next with no manual checking when everything reconciles; approval is always given by a person.

1. Ingestion from Gmail

OAuth connection to the admin department's inbox. The system reads incoming emails, identifies those containing invoices (PDF or image attachment), extracts the files and discards the rest. It never modifies or deletes emails. Ingestion is continuous: invoices enter the system within minutes of the supplier sending them.

2. OCR and IDP (Intelligent Document Processing)

Each invoice is parsed. If it is a native PDF the text is extracted directly; if a scanned PDF or an image, OCR is applied. The result is a canonical object with number, date, supplier (tax ID), individual lines with description, quantity, pre-VAT unit price, applied VAT, base, total. The difference between classic OCR and IDP is robustness on poorly formatted invoices: IDP understands the structure of the document instead of reading fixed positions.

3. Line-by-line three-way matching

The system locates the matching PO (by explicit reference or by fuzzy matching on supplier, date, descriptions and amounts). It locates the goods receipt. And compares line by line, pre-tax: invoice unit price vs PO unit price, invoiced quantity vs received quantity. Tolerances are configurable: absolute (e.g. 1.50 EUR per line) and percentage (e.g. 2%), with an OR combiner by default. Any line outside tolerance generates a variance typed by cause.

4. Matching invoice: ready to approve

If every line reconciles, the invoice is marked as matched, ready for a person to approve. If a line falls outside tolerance, it is held with the line and the difference visible. Who signs each amount tier is your company's policy (next section); in ininvoice no invoice approves itself, not even in the lowest tier.

5. One-click approval

The approver sees a clean view in their inbox: invoice, referenced PO, delivery note, reconciled lines, amount to approve. A single button. If they need to reject or query, they leave a comment that enters the audit trail. No need to open the ERP, look up the PO or download a PDF.

6. Export to the ERP

Approved invoices are exported as a CSV or Excel file importable into the ERP (Holded, Sage 50/Despacho, A3, Contasol, Quipu, Anfix), with the validated data: supplier, lines, VAT, withholding if applicable, due date. Subsequent bank reconciliation is simpler because the amounts are already correct. The operational source on the payer-side model is in touchless accounts payable.

Approval tiers by amount

Defining thresholds is not optional. With no rules, every invoice requires the same signature and the human bottleneck does not move. A common and sustainable distribution. The tiers are your internal policy: ininvoice does not route invoices by amount and has no "automatic" tier; even when the invoice matches, a person approves it.

Amount tier	Approver	Suggested internal deadline	Additional condition
< 500 EUR	Area lead (one click)	Same day	Three-way matching reconciles and supplier is recurring
500 - 5,000 EUR	Area lead or purchasing supervisor	24 h	Three-way matching reconciles
5,000 - 25,000 EUR	Finance director (CFO)	48 h	Three-way matching reconciles and supplier is verified
> 25,000 EUR	Dual signature CFO + CEO (or board)	72 h	Three-way matching reconciles and framework contract reviewed
Any amount with variance	Owner of the variance type (purchasing, warehouse, accounting)	Until resolved	Payment block until closure

The amounts are indicative. An accounting firm processing AP for small clients may operate with lower thresholds (50 / 500 / 5,000); an industrial distributor with high volume can lift them (1,000 / 10,000 / 50,000). What matters is that the tiers are defined, documented and applied consistently, not left to each operator's interpretation.

A rule worth adding whatever the tier: the first invoice from a new supplier deserves a closer look, to check the supplier data, the accounting code and the payment terms before it is approved.

Digital audit trail

The audit trail is the immutable record of everything that has happened with every invoice: who ingested it, who approved it, who modified any field, when, with what result. It is not an optional logbook; it is the piece that justifies traceability before an external audit, a tax authority inspection or an internal control.

For each invoice, the audit trail keeps at minimum:

• Email origin (sender, subject, message-id, attachment hash).
• Ingestion date and time.
• Initial version extracted by OCR/IDP and any manual corrections with their author.
• Associated PO and delivery note, with matching timestamp.
• Detected variances and their resolution (what was changed, who, why).
• Approvals: user, date and time, comment.
• Rejections and reasons.
• Export of the approved invoice: date and time.

This level of granularity satisfies a COSO-style internal control framework (segregation of duties, full logging, authorizations), and is the substrate on which SOX-equivalent certifications are built as the company grows. For annual account audits, it lets you reconstruct any invoice without asking for attachments. For AEAT inspections, it shows that booked data corresponds to the physical invoices.

The audit trail must be immutable: not even an administrator can delete lines. Corrections are made by adding new entries that supersede the previous one. Retention must cover at least the tax limitation period (four years, General Tax Law, art. 66) and the six years required for commercial records (Commercial Code, art. 30).

Compliance: Verifactu invoices in the approval flow

Verifactu (Royal Decree 1007/2023) requires the issuer's billing software to be adapted before 1 January 2027 for corporate income taxpayers and before 1 July 2027 for everyone else, after Royal Decree-law 15/2025; businesses on the SII are outside it. From then on, invoices issued by suppliers using Verifactu-compliant software will carry a QR code. The receiver sees them like any other invoice, but can now verify against the AEAT that the invoice exists in the issuer's record.

The QR verification against the AEAT is a separate check that ininvoice does not perform today. ininvoice reads the PDF invoice and runs the control that matters on the receiving side: line-by-line three-way matching, duplicate blocking and tax validation, all recorded in a per-invoice audit trail.

Verifactu, where a company chooses to verify the QR, reduces fraud (made-up or duplicate invoices the supplier did not actually issue). It does not replace three-way matching, because it confirms the invoice exists but not that what is invoiced matches what was ordered and received. For details on operational impact on the payer flow, see Verifactu from the paying company side.

In parallel, the entry into force of mandatory B2B e-invoicing (Law 18/2022, developed by Royal Decree 238/2026: from 6 October 2027 for companies with turnover above EUR 8 million and from 6 October 2028 for everyone else, according to the AEAT calendar) will shift the invoice input format from PDF toward structured XML, starting with large suppliers. During the transition, most invoices a company receives will still be PDF. Receiver-side coverage is in mandatory e-invoice reception.

ROI: how much is saved by automating approvals

The average cost of processing a received invoice is between 9 and 16 EUR per invoice in companies with no meaningful automation, and below 3 EUR in best-in-class companies. These amounts include staff time, infrastructure, errors and rework.

For a typical Spanish company, the calculation looks like this:

• Company A: 300 invoices/month. Manual cost: 300 x 12 EUR = 3,600 EUR/month · 43,200 EUR/year. Automated cost: 300 x 3 EUR = 900 EUR/month · 10,800 EUR/year. Gross saving: 32,400 EUR/year.
• Company B: 800 invoices/month. Manual cost: 800 x 12 EUR = 9,600 EUR/month · 115,200 EUR/year. Automated cost: 800 x 3 EUR = 2,400 EUR/month · 28,800 EUR/year. Gross saving: 86,400 EUR/year.
• Company C: 2,000 invoices/month. Manual cost: 2,000 x 12 EUR = 24,000 EUR/month · 288,000 EUR/year. Automated cost: 2,000 x 3 EUR = 6,000 EUR/month · 72,000 EUR/year. Gross saving: 216,000 EUR/year.

The calculation above does not include two additional savings that are typically of the same order of magnitude:

• Undetected overpayments. The gap between matching by totals and matching line by line ranges from 0.3 to 1.2% of invoiced volume. For a company with 5 million euros of annual purchases, that is 15,000 to 60,000 EUR/year of silent bleed. Reproducible detail in matching by totals: the silent trap.
• Early-payment discounts. An approval cycle that drops from 10 days to 2 days lets you capture early-payment discounts common with strategic suppliers (1 to 3% on the amount), where before the invoice would have been approved past the discount window.

ininvoice pricing is tailored: it is set in a proposal within 48 hours of seeing your invoices (annual volume, companies, ERP), with no implementation fee. With the gross savings of the three scenarios in view, the proposal is weighed directly against them.

How to start with ininvoice

The operational rollout of an automated approval flow with ininvoice has three phases. None of them requires an external consultant or affects ERP historical data.

Phase 1: Connection and set-up (day 1)

OAuth connection to the admin department's Gmail. Purchase orders and delivery notes come in like invoices, by e-mail or upload. Configuration of matching tolerances (absolute and percentage). Estimated time: 2 hours.

Phase 2: Parallel ingestion (days 2-7)

The system processes incoming invoices in parallel to the current flow. During this week, the admin keeps their manual routine and compares with what the system suggests. Discrepancies are reviewed and the tolerances adjusted if needed.

Phase 3: Process cutover (from day 8)

The manual flow is replaced. Invoices are approved in ininvoice. ERP exports are done from ininvoice. The admin approves what matches and focuses on the exceptions the system holds with their reason, not on bulk processing. The first two weeks after the cutover are monitored more closely to catch edge cases (uncommon suppliers, seasonal invoices).

Pricing is tailored: a proposal within 48 hours of seeing your invoices. For a broader look at the control an AP automation layer adds over suppliers, see supplier invoice control. If you arrived from the blog, the original piece we expand here is automate invoice approval: the digital flow.

Frequently asked questions

What does automating supplier invoice approval mean?

It means replacing the manual flow (receive invoice by email, print, request signature, book) with a system that ingests the invoice from the inbox, extracts its lines, reconciles against PO and delivery note, marks the invoice that matches as ready for a person to approve and only exports it to the ERP when reconciliation and approval are firm. Manual checking is reduced to exceptions.

Do I need an ERP to automate approvals?

Not strictly required, but the natural target for the data is the accounting system (Holded, Sage, A3, Contasol, Quipu, Anfix). The automation layer sits between the inbox and the ERP. If you are still on Excel, automating approval is the recommended first step before migrating to an ERP.

What amount thresholds make sense for your company?

A common distribution: under 500 EUR, one click by the area lead if three-way matching reconciles; 500 to 5,000 EUR approval by area lead or purchasing supervisor; over 5,000 EUR approval by finance director; over 25,000 EUR dual signature (CFO + CEO or board). Thresholds should be calibrated to volume and spend profile. They are your internal policy: ininvoice does not route invoices by amount and has no automatic tier; even when the invoice matches, a person always approves it.

What happens if the invoice has a variance with the PO?

It is never approved on its own. It is held with an exception tagged by cause (price, quantity, VAT, withholding, potential duplicate) and the reason visible, for a person to approve it, reject it or ask the supplier for clarification; a potential duplicate is blocked. Approval is held until the variance is resolved, with full traceability of who did what and when.

Is approval automation compatible with Verifactu?

Yes. Verifactu is an obligation on the issuer's billing software; from 2027, invoices received from suppliers under the regime carry a QR code. Checking the QR against the AEAT is a voluntary control for the recipient, done separately: ininvoice does not do it. It reads the invoice and runs the control that matters on the receiving side: line-by-line matching, duplicate blocking and tax validation. Verifactu does not replace matching, because it confirms the invoice exists, not that what is billed matches what was ordered and received.

How much do you actually save by automating?

The average cost of processing an invoice manually is between 9 and 16 EUR per document, while best-in-class companies come in below 3 EUR. For a company with 800 invoices a month, the annual difference exceeds 100,000 EUR in process cost, without counting undetected overpayments or late-payment interest.

How is approval traceability retained?

Every action (email read, extraction, matching, approval, rejection, modification) is logged with user and timestamp in the invoice's audit trail. This supports COSO-style internal controls, external audit requirements and the retention obligation: four years for the tax limitation period under art. 66 of the General Tax Law, and six years for commercial records under art. 30 of the Commercial Code.

How much does automating approvals with ininvoice cost?

Tailored pricing: a proposal within 48 hours of seeing your invoices, no implementation fee. Try it with your own invoices.

This guide is reviewed periodically to reflect regulatory changes and industry benchmarks. Last review: 24 October 2026 by ininvoice team. Regulatory references have been verified against BOE and AEAT on that date. Always consult a tax adviser before making operational decisions with tax impact.