A practical playbook for IA firm owners and claims managers: how to standardize terms, bucket your receivables, and tell slow-paying carriers from stalled invoices, whether you run it in a spreadsheet or a single operating system.
When your firm bills one carrier, aging is simple: an invoice is either current or it is overdue. When you bill a dozen carriers, it stops being simple. Each carrier has its own payment terms, its own billing contact, and its own rhythm that shifts after a storm. The same "60 days outstanding" can be perfectly normal for one carrier and a red flag for another. Without a consistent way to track it, your real receivables picture lives in your head and in a spreadsheet that was already stale when you saved it.
The cost of that blur is quiet but real. Completed work goes uninvoiced. Invoices that were sent never get followed up. A carrier that genuinely lost your invoice looks identical to one that simply pays slowly, so nobody calls until the receivable is months old and the claims contact who could have fixed it has moved on.
Tracking invoice aging well is less about software and more about discipline: a consistent definition of "outstanding," consistent buckets, and a consistent cadence for reviewing them. The steps below are tactics you can apply today, even in a spreadsheet. At the end, we cover how a single-view system removes the manual upkeep so the picture stays current on its own.
Work through these in order. Each one removes a source of ambiguity that makes multi-carrier receivables hard to read.
Aging is only comparable if every invoice starts its clock the same way. Pick one anchor and use it everywhere: the date the invoice was sent to the carrier, not the date the claim closed or the date you drafted the invoice. Then record each carrier's stated payment terms next to that date.
An invoice can only age once it exists. The most expensive receivables problem is work that was completed but never billed, so it never enters the aging report at all. Before you can track aging across carriers, you need a reliable list of closed or completed claims that have not yet been invoiced.
Once invoices are sent, sort them by days outstanding into standard buckets: current, 1-30, 31-60, 61-90, and 91-120+ days. Buckets turn a long list of invoices into a shape you can read at a glance, and they make the trend obvious as balances slide from one bucket to the next over time.
This is the step generic accounts-receivable tools miss. A raw age number is not enough; you have to read it against the carrier it came from. Compare each overdue invoice to that carrier's normal pattern from step one. A carrier that usually pays in 45 days sitting at 50 is slow but expected. The same carrier at 120+ days is an exception worth escalating.
An aging report that nobody owns is just a record of money you are not collecting. Every overdue invoice past a threshold should have a named person responsible for the next action and a date for that action. Ownership is what converts visibility into collected cash.
Receivables drift when review is occasional. Put aging on a calendar: a quick weekly look at new exceptions and a deeper monthly review of the full aging by carrier. The cadence matters more than the tool, because a stale report and no report are nearly the same thing.
You do not need software to begin. A disciplined sheet captures most of the value, and shows you exactly where the manual upkeep gets painful.
Columns for carrier, claim number, send date, amount, days outstanding, bucket, owner, and last action. One row per invoice keeps the math simple and lets you pivot by carrier or by bucket whenever you need a rollup.
Let the sheet compute days outstanding from the send date so the bucket updates itself when you reopen the file. The bucket column should follow from that number, not be typed by hand, or it will drift out of date.
The sheet is only as current as the last time someone updated it. Send dates get entered late, paid invoices linger, and unbilled work never makes it onto the list at all. The discipline is real work, and it competes with the next assignment.
Every step above stays accurate only if someone keeps it accurate. That is the part a single operating view removes. FileRidge ties each invoice to the claim and carrier it came from, ages it automatically from the send date, and rolls everything into one accounts-receivable view across all the carriers you bill. Set each carrier's fee schedule and terms once and invoices generate from the claim, so unbilled work surfaces instead of hiding, and aging buckets update on their own. The method is the same; the manual upkeep is gone.
Most firms use current, 1-30, 31-60, 61-90, and 91-120+ days, measured from the date each invoice was sent to the carrier. The buckets themselves matter less than applying them consistently to every invoice and reading them against each carrier's normal payment pattern, so you can tell a routine slow-pay from an invoice that has actually stalled.
Measure from the date the invoice was actually sent to the carrier, not the date the claim closed or the date you drafted the invoice. The send date is when the carrier's payment clock starts, so it is the only date that lets you compare an invoice fairly against the carrier's terms and typical pay cycle.
Yes. A spreadsheet with one row per invoice and columns for carrier, claim, send date, amount, days outstanding, and owner will work, and the tactics in this guide apply directly to it. The limitation is that the sheet is manual and goes stale the moment work moves on, which is why firms eventually move aging into a system that ties each invoice to its claim and ages it automatically.
We'll walk through how your firm bills today, where invoices age across carriers, and how FileRidge keeps unbilled work, aging buckets, and follow-ups in one view that stays current on its own.
Related: Receivables & invoice aging · How to reconcile receivables by adjuster · IA firm software · Pricing