Billing operations guide

Write an accounts receivable escalation ladder before balances age

A step-by-step AR escalation ladder with owners, evidence, and stop rules for aging balances.

Published 6 min read
On this page

Define the aging buckets you will act on

Choose buckets that match the payer contract and the team's ability to act. Common buckets are current, thirty, sixty, ninety, and over ninety days, but the labels should reflect the actual follow-up cycle. Record how the age is calculated and which date starts the clock. A bucket without a definition is just a color on a report.

Separate patient balances from payer balances and from patient responsibility after adjudication. Each has a different contact route and a different legal context. Do not apply a payer escalation step to a patient account. The ladder should branch by the party who owes the money.

Assign an owner to each rung

Name the role that acts at each step and the person who reviews the action. A rung without an owner becomes a report that nobody works. Include a backup for absences and a maximum time in each rung. The ladder should move an account forward, not leave it parked.

Define what the owner must record before moving the account. For a payer, that may be a call reference and the next review date. For a patient, that may be a statement date and a contact attempt. The record is the evidence that the rung was completed. Without it, the next owner starts over.

Make the first contact count

Before the first contact, confirm the balance, the payer, the date of service, and the reason the claim is unpaid. Check whether a denial or a request for information is already open. A call made without that context wastes the payer's time and the team's. Preparation is part of the escalation.

Ask a specific question and record the answer. If the payer says the claim is in process, ask for the expected completion date and the reference. If the payer says information is missing, ask what was requested and when. The first contact should produce a next step or a documented dead end.

Set evidence requirements for escalation

Require the claim, the remittance, the denial letter, and the contact history before an account moves to a supervisor or a payer relations team. State which evidence is mandatory and which is optional. A supervisor should be able to review the file without requesting it again. Missing evidence is a reason to return the account, not to escalate it.

Keep the evidence in a shared repository and link it from the account note. Do not rely on a personal inbox or a screenshot on a desktop. Check that the evidence is readable and that the dates match. An escalation built on the wrong document can delay the account further.

Coordinate with clinical and front-desk teams

Some balances cannot move until a clinical record, a corrected diagnosis, or a registration update arrives. Add a rung for that dependency and name the team that owns it. Set a date for the response and a path for escalation. The AR team should not be blamed for work it cannot complete.

Share the reason for the request in plain language and with the specific claim reference. Avoid sending a general request for records that forces the other team to search. Close the loop when the document arrives so the account can move. Coordination is a handoff, not a transfer of blame.

Decide when to stop collecting

Set stop rules for small balances, deceased patients, bankruptcy, and accounts that have passed the legal or contractual limit. A stop rule should be approved by the owner who understands the policy. Record the reason and the date. Continuing to work an uncollectible account consumes capacity without improving revenue.

Do not use a stop rule to hide a process problem. If many accounts reach the stop threshold because the first contact was late, fix the earlier rung. Review stopped accounts quarterly for patterns. The stop rule is a control, not a shortcut.

Review the ladder with real accounts

Pull a sample from each aging bucket and trace it through the ladder. Check whether the owner acted on time, the evidence is present, and the next step is clear. Count accounts that skipped a rung or repeated one. The sample shows whether the ladder works in practice.

Ask the people who work the accounts which step is hardest to complete. A step that requires a permission or a tool they do not have will always be late. Fix the constraint before adding more reporting. The ladder should reflect the work, not an idealized process.

Update payer-specific exceptions

Record exceptions such as a payer that requires a portal dispute before a phone call or a contract that sets a different appeal window. Keep the exception beside the standard step it replaces. Review exceptions each quarter and remove the ones that no longer apply. An exception without an owner becomes an unofficial rule.

Tell the team when an exception changes and update the scripts and templates. Test the new path on one account before rolling it out. Record the result. The ladder stays useful when the exceptions are visible and controlled.

Set the review cadence for each rung

Each rung should have a review interval that matches the payer's response time and the account's risk. A high-value appeal may need a weekly check, while a routine patient balance may need a monthly statement cycle. Record the interval beside the rung. A single cadence for every account either overworks the team or lets important balances sit.

Review missed intervals in the monthly sample and ask why the check did not happen. If the cause is workload, adjust the queue or the target. If the cause is an unclear owner, fix the assignment. The cadence is a promise about attention, and it should be tested like any other control.

Authoritative references

  1. CMS Medicare Learning Network
  2. CMS Medicare Appeals
  3. Consumer Financial Protection Bureau
  4. GAO Green Book

Philippines staffing intake

Define the role before hiring begins.

Share the tasks, tools, schedule, and approval limits for your Filipino team member. The intake turns those details into a practical staffing brief.

Contact Us