A purchase request is approved and signed by the department head, goes to the COO above a spending limit, and the buyer then files the matching expense form.
A purchase order approval workflow template is a ready-made process that takes a purchase request from the employee who raises it, through signed approval by the right people for its value, to a recorded supplier invoice that finance has matched against what was approved.
Sign in with your Edesy account; the setup wizard opens on this template.
Category
Type
Business process
Steps
9
Roles
Department head, COO, Buyer, Finance team
Level
Advanced, about 15 min to set up
Updated
2026-11-19
Use it for office supplies, equipment and small services. The department head approves and signs first. Anything above ₹1,00,000 also needs the COO. Once approved, the requester is told, and the buyer gets a follow-up form to record the supplier, invoice number and amount actually paid, which closes the loop for accounts. Finance receives a flow report with every decision and signature.
Form: Purchase Request
Starts the workflow
Department head: approve & sign purchase
Approve & sign · Department head
Deny: E-mail: Purchase request not approved · Approve: Over ₹1,00,000?
E-mail: Purchase request not approved
Over ₹1,00,000?
If / else
Yes: COO sign-off · No: E-mail: Purchase approved: ₹…
COO sign-off
Approve & sign · COO
Deny: E-mail: Purchase request not approved · Approve: E-mail: Purchase approved: ₹…
E-mail: Purchase request not approved
E-mail: Purchase approved: ₹…
Record the purchase
Follow-up form · Buyer
Match invoice to the PO
Task · Finance team
Mark as done: Flow report
Flow report
Flow report
Purchase Request
Starts the workflow · 10 questions
Employee name · Work e-mail · Employee ID · Department · Items to buy · Estimated total (incl. GST) · Needed by · Is this in your approved budget? · What is it for? · Supplier quotation
Purchase Record
Follow-up form · 5 questions
Supplier · Invoice number · Amount paid (incl. GST) · Order date · Invoice copy
Every field the approvers need is on one page, so nobody has to reply asking what the money is for. The Items to buy table keeps line items structured, and Is this in your approved budget? is shown in the approval description so the department head sees it before signing.
An approval with a drawn signature, completed by any one assignee, with a comment required on Deny. Reassign and Request info are allowed, so a head who is on leave can pass it on and one who needs a quotation can ask for it instead of refusing.
Compares Estimated total (incl. GST) with 100000. Yes goes to the COO, No skips straight to the approval e-mail. Change the value or add a second condition, such as Is this in your approved budget? equal to No, if unbudgeted spends should also go up a level.
A second signed approval for high-value requests, with the same 3-day due time and daily reminders. Its description carries the name of the department head who signed, so the COO knows the request has already been checked.
Two separate 'Purchase request not approved' e-mails, one quoting the department head's comment and one quoting the COO's, so the requester knows who refused and why.
Sent to the requester with the Buyer in copy and a link to track the run, so the person placing the order hears about it at the same moment as the person who asked.
Assigned to the Buyer after the order is placed. Supplier, Invoice number, Amount paid (incl. GST) and Order date are required, and Invoice copy is an optional upload. This is what closes the loop for accounts.
The Finance team checks the amount paid and invoice number against the approved request and marks the task done; only then does the Flow report with every decision and signature go to finance.
The run starts when an employee submits the Purchase Request form: Employee name, Work e-mail, Employee ID, Department, an Items to buy table, Estimated total (incl. GST), Needed by, Is this in your approved budget? (Yes, No or Not sure), What is it for? and an optional Supplier quotation upload. The first step, 'Department head: approve & sign purchase', is an Approve & sign step: the Department head sees who is asking, the total, the date and whether it is budgeted, and either approves with a drawn signature or denies with a required comment. Deny sends the requester the e-mail 'Purchase request not approved' with the reason, and the run ends. On Approve, the If / else step 'Over ₹1,00,000?' checks the estimated total. Above that limit the request goes to 'COO sign-off', a second signed approval whose description notes who signed first; a COO denial sends its own 'Purchase request not approved' e-mail. When the amount is within the limit, or the COO approves, the requester gets 'Purchase approved: ₹…' with a tracking link, copied to the Buyer. The Buyer then fills the 'Record the purchase' follow-up form (Purchase Record: Supplier, Invoice number, Amount paid (incl. GST), Order date and Invoice copy), the Finance team completes the task 'Match invoice to the PO', and a Flow report with every decision and signature goes to the Finance team.
It fits companies that buy office supplies, equipment and small services often enough that e-mail approvals get lost but not so often that they need a full procurement suite: Indian SMEs, agencies, schools, clinics and back offices of manufacturing firms. Because the form asks for the total including GST and the follow-up records the amount actually paid including GST, the numbers your accountant compares are like for like. Owners who want a second signature on bigger spends get one automatically, without the department head having to remember to forward anything.
Click Use this template and sign in with your Edesy account; in the setup wizard, map the Department head, COO, Buyer and Finance team roles to real people and let it create the Purchase Request and Purchase Record forms.
Open the 'Over ₹1,00,000?' If / else step in the visual builder and change 100000 to the spending limit in your delegation of authority.
Edit the Department options on the Purchase Request form to match your organisation, and decide whether Supplier quotation should be required for larger purchases.
Review the due time and reminders on each approval and task (3 days, with a reminder every day up to 3 times) and shorten them if purchases are usually urgent.
Submit a test request above and below the limit to check both paths, then share the form link with your teams.
Track requests with a purchase request: who is asking, what they need, by when and how urgent it is. Ready for approvals: add approvers in Settings → Approvals after you create the form.
12 questionsEdesy SignPurchase Order with AcceptanceA purchase order that the supplier accepts by signing, confirming items, prices, delivery date and terms in one record.
2 signer roles · 26 fieldsEdesy AgentsPurchase Requisition AgentCaptures complete purchase requisition submissions — what, why, by when and priority — and routes them to the right team.
Request · 2 actionsThe Department head always approves and signs first. If the estimated total including GST is over ₹1,00,000, the COO must also approve and sign. You can change the limit in the 'Over ₹1,00,000?' step.
The approver must enter a comment, and the requester receives the e-mail 'Purchase request not approved' with that comment as the reason. The run then ends; the employee can submit a new request.
Yes. Each approval has a due time of 3 days and sends a reminder every day, up to 3 reminders. The Buyer's follow-up form and the Finance team's matching task use the same settings.
After approval, the Buyer fills the Purchase Record form with the supplier, invoice number, amount paid including GST, order date and an optional invoice copy. The Finance team then matches that invoice to the approved request before the Flow report is sent.
Yes. In the visual builder you can add another Approval or Approve & sign step after COO sign-off, or add a second If / else step with a higher limit.
The template does not include a call, but you can add an Edesy Voice Agent app action that places an outbound AI call, now or scheduled, for example to the requester once a large purchase is approved. It needs an Edesy voice agent account.
You sign in to Edesy Flow with your Edesy account and the template wizard opens: map each role to a person, pick the app connections it needs, and Flow creates the forms and the workflow for you to edit.
Yes. The workflow opens in the visual builder, where you can add, remove or reorder steps, change who approves, edit the e-mails and add branches.
Vendor invoices are matched to the PO and goods receipt, routed to the right approver by value (budget owner, finance manager or CFO), filed in Google Drive and scheduled for payment.
11 steps · 4 rolesAccountingManual journal entries go to the financial controller, who can ask the preparer for more support before approving; the GL accountant posts the entry and the close channel in Slack is updated.
6 steps · 2 rolesDiscount Approval ProcessCustomers or sales reps ask for a special price; one reviewer from sales and finance approves and signs it, and the requester hears back by e-mail.
4 steps · 2 rolesFinancial Aid Approval ProcessStudents apply for a scholarship with marks, family income and a short statement; the scholarship committee chair approves and signs the award, and the student is told by e-mail.
4 steps · 1 roleKYC Approval ProcessCustomers submit identity and address proofs; a KYC analyst verifies and signs, the compliance officer signs off on the risk category, and the customer is told the outcome.
7 steps · 2 rolesRisk Assessment ApprovalBefore a new deal, market or vendor goes ahead, a risk analyst scores it, the risk manager and chief risk officer approve the assessment, and the owner puts the agreed mitigations in place.
9 steps · 3 roles