- Unbilled services are invisible by default: a denial generates a remittance line, but a session with no charge generates nothing at all.
- Most of it hides in a handful of places: unsigned notes, attendance never recorded, encounters that never produced a charge, held charges nobody released, and census days that never reached a claim.
- The fix is a weekly comparison of three lists: what was scheduled or occupied, what was documented, and what was charged.
- Every gap needs an owner outside billing and a reason code, so you fix the workflow rather than chase the same gap every week.
- Age matters: payer filing limits and documentation rules vary, so confirm them against each contract and work the oldest gaps first.
A clinician runs a Tuesday afternoon IOP group, goes home sick, and never signs the notes. By Friday the schedule shows the group happened, the attendance sheet sits in a folder at the front desk, and the billing system shows nothing, because nothing was ever sent to it. Nobody is ignoring the problem. Nobody knows it is there. Unlike a denial, which arrives on a remittance with a reason code attached, a delivered service that never became a charge produces no signal of any kind. It just quietly ages until it can no longer be billed.
Unbilled is a different problem from denied
Most revenue cycle reporting starts at the claim. First-pass rate, denial rate, days in A/R: every one of them counts things that already reached billing. A service that never got that far is outside the denominator. You can have a clean denials queue and a healthy first-pass rate while a meaningful slice of delivered care never appears anywhere in the numbers.
That is why this needs its own routine. The month-end version of this question is covered in our month-end close checklist. This piece is about the weekly habit that keeps the month-end list short, and about the specific places to look.
A denial at least tells you it exists. An unbilled service waits silently until the filing window closes.
Where unbilled services hide
The unsigned note
The most common and the most obvious. Many programs hold a charge until the note is signed, which is the right default. The failure is that the hold has no clock and no escalation. A note left in draft on a Thursday becomes a note left in draft for three weeks, and when the clinician has since left the organization, it may never be signed at all. Look specifically for drafts belonging to departed or inactive staff, and for notes waiting on a supervisor co-signature, which often sit in a queue nobody owns.
Attendance that was never recorded
In group-based programs, attendance is often what turns a scheduled session into a billable one. When the sign-in sheet stays on paper, or a substitute facilitator does not know where to record it, the group happened clinically but not administratively. Watch for groups with notes but no attendance, attendance for fewer participants than were scheduled with no reason recorded, and patients marked late or left early whose status was never resolved, because the program's rules on partial attendance decide whether that day can be billed at all.
The encounter that produced no charge
Sometimes everything clinical is complete and still no charge exists. The usual causes are mapping problems: a note type that is not linked to a service code, a new program or location added without its charge setup, a telehealth session documented under an in-person template, or an ad hoc service such as a crisis session or family session that was never put on the schedule in the first place. These tend to repeat every week until someone fixes the configuration, which makes them worth finding early.
Held charges nobody released
A charge held for a missing authorization, a credentialing question or an eligibility problem is supposed to come back once the issue is resolved. Often the issue is resolved and the charge stays held, because the person who fixed the authorization did not know a charge was waiting on it. Review every hold for whether its reason is still true.
Census days that never reached a claim
In residential and detox, the gap is usually between the census and the billed days. A late-night admission entered the next morning, a transfer between levels of care recorded on the whiteboard but not in the system, or a discharge date corrected after the claim was built can all leave days delivered and unbilled. The weekly check is simple: patient-days on the census against days on claims or in the billing pipeline, per payer.
The weekly sweep: three lists and a comparison
The method does not depend on any particular system. It depends on comparing three lists that should describe the same week and investigating every place they disagree.
- Pull what was delivered. For outpatient, PHP and IOP, that is completed appointments and group sessions with attendance. For residential and detox, it is patient-days from the census. Use a fixed window, such as the week ending the previous Sunday, plus anything still open from earlier weeks.
- Pull what was documented. Signed notes, notes in draft, notes awaiting co-signature, and attendance records, each with the service date.
- Pull what was charged. Charges created, charges on hold with their hold reason, and claims submitted for those service dates.
- Match them on patient, date and service. Every delivered service should have a documentation status and a charge status. Anything with a gap goes on the exceptions list.
- Classify every exception with a short reason: unsigned note, no attendance, no charge mapping, stale hold, census mismatch, or cancelled-but-shows-completed. The last one matters, because some gaps are schedule errors and should be corrected, not billed.
- Assign an owner and a due date to each exception, then carry unresolved items into next week's list with their age visible.
For a small program, this can be a spreadsheet and an hour on Monday morning. Say a hypothetical 24-client IOP runs four groups a day, four days a week. That is a few hundred participant-sessions a week, and a mismatch report against that volume is usually a page or two. The first week is the slowest, because it surfaces the backlog. After that, the list is mostly new items.
Every gap needs an owner who is not billing
The tempting design is to hand the exceptions list to the billing team. It does not work, because billing cannot sign a note, record attendance for a group they did not run, or decide whether a session actually happened. The same principle we describe for claim readiness applies here: the gap goes to the team that owns its source.
- Unsigned notes and pending co-signatures: the clinician, with the clinical director or supervisor copied once an item passes your internal deadline.
- Missing or unresolved attendance: the program lead or group facilitator for that session.
- Encounters with no charge mapping: whoever owns system configuration, usually with billing confirming the right service code.
- Stale holds: the team that owns the hold reason, such as utilization review for authorizations or credentialing for enrollment.
- Census mismatches: nursing or admissions, whoever records admissions, transfers and discharges.
- Notes from departed clinicians: the clinical director, who decides with compliance how that documentation is handled.
The goal of the sweep is to find services that were delivered and documented, or that can be honestly completed by the person who delivered them. It is not to produce records after the fact for services nobody can attest to. A late signature or late entry should be identified as late, with the actual date it was made, under your documentation policy. See our guide to late entries, addenda and amendments. If a service cannot be supported, it should not be billed, and compliance should know why.
Age is the number that matters most
An unbilled service from last week is a workflow problem. One from four months ago may be a write-off. Payer filing limits differ by payer, plan and contract, and some payers and organizational policies also restrict how long after a service a note can be completed for billing. Do not assume a single deadline. Confirm the filing limit in each payer contract or provider manual, record it per payer, and sort the exceptions list by how close each item is to that payer's limit rather than by service date alone. Our working guide to timely filing and proof of submission covers what to do once a claim is near or past that line.
Two numbers are worth reporting weekly alongside your other revenue cycle KPIs: the count of delivered services with no charge, and the age of the oldest one. A falling count with a rising oldest age means new work is being handled while an old problem is being avoided.
Make the list shorter, not just cleared
If the same reason code fills the list every week, the sweep is doing triage and nothing else. Once a month, group the past four weeks of exceptions by reason and by source, and ask what single change would remove the largest group.
- If one program dominates the missing-attendance gaps, the problem is probably where and when attendance gets recorded, not the people recording it.
- If unsigned notes cluster around a few clinicians, it is a supervision conversation. If they are spread evenly, the documentation deadline itself may be unrealistic for the schedule.
- If no-charge encounters cluster on one note type or location, fix the mapping once and the gap disappears.
- If stale holds keep appearing, the team resolving the hold has no way of knowing a charge is waiting. That is a handoff to design, not a reminder to send.
This is also where the sweep pays off beyond revenue. An unsigned note is a billing gap and a documentation finding waiting to happen. A census mismatch is a billing gap and a records problem in any later review.
Where the system can carry part of the work
The sweep works on paper. It gets shorter when the gaps surface on their own before the week ends. In Unisona Health, the documentation clock runs against the window you set from the end of each session, reminds the clinician, notifies the supervisor, and marks the note overdue with the claim held, so unsigned notes appear on a dashboard rather than in a Monday reconciliation. For PHP and IOP, attendance recorded per participant drives the per-diem claim directly, which removes the gap between the sign-in sheet and the charge. Whatever you use, keep running the three-list comparison: it is the check that catches what no single alert was built to see.
Frequently asked questions
How do I find services that were delivered but never billed?
Compare three lists for the same week: what was delivered (completed appointments, attended groups or census days), what was documented, and what was charged. Match them on patient, date and service, and treat every disagreement as an exception with a reason, an owner and a due date.
What is the difference between unbilled services and denied claims?
A denied claim reached the payer and comes back on a remittance with a reason code, so it shows up in reporting. An unbilled service never became a claim, so it produces no signal and sits outside metrics like first-pass rate and denial rate until someone looks for it.
Who should own unsigned notes and missing attendance in the unbilled report?
The team that owns the source of the gap, not billing. Clinicians and their supervisors own unsigned notes and co-signatures, program leads own attendance, configuration owners fix encounters with no charge mapping, and the team behind each hold reason releases stale holds.
How long do we have to bill a service that was missed?
It depends on the payer. Filing limits vary by payer, plan and contract, and some payers and internal policies also limit late documentation. Confirm the limit in each payer contract or provider manual and work the unbilled list in order of how close each item is to that payer's limit.
Can a clinician sign a late note so we can bill the service?
Only if the clinician who delivered the service can honestly complete it, and the late signature or entry is identified as late under your documentation policy and the payer's rules. Documentation should never be created for a service nobody can attest to; if it cannot be supported, it should not be billed.
