Invoice Processing with Email Webhooks

The Problem

Accounts payable teams receive invoices via email from dozens of suppliers. Each supplier uses a different format — some send PDF attachments, others embed invoice details in the email body, and some use a mix of both. Manual processing means downloading attachments, re-keying data into accounting software, matching invoices to POs, and filing for audit. This workflow is slow (average 15 minutes per invoice), expensive ($15–$40 per invoice in processing costs), and prone to errors that cause duplicate payments or missed early-payment discounts.

How JsonHook Solves Invoice Processing

JsonHook receives invoice emails on a dedicated inbound address and delivers the parsed content — including base64-encoded PDF attachments — to your webhook handler. Your handler extracts invoice numbers, vendor details, line items, and totals using OCR on the PDF or regex on the email body, then writes the structured data to your accounting system. The AP team reviews pre-populated records instead of manually keying data, cutting processing time by 80% and virtually eliminating data entry errors.

Architecture Overview

A production invoice processing pipeline built on JsonHook follows this architecture:

• Inbound address: [email protected] — suppliers send invoices to this address or you forward from your AP mailbox
• JsonHook parsing: Extracts email body, sender, subject, and base64-encoded attachments (PDFs, images) with filename and MIME type
• Webhook handler: Decodes PDF attachments, runs OCR or regex extraction, and outputs structured invoice data (vendor, amount, due date, line items)
• Accounting integration: Creates draft bills in QuickBooks, Xero, NetSuite, or your custom AP system via API
• Approval workflow: Sends structured invoice summary to an approver via Slack or Teams with one-click approve/reject actions

This architecture keeps each layer stateless and independently scalable. The inbound email address, the webhook handler, and the downstream data store can each be deployed, monitored, and scaled separately without affecting the others.

Implementation Guide

Follow these steps to set up invoice processing automation with JsonHook:

1. Create a JsonHook inbound address for invoice processing with your invoice-handling webhook URL
2. Configure forwarding from your AP inbox or ask suppliers to CC the JsonHook address on invoice emails
3. Build a handler that extracts attachments from the JSON payload — decode base64 content and save PDF files for processing
4. Add OCR extraction — use a service like AWS Textract, Google Document AI, or an open-source OCR library to extract invoice number, vendor, amount, due date, and line items from PDF invoices
5. Write to your accounting system — create a draft bill or AP entry with the extracted data via the accounting software's API
6. Implement duplicate detection — check invoice number + vendor combination against existing records to prevent duplicate entries

Once the pipeline is active, every qualifying email delivers structured JSON to your handler within seconds of arrival — no polling, no manual exports, no missed messages.

ROI & Benefits

Automating invoice processing via email webhooks delivers measurable improvements across multiple dimensions:

• 80% faster processing: Invoices are pre-populated in your accounting system — AP staff review and approve instead of manually entering data
• Near-zero data entry errors: Automated extraction eliminates mistyped amounts, wrong vendor codes, and transposed invoice numbers
• Never miss a discount: Real-time processing means invoices are queued for payment immediately — no more losing early-payment discounts because the invoice sat in an inbox for a week
• Complete audit trail: The original email, extracted data, and accounting system entry are all linked and traceable for audit purposes
• Vendor-agnostic: Handles invoices from any supplier regardless of their email format, template, or attachment style

Teams that adopt email-to-webhook automation for invoice processing consistently report faster response times, lower error rates, and significant labour savings within the first month of deployment.