Incident-To Billing: When NPs and PAs Can Bill Under the Physician
Every time a nurse practitioner or physician assistant sees an established patient and bills under their own NPI, your practice collects 85% of the Medicare Physician Fee Schedule. That’s a 15% haircut on every single encounter — not because the care was different, but because of how the claim was filed.
Incident-to billing eliminates that haircut. When the requirements are met, NP/PA services can be billed under the supervising physician’s NPI at 100% of the fee schedule. For a busy practice with 2–3 NPPs seeing 15–20 patients per day, the revenue difference is substantial.
But incident-to billing is not a blanket permission. It has 5 strict requirements, and failing any one of them exposes your practice to fraud liability — not just claim denials, but potential False Claims Act violations. This guide covers exactly when it works, when it doesn’t, and how AI can flag non-compliant encounters before you submit.
What Incident-To Billing Actually Means
Incident-to is a Medicare billing provision (42 CFR §410.26) that allows services furnished by non-physician practitioners to be billed under the supervising physician’s NPI — as if the physician performed the service themselves. The rationale: the physician initiated the treatment plan, remains responsible for the patient’s care, and is physically present to intervene if needed.
The financial impact is straightforward:
- NP/PA billing under own NPI: 85% of Medicare Physician Fee Schedule
- NP/PA billing incident-to physician: 100% of Medicare Physician Fee Schedule
- Difference per 99214: approximately $23–$26 per claim
- 15 qualifying encounters/day × $24 × 250 days: $90,000/year per NPP
For a practice with 3 NPs, that’s $270,000 in annual revenue from billing correctly — not from seeing more patients, working longer hours, or changing anything about the clinical care delivered.
The 5 Requirements for Incident-To Billing
All five must be met simultaneously. Failing any single requirement disqualifies the encounter from incident-to billing.
1. The Physician Must Initiate the Treatment Plan
The physician must have personally seen the patient and established the course of treatment for the condition being managed. The NP/PA is executing a plan the physician created — not independently managing a new clinical problem.
What this means in practice: The physician must have a documented encounter in the patient’s record for the same condition, with a treatment plan that the NP/PA is now following or adjusting within parameters the physician established.
Common mistake: A patient sees the NP for the first time for a new problem. Even if a supervising physician is in the building, this cannot be billed incident-to because the physician did not initiate the treatment plan for this specific problem.
2. Direct Physician Supervision
The supervising physician must be physically present in the office suite during the NP/PA encounter. “Direct supervision” under Medicare means immediately available — not in the next building, not on call from home, not “reachable by phone.”
Critical distinction: The physician does not need to be in the exam room. They need to be in the same office suite — available to physically intervene if needed. If the physician steps out for lunch, leaves early, or is in a different clinic location, all incident-to billing during that absence is non-compliant.
Telehealth note: CMS temporarily relaxed direct supervision requirements during COVID-19, allowing virtual presence. As of 2024–2026, the permanent rule requires physical presence in the office suite unless subsequent CMS guidance changes this.
3. Established Patient Only
Incident-to billing applies only to established patients. New patient encounters (99202–99205) cannot be billed incident-to under any circumstances. The rationale: a new patient requires an independent evaluation and treatment plan initiation, which is the physician’s role.
What counts as “established”: The patient must have been seen by the physician (not just the NP/PA) within the past 3 years for any condition in the same practice/group.
4. The Problem Must Be Physician-Initiated
The specific clinical problem being addressed in the incident-to encounter must have been previously evaluated and treated by the supervising physician. The NP/PA is providing follow-up care for an existing treatment plan.
New problem = cannot bill incident-to. If an established patient presents with a brand-new complaint that the physician has never evaluated, the NP/PA must bill under their own NPI for that problem — even if all other requirements are met.
Example: A patient sees the physician for hypertension management in January. In March, the patient returns for a hypertension follow-up and sees the NP. This qualifies for incident-to. But if that same patient also mentions new knee pain during the March visit, the knee evaluation cannot be billed incident-to — only the hypertension follow-up qualifies.
5. Service Must Be Integral to the Physician’s Service
The NP/PA service must be an integral, though incidental, part of the physician’s professional service. This means the NP/PA is functioning as an extension of the physician — carrying out the physician’s treatment plan, not practicing independently.
In practical terms: the documentation should reflect that the NP/PA is managing the patient within parameters the physician established. Medication adjustments within a pre-defined range, monitoring lab values the physician ordered, and follow-up on a treatment the physician initiated all qualify.
When Incident-To Does NOT Apply
These scenarios disqualify incident-to billing regardless of other factors:
- New patients — always bill under the NPP’s own NPI
- New clinical problems on an established patient that the physician has not previously evaluated
- Physician not physically present in the office suite during the encounter
- Hospital, SNF, or home visits — incident-to is an office/clinic benefit only
- NP/PA independently initiating a new treatment plan — even if the physician later co-signs, the plan was not physician-initiated
- Physician has never seen the patient for the condition being managed
The most common compliance failure: a practice bills all NP/PA services incident-to as a blanket policy, without verifying encounter-by-encounter that the 5 requirements are met. This pattern is exactly what Medicare auditors look for.
Medicare vs Commercial Payer Rules
Incident-to is a Medicare-specific billing provision. Commercial payers have their own rules:
- Medicare: 85% for NP/PA under own NPI, 100% incident-to. Strict 5-requirement test.
- Medicaid: Varies by state. Some states recognize incident-to; others credential NPs independently at 100%. Check your state’s Medicaid manual.
- UnitedHealthcare: Generally credentials NPs/PAs at the same rate as physicians for most services. Incident-to is less financially relevant but may still apply for specific contract arrangements.
- Cigna: Recognizes incident-to in some markets; requires NPP credentialing in others. Contract-dependent.
- Aetna: Generally does not apply a payment differential for NPP services — NPs/PAs are reimbursed at 100% under their own NPI for most contracted services.
- BCBS: Varies dramatically by plan and market. Some BCBS plans pay NPs at 85% (making incident-to valuable); others pay at parity.
The revenue impact of incident-to billing depends entirely on your payer mix. If 60% of your patients are Medicare, the 15% differential on NP/PA encounters represents significant annual revenue. If your payer mix is primarily commercial plans with NP parity, the financial impact is minimal.
The Fraud Risk: What Happens When Requirements Aren’t Met
Incident-to billing violations are not mere claim denials. They can trigger:
- Recoupment: Medicare recovers the 15% differential on every non-compliant claim, often going back 3–5 years.
- Civil Monetary Penalties: Up to $11,000 per false claim under the Civil Monetary Penalties Law.
- False Claims Act liability: Treble damages (3x the overpayment) plus $11,000–$23,000 per claim. Whistleblower (qui tam) suits from former employees are common.
- Exclusion from Medicare: In egregious cases, the practice or individual providers can be excluded from Medicare participation.
The risk calculus is clear: $90,000/year in legitimate incident-to revenue is worth pursuing. But $90,000/year in non-compliant incident-to billing can become a $500,000+ liability when Medicare audits go back 5 years with treble damages.
Documentation Best Practices for Incident-To
Compliant incident-to documentation should establish all 5 requirements are met:
- Reference the physician’s treatment plan: “Patient returns for follow-up per Dr. [Name]’s treatment plan initiated [date] for [condition].”
- Confirm physician presence: Many practices note “Supervising physician present in office suite” in the encounter documentation. Some use scheduling software that verifies physician presence.
- Document the problem as established: Reference previous encounters for the same condition. Link to the physician’s prior visit where the treatment plan was initiated.
- Show continuity of the physician’s plan: “Continuing metformin 1000mg BID per plan. A1c improving from 8.2 to 7.4.” This demonstrates the NP is executing, not independently initiating.
- Flag new problems separately: If a new problem arises during the visit, document it separately and bill that portion under the NP’s own NPI. You can split the visit: incident-to for the established problem, NP-billed for the new problem.
How AI Flags Non-Compliant Incident-To Encounters
CodeItRight’s AI engine can analyze NP/PA encounters and flag potential incident-to compliance issues before claims are submitted:
- New problem detection: The AI identifies clinical problems in the note that have no prior physician encounter in the treatment history. These cannot be billed incident-to.
- Treatment plan continuity: The AI checks whether the note references an existing physician-initiated treatment plan or appears to establish a new independent plan.
- Documentation gap flagging: If the note lacks reference to the supervising physician, the prior treatment plan, or the established nature of the problem, the AI flags it as potentially non-compliant for incident-to billing.
- MDM analysis: The AI ensures the E/M level billed is supported by the documentation, regardless of whether it’s billed incident-to or under the NPP’s own NPI.
Catching one non-compliant incident-to claim per day saves $24 in potential recoupment — but more importantly, it prevents the pattern of non-compliance that triggers full-scale Medicare audits. One bad claim is a refund. A pattern of bad claims is a False Claims Act investigation.
Revenue Optimization Strategy
The practices that maximize incident-to revenue without compliance risk follow this workflow:
- Physician sees all new patients and new problems first. This establishes the treatment plan that enables future incident-to billing.
- NP/PA handles follow-ups for physician-initiated problems. These qualify for incident-to when the physician is present.
- Scheduling ensures physician presence. If the physician is out, all NP/PA encounters that day bill under the NP/PA’s own NPI. No exceptions.
- New problems during follow-up visits are split. The established problem bills incident-to; the new problem bills under the NP/PA. This requires modifier 25 on the separately billed E/M if a procedure is also performed.
- AI pre-submission review flags any encounter that doesn’t meet all 5 requirements. Fix the billing before it goes out — not after an audit notice arrives.
The Bottom Line
Incident-to billing is legitimate, valuable, and widely underutilized by practices that either don’t understand the rules or fear the compliance complexity. The 15% Medicare differential on NP/PA encounters adds $60,000–$270,000 annually depending on your NPP count and patient volume. But the requirements are absolute: physician-initiated plan, established patient, established problem, direct supervision, integral service. Miss one, and you’re not just losing the 15% — you’re risking treble damages on every non-compliant claim. AI-powered compliance checking turns incident-to from a risk into a reliable revenue stream.