69.5%
of bill headers were below 500, but they represented only 7.9% of billed amount at the approximate median source ID. This is an automation workload.
Cost-control system
Contractor cost controls work when evidence and ownership reach the operating decision. Most leaks are failures there before they are supplier failures. A repeat purchase may need a quote. A rental may need an off-rent decision. A software renewal may need a contract owner. An exception may need a fast path, not a blocked job.
This construction cost control system is built around a weekly cost review, not an annual budget meeting. A useful vendor cost control asks which repeat decision can be changed before the bill arrives, what record makes that decision credible, and who will prove the result. That lets a contractor move quickly without making every field purchase a finance meeting.
Level 2024 historical AP research
69.5%
of bill headers were below 500, but they represented only 7.9% of billed amount at the approximate median source ID. This is an automation workload.
72.5%
of billed amount sat with the five largest vendor names at the approximate median source ID. This is the negotiation and service-level agenda.
33.3%
of vendor names appeared once, but represented only 3.8% of billed amount. This is an onboarding and control problem.
Approximate medians across 652 eligible source company IDs and 1,192,695 eligible 2024 bill headers. Source IDs were not independently deduplicated or verified as contractors. Bills are not cash, consumption, overpayment, or savings. Open the full study →
01
Keep commitments, bills, payments, credits, rebates, and savings in separate fields. A lower quoted price is not a realized saving.
02
Preserve the prior quote, basket, rate card, contract, or invoice. Without a comparable baseline, an improvement is a story.
03
Use approved vendors, SKUs, permissions, and coding rules for repeat work. Route unusual purchases, urgent substitutions, and new vendors to an exception queue.
04
Check the later invoice, credit, off-rent record, renewal change, or service result. Close the action only when the evidence chain is complete.
The operating model
The aim is not to ask finance to approve every field purchase. It is to make the few repeating decisions that can create a loss visible early enough to act. The same register can cover materials, subcontracts, equipment, software, freight, cards, and recurring services. It should capture the business question, owner, evidence, decision deadline, and proof that closes the item.
| Control type | Trigger | Decision owner | Proof to close |
|---|---|---|---|
| Routine material | New vendor, nonstandard SKU, order threshold, or price variance | Operations or purchasing | Matched order, delivery, invoice, and job or stock destination |
| Supplier program | Quote, rebate, volume-price, card, or member offer | Purchasing plus finance | Terms, qualifying basket, invoice or credit, and landed-cost comparison |
| Recurring software | Renewal notice, new user, add-on, or unused workflow | Named business owner | Signed change, user and feature decision, and later statement |
| Equipment rental | Extension, job completion, no next use, or unassigned asset | Project or service owner | Off-rent confirmation, pickup record, and final invoice |
| Emergency exception | Availability, safety, customer recovery, or job-critical timing | Field leader with time-bound authority | Reason, cost, job impact, and later exception review |
The 45-minute cadence
A CEO does not need a full general-ledger review to control cost. Use a short weekly meeting with the person who can change the work. Start with open rentals and expiring renewals, then quote requests, purchase exceptions, price changes, and credits that have not arrived. Keep an item open until its promised evidence exists.
The accounting boundary
A purchase order is a commitment. A bill is an obligation. A payment is cash movement. A credit is a separate event. A lower unit price may be offset by freight, tax, a larger required order, carrying cost, a missed job, or a service delay. Keep those objects separate. When a result is reported, show the baseline, current landed cost, comparison period, service effect, and source documents. If one is missing, report an action taken, not savings realized.
That discipline turns a generic cost-cutting exercise into a usable management system. It also protects the field: a true emergency path remains fast because it is reviewed after the work, instead of being silently buried in a supplier report.
Level publishes aggregate historical AP research with its source-ID denominator, approximate-percentile method, query receipts, sensitivity, and limitations. Customer identifiers, raw transactions, uncommon merchants, dominated software cells, and claims of cash paid, contractor prevalence, overpayment, or verified savings remain excluded.
A cost control is a repeatable decision rule that names the owner, evidence, approval, action, and proof of result. It is broader than a budget or purchase approval.
No. An infrequent supplier can be necessary for emergency availability, technical support, or backup supply. Standardize routine work and review exceptions separately.
Only when a valid baseline and later invoice, statement, credit, or off-rent record show the change, while delivery, tax, freight, credits, inventory, downtime, and service effects are considered.
Drop your info and we’ll show your real margin after callbacks and rework, which crews and jobs are worth the time, and how much cash is sitting in work you have already finished.
No commitment. Real numbers, not generic advice.