For an RCM company managing several provider clients, a single collections total cannot explain those delays. You need to know which encounters are blocked, what evidence is missing and who can move them forward.
Use the following checklist in your next operations review. It is an operational review framework, not a universal payer rulebook. Apply the requirements for the specific plan, service, provider and date of service.
Start with a small, traceable sample
Choose one behavioral health client and a defined service period. Include encounters awaiting billing, rejected submissions, denied claims and paid claims with unresolved balances. This avoids examining only the problems that have already reached the denial queue.
For each item, record the encounter or claim identifier in your approved internal system, current status, supporting evidence, responsible team and next review date. Keep patient information out of public collaboration tools.
Before service: verify the conditions that affect billing
- Coverage for the service date. Verify the member, plan and effective dates. Record when the check occurred and recheck when information changes.
- The correct benefit administrator. Confirm who administers the relevant behavioral health benefit. Do not assume that the medical plan and behavioral health claim destination are always identical—or always different.
- Provider participation and enrollment. Check the rendering provider, billing entity and service location against the applicable payer requirements. A valid NPI alone does not establish participation.
- Authorization requirements. Establish whether the planned service requires authorization, notification or another review. Save the payer response and its scope.
- Authorization use and expiry. When authorization applies, track its dates, approved service and units. Reconcile completed visits promptly so remaining units reflect actual activity.
Before submission: connect the record to the claim
CMS's behavioral health documentation guidance explains that records should support the services billed. The practical implication is to review the documented encounter alongside the claim, rather than treating the presence of a note as sufficient. [1]
- Completed documentation. Check that the required encounter record and authentication are present. Route unfinished records to the appropriate clinician.
- Support for the service. Have qualified reviewers assess whether the record supports the service delivered. Billing staff should raise questions, not invent clinical detail to obtain payment.
- Documented time and billed service. Where coding depends on time, compare the documented duration with the applicable code requirements. Avoid applying one timing rule to every service.
- Claim-to-record consistency. Reconcile the service date, provider, procedure, diagnosis, units and location. Investigate mismatches before release.
- Telehealth details. Where relevant, verify modality, place of service and modifiers against current plan requirements. One payer's configuration is not a universal template.
- Submission and filing evidence. Track the applicable filing deadline and the payer's acceptance response. A batch sent to a clearinghouse is not proof that every claim was accepted by the payer.
After submission: make unresolved work visible
- Rejection versus denial. Separate submissions that failed acceptance from claims denied after adjudication. The correction and follow-up routes can differ.
- Root cause and next action. Translate the remittance or payer response into a verified issue. Record the action needed, not just a generic status such as “pending.”
- Expected versus received payment. Compare payments with reliable contract or fee-schedule information, accounting for valid adjustments and patient responsibility before labelling a variance an underpayment.
- Ownership and deadlines. Assign one accountable owner and a next-action date. Escalate approaching filing or appeal deadlines using the client's agreed process.
Turn the checklist into a working queue
Consider a fictional case: an authorization is saved in the payer portal, but its end date was not transferred into the scheduling workflow. The biller discovers the mismatch after a later visit. The useful finding is not merely “authorization problem.” It is the missing handoff between the authorization record and the scheduled encounter.
| Finding | Evidence to review | Suggested owner | Next action |
|---|---|---|---|
| Unclear authorization balance | Approval plus completed services | Authorization team | Reconcile units before the next applicable visit |
| Documentation incomplete | Encounter record status | Clinical liaison | Request clinician review before claim release |
| Unexplained payment difference | Remittance plus expected allowance | Payment review team | Validate the variance and determine follow-up |
Repeat the review after the corrective action. A queue item closed without evidence can conceal the same problem until the next claim.
Questions RCM teams ask
Is every unpaid claim revenue leakage?
No. Some claims are still within normal processing time; others require valid adjustments. Distinguish processing delays, unresolved risk and confirmed losses before reporting a leakage total.
Can this checklist eliminate denials?
No checklist guarantees payment. Its purpose is to expose preventable gaps and make follow-up more consistent.
Where should a multi-client RCM company begin?
Start with one client and a recurring issue your team can verify. Establish the evidence, owner and measure before extending the process across clients.
Source
[1] CMS: Medical Documentation for Behavioral Health Practitioners. Foundational documentation guidance; consult current payer policies for specific billing requirements.
