Quick Answer: Aging reports date a claim from its most recent submission. Rebill a claim during a dispute and its official age resets to zero, so a five-month fight can sit in the 0-to-30-day bucket looking fresh. In one 18-month claims investigation, payments at more than two dozen carriers routinely arrived before the claim’s latest submission date, which is proof of rebilling after payment and resubmission during disputes. Filing and appeal deadlines do not reset with the report. The aging can look current while the money runs out of time.
You run the aging report every month, and the 90-plus bucket is the one you worry about. Reasonable. But the report is answering a different question than the one you are asking. You want to know how long you have been fighting for each dollar. The report tells you how long it has been since somebody last touched the claim. Those are the same number only if nobody ever resubmits anything.
In a claims investigation for a nationwide practice, written up in full in Your Claims Went Somewhere. Nobody Could Say Where., we put payment dates next to submission dates and found claims paid before they were submitted. Read that again: paid before submitted. At more than two dozen carriers this was routine, and there is only one way it happens. Claims were being rebilled after they were already paid, or resubmitted again and again during disputes, and each resubmission stamped a new date on the claim and reset its official age.
We were not hunting for this. It fell out of a consistency check, the kind of thing you run to make sure the data is assembled right, because no payment should predate its own claim. When the check lit up at carrier after carrier, the first assumption was a data error. The data was fine. The reporting convention was doing exactly what it was designed to do, at a practice where disputes had turned resubmission into a habit.
We have seen where that road ends. One claim was submitted 18 times before anyone asked why. The resubmission treadmill is its own problem, but it does something quieter along the way: it launders the age of every claim on it.
The claim that looks 20 days old and is two weeks from dead
Deadlines run on the contract’s clock, not the report’s. Timely filing windows run from the date of service. Appeal windows run from the date of the denial. Neither one resets because your team dropped the claim again last Tuesday.
So a claim can show 20 days old on the aging report and be two weeks from unappealable. In the practice above, the under-60 buckets were understated across the worst carriers, which meant the freshest-looking part of the report was hiding the practice’s oldest, most fought-over money. Leadership was staring at the 90-plus bucket while the real fires wore a 0-to-30 label.
The cruelest version is the appeal window. A denial arrives, the team rebills instead of appealing, the rebill denies again, and the claim looks busy the whole time it is bleeding out. Activity reads as progress on a report that only measures touch.
Nobody falsified anything. The report dates claims the way it dates claims, the team resubmitted claims the way disputes require, and the two behaviors combined into a report that answers the wrong question with full confidence.
How to find your real ages in ten minutes
Two checks, both runnable against data you already have.
First, compare each open claim’s first submission date to its current aging bucket. A wide gap marks the resubmission treadmill, and the size of the gap is how much older the claim really is than the report admits.
Second, scan for payments dated before the claim’s most recent submission. Every hit is a claim that was rebilled after it was paid, which costs rework on your side and goodwill on the carrier’s, and inflates your submission counts for nothing.
Sort both lists by dollars. The top of each list is where a filing or appeal deadline is quietly closing on money you think is fresh.
Knowing the real ages changes the Monday meeting. The question stops being why the 90-plus bucket is growing, which has no owner and no answer, and becomes which disputes have run longest and which deadlines close this month. A person can work that list, ranked by dollars and days remaining.
Book a 30-minute look. You’ll see your claims’ real ages next to the ages your report shows.
Questions people ask
Why is my AR aging report inaccurate?
Because it dates each claim from its most recent submission. Every resubmission during a dispute resets the claim’s official age, so long-fought claims migrate back into the young buckets. The report is behaving as designed. It measures time since last touch, and long disputes get touched constantly.
Does resubmitting a claim reset its age?
On the aging report, yes. Each resubmission stamps a new date and moves the claim back toward the 0-to-30 bucket. The claim’s real age, measured from date of service or first submission, keeps running. The gap between the two numbers grows with every rebill.
Do filing deadlines reset when a claim is resubmitted?
No. Timely filing runs from the date of service and appeal windows run from the denial date, per your carrier contract. Resubmission changes the aging report’s date, and only that. A claim can look fresh on the report while its contractual deadlines keep closing.
How do I find claims that are older than they look?
Compare first submission dates to current aging buckets and flag wide gaps. Then scan for payments dated before the latest submission, which marks claims rebilled after payment. Sort both lists by dollar amount. In one investigation this pattern was routine at more than two dozen carriers.