On this page Jump to section
Published October 27, 2026
Question and scope
The protocol does not estimate an industry benchmark; it produces a local description that small business bookkeeping teams can review. If one request produces several journal memo updates, define whether the unit is the request or each update before sampling. Record how corrections, reopens, and duplicate requests are treated so missing receipt rate cannot be inflated by reclassification. Separate the operational question from the compliance question; this method does not certify either outcome. Link the observation to the exact field in the bill pay system and to the journal memo that supports it.
The scope is one defined population of chart of accounts cases observed from first request through verified close in the receipt inbox. If one request produces several missing receipt note updates, define whether the unit is the request or each update before sampling. Write the primary measure and one supporting measure; a measure without a denominator or observation window is not ready. Separate the operational question from the compliance question; this method does not certify either outcome. Do not let a summary written later replace the evidence that was available at the first decision.
Population and unit
If a reopened case creates a new requirement, count it as a new case and retain a link to the earlier record. A case that moves between owners stays one case unless the process defines a new requirement at the handoff. The definition should make it possible to classify a case without asking the person who did the work. If a request was reopened after the window, keep it in the original population and report the later event separately. If the case moved between owners, include both owner periods in the review note and name the handoff time.
Record the opening count by owner and channel, because a single total can hide a queue concentrated in one person. A denominator that changes during the window should be reported separately for each period. Write the rule for a missing bill image before the first case so the treatment is consistent. A case that never received an owner still belongs in the population; do not drop it because it is difficult to classify. Keep the review note with the case so the next sampler does not have to reconstruct the decision from memory.
Definitions and measures
If the definition of completion changes, keep the old and new rules side by side for the transition period. Test the data dictionary on a small set of cases and revise ambiguous fields before the main sample. Before collection, test the definitions on a missing bill image, a reopened case, and a handoff. Keep a change log for every definition adjustment and the date it took effect. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract.
Test each definition on a routine case, a missing-evidence case, and a case that crossed owners. Define allowed values for status, reason, owner, and evidence state before collection. Record the person who approved the definition and the date it became effective. Write the start and stop events as observable actions, not as opinions about whether the work felt finished. At QBO Assistant, the chart of accounts review should end with a dated note and a named owner for the next check.
Data dictionary and evidence
Mark missing, unavailable, and confirmed negative values separately; collapsing them hides the difference between no evidence and evidence of absence. Version the dictionary and report which version was used for each observation period. A missing value should have a reason code, not a blank cell or a zero. Use a separate field for reviewer notes so the coded values stay comparable. If the evidence is sensitive, record the approved reference and access path rather than copying the content.
Mark missing, unavailable, and confirmed negative values separately; collapsing them hides the difference between no evidence and evidence of absence. Use a controlled list for exception reasons; do not let free text become the analysis category. Record the data extraction date and the version of QuickBooks Online used for the population count. Archive the dictionary with the study so a later reviewer can reproduce the categories. The note should distinguish what was observed, what was inferred, and what still needs an owner decision.
Record the version or date of the reconciliation report and the the bank feed value so a later reviewer can see what was known at the first action. Version the dictionary and report which version was used for each observation period. A missing value should have a reason code, not a blank cell or a zero. Do not use a zero or an empty string to represent missing evidence. Record this decision in the study log with the case key, the review date, and the person who approved the classification.
Sampling and collection
Use a random or systematic start rule for the first case, then take consecutive cases within each stratum. A second reviewer should re-extract a small subsample and record disagreements before the full analysis. Include reopened, unresolved, and exception cases in the sample frame. Keep a table of planned, eligible, selected, and reviewed counts for each stratum. Keep the evidence reference beside the coded value so a reviewer can test the same case without rebuilding the queue.
A convenience sample of recently closed cases will overrepresent easy work and underrepresent the tail that needs attention. Use the same collection form for every case and keep the original record linked to the extracted fields. Keep the sample selection reproducible by recording the export date, filter, and random seed or start rule. Do not let the reviewer choose the sample after seeing the results. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it.
Record the eligible count, the sample size, and every exclusion so another reviewer can reproduce the sample. A second reviewer should re-extract a small subsample and record disagreements before the full analysis. Use a random or systematic start rule and then take consecutive cases within each stratum. Include at least one case from each owner in scope when the frame allows it. At QBO Assistant, the reviewer should be able to explain this step to business owner from the case record alone.
Analysis and reporting
State which findings are descriptive and which require a follow-up test with a larger or different sample. A small sample should be reported with the number of cases that drive the result. Write the finding in plain language and separate what was observed from what the team believes caused it. Show the age distribution and the open-case count by owner, not only the mean. Use the same note in the case file and the study extract; do not create a second version in a personal document.
A difference between two periods is a signal to inspect, not proof that a process change caused the change. For chart of accounts, report the age distribution and the share of cases waiting on a named owner. When two groups differ, check whether the difference survives after adjusting for case mix and evidence standard. Use a case-level table to explain an outlier before treating it as a process signal. When a case needs an exception, record the reason, the owner, and the date before continuing the review.
Limitations
The method also cannot observe work that never entered the queue, which may be the most important missing population. Changes in staffing, access, or the bill pay system during the window can create a difference that is not a process effect. Name the follow-up evidence that would reduce the largest uncertainty. State that the result describes the observed sample, not the whole industry or every team in the service. Keep the measurement note short enough to read with the case and specific enough to support the reported missing receipt rate.
Selection bias remains if the team samples only records that are easy to open or cases handled by cooperative owners. The cited sources describe recordkeeping, privacy, security, or control practice; they do not supply a local benchmark. State that the result describes the observed sample and not the entire industry or every team in the service. A missing record is evidence about the record, not proof that the work was never done. If two reviewers disagree, preserve both classifications until the definition or the evidence is resolved.
Review and next action
Keep the review note with the chart of accounts evidence so the next reviewer can see why the process changed. A quality review should end with a testable next step, not a general instruction to improve. If the action requires a policy or access change, route it to the owner and record the decision. Record the owner, due date, and exact change that will be tested at the next review. Link the observation to the exact field in the receipt inbox and to the missing receipt note that supports it.
Record the decision and the next check so the study does not end as an archive. Keep the review note with the chart of accounts evidence so the next owner can see why the process changed. Report the action result even if the change did not work; a failed test is still evidence. Keep the prior procedure available so the next reviewer can compare the old and new states. Do not let a summary written later replace the evidence that was available at the first decision.