Superbills for Therapists: What They Are and When to Use One

Short answer: a superbill is an itemized receipt a therapist gives a self-pay or out-of-network client, which the client then submits to their own insurance company for reimbursement. The practice never files a claim. The client does, using the superbill as the supporting documentation.

Some of what follows is standard billing mechanics. The rest comes from somewhere Oasys is lucky to sit: Oasys runs at the infrastructure layer of working practices, and out-of-network billing questions come up constantly in conversations with practice owners who serve a mixed caseload of in-network and self-pay clients.

What a superbill actually is

A superbill is not a claim. A claim is what a practice submits directly to a payer for direct reimbursement, on behalf of the client, under a contract the practice holds with that payer. A superbill is what a practice hands to the client, who then files it themselves with their own insurer for possible reimbursement under their out-of-network benefits.

The distinction matters because the practice's obligations are different in each case. A claim requires the practice to be enrolled with that specific payer for the claims transaction. A superbill requires none of that. It only requires accurate documentation of what happened, since the client's insurer is the one deciding whether and how much to reimburse.

Oasys treats both documents as outputs of the same underlying session record rather than two separately maintained processes, so a practice serving a mixed in-network and self-pay caseload is not running two disconnected billing systems.

What has to be on a superbill

A superbill needs to carry the same core facts a claim would, even though it travels a different path:

Client name and date of birth.

Provider name, credentials, and NPI (National Provider Identifier).

Date of each service and the CPT code that describes it (90837, 90834, 90832 for individual therapy; 90853, 90847, 90846 for group and family sessions).

The ICD-10 diagnosis code supporting medical necessity for the service.

The fee charged for each service, and what the client has already paid.

Practice tax ID or NPI, and often a license number, depending on the payer.

Missing any of these is the most common reason a client's insurer rejects a superbill and asks for a corrected one, which delays reimbursement and usually lands back on the practice to fix. Oasys pulls the CPT code, ICD-10 diagnosis, and provider NPI for a superbill from the same signed note that would support a direct claim, so none of these fields require separate manual entry.

When a practice actually needs superbills

Any practice with self-pay or out-of-network clients who want to seek their own reimbursement needs the capability, even if it is used rarely. A fully in-network practice with contracted payers for every client may never generate one. A practice built around a private-pay or hybrid model generates them constantly, sometimes as the default document handed out after every session rather than a claim at all.

Other platforms may be built differently, and treat superbills as a separate report generated outside the normal documentation and billing flow. Oasys already generates a CPT-coded claim directly from the signed note for every session, including the diagnosis code and provider information a claim requires, which is the same underlying data a superbill needs. The difference between the two is who the document goes to, not what has to be on it.

Superbills versus claims versus statements

Three documents get confused constantly, and they serve different purposes. A claim goes from the practice to a payer, for direct reimbursement to the practice. A superbill goes from the practice to the client, for the client to seek reimbursement from their own insurer. A statement or invoice goes from the practice to the client, showing what is owed or was paid, with no insurance component at all.

A practice can generate all three from the same underlying session data. What changes is the destination and the purpose, not the clinical facts behind them. Oasys generates all three from the same signed note rather than three separately built documents, so a practice does not maintain a parallel data-entry process for whichever one a given client needs.

Common superbill mistakes

Missing or incorrect ICD-10 codes. A superbill without a supported diagnosis code gets rejected by the client's insurer as readily as a claim would.

Vague CPT coding, like billing every session as 90837 regardless of actual length. The same time-based rules that apply to insurance claims apply to superbills, because the client's insurer is checking the same thing a direct payer would.

Missing NPI or tax ID. A superbill is only as useful as the identifying information a client's insurer needs to process it.

Inconsistent fees between what was charged and what the superbill states. Any mismatch is a red flag to the reviewing insurer and a delay for the client.

Each of these mistakes comes from the superbill being assembled separately from the note it should match. Oasys avoids that gap by generating the superbill's fields from the same record a clinician already signed.

What to ask before you commit to a platform

Can the system generate a superbill from the same documentation used for a regular claim, or does it require separate manual entry?

Does the superbill automatically carry the correct CPT and ICD-10 codes from the signed note?

Can a client request a superbill for a past date of service without staff manually reconstructing it?

Oasys answers the first two by design, since the superbill and the claim draw from the same signed note rather than separate entry paths.

How Oasys handles it

Oasys draws superbill-ready information (CPT codes, diagnosis codes, provider NPI, and fees) from the same signed documentation used for insurance claims, rather than a parallel process built only for direct-billed clients. Pricing is $80 per clinician per month on an annual contract, with no separate fee for out-of-network documentation.