Telehealth medical billing: what practices need to know

Why telehealth claims fail when the same visit in person would not

Practices are often surprised that a telehealth visit denies while the identical service, delivered in the office, pays without a second thought. The clinical work was the same. The code was the same. Something else went wrong.

The reason is that a telehealth claim has to answer questions an in-person claim never raises. An office visit implicitly answers “where did this happen?” and “how was it delivered?” — the patient was in the office, face to face. A telehealth claim has to state both of those things explicitly, using codes, and it has to state them the way the specific payer expects. Get either one wrong and the claim is rejected or denied even though the underlying service is covered.

That is why telehealth denials tend to concentrate in a handful of causes rather than spreading evenly across the book. They are more often a description problem than a clinical disagreement — a claim that failed to describe the encounter in the terms the payer’s adjudication system was built to read.

The four things a telehealth claim has to communicate

Before worrying about any individual code, it helps to know what the claim is being asked to establish. Every telehealth claim has to make four things unambiguous:

• What service was performed. The procedure code, exactly as it would be for the same work in person, supported by the documentation.
• How it was delivered. Whether the encounter was real-time audio and video, real-time audio only, or asynchronous — the modality. This is usually carried by a modifier.
• Where each party was. The patient’s location and the provider’s location. In telehealth terminology the patient’s location is the originating site and the provider’s is the distant site. The place-of-service code is what reports the patient’s setting; the provider’s location reaches the payer through other fields on the claim and through enrollment.
• Who provided it, and under what authority. The rendering provider, their credentials, and their enrollment with that payer — which for telehealth also raises where they are licensed.

In practice, most telehealth denials trace back to one of those four being absent, contradicted elsewhere on the claim, or expressed in a form that particular payer does not accept.

Modality: the modifier that says how the visit happened

Modifiers are how a claim reports the manner of delivery without changing the procedure code. CPT maintains a modifier for synchronous telemedicine delivered by real-time interactive audio and video, and a separate one for synchronous services delivered by real-time audio only — the distinction between a video visit and a telephone visit. HCPCS carries additional telehealth modifiers, including one for asynchronous store-and-forward transmission, and some payers ask for those instead.

Two practical points matter more than memorizing the values:

• Audio-only and audio-video are not interchangeable. They are separate modifiers because payers treat them as separate things, and coverage for one does not imply coverage for the other. Billing a telephone visit as though it were a video visit can be a compliance problem, not a shortcut.
• Which modifier a payer wants is a payer-by-payer fact. Commercial plans, Medicaid programs and Medicare do not align on this, and individual plans within the same carrier can differ. A modifier that one payer requires can be the one another payer rejects.

Modifier errors of this kind sit alongside the other quiet revenue drains covered in common CPT coding mistakes.

Location: place of service, and why the two signals must agree

Place-of-service codes describe the setting in which a service was furnished. The code set distinguishes telehealth delivered while the patient is at home from telehealth delivered while the patient is somewhere else — a clinic, a facility, a workplace. That distinction matters because payment policy can differ between the two, so the wrong one is not a cosmetic error.

The failure mode worth guarding against is a mismatch between the two signals and what the payer asked for. Some payers want a telehealth place of service paired with a telehealth modifier; others want the place of service that would have applied in person, with the modifier carrying the whole telehealth signal. A claim built to one convention and sent to a payer using the other can be rejected up front, or paid and then revisited on post-payment review — the second being the more expensive outcome, because the practice has already spent the money. Charge review should treat modality and place of service as a matched pair, and check the pair against that payer’s published telehealth policy rather than against a house default.

Where this bites hardest is a hybrid schedule — a provider seeing some patients in the office and some by video on the same day. The encounters flow into the same charge batch, and the telehealth ones inherit the office default unless something in the workflow flags them. A visit-type flag that drives the place of service automatically is far more reliable than asking a biller to remember which appointments were virtual.

Verify telehealth benefits, not just eligibility

Standard eligibility verification answers “is this policy active and does it cover this service?” For telehealth that is not enough, because a plan can cover a service in person and restrict or exclude it when delivered virtually. Telehealth benefit verification has to ask further questions:

• Is this service covered when delivered by telehealth, and by which modalities — video, audio-only, or both?
• Does the plan restrict telehealth to certain provider types or specialties?
• Does the patient’s cost share differ for a virtual visit?
• Does the plan require a prior in-person visit, or an established-patient relationship, before a telehealth visit is covered?
• Does telehealth require prior authorization when the in-person equivalent does not?
• Which modifier and place-of-service combination does this plan expect?

Answering those before the visit is the difference between a covered encounter and an unexpected patient balance. It is ordinary insurance verification work with a telehealth-specific question set bolted on, and it belongs in the pre-visit workflow described in the medical billing process. Where a plan does require authorization, the same approach that shortens prior authorization delays applies.

Where the patient is sitting can change the answer

A telehealth encounter has two locations, and the patient’s is the one that tends to govern. Two consequences follow.

Licensure generally follows the patient. The prevailing principle across states is that medicine is practiced where the patient is located at the time of the encounter, so the provider is generally expected to hold a licence in that state. Requirements differ by state and by profession, exceptions and multi-state licensure pathways exist, and this is an area where state law genuinely varies — so treat it as something to verify with counsel or the relevant licensing board rather than a rule to assume. It is a billing issue as well as a clinical one, because a claim for a service the provider was not authorized to deliver in that state is not a claim you want to have submitted. This is general information about billing workflow, not legal advice.

Payer network and benefit rules can follow the patient too. A patient who travels and takes a video visit from another state may fall under different plan terms than the ones verified at registration. Asking the patient to confirm their physical location at the start of the encounter, and recording it, is a small step that resolves both problems at once.

Enrollment matters here as well: a provider has to be enrolled with the payer in a way that covers how and where they are practicing. That is the distinction explained in credentialing versus payer enrollment — being credentialed is not the same as being able to send a claim.

Documentation that supports a telehealth claim

Telehealth documentation carries everything an in-person note carries, plus the facts that establish the encounter really was a telehealth encounter of the type billed. In practice that means recording:

• The modality actually used — audio and video, or audio only. If the video failed and the visit continued by phone, the note should say so, because the modifier has to follow what happened, not what was scheduled.
• The location of the patient and the location of the provider at the time of service.
• The identities of everyone present, including anyone else in the room on either end.
• Patient consent to be seen by telehealth, in the form the payer or the state requires — and, where that state or payer requires it, a note that the patient was told an in-person visit was available instead. Consent requirements vary by state and by plan, so build the template around the ones that apply to you.
• The start and end time of the encounter, which matters whenever a code is time-based.
• The clinical content itself, at the same standard as an office note.

A template that prompts for these fields is worth building once. Retrofitting them onto notes months later, in response to a records request, is a far more expensive way to find out they were missing.

Build a telehealth policy matrix instead of memorizing rules

The single most useful thing a practice can do about telehealth billing is stop treating it as a set of rules to be learned and start treating it as a set of payer facts to be maintained. Telehealth policy has changed repeatedly, changes at different times for different payers, and there is no reason to expect that to settle.

A telehealth policy matrix is a simple table with one row per payer — including each Medicaid program and each commercial plan you actually see — and columns for:

• Covered modalities, video and audio-only stated separately
• Required modifier or modifiers
• Required place-of-service code
• Any prior-relationship or prior-authorization condition
• Provider types the plan permits to bill telehealth
• Patient cost-share differences
• Where the policy is published, and the date you last checked it

That last column is the one that makes the matrix durable. A matrix without check dates quietly becomes a source of confident, out-of-date answers. Reviewing the payers that represent the bulk of your telehealth volume on a set cadence — and immediately when a denial pattern appears — keeps it honest.

Specialties that deliver a large share of their care virtually feel this most. Behavioral health billing is the clearest example, where telehealth is routine rather than exceptional and the policy variation between payers is correspondingly expensive.

Working telehealth denials: what to look at first

When telehealth claims start denying, the fastest diagnosis is to sort the denials by payer before sorting them by reason. Telehealth denial patterns tend to be payer-specific, so a mixed pile can look random while a single payer’s pile often points at one field.

Then work through the likely causes in order of how cheap they are to fix:

1. Modifier and place of service. Are they present, do they agree with each other, and are they the combination this payer publishes? This is a common and comparatively cheap category to fix, and it usually calls for a corrected claim rather than an appeal.
2. Modality mismatch. Was an audio-only visit billed with a video modifier, or the reverse? Check the note, not the schedule.
3. Benefit exclusion. Does this plan cover this service by telehealth at all? If not, the fix is upstream in verification, not in the claim.
4. Enrollment and licensure. Is the rendering provider enrolled with this payer, and licensed where the patient was?
5. Documentation. Does the note establish the modality, the locations and, where required, consent?

Categorize every one, because the value of a telehealth denial is mostly in what it tells you about the next hundred claims. That is the discipline described in denial management, and the prevention side of it in reducing claim denials. Tracking first-pass resolution rate separately for telehealth and in-person claims gives a practice a direct read on how well its telehealth workflow is working.

How Synergy handles telehealth billing

Synergy has been running billing for U.S. practices from Aurora, Illinois since 2005, and telehealth is part of the ordinary workload rather than a special case. Charges are reviewed before the claim is built, so a telehealth encounter that reaches us with an office place of service can be caught at charge entry rather than at the remittance. Claims go out within 24 hours, denials are worked within 48 hours, and our clean-claim rate on first submission is 98%. Provider credentialing is included at no extra charge, which matters when telehealth expands a practice into payers or states it was not previously enrolled with.

We are HIPAA compliant and work under a signed business associate agreement, inside your existing practice management or EHR system. There is a 30-day free trial, no long-term contract, and a 90-day money-back guarantee on full revenue cycle management. The engagement models are set out on pricing.