On this page Jump to section
Question and scope
How long does an approved vendor bill wait before someone schedules it for payment, and which stage carries most of that wait? The scope is the accounts payable record of one business during a defined review window. The result describes that record rather than an industry benchmark. This note does not decide whether a particular payment was early, late, or commercially wise, because those judgments depend on vendor terms, cash position, and the owner's written payment policy. The narrow purpose is to make the approval-to-scheduling gap visible and reproducible.
Population and unit
Start with a dated export of bills approved during the review window, including bills that were approved but not yet scheduled. Record the vendor, bill reference, amount, due date, approver, approval evidence, and payment status. The unit is one approved bill. A bill approved twice after a correction remains one bill, but both approval events should be retained because the later event may reset the clock. Exclude bills that were voided before approval and bills that never required approval under the written policy, and record those exclusions so the denominator can be rebuilt.
Keep the population frozen at the moment of export. If a bill is scheduled during the review, note the change but do not silently replace the original row. A moving population makes the median look better or worse depending on when the analyst stops looking. Assign each bill a stable internal reference that does not expose bank details. Store the export with the review date and the name of the preparer, because the frozen list is the evidence that the measurement was bounded rather than assembled after the result was known.
Definitions and measures
An approval begins when a named approver records a decision in the system or in the documented approval channel. A verbal approval that is later entered counts only if the entry names the approver, the date, and the bill. Scheduling begins when the bill is placed in a payment batch or assigned a payment date in QuickBooks Online. The primary measure is whole calendar days from the recorded approval date to the recorded scheduling date. Compute the median and the 75th percentile, then report age bands such as same day, one to three days, four to seven days, and more than seven days.
Split the total gap into two stages. The first stage runs from approval to the moment a payment candidate is selected for a run, while the second runs from selection to the assigned payment date. That split separates a queue problem from a calendar problem, since a bill can sit unselected for days and then be paid immediately. A bill can also be selected quickly and wait for a scheduled run. Report the stages separately, because a single average hides which step the team can actually change.
Data collection
Use the bill history, audit log, and payment screen rather than memory. Capture the approval event, the bill status changes, the payment batch reference, and the scheduled date. If the system does not record a clean timestamp, mark the date as reconstructed and note who reconstructed it. A reconstructed date is weaker evidence than an audit-log event. Keep the raw export beside the coded sheet so another reviewer can retrace each row, and do not overwrite the original columns when adding analysis fields.
Where a bill moves between approval queues, record each queue entry and exit if the system exposes them. The extra rows can show whether the delay came from a missing document, a changed approver, or a payment run that was already closed. If the tool cannot show queue movement, say so in the limitations rather than inventing a stage. A shorter measurement with an honest gap is more useful than a complete-looking table built on assumptions.
A worked example
Consider a bill approved on the second day of the month with terms that allow payment on the twentieth. The approval is clear, but the bill is not selected for a run until the fifteenth. The first stage is thirteen days, and the second stage is five days to the scheduled date. The total gap is eighteen days, yet only five of those days belong to the payment calendar. The split keeps the team from blaming the run schedule for a wait that came from queue selection.
Now suppose a second bill is approved on the third and selected on the fourth, but the scheduled date lands on the eighteenth because the run is full. Its first stage is one day and its second stage is fourteen days. Both bills have long total gaps, but the correction differs. The first case points to queue ownership or document follow-up, while the second points to run capacity or cutoff design. A report that shows only totals would merge two different problems into one number.
Evidence standard
Each row needs the bill reference, the approval decision, the approver, the scheduling event, and the source of each date. If approval came through email, preserve the message reference in the approved system rather than copying its contents into the analysis file. If the payment date changed after scheduling, keep both the original and revised dates. Record the reason for the change when it is documented. This prevents a later delay from looking like an initial scheduling failure.
Protect vendor bank details, contract terms, and personal contact information. The analysis file should use internal references and amounts only where the amount is needed to interpret the queue. Do not place account numbers or tax identifiers in a shared spreadsheet. Limit access to the evidence folder to the review owner and the approver. The point of the measure is to improve the process, not to create a second store of sensitive payment data.
Interpretation limits
A long approval-to-scheduling gap does not prove that the team was careless. The vendor may offer extended terms, the owner may be conserving cash, or the bill may be disputed. A short gap does not prove that the process is strong, because a bill can be scheduled before the supporting evidence is complete. Pair this measure with a review of approval evidence and payment accuracy. Report the conditions that were present during the window, including holidays, staffing changes, and any policy change.
Avoid using the gap as an individual performance score. The same approver can face different vendor mixes and different bill values in different weeks. A median built from a small number of bills is sensitive to one unusual item. Report the count and the distribution, not just a single average. If the population is too small to support a stable percentile, say that plainly rather than presenting a fragile number as a trend.
The useful question is whether the team can explain the waits it sees and whether the explanation matches the evidence. A short written note beside each age band can capture the known cause without pretending to prove it. Mark the note as an observation, not a finding, until a second reviewer checks the source. This keeps the analysis honest when the underlying system has thin history. A measured gap with a modest explanation is more trustworthy than a confident story built from missing timestamps.
Review cadence
Run a baseline review, then repeat after any change to the approval policy, payment run calendar, or accounts payable staffing. A monthly cadence fits a steady payables process, while a quarterly review may be enough for a small vendor base. Keep the same definitions and the same exclusion rules so the comparison is meaningful. If a definition changes, record the change and start a new baseline rather than mixing two designs in one chart.
End each review with a decision record. The team might add a second weekly payment run, assign a backup scheduler, require a same-day selection step, or leave the process unchanged. Name the owner and the recheck date. Archive the export, the coding sheet, the review notes, and the decision. A measurement that ends without a decision becomes a recurring report that nobody uses, so the decision record is what turns the observed wait into a manageable operating choice.