Billing operations guide
Run a weekly unbilled claims review without slowing the team
A short weekly review that finds the causes of unbilled claims and assigns one owner to each hold.
On this page
Define what counts as unbilled
An unbilled claim is work that has not reached the payer, not merely work that is missing from a report. Include charges on hold, claims that failed an edit, and accounts waiting on documentation. Record the date the service was completed and the date the claim should have gone out. Without both dates, the age of the item is ambiguous.
Separate a new charge from a corrected claim and from a claim that is waiting for patient information. Each type has a different owner and a different clock. A single unbilled list that mixes them will mislead the review. Label the type before discussing the count.
Set the age threshold by claim type
Choose an age threshold that reflects the payer's filing limit and the team's normal turnaround. A clean electronic claim may have a short threshold, while a claim awaiting records may need more time. Write the threshold beside the type. One threshold for every claim creates false alarms and missed deadlines.
Calculate age from the service date or the date the charge became billable, and say which. A service date is stable, while a billable date can move when documentation arrives. Use the stricter date for items near a filing limit. The review should show the filing deadline when one is at risk.
Assign one owner per hold reason
Every item on the list needs a named owner and a reason code. The owner may be a person, a queue, or a team, but it must be identifiable. A reason such as pending review tells the reviewer nothing about who acts. The list should route work rather than describe it.
Group the reasons into a short set that the team can act on. Examples include missing authorization, documentation request, coding query, and payer rejection. Review the counts by reason before reviewing individual claims. A large reason bucket is a process problem, not a long to-do list.
Read the report by cause, not by count
A rising unbilled count can come from higher volume, a new payer edit, or a backlog in one queue. Compare the count with the volume submitted in the same week. Look at the age distribution rather than the total. A stable total with older items is a worsening backlog.
Report the oldest item, the median age, and the share past the threshold. These three numbers describe the queue better than a single total. Add the top reason and its owner. The team can then decide where to intervene.
Set a decision rule for stuck claims
Some claims cannot move without a decision from a qualified owner. Write the conditions that trigger escalation and the evidence to send. Set a maximum time in each queue before escalation. A claim that sits without a decision consumes the same attention as active work.
Distinguish a claim waiting on the payer from one waiting on the team. Payer waits need a follow-up date and a reference. Internal waits need a named owner and a due date. The decision rule should make the wait visible instead of hiding it in an average.
Protect the review from becoming a meeting
Keep the weekly review to a fixed agenda and a fixed length. Review the numbers, the top reason, and the exceptions that need a decision. Do not read claims aloud one by one. The report should be available before the meeting so the time is spent on action.
Assign actions during the review with an owner and a date. Record them beside the claim or the reason. Start the next review by checking the prior actions. A review without follow-up becomes a ritual that the team learns to skip.
Track recovery after the decision
Measure how many items left the list after the review and how quickly. Compare the recovery with the reason and the owner. A queue that clears but returns next week has a recurring cause. Recovery is the outcome that shows the review worked.
Sample a few recovered claims to confirm they were billed correctly. A claim removed from the list is not necessarily a clean claim. Check the submission, the acceptance, and any payer response. The review should improve billing, not just reduce a count.
Escalate only what needs escalation
Reserve escalation for claims near a filing limit, high-value claims, and items blocked by another team. Give the escalation a clear ask and a deadline. Do not escalate every old claim, because the recipient will stop reading. A narrow escalation is more likely to succeed.
Record the escalation and the response in the claim history. If the response is slow, review the route rather than sending more messages. The pattern may show that the wrong owner receives the request. Fix the route before adding pressure.
Authoritative references
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