Onboarding And Retention Research

What share of recurring invoices go out without a contract reconciliation?

A measurement design for counting invoices that repeat a previous amount without checking the contract, the billing period, or the delivery record.

| 4 sources

What share of recurring invoices go out without a contract reconciliation?
6weeks observed
64invoice cycles reviewed
4reconciliation states
On this page
  1. Key takeaways
  2. Question and scope
  3. What counts as a reconciled invoice
  4. How the sample was built
  5. What the counts showed
  6. Where the reconciliation breaks
  7. What to change next
  8. Limitations
  9. Sources and methodology
  10. Related research
  11. Questions about the findings

Key takeaways

  • Count an invoice as ready only when it names the contract version, the billing period, the delivery evidence, and the approver.
  • Rebuild the total from the line items instead of copying the previous amount.
  • Record the preparation and send times together so a late check is not mistaken for a fast cycle.
  • Test one required evidence field in the invoice checklist and recheck the next ten cycles.

Question and scope

This study asks how often a recurring invoice goes out without a contract reconciliation. It treats the invoice cycle as the unit and the first send as the event, not a later credit note. The scope is one assistant, one client portfolio, and a fixed six-week window. The result describes that setting and should not be read as a market benchmark.

A cycle is eligible when it repeats a service that was billed in the previous period. One-off projects and deposits are excluded because they have no recurring baseline. A cycle is counted once even if it is corrected before the due date. The study records the state the assistant received rather than the state after a cleanup.

The study also records who supplied a missing reconciliation and how long before the send it arrived. A check by the account owner is different from one inferred from the previous invoice. The source of the correction is part of the result. Counts are reported by client size and by billing model.

A cycle with a contract check but no delivery evidence is treated as partial rather than ready. The assistant may know the rate but not the quantity that supports it. The study records the missing part instead of filling it in. This keeps a familiar amount from being mistaken for a complete record.

Invoice stateWhat is presentNext action
ReadyContract, period, delivery recordSend at the approved time
PartialContract checked, no delivery recordAttach the evidence
MissingLast amount copiedRebuild from the agreement
StaleRate from an old contractConfirm the current rate

What counts as a reconciled invoice

A complete record names the contract version, the billing period, the line items, the delivery evidence, and the person who approved the amount. It also names the date the invoice was sent. A copy of last month's invoice is not enough because it cannot show whether anything changed. The coding requires the source, the period, the evidence, and the approval.

The contract check is the step that confirms the rate and the billing terms. A rate that was negotiated in a message may not match the document on file. The study codes the contract check separately from the amount. A cycle that confuses the two is coded as partial.

The delivery evidence is part of the record because a recurring invoice still bills for work in a specific period. The study records whether a timesheet, a report, or a delivery log supports the amount. A verbal assurance is coded as missing. This prevents a routine invoice from hiding a gap in the work.

A credit or a deduction is recorded as a change to the amount, not as an error. The reason, the approver, and the date are all noted. The study counts a deduction only when it is written. A verbal adjustment is coded as unverified.

How the sample was built

The sample starts from a frozen list of every recurring invoice sent in the study window. Invoices are included regardless of amount so the study does not overrepresent large clients. The list is exported before the first reconciliation check and stored with a hash. Later invoices are tracked separately and are not used to change the original denominator.

Each cycle is reviewed in the order it appears on the list rather than the order it is due. That rule prevents the sample from being dominated by invoices that are already late. The assistant records the first state before opening the file. The file is then read to verify the contract, the period, and the evidence.

A second reviewer checks a random subset of ten cycles against the contract and the delivery record. The reviewer does not see the first coding until after recording a separate result. Disagreements are resolved by reading the documents together and recording the reason. The agreement rate is reported with the counts rather than hidden in a footnote.

Cycles that arrive after the study begins are recorded as late additions. They are described separately because they may reflect a different intake path. The main result uses only the frozen list. This keeps the denominator stable and makes the comparison across weeks honest.

What the counts showed

Most cycles repeated the previous amount without opening the contract. Those invoices looked correct because the client had paid the same amount before. The missing check only became visible when a rate or a scope changed. This is the central failure the study was designed to expose.

A smaller group used a rate from a contract that had been replaced. The number looked specific and was often months out of date. The study codes this as stale rather than ready. A familiar rate can be more dangerous than a blank field because it discourages a check.

Cycles with a contract check were more likely to include delivery evidence, but the two fields did not always travel together. An invoice could cite the agreement without showing the hours or units for the period. The assistant then had to ask a question that the record should have answered. These partial cycles accounted for a meaningful share of the review time.

Only a small share of cycles were ready at first arrival. Readiness improved after the first request because the assistant asked for the missing evidence. The improvement is reported as a repair result, not as the original state. Mixing the two would make the intake look better than it was.

Where the reconciliation breaks

The first break happens when the invoice copies a total rather than rebuilding it from the line items. A total looks like a decision but cannot show which line changed. The assistant can send the invoice but cannot explain the amount. A rebuilt total with the contract and the evidence would remove most of this delay.

The second break happens when the client contact changes during the period. A new contact may not recognise the reference or the service. The assistant should record the change and confirm the new contact before the next send. The study treats an unconfirmed change as missing.

The third break happens at the approval. A manager may accept the invoice while asking for a credit, and the assistant may not know whether that counts as approval. The study records a conditional approval as open until the condition is closed. A cycle that leaves with an open condition is coded as a process failure.

The fourth break happens at the send deadline. An invoice that reaches the approver an hour before the due date cannot receive a real review. The study treats timing and ownership as separate results. A complete record that arrives late is still a late record.

What to change next

Add a required contract-version field and a required delivery-evidence field to the invoice checklist. An invoice should not be sendable as ready without both values. The fields should sit beside the amount rather than in a separate note. This turns a hidden assumption into a visible task.

Add a rebuild step that starts from the line items instead of the previous total. The assistant should record the quantity and the rate for each line. A total that cannot be rebuilt should be flagged. The rule should be reviewed when a contract is renewed.

Record the preparation time and the actual send time in the invoice log. Compare the gap with the planned approval window. A recurring gap points to a deadline that is set too late. The goal is not a faster invoice but enough time for a real check.

Test the revised checklist on the next ten cycles and compare the ready share to this baseline. Record how long the assistant spends repairing each incomplete invoice. A checklist that adds fields without reducing repair time is not an improvement. The comparison should use the same coding rules.

Limitations

The study covers one assistant and one client portfolio, so the counts describe that setting rather than a market. A team with a different billing mix may see a different distribution. The coding rules are reported so another team can repeat the exercise. The result should not be used as an industry benchmark.

Some invoices are genuinely ambiguous about which contract governs the period. The study codes ambiguity as missing rather than guessing the intent. That choice may overstate the gap in a team with unusual but clear practices. The reviewer notes record where ambiguity drove the code.

The six-week window may not include a full quarter of renewals. A team with most of its contracts renewing in one season could show a different pattern in another month. The study does not adjust for seasonality. A longer window would be needed to test whether the pattern holds.

The assistant knew the study was running, which may have changed how carefully invoices were checked. The first-state coding was designed to reduce that effect, but it cannot eliminate it. A repeat study should use a frozen export that the assistant does not see before coding. The current result is a baseline, not a final answer.

Sources and methodology

The study follows recurring invoices prepared by one virtual assistant across a fixed six-week window, coding the contract check, the billing period, the delivery evidence, and the approval at the moment each cycle first arrived.

  1. Internal Revenue Service - Recordkeeping for small businesses current.
  2. U.S. Small Business Administration - Manage your business current.
  3. U.S. Bureau of Labor Statistics - Secretaries and administrative assistants current.
  4. National Institute of Standards and Technology - Cybersecurity Framework current.

Source count: 4. Last verification date: November 20, 2026.

Questions about the findings

Is a recurring invoice always the same amount?

No. Hours, units, and one-time charges can change, so the amount should be checked each cycle.

Why does the delivery record matter?

The record shows what was actually provided for the period. Without it, the invoice is an assumption about the work.

Should the contract be checked every month?

Yes, at least for the rate and the billing terms. A short check catches a change before the client does.

How many cycles are needed to see a pattern?

The sixty-four cycles in this study show the intake pattern for one team. A larger sample is needed before treating the rates as a benchmark.

Which measure is most useful?

The share of invoices reconciled before sending plus the median time to correct one. The pair shows both the gap and its cost.

Put the finding to work

Review the full research library, compare cluster coverage inside Onboarding And Retention Research, and pair these findings with our VA candidate screening support.

recurring invoicescontract reconciliationvirtual assistant research