.png)
ABA accounts receivable: working aging without losing claims
Claims don't age because they're hard. They age because nobody owns them.
A claim sitting at 90 days is almost never a claim someone tried three times to collect. It's a claim that got submitted, didn't pay, and never got assigned to a human with a date attached. ABA accounts receivable follow-up is mostly an ownership problem dressed up as a volume problem.
The fix isn't working faster. It's making sure no open claim exists without a next action and a next follow-up date.
What every AR record needs
An aging report tells you a claim is old. It doesn't tell you what to do about it, which is why aging reports get printed and then ignored.
Payer and plan
Claim number and date of service
Claim amount and amount outstanding
Aging bucket
Claim status with the payer, not just in your system
Last contact date and what was said
Next action
Next follow-up date
Owner
Timely filing deadline
Resolution and history
Last contact date and next follow-up date are separate fields for a reason. One records history, the other creates work. A system with only the first produces reports. A system with both produces payments.
Bucket discipline
Aging buckets are useful only if each one means something different operationally.
0 to 30 days is monitoring. Most payers haven't finished processing. Watch for claims that never acknowledged, since those are usually clearinghouse rejections that never became claims at all.
31 to 60 days is first contact. Anything unpaid here gets a status check with the payer, and the answer goes in the record. This is the bucket where most recoverable money still is.
61 to 90 days is escalation. You need a reason, not a status. Pended for documentation, denied and not worked, processed to the wrong plan, or lost.
91 to 120 days is triage against the filing clock. Some of these can be corrected and refiled, some need an appeal, and some are already outside the window.
Over 120 days is a decision, not a task. Appeal, escalate to a payer representative, or write it off with a root cause recorded. Leaving it open without a decision is the worst of the three options.
Where ABA accounts receivable follow-up breaks
Claims get worked by whoever has time
Without a named owner, the same claim gets called on twice in one week and then not at all for two months. The payer's notes show two contacts. Your team remembers neither.
Small balances get worked first
They close faster, so the queue looks better. Meanwhile the $4,000 authorization denial sits untouched because it takes an hour and an appeal.
Sort by dollars at risk against the filing deadline, not by how satisfying a claim is to close.
The follow-up happens but nothing gets recorded
Someone calls, gets told the claim is in process, hangs up, and moves on. Three weeks later a different person calls and gets the same answer.
The record needs what the payer said, the reference number, and what happens next. Without those, every call starts over.
Timely filing is watched at the wrong time
Filing deadlines get checked when a claim reaches 120 days. By then several of them have already passed, especially with payers running 90-day windows.
The deadline belongs on the record from day one, and the AR list should sort by it whenever the bucket is 61 days or older. This is also where denial root-cause tracking matters, because aging claims often point back to authorization, eligibility, credentialing, coding, or timely-filing failures.
The next-action rule
One rule holds the whole system together. No open claim closes a follow-up without a next action and a next follow-up date.
"Called payer, in process" is not a complete entry. "Called payer, in process, rep says adjudication by the 15th, recheck the 16th, ref 4471029" is.
Apply it without exception and the aging report stops being a list of problems and becomes a calendar. That's the entire difference.
Where connected operations help
Most AR problems trace back to something that happened before the claim was submitted. Coverage wasn't re-verified through the benefits verification workflow, authorization units ran out, or the rendering provider wasn't enrolled with that payer yet.
Working AR without visibility into those upstream steps means guessing at why a claim is stuck and calling the payer to find out.
SparkzABA keeps AR records with aging, owner, next action, next follow-up date, and history connected to the authorization, credentialing, and denial work that explains most of the aging through a connected ABA Revenue Cycle Management workflow. Your clearinghouse still transmits the claims. The change is that nothing open sits without a name and a date on it.
If authorization is one of the main reasons claims are aging, the ABA prior authorization renewal guide shows where those gaps usually start before they reach AR.
Frequently asked questions
How often should ABA clinics work accounts receivable?
Weekly for everything past 30 days, with a full AR review monthly. Weekly cadence matters most in the 31 to 90 day range, where claims are still straightforward to resolve and filing windows are not yet a factor. Waiting for a monthly cycle pushes recoverable claims into appeal territory.
What is a healthy AR aging profile for an ABA practice?
Most ABA organizations aim to keep the majority of AR under 60 days, with the over-90 bucket small and shrinking. Benchmarks vary by payer mix, since Medicaid and commercial plans pay on different timelines, so track your own trend over several months rather than comparing to a single industry figure.
What should be recorded after every payer follow-up call?
The date, the representative's name, the reference number, what the payer said about claim status, the next action, and the next follow-up date. Without a reference number, the payer has no record of the conversation, and your team restarts the same call weeks later.
Give every open claim a name and a date
Open your current aging report and count how many claims past 60 days have no owner and no next follow-up date. That number is the real state of your ABA accounts receivable follow-up.
Comments