Timely filing is a write-off schedule
Most of what goes wrong in follow-up is recoverable later. A claim worked in the wrong order still gets worked. A denial misread is read again. Timely filing is the exception: past the deadline the money is gone, and no amount of subsequent effort brings it back.
That makes the filing deadline the only hard constraint in the whole process, and it is worth managing as one.
There is more than one deadline
Operations that track timely filing usually track the initial one — how long you have from the date of service to submit the claim. Medicare requires a claim to be filed within one calendar year of the date of service (42 CFR 424.44). Commercial contracts vary widely and many are considerably shorter.
The second deadline is missed more often. After a denial, the window to appeal or request reconsideration usually runs from the remittance date rather than the date of service, and it is usually much shorter than the filing window. A claim can be comfortably inside its filing limit and already out of time to dispute the decision it received.
The third sits on secondary claims. Where a secondary payer's clock starts at the primary payer's remittance, a slow primary consumes none of the secondary window — but a slow post of that remittance consumes all of it. The claim can be correctly aged and correctly filed and still expire, because nobody started the second clock.
Three deadlines, three different start dates, and only the first is a property of the claim's age.
The report does not show it
An aging report counts days elapsed. A deadline is days remaining. The conversion is not a subtraction from one constant, because the limit differs by payer, by contract, sometimes by plan within a payer, and by which of the three clocks applies.
Which is exactly why it is worth computing once and storing, rather than recomputing in someone's head each time a claim is picked up. A worklist that can be sorted by days remaining puts the irreversible losses at the top — the only sort order that reflects what is actually at stake.
Proof matters as much as the deadline
A claim submitted inside the window is not the same thing as a claim you can demonstrate was submitted inside the window. When a payer's position is that nothing arrived, what settles it is your own dated record: when the claim was first sent, when it was sent again, what each response was, and when each of those happened.
That record has to exist before it is needed, and it has to have been written at the time. Reconstructed evidence is worth much less, and reconstructing it is expensive at precisely the moment you can least afford the time — near a deadline, on a claim already in dispute.
This is the most under-appreciated reason to record every touch with its date and its outcome. Most of the value of that record is not operational. It is evidentiary, it is claimed rarely, and when it is claimed it is the difference between a paid claim and a write-off.
What to do with it
Three practices, none of which requires anything new:
- Store the limit per payer and per contract, not as a company-wide default. A single default is wrong for every payer it does not describe, and it is wrong in the dangerous direction for the shortest ones.
- Sort at least one worklist by days remaining. Not necessarily the main one — but if nothing is ever sorted this way, the claims closest to permanent loss are being worked in balance order like everything else.
- Count the claims that expire. By payer, by reason, and by whether they were ever touched. A claim that expired untouched is a capacity problem. A claim that expired after four touches is a process problem. They have different fixes and they look identical on a write-off report.
The deadline is the one part of the revenue cycle where doing the work late is identical to not doing it at all. Everything else in follow-up is a question of cost and probability. This one is a question of whether the claim still exists.