The invoice is not the approval: a 1-page control for supplier spend
Use a lightweight supplier-commitment register to match invoices to approved spend, resolve exceptions early, and keep payments moving.
An invoice is a request to pay money. It is not the moment to decide whether the company should have spent it.
That distinction matters in a growing business. Someone asks a familiar supplier for an urgent delivery, accepts a quote in an email, or asks a contractor to start. The invoice reaches the bookkeeper later. The manager is then asked to approve payment for work that has already been ordered or completed.
The invoice may be completely legitimate. The supplier may have done exactly what was requested. But the company has lost the useful moment to decide the price, scope, and owner of the commitment.
The solution is not necessarily procurement software or a purchase order for every low-value expense. It is a small, visible record for material supplier commitments before they become invoices.
By the end of this article, you should be able to set up that record, decide which bills it applies to, and give Accounts Payable a clear rule for what to do when an invoice does not match it.
First, separate the 2 decisions
Most companies combine 2 distinct decisions into 1 invoice-approval step.
Spend approval happens before the company commits. It answers:
- Do we need this?
- Is this supplier acceptable?
- What price, scope, and delivery date did we agree?
- Who owns the budget?
Payment approval happens when the invoice arrives. It answers:
- Did we receive the goods or work?
- Does the invoice match the commitment?
- If it differs, who is choosing to accept the difference?
Both decisions are necessary. But a payment approval cannot retroactively control a commitment made weeks earlier.
This is not a criticism of the person approving the invoice. In a small company, they may be the same person who made the original decision. The weakness is simply that the evidence of that decision is scattered, or does not exist, when finance needs it.
The practical solution: a supplier-commitment register
Use the accounting package, a purchasing tool, or a shared spreadsheet. The tool matters less than the record. For each material, non-recurring supplier commitment, record these 6 fields before work starts or an order is placed:
| Record | Why it matters |
|---|---|
| Supplier | Makes the commitment searchable when the invoice arrives. |
| Budget owner | Gives finance 1 accountable person for a question or exception. |
| Scope or item | Distinguishes a $5,000 project from an open-ended request for “support.” |
| Approved ceiling | States the agreed total, or a defined not-to-exceed amount. |
| Evidence link | Points to the quote, email approval, contract, or purchase order. |
| Delivery or renewal point | Tells finance who can confirm completion, receipt, or a scheduled change. |
This is not an extra ledger to reconcile. It is an index to the decision the company already made. The bookkeeper should be able to find it in under a minute from the supplier name or reference number.
Choose a threshold so the register applies where the effort is justified. The threshold may differ for a $200 office purchase, a $3,000 subcontractor bill, and a $15,000 inventory order. The point is not to impose 1 number on every business. It is to define the spend for which “I think someone approved it” is not enough.
Give finance a simple invoice rule
Once the register exists, the invoice process becomes short.
- Find the commitment. Match the invoice to its supplier record, order, or approved email.
- Confirm the receipt. For goods, confirm what arrived. For services, ask the owner to confirm the work or milestone due for payment.
- Compare the amounts. Check the invoice total, quantity, price, charges, and payment terms against what was approved.
- Pay or send an exception. If it matches, pay it through the normal run. If it does not, send the difference to the budget owner who can accept, dispute, or renegotiate it.
The rule for an invoice with no prior commitment should be equally clear: hold it from the payment run until the owner supplies the original approval or explicitly treats it as an exception. “Hold” does not mean accuse the supplier or refuse a legitimate invoice. It means the business decides how to deal with an unrecorded commitment instead of making it invisible.
An accounting or purchasing system can automate parts of this later. A small company can apply the control now without adopting enterprise vocabulary or a full software stack.
Keep recurring bills out of the exception pile
Recurring supplier bills need a lighter version of the same control.
For each recurring bill, record the supplier, owner, expected monthly or annual amount, contract end or renewal date, and the event that requires fresh approval. That event might be a price change, a new minimum term, a scope change, or a renewal date.
When the bill arrives at the expected amount, finance can pay it promptly. When it changes, the register turns the difference into a decision for the owner instead of an unexplained surprise in the payment run.
This is particularly useful for managed services, software subscriptions, property costs, equipment leases, and contractors on monthly retainers. It is not a reason to make an approver click “yes” every month merely to prove they are still employed.
An illustrative example
Assume a company approves an order for 100 units at $120 each. The approved ceiling is $12,000 and the quote does not include an expedite fee.
The invoice arrives for $12,600: $12,000 for the units and a $600 expedite charge.
The arithmetic is straightforward:
- Approved commitment: 100 × $120 = $12,000.
- Invoice: $12,600.
- Difference requiring a decision: $12,600 − $12,000 = $600.
The $600 may be valid. The buyer may have asked for urgent delivery, or the supplier may have made a mistake. The register does not decide that. It does ensure the right person makes the decision while the invoice is still an exception, rather than allowing an extra charge to become the default because nobody can find the original agreement.
This is an illustrative scenario, not a client result or a claim that every variance can be recovered.
Run a 30-day test before buying anything
Start with 1 category where supplier commitments are meaningful: inventory, subcontractors, maintenance, freight, or recurring technology costs. Do not start with all company spending.
For 30 days:
- Set the threshold and nominate the budget owners.
- Create the 6-field register in the tool the finance team already uses.
- Require a record before new commitments above that threshold are made.
- Match incoming invoices to the record and note every exception.
- Review the exceptions at month-end: missing approvals, changed prices, incomplete deliveries, duplicate invoices, and justified urgent purchases.
At the end of the test, make the next decision from evidence:
- Keep the lightweight process if the commitments and invoices are traceable.
- Extend it to another spend category if the same exceptions recur.
- Configure the controls already available in the accounting or purchasing system if invoice volume makes the manual register impractical.
- Investigate a supplier or category if the same unexplained changes keep appearing.
That is a more useful outcome than issuing an enterprise-software mandate before the company knows whether the weakness is its process, its data, or 1 supplier relationship.
Where FoundMargin can help
The hard part is rarely building a spreadsheet. It is deciding which invoices and commitments are material, reconstructing the real approval path across finance and operations, and separating a one-off exception from a repeatable source of cost or risk.
FoundMargin can examine a sample of supplier invoices, approval records, purchase data, and recurring commitments alongside the way the work actually moves through the business. The goal is to identify the exceptions worth fixing, quantify them where the evidence supports it, and recommend the lightest control that will hold. Sometimes that means a better register and a named owner. Sometimes it means using an existing system feature. Sometimes the evidence supports keeping the current process.
The value is not more administration
The register earns its place when it reduces the time spent reconstructing a decision after the invoice arrives. It gives an owner a chance to challenge an unexpected charge, lets finance pay clean invoices faster, and makes recurring commitments visible before they renew.
For a small company, the first version may be a spreadsheet with links to approved emails. For a purchasing-heavy business, it may become a purchase order and goods-received workflow. Either is acceptable if it answers 3 questions reliably:
- Who approved this commitment?
- What did the company agree to pay for?
- Did the company receive it before cash left the bank?
The invoice is evidence for the third question. It should not be the first evidence the company has for the first 2.
· M Lokhandwala