Set spending rules by defining what staff may buy, the full cost they can commit, which budget pays and who must approve before ordering. Add a simple request record, a named deputy and an urgent-purchase route. Reserve approved commitments so that several individually acceptable purchases cannot overspend the same budget.
Spend management starts before a card is used or an invoice arrives. A card limit controls one payment method; a purchase policy controls the business commitment. A $45 monthly subscription with a 12-month minimum can create a $540 commitment even though the first card charge is small.
Write the permission in terms of the whole purchase
Start with a sentence staff can apply: “Get approval for the full purchase commitment, including required delivery, setup and minimum contract charges, before placing the order.” Specify how to handle any applicable charges using the actual supplier quote, and ask your bookkeeper to confirm consistent treatment. Do not leave “total cost” open to individual interpretation.
Apply limits to the related purchase, not each line, invoice or card transaction. Otherwise a requester can divide one order into several small payments without receiving the intended review. Define related purchases by their purpose and project, using judgement rather than automatically grouping every order from the same supplier forever.
An illustrative butcher needs 15 storage tubs at $18 each, with $20 delivery. The approval value is $290: $270 for tubs plus delivery. A request for “tubs, $18” is incomplete. The form should ask for quantity, unit price, delivery and total, so the approver can see the actual commitment without reconstructing it.
An illustrative furniture maker orders $310 of drawer hardware and $310 of handles for the same commission on the same day. Under the example policy below, the $620 combined purchase needs the higher approval route. Two $310 requests should be linked, not treated as independent purchases merely because different staff entered them.
For subscriptions, capture the minimum term, renewal date and notice deadline alongside the monthly charge. Where a service can genuinely be cancelled each month without another commitment, use the commitment your contract creates and set a separate ongoing budget cap. Do not assume every monthly price means a monthly contract.
Use a small matrix with clear boundaries
The following limits are illustrative, not recommended amounts for every business. Choose values by reviewing recent purchases and your cash capacity. Aim to delegate routine decisions while keeping unusual commitments visible. A team buying expensive materials will need different limits from one buying mainly low-cost supplies.
| Total commitment | Example approval route | Conditions |
|---|---|---|
| Up to $100 | Delegated purchasing permission | Approved category and supplier; budget available; record required |
| More than $100, up to $500 | Budget manager before ordering | Business purpose, full quote and budget check |
| More than $500, up to $2,000 | Budget manager and owner | Both decisions recorded before commitment |
| More than $2,000 | Owner plus nominated independent reviewer | Cash timing, alternatives and contract reviewed |
| Any value with an exception | Relevant specialist or owner review | New data access, unusual terms or other defined concern |
Say explicitly which band includes an amount exactly on the boundary. In this matrix, $500 requires the budget manager; $500.01 also requires the owner. If the system accepts whole numbers only, document how amounts are rounded for routing without understating the actual commitment.
Delegated purchasing permission is a standing approval for tightly defined routine spending. It still requires a record and an available budget. It should not let staff approve their own exceptional requests. Decide who reviews purchases made by each manager or owner, especially where they hold broad system permissions.
Make policy precedence explicit. A low-value purchase involving access to customer records still needs the defined data review. A purchase inside the amount limit but outside the budget is held for a budget decision. The most restrictive applicable requirement should remain visible rather than disappearing when the amount test passes.
For supplier choice, require a proportionate comparison when it would improve the decision. Three quotes for a $30 replacement cable can cost more in staff time than the item. For a $3,000 equipment purchase, comparing specification, delivery and support may be worthwhile. Use a structured supplier-quote comparison when the options need careful checking.
Distinguish money spent from money already promised
A budget can appear healthy while open orders have already consumed it. Track actual spending and approved commitments separately. Available budget equals the budget limit minus actual spending minus outstanding commitments, after any authorised adjustments. Do not count a paid or invoiced commitment twice as both spent and still reserved.
Reserve the budget when the purchase is approved, not when the supplier finally sends a bill. Release the reservation when the request expires or is cancelled. When the invoice arrives, replace the relevant reservation with the actual amount and investigate any difference under your amendment rules.
The update must be handled as one controlled transaction in your process. In a manual pilot, one coordinator checks and records reservations. In software, ask the supplier to demonstrate two requests arriving together. Both should not see the same unreserved balance and each assume it is theirs to use.
For an illustrative homeware brand, only $1,300 remains in a packaging budget. An $800 request and a $700 request arrive almost simultaneously. Once the first is approved and reserved, only $500 remains. The second needs a budget change or a reduced order. Checking the balance only when the form was opened would miss the conflict.
Keep recurring commitments visible across the relevant periods. A yearly contract may need approval for its full term while the monthly budget report spreads planned charges across months. Both views are useful, but neither should erase the full obligation. Connect the figures to budget-versus-actual reporting using agreed definitions.
Follow a catering equipment request through the budget
This illustration uses a catering company's $6,000 monthly equipment and event-supplies budget. It has spent $2,200 and has $1,600 of approved orders still outstanding. Available budget is therefore $2,200. A team member requests insulated carriers quoted at $870 plus $30 delivery, giving a $900 total commitment.
The request names the event programme, explains why existing carriers are insufficient and attaches the supplier quote. Because $900 sits in the example's third band, the budget manager checks the need and the owner checks the commitment. The requester does not place the order while either decision remains pending.
After both approvals, the coordinator reserves $900 against request BUY-046. The budget now shows $2,200 spent, $2,500 committed and $1,300 available. The approved request includes the supplier, specification, delivery requirement, maximum total and approval expiry date. The buyer receives permission for those details, not an unrestricted $900 allowance.
The final accepted invoice is $880 because delivery was reduced to $10. The bookkeeper records $880 actual spending and removes the $900 reservation. Total spending becomes $3,080, commitments return to $1,600 and available budget becomes $1,320. The $20 difference has been released once, with the original request still traceable.
If the supplier instead proposes a $980 substitute, pause before accepting it. The budget may have room, but the price and specification differ from the approved request. Send the revised commitment through the policy's amendment route. Do not let an assistant decide that an $80 increase is “close enough” unless the policy explicitly authorises such a tolerance.
The owner reviews the request after delivery: were the carriers received, did they meet the requirement and was the reservation closed correctly? This final step stops unused commitments accumulating and makes the next budget check reliable. Invoice payment itself belongs in the accounts payable process, with its own evidence and release controls.
Give repeat purchases a bounded standing approval
Regular low-risk purchases can operate under a standing approval that names the supplier, category, maximum order size, total period cap and expiry date. Require a fresh decision when any boundary changes. This reduces repetitive approval messages without handing out permission for unrelated purchases.
An illustrative delicatessen buys cleaning supplies weekly. Its standing approval covers up to $40 per order and $160 per calendar month from a named supplier, reviewed after three months. Five $35 orders would total $175, so the fifth order needs review even though each individual order is below $40.
A catering team with a standing ingredients order may need a volume range as well as a spending cap. A supplier's price increase can make the same quantity exceed the cap. The right response is an updated budget decision or changed order, not silently reducing a recipe quantity to keep a payment within the old limit.
Keep card budgets and purchasing permission aligned, while recognising that they are different controls. An employee with an approved $900 equipment request should not necessarily receive a permanent $900 increase in general purchasing authority. Set a limited funding arrangement where your tools support it and close unused permission after the purchase.
Spendesk's documentation illustrates the distinction. An approval policy sets two thresholds, the most a requester can spend in one transaction and in one month without approval, and those sit separately from the card's monthly budget. Only users with the Requester role have one: its help centre says Account Owners and Admins are not subject to an approval policy, so their requests are approved automatically. Test actual roles in your account; a written policy still needs an independent after-the-fact review for privileged users.
Create an urgent route that staff can actually use
Define an emergency by its business impact, such as preventing immediate loss of stock or restoring essential service, rather than by the requester writing “urgent”. Name the decision-maker, deputy, amount boundary, acceptable evidence and deadline for recording the purchase. Tell staff how to reach the deputy outside normal working hours if that is relevant.
An illustrative food truck's essential water pump fails before service. Its emergency policy allows the duty manager to approve up to $200 for a necessary replacement after confirming the fault and supplier. A $190 pump fits that route. The manager records the reason, receipt and request reference that day, then includes it in the next review.
A $460 optional display upgrade does not become an emergency because a supplier's promotion ends tonight. It follows the normal route. Use this contrast when explaining the policy to staff: urgency comes from the operational need, and the evidence should make that need understandable to someone who was absent.
Do not promise reimbursement for every purchase described as urgent, or declare that every policy breach can automatically be deducted from pay. Those questions can involve employment and contractual obligations. Record the facts and ask a qualified adviser where needed. Your internal policy should make permission clear before staff use personal money.
If the owner is unavailable, the deputy should have defined authority rather than an instruction to “use judgement” without limits. A genuinely unusual commitment can wait for a named escalation decision unless the documented emergency conditions apply. Silence from an approver is not an approval.
Make the request form short enough to be used
Collect the fields that change a decision: purpose, requester, budget, supplier, items, total commitment, recurring term, required date and supporting quote. Use a unique request reference. Ask additional questions only when relevant, such as whether a tool will access business records or whether a contract renews automatically.
Illustrative purchase request
Reference: BUY-061
Purpose: replace damaged packing bench scale
Budget: warehouse equipment
Supplier: approved supplier S-08
Equipment: one scale matching attached specification
Item cost: $260
Delivery: $20
Total commitment: $280
Recurring charges: none
Required by: 18 November
Budget available before request: $760
Requested by: warehouse coordinator
Approval required: budget manager
Approval expires: 15 NovemberUnder the example matrix, this request needs the budget manager's decision and would leave $480 available after reservation. It contains enough detail for approval without a long email thread. If the requester omitted delivery, return it for the missing figure rather than allowing AI to fill in a plausible shipping charge.
An assistant can review completeness before the approver reads the form. Ask: “List missing fields and contradictions; do not approve the purchase or infer prices.” For an illustrative $45 monthly software request with no term supplied, a useful output is: “Minimum commitment unknown; obtain contract term and renewal conditions.” The fix is to get the terms, not multiply by an arbitrary number of months.
Keep the approval tied to the submitted version. Changing the supplier, amount, term or purpose should trigger the specified reapproval rule. The tutorial on connecting human approval to the actual action helps when requests move between forms, messages and purchasing systems.
Test the policy at the boundary before enforcing it
Walk through recent purchases with the team and ask which route each would take. Include amounts exactly on a threshold, split orders, missing quotes, insufficient budget, a subscription renewal and the owner's own purchase. If two people interpret a case differently, repair the wording before configuring automation.
Use a two-week pilot in one budget. Record the decision time, requests returned for missing information, commitments made before approval and corrections to reserved amounts. A policy that creates a queue for every small replacement may need broader standing permission. A policy that routinely approves after ordering needs clearer timing or easier access.
For a simple manual pilot, allow an illustrative four hours to review purchases, write the matrix and set up the register. At an internal rate of $30 an hour, that is $120 of capacity. A 15-minute weekly review adds roughly one hour, or $30, in a four-week month. Obtain separate software pricing only after identifying which controls require a new tool.
Check the register against actual orders and invoices, not just submitted forms. Unrecorded purchases cannot appear in a form-completion statistic. Sample a few payments and trace backwards to their approval, budget reservation and receipt evidence. Investigate gaps as process problems before assuming staff deliberately ignored a rule.
Publish the final policy with an owner, effective date and review date. Explain what staff can buy confidently, where to ask for a decision and how to handle an urgent need. A useful spending policy gives people permission within clear boundaries and leaves a record that the next person can understand.
Questions staff ask about purchase permission
Can someone request a purchase without a company card?
Yes. Keep permission to request separate from the method used to pay. A staff member can submit the business need, proposed supplier and full cost, then an authorised buyer places the order after approval. Record the requester and buyer separately so that delivery questions go to the right person and the approval remains traceable.
What if an approval was given verbally?
Record it promptly against the purchase reference, including the amount, scope, approver and time. Ask the approver to confirm the record. For a genuine emergency, your policy can specify how that confirmation follows the urgent decision. A later note should describe what actually happened rather than pretending approval was recorded before the purchase.
Can one purchase use two department budgets?
Yes, if you record the agreed allocation and obtain the required approval from each budget owner. Apply the spending threshold to the whole purchase, rather than treating each share as a separate lower-value request. Reserve each budget's share only when the necessary decisions are complete, and keep both allocations linked to one purchase reference.
Further reads
- How to Automate Purchase Orders and Supplier Emails With AI — Carry approved requests into supplier orders.
- AI Accounts Payable: Approvals and Payment Runs Without Chaos — Control invoice approval and payment after purchasing.
- AI Expense Management: Receipts, Mileage, and Approvals — Handle receipts and staff reimbursement separately.
- AI Tool Approval Process: How Staff Request a New AI Tool — Add appropriate checks for new AI subscriptions.
- How to Catch Duplicate Invoices and Payment Fraud With AI — Why built-in duplicate checks miss near-matches, how a monthly AI sweep and a scoring rubric catch them, and the callback rule that stops bank-detail fraud.
- How to Match Supplier Invoices to Purchase Orders Automatically — Two-way vs three-way matching, the tools that do it, tolerance rules you can copy, an AI prompt for invoices without PO numbers, and a farm shop's fortnight.
- AI Supplier Management: Track Prices, Lead Times, and Risk — A supplier register AI can keep up to date: price histories from invoices, measured lead times, delivery performance and a simple risk score, reviewed monthly.
- AI Invoice Processing: Stop Typing Supplier Bills by Hand — How AI reads supplier bills into your accounting software, the six places extraction goes wrong, and a 50-bill audit to prove it's working.
- How to Set Spending Limits and Alerts on Pay-As-You-Go AI Tools — Where the spend limits live in OpenAI, Anthropic, ChatGPT, Claude, Zapier, Make and n8n, and how to choose caps that stop a runaway without breaking bookings.
- How to Set Up an Approval Step for AI-Written Quotes — Approval rules, sending blocks and a two-minute approver checklist that catch wrong prices, bad maths and invented discounts in AI-drafted quotes.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Spendesk help centre, Understand your approval policy and Physical cards and Approval policies, checked 28 September 2026. All policy limits, budgets and scenarios are illustrative choices rather than legal requirements or software prices.