A claim comes back denied. The visit was clean. The note was signed. The patient was on video for 30 minutes. The code was right.
So why did the payer say no?
For many telehealth practices, the answer is not in the claim at all. It sits in the provider file. A location was never added. A license was never linked to a payer. A group roster was never updated. The claim was only the place where the gap became visible.
That is why telehealth claim denials credentialing issues are so hard to fix with edits alone. You can change the place of service code, add a modifier, and resubmit. If the enrollment record still does not match, the claim will fail again.
This guide connects each common denial to its root cause. You will see how POS 02 and POS 10 work, where modifier 95 and modifier GT fit, what CARC 242 and CARC B7 really signal, and how enrollment mismatches create denials that look like coding errors. You will also get a clear workflow to prevent them.
Why Telehealth Denials Often Start Before the Claim
Telehealth added new variables to an old process. A traditional visit has one provider, one office, and one patient in the same room. A telehealth visit can have a provider in one state, a patient in another, and a group billing from a third address.
Payers check each of those pieces. They compare the claim against three sources:
- The provider’s enrollment and credentialing record
- The group contract and roster
- The patient’s plan rules for virtual care
If any piece disagrees with the claim, the payer’s system flags it. The denial code then points to the symptom, not the cause.
Here is a simple example. A New York psychiatrist sees a patient by video. The claim goes out with POS 10 and modifier 95. It denies with a message that the provider is not eligible for payment on the date of service. The billing team checks the code and the modifier. Both are right. The real issue is that the psychiatrist was credentialed with the payer under a different group number. The payer never linked the provider to the billing group for that date.
No coding fix would have worked. Only an enrollment fix would.
The three layers of a telehealth claim
Think of every telehealth claim as three layers stacked together.
The clinical layer. This covers the service, the diagnosis, and the documentation.
The coding layer. This covers CPT codes, place of service, and modifiers.
The enrollment layer. This covers licensure, credentialing, payer enrollment, rostering, and service location data.
Most billing teams audit the first two layers well. The third layer gets less attention, and it causes a large share of repeat denials. A strong denial program checks all three before a claim leaves the building.
POS 02 vs POS 10: What Each Code Means and Why It Matters
Place of service codes tell the payer where the patient was during the visit. Two codes cover most telehealth billing.
POS 02 means telehealth provided other than in the patient’s home. The patient might be at a clinic, a school, a workplace, or another facility. The provider is delivering care by two-way technology.
POS 10 means telehealth provided in the patient’s home. This includes a private residence where the patient receives the service.
The difference sounds small. It is not. CMS uses these codes to set payment rates. Under the Medicare Physician Fee Schedule, POS 10 has generally been paid at the non-facility rate, while POS 02 has been paid at the facility rate. Commercial payers and Medicaid plans may follow their own rules. Some accept both codes. Some require only one. Some still expect the POS that matches the provider’s usual office location, paired with a telehealth modifier.
How a POS error turns into a credentialing problem
A wrong POS code is a coding issue. A POS code that does not match the provider’s enrolled service locations is a credentialing issue.
Here is how that happens. A payer’s system holds a record of where each provider is approved to deliver care. If the record lists only a physical office, and the claim arrives with a telehealth POS, the edit may fail. The system may not know the provider is approved for virtual care. Or the home address used for telehealth may never have been reported.
This is why telehealth service location credentialing matters. Payers and Medicare Administrative Contractors care about where the provider practices from, and some require that location to be on file.
Common POS mistakes to watch for
- Using POS 11 for a video visit because the template defaults to the office
- Using POS 02 when the patient was at home, or the reverse
- Applying one POS code to every telehealth claim in the practice
- Ignoring plan-specific rules for behavioral health or Medicaid
- Letting the EHR choose the POS code without a review rule
Each of these can trigger a denial. Some also cause underpayment, which is harder to spot. A claim that pays at the wrong rate may never be flagged. Over a year, that gap adds up.
A quick comparison
| Item | POS 02 | POS 10 |
| Patient location | Not at home (clinic, school, work site) | Patient’s home |
| Typical use | Remote visit to a non-home setting | Home-based virtual visit |
| Medicare payment rate (since 2024) | Facility rate | Non-facility rate |
| Common denial trigger | Patient was at home, or POS not accepted by plan | Payer does not recognize POS 10 for the service |
| Credentialing link | Location data and provider status must match payer records | Same, plus home-based practice site reporting where required |
Always confirm the current rule with each payer. These policies have changed more than once, and they differ across plans.
Telehealth Modifiers: 95, GT, and Others
Modifiers add detail to a CPT code. For telehealth, they tell the payer how the service was delivered.
Modifier 95 means a synchronous telemedicine service delivered through real-time audio and video. It is the most widely used telehealth modifier across commercial plans and many Medicaid programs.
Modifier GT means via interactive audio and video telecommunication systems. It is older. Medicare stopped requiring it for most professional claims, but some payers and some provider types still ask for it. Critical access hospitals billing under certain methods have used it as well.
Other modifiers can apply depending on the service. Examples include modifier 93 for audio-only services and modifier FQ for certain Medicare behavioral health audio-only visits. Rules shift often, so each payer’s policy should be checked at the time of service.
Why the wrong modifier leads to denials
A modifier denial often shows up as CARC 4, which says the procedure code is inconsistent with the modifier used or a required modifier is missing. It can also appear as a rejection from the clearinghouse before the payer sees the claim.
Most of these are coding fixes. Add the right modifier, resubmit, and the claim pays.
The credentialing connection appears in a second way. Some payers load telehealth eligibility into the provider record. If the provider is not marked as approved for virtual services, then modifier 95 triggers a denial even though the modifier is correct. The payer’s system sees a telehealth claim from a provider who has no telehealth flag.
That is a good rule of thumb. If a correct modifier still denies, check the enrollment file.
Modifier use by payer type
- Medicare: Follows CMS rules for the list of covered telehealth services and the required modifiers. Policies have been changed by Congress through temporary flexibilities, so confirm the current status on the CMS telehealth page.
- Medicaid: Varies by state. New York Medicaid has its own telehealth policy, and other states differ.
- Commercial plans: Each plan sets its own rules. Many accept modifier 95. Some require GT. Some want a specific POS and modifier pair.
When a practice bills across states, the number of rule sets grows quickly. A written payer matrix saves hours of rework.
CARC 242 and CARC B7: What They Signal
Denial codes are the language payers use to explain a result. Reading them correctly saves time. Two of them point straight to credentialing.
CARC 242: Services not provided by network or primary care providers
CARC 242 tells you the service was billed by a provider outside the plan’s network, or the plan did not recognize the provider as in network for that service.
For telehealth, this often happens in three situations.
- The provider is credentialed with the payer, but not linked to the billing group’s contract.
- The provider is in network for office visits, but not for virtual visits under that plan.
- The provider is licensed and enrolled in one state, and the patient is located in another where the provider has no network status.
None of these is a coding mistake. Each is a network status gap. The fix is to confirm the provider’s effective date, group affiliation, and service locations with the payer, then request a correction if the record is wrong.
CARC B7: Provider not certified or eligible for this service on this date
CARC B7 says the provider was not certified or eligible to be paid for this procedure or service on the date of service.
This one is often a date problem. The provider may have been approved after the visit took place. The credentialing effective date may be later than the first claim date. Or a recredentialing cycle lapsed, and the provider fell off the roster for a stretch.
Related codes can also appear on telehealth denials:
- CARC 185: The rendering provider is not eligible to perform the service billed.
- CARC 170: Payment is denied when performed by this type of provider.
- CARC 5: The procedure code or bill type is inconsistent with the place of service.
- CARC 16: The claim lacks information or has errors.
A full guide to these messages is available in this overview of insurance denial codes. Use it as a reference while you triage.
A denial code map
The table below links common telehealth denial codes to the most likely root cause. Use it as a starting point, not a final answer. Always read the remark codes and the payer’s own explanation as well.
| Denial code | What the payer is saying | Most likely root cause | First fix |
| CARC 242 | Not provided by a network provider | Provider not linked to group or plan network | Verify participation and group affiliation |
| CARC B7 | Provider not eligible on date of service | Effective date after the visit, or lapsed credentialing | Check effective dates and recredentialing status |
| CARC 185 | Rendering provider not eligible for this service | Provider type or specialty not approved for telehealth | Confirm provider type and taxonomy on file |
| CARC 170 | Denied for this type of provider | Wrong provider classification in payer system | Request a record correction |
| CARC 5 | Code inconsistent with place of service | POS mismatch with enrolled service location | Match POS to patient location and payer rules |
| CARC 4 | Modifier missing or inconsistent | Coding error, or telehealth flag missing in payer file | Add modifier, then verify telehealth flag |
Enrollment Mismatches That Cause Telehealth Denials
Enrollment mismatches are the most common hidden cause. They happen when the information on the claim does not match the information in the payer’s provider file. Telehealth makes these mismatches more likely because more details are involved.
Out-of-state provider denials
Telehealth lets a provider treat patients across state lines. Payers still apply state rules. A claim for a patient in another state can deny for several reasons.
The provider may not hold a license in the patient’s state. The payer may not have the provider listed in the patient’s state network. The plan may only cover providers in its approved service area.
Many practices assume that one license and one enrollment cover every patient. That is rarely true. Licensing and payer credentialing are separate steps. Our guide on multi-state credentialing for telehealth explains how to plan for each state and each payer.
A licensure compact can help with the license side, but it does not replace payer credentialing. A provider can hold a compact privilege and still be out of network with a plan.
Rendering provider and billing provider confusion
Every claim names a rendering provider and a billing entity. Telehealth often adds a twist. A provider may work for a group but see patients from home. The claim must still show the group as the billing provider and the individual as the rendering provider.
If the group NPI, individual NPI, or tax ID does not match the payer’s record, the claim denies. This also happens when a provider joins a group and the roster update is delayed. The provider is credentialed, but the payer has not linked them to the group yet.
Service location mismatches
Payers collect practice locations during enrollment. When a provider works from home, a few questions come up. Is the home address reported? Does the payer require it? Does the claim list the office address instead?
The answer depends on the payer. Medicare has made changes to how telehealth providers report practice locations, and those rules have been adjusted over time. Commercial plans vary. The safe approach is to ask each payer what it needs and to record the answer in your credentialing tracker.
Taxonomy and specialty mismatches
A provider’s taxonomy code tells the payer their specialty. If the claim uses one taxonomy and the payer file shows another, a denial can follow. This is common when a provider has more than one specialty or changed their focus after enrollment.
Date and status mismatches
Three date problems cause many B7 style denials:
- The credentialing effective date is after the date of service
- The recredentialing deadline passed without renewal
- A CAQH attestation expired and the payer paused the record
Each of these is preventable with a calendar and a tracking system.
Real Scenarios: How Denials Trace Back to Credentialing
Examples make these patterns easier to spot. The scenarios below are composites based on common cases.
Scenario 1: The new hire who was never rostered
A group practice in New York hires a licensed clinical social worker. She completes credentialing with a major commercial plan and receives an approval letter. The group starts billing her visits the next week.
Every claim denies with CARC 242.
The cause is simple. The plan approved her as an individual, but the group never submitted a roster update. The payer’s system did not link her NPI to the group contract. Once the roster was updated, the claims were reprocessed. The group lost about six weeks of cash flow while waiting.
The difference between credentialing and rostering is explained in more detail in this guide on adding a provider to an insurance contract, and it deserves a step in every onboarding checklist.
Scenario 2: The correct POS with the wrong location
A solo therapist works from a home office and sees patients by video. Her claims use POS 10 and modifier 95. The first batch pays. The second batch denies for a location mismatch.
The payer had her enrolled at a prior office address that she closed. Claims were matching against that old location. A simple update to the practice location file solved it. The coding was never the issue.
Scenario 3: The patient who traveled
A psychiatrist licensed in New York sees an established patient by video. The patient is vacationing in another state that day. The claim denies as out of network.
The provider has no license or payer enrollment in the state where the patient was located. Some plans cover the visit based on the patient’s home plan state. Others do not. The practice needed to check both licensure rules and plan policy before the visit. Now the front desk asks patients to confirm their location at check-in, and the clinician documents it in the note.
Scenario 4: The expired CAQH profile
A specialty group bills telehealth for a cardiologist. Claims deny with a code indicating the provider is not eligible. The cause is an expired CAQH attestation. The payer paused the provider’s record until the attestation was renewed.
A reminder system would have caught it 30 days earlier. Our guide on credentialing mistakes covers this and other gaps in more detail.
Payer-Specific Pressure Points
Different payers create different problems. A few patterns appear often.
Medicare
Medicare rules for telehealth have been shaped by statute and by CMS guidance. Many flexibilities introduced during the public health emergency have been extended in stages, and some have lapsed or been restored. Coverage lists, eligible provider types, and originating site rules can change with each extension. Check the CMS telehealth page for the current status before you set your billing rules.
Medicare also requires providers to be enrolled and to report practice locations. A mismatch between enrollment and claim data can result in a denial from the Medicare Administrative Contractor.
Medicaid
Each state runs its own program. New York has its own telehealth rules, and managed care plans inside the state may add their own requirements. A practice that bills Medicaid in more than one state needs a separate review for each. This overview of Medicaid enrollment for telehealth providers covers the main steps.
Commercial plans
Large commercial payers often have separate telehealth policies, separate credentialing rules for virtual-only providers, and different requirements for each plan product. A provider approved for a PPO may not be approved for an HMO product from the same company. Always verify at the product level.
How Clearinghouses Fit In
Clearinghouses sit between your practice and the payer. They scrub claims, check formatting, and route files. They are useful, but they have limits.
A clearinghouse can catch a missing modifier or an invalid POS code. It cannot check whether the provider is properly enrolled with the payer. It may not know that a roster update is pending.
Use clearinghouse reports as an early warning. Rejections at this stage are cheaper to fix than denials after submission. Look for patterns. If the same rejection appears for one provider again and again, the problem may sit in the enrollment file.
A well-configured setup with strong clearing house solutions can add custom edits. For example, you can flag any telehealth claim where the provider’s payer effective date is after the date of service. This catches B7 style problems before submission.
A Pre-Billing Workflow to Prevent Telehealth Denials
Prevention costs less than rework. The workflow below adds a few checks to the front end. Each check takes minutes and can save weeks.
Step 1: Build a provider enrollment matrix
Create one sheet or database that lists every provider, every payer, and every state. For each combination, record:
- License status and expiration date
- Payer credentialing status and effective date
- Group affiliation and roster date
- Telehealth approval status
- Service locations on file
- CAQH attestation date
This matrix becomes your source of truth. Review it before onboarding a new provider and before expanding to a new state.
Step 2: Confirm patient location at the start of each visit
Ask where the patient is during the visit. Record it in the note. This confirms the right POS code and checks state licensure rules. It also protects you in an audit.
Step 3: Set POS and modifier rules by payer
Do not let one default apply to every claim. Build rules by payer and plan type. Have your billing team review them every quarter, since telehealth policy changes often.
Step 4: Verify eligibility and network status
Eligibility checks should confirm more than active coverage. They should confirm telehealth benefits and whether the provider is in network. This step reduces CARC 242 denials before they start.
Step 5: Add pre-submission edits
Work with your clearinghouse to add edits that catch date, location, and group mismatches. Even a few targeted edits can lower denial rates.
Step 6: Track denials by root cause
Do not only track denial codes. Tag each denial with its true cause: coding, documentation, enrollment, licensure, or eligibility. After a few months, you will see where the real losses sit. Many practices are surprised by how many belong to enrollment.
What To Do When a Telehealth Claim Already Denied
Sometimes prevention comes too late. Here is a practical way to work a denied claim.
First, read the full remittance. Look at the CARC, the RARC, and any free-text note. The combination tells more than any single code.
Second, check the claim data. Confirm the POS, modifier, NPI, tax ID, taxonomy, and service location. Compare each to the payer’s records.
Third, check the provider file. Open your enrollment matrix. Confirm the effective date, group link, and telehealth status.
Fourth, contact the payer. Call the provider relations line or use the payer portal. Ask what the payer has on file. Ask whether a correction is needed. Document the call with the date, name, and reference number.
Fifth, fix the root cause. If the file is wrong, submit a correction. If the dates are wrong, request a retroactive effective date where the payer allows it. If coding was the issue, correct and resubmit.
Sixth, check the filing deadline. Each payer sets a window for corrected claims and appeals. Missing it turns a fixable denial into a write-off. Review the rules on the timely filing limit for insurance claims before you start the appeal.
Retroactive Effective Dates: Set Realistic Expectations
Practices often ask whether a payer will backdate coverage. Sometimes yes. Often no.
Many commercial payers set the effective date as the date credentialing is approved. They may not pay for visits before that date. Some will consider a retroactive date if the delay was on their side. Medicare has its own rules for enrollment effective dates, which depend on the type of application and the filing date.
The safe approach is to not bill until the effective date is confirmed in writing. If you must see patients early, ask the payer about their policy ahead of time, and tell patients about the risk.
Delays are common. This article on how physician credentialing delays affect practice revenue shows how a few weeks of waiting can change cash flow for the year.
Managing Telehealth Credentialing as You Grow
Growth adds complexity. Each new provider, state, and payer adds another row to the matrix. Practices that scale well treat credentialing as an ongoing function, not a one-time task.
Plan state expansion early
Before you open telehealth in a new state, map the requirements. Check licensure, payer networks, Medicaid rules, and any state-specific telehealth laws. Build the timeline backward from your launch date. Credentialing can take months.
Assign ownership
Someone must own the enrollment matrix. This might be a credentialing specialist, an operations manager, or an outside partner. Without an owner, dates slip and gaps appear.
Review quarterly
Set a quarterly review. Check expiring licenses, upcoming recredentialing dates, CAQH attestations, and changes in payer policy. Add any new telehealth rules to your billing matrix.
Consider outside support
Credentialing is detailed work that takes time away from patient care. Many practices work with a partner for credentialing services so that applications, follow-ups, and roster updates stay on schedule. An outside team can also supply payer-specific knowledge that a small practice may lack.
Compliance and Audit Considerations
Telehealth claims draw audit attention. Payers compare POS codes, modifiers, and provider locations against documentation. Weak records can lead to recoupments.
Keep these records ready:
- Patient location documented in each visit note
- Proof of provider licensure for the patient’s state
- Payer approval letters with effective dates
- Evidence of the platform used and its security measures
- Policies for audio-only visits where applicable
Good documentation does two jobs. It supports the claim, and it exposes enrollment gaps early. A regular internal audit helps you see problems before a payer does.
Common Mistakes That Repeat
Some errors show up again and again. Watch for these.
- Treating every denial as a coding problem
- Assuming a license equals payer approval
- Updating a provider’s location with one payer but not the others
- Forgetting to update the group roster after a new hire
- Billing before the effective date is confirmed
- Letting CAQH attestations expire
- Using one POS and modifier setup for all payers
- Skipping patient location checks
Each mistake is simple to prevent. The cost of ignoring them is high.
Telehealth Claim Denials : FAQs
Why are my telehealth claims being denied when the coding looks correct?
Correct coding does not guarantee payment. The payer also checks the provider’s enrollment record, group affiliation, effective date, and service location. If any of these do not match the claim, the claim can deny. Compare the claim against the provider file before you rework the codes.
What is the difference between POS 02 and POS 10?
POS 02 is telehealth delivered when the patient is not at home. POS 10 is telehealth delivered when the patient is at home. Medicare has paid POS 10 at the non-facility rate and POS 02 at the facility rate since 2024. Other payers may follow different rules, so check each plan.
Do I need modifier 95 or modifier GT?
It depends on the payer. Modifier 95 is widely used for real-time audio and video visits. Modifier GT is older and is still required by some payers. Medicare no longer requires GT for most professional claims. Always confirm with the specific payer.
What does a CARC 242 denial mean for telehealth?
CARC 242 says the service was not provided by a network provider. For telehealth, this usually means the provider is not linked to the group contract, or not approved for the plan’s network in the patient’s location. Verify participation and roster status first.
What does CARC B7 mean?
CARC B7 means the provider was not certified or eligible to be paid for the service on the date of service. Check the credentialing effective date and any lapses in recredentialing or CAQH attestation.
Why do out-of-state patients cause denials?
State licensure and payer networks are tied to location. If the provider is not licensed or not in network where the patient sits, the payer may deny the claim. Confirm patient location at the start of every visit and review state rules before you treat patients in new states.
Can a clearinghouse prevent these denials?
A clearinghouse can catch format errors, missing modifiers, and invalid codes. It cannot confirm payer enrollment on its own. Custom edits can help, but enrollment accuracy still has to come from your credentialing process.
How long does it take to fix an enrollment mismatch?
It depends on the payer. A simple data correction may take a few days. A roster update or retroactive effective date request can take several weeks. Start as soon as you see the pattern, and watch the timely filing deadline.
Putting It Together
Telehealth denials are rarely random. They follow patterns. When you read a denial code as a signal about enrollment, the fix becomes clearer.
POS 02 and POS 10 depend on patient location and payer rules, and they must also match the provider’s service locations on file. Modifier 95 and modifier GT only work when the payer recognizes the provider for virtual care. CARC 242 points to network and roster problems. CARC B7 points to date and eligibility problems. Out-of-state denials point to licensure and state network gaps.
The practical takeaway is simple. Treat credentialing and billing as one system. Keep an enrollment matrix. Confirm patient location. Set payer-specific rules. Track denials by root cause. Review it all every quarter.
Get Help With Telehealth Credentialing and Denials
If your telehealth denials keep returning, the cause may sit in your provider files. eBridge RCM is a medical billing company in USA that supports practices with credentialing, enrollment cleanup, and denial resolution. Our team reviews your provider records, matches them to your claims, and builds a plan that prevents repeat denials.
New York practices can start with our medical credentialing in New York team. Visit eBridge RCM to request a review of your telehealth claims and enrollment records.


