HCPCS code T2033 – Unspecified waiver residential care

Key takeaways

T2033 is an HCPCS Level II T-code for residential care NOS under Medicaid HCBS waiver programs.

The billing unit is per diem, so one unit equals one calendar day of residential care.

Claims require active waiver enrollment, a current person-centered service plan, and daily notes matching the billed units.

Reach for T2033 only when no named waiver code in the T2012-T2041 range describes the service.

Pabau’s claims management software tracks HCPCS codes, prior authorization documents, and denial workflows in one record.

HCPCS code T2033: Official descriptor and code details

HCPCS code T2033 belongs to the T2012-T2041 range of waiver services codes maintained by the Centers for Medicare and Medicaid Services (CMS).

That range covers home and community-based services authorized under state Medicaid HCBS waiver agreements. T2033 is the catch-all code for residential care with no more specific descriptor elsewhere in the range.

The NOS qualifier is intentional. T2033 applies precisely when the residential care provided does not fit a named code in the waiver range.

Verify the full CMS HCPCS Level II code set annually, since T-code descriptors and program applicability change with each fiscal year update. CMS does not set the money side of this code. Rates, unit definitions, and covered populations follow each state waiver agreement.

What services does T2033 cover?

T2033 covers the daily residential care provided to a Medicaid waiver participant who lives in a community-based residential setting approved under that state’s HCBS waiver. The NOS designation means the service bundle does not match a more specifically described residential care code in the T2012-T2041 range.

Services captured under T2033 usually include overnight supervision, help with activities of daily living (ADLs), health monitoring, and non-skilled supportive care.

The residential site must be an approved waiver-funded setting. A group home, a supported living arrangement, or a similar community-based residence qualifies; a nursing facility or hospital does not.

• Overnight residential supervision: staff present to monitor and assist the participant through the night
• ADL assistance: help with bathing, dressing, grooming, meal preparation, and mobility within the residence
• Health monitoring: routine observation of the participant’s condition and reporting changes to the care team
• Behavioral support: implementation of behavior support strategies documented in the person-centered service plan
• Non-skilled personal care: supportive tasks within the residential setting that do not require a licensed clinical credential

The HCBS waiver context is the defining condition, and T2033 cannot be billed outside a waiver program. If the participant is not enrolled in an approved state HCBS waiver on the date of service, the code does not apply.

That holds regardless of the setting or the services delivered. Check AAPC’s HCPCS Level II code range reference for additional descriptor context and coding guidance.

What T2033 does not cover: Exclusions and limitations

Several service types and settings fall outside the scope of HCPCS code T2033. Billing T2033 for excluded services is a frequent cause of claim denial and audit exposure.

• Skilled nursing services: nursing care, wound care, IV administration, and therapy require separate CPT or HCPCS codes
• Institutional settings: care in a nursing facility, psychiatric residential treatment facility, or ICF/IID is billed under different code sets
• State plan services: services covered under the standard Medicaid state plan rather than an HCBS waiver are not billed with T-codes
• Day services billed separately: where daytime habilitation happens at another site under its own code, T2033 covers only the residential portion
• Transportation: non-emergency medical transportation has its own HCPCS codes and is never bundled with T2033

The most consequential exclusion is residential habilitation with a named descriptor. Where a state’s waiver uses T2016 (habilitation, residential, waiver; per diem) for the services delivered, T2033 is the wrong selection.

Confirm which code your state Medicaid program has authorized for the specific service type before defaulting to the NOS code.

How to bill T2033: Per diem billing requirements

Per-diem billing means one unit of T2033 equals one calendar day of residential care. A participant who receives residential care for 28 days in a month generates 28 billable units. Do not prorate for partial days or adjust units based on staffing ratios; the unit is the day, not the hour.

Several claim fields carry the audit risk on a T2033 line, and payers review them closely. Refer to your state Medicaid billing manual for the exact CMS-1500 or 837P field requirements, as the specifics vary by program.

Getting those six fields right on the first submission is the cheapest way to protect T2033 revenue. A reworked claim costs staff time that the per-diem rate was never priced to cover.

Documentation requirements for T2033

Thin documentation is the primary reason T2033 claims fail on audit. The record has to show three things. The participant was enrolled in an active HCBS waiver, the service plan authorized residential care, and staff delivered that care on each billed day.

• Current person-centered service plan (PCSP): authorizes T2033 with specified hours, setting, and funding source, current at the time of service
• Waiver enrollment verification: proof the participant held active waiver status on each billed date, since a lapse voids the claim
• Daily service notes: a note for each calendar day billed, naming the staff member, the residential period, and any significant observations
• Provider credentialing records: the rendering provider or agency must be enrolled with the state Medicaid program as an approved waiver provider
• Prior authorization documentation: the authorization number, approval dates, and authorized units on file and referenced on the claim

Documentation in residential settings must be contemporaneous, meaning written at or near the time of service rather than reconstructed later. Retrospective documentation is a red flag for Medicaid auditors and may be treated as falsification in enforcement actions. A structured daily log template, adapted for waiver residential services, keeps the record consistent across every staff member on the roster.

Prior authorization and payer requirements for T2033

Most state Medicaid programs require prior authorization (PA) before T2033 services can be billed. PA approval specifies the authorized number of days, the waiver program, the approved setting, and the service start and end dates. Billing beyond the authorized period or for more days than approved is a billing error, not a gray area.

The authorization process typically flows through the state Medicaid agency or its contracted managed care organization (MCO). The referring care coordinator or support broker submits the request as part of the HCBS waiver service planning cycle.

Providers should not begin billing T2033 until written authorization is received and on file. Running insurance eligibility verification before each service period confirms active waiver enrollment and catches lapsed authorizations before services are rendered.

Managed Medicaid plans add another layer. Each MCO may run its own PA form, submission portal, and review timeline, separate from the state fee-for-service process.

Providers serving participants across several MCOs need a system that tracks PA status by plan and by participant, not just by code. Contact your state Medicaid agency or MCO for the exact process that applies to your waiver program.

T2033 vs. related residential care codes

Four codes are regularly confused with T2033: T2016, T2031, T2048, and H2033. Each one covers a different service type or setting. Picking the wrong one usually produces a denial, or a recoupment demand once an audit reaches the claim.

The decision runs on one question: does your state waiver name a code for the specific type of residential care being delivered? Use that named code where one exists. Where no named code fits, T2033 is the correct selection. Defaulting to T2033 without checking for a more specific T-code is a shortcut that payers flag during claims review.

Common T2033 claim denial reasons and how to avoid them

T2033 denials cluster around five root causes. Knowing which adjustment reason code (CARC) maps to each one helps billers respond correctly and prevent a repeat.

• Missing or expired prior authorization (CARC 15 / 197): the claim cites an authorization that expired, has not taken effect, or was never obtained. Secure the PA before the service period opens and track expiry dates in your billing system.
• Lapsed waiver enrollment (CARC 27 / 30): the participant held no active HCBS waiver status on the billed date. Verify enrollment at the start of each service month, not only on admission.
• Incorrect place of service (CARC 5): the POS code does not match the approved residential setting type. Confirm the POS code your Medicaid payer requires for this waiver program before billing.
• Insufficient documentation on request (CARC 16 / 50): the payer asks for records and the provider cannot produce contemporaneous daily notes. Documentation discipline at the point of care is the only reliable fix.
• Units exceed authorized limit (CARC 119): the billed days run past the number approved on the PA. Track authorized units against billed units as the month progresses.

Every one of those five failures is catchable before submission, and the sequence below is the order to catch them in. Billers decoding a remittance line can start from our reference on denial codes. From there, map each CARC back to the step that prevents it.

Appeals for T2033 denials should include the waiver enrollment record, the PCSP page authorizing residential care, the PA documentation, and the relevant daily service notes.

A denial on documentation grounds is rarely won without all four. Refer to the CMS HCPCS code list and your state Medicaid billing manual to confirm current coverage criteria before submitting an appeal.

State-specific T2033 rates and fee schedule variations

T2033 reimbursement rates are set by each state Medicaid agency, not by CMS, and they vary substantially. A state running a supported living waiver may pay a different daily rate than a neighboring state running an intellectual disability waiver. The services can look identical on paper.

Several factors shape state-level rate variation for T2033:

• Waiver type: rates differ between an aged and disabled waiver, a developmental disabilities waiver, and a brain injury waiver even within the same state
• Setting level: some states tier T2033 rates by service intensity, with higher staff ratios attracting higher per-diem reimbursement
• Managed care vs. fee-for-service: MCO-contracted rates may differ from the state fee-for-service rate, so obtain the applicable MCO fee schedule directly
• Annual rate updates: state fee schedules change at least annually, often on a state fiscal year that differs from the federal one

To find the current T2033 rate for your program, go straight to your state Medicaid agency’s provider billing manual or fee schedule page. State Medicaid billing portals are the authoritative source. A neighboring state’s rate or a commercial coding database is no substitute, because those figures may be stale or tied to a different waiver.

How Pabau keeps T2033 claims and their documentation together

In most residential waiver programs the claim and the evidence behind it live in separate systems. Enrollment sits with the care coordinator, the PA letter sits in a shared drive, and the daily notes sit in a logbook at the residence. When a payer asks for records on a 30-day claim, someone spends an afternoon assembling them.

Pabau is practice management software that keeps the billing record and the clinical record in the same place. Our claims management software stores the HCPCS code, the authorization number and dates, and the daily documentation against one patient record. Staff write the day’s note in the same system that later produces the claim line.

The result is a shorter path from a denial to an answer. Instead of chasing four documents across three systems, a biller opens the patient record and reads the authorization and the notes side by side. That also makes the monthly unit reconciliation a review rather than a rebuild.

Keep waiver billing and its paperwork in one record

Pabau stores prior authorization dates, daily service documentation, and HCPCS claim lines against a single patient record. Residential providers can answer a payer records request without rebuilding the month.

Book a demo

Conclusion

T2033 is a simple code with a complicated claim. The descriptor takes a minute to understand, but the per-diem unit means every single billed day has to be defensible on its own. That is why the denial rate on this code tracks process discipline far more closely than coding knowledge.

So the work worth doing is upstream. Run the five checks before submission and keep each daily note written on the day. Do that, and filing an appeal becomes the exception rather than the routine. Book a demo to see how Pabau keeps waiver authorization records and daily documentation attached to the claims they support.

Continue your research

Looking to build a consistent pre-submission billing process? Medical billing fundamentals covers the end-to-end claim lifecycle from service delivery to payment posting.

Want to reduce claim rejections before they happen? What makes a clean claim outlines the elements payers check on first-pass review and where most claims fall short.

Frequently asked questions