Blog › First-pass acceptance: the billing metric to track

First-pass acceptance: the billing metric commercial contractors should track

First-pass acceptance shows how often your invoices are accepted the first time you send them. Here is how to define it, measure it and act on it.

· 6 min read · By Closebill

Aerial view of a retail building roof with several rooftop HVAC units

What first-pass acceptance means

First-pass acceptance answers one question: when you send a customer an invoice for the first time, how often do they accept it as it is?

The definition that holds up best is:

First-pass acceptance = first submissions accepted without being returned ÷ first submissions that have been decided (accepted or returned)

Two parts of that definition matter.

First submissions only. If an invoice is rejected and you fix it and resubmit, the resubmission does not count as a new first pass. Otherwise every fixed invoice would improve your score.

Decided only. An invoice sitting in a customer's portal with no decision yet has neither passed nor failed. If you count pending invoices as accepted, your rate looks better than it is in a month with lots of recent submissions. If you count them as failed, it looks worse. Leave them out until the customer decides, then add them to the month they were submitted.

Some customers short-pay rather than reject. Decide up front how you will treat a short payment, write it down, and apply it the same way every month. Treating it as a return is the stricter choice and usually the more useful one.

Why this metric matters

Owners of commercial service businesses usually watch revenue, gross margin and days sales outstanding (DSO). DSO tells you that cash is late. It does not tell you why. An invoice can be late because the customer pays slowly, or because you sent it late, or because it bounced twice before it was accepted. Only the last two are fully in your control.

Uneven cash flow is common in small firms. In the Federal Reserve's 2026 Report on Employer Firms, from the Small Business Credit Survey, 50% of employer firms said uneven cash flow was a financial challenge in the prior 12 months, and the survey counts collecting on receivables as part of that. First-pass acceptance is a way to see how much of that problem starts in your own billing office.

It is also a fair measure for the billing team. Unlike DSO, it reflects the quality of what they send, not how quickly the customer's AP department works.

How to measure it from your own records

You need one row per invoice for a period, say the last 90 days. Most of the data is already in your field-service or accounting system, and the rest is in your customers' portals or email.

For each invoice, collect:

  • Customer
  • Your job number and the customer's work order or PO number
  • Date the job was completed
  • Date the invoice was first submitted
  • Invoice value
  • Outcome of the first submission: accepted, returned, or pending
  • If returned: the date and the customer's stated reason
  • If returned: minutes spent fixing it, estimated by the person who did the work

The outcome and reason are usually the hardest parts to find. Portals usually show a status history. Where customers return invoices by email, search the billing inbox for the job numbers. If you cannot find an outcome for older invoices, start the measure from today and build up the history going forward.

MeasureHow to calculate itWhat it tells you
First-pass acceptanceAccepted first submissions ÷ decided first submissionsHow often invoices are right the first time
Returns by reasonCount of returned first submissions, grouped by reasonWhich check to add or fix next
Days from completion to submissionMedian of (first submission date − job completion date)How long finished work waits before it is billed
Minutes of reworkTotal minutes spent fixing returned invoices, and minutes per returnThe staff time returns cost you
Value waitingSum of invoice value for completed jobs not yet submitted because something is missingCash held up in your own office

Use the median for days to submission rather than the average. One job that waited 200 days for a missing PO will drag an average up and hide what usually happens.

Returns by reason connects directly to prevention. If most returns at one customer are for missing photos, the fix is on the technician side; see our guide to signed service reports. If they are for PO problems, see PO numbers on FM invoices. Our list of common rejection reasons gives a starting set of reason codes.

How to set up a simple spreadsheet

Create one sheet called Invoices with these columns:

ColumnContents
A: CustomerCustomer name, spelled the same way every time
B: JobYour job number
C: CompletedJob completion date
D: SubmittedFirst submission date
E: ValueInvoice value
F: OutcomeAccepted, Returned or Pending (use a dropdown)
G: ReasonReturn reason from a fixed list (use a dropdown)
H: Rework minutesMinutes spent fixing, if returned
I: Days to submit=D2-C2

Then build a summary on the same sheet, starting in column K, with one row per customer: K holds the customer name, and L to P hold the numbers. For the first customer, in row 2, these formulas work in Google Sheets and current versions of Excel:

  • L, accepted: =COUNTIFS(A:A,K2,F:F,"Accepted")
  • M, returned: =COUNTIFS(A:A,K2,F:F,"Returned")
  • N, first-pass acceptance: =L2/(L2+M2), formatted as a percentage
  • O, rework minutes: =SUMIFS(H:H,A:A,K2)
  • P, median days to submit: =MEDIAN(FILTER(I:I,A:A=K2,D:D<>""))

Pending invoices drop out of the rate automatically, because the formula only uses Accepted and Returned. Add a row for all customers together, and a column for the month so you can see the trend.

Keep the reason list short, around eight to ten reasons, and agree what each one means. "Paperwork" is too broad to act on; "service report unsigned" and "after photos missing" are specific enough to fix.

Reading the numbers

  • Look by customer first. Each customer has its own rules. A company-wide rate can look acceptable while one large customer returns a third of what you send.
  • Weight by value as well as count. Ten small returns may matter less than one large project invoice stuck for a month.
  • Watch for gaming. If people are measured on first-pass acceptance alone, invoices may be held back until they are perfect. Track days to submission alongside it so speed and accuracy are seen together.
  • Review monthly with the billing lead and an operations lead. Many fixes, such as photos and signatures, sit with the field team, not the office.

A monthly routine

  1. Update outcomes for invoices that were pending last month.
  2. Calculate first-pass acceptance, returns by reason, median days to submit and rework minutes per customer.
  3. Pick the top return reason at the customer with the most returned value.
  4. Agree one change to prevent it, and who owns it.
  5. Check next month whether that reason went down.

Closebill's scorecard reports these same measures, first-pass acceptance on decided first submissions, returns, median days from completion to submission and blocked value, from the jobs it checks. See the product.

Get a baseline from your last 30 jobs

If you do not have the history to calculate this yourself, we can build it for you from a batch of jobs. Book a job review and we will check 30 consecutive completed jobs, list the confirmed blockers and estimate the minutes of rework per job.