Free Word download β’ Edit online β’ Save & share with Drive β’ Export to PDF
A Purchasing Process is a documented operational framework that defines every step an organization follows to acquire goods and services β from identifying a need and selecting a vendor, to issuing a purchase order, confirming delivery, and processing payment. Rather than leaving buying decisions to individual judgment, a purchasing process establishes consistent approval thresholds, vendor selection criteria, and record-keeping requirements that apply across all departments. The result is a repeatable, auditable workflow that controls costs, reduces fraud exposure, and ensures every dollar spent can be traced back to an authorized decision.
Without a documented purchasing process, spending decisions default to whoever has a company card and a vendor relationship β which means duplicate suppliers, missed volume discounts, invoices paid without proof of delivery, and approval chains that exist only in people's heads. The consequences are concrete: over-payments that go undetected until an audit, vendor fraud enabled by absent receipt controls, and budget overruns that surface at month-end with no paper trail to explain them. Banks and investors routinely request evidence of purchasing controls during due diligence, and ISO and SOC 2 audits treat their absence as a significant finding. This template gives you a structured, customizable starting point that takes hours β not weeks β to deploy, and grows with your business as spend complexity increases.
| If your situation is⦠| Use this template |
|---|---|
| Defining the full end-to-end procurement policy for a growing business | Purchasing Policy |
| Issuing a formal buying document to a specific vendor | Purchase Order |
| Soliciting competitive bids from multiple vendors | Request for Proposal (RFP) |
| Evaluating and scoring vendor candidates before selection | Vendor Evaluation Form |
| Tracking all active purchase orders and their status | Purchase Order Log |
| Establishing terms for an ongoing supplier relationship | Vendor Agreement |
| Requesting internal approval before spending above a threshold | Purchase Requisition Form |
Why it matters: Applying a five-step approval chain to a $30 office supply order slows operations and trains employees to route small purchases around the process entirely.
Fix: Create tiered workflows β a single approval for under-threshold purchases and a multi-step process with competitive quotes above the threshold.
Why it matters: Paying a vendor without a W-9, proof of insurance, or verified banking details creates tax filing gaps, potential fraud exposure, and legal liability.
Fix: Make vendor onboarding documentation a hard prerequisite before any PO is issued, and store onboarding records centrally with the vendor's first invoice.
Why it matters: Over-payments and duplicate invoices disproportionately occur on small, routine invoices precisely because teams assume the risk is too low to check.
Fix: Apply the three-way match to all invoices, but automate the match for recurring low-value invoices so it does not create manual bottlenecks.
Why it matters: When the sole approver is traveling or on leave, purchases stall β and employees resort to personal credit cards or verbal approvals that leave no audit trail.
Fix: Designate a backup approver for every approval role and document the delegation authority formally in the process document.
Why it matters: Thresholds, systems, and team structures change β a process document that is 3 years out of date is worse than none because it creates false confidence in controls that no longer exist.
Fix: Schedule an annual review date in the document header and assign a named owner responsible for triggering the update cycle.
Why it matters: Email threads cannot be searched systematically during an audit, and they are permanently lost when an employee leaves the company.
Fix: Require all approvals to be recorded in a central system β even a shared spreadsheet β so the full approval chain is reconstructable independently of any individual's inbox.
Start by listing the spend categories and transaction sizes the process will govern. Set specific dollar thresholds β e.g., $500 for a single-approver review and $5,000 for a competitive-bid requirement.
π‘ Calibrate thresholds to your business size: a 10-person company and a 200-person company have very different transaction volumes.
List every role involved in purchasing and assign a specific dollar approval limit to each. Document who covers each role during vacations or absences.
π‘ A simple RACI table (Responsible, Accountable, Consulted, Informed) makes the role section scannable and unambiguous for new employees.
Sketch the step-by-step approval path from initial request to PO issuance for three scenarios: under threshold, over threshold, and emergency purchase. Add service-level timelines to each step.
π‘ Keep the under-threshold path to two steps maximum β requestor submits, manager approves β or employees will bypass the process with personal credit cards.
Define the minimum number of quotes required at each spend tier, the information vendors must provide during onboarding, and the criteria for approving a sole-source purchase when competition is not feasible.
π‘ Document your preferred-vendor list by category so requestors default to pre-vetted suppliers instead of searching the internet for the cheapest option.
Choose a PO numbering format (e.g., PO-2026-0001) and list every required field on the PO form. Confirm the format matches what your accounting system can import or accept.
π‘ If you use accounting software, align your PO fields to the system's import template now β retrofitting is significantly more disruptive later.
Write out exactly who performs the three-way match, the maximum tolerable variance before escalation (e.g., Β±$25 or Β±2%), and who has final authority to approve payment.
π‘ Set a variance tolerance in dollar terms, not just percentage β 2% on a $50 invoice is trivial; 2% on a $100,000 PO is $2,000.
Specify the retention period (7 years is standard for financial documents in most jurisdictions), the folder structure, and who is responsible for archiving each document type.
π‘ Name the folder structure explicitly in the policy β e.g., 'Procurement / [Year] / POs' β so there is only one place documents can be stored.
Add the four core metrics (PO cycle time, purchase-to-pay cycle time, maverick spend rate, vendor on-time delivery) with targets and assign ownership of each to a named role.
π‘ Schedule the first quarterly review before you publish the policy β it signals to the team that the document is a living tool, not a shelf artifact.
A purchasing process is a documented, step-by-step workflow that defines how an organization identifies a need, selects a vendor, authorizes a purchase, receives goods or services, and processes payment. It establishes who can approve what spending, at what thresholds, and under what conditions β replacing informal buying decisions with repeatable, auditable controls.
Without a formal process, small businesses routinely overpay vendors, accumulate duplicate suppliers for the same category, miss early-payment discounts, and lose invoices before month-end close. A documented process becomes essential once more than two people have spending authority β and is typically required by banks, investors, and ISO auditors as evidence of internal financial controls.
A purchase requisition is an internal document an employee submits to request approval to buy something β it stays inside the company. A purchase order is the external document the company sends to a vendor once the requisition is approved β it creates a formal buying commitment and becomes a legally referenced document in the vendor relationship. The requisition triggers the approval; the PO triggers the transaction.
Three-way matching compares three documents before a vendor invoice is approved for payment: the original purchase order, the goods receipt note confirming delivery, and the vendor's invoice. All three must agree on item, quantity, and price within an acceptable tolerance before payment is released. The process catches over-billing, short-shipments, and duplicate invoice submissions before money leaves the business.
Common structures for small to mid-size businesses: purchases under $500 require a manager's email approval; $500β$5,000 require a formal purchase requisition and budget owner sign-off; above $5,000 require at least three competitive quotes and CFO approval. The right thresholds depend on your total annual spend, team size, and risk tolerance β the key is that every tier has a clear owner and a documented approval step.
Auditors β internal, external, and regulatory β test whether spending decisions were authorized, documented, and consistent. A purchasing process creates the paper trail: approved requisitions, POs with signatures, matched GRNs and invoices, and archived approvals. Without it, auditors default to assuming controls are absent, which typically results in expanded testing, qualified findings, or failed compliance certifications.
Maverick spending occurs when employees buy goods or services outside the approved process β using a personal credit card, calling an unapproved vendor, or skipping the requisition step because the approval takes too long. The primary cause is an approval workflow that is slower or more cumbersome than the bypass. Reducing it requires tiered thresholds that make small purchases fast, a preferred-vendor list that removes the need to search for suppliers, and visible tracking of maverick spend as a KPI.
At minimum, review the process annually and after any of the following: a significant change in team size or organizational structure, a switch in accounting or procurement software, an audit finding related to purchasing controls, or a vendor fraud incident. The process document should include a version number, effective date, and the name of the owner responsible for triggering reviews.
Yes. The core workflow β request, approval, vendor selection, PO issuance, receipt confirmation, and payment β applies to services as well as physical goods. For services, the goods receipt note becomes a service confirmation or delivery acceptance form, and the three-way match compares the PO, the accepted deliverable, and the invoice. Adjust the terminology in the template's scope and workflow sections to reflect your business model.
A purchase order is a single transaction document sent to one vendor for one order. A purchasing process document defines the end-to-end workflow that governs how and when POs are created, approved, and tracked across the entire organization. The process document is the policy; the PO is one output of that policy.
A vendor agreement establishes the legal terms of an ongoing supplier relationship β pricing, liability, warranties, and termination conditions. A purchasing process document defines the internal operational steps your team follows when engaging any vendor. Both are needed: the vendor agreement governs the relationship; the purchasing process governs how your team manages it.
An RFP is used at one specific stage of the purchasing process β competitive vendor selection for a significant purchase. The purchasing process document defines the broader framework, including when an RFP is required, who evaluates responses, and how the winning vendor is onboarded. The RFP fits inside the purchasing process as a required step at certain spend thresholds.
An expense report documents spending an employee has already made out of pocket and is seeking reimbursement for. A purchasing process governs spending before it happens β through pre-authorization, vendor selection, and PO issuance. The two controls are complementary: the purchasing process prevents unauthorized buying; the expense report process manages the exceptions.
Raw material purchasing requires lead-time tracking, safety-stock triggers, and supplier quality certifications integrated into the vendor onboarding step.
Subcontractor and software tool procurement dominates spend; the process must handle statement-of-work attachments to POs and milestone-based payment schedules.
High-volume, low-value purchase orders require automated three-way matching and vendor scorecards tracking on-time delivery and fill rates.
Medical supply purchasing must layer regulatory compliance checks β FDA registration, sterility certifications β onto the standard vendor onboarding and approval workflow.
Job-cost coding is critical: every PO must be tied to a specific project and cost code so material costs roll up accurately into project margin reporting.
Software and SaaS subscription procurement requires annual renewal tracking, seat-count reconciliation, and security review steps embedded in the vendor selection process.
| Path | Best for | Cost | Time |
|---|---|---|---|
| Use the template | Small and mid-size businesses building their first documented purchasing workflow | Free | 2β4 hours to customize and deploy |
| Template + professional review | Businesses preparing for ISO certification, investor due diligence, or an external audit | $300β$800 for a CFO or operations consultant review | 1β3 days |
| Custom drafted | Enterprises with complex multi-entity structures, regulated industries, or ERP-integrated procurement workflows | $2,000β$8,000 for a procurement consultant engagement | 2β6 weeks |
This document is one of 3,000+ business & legal templates included in Business in a Box.
Access over 3,000+ business and legal templates for any business task, project or initiative.
Customize your ready-made business document template and save it in the cloud.
Share your files and folders with your team. Create a space of seamless collaboration.
"Fantastic value! I'm not sure how I'd do without it. It's worth its weight in gold and paid back for itself many times."
"I have been using Business in a Box for years. It has been the most useful source of templates I have encountered. I recommend it to anyone."
"It has been a life saver so many times I have lost count. Business in a Box has saved me so much time and as you know, time is money."
Stop downloading documents. Start operating with clarity. Business in a Box gives you the Business Operating System used by over 250,000 companies worldwide to structure, run, and grow their business.
Start freeΒ Β·Β No credit card required
