Small-business outsourcing research
How often do supplier price changes reach the invoice unchecked?
A protocol for testing whether a supplier price change is approved, recorded, and matched to the invoice before the business pays it.
Research question and scope
This protocol asks how often a supplier price change reaches a paid invoice without a recorded review. The unit is one price change that affects at least one invoice in the observation window. The study measures whether the change was documented, approved, applied to the correct items, and matched to the invoice. It does not evaluate whether the new price was fair or whether the supplier was entitled to raise it.
Set the scope to one small business, one purchasing process, and one supplier group. Record the purchase order system, the invoice approval path, and the price list in force at the start. If the process changes during the window, keep the earlier definition for the full sample or analyze the change separately. A new approval step can look like better control when it is only a new form.
Population and unit of analysis
Define the population as all supplier price changes that affected an invoice during the window, including changes that were rejected or absorbed. The unit is the price change, identified by the supplier, the item, and the effective date. A change that applies to several items is one unit with several line items. A second change for the same item on a later date is a new unit.
Record the supplier, the item category, the change size, and whether the item is customer-facing. These strata matter because a price change on a commodity input and one on a custom component carry different approval needs. Include changes that were communicated verbally, because the absence of a written notice is part of the finding. Test the unit definition on two ordinary changes before collection begins.
Definitions that make the measure reproducible
Define a documented change as one with a written notice that names the item, the old price, the new price, and the effective date. Define an approved change as one with a named owner's decision recorded before the invoice was paid. Define a matched invoice as one where the price, quantity, and unit of measure agree with the approved change. Define an unchecked change as one paid without at least one of those conditions.
Do not count a supplier portal update as documented unless the business recorded the change in its own system. Do not count a verbal approval as approved unless it was written down the same day. A change that is correctly applied but never reviewed is still unchecked under this definition. Each definition should include one positive example and one boundary example.
Evidence standard and data dictionary
For each change, capture the supplier, the item, the old price, the new price, the effective date, and the notice format. Add the approval owner, the approval date, the purchase order, the invoice, and the payment date. Record whether the invoice matched and whether the price list was updated. Code each field as present, missing, or not applicable.
Also record whether the change was communicated to the customer-facing team and whether an open quote was affected. These fields help explain a margin loss that happened after the invoice was correctly paid. If the notice is a portal screenshot, record the capture date. A second coder should be able to classify the change from the packet without asking the buyer what happened.
Sampling and collection
Draw the sample from the purchase order and invoice systems rather than from a list of recent price arguments. Record the export date, the filters, the row count, and the selection rule. Include changes from different suppliers and item categories so the result is not dominated by one relationship. If the population is ordered by invoice date, a fixed interval spreads the sample across the window.
Collect the notice, the approval, the purchase order, and the invoice as they existed at the time of payment. Do not reconstruct a missing approval from memory or from a later email. If the notice was verbal, record who gave it and when. Note the collection date separately from the payment date so the reader can see how much of the record has aged.
Analysis and reporting
Report the number of price changes, the share documented before the invoice, the share approved before payment, and the share matched to the invoice. Show the counts by supplier and item category. Present the median time from notice to approval and the share of changes that updated the price list. Use the same denominator for every rate.
Inspect the unchecked changes and describe the pattern without naming the supplier. A cluster in one supplier may point to a notice problem, while a cluster in one item category may point to a missing approval rule. Compare the change size with the review outcome, because a small change may be below the approval threshold. Report the changes that reached a customer quote separately.
Limitations and sources of error
The record cannot show whether the business negotiated well or whether the supplier's cost increased. It can show only whether the change was documented, approved, and matched. A checked change is not proof of a good price, and an unchecked one is not proof of a loss. The protocol also cannot capture a change that was absorbed in a lump-sum invoice without a line-item detail.
Purchase records can omit verbal notices, portal updates, and changes that were applied by the supplier without telling the buyer. A change that never appeared as a separate event may be invisible in the sample. Record those cases and their treatment instead of dropping them silently. If the same person buys and approves, note the independence limitation.
Review cadence and next action
Give the result to the owner and the purchasing lead and ask them to choose one observable change. The change might be a written notice requirement, an approval threshold, or a price-list update step before payment. Record the owner, the effective date, and the measure that will show whether the change worked. Avoid changing the threshold and the invoice check at the same time.
Repeat the protocol with the same definitions after the change and compare the same fields. If documentation improved but matching did not, the invoice check may be the weak step. If matching improved but the price list did not, the next order may still use the old price. Close the review when the owner accepts the finding and the next sample is scheduled.
Sources
- Association for Supply Chain Management, Association for Supply Chain Management; checked 2026-11-04
- U.S. Small Business Administration, manage your business, U.S. Small Business Administration; checked 2026-11-04
- Internal Revenue Service, small business and self-employed, Internal Revenue Service; checked 2026-11-04
- NIST Cybersecurity Framework, NIST; checked 2026-11-04
Frequently asked questions
Does a favorable sample prove the routine caused the result?
No. The design is observational and supports a bounded operating decision, not a universal causal claim.
What should an owner review first?
Start with high-consequence defects, missing denominators, exceptions, and cases that required the owner to reconstruct the evidence.
Related research
How complete is the call-back record for missed small-business inquiries?
A protocol for measuring whether every missed call gets a complete call-back record, a named owner, and a confirmed customer contact.
How old are overdue receivables before the first follow-up?
A measurement protocol for the gap between an invoice due date and the first collection follow-up, with definitions, sampling, and reporting.
What does a new-customer onboarding handoff lose between sales and delivery?
A protocol for comparing what sales promised with what delivery received, including scope, dates, access, and the first success measure.