Small-business outsourcing research

How often do small-business invoices arrive without a matching purchase record?

A protocol for measuring invoice-to-purchase-record matching in a small business, with a clear unit, evidence standard, and dated review.

Research question and scope

This protocol asks how often a supplier invoice arrives without a matching purchase record and how the business handles the mismatch. The unit is one supplier invoice that reached a payment decision during the observation window. The study measures whether a purchase order, quote, or delivery record was available, whether the amount and quantity matched, and whether the invoice was paid before the mismatch was resolved. It does not evaluate whether the supplier was at fault.

Set the scope to one small business, one accounting system, and one invoice approval process. Record the purchase-order rules, the payment run schedule, and the supplier list at the start. If the process changes during the window, keep the earlier definition for the full sample or analyze the change as a separate period. A new approval step can look like better control when it is only a new gate.

Population and unit of analysis

Define the population as every supplier invoice that reached a payment decision during the window, including invoices that were held or disputed. The unit is the invoice, identified by the supplier and the invoice number. A corrected invoice is a revision of the same unit; a separate invoice for a different delivery is a new unit. A recurring subscription invoice is a new unit for each billing period.

Record the supplier, the amount band, the invoice type, and whether the invoice was expected. These strata matter because a utility bill and a custom order carry different matching expectations. Include invoices that were paid without a purchase order, because the base rate is part of the finding. Test the unit definition on two ordinary invoices before collection begins.

Definitions that make the measure reproducible

Define a matching purchase record as a purchase order, signed quote, or delivery note that names the same supplier, item, quantity, and agreed price. Define a match as agreement on the amount and quantity within a stated tolerance. Define a mismatch as a difference outside that tolerance. Define a missing record as no purchase record available at the payment decision.

Do not count an email approval as a purchase order unless it states the item, quantity, and price. Do not count a verbal confirmation as a matching record. A subscription invoice can match a contract that states the recurring amount and period. Each definition should include one positive example and one boundary example so a second reviewer can apply it consistently.

A purchase record can exist and still be unusable if it does not name the item or the agreed price. Record whether the record is specific enough for a reviewer to compare, not only whether a file exists. A vague record creates a match that looks complete but cannot be defended. That distinction belongs in the evidence standard.

Evidence standard and data dictionary

For each invoice, capture the supplier, the invoice number, the date, the amount, the purchase record reference, and the match result. Add whether the invoice was paid, held, or disputed and the date of the decision. Record the person who approved the payment and the system where the approval is stored. Keep the packet with the invoice record.

Also capture whether the purchase record was created before the invoice arrived. A record created after the invoice is a weak control even when the amount matches. If the record is a quote rather than an order, note the difference. A second reviewer should be able to reproduce the classification from the invoice packet.

A second view is the share of invoices that were paid before the purchase record was created. That pattern is a stronger control failure than a missing record that was later supplied. Record the creation time and the payment time together. The owner can then see whether the process is preventive or only corrective.

Sampling and collection

Draw the sample from the accounting system rather than from a list of disputed invoices. Record the export date, the filters, the row count, and the selection rule. Include invoices from every supplier band and every month so the result is not dominated by one large supplier. If the population is ordered by invoice date, a fixed interval spreads the sample across the window.

Collect the invoice and the purchase record as they existed at the payment decision, not as they look after later corrections. If a purchase order was created after the payment, record the creation date and analyze the original gap separately. Do not infer a match from the absence of a dispute. Note the collection date separately from the invoice date.

The review should also separate a missing purchase order from a purchase order that does not match the invoice. The first is a documentation gap, while the second is a price or quantity dispute. Show the two counts separately and describe the different fixes. A single mismatch rate hides which process needs attention.

Analysis and reporting

Report the number of invoices, the share with a matching record, the share with a mismatch, and the share with no record. Show the counts by supplier band and invoice type. Present the median time from invoice to payment and the share of mismatches paid before resolution. Use the same denominator for every rate.

Inspect the missing-record cases and describe the pattern without naming the supplier. A cluster in one invoice type may point to a missing purchase-order rule, while a cluster in one supplier may point to a recurring delivery that was never documented. Compare the result with the amount band, because a large invoice may receive more scrutiny. Report the held and disputed invoices separately.

A useful additional view is the age of the purchase record when the invoice arrived. A record created months earlier may not reflect the current price. Show the age distribution and describe the consequence. That view helps the owner decide whether the purchase-order process or the price-review process needs attention.

A useful check is whether the supplier was told about the missing record. A supplier who keeps sending invoices without a reference may need a purchase-order field on the invoice. Record the communication and the supplier response. That evidence helps the owner decide whether to change the supplier process.

Limitations and sources of error

The record cannot show whether the invoice was legitimate or whether the business received the goods. It can show only whether a matching record existed and how the payment was handled. A missing record is not proof of fraud, and a matching record is not proof of a good purchase. The protocol also cannot capture a purchase approved in a meeting and never written down.

Accounting systems can omit manual payments, petty cash, and invoices paid from a personal card. A supplier invoice that was paid outside the system may never appear in the sample. Record those cases and their treatment instead of dropping them silently. If the same person approved the purchase and the payment, note the independence limitation and analyze that subgroup separately.

The final view is the age of the invoice at payment. A late payment may be caused by a missing record rather than by cash flow. Show the age distribution and describe the relationship. That view helps the owner separate a control problem from a working-capital problem.

Review cadence and next action

Give the result to the owner and the bookkeeper and ask them to choose one observable change. The change might be a purchase-order threshold, a required delivery note, or a rule that no invoice is paid without a record. Record the owner, the effective date, and the measure that will show whether the change worked. Avoid changing the threshold and the payment run at the same time.

Repeat the protocol with the same definitions after the change and compare the same fields. If matching improved but payment time rose, the new control may be creating a bottleneck. If missing records fell but mismatches did not, the purchase record may be too vague. Close the review when the owner accepts the finding and the next sample is scheduled.

Keep the sample packet with the accounting record so the next review can repeat the same check. A finding without the underlying invoices is hard to defend or compare. Record the reviewer and the date. The packet is part of the control, not an archive afterthought. Record the review date with the sample.

Sources

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