To automate purchase orders without code, you need to map your current approval hierarchy, build a digital requisition form, configure spend-based routing rules, connect to your accounting system, and test before going live — using a no-code platform like Kissflow that your finance or procurement team can own and maintain independently. This step-by-step tutorial walks through the complete process, from initial planning to go-live.
The goal is not just to digitize your existing PO process — it is to improve it. Many manual PO processes contain unnecessary steps, redundant approvals, or missing controls. This tutorial will help you identify and fix those issues as you build.
The single most important pre-work step in PO automation is process mapping. Spend one to two hours with your procurement lead, your finance manager, and a representative of the teams that originate most purchase requests. Walk through a recent PO from submission to payment and document every step.
Ask these questions during the mapping session: Who can initiate a PO? Is there a pre-approval required before formal requisition? Who approves POs at each spend level? What are the exact thresholds? What happens when the primary approver is unavailable? How does the PO get communicated to the vendor? How does the goods receipt connect back to the PO? How does the invoice get matched?
The answers reveal the true process — not the intended process, but what actually happens. You will likely find approval bypasses, informal workarounds, and missing steps. Address these during the workflow design, not after.
Your approval hierarchy is the decision map for the entire PO workflow. Most organizations have a tiered approval structure based on spend amount, with additional routing conditions for certain vendor types or expense categories.
A common structure looks like this: Requests under $1,000 require manager approval only. Requests from $1,000 to $10,000 require manager plus department director approval. Requests above $10,000 require manager, director, and CFO approval. Capital expenditures above any amount require an additional facilities or IT review depending on category.
Document your hierarchy in a table before building anything. Include the threshold ranges, the approval roles at each tier, the maximum response time (SLA) for each stage, and the escalation path if the approver is unavailable. This document becomes your workflow configuration spec.
The requisition form is the structured data entry point that replaces the unstructured email request. In Kissflow, you build this form on a drag-and-drop canvas. Here are the fields every purchase requisition form should include:
Set all cost and justification fields as required. A form that allows submission without a clear business justification will generate low-quality requests that slow down approvers and degrade the process.
With the form built and the approval hierarchy documented, you are ready to configure the routing logic. In Kissflow, routing rules are set as conditions on the connections between workflow stages.
Start with the base routing: every PO request routes to the submitter's direct manager. This is a dynamic assignment pulled from the user's profile — no static routing lists that become outdated when people change roles.
Add conditional routing for spend tiers. Click the connection between 'Manager Approval' and 'Finance Review,' select 'Add Condition,' and set: 'If Total Cost is greater than or equal to 1000, route to Director Approval. Otherwise, skip to Finance Review.' Add the CFO routing condition for the $10,000 threshold in the same way.
Add category-based conditions for capital expenditures, IT purchases, or other categories requiring specialist review. These conditions can stack — an IT purchase over $5,000 might route to both IT and the director simultaneously (parallel approval).
Once a PO is approved, the vendor needs to receive a formal purchase order document. Manual processes handle this by having someone export the approved request, format it into a PO document, and email it to the vendor contact. Automated workflows handle this in seconds.
In Kissflow, configure an automated email triggered when the final approval stage is completed. The email body includes the PO details — PO number (auto-generated), line items, quantities, delivery address, and payment terms — formatted as a professional PO document.
You can also configure Kissflow to generate a PDF PO document automatically using its document generation feature, attach it to the notification email, and send a copy to the internal finance team and the requestor simultaneously. The vendor receives their PO; finance has their record; the requestor sees confirmation — all without a single manual action.
A PO workflow that does not connect to your financial system requires someone to manually enter approved POs into the ERP — which reintroduces data entry errors and delays. The integration step is not optional if you want a truly automated process.
Kissflow offers native integrations with QuickBooks Online, Xero, NetSuite, and SAP. For other ERP systems, Kissflow's webhook and REST API capabilities allow custom integration. The configuration typically takes less than an hour for standard systems with IT assistance for credentials and field mapping.
Once integrated, approved POs create purchase order records in the ERP automatically, pre-populated with all the data from the Kissflow form. The only human involvement is the approval decision — not the data transfer.
Before going live, run the workflow through a complete test cycle using a real purchase scenario. Use your own account to submit a test request, then approve it at each stage yourself to verify the routing logic, check that notification emails arrive correctly, confirm that the PO document is generated as expected, and verify that the ERP integration creates the record correctly.
Test these specific scenarios: a standard request under the first threshold, a request at the first threshold (boundary testing is important), a request requiring CFO approval, a request in a category that triggers specialist routing, and a request where you deliberately miss an approval SLA to verify that escalation fires correctly.
Document any issues found during testing and fix them before launching to users. A workflow with routing bugs discovered after go-live requires re-processing requests and erodes user confidence more than a delayed launch.
Training for a well-designed no-code PO workflow should take no longer than 20 minutes per user group. The requestor experience — filling out the form and receiving confirmation — is intuitive. The approver experience — receiving a notification, reviewing the request, and clicking approve or reject — requires minimal instruction.
Run a 30-minute training session for requestors showing the form, what happens after submission, and how to check the status of a pending request. Run a separate 20-minute session for approvers showing the approval interface, how to access supporting documentation, and how to add rejection comments.
For the first two weeks after go-live, have someone from the workflow team available to answer questions. Most questions are about where to find something, not how to use the system — the interface is designed to be intuitive.
Building too much on day one. The three-way match, OCR integration, and ERP connection are all valuable — but launching a workflow with just the approval routing delivers immediate value and can be expanded incrementally. Perfect is the enemy of live.
Static approver assignments. Hard-coding specific names as approvers creates maintenance problems when people change roles or leave. Always use role-based or manager-hierarchy routing that updates automatically.
No rejection workflow. Rejected PO requests need to be returned to the requestor with a clear explanation, and the requestor needs a path to revise and resubmit. Build this explicitly — a workflow that ends at 'rejected' creates confusion.
Skipping the change management piece. The most common reason PO automation fails is not technical — it is adoption. If employees find a faster workaround (emailing their manager directly), they will use it. Make the automated process faster and easier than the workaround, not harder.
Kissflow's no-code automation platform gives your procurement and finance team full ownership of the purchase order workflow — from requisition form to ERP integration — without waiting for IT. The platform includes a pre-built PO workflow template with form, routing logic, vendor notification, and accounting integration pre-configured and ready to customize.