Small-business outsourcing research
What share of vendor rebate credits arrive inside the stated rebate term?
A protocol for measuring how many vendor rebate claims are credited inside the term, and for keeping short pays and denials visible.

Research question and scope
This protocol asks what share of vendor rebate claims are credited inside the term the vendor states. The unit is one claim line, not one invoice and not one vendor. The study measures the share credited on time, the share credited late, and the amount written off. It does not judge whether the rebate program was worth the administrative cost.
Set the scope to one business, one vendor program, and one term document. Record the qualifying products, the purchase window, the claim deadline, and the credit method. If the vendor changes the term during the study, keep the original term for purchases already made and analyze later purchases separately. A new portal can change submission speed without changing the agreement.
Define the population as every claim line submitted during the window, including lines that were denied and lines the vendor short paid. State any exclusion, such as a sample or promotional order, and apply it to every line. Test the definition on ten closed claims before collection begins. The reader should be able to rebuild the population from the claims and the ledger.
Definitions that make the measure reproducible
Define the claim date as the date the vendor received the submission, not the date the assistant prepared it. Define the credit date as the date the credit note was issued or the ledger entry was posted, and record which one the business uses. Define the stated term from the vendor document in force at purchase. A term that is not written down cannot be measured.
Define a short pay as a credit below the claimed line amount and a denial as a line with no credit. Record both in the denominator rather than dropping them. Treat a credit applied to a future invoice as a credit with the invoice date noted. A protocol that counts only clean credits will overstate the result.
Evidence standard and data dictionary
For each claim line, capture the claim identifier, program, vendor, purchase invoice, product, quantity, claimed amount, submission date, credit note date, credited amount, and ledger reference. Add the reviewer and the date the match was checked. Keep the term document and the vendor confirmation linked to the claim. A line with no invoice reference is not ready for analysis.
Capture the reason for a short pay or denial when it is documented: an excluded product, a missing proof of purchase, an expired term, or a calculation dispute. Do not infer a reason from an empty field. Mark unknown reasons as unknown and report the count. A guessed reason hides the step that actually needs repair.
Sampling and collection
Collect every claim line in the window rather than a sample, because the term applies to each purchase. If the business runs several programs or vendors, collect each separately and record the group. A combined rate can hide one vendor that pays consistently late. Report the number of lines and the claimed value behind every percentage.
Draw dates from the vendor portal, the credit notes, and the ledger, not from a spreadsheet maintained after the fact. If the portal history is incomplete, say so and reduce the claim. Record the export date, the filters, and any line that could not be matched to a credit. A missing match is itself a finding about the control.
Analysis and reporting
Report the share credited inside the term, the share credited late, and the share denied or still open. Show the median and range of days from submission to credit. Present the results by vendor, program, and purchase period. Use the same denominator for every rate.
Separate a late credit from a short pay, because one is a timing problem and the other is an amount problem. Report both because they lead to different follow-ups. A late credit may still arrive in full and need only a reminder. A short pay needs a documented decision before the difference is written off. A business may accept a late credit but should not accept a silent write-off.
Limits of the evidence
The credit note can show that money was applied, but it cannot show whether the rebate was profitable after the administrative cost. The protocol also cannot capture a verbal promise from a sales representative. Record the gap in the file when a promise was never written down. A rate that ignores the cost of claiming may make a weak program look strong. State that limitation before presenting the rate.
A small business may have too few claims to support a stable trend. Describe the line count and the vendor mix instead of ranking staff. Do not compare a program with a thirty-day term with one that pays quarterly. Report the term beside the rate.
What to change
Give the result to the owner and the purchasing lead and ask them to choose one observable change. The change might be a claim calendar, a required proof-of-purchase pack, a named claim owner, or a quarterly vendor review. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions.
If the on-time rate rises but short pays also rise, the team may be filing fast with weak evidence. If both fall but write-offs shrink, the vendor may be enforcing a stricter term. Report the movements together before declaring success. Close the review when the owner accepts the finding and the next collection date is set.
Sources
- Internal Revenue Service, Publication 583, starting a business and keeping records, Internal Revenue Service; checked 2026-11-18
- U.S. Small Business Administration, manage your business, U.S. Small Business Administration; checked 2026-11-18
- U.S. Government Accountability Office, internal control standards, U.S. Government Accountability Office; checked 2026-11-18
- U.S. Small Business Administration, marketing and sales, U.S. Small Business Administration; checked 2026-11-18
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
What share of waitlisted customers are offered a slot within two business days?
A protocol for measuring how many waitlisted customers receive a specific slot offer inside the two-business-day window the shop states.
How long do delivery route exceptions wait before the customer is told?
A protocol for measuring the time between a recorded route exception and the first customer notice, and for separating internal delay from an unreachable customer.
How often are seasonal shift call-offs recorded before the shift starts?
A protocol for measuring how many seasonal shift call-offs reach the register before the scheduled start, without collecting medical detail.