Free Purchase Approval Policy Template (2026): For Teams of 5–50
If you're trying to write a purchase approval policy for your small business and you've found yourself reading 40-page corporate procurement manuals from Fortune 500 companies, stop. Those policies aren't designed for you. They're designed for organizations with full procurement departments, vendor onboarding committees, and three layers of approval.
You're a 12-person agency. Or a 25-person SaaS company. Or a 40-person restaurant group. You need a real policy — but a one-page one your team will actually read.
Below is a free, editable template we've refined across hundreds of small businesses. Copy it. Customize the bracketed parts. Send it to your team. Done.
The one-page purchase approval policy template
[Company Name] — Purchase Approval Policy
Effective date: [Date] Owner of this policy: [Name / Role] Last updated: [Date]
Why this policy exists
So everyone at [Company Name] can buy what they need to do their job — without confusion, delays, or surprises at month-end. This policy makes spending predictable for the company and approvals fast for you.
1. Who can request a purchase
Any employee can submit a purchase request. Contractors and freelancers must route requests through their primary point of contact at [Company Name].
2. Spending thresholds
Amount Required approval Under $[50] Auto-approved (no review needed) $[50] – $[500] Department manager approves $[500] – $[2,000] Department head approves Over $[2,000] Owner / CEO approves Over $[10,000] Owner approval + 24-hour cool-off period before purchase Customize these numbers based on your team. Round numbers are easier to remember.
3. What every request must include
- Title (what you're buying, in plain English)
- Vendor (where you're buying it from)
- Amount (your best estimate; the final amount goes in later)
- Category (Software, Hardware, Travel, Office, Marketing, Services, Other)
- Department (which team's budget this comes out of)
- Justification (one sentence — "why does the company need this?")
- Attachments (quote, screenshot, or invoice if available)
4. Approval timing
Approvers will respond within one business day. If 24 hours pass with no response, the request automatically escalates to the next approver level.
Urgent requests (something that blocks revenue or operations) should be flagged at submission and may go directly to the owner.
5. Making the purchase
Once approved, the designated fulfiller — usually the requester themselves, unless otherwise noted — places the order. Use one of:
- Company card (preferred)
- Vendor invoice billed to [Company Name]
- Personal payment with reimbursement (only if the above two are not options)
6. Receipts are mandatory
Every approved purchase must have a receipt or invoice uploaded within 5 business days of the purchase. The final amount must be entered.
No receipt = no future approvals for that requester until resolved.
7. What happens if you don't follow this policy
Spending without prior approval is treated as a personal expense. Reimbursement is at the company's discretion. Repeated violations may affect your role.
This isn't about catching people — it's about making sure no one ends up out of pocket because they assumed something was approved when it wasn't.
8. Special cases
- Recurring subscriptions — approve once per year, not per renewal
- Travel — follow the separate travel policy [link]
- Vendor onboarding — anything from a new vendor over $1,000 requires owner sign-off
- Personal use — the company does not approve purchases for personal use under any circumstances
9. Reporting
Department heads receive a monthly spending report. The owner receives a quarterly summary. Reports are available on request to any employee about their own spending.
10. Questions or exceptions
Contact [Name / Role] for any questions about this policy or to request an exception.
How to actually roll this out
Writing the policy is the easy part. Getting your team to follow it is where most small businesses fail. Here's the step-by-step rollout that works:
Week 1: Soft launch with one department
Pick the department most likely to embrace it (usually Operations or Finance). Run the new process there for one week. Take notes on what's confusing.
Week 2: Refine and announce
Adjust your thresholds based on what week 1 taught you. Then send a single, short email to the whole team:
Subject: New purchase approval process starts Monday
Hey team —
Starting Monday, all purchases over $[X] need to go through our new approval process. This is a 5-minute thing, not a 5-day thing — you submit a request, the right person gets pinged, you make the purchase, you upload the receipt.
Why we're doing this: we've outgrown the "ping me on Slack" approach, receipts have been getting lost, and at month-end we don't always know where money went. This solves all three.
Full policy attached. Read time: 4 minutes.
Submit your first request here: [link]
Questions go to me directly.
Thanks! [Your name]
Week 3: Hold the line
Someone will try to slip a purchase through over Slack. Politely but firmly redirect them: "Hey, can you submit that through the new system? Otherwise it doesn't get approved." Do this consistently for two weeks and the muscle memory shifts.
Week 4 onward: Trust the process
The team will be using it without thinking. The owner will stop seeing 80% of requests. Receipts will start piling up correctly. Your bookkeeper will stop sending you angry messages.
Spending threshold cheat sheet by team size
Not sure where to set your numbers? Here are starting points based on team size:
| Team size | Auto-approve | Manager approves | Owner approves above |
|---|---|---|---|
| 5–10 people | Under $25 | Up to $500 | $500 |
| 10–20 people | Under $50 | Up to $1,500 | $1,500 |
| 20–35 people | Under $100 | Up to $3,000 | $3,000 |
| 35–50 people | Under $200 | Up to $5,000 | $5,000 |
Adjust based on industry. Restaurants and retail typically have higher transaction volume and benefit from higher auto-approve limits. Software companies often run lower because individual purchases (a single Figma seat, a CI subscription) are small but recurring.
Common questions about purchase approval policies
Q: Should we require approval for recurring subscriptions every month? No. Approve once at signup, then again at annual renewal. Constant re-approval of the same Slack subscription will cause your team to revolt.
Q: What about company credit cards? A purchase approval policy and a corporate card policy work together. The card is how people pay; the policy is whether they're allowed to. Cards make purchases easier; they don't replace approvals.
Q: How do we handle emergencies? Build in a "Urgent" flag that bypasses the queue and pings the owner directly. Use sparingly. Once "urgent" gets used five times in a week, retrain.
Q: Do we need approval for things under $25? Probably not, unless you're in a highly regulated industry. Trust your team for small things; require approval where it matters.
Q: How often should we revisit the policy? Every 6 months. Spending patterns change, the team grows, and what worked at 12 people doesn't work at 25.
The tool that makes this policy actually work
A policy is a piece of paper. A workflow is what your team uses every day. The two have to match.
We built Becision specifically to enforce policies like the one above. You configure the spending thresholds in settings, set who approves what, and the system handles the rest. Mobile + web. Receipts mandatory. Reports built in. Free for small teams. Set up an account in five minutes →
If you'd rather wire up your own system with Google Forms, Notion, or a spreadsheet, that's fine too. The important thing is that you have a policy and your team is following it.
TL;DR — your action items
- Today: Copy the template above. Replace the bracketed parts with your numbers.
- This week: Pick a tool to enforce it (Becision, a Google Form, anything beats Slack).
- Next week: Send the rollout email above.
- In one month: Review your data. Did approval times drop? Are receipts being uploaded? Adjust.
That's it. Most "purchase approval policy" guides are 8,000 words of corporate fluff. You don't need that. You need clear rules, a clear tool, and a clear rollout. You now have all three.