Billing operations guide

Write a month-end AR follow-up plan that names every owner

A month-end accounts receivable plan with defensible aging, risk-based priorities, payer call packets, and a clean close review.

Published 6 min read
On this page

Start with the aging report you can defend

A month-end AR plan starts with an aging report whose population, cutoff, and source are documented. Confirm that the report includes open claims, patient balances, and credits that affect the total. Reconcile the report total to the general ledger or billing system summary before using it for priorities. An aging report that cannot be tied back is a conversation starter, not a work plan.

Check the aging buckets against the organization's definition of current, past due, and disputed. A claim that is waiting for a payer response should not sit in the same bucket as a claim that has never been submitted. Separate denied claims, appealed claims, and claims with no response. The team needs different actions for each group.

Set priorities by risk, not by balance alone

Rank the work by value, age, payer behavior, and the chance that the claim can still be corrected. A large claim near a filing deadline deserves attention before a small claim with no deadline pressure. A claim with a clear payer error may be easier to recover than a larger claim with missing documentation. Explain the ranking in the plan so the team can defend its choices.

Include patient balances that are aging without contact and accounts with repeated broken promises. Review credit balances that could offset the AR total and create a misleading picture. Set a cap on how many accounts each specialist can work in a day so the plan is realistic. A plan that ignores capacity becomes a list of good intentions.

Name the owner for each follow-up path

Each path needs an owner: payer follow-up, denial appeal, patient contact, coding review, or cash application. Put the owner's role and backup in the plan, not only the team name. Define the next action and the date it is due for every account in the working list. If an account needs two owners, say which one acts first.

A handoff between owners should include the account reference, the last action, the response, and the next question. Do not send an account to another queue without that context. The receiving owner should be able to continue without calling the sender. A clean handoff is part of the follow-up work, not an administrative extra.

Prepare the payer call packet

A payer call packet should include the claim identifier, service date, billed amount, current status, prior reference numbers, and the specific question for the payer. Add the date and time of the last contact and the name of the representative if one was provided. Keep the packet short enough to use during the call. A long history without a clear question wastes the call.

During the call, record the reference number, the stated status, the next step, and the expected date. Ask the payer to confirm whether the claim is under review, denied, or waiting for information. If the answer is vague, ask for the policy or unit that can clarify it. End the call with a specific follow-up date.

Record promises and next dates

A promise to pay or a promise to review is not a resolution until the account shows the result. Record the promise date, the amount, the source, and the person who made it. Set the next review date before the promise expires. If the promise is missed, escalate using the documented path instead of restarting the same call.

Keep the follow-up history in one place so the next specialist can see what was said and when. Do not rely on a personal note or a separate spreadsheet that only one person can find. Link the history to the claim and the patient account. The record should show the difference between a payer statement and a team assumption.

Close month end with a short review

At month end, compare the opening and closing AR, the cash collected, the adjustments, and the accounts that moved between buckets. Explain the largest changes and the accounts that remain unresolved. Review whether the plan's priorities produced the expected work. Link the review to collections follow-up and month-end billing support so the next month starts with the same definitions.

Keep the plan current during the month

A month-end plan should be updated when a payer changes a rule, a large account is resolved, or a new backlog appears. Set a weekly review of the plan's priorities and owners. Do not wait for month end to discover that the largest account moved to a different queue. The plan is a working document, not a report written after the fact.

Record the reason for each priority change so the team can see why the plan moved. A change caused by new information is different from a change caused by missed work. Keep the original target and the revised target side by side. That history helps the next month's plan start from reality.

Handle disputes inside the AR plan

A disputed account needs a different path from a collectible balance, because the next action may be evidence review rather than a payment call. Mark the dispute reason, the owner, and the date the dispute started. Pause automated statements or collection activity according to policy. A dispute that stays in the normal AR queue can damage the patient relationship and distort the aging.

Keep the dispute evidence with the account, including the patient or payer question, the records reviewed, and the response. If the dispute is valid, correct the balance through the approved adjustment path. If it is not, explain the basis in plain language and record the next contact. Do not close a dispute because the account is old.

Review disputes separately at month end and report their value and age. A rising dispute balance may point to a billing error, a communication problem, or a payer policy change. Link the finding to customer billing support and billing data quality review so the upstream cause is addressed.

Authoritative references

  1. CMS Medicare Appeals and Grievances
  2. CMS Medicare Learning Network
  3. GAO Green Book
  4. HHS HIPAA Privacy Rule
  5. X12 Health Care Claim 837

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