What it means
An employee needs a new service and, without clear rules, may buy it on a company card while another team already pays for the same product, so spend control makes the need, approver, budget and supplier visible before a commitment is made. Set approval thresholds that fit the risk and the size of the business: a routine low-value purchase may need only a team budget holder, while a long contract or sensitive vendor warrants finance, legal or security review.
Higher thresholds are design choices, not universal rules. Define who can commit the company, because an approval to order does not necessarily permit signing a contract with unusual terms, and purchasing authority, payment authority and contract-signing authority should be kept distinct.
A budget states the spending plan while an approval confirms a particular purchase fits the plan and the need, and both matter because an item can be within budget yet unnecessary, or necessary but require a deliberate budget change. Purchase orders can document the approved quantity, price and supplier before goods arrive, and invoices should be matched to the order and evidence of delivery when the process fits, since small businesses may use a lighter control but should still know what was promised.
Company cards need appropriate limits and prompt review, because a monthly cap prevents some overspending but cannot tell whether each transaction had a valid purpose, so require receipts and review unusual merchants or repeat charges. Recurring charges deserve their own register recording owner, renewal date, notice period, contracted amount and payment method, since a small monthly subscription can accumulate into a meaningful annual expense if nobody owns it.
Spend analysis examines who spent money, on what, when and with which suppliers, and APQC describes it as a way to see procurement patterns and find opportunities for better decisions, so categorise transactions well enough to spot overlap and price changes. One illustrative metric is spend through approved channels divided by total addressable spend, so if $8.5 million of $10 million went through approved channels, the share is 85%, and exclusions and the period should be defined before comparing teams.
That share does not say whether prices were fair or approvals were thoughtful, since a business could route every bad purchase through an official form, so pair channel compliance with reviews of value, delivery and supplier performance. Separate duties where practical, because the same person should not routinely choose a supplier, approve their own invoice, change bank details and release payment without review, although small teams can use owner review or independent reconciliation where full separation is impossible.
Control design should match risk: emergency repairs may need a fast exception with an after-the-fact record, not a rule that stops urgent work, and the record should show who approved the exception and why it was needed. Track both commitments and cash payments, because a signed annual service contract can tie up future cash before the invoice is paid and looking only at this month's bank balance may understate what has already been promised.
Preferred suppliers can simplify due diligence and pricing, but a documented alternative should be allowed when service, location or quality makes the approved supplier unsuitable, because an inflexible list can drive staff to work around the system. Review supplier and employee data carefully, since duplicate invoices, split purchases just below thresholds and unusual refunds deserve a second look, although a flag starts a review and is not proof of misconduct.
Finance should report planned, committed and actual spending by category and owner so budget holders get timely information rather than a surprise at month-end, and the cost of control also matters because multi-stage approvals for a minor expense waste time and encourage workarounds, so simplify the route for low-risk spending and focus attention on large, recurring or hard-to-reverse commitments. Good spend control leaves a usable record of request, approval, contract or order, receipt and payment, which helps managers decide whether an expense should continue and who can explain it, with the aim of better choices and fewer cash surprises.
In practice
Real-world examples.
Example
A team obtains manager approval before a purchase above its internal threshold. The request names the need, the supplier and the budget line, so finance can see the commitment before any money moves. Purchases below the threshold follow a lighter route.
Example
A card owner checks recurring software charges each month against an owner list. A tool that nobody on the list claims is queried before the next renewal date. The check takes minutes and prevents a quiet annual charge from rolling over.
Example
Finance reviews an emergency purchase after it is made and documents the exception. A burst pipe needed an immediate repair, so no prior approval was possible. The record shows who authorised the work, why it was urgent and what it cost.
Formula
Calculation
Approved-channel share = spend through approved channels / total addressable spend x 100. Worked example: $8.5 million / $10 million x 100 = 85%. The denominator must be defined, and the remaining $1.5 million should be reviewed to see which purchases fell outside approved channels and why.
A second calculation tracks commitments against cash. A fictional company signs a $60,000 annual software contract in January, payable at $5,000 a month. At the end of January the bank shows only $5,000 paid, but the company has committed $60,000, so $60,000 - $5,000 = $55,000 of cash is still promised for the rest of the year. A manager who looks only at the bank balance would miss that $55,000.Case study
Seen in the real world.
This entirely fictional example follows Horizon Tech, an invented startup. Teams ordered overlapping subscriptions on company cards, and several annual renewals surprised finance. The company assigned budget owners, logged renewals and set proportionate purchase approval limits. At the next review, it cancelled tools it no longer needed and kept some specialist services.
Any savings would depend on actual contract terms and usage; this example claims no guaranteed percentage. Horizon Tech also kept its controls light for small items. Purchases under a modest threshold needed only the budget owner's approval, while multi-year contracts went to finance and legal. Staff stopped working around the system because the routine route was quick, and the exceptions that remained were recorded with a reason.
Watch out
Common mistakes.
- Making approval steps so slow that staff work around them.
- Reviewing invoices but ignoring signed future commitments.
- Treating spend through approved channels as proof that every purchase adds value.
Questions
People also ask.
What is spend control?
Rules and checks for authorizing purchases and monitoring committed and actual costs.
What tools are used?
Approvals, budgets, purchase orders, card controls, renewal records and spend reports can all help.
Can it be too strict?
Yes. Slow rules can block useful work and encourage unrecorded exceptions.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%