How to Automate Invoice Approval
Without Upgrading Your ERP

The Bottleneck Nobody Talks About: Data Prep, Not Approval

When someone says "invoice approval is too slow," the instinctive fix is to make the approval step faster. Add a mobile app so managers can approve from their phone. Set up email notifications. Escalate after 48 hours.

But walk through what actually happens when an invoice lands in a mid-market company's AP inbox. A clerk opens the PDF. They look at the vendor name. They find the invoice number. They locate the date, the total, the PO reference. They open the PO — which lives in a different system or a different folder — and manually compare line by line. They check the GL coding from last month's entry for the same vendor. Only then, after 8 to 15 minutes of data assembly, does the approval step even become possible. The actual "click Approve" takes three seconds.

This isn't speculation. The Institute of Finance & Management (IOFM) benchmarks manual invoice processing at approximately 12 minutes of touch time per invoice. The approval decision itself — reviewing a correctly assembled comparison and authorizing payment — accounts for maybe 10% of that. The other 90% is data preparation: opening documents, reading fields, cross-referencing, and entering numbers into a system that has no idea any of this is happening.

This is why so many AP teams stay stuck. They have an ERP. They have email. Maybe they even have a shared spreadsheet tracking approvals. But the most time-consuming step — turning a PDF into a set of fields someone can actually review — remains entirely manual. And that step isn't in the ERP's feature list.

The Two Architecture Choice: Full Platform or Extraction Layer

When companies decide to fix this, they typically face two paths — and the price difference between them isn't incremental. It's an order of magnitude.

The Enterprise Platform Path

The full-suite AP automation platforms — SAP Ariba, Coupa, Tipalti — handle everything from supplier onboarding through invoice capture, matching, approval routing, payment execution, and ERP posting. They're comprehensive. They're also priced for organizations that have dedicated procurement operations teams.

SAP Ariba starts at approximately $2,438 per month, sold in blocks with contracts ranging from 3 to 36 months. Full enterprise deployments typically run $250,000+ per year, with implementation timelines of 12 to 18 months and roughly 20 hours of training per user before teams become productive. Coupa, taken private by Thoma Bravo for $8 billion in 2023, operates at a similar pricing tier aimed at mid-to-large enterprises with complex global supply chains. For a company processing 500 invoices a month with a two-person AP team, these numbers don't add up — the platform cost exceeds the entire AP department's annual salary.

These platforms work. They're the right choice for organizations that need SOX-grade segregation of duties enforcement, formal audit trails with digital signatures, and multi-entity procurement governance. But they're not the only way to automate an approval workflow — and for the majority of companies without those compliance requirements, they're overkill.

The Extraction Layer Path

The alternative is to leave your ERP — QuickBooks, Xero, NetSuite, whatever you're using — exactly where it is, and insert a single new step: an AI extraction layer that turns invoice PDFs into structured data before they enter your existing workflow.

Here's what this path looks like: invoices arrive in whatever format suppliers send them (PDF, scan, photo, email attachment). They pass through an extraction step that reads the document, identifies the fields you care about, and outputs them as a structured table. That table becomes the input to your existing approval process — whether that's a shared spreadsheet, a Google Sheet, or your ERP's native invoice entry screen. The downstream process stays unchanged. What changes is that the AP clerk no longer spends 12 minutes per invoice typing.

This isn't a compromise architecture. For teams that don't need enterprise compliance features, it's the architecture — because it solves the root problem (manual data prep) without imposing a platform migration that costs more than the problem it solves.

The rest of this article walks through how to build the extraction-layer path: three steps, phased over four weeks, with specific thresholds and rules you can adapt to your invoice volume.

Step 1: Extract — Turn Invoice PDFs into Structured Data in 5 Seconds

The extraction step is where most of the time savings live. Instead of a person opening a PDF and reading vendor, date, amount, and PO number off the page, an AI model reads the document and outputs those fields directly into a table.

The mechanism that makes this work without templates is worth understanding, because it's what separates this approach from the OCR tools AP teams have already tried and abandoned. Traditional invoice OCR works by template: you tell the software "the invoice number is at coordinates X,Y on page 1," and it works — until the supplier changes their invoice layout, at which point the template breaks and someone has to rebuild it. At 200 suppliers, template maintenance quietly becomes a full-time job.

AI extraction based on vision language models works differently. Instead of remembering where a field sits on a page, it understands what the field means. You define the columns you want — "Invoice Number," "Vendor Name," "Invoice Date," "Total Amount," "PO Number" — and the model locates each value by understanding what it represents, not where it's positioned. A supplier can redesign their invoice layout every month. The extraction still works, because "Total Amount" is semantically the same thing whether it appears in the top-right corner or the bottom-left summary block.

The practical setup for an approval workflow is straightforward: define columns that map to the fields your approvers need to see. A typical setup for PO-based invoice approval would include Vendor Name, Invoice Number, Invoice Date, Due Date, PO Number, Line Item Description, Quantity, Unit Price, Line Total, Invoice Total, and Tax Amount. For non-PO invoices, drop the PO Number and add Department or Cost Center for coding.

If your invoices contain line-item details that need to feed into your ERP at the line level — common in manufacturing and distribution — you need the extraction to capture line items individually, not just the header fields. The tool you use should produce one row per line item for downstream matching, which we'll cover in the next step.

Once the data is extracted and sitting in a structured table, the real workflow value begins: automated comparison against your purchase orders.

Step 2: Match — Auto-Compare Invoice Data Against Purchase Orders

The step that eats the most AP time after data entry is the three-way inspection: Is what the supplier invoiced the same as what we ordered, and does it match what we received? In a manual workflow, this means the AP clerk opens the PO (stored in the ERP or — more commonly — in a procurement system the AP team doesn't have access to), scrolls to the relevant line, and compares quantity, unit price, and total line by line. If the PO was a blanket order covering multiple deliveries, the comparison requires tracking cumulative quantities across shipments — a reconciliation step that's linear in complexity with the number of partial deliveries.

Building the PO Match in a Spreadsheet

With extracted invoice data in one sheet and PO data (exported from your ERP or procurement system) in another, the match becomes a lookup operation:

1. Export PO data from your ERP as a CSV — include PO Number, Line Item, Quantity Ordered, Unit Price, Line Total, and Remaining Quantity (if your ERP tracks cumulative receipts).
2. In your invoice extraction spreadsheet, add a column called "PO Match Status" with a VLOOKUP or INDEX/MATCH formula that compares Invoice Total to PO Line Total for the matching PO number.
3. Use conditional formatting to flag rows where the match fails — red for quantity discrepancies, yellow for price variances over 5%, green for exact matches.
4. Add a "Variance" column that calculates the dollar difference: =Invoice_Total - PO_Line_Total. This single column becomes the dashboard your approver reviews.

For teams using Google Sheets, the Google Sheets add-on approach eliminates the CSV export step — extraction results land directly in the sheet, and PO data can be pulled in via IMPORTRANGE or a connected ERP integration. The matching formulas work identically whether the data arrives via manual CSV export or live sync.

One underappreciated benefit of this approach: the matching rules are visible and editable. When a procurement manager changes a PO after the fact (price adjustments, quantity revisions), the spreadsheet formula catches the discrepancy immediately. In a black-box ERP workflow, the match simply fails and someone has to investigate why. In a spreadsheet, the formula is the investigation.

For deeper coverage of why matching breaks in manufacturing specifically — blanket POs, unit-of-measure drift, partial shipments — see our breakdown of the structural reasons three-way matching hurts manufacturing AP more than teams admit.

Step 3: Route — Build Approval Tiers Without an ERP Workflow Module

This is where most AP teams worry the spreadsheet-based approach will fall apart. Enterprise platforms sell their routing engine as the core value proposition: define rules, assign approvers, enforce escalation. Can you replicate that with a spreadsheet and email?

For teams that don't need SOX-grade sealed audit trails — which is most private companies and many public companies below the materiality threshold — the answer is yes. Here's how.

Threshold-Based Auto-Approval

The simplest routing rule is also the one that eliminates the most manual work: invoices under a certain dollar amount don't need human review at all. Set a threshold based on your audit materiality and historical error rate. A common starting point:

Conditional Formatting as Your Exception Engine

The spreadsheet becomes the approval dashboard. Conditional formatting rules flag what needs attention:

• Red row = PO match failed (quantity or price discrepancy over 5%) → requires manual investigation before routing
• Yellow row = PO match passed but invoice contains a new vendor not in the approved vendor list → flag for vendor setup review
• Green row = all checks passed, under threshold → auto-approved, no routing needed
• Blue row = approved and awaiting payment → transitions to the payment queue

This color-coded view gives the AP manager a single-screen status dashboard. At a glance, they can see how many invoices are in each stage — something that's surprisingly hard to get from most ERP systems without running a custom report.

On r/Accounting, one AP manager described a workflow where "things are sent out for approval but in many cases are never circled back to until a new invoice lands in the AP inbox." The spreadsheet solves this by making "awaiting approval" a visible state, not an invisible email that may or may not get a reply. A weekly review of the red and yellow rows becomes the AP manager's exception handling routine — 15 minutes instead of 15 follow-up emails.

Four-Week Rollout Plan

The fastest way to kill an automation initiative is to change everything at once. A phased rollout introduces one change per week, lets the team adjust, and builds momentum from early wins.

By the end of Week 4, you have a functioning approval workflow that didn't touch your ERP configuration. The extraction step handles data prep. The spreadsheet handles matching and routing. The email notification triggers the approval action. And your AP team has reclaimed the majority of the 12-minutes-per-invoice they were spending on transcription.

Where This Approach Fits — and Where It Doesn't

Not every company can or should replace an enterprise approval platform with a spreadsheet. Here's the honest boundary.

This approach works well when: your company processes 100–2,000 invoices a month, you already have an ERP or accounting system (QuickBooks, Xero, NetSuite, Sage), your approval routing is straightforward (by amount, by department, by vendor), and you are not subject to SOX Section 404 internal control requirements that mandate digital signatures and system-enforced segregation of duties.

This approach runs into limits when: your company is publicly traded and subject to SOX compliance where external auditors test segregation of duties at the system level, you need legally binding digital signatures on every approval step, you process more than 3,000 invoices a month and need automated three-way matching against real-time ERP data, or your approval routing involves complex multi-entity intercompany logic that a spreadsheet can't model cleanly.

For teams not under SOX but still wanting more structure than a standalone spreadsheet provides, several mid-market AP platforms offer approval routing at a fraction of the Ariba/Coupa price point — Bill.com, Stampli, and Precoro (starting around $600–$1,000/month) bridge the gap between spreadsheet and enterprise platform. These can be layered on top of the extraction step if your approval complexity outgrows the spreadsheet approach.

This article is focused on the workflow layer — how extraction feeds into approval routing. For the complementary question of what an extraction tool actually replaces in the AP process, see why AP teams still enter invoice data manually in 2025. For a detailed comparison of extraction approaches across different invoice formats, structured e-invoices vs. PDF invoices covers the reality that most invoices still arrive as PDFs even in markets with mature e-invoicing mandates — a dynamic explored more deeply in the Europe e-invoicing mandate timeline, with country-specific breakdowns for France and Germany.

FAQ

Can this approach handle both PO and non-PO invoices in the same workflow?

Yes. For PO invoices, the match step compares extracted data against the PO export. For non-PO invoices, skip the PO matching column and route directly to the appropriate budget owner for coding approval. The conditional formatting can be set to flag any invoice without a PO number as a non-PO item, ensuring it routes to the correct review path automatically.

What happens when a supplier sends a corrected invoice after the original was already approved?

This is a process question, not a tool question. The spreadsheet should have a "Status" column with values like Pending Extraction → Matched → Awaiting Approval → Approved → Paid → Voided. When a corrected invoice arrives, mark the original as Voided (with a note linking to the correction), extract the new version, and restart the matching and routing steps. The audit trail is visible in the spreadsheet's version history — it's not a sealed digital signature, but it shows who changed what and when.

Does this work for international invoices with multiple currencies?

The extraction step handles multi-currency invoices — the AI reads the currency from the document and extracts the amount as-is. The matching step requires you to define a currency conversion rule if your PO is in one currency and the invoice is in another. The simplest approach is to add a "Currency" column and a "Converted Amount" column with a lookup to a manually maintained exchange rate table. This isn't automated forex reconciliation, but for teams dealing with a handful of international suppliers, it's practical.

How do you handle approvers who simply don't respond?

The spreadsheet approach makes non-response visible — the invoice sits in "Awaiting Approval" status with a timestamp. Set an escalation rule: if an invoice has been in "Awaiting Approval" for more than 3 business days, the AP manager sends a follow-up and CC's the approver's manager. This is the same escalation logic an ERP workflow would enforce, but it relies on human follow-through rather than automated nudges. For teams where approver non-response is a persistent problem, this is the one area where a dedicated approval platform's automated escalation features provide genuine value over a spreadsheet.

What's the break-even point where the spreadsheet approach stops making sense?

Around 2,500–3,000 invoices per month, the spreadsheet's performance starts degrading — not because formulas break, but because conditional formatting across thousands of rows becomes slow and the AP manager's exception review becomes a bottleneck. At that volume, you should be evaluating a mid-market AP automation platform. But here's the important nuance: the extraction step — the data-prep layer — continues to provide value regardless of what routing system sits downstream. You don't outgrow the extraction layer. You outgrow the spreadsheet routing layer and replace it with a platform, while the extraction step keeps feeding clean data into whatever system comes next.

What about the Collection Link — can suppliers submit invoices directly into this workflow?

Yes. Instead of suppliers emailing PDFs to an AP inbox where they compete with every other email for attention, you can generate a dedicated Collection Link — a URL you share with vendors — where they upload invoices directly. Uploaded files enter your processing queue automatically, and the sender doesn't need an account or login. This eliminates the "invoice lost in someone's inbox" problem that AP teams on r/Accounting consistently cite as a top-three frustration, without requiring suppliers to adopt a portal or change their existing process. For AP teams receiving invoices from dozens of recurring vendors, this single change — centralizing intake — often reduces processing time more than any routing optimization.

The extraction layer isn't competing with your ERP. It's feeding it. And once that feed is clean and automated, the approval workflow that sits on top of it becomes a configuration exercise, not a transformation project.

Test It on Your Own Invoices

The fastest way to evaluate whether an extraction layer changes your AP workflow is to run your actual invoices through it — not a demo invoice, not a clean sample. Pick five invoices from five different suppliers. The ones with the weirdest formats. Define the columns your approvers need to see. If extraction handles those five without template setup, you've validated the core premise: the data-prep bottleneck can be automated without touching your ERP configuration, and the approval workflow you build downstream is limited only by how you structure your spreadsheet — not by what your ERP allows.