Invoice Approval Audit and Exception Queue
Audit structured supplier invoices and route vendor, PO, amount, bank-change and duplicate exceptions to a human approval queue.
Workflow preview
Import into n8n, configure your own services, and test before activation.
- Version
- 0.1.0
- Services
- n8n Webhook
- Credentials
- None required
- n8n version tested
- Version not recorded; see validation notes
Additional dependencies
- Structured invoice, vendor and PO data
- Maintained prior invoice key ledger
What this workflow does
Check structured supplier invoices before they reach an approval or payment system. The workflow compares each invoice with a supplied vendor master, individual and combined purchase order balances, and prior invoice keys, checks amount and calendar-date consistency, and routes exceptions to a human queue.
What you receive
- An inactive 17-node n8n workflow with a fictional five-invoice demo and a POST webhook for real batches.
- Three decisions:
ready_for_approval,reviewandhold, each with reasons and a suggested AP owner. - A JSON response and downloadable JSON report. No payment, email or accounting write is performed.
Setup
- Download and import the workflow JSON. Run Run Fictional Demo to inspect the queue.
- Map your ERP or document extraction output to the batch contract in the included README. Supply invoices, current vendors, purchase orders and prior accepted invoice keys.
- Test POST requests using n8n's test webhook URL. Protect the endpoint with your normal access controls before activation; the included webhook has no authentication configured.
- Review all decisions. Add a key to your own ledger only after the invoice is accepted, and include that ledger in subsequent batches.
Requirements and costs
The template uses built-in n8n nodes and no paid API or credentials. It requires structured invoice data and an external ledger for cross-run duplicate checks. It does not extract PDF data, verify bank ownership, update PO balances or pay suppliers.
Tested behavior
The source and a fresh clean-export SDK recreation passed normal, empty, invalid and in-batch duplicate tests. The fictional normal case produced one ready item, two reviews and two holds. Native editor JSON upload and a production ERP integration were not available for testing. The exact n8n server version was not exposed.