Automate supplier invoice approval: 2026 guide for SMEs

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, an SME 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 SMEs 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, Gmail or Outlook 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: Touchless approval with AP automation

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, routes only the exceptions, writes validated invoices to the ERP. The owner only sees 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 SME with 200-2,000 monthly invoices, 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 SME is 6 to 14 days. The legal B2B payment deadline in Spain is 60 days for private companies and 30 for the public sector; 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 human intervention when everything reconciles.

1. Ingestion from Gmail or Outlook

Read-only OAuth connection to the admin department's inbox. The system reads incoming emails, identifies those containing invoices (PDF attachment or structured XML), 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, OCR is applied; if structured XML (FacturaE, UBL, Factur-X, CII), the structure is read directly. 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 learns from the specific supplier's history.

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. Routing by amount

If every line reconciles, the system evaluates the total amount and applies the approval rules by threshold (next section). Invoices in the "auto-approve" tier go straight to booking. Those requiring human signature are routed to the relevant approver with a notification (email, app, Slack if integrated).

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. Booking in the ERP

The approved invoice is exported to the ERP (Holded, Sage 50/Despacho, A3, Contasol, Quipu, Anfix) with all validated data: supplier account, lines with their accounting code, 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 in SMEs:

Amount tier	Approver	Target SLA	Additional condition
< 500 EUR	Auto-approval	Immediate	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 by the system, not by each operator's interpretation.

Universal exception to auto-approval: the first invoice from a new supplier. Even if the amount is below the minimum threshold, it must go through at least one human validation to set the accounting code, supplier data and payment terms. After the third invoice from the same supplier with no incidents, it enters the automatic flow.

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, from what IP, 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, timestamp, IP, device, comment.
• Rejections and reasons.
• Export to ERP: timestamp, target system, result.
• Final payment and bank reconciliation.

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 (4 years generally in Spain, extendable).

Compliance: Verifactu invoices in the approval flow

From 1 January 2027 for companies under Corporate Income Tax and 1 July 2027 for freelancers, invoices issued by suppliers using Verifactu-compliant software will carry a QR code and a chained hash. The receiver sees them like any other invoice, but can now verify against the AEAT that the invoice exists in the issuer's record.

In an automated approval flow, Verifactu verification is added as an extra step between ingestion and matching:

1. Invoice ingestion.
2. Verifactu QR detection (if present).
3. Verification against the AEAT of the hash and basic data (issuer tax ID, receiver tax ID, date, total).
4. If verified: continue to matching and approval with a "Verifactu OK" flag in the audit trail.
5. If not verified: the invoice goes into the exception queue for manual review before any approval.

Verifactu verification reduces fraud (made-up or duplicate invoices the supplier did not actually issue). It does not replace three-way matching, because Verifactu 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, technical regulation pending as of May 2026) will shift the invoice input format from PDF to structured XML. The automated workflow must accept both formats in parallel during the entire transition. Receiver-side coverage is in e-invoice reception 2026.

ROI: how much is saved by automating approvals

The reference benchmark for the cost of processing a received invoice is the annual Ardent Partners report. The 2024 edition puts the average cost between 9 and 16 EUR per invoice in companies with no meaningful automation, and below 3 EUR in best-in-class SMEs and mid-market companies. These amounts include staff time, infrastructure, errors and rework.

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

• SME 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.
• SME 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.
• SME 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 an SME 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.

The software cost (ininvoice plan: 249 EUR/month up to 300 invoices/month) pays for itself within weeks in all three scenarios. For SME A, the annual software cost (2,988 EUR) is 9% of the gross saving; for B and C, a smaller fraction.

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, none implies lock-in, none affects ERP historical data.

Phase 1: Connection and calibration (day 1)

Plan signup. Read-only OAuth connection to the admin department's Gmail or Outlook. Initial load of the active supplier catalog and recent PO history (CSV exported from the ERP). Configuration of approval thresholds by amount and 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 calibrated by tuning suppliers, descriptions and rules. By the end of the week, alignment with the manual flow should exceed 95%.

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 focuses on the exceptions the system routes, not on bulk processing. The first two weeks after the cutover are monitored more closely to catch edge cases (uncommon suppliers, seasonal invoices).

Detail of features, pricing and operating policies is on the plan. 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, routes to the right approver based on amount and only writes to the ERP when reconciliation and approval are firm. Human intervention 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 an SME?

A common distribution: under 500 EUR auto-approval 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.

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

The system does not auto-approve. It generates an exception tagged by cause (price, quantity, VAT, withholding, potential duplicate) and routes it to the right owner: price to purchasing, quantity to warehouse, duplicate to payment block. Approval is held until the variance is resolved, with full traceability of who did what and when.

Is approval automation compatible with Verifactu?

Yes. From 2027, invoices received from suppliers under the Verifactu regime carry a QR code and a chained hash. The approval system can verify the QR against the AEAT as an additional step before matching and approving. Verifactu strengthens receiver-side traceability but does not replace matching.

How much do you actually save by automating?

Ardent Partners puts the average cost of processing an invoice manually between 9 and 16 EUR per document, while best-in-class SMEs come in below 3 EUR. For an SME 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, timestamp, IP and result in an immutable audit trail. This satisfies COSO-style internal controls, external audit requirements and the tax retention obligation for the limitation period (4 years in general).

How much does automating approvals with ininvoice cost?

The plan is 249 EUR/month up to 300 invoices per month, no implementation fee, no commitment. Plug and play. Operational detail and comparison on pricing.

This guide is reviewed periodically to reflect regulatory changes and industry benchmarks. Last review: 13 May 2026 by ininvoice team. Per-invoice cost data is from Ardent Partners: State of ePayables 2024. Regulatory references have been verified against BOE and AEAT on that date. Always consult a tax adviser before making operational decisions with tax impact.