Mental Health Billing Mistakes That Slow Down Reimbursement

These problems linger because they rarely start with one claim. In behavioral health, small upstream mistakes compound fast because payer rules, note requirements and the handoff from clinician to biller sit close together. The most expensive medical billing mistakes usually start as operations mistakes.

Plenty of practices work denials one at a time without asking why the same ones keep showing up. A denial can look like a payer problem, but repeat denials often trace to registration gaps, documentation that doesn’t match the claim, or follow-up nobody owns. Without a pattern review, the team works the same denial categories repeatedly, slowing reimbursement and eating staff time.

Sort denials by reason instead and trace each group to the step where it started. Then decide whether the fix belongs with the front desk, the clinicians, the billing queue or payer follow-up. That’s where mental health billing services and revenue cycle management overlap.

Claims age when nobody has a clear rule for what gets reviewed daily, escalated weekly, or needs a payer call versus internal cleanup. They drift through the queue, and leadership loses track of which dollars are still recoverable. It’s common in growing psychology and PMHNP practices where the owner’s still everyone’s backup.

Put one name on each queue, write down when to escalate, and review aging work on a set schedule before it becomes a month-end surprise. If you’re adding providers, check whether some aging claims belong to someone who isn’t fully credentialed and enrolled yet.

Behavioral health claims live or die on the note. When the clinical and billing sides don’t talk, billing finds the problem after the claim’s gone out, and you pay in denials and corrected claims. Nobody can tell whether the notes or the handoff is at fault.

You probably need a routine for finishing notes and a set path from note to claim, not more software. For some teams that includes AI documentation support. Others need standard templates and review expectations before adding any technology.

A lot of practices let the owner, one biller or one office manager become the only person who knows what each payer wants and where the queue stands. That works until they take time off or burn out. Then everything slows down at once.

Write the routine down and put a name on each piece, so billing runs the same when that person’s out.

Codes like 90837 (53+ minutes) and 90833 (the 30-minute psychotherapy add-on to E/M) are unit sensitive. A documented 60-minute session billed as 90834 (45-minute) underbills a real service. The reverse, billing 90837 when documented time supports 90834, is a compliance risk. Fix it in the template: your note tool should require explicit start and stop times, and the billing scrub should reject any therapy code the documented time doesn’t support.

Telehealth billing has two parts, the place-of-service code (POS) and the modifier. Most commercial payers want POS 10 (patient home) or POS 02 (other location), plus modifier 95 for synchronous telehealth. Some Medicaid plans still want the GT modifier.

Miss one and you get a soft denial that ages and gets ignored. Split care psychiatry (med management plus therapy in the same visit) needs the right add-on and separate documentation in the note. Both standardize easily with an agreed matrix.

Most behavioral health contracts allow some no-show or late cancel fee, depending on the payer. Commercial plans usually allow it. Most state Medicaid plans don’t, and several explicitly forbid it, so one rule for every patient either leaves revenue on the table or triggers a compliance flag. The fix is a one-page matrix at the front desk listing each payer, whether the fee’s allowed (yes, no or conditional) and the documentation it needs.

This one’s more about patient experience and collection rates than coding, but it lands in billing. Once the statement goes out 30 days after the visit, collection rates drop sharply. A real-time eligibility tool and a simple front-desk script usually fix it.