TruTec Blog
Monday morning at a paving shop has a way of telling the truth fast. The crew finished two lots late Friday, the office has a stack of invoices to send, and by 8 a.m. somebody is already calling about a line item, a missed change order, or a customer name that's slightly wrong in the billing system. That's when most contractors realize accounts receivable tracking is not really a collections problem, it's a process problem that started before the invoice ever left the office.
The fix starts upstream. If the billing package is clean, the aging report is honest, and the follow-up cadence is disciplined, you spend less time arguing about money and more time getting paid on work you completed. Recent practitioner guidance puts that upstream issue front and center, with invoice accuracy and dispute prevention as leading indicators of whether receivables will move, instead of just watching late-stage symptoms like aging buckets and reminder volume. One CFO-focused benchmark sets invoice accuracy at 98 to 99.5 percent and dispute rate below 5 percent as healthy ranges, which is a strong hint that many teams are tracking the wrong end of the problem, accounts receivable KPI guidance.
Why Most Contractor AR Problems Start Before the Invoice
The worst AR days usually begin with a small field miss, not a big collections failure. A foreman sends back a completion photo without the right quantity notes, a change order never gets tied to the job ticket, or the office uses the wrong customer contact from last season's bid list. By the time the invoice hits the customer, the delay is already baked in.
The Monday Morning Failure Pattern
In contractor billing, the “collections” conversation often starts too late. If the invoice doesn't match the contract, the site records, or the customer's internal approval path, the account gets stuck in a dispute state before anyone even talks about payment terms. That's why contract-aware invoicing, daily usage checks, and tighter sales-to-billing handoff matter, because they cut off the common mismatch that turns a normal invoice into a stalled one, AR KPI and billing accuracy guidance.
Practical rule: if a customer has to ask for back-up every time, the invoice process is too loose.
A controller in a paving or striping business should think about AR as a chain, job closeout, field documentation, billing review, invoice delivery, aging review, reminder, escalation, and payment application. If one link is weak, the aging report becomes a record of internal friction as much as customer behavior. The useful question isn't just “what's overdue?”, it's “what part of this balance was avoidable?”
What You Should Fix First
Start with the invoice itself. Make sure the description matches the contract language, the units match the field notes, and any extras are captured before the invoice goes out. Then build a short pre-send check so one person confirms the backup, the contact, and the due date before release.
The goal is simple. Accurate invoices are collectible invoices. That mindset changes the whole AR conversation from chasing to preventing.
Building the Invoice Process From Job Site to Sent
The strongest contractor AR systems are built at the job site, not in the office after the fact. If the field team captures the right evidence, the office can invoice faster and defend the bill when a customer asks for proof. If the field data is sloppy, every later step gets slower.
Build the Handoff Like a Checklist
The process should move in a straight line. Job completion gets documented, photos and measurements are captured, change orders are reconciled, the customer gets a chance to verify the work, and then the final invoice goes out. That sequence sounds basic, but it's where a lot of contractors lose time because each crew, PM, or dispatcher records different details.
Use the same descriptions every time. If one crew writes “patch repair” and another writes “partial mill and overlay,” the billing team ends up translating the job instead of sending the invoice. Keep unit language consistent too, because the customer should be able to trace each line item back to a field record without a phone call.
Add One Confirmation Before You Send
A quick confirmation step saves a lot of dispute cleanup. Before the invoice is sent, one person should verify the customer name, site address, scope description, backup documents, and any approved change orders. For larger jobs, a short verification call or email with the customer contact can catch mismatches before the invoice lands in their payable queue.
Good billing is mostly disciplined repetition. The same capture steps, the same review steps, the same send steps. That's what keeps invoices from becoming arguments.
| Contractor Invoice Process Checklist | What to Capture | Common Failure Point |
|---|---|---|
| Job Completion | Signed closeout, date, location | Work marked complete before all crews are off site |
| Photo & Measurement Capture | Before, during, after photos, quantities, dimensions | Missing proof for extra work or field changes |
| Change Order Reconciliation | Approved scope changes, revised pricing | Extras billed without documented approval |
| Customer Verification | Contact name, billing address, AP requirements | Invoice sent to the wrong person or department |
| Final Invoice Sent | Correct line items, terms, backup attached | Invoice released without a pre-send review |
The practical payoff is straightforward. A contractor AR process only works if the inputs are clean. When the office starts with complete field data, the rest of the cycle gets easier to track and easier to defend.
Setting Up Aging Reports and the KPIs That Matter
Aging reports should use the actual invoice date, not an estimate or whatever someone in the office recalls on Friday afternoon. The standard buckets are current, 1 to 30, 31 to 60, 61 to 90, and 90+ days, and each invoice belongs in only one bucket based on how long it has been outstanding. If the bucket logic is loose, the report looks active but does not help anyone make a Monday decision.
Keep the Dashboard Contractor-Simple
Three numbers do most of the work: Days Sales Outstanding (DSO), Collection Effectiveness Index (CEI), and invoice accuracy rate. DSO shows how long cash sits out there. CEI shows how much receivables you collected in the period. Invoice accuracy shows whether the billing process is feeding the AR process cleanly in the first place.
Those three numbers answer different questions. DSO is the “how fast” number. CEI is the “how well” number. Invoice accuracy is the “how clean” number. A contractor can collect a fair amount and still have a messy AR book if the office keeps fixing billing defects, reworking backup, or explaining line items that should have been right the first time. That is why a collections-only view misses a lot of the friction that slows cash.
Aging reports also need a reality check on the job mix. A paving crew with change orders, retainage, and split billing does not need a generic dashboard with fifty fields. It needs a short list that shows which invoices are aging, which customers need follow-up, and which bills were built wrong before they left the office. That is the same reason the discipline behind collections KPIs for agencies translates well here. The businesses are different, but the habit of measuring a small set of useful indicators is the part worth copying.
Refresh the Report for Action, Not Decoration
The useful aging report is the one somebody touches. In a contractor setting, that means checking current invoices for exceptions, reviewing past-due buckets for action, and watching whether a customer group keeps drifting into the same delay pattern. Historical values matter too, because you need enough history to tell whether a problem is seasonal or structural, and recent guidance recommends reviewing at least six months of historical values to see trend and seasonality, AR tracking cadence guidance.
Monday test: if you cannot point to the next action for each overdue invoice within five minutes, the report is too broad.
That is the value of the dashboard. It should not just show what is overdue. It should show what needs a call, what needs backup, and what needs escalation before the balance moves into the next bucket.
Choosing the Right Tracking Cadence for Your Business
A monthly AR review is too slow for many contractors. By the time a report gets attention, a few invoices have already moved from current to past due, and the office is trying to correct a pattern that started weeks earlier. That is why cadence matters. The right rhythm catches billing mistakes and dispute signals before they turn into cash delays, and it keeps follow-up tied to the actual state of the ledger instead of last month's summary.
Use Three Layers, Not One
Weekly review should focus on aging movement, exceptions, and the accounts that need action now. Monthly review should look at trend, customer behavior, and whether the team's process is getting cleaner or noisier. Quarterly review can stay strategic, with a deeper look at who needs tighter terms, better documentation, or a different billing rhythm.
That layered cadence fits the paving business well. Work is seasonal, job sizes change, and payment behavior can look fine for a few weeks before it suddenly isn't. A monthly-only rhythm hides that kind of drift until cash flow is already under pressure.
Weekly work is where invoice accuracy gets protected. If a pay app, backup document, or change order is missing, the account can sit in the wrong bucket long enough to create a dispute that should have been prevented on day one. That is also where failed payment recovery starts to matter, because the earlier the office sees the issue, the less time it spends chasing a balance that should have been resolved at the source.
Segment by Risk, Not Just by Balance
A large, reliable account does not deserve the same follow-up plan as a smaller account that has already bounced two invoices. Segment customers by payment behavior, dispute history, and how fast they respond when the office reaches out. Then put the riskiest accounts on the shortest review cycle.
A simple Monday routine can stay under thirty minutes if the list is clean. Look at new invoices, check anything that crossed into the next aging bucket, and flag the accounts that need owner involvement or backup before noon. If no one is assigned to the exception, the exception becomes the new normal.
Weekly visibility does not replace monthly reporting. It keeps the monthly report from turning into a postmortem.
Reminders, Escalation, and Customer Conversations That Get Paid
The best reminder workflow is calm, specific, and boring in the right way. A contractor doesn't need a dramatic collections script. The customer needs a clear next step, the invoice number, and a documented reason to act.
Use a Four-Touch Sequence
At due date, send a friendly reminder by email, and keep it short. At seven days past due, follow up firmly and include the invoice copy plus any backup. At thirty days, send a final notice that names the overdue balance and asks for a response by a specific date. At sixty days, escalate to the owner or senior contact who can resolve the issue.
| Touchpoint | Day Offset | Channel | Tone |
|---|---|---|---|
| Friendly Reminder | Due Date | Email or portal message | Helpful and direct |
| Firm Follow-up | 7 Days Past Due | Phone or email | Clear and professional |
| Final Notice | 30 Days Past Due | Email and phone log | Firm and specific |
| Escalation | 60 Days Past Due | Owner call or formal notice | Serious and documented |
Here's a simple reminder line you can adapt, “Just a friendly reminder that invoice #____ is now due. Please let me know if you need backup or if AP needs anything from our side.” A firmer follow-up can say, “I'm following up on invoice #____, which is now past due. If there's a dispute, send it over today so we can resolve it quickly.”
Match the Channel to the Situation
Email works for most routine touches because it leaves a paper trail. Phone calls help when the customer says they never saw the invoice or when AP needs a direct answer. Text can work for trusted contacts on smaller maintenance accounts, but it should be used carefully and logged like any other touchpoint.
If the issue is a dispute, don't keep chasing as if it's a slow pay. Pull the invoice, line up the backup, and resolve the billing question first. For a useful reference on failed payment recovery workflows, the logic in Suby's dunning process overview maps well to the kind of structured follow-up that contractors need, even if the business context is different.
Log every touchpoint. If a customer says nobody called, the record should settle it.
Retention on multi-phase work deserves its own line in the system too. If retainage isn't tracked separately, it gets lumped in with normal receivables and forgotten until someone is scrambling to collect it later.
Automation and Integrations Without Overbuilding
Automation should remove repetitive work, not create a software project the office can't keep up with. A five-crew paving company doesn't need the same stack as a regional contractor with multiple divisions, but both need clean invoices, reliable reminders, and clear payment status. The right question is which layer fits the volume and complexity you have.
Match the Stack to the Job
A spreadsheet plus email can work when invoice volume is light and the same people handle billing every week. Accounting software with built-in AR gives you better control over aging, reminders, and cash application without much setup drama. Full estimating-to-invoicing platforms add more value when job data, measurements, photos, and line items need to move together without manual re-entry.
The biggest gain comes when the field information flows into the invoice automatically. If measurements, takeoff outputs, or job photos can populate line items directly, the customer sees exactly what they're being billed for, and the office spends less time translating field notes. That's also where a platform like TruTec can fit, since it can turn site photos and aerial imagery into takeoff-style outputs and connect field documentation to the billing conversation without requiring the office to rebuild the record by hand.
Automate the Repetitive Parts First
Automatic invoice delivery is usually the fastest win. Scheduled reminder emails are another easy step, especially if they pull the correct invoice number and due date every time. Payment links can also reduce friction when a customer is ready to pay and just needs a direct path.
The things that are often overbuilt early are custom approval chains and complicated dashboards nobody reviews. A contractor is usually better off with a simpler system that invoices on time, sends reminders on schedule, and shows the team which accounts need human intervention. If the software takes more time to manage than the old process, it's not automation, it's another job.
Internal integration matters too, especially if your estimating, dispatch, and billing data live in separate places. A well-connected workflow prevents the office from chasing missing details after the work is done, which is where many AR delays begin, construction software integration guidance.
Common Pitfalls and How to Fix Them
Most contractor AR problems look like customer behavior from a distance, but the root cause is often internal. The wrong contact is on file, the change order never got billed, or the office lost track of retainage and kept chasing the wrong balance. When the invoice package is weak, slow payment gets blamed on the customer even when the office handed them a reason to delay.
Fix the Source, Not Just the Symptom
Wrong customer contact on file. The symptom is invoices sitting untouched while AP says nobody sent them anything. The fix is to verify and update billing contacts before every project starts, then confirm the delivery path before the first invoice goes out.
Missing change orders. The symptom is a customer saying the price doesn't match the scope. The fix is to keep change approvals tied to the job record and bill them as soon as they're approved, not at the end of the month.
No retention tracking. The symptom is a healthy-looking aging report that still has money trapped in holdback. The fix is to separate retainage from standard receivables so it doesn't disappear into the rest of the balance.
Commingled personal and business finances. The symptom is a messy cash picture and unclear support for what was billed. The fix is to keep business receipts, job costs, and owner spending separated so AR and bookkeeping aren't guessing at the same time.
Inconsistent follow-up. The symptom is one account getting three reminders and another getting none. The fix is to assign a cadence, log every touch, and make the reminder workflow part of the job, not a favor somebody does when they have time.
A healthy AR system doesn't need heroic collection calls. It needs clean billing, visible aging, and follow-up that happens the same way every time.
If those five areas are under control, the collection conversation gets a lot easier. If they're not, the aging report will keep telling the same story in different weeks.
If your team is still spending Monday morning untangling disputed invoices, stale contacts, and missing backup, TruTec can help tighten the front end of the process with photo-driven documentation, takeoffs, and customer-facing outputs that support cleaner billing. Visit TruTec to see how a better field-to-office workflow can make accounts receivable tracking easier to run and easier to trust.