Small-business outsourcing research

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.

Research question and scope

This protocol asks how much time passes between an invoice due date and the first collection follow-up. The unit is one overdue invoice inside a defined observation window. The study measures the first follow-up date, the channel, the owner, and the customer's response. It does not evaluate whether the customer was able to pay or whether the invoice was correct.

Set the scope to one small business, one billing system, and one collection routine. Record the payment terms, the follow-up schedule, and the person responsible in force at the start. If the routine changes during the window, keep the earlier definition for the full sample or analyze the change separately. A new reminder template can change the response rate without changing the timing.

Population and unit of analysis

Define the population as all invoices that became overdue during the window, including invoices that were paid before any follow-up. The unit is the invoice, identified by the invoice number and the customer. A partial payment leaves the invoice as one unit with a balance history. A separate invoice for a different period is a new unit.

Record the customer type, the invoice amount, the payment terms, and whether the customer had a history of late payment. These strata matter because a large invoice to a long-term customer and a small invoice to a new customer carry different risk. Include invoices that were disputed, because a dispute changes the follow-up path. Test the unit definition on two ordinary invoices before collection begins.

Definitions that make the measure reproducible

Define the due date as the date stated on the invoice, not the date the customer received it. Define the first follow-up as the first outbound contact that asks for payment, whether by email, phone, or letter. Define a reminder as a message that only restates the invoice without asking for a specific action. Define a response as any reply from the customer that acknowledges the balance.

Do not count an automated system notification as a follow-up unless a person reviewed the account. Do not count a message sent to the wrong contact as a valid attempt. An invoice that was paid before the follow-up is still part of the population because it shows how often the routine is unnecessary. Each definition should include one positive example and one boundary example.

Evidence standard and data dictionary

For each invoice, capture the invoice number, the customer, the amount, the due date, the first follow-up date, the channel, the sender, and the response date. Add the payment date, the balance, and whether the invoice was disputed. Record the number of follow-ups before payment and the escalation step if any. Code each field as present, missing, or not applicable.

Also record whether the customer had an approved payment plan and whether the follow-up was sent to the billing contact. These fields help explain a late follow-up that was caused by a missing contact. If the follow-up date is inferred from a sent folder, mark it as inferred. A second coder should be able to reproduce the classification from the record.

Sampling and collection

Draw the sample from the billing system rather than from a list of problem accounts. Record the export date, the filters, the row count, and the selection rule. Include invoices of different sizes and customer types so the result is not dominated by one large account. If the population is ordered by due date, a fixed interval spreads the sample across the window.

Collect the invoice and the communication record as they existed at the time of the follow-up. Do not reconstruct a missing reminder from memory. If a message was sent from a personal inbox, record that fact and the reason. Note the collection date separately from the due date so the reader can see how much of the record has aged.

Analysis and reporting

Report the median days from due date to first follow-up, the share followed up within the stated window, and the share paid before any follow-up. Show the counts by invoice size and customer type. Present the response rate and the median days to payment after the first follow-up. Use the same denominator for every rate and show the number of invoices with incomplete evidence.

Inspect the invoices with the longest delay and describe the pattern without naming the customer. A cluster in one customer type may point to a contact problem, while a cluster in one amount band may point to a prioritization rule. Compare the delay with the payment terms, because a net-60 invoice has a different clock from a net-7 invoice. Report disputed invoices separately.

Limitations and sources of error

The record cannot show whether the customer would have paid sooner with a different message or whether the business needed the cash earlier. It can show only when the first follow-up happened and what the customer did. A fast follow-up is not proof of a good relationship, and a slow one is not proof of neglect. The protocol also cannot capture a conversation that happened in person.

Billing exports can omit invoices that were voided, rewritten, or paid outside the system. A cash payment may never appear in the follow-up record. Record those cases and their treatment instead of dropping them silently. If the same person sends the invoice and the follow-up, note the independence limitation and analyze that subgroup separately.

Review cadence and next action

Give the result to the owner and the bookkeeping lead and ask them to choose one observable change. The change might be a first follow-up on the due date, a required contact field, or a weekly aging review. Record the owner, the effective date, and the measure that will show whether the change worked. Avoid changing the terms and the reminder template at the same time.

Repeat the protocol with the same definitions after the change and compare the same fields. If the first follow-up got faster but payment did not, the message or the contact may be the problem. If payment improved but disputes did not, the invoice itself may need a clearer description. Close the review when the owner accepts the finding and the next sample is scheduled.

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