Billing Lag: The Days Before the Invoice That DSO Misses
Payment terms start when the invoice goes out, not when the work is done. Here is how a 3 to 5 person AR team can measure billing lag, find where it comes from, and take days out of delivery-to-cash.

Pratheek Adi
Co-Founder & CTO

Table of contents
Share
Your customer's payment clock does not start when the job is finished or the order ships. It starts when the invoice lands. Every day between the two is a day of free credit you gave away without deciding to, and most AR dashboards never show it.
That gap is billing lag. For a team already fighting late payers, it matters: Atradius' 2026 North America survey found US businesses make 45% of their B2B sales on credit terms, and that late payments affect an average of 23% of B2B receivables in the region. Your collectors work hard on the days after the due date. Billing lag adds days before the terms even begin.
Billing lag is the number of days between the moment you earn the right to bill and the date the invoice reaches the customer. It does not show up in DSO, because DSO only counts invoices that already exist. Measure it per invoice, find the handful of causes behind most of it, and give each cause an owner. This guide shows a 3 to 5 person AR team how.
What Is Billing Lag?
Billing lag is the time from billable event to invoice delivered. The billable event is whatever your contract says lets you bill: a shipment, a completed service call, a signed delivery ticket, a month of service, or an approved milestone. If the work was done on the 3rd and the invoice reached the customer on the 17th, your billing lag on that invoice is 14 days.
Billing lag versus DSO
DSO measures how long it takes to collect invoices once they are on the books. Our guide on how to calculate DSO walks through the formula. Billing lag sits upstream of it. A team can report a healthy 42 day DSO while customers wait two weeks for invoices, because unbilled work never enters the receivables balance.
Billing lag versus days delinquent
Average days delinquent tells you how far past the due date customers pay. Billing lag tells you how late the due date was set in the first place. Read our explainer on average days delinquent for the collection side. Put the two together and you see the full delay from work done to cash in.
Why Doesn't DSO Show Billing Lag?
DSO is built from invoiced receivables and revenue. Work that has not been invoiced is not in accounts receivable, so it cannot slow DSO down. In some ERPs it sits in unbilled receivables or a contract asset account. In others it sits nowhere until someone creates the invoice.
A worked example
Take a distributor with net 30 terms. A shipment goes out on March 1. The invoice is created on March 9 after the packing slip comes back, and emailed on March 11 with the next billing run. The due date is April 10. The customer pays on April 15. DSO for that invoice counts 35 days, from March 11 to April 15. The real delay from shipment to cash is 45 days, and 10 of those days happened before collections had anything to collect.
Why the AR team should care
The days are invisible on the dashboard, but they are not invisible to the customer. A late invoice looks careless, invites questions about what it covers, and lands after the customer's AP team has closed the month. Late invoices also arrive in bunches, which piles work onto your collectors at the same time every month.
How Do You Measure Billing Lag?
Measure it per invoice, then roll it up by customer, by billing type and by the person or team that prepares the invoice. Averages hide the problem. A median of three days can sit next to a long tail of invoices that took three weeks.
The three dates you need
You need the billable event date, the invoice date and the date the invoice was sent or uploaded. Most ERPs store the invoice date. The event date usually lives on the sales order, the shipment, the timesheet or the job. The sent date lives in your email log or the customer's portal confirmation.
The formula
Billing lag in days equals the invoice sent date minus the billable event date. Track the share of invoices sent within two business days as a second measure. A median tells you how most invoices behave. The two business day share tells you whether the long tail is shrinking.
Where the dates live in common systems
In NetSuite, compare the item fulfillment date with the invoice date and the email sent date on the transaction. In QuickBooks Online, compare the delivery or service date field with the invoice date and the sent status. In Business Central and Sage Intacct, compare the posted shipment or project task date with the posting date of the sales invoice. If the event date is not stored anywhere, start by adding it as a required field on the order.
Start with last quarter
You do not need a new report to begin. Export last quarter's invoices with their event dates, calculate the lag for each one in a spreadsheet and sort from longest to shortest. The top 50 invoices on that list will show you which causes and which customers to look at first.
Where Does Billing Lag Come From?
Most billing lag comes from a short list of causes, and each one has a different owner. The table below is a starting point for a cause review.
Cause | What it looks like | Usual owner | First fix |
|---|---|---|---|
Missing proof of delivery | The invoice waits for a signed ticket or packing slip | Operations or warehouse | Attach the signed ticket before the job closes |
Missing PO or approval | Billing waits for the customer's PO number | Sales or account manager | Collect the PO before work starts |
Unpriced extras | Extra work waits for a price and approval | Project or service manager | Bill the base work now and extras once approved |
Batch billing runs | Finished work waits for the weekly or monthly run | Billing | Bill completed work daily |
Timesheet approval | Service invoices wait for approved hours | Field supervisor | Set a weekly timesheet approval cutoff |
Wrong contact or portal | The invoice is sent but never received | AR or billing | Confirm the contact and the portal upload |
Pick the two causes behind the most lagged invoices and fix those first. A single rule, such as no shipment closes without a signed delivery ticket attached, can remove more lag than a full process redesign.
Missing backup
When AP needs a proof of delivery, a timesheet or a PO number to approve the invoice, billing waits until it has them. Our guide to invoice backup documentation lists what each type of customer usually asks for.
Change orders and extras
Extra work agreed in the field often waits for a price and an approval. Bill the base work on time and the extra separately once approved. Our change order billing guide covers how.
Batch billing runs
A weekly or end-of-month billing run means work finished the day after the run waits up to a week or a month. Daily billing for completed work removes this cause at no cost.
How Can Your AR Team Cut Billing Lag?
Set a target, give every cause an owner and review the lagged invoices every week. The AR team does not own every step of billing, but it owns the result, because it is the team that waits for the cash.
Set a billing standard in writing
Write a standard into your collections policy: invoices go out within two business days of the billable event, with the backup the customer requires. Name who prepares each billing type and who approves exceptions.
Bill daily, not in batches
Move completed work to a daily billing run. For recurring service, bill on the first business day of the period. For milestone work, bill on the approval date, not the next month-end. Our list of month-end close failure points shows how batch habits drift into the close.
Fix the handoff from operations
Most lag starts outside finance. Agree one trigger with operations, such as a completed job status or a signed delivery ticket, that tells billing the work is ready. Then report the lagged invoices back to the operations manager each week, by name and by job.
Get the invoice into the right place
An invoice emailed to the wrong address or never uploaded to the customer's portal has a lag that never ends. Keep billing contacts current and confirm the portal upload. Our guide to supplier portal invoicing covers the portal side.
What Should You Track Each Week?
Keep the scorecard short. Three numbers are enough to see whether billing lag is shrinking. Add them to the AR KPIs you already review.
Median billing lag
The median days from billable event to invoice sent, overall and by billing type. It tells you how a normal invoice behaves.
Share sent within two business days
The percentage of invoices sent within your standard. This is the number to put in front of operations.
Unbilled work older than five days
The count and value of completed work with no invoice after five days. This list is the action list for the week.
Where Does Abivo Fit?
Abivo's AI collections agent, Kate, works from the moment an invoice exists. Kate sends reminders before the due date, follows up by email and phone when an invoice slips, asks for a payment date and records every answer against the account. When customers say they never received an invoice or are missing backup, Kate logs that reason, which gives your team a clear list of billing fixes instead of guesses. Your collectors spend their time on disputes and key accounts, and the lever in our guide to lower DSO without hiring stays in your hands. To see how it would work with your customers, visit Get Started.
Practical Takeaways for Controllers and AR Managers
Billing lag is the time from billable event to invoice delivered, and DSO does not show it.
Measure it per invoice with three dates: event, invoice and sent.
Track the median and the share of invoices sent within two business days.
Fix the two causes behind most lagged invoices before redesigning anything.
Move completed work to a daily billing run.
Report lagged invoices to operations every week, by job.
Frequently Asked Questions
What is billing lag in accounts receivable?
Billing lag is the number of days between the billable event, such as a shipment or a completed job, and the date the invoice reaches the customer. It delays cash before payment terms even start.
Does billing lag affect DSO?
Not directly. DSO counts invoices that already exist, so days spent before the invoice is created do not appear in it. Billing lag delays cash all the same, which is why it needs its own measure.
What is a good billing lag?
Most AR teams aim to send invoices within one to two business days of the billable event. Track the share of invoices that meet your standard, not only the average.
How do I find the cause of billing lag?
Pull every invoice sent more than five days after the event in the last quarter and note the reason for each one. A short list of causes, such as missing backup or batch billing, usually explains most of them.
Who should own billing lag?
Billing usually sits in finance, but the trigger often sits in operations. Give the AR or billing lead ownership of the number and agree the trigger with operations in writing.







