How to Write ABA AR Notes Your Billing Director Can Actually Act On

Open your AR report and read the comments column. Not all of it. Five notes, picked at random.

For each one, ask a single question: could you set a deadline based on what this says?

Most practices fail that test badly. In one sample ABA audit, 47 AR follow-up notes were scored and two of them had an expected payment date on them. Two. The other 45 described activity without ever committing to a checkable outcome.

That's not a documentation problem. It's a collections problem wearing a documentation costume, because a balance nobody can set a deadline on is a balance that stops moving.

What AR follow-up notes are actually for

There's a common assumption that AR notes exist to prove work happened. Somebody called the payer, somebody wrote it down, the file shows effort.

That's the wrong job description.

AR follow-up notes exist so that a second person, reading the file cold, knows what to do next and when. That's it. If your director reads a note in 30 seconds and still doesn't know what happens next or when to check back, the note failed regardless of how much work went into it.

This reframe changes what a good note looks like. It's not about detail. It's about handoff.

The 1 to 5 scale for scoring AR follow-up notes

Here's the scoring most audits use. It's worth internalizing because it's simple enough to apply while you're writing.

5 is strong. Explains why the balance is open, gives a specific expected date, and the reasoning is verifiable. Something like: "All June claims submitted 07/01. Standard 21-day processing. Anticipate EFT by 07/22."

4 is good. Clear explanation and a credible timeline, even if slightly less precise. "Auth corrected, resubmitted 06/28. Payer confirms 30-day adjudication. Expected payment by 07/28."

3 is acceptable. Explains the situation but goes vague on timing. "Claims denied for auth, team resubmitting, should resolve in the coming weeks." You know what's happening. You don't know when to follow up.

2 is weak. Copy-paste language, no date, no explanation of cause. "Approved for payment, anticipate receipt in the next few weeks."

1 is suspect. Contradicts something else in the file, or is clearly stale. The same "waiting on client" note appearing for four months on claims now 250 days old.

The sample account averaged 2.30 across 47 notes, with 51% red flagged. That's roughly typical for a practice that has never audited its AR follow-up notes, in-house or outsourced.

Length is not quality in AR follow-up notes

This is the part that surprises people.

A 340-word note with no payment date scores a 2. A two-line note naming a dispute number and a submission date scores a 4.

Long notes feel thorough, which is exactly why they're dangerous. They give the reader a sense that the balance is being handled without giving them anything to check. And they're the notes most likely to get copy-pasted forward, because rewriting 340 words every month is nobody's idea of a good time.

The worst offender in that sample file was a 340-word paragraph pasted verbatim onto five claims spanning eight months. Every instance ended with a commitment to continue following up. Every instance was identical. Twelve months elapsed and the balance never moved.

Nobody caught it, because at a glance it looked like the most thoroughly documented account in the file.

Copy-paste is the failure mode that hides money

Duplicate AR follow-up notes are the single strongest signal that a balance has gone static.

The mechanism is straightforward. Working a claim properly produces new information: a rep's answer, a status change, a resubmission date. New information changes the note. When the note doesn't change, either nothing was learned or nothing was done, and from the outside those two look identical.

Four patterns worth scanning for.

The same paragraph across multiple months on one claim. Balance isn't moving and the note is covering for it.

The same paragraph across multiple claims in one month. One generic sentence covering seven payers. In the sample file, the largest single open balance in the report, $20,260, was documented exactly this way, with no owner and no per-payer detail.

A note that belongs to a different claim. Copy-paste that carried over the wrong payer's dispute, or repeats last month's date of service and dollar amount. The current claim is never actually described.

A note that contradicts a known fact elsewhere in the file. One example: a note still asking the provider to advise on a coverage question the payer had confirmed and closed five months earlier.

That last category is worth pausing on. Contradictions inside your own AR file are where money reliably gets stuck, because two people are working from different assumptions and neither knows it.

What separates a 4 from a 2 in practice

Four elements, and you don't need all four every time.

Why the balance is open. Not "pending." The actual reason. Denied for auth, never submitted, awaiting EOB, in appeal, in dispute.

What was done about it, with a date. Submitted 07/08. Appeal mailed 06/23. Auth request filed 07/15.

What happens next, with a date. This is the one that's almost always missing. Payer states 10 to 15 business days, so the window closes 07/23. Expect payment by 07/28. Follow up 08/01.

Who owns it, if it's shared work or an escalation.

What you don't need: claim numbers and rep names in a summary note. Useful in a detail log, but their absence isn't what makes a note unusable. Missing dates are.

Compare these two on the same claim.

Weak: "Please allow 10-15 business days." That was written on a $3,781 balance. No submission date, so nobody could calculate when the window closed. It closed on 07/23 and no one noticed.

Strong: "Submitted 07/08, payer states 10-15 business days, window closes 07/23, follow up 07/24 if no payment." Same information, same length, now checkable.

The difference is fifteen seconds of writing.

How to audit your own AR follow-up notes this week

Twenty minutes, and you don't need any special tooling.

Pull the ten largest open balances. Money first, always. A perfect note on a $132 claim matters less than a vague one on $9,000.

Score each note 1 to 5 using the scale above. Be strict about the date requirement, because that's the whole point.

Calculate your average. Under 2.5 means your AR documentation isn't functioning as documentation. Above 3.5 means your team is doing this well and you should say so.

Scan for duplicates. Sort your comments column alphabetically and look for identical or near-identical text. Duplicates surface immediately this way.

Pick the three worst and rewrite them. Not as a correction exercise. As a template. Your team needs to see what a 4 looks like on their own claims, in their own language.

One thing worth knowing before you start: in that sample file, two notes did score a 4. One named the payer dispute number and submission date.

The other identified a plan migration, cited the inquiry ticket, and gave a 30-day turnaround from a stated date.

The standard was achievable. The team had already hit it twice. They just weren't hitting it consistently, and nobody had told them which version was right.

Read More What Is an ABA AR Audit? Why Reports Miss Money

Common questions about ABA AR follow-up notes

How detailed should an AR follow-up note be?

Two or three lines is usually enough if those lines carry a cause, an action with a date, and an expected outcome with a date. Detail beyond that belongs in a claim-level log, not the AR summary. The test is whether a director reading it cold in 30 seconds can set a follow-up date without asking anyone a question.

What if my billing company writes the AR notes?

You can still score them, and arguably you should, since the notes are the only visibility you have into work you're paying for. Score the ten largest balances monthly and share the results. Most outsourced ABA billing services teams respond well to a specific standard, because vague expectations are usually what produced the vague notes in the first place.

Do AR note quality problems actually cost money?

Yes, indirectly but reliably. A note without a checkable date means nobody knows when to follow up, so nobody does, and the balance ages until a filing or appeal window closes. In audits that grade ABA revenue cycle management performance, note quality below a 2.5 average is treated as a full letter-grade problem for this reason.

Start with the ten biggest balances

You don't need to fix every note in your file. Most of them are attached to small amounts that will resolve on their own.

Take the ten largest open balances and read what's written next to them. If fewer than three carry a date you could actually check next week, you've found the reason those balances haven't moved.

Then rewrite those ten. It takes half an hour and it's the cheapest thing you'll do all month for your AR.