Billing

Unbilled Behavioral Health Encounters: Find the Hold

•
October 29, 2026
Two healthcare professionals walking through a bright clinic corridor with plants

Build an unbilled behavioral health encounter worklist with clear aging dates, hold reasons, owners, source records, and verified resolution evidence.

An unbilled encounter worklist should explain the hold, its owner, the relevant aging date, and the evidence needed for the next legitimate action. A long list of encounters with no claim can identify a problem without telling anyone how to resolve it.

This guide describes an operational review for behavioral health billing teams. It does not establish that every encounter is billable, select claim codes, or prescribe a payer-specific action. Use the actual service facts, current instructions, and authorized clinical and billing review.

Behavioral health unbilled encounter aging starts with scope

Define the population. Scheduled appointments, completed encounters, signed notes, draft charges, and reviewed claims represent different stages. Decide which stage the report starts from and what event counts as leaving the unbilled population.

The CMS electronic health care claims overview provides a Medicare submission reference. It does not establish that every local encounter should become a claim. Keep the organization's service and payer review separate from the existence of a record.

Identify legitimate exclusions such as nonbillable activity, test records, duplicates, and canceled encounters. Record the reason and owner. Exclusion can be appropriate, but unexplained removal can make the backlog appear better without resolving actual work.

Name the clock being measured

Service-to-submission time, documentation-to-review time, and time waiting with a particular owner answer different questions. A single age field can conceal where the delay actually occurs.

Preserve service date, documentation status dates, charge creation, hold assignment, and submission events where relevant. The report can display more than one interval if that helps staff distinguish old services from newly assigned work.

For a fictional example, a service occurred two weeks ago but a billing hold reached a specialist yesterday. The service is old, while the current specialist's task is new. Both facts matter, and neither should be used to misrepresent the other's performance.

See this working in Ease.
Book a demo

Classify holds by the unresolved decision

Use specific categories such as documentation question, coverage review, authorization evidence, provider information, location mismatch, coding review, external dependency, or nonbillable determination. Tailor the list to the organization's actual process.

Avoid a generic pending label that forces the next reviewer to reopen every chart to discover the issue. Include a short question, source identifier, owner, and next action. Keep clinical narrative in the authorized record rather than broad worklist text.

Review whether the hold is still valid. An item may remain in a queue after the underlying record changed because no one accepted the next handoff. The process needs both detection and a defined resolution event.

Keep clinical facts with clinical owners

Billing staff can identify that a note is missing or inconsistent, but authorized clinicians determine what occurred and what documentation action is appropriate. Do not create retrospective clinical facts to release a charge.

Use a fictional case involving an unsigned note and another involving a wrong encounter association. The first may need author review; the second may need a different authorized correction. Repeated reminders to the same person will not solve every documentation-related hold.

If the original clinician is unavailable, route the case through the organization's approved supervisory and record policies. Preserve authorship and history. Reassigning a work item should not imply that a replacement user delivered or witnessed the original service.

Want to see it with your own workflows?
Book a demo

Distinguish charge creation from submission

A charge can exist without a reviewed claim, and a claim can be prepared without an acknowledged submission. Define which stage the worklist tracks so staff know what completion means.

The CMS Medicare remittance advice page provides a later payment-response context. Keeping that stage distinct helps the organization avoid mixing unbilled work with adjudication and posting work.

Hold state Evidence for the next owner
No expected record Encounter facts and authorized documentation question
Record incomplete Missing action and clinical owner
Charge review pending Specific administrative issue and reviewer
External evidence pending Request reference, responsible contact, and follow-up
Ready for submission Reviewed artifact and submission owner
Nonbillable or duplicate Supported disposition and retained explanation

The table is a routing aid. It does not establish that every case belongs in a claim workflow or that resolving one hold removes every other review obligation.

Measure movement and verified outcomes

Track opening items, newly identified items, resolved items, reclassified items, and ending items. A declining backlog can result from legitimate submission, a changed filter, or bulk exclusion. The ledger should explain the difference.

Review outcomes by cause and owner, with stable definitions. If a rate is used, name the denominator and period. Avoid adopting a generic industry benchmark without compatible scope and evidence.

Sample closed items under the organization's quality process. Confirm the recorded outcome happened and that the source issue was corrected where appropriate. An item marked resolved while the underlying record remains wrong can recur in the next encounter.

Questions about your setup? Ask them on a demo.
Book a demo

Test the worklist with ordinary and exception cases

Create fictional cases for completed documentation, missing note, coverage question, authorization ambiguity, wrong provider, duplicate record, nonbillable activity, and an external dependency. Write the expected owner and next action before the demonstration.

Ask vendors to show the actual queue, history, routing, and resolution evidence using ordinary staff roles. Record which steps are available, configurable, external, manual, or unverified. A dashboard total alone does not establish an actionable workflow.

After implementation, examine recurring causes. A configuration change, clearer intake handoff, or revised training may reduce the same hold category. More reminders are unlikely to fix a process with no agreed owner.

Ease Health publishes this guide and offers a unified CRM, EHR, and RCM platform for behavioral health. Ask the team to demonstrate the proposed unbilled encounter workflow and its dependencies. Related material includes the RCM overview, claim-status queue guide, and appointment reconciliation guide.

The useful result is an aging report that explains work and supports legitimate action. It helps the organization find stalled handoffs without assuming every missing claim represents the same kind of problem.

Related reading

Frequently Asked Questions

Is every documented encounter supposed to become a claim?

No. Nonbillable activity, corrections, duplicates, service circumstances, and applicable payer rules can produce legitimate differences. Define the expected relationship before treating every missing charge as lost revenue.

Which date should an unbilled aging report use?

Name the purpose and date explicitly. Service date, documentation completion, charge creation, and the date a hold reached its owner measure different intervals. Preserve the underlying events.

Who should resolve a documentation hold?

The authorized clinical owner resolves clinical documentation questions under organizational policy. Billing staff can identify the issue and track the handoff without inventing or rewriting clinical facts.

What proves an unbilled item is resolved?

Retain the actual outcome, such as reviewed submission, an authorized nonbillable disposition, a corrected duplicate, or another supported decision. A cleared screen alone is not enough.

Want to see how Ease handles this?