Every accounts team has the same quiet tax: someone opens supplier PDFs, squints at line items, and re-types them into a spreadsheet. It's slow, it's error-prone, and the prices are stale the moment they're entered. AI can read those PDFs. But the gap between a demo that works on one invoice and a system that runs on fourteen suppliers, unattended, every morning, is where most projects die.
Why most invoice AI fails after the demo
A single clean invoice is easy. Real inboxes are not: each supplier has a different layout, some send images instead of text PDFs, threads get re-sent, and the same order arrives twice. If your pipeline doesn't handle dedup, layout drift, and timeouts, it works for a week and then quietly corrupts the data it's supposed to protect.
- Different layout per supplier, a fixed template parser can't keep up.
- Duplicate threads, the same invoice processed twice doubles your numbers.
- Timeouts, long PDFs blow past script execution limits if you don't guard for it.
- Silent failure, the worst outcome is a pipeline that looks fine but skips rows.
The architecture that holds up
We give each supplier its own watcher that searches the inbox, pulls the PDF, and sends it to an AI model that reads any layout and returns structured line items as JSON. Each supplier writes to its own tab; a master sync then consolidates the most-recent unit price per SKU across all of them into one live sheet. Dedup keys off the order number before the API call, threads are labelled as processed, and a daily summary email tells the owner exactly what ran.
What you actually get
Zero manual data entry across every supplier, a price list that's current every morning, and a system documented well enough that any developer can maintain it. That last part matters more than the AI: a clever pipeline nobody can fix is a liability, not an asset.
Related reading
Approval workflows in Google Forms and Sheets, without an add-on
A request comes in, the right person approves it with one click, nobody has to chase, and there is a record. You can build that inside Google Workspace with a Form, a Sheet and Apps Script. Here is the design, and the five things that break once real volume arrives.
Google Form → Apps Script → Approver → Decision → Sheet
AI shopping agents can now buy from your store. Is your data ready?
In September Shopify switched checkout on for AI shopping agents. An agent does not see your homepage; it reads your product data and believes it. Here is what changed, where stores lose the sale, and the four checks to run before your first agent order.
Buyer asks → Agent → Product data → Checkout → Buyer approves → Your fulfilment
What changed in Google Workspace this September, and what it means for your automations
Workspace Studio flows can now run your own Apps Script steps and call webhooks, Sheets doubled its cell limit to 20 million, Apps Script data regions went GA, and Gemini connects to QuickBooks, HubSpot and Salesforce. A working read of 4 announcements.
Studio flows → Sheets → Apps Script → Gemini
Continues · Got a workflow like this?