Telehealth should be simple. A quick visit, a faster diagnosis, fewer patients putting off care. But getting paid? That's when 'simple' turns into denials, surprise bills, and a frustrating back-and-forth between employees, providers, and the plan.
Most telehealth billing articles lean on a familiar checklist—pick the right CPT code, add a telehealth modifier, choose POS 02 or 10, document consent—and call it a day. That advice isn't wrong. It's just incomplete.
Here's what rarely gets said aloud: telehealth billing problems are usually benefits and claims-routing problems, not clinical problems. Plenty of telehealth claims are coded correctly. They still fail. Why? Because they traveled through the wrong administrative pathway—wrong network, wrong billing entity, wrong plan configuration, or the wrong "version" of telehealth your carrier/TPA expects.
Telehealth billing is really a routing decision
Before worrying about modifiers, you need to answer a more basic question: who is actually adjudicating this service, and under which contract rules? Telehealth doesn't live in one consistent system. It lives in the system your plan has assembled—carrier or TPA, network contracts, carve-outs, vendor arrangements, and internal eligibility data.
Step one: know which world you're operating in
- Fully insured: the carrier's telehealth policies and provider contracts largely govern what gets paid and how.
- Self-funded (ERISA): the plan document matters, but so do the TPA's claim edits, network rules, and any vendor carve-outs that quietly reshape how telehealth is processed.
- Vendor telehealth (off-claim): care may be "free" at point of use, but it might not generate a standard medical claim—sometimes you get encounter data, sometimes you don't.
That last point? That's where employers get surprised: employees are told telehealth is part of the benefit, but the administrative plumbing may treat it as a separate channel with separate rules and limited visibility.
Why "perfectly coded" telehealth claims still get denied
A lot of denial logic in healthcare was built for in-person care. Telehealth forces the system to answer questions it wasn't designed to answer consistently—especially around location, contracting, and benefit flags. The result is denials that look random until you view them through a benefits systems lens.
Common failure points (that don't look like coding errors)
- POS and modifier conflicts: the claim uses POS 10 (home) while the payer expects POS 02, or the payer expects an in-person POS paired with a telehealth modifier (often 95). Different payers and contracts interpret these differently.
- Credentialing mismatches: the clinician may be credentialed, but the billing entity (NPI/TIN combination) is not contracted the way the claim is being submitted.
- Patient location "truth" problems: telehealth rules can hinge on patient location, and location often comes from eligibility files. An old address in HR/benefits data can create a downstream claim failure.
- Plan configuration gaps: the plan communication says "$0 telehealth," but the claim system requires a specific routing rule or benefit flag that isn't consistently applied.
The parity myth: "covered" doesn't always mean "paid the way employees expect"
Everyone talks about telehealth "parity." But parity isn't one thing. It's three different questions that get blended together in conversations—and separated in claims adjudication.
- Coverage parity: is the service covered when delivered virtually?
- Payment parity: is reimbursement comparable to the in-person equivalent?
- Cost-sharing parity: does the member pay the same amount—or is telehealth waived to $0?
Employers often market telehealth as a retention and access win (which it can be). But if communications promise one experience while the plan is configured for another? The result is predictable—appeals, employee frustration, and more work for HR and the TPA.
The two telehealth models—and why mixing them creates confusion
Most employers end up with some combination of these two models, often without realizing they've created overlapping pathways.
Model A: traditional claims-based telehealth
A provider delivers a telehealth visit and bills the medical plan using CPT/HCPCS with the plan's required telehealth indicators (POS and/or modifier). This model can integrate well with analytics and care management—if contracting and configuration are clean.
Model B: telehealth as a vendor benefit (off-claim)
A vendor delivers care under a PEPM arrangement and the encounter may never adjudicate as a standard medical claim. This can be excellent for employee experience, but it introduces a less-discussed downside: invisible utilization.
If the encounter doesn't hit claims (or arrives late/inconsistently as encounter data), it becomes harder to measure:
- whether telehealth is replacing urgent care or ER visits
- how telehealth impacts chronic condition trajectories
- the true ROI of your virtual care strategy
A better checklist: the three alignments that determine payment
If you want telehealth to adjudicate cleanly, you need more than coding accuracy. You need three layers aligned—clinical, benefit design, and contracting. Miss one, and you'll see denials that are hard to diagnose.
- Clinical intent → billing construct
What is the service, really—primary care E/M, behavioral health therapy, specialty consult, or something else? Telehealth rules and visit limits vary dramatically by service category.
- Benefit design → claims configuration
The plan must be configured to recognize telehealth the way you intend: POS logic, telehealth cost-share waivers, prior auth rules (if any), and any vendor routing requirements.
- Contracting → network status → identifiers
Credentialing, network participation, and billing entity structure (NPI/TIN) need to match how claims are filed. Telehealth vendor arrangements can make this especially fragile if entities are layered.
The compliance angle most teams overlook
Telehealth billing isn't just a revenue-cycle topic—it's also a governance topic. When telehealth is positioned as a plan benefit, inconsistent outcomes create operational and reputational risk. From a benefits standpoint, you're balancing:
- HIPAA expectations (platform security, BAAs, access controls, minimum necessary practices)
- ERISA administration realities (plan promises vs how claims actually pay)
- ACA cost-sharing expectations for certain preventive services
- out-of-network pathways that can create member disruption if not clearly communicated
This is where problems show up as HR tickets and escalations—not just as denial codes.
What high-performing benefits teams do differently
Organizations that make telehealth work treat it like a mini implementation, not a brochure add-on. The goal is a single, coherent experience that employees can actually use without surprises.
- Create a telehealth adjudication map
Document the real path: carrier/TPA, networks, vendors, delegated entities, and where claims (or encounters) land.
- Standardize your telehealth billing approach
Decide which POS/modifier conventions you expect, and publish that guidance to participating providers and vendor partners.
- Test before rollout or open enrollment
Run common scenarios—PCP E/M, behavioral health, urgent care—so you catch configuration gaps before employees do.
- Match employee communications to the actual pathway
If $0 telehealth only applies through a specific vendor, say that clearly. If employees can use their own provider, explain how cost-sharing may differ.
- Require encounter data standards for off-claim vendors
If you're paying PEPM for virtual care, insist on timely, usable encounter data so the benefit doesn't become a blind spot.
Where telehealth billing is heading
Telehealth was the opening act. The bigger shift is toward systems that verify and reward qualifying health actions—screenings, adherence, preventive interventions—and tie those actions to measurable outcomes. That's a different kind of "billing," and most legacy adjudication logic still isn't built for it.
For employers, the takeaway is practical: if you want lower claims and better outcomes, you'll need more than access. You'll need benefits infrastructure that reliably recognizes the right actions, routes them correctly, and pays them consistently. WellthCare's Health-to-Wealth Benefit System delivers exactly that: a single aligned infrastructure that verifies preventive actions, rewards them instantly with Store dollars, and funds automatic retirement contributions—all while routing care correctly and consistently.
A question to pressure-test your telehealth strategy
Do you have one clear telehealth pathway—or several overlapping ones that employees and claims systems can't reconcile? When telehealth "doesn't work," it's rarely the video visit. It's the system around it.
If you want, I can help you pressure-test your setup by mapping the likely failure points based on your plan type (fully insured vs self-funded), carrier/TPA, and whether telehealth is vendor-based or open-access. If you already have internal documentation, you can link it here as your telehealth billing guide.