.png)
Most accounts payable automation content starts with the invoice. That makes sense: the invoice is where most AP teams feel the pain most acutely.
But the invoice is the end of the purchasing cycle, not the beginning. By the time an invoice arrives, four manual steps have already happened: someone created a purchase requisition, someone approved it, someone generated a purchase order, and someone sent it to a supplier and tracked whether the supplier acknowledged it.
Those four steps are where the real procurement inefficiency lives. And for most mid-market manufacturers, all four are still
manual.
This post covers the full purchase-to-pay cycle and how to automate each stage using n8n and your existing ERP, without adding procurement software to your stack.
The complete P2P cycle for a typical mid-market manufacturer:
Most manufacturers have automated step 7 or are aware it can be automated. Steps 1 through 5 are consistently manual. That is where this post focuses.
Step 1: Requisition creation: In most manufacturers, purchase requisitions are created by email (to the purchasing team), on a paper form, or in a shared spreadsheet. There is no consistent trigger, no structured format, and no automatic routing. Requisitions get lost. Duplicate orders happen. Urgency is communicated verbally rather than through the system.
Step 2: Approval routing: Approval rules exist informally. Purchases under $500 go to the department manager. Purchases over $2,000 go to the COO. But the routing is done manually: the purchasing coordinator knows the rules and emails the right person. If that person is out, the approval sits.
Step 3: PO generation: Once approved, someone manually creates the PO in the ERP. They look up the supplier record, enter the line items, set the expected delivery date, and send it. For manufacturers running 100 to 400 POs per month, this is a material time investment.
Step 4: Supplier acknowledgment: The PO is emailed to the supplier. Whether the supplier received it and accepted it is tracked in a spreadsheet, or not tracked at all. Unacknowledged POs are discovered when the material does not arrive.
Step 5: Receipt and follow-up: If a shipment is late, someone has to follow up with the supplier manually. There is no automatic alert when an expected receipt date passes without an ASN or shipment confirmation.
These five manual steps in sequence create the conditions for late material, duplicate orders, and purchasing decisions made without visibility into what is already on order.
The following workflow runs in n8n alongside the existing ERP. No new procurement platform required.
Replace the email or spreadsheet with a structured form: either a Retool form for internal users or a simple webhook-connected form tool. The form captures: requester, department, item description, estimated amount, preferred supplier (if applicable), and urgency level.
On submission, n8n creates a requisition record and immediately routes it based on approval rules defined in the workflow.
n8n applies the approval matrix:
If no response within a defined window (typically 24 hours for standard, 4 hours for urgent), n8n escalates to the approver's manager with a flag. No requisition sits unreviewed.
Rejected requisitions return to the requester with the rejection reason recorded. Approved requisitions trigger the next step automatically.
n8n calls the ERP API to create the PO directly from the approved requisition data. No manual entry. The PO is created with the correct supplier record, line items, quantities, unit prices (pulled from the ERP's vendor price list if one exists), and expected delivery date.
ERPs with clean REST APIs that support programmatic PO creation: NetSuite, SAP Business One, Epicor Kinetic, JobBOSS2.
The PO confirmation is sent back to the requester and the purchasing team automatically.
n8n sends the PO to the supplier via email (formatted PDF attachment) or via supplier portal API if the supplier supports it.
An acknowledgment clock starts. n8n monitors for one of three signals:
If no acknowledgment is received within the defined window (24 to 48 hours depending on supplier tier), n8n sends an automated follow-up to the supplier contact on file. A second non-response escalates to the purchasing manager.
n8n monitors for an ASN (advance shipment notice) or carrier tracking update for each open PO. When the expected receipt date is within 48 hours and no ASN exists, a proactive alert goes to the receiving team and the purchasing coordinator.
If a shipment is confirmed late, the production planner is notified with the PO details and the revised expected date, so they can adjust the production schedule before the material is needed.
The workflow above handles steps 1 through 5. The AP side (invoice receipt, 3-way match, exception routing, and ERP write-back) is a separate workflow, covered in a previous post.
Non-PO purchases (employee expenses, subscriptions, one-time vendor payments) require a different approval workflow and are out of scope here. They follow similar logic but trigger differently.
1. A structured approval matrix. The workflow cannot route what has not been defined. Before building, document: who approves what amounts, what categories require special routing, and what happens when the primary approver is unavailable.
2. Supplier contacts in the ERP. n8n sends the PO to the supplier contact on file. If your ERP has incomplete or outdated supplier contact records, this is the first data cleanup task.
3. ERP API access. The PO creation step requires your ERP's REST API and a configured integration user. Confirm this before scoping the build.
4. A named internal owner. The purchasing coordinator or procurement manager who will monitor the workflow, tune the approval rules as they evolve, and escalate exceptions that fall outside the automated logic.
Procurement automation spans multiple systems (ERP, email, potentially supplier portals and EDI). If you are evaluating a business process automation services partner to build this, the questions that matter most:
Do they have ERP API integration experience with your specific system? Procurement automation that writes POs to the ERP requires someone who has done it before with your ERP version.
How do they handle the approval matrix configuration? Good partners document the approval rules before writing a single line of workflow logic. Partners who start building before the rules are defined will be back for multiple rounds of revisions.
What is their escalation handling approach? The value of procurement automation is not in the happy path: it is in what happens when an approver does not respond, a supplier does not acknowledge, and a shipment does not arrive. Partners who design exception paths upfront build workflows that actually reduce manual intervention.
The Flow Kaizen guide includes a readiness scoring framework that covers procurement workflows specifically, including what data needs to be clean in the ERP before the build starts and how to sequence the P2P automation against other priorities.
.png)
