How Do Practices Win Enough Authorized Testing Hours and Bill 96130 to 96139 Units Without Denials?

How to Get the Testing Hours Approved and the Units Paid

The goal is the full clinically necessary battery authorized before testing begins, and every 96130 to 96139 unit paid on the first claim. Here is what does that, move by move.

1. Build the Request to Justify Every Hour, Not Just Ask for Them

A testing request that names a number of hours without defending it is a request that gets trimmed to the payer’s default cap. The fix is to write the justification the way the policy reads it: the referral question, the clinical indication, the specific instruments planned, and why the battery requires the hours it requires. When the request explains the battery, the reviewer has something to approve against; when it just states a number, the reviewer falls back to the policy maximum. The hours you defend are the hours you keep.

2. Map Your Units to the Payer’s Own Code-Family Caps

Every payer publishes its own maximums per code family: how many units of the base evaluation code, how many of the per-hour add-on, how many technician units, per date and per fiscal year. Requesting outside those caps invites an automatic trim; requesting inside them, with the rationale attached, is what gets approved. Before a single unit is requested, pull the plan’s testing policy and map the battery to its actual caps, so the request lands inside the box the reviewer is checking rather than outside it.

3. Sequence Base and Add-On Codes Correctly on the Claim

Half the lost money is not the auth, it is the claim. Add-on codes like 96133, 96137, and 96139 deny when they hit a claim without the base code that anchors them, or when they are sequenced out of order. The claim has to carry the base evaluation code and the add-on units together, in the right order, mapped to the units actually authorized. Getting the sequencing right the first time is the difference between a clean payment and an add-on denial on hours that were fully worked and fully authorized.

4. Appeal the Trim Before the Write-Off Is Booked

When the payer approves three hours against a request for eight, that gap is not automatically a write-off; it is an appeal that has not been filed yet. The moment the partial approval lands, the corrected justification goes back with the clinical indication and instrument rationale the first request lacked, mapped to the plan’s own criteria. And when an add-on unit denies for sequencing, it is corrected and resubmitted, not written off. Tracking every partial approval and unit denial in one place is what keeps worked hours from quietly becoming lost revenue.

5. Hand Testing Auth and Unit Billing to a Dedicated Team

Practices that stop writing off testing hours do it by handing the whole chain to a dedicated team: remote specialists who build the hour justification, map the units to each payer’s caps, sequence the claim correctly, and appeal the trims, live in 1 to 2 weeks. The clinicians go back to testing and interpreting instead of fighting policy caps, a trained backup covers every gap, and the write-off pile stops growing. Below is what it sounds like when nobody owns this yet, in providers’ own words.

Why This Keeps Happening

If the testing is clearly necessary, why does the payer only approve part of it? Because the reviewer is not judging clinical need in the abstract; they are checking the request against a published policy that caps hours and units per code family and per fiscal year. Guidance from the American Psychological Association on psychological and neuropsychological testing billing is explicit that authorization requests must specify the clinical indication, the specific tests planned, and the rationale for the number of hours and units requested. When a request omits that rationale, the reviewer has nothing to approve the extra hours against, and defaults to the policy maximum. The trim is a documentation gap, not a clinical disagreement.

The unit denials are a separate trap on the claim side. Codes 96130 and 96132 are base evaluation codes billed for the first hour, and 96131, 96133, 96137, and 96139 are add-on codes for additional time. Payer edits deny add-on units that arrive without the anchoring base code on the same claim, and many plans cap technician-administered units per encounter. So a fully authorized battery can still lose money at billing if the codes are sequenced wrong. Closing that gap between what was authorized and what actually gets paid is exactly what an AI prior authorization workflow with human oversight is built to do.

And the cost compounds because the two failures stack. A trimmed authorization means hours worked and written off; a sequencing denial means hours authorized and still unpaid. On a neuropsych practice running full batteries all week, those two leaks together can turn a clinically busy schedule into a financially thin one, while the clinician has no idea the money left on partial approvals and add-on denials that nobody appealed. Working that whole chain, auth through clean claim through appeal, is the kind of end-to-end ownership that dedicated revenue cycle management support is built to provide.

Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:

The Solution

So what does “someone whose whole job it is” look like on a neuropsych battery? It starts at the request. The specialist builds the authorization to justify the hours the way the payer reads them: the referral question, the clinical indication, the specific instruments, and why the battery requires the time it requires, mapped to the plan’s published caps per code family. The reviewer gets a request that explains itself, so the default trim to the policy maximum has nothing to fall back on. That is where the hours are won, before a single test is administered, and it is the core of what dedicated psychiatry prior authorization support does for testing.

Then the claim, where the second leak lives. The specialist sequences the base evaluation code and the add-on units together and in order, mapped to the units actually authorized, so 96130 through 96139 pay on the first pass instead of denying for a missing base code. And when a request is trimmed or a unit denies anyway, they work it as an appeal, not a write-off: the corrected justification goes back, the sequencing is fixed and resubmitted, and the earned hours get recovered instead of expiring in the write-off column.

Behind all of it, AI drafts the first pass and a credentialed human verifies. The workflow assembles the hour justification, maps the units to the caps, and flags the sequencing before the claim goes out; a person confirms the clinical rationale is right and owns every appeal. Every security control that protects the testing and chart data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving behavioral health documentation through an auth-and-billing workflow is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced team win your testing hours better than your own staff? Because reading payer testing policies, defending hour justifications, and sequencing add-on codes is their entire day, not the thing they squeeze between evaluations. The people working your auths and claims are credentialed medical professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, trained in US behavioral health testing and prior authorization workflows. They know what each payer wants to see in a testing request, how the code-family caps actually read, and how to sequence a claim so the add-on units pay. That is not a generalist task handed to whoever is free; it is a specialty.

We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical practice is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and no one on our side goes out without a trained backup already inside your workflow, so a testing auth never sits because the one person who handles it is on vacation.

And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; the full detail lives in our HIPAA and security posture.

Put the routine and the people together, and a specific list of things simply stops happening.

How We Permanently Fix the Process

A person alone is not the fix, and neither is a bot alone. The fix is a documented testing-auth-and-billing workflow: which payers cap which code families at what maximums, what each one wants in an hour justification, how the fiscal-year rules read, and the exact claim sequencing for base and add-on codes, all written down and worked the same way every time. Before we take a single testing auth for a new practice, we chart your top payers’ testing policies and your recent trims and unit denials so we can see where the money is actually leaking, and we build the workflow against that, not a generic template.

From there the workflow becomes a living playbook rather than knowledge in one biller’s head. It records how each payer wants a battery justified, the unit caps per code family, the sequencing rules that keep add-on units from denying, and the appeal path for every partial approval. It is written down, kept current as payers update their testing policies, and owned by the team. When your specialist is out, a trained backup works the same playbook the same way, so a trimmed auth or a denied unit never waits for one person to come back.

That is the difference between reworking this month’s write-offs and fixing the process for good, and it is what a dedicated prior authorization partner actually buys you. A biller leaving used to mean the testing auths got sloppy and the write-offs climbed again. Under this model the workflow keeps running, the playbook stays, the backup steps in, and a partial approval stops being a silent write-off.

The Whole Thing in Four Sentences

Practices win enough authorized testing hours and bill 96130 to 96139 cleanly by treating the authorization and the claim as one connected job. The hours get trimmed when the request omits the instrument list and hour rationale the payer’s policy reads against, and the units deny when the add-on codes are billed without the base code on the same claim. Requesting hours without justifying them, billing add-ons as they come, and writing off partial approvals all fail the same way. The fix is to justify every hour to the payer’s criteria, map units to the code-family caps, sequence the claim correctly, and appeal every trim before it is booked. A multi-clinician psychiatry and psychology group runs exactly this model with us today, names withheld, no patient data shown.

If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.

Ready to stop writing off testing hours? Try us risk free: two weeks, your real testing auth and unit-denial queue, dedicated specialists building the justifications and sequencing the claims, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.

Written By

Dan Nandan

Founder and CEO, Staffingly, Inc. · Piscataway, NJ

Dan Nandan has spent 25+ years in IT consulting and healthcare BPO, was among the first in the US to build an RPO/BPO delivery network in India, and has been featured in Computerworld. He runs the operations and the dedicated virtual teams behind the workflows on this page; the team-voice answers above come from the remote specialists who work them every day.

Connect on LinkedIn

Where the Claims on This Page Come From