Offshore BookkeepersPowered by StealthAgentsPlan my role

Payables & Expenses

Vendor payment timing reports for small accounting teams

A method note on vendor payment timing reports, covering what to record, how to read the results, and the limits of a timing measure.

A method note on vendor payment timing reports, covering what to record, how to read the results, and the limits of a timing measure.
Table of contents

Key takeaways

  • Measure from invoice receipt and approval, not from the invoice date alone.
  • Separate on-time payment from early payment and from payment after a hold.
  • Report counts and days, not a single average.
  • Use the pattern to fix approval bottlenecks, not to rank vendors.

A vendor asks why an invoice was paid late. The accounts payable report shows the invoice date and the payment date, and the gap looks like a delay. The invoice sat in the client's approval queue for two weeks, and the report does not show it.

A vendor payment timing report is useful when it separates the parts of the cycle. It is misleading when it compresses them into one number. This method note describes what to record and how to read the result without overclaiming.

Define the measurement points

Record at least three dates: invoice received, invoice approved, and payment issued. The gaps between them describe different processes, and combining them hides where the time goes.

The invoice date can be added as a reference, but it should not be the starting point for the team's performance. The team does not control when the vendor issues the invoice.

Separate on-time, early, and held

An invoice paid before terms is early, not on time. An invoice held for a dispute is not late in the same sense as one that was simply missed. Each category needs its own count.

Without the separation, the report averages unrelated cases and produces a number that no one can act on. The categories also protect the team from being blamed for a hold the client requested.

Use terms that are written down

On-time is defined by the client's agreed terms. If the terms are not recorded, the report should say so rather than assume a standard.

Where terms differ by vendor, record the term beside the result. A single on-time percentage across mixed terms is not comparable, and it will be challenged the first time a vendor asks for the basis.

Report counts and days

Report the number of invoices in each category and the median days for each stage. A single average hides the slow cases, which are the ones that generate complaints.

Include the slowest cases in the summary, with the stage where they waited. A list of five slow invoices with reasons is more useful than a percentage that no one can trace.

Find the bottleneck

Group the results by stage: receipt to approval, approval to payment, and payment to clearance. A cluster in one stage points to a specific fix, such as a missing approver or a payment run schedule.

A cluster spread across stages suggests a capacity or data problem. The report should support that diagnosis rather than imply that the team is slow in general.

What the report cannot show

The report cannot show whether the vendor's invoice was correct, whether the goods were received, or whether the client was satisfied. Those questions belong to the invoice review and the business relationship.

It cannot prove that a late payment was avoidable. A hold for a disputed amount is a legitimate reason, and the report should record it as such rather than as a delay.

Invoice receipt and approval data

The receipt date is often missing from the invoice record. When it is, the timing report starts at the invoice date and assigns transit time to the team.

Ask the client to log the receipt date at the mailbox or the intake queue. A single field turns the report from an estimate into a record of the team's actual cycle.

Payment runs and bank clearing

A payment issued on the due date may clear the bank two days later. The timing report should say whether it measures issuance or clearance, and keep that choice consistent.

For vendor conversations, issuance is usually the relevant date. For cash forecasting, clearance matters more. Reporting both, where the data allows, prevents the same number being used for the wrong purpose.

Disputes and holds

A disputed invoice is not a late payment in the ordinary sense. Record the hold, the reason, and who lifted it. Without that field, the report will attribute the delay to the payment team.

The same applies to invoices waiting on a purchase order or a goods receipt. The stage where the invoice waits is the finding, not the total days.

A worked example

A report shows a median of 31 days from invoice date to payment against 30-day terms. The number looks like a one-day miss. The stage data shows receipt took two days and approval took eighteen.

Payment issued on day thirty-one. The problem is approval, not payment. A report built only on invoice and payment dates would have pointed at the wrong team.

Vendor communication

Share the timing summary with vendors only after the categories are agreed. A vendor who sees a single average will read it as a promise, and the exceptions will look like excuses.

Where a delay is caused by a dispute, tell the vendor directly. The report is an internal tool; the conversation is the relationship.

Reporting cadence

Run the report monthly and review it quarterly with the client. Monthly data shows the operational pattern; a quarterly conversation allows a process change to be judged.

At each review, compare the same categories and the same stages. A report that changes shape every month cannot show whether a fix worked.

Data quality checks

Check for missing receipt dates, invoices recorded twice, and payments matched to the wrong invoice. These defects distort the stage times and are common in small teams.

Record how many records were excluded and why. A report with a large excluded share is not a measurement of the process; it is a measurement of the data.

Vendor terms and discounts

Short terms and early-payment discounts change what on time means. Record the term and whether a discount was taken, because a payment that captures a discount is early by design.

A report that ignores discounts will show avoidable early payments and may prompt a policy change that costs the client money. The terms belong in the record, not in a separate note, and they should be reviewed whenever a vendor changes an agreement.

What to do with the slow cases

List the slowest invoices each month with the stage where they waited and the reason. A short list is actionable; a percentage is not.

Assign a follow-up for each item that is still open. The next report should show whether the item moved, and the reviewer should be able to see the owner.

Methodology and limits

This note is an operating design informed by public guidance on internal control, recordkeeping, and small-business operations. It does not report an empirical study or establish a target payment time.

The fields were tested against common cases in small accounting teams: a clean invoice, a missing purchase order, a disputed charge, a scheduled payment run, and a vendor with short terms. The design favours a small number of dates that are consistently available.

Conclusion

A vendor payment timing report is useful when it separates receipt, approval, and payment, and when the categories reflect the reason for the timing. It is misleading when it reduces the cycle to one average. Used carefully, it shows where the process waits and what to fix.

Listed sources

  1. U.S. GAO, Standards for Internal Control in the Federal Government
  2. IRS, Recordkeeping
  3. U.S. Small Business Administration, Manage your business

Related research