When does modifier 25 apply?

Modifier 25 may be appropriate when a significant, separately identifiable E/M service is performed by the same physician or other qualified healthcare professional on the same day as another procedure or service. The E/M work must go beyond the usual evaluation associated with performing the procedure and must be supported by the documentation, medical necessity, and applicable payer requirements.

What is the difference between modifier 25 and modifier 59?

Modifier 25 is E/M service plus procedure. Modifier 59 is procedure plus procedure. Modifier 25 helps communicate that an E/M service was separately identifiable from another service performed that day. Modifier 59 helps communicate that two procedural services that might ordinarily be bundled were distinct under the applicable coding rules.

Should I use modifier 59 or an X modifier?

When an X modifier — XE, XS, XP, or XU — accurately describes why services were distinct and is appropriate under the payer's requirements, it provides more specific information than modifier 59 alone. Because payer policies differ, practices should verify requirements before establishing standard billing rules.

Does forgetting a modifier always cause a denial?

No. That is part of what makes modifier-related revenue leakage difficult to identify. Depending on the payer and edit involved, a service may be bundled, reduced, or allowed at zero rather than creating the type of denial your team routinely works. Reviewing line-level remittance data is therefore just as important as reviewing denial reports.

Is overusing modifier 25 risky?

Yes. Routine or unsupported use of modifier 25 can create compliance and repayment exposure. But avoiding modifier 25 entirely is not the answer either. The appropriate goal is accurate use based on the services actually performed, the documentation, coding guidance, medical necessity, and payer requirements.

How do I audit our modifier use?

Start with utilization data. Compare modifier usage among similar providers and identify significant outliers. Then review a sample of records in both directions — encounters where the modifier was used and encounters where potentially distinct services occurred without it. For modifier 59 and the X modifiers, also review whether the documentation clearly explains why the procedures were distinct.

Modifier 25 and 59: The Modifier Mistakes That Cost Practices the Most

Modifiers may only be two characters, but those two characters can determine whether a service is paid separately, bundled into another service, or questioned during an audit. The challenge is that modifier mistakes do not always create obvious denials.

9 min readReviewed by The Provider Partner

The silent failure

Most practices are good at finding problems that announce themselves. A rejected claim lands in a queue. A denial generates a reason code. An unpaid claim eventually appears on an aging report.

Modifier-related payment issues can be much quieter.

Imagine submitting an E/M service and a procedure on the same claim. The claim processes and the payer issues payment. At first glance, everything appears fine. But one line was allowed at $0 because the payer bundled it into another service.

Figure 1A claim can be paid and still be shortThe claim status says paid, so it leaves the work queue. One line was allowed at $0 because the payer bundled it. There is no denial code, nothing lands in a follow-up report, and no one is prompted to ask why.

If your team primarily monitors denials and unpaid claims, who reviews that encounter? Possibly no one.

This is why strong denial management does not necessarily equal strong payment integrity. A practice can be very effective at working denied claims while still overlooking services that were processed but not reimbursed as expected.

The question that finds it

Sometimes the most important question is not “did the payer pay the claim?” It is: did the payer pay every service correctly?

Modifier 25: when the visit is separate from the procedure

Modifier 25 is used with an E/M service when a significant, separately identifiable E/M service is performed by the same physician or other qualified healthcare professional on the same day as another procedure or service. The most important phrase is separately identifiable.

A procedure naturally involves some evaluation. The provider has to evaluate the problem, determine whether the procedure is appropriate, examine the area, discuss the procedure, and perform the work necessary to safely complete it. That does not automatically create a separately billable E/M service.

Modifier 25 becomes relevant when the provider performs medically necessary E/M work above and beyond the usual work associated with the procedure, and the documentation supports that distinction.

Figure 2Modifier 25 and modifier 59 answer different questionsModifier 25 separates an evaluation from a procedure. Modifier 59 separates one procedure from another. Confusing the two is the most common modifier error we see.

Two encounters that look similar, but are not

Modifier 25 may not be supported. A patient schedules an appointment specifically for removal of a skin lesion. The provider examines the lesion, confirms that removal is appropriate, discusses the procedure, performs it, and provides routine post-procedure instructions. There may be evaluation documented, but that evaluation is associated with performing the procedure. Simply documenting an examination does not automatically make a separate E/M service billable.

Modifier 25 may be supported.A patient presents for a scheduled diabetes follow-up. During the encounter, the provider reviews glucose readings, evaluates the patient's response to treatment, adjusts medications, and addresses a new complaint of numbness in the feet. The patient also asks about a lesion, which the provider evaluates and removes during the same encounter. Now there are potentially two distinct pieces of work, and when appropriately documented and supported by payer policy, the E/M service may be separately reportable.

A simple way to think about modifier 25

Mentally remove the procedure from the encounter, then ask: if the procedure had not been performed today, would the remaining documentation still support a medically necessary, separately identifiable E/M service?

If the answer is yes, modifier 25 may be appropriate. If removing the procedure leaves little more than the assessment necessary to perform that procedure, a separate E/M service may not be supported. This is not a replacement for CPT guidance or payer policy, but it is an excellent way to help providers and coding teams understand the concept.

Modifier 25 can cost you in both directions

There are two very different modifier 25 problems, and practices should be looking for both.

Both directions carry a cost
Modifier 25 issue	What may happen	Primary risk
Omitted when supported	E/M may be bundled or not separately reimbursed	Lost revenue
Appended when not supported	Both services may initially pay despite insufficient documentation	Audit and repayment exposure

This is why telling providers to “use modifier 25 more often” is not the answer. Neither is telling them to avoid it. The goal is accurate modifier use supported by medical necessity, documentation, coding guidelines, and payer requirements.

Fear of an audit should not cause a practice to systematically underreport legitimate services. At the same time, revenue pressure should never lead to routinely appending modifier 25 simply because an E/M and procedure occurred on the same day. Accuracy protects both revenue and compliance.

Modifier 59: when two procedures really are distinct

Instead of distinguishing an E/M service from a procedure, modifier 59 is generally used to identify procedural services that are distinct from other services performed during the same encounter when they would otherwise be subject to an edit. This is particularly important when National Correct Coding Initiative (NCCI) edits or payer-specific bundling rules would normally prevent separate reimbursement.

But modifier 59 should never be treated as the universal “make it pay” modifier. The fact that two procedure codes were performed does not automatically mean modifier 59 belongs on the claim. The services must actually meet the requirements for being reported separately.

Depending on the circumstances, that distinction may involve a different encounter, anatomical site, organ system, lesion, incision, or other qualifying circumstance supported by the applicable coding rules. The documentation should tell that story clearly.

Modifier 59 and the X modifiers

CMS established four modifiers that provide greater specificity in situations where modifier 59 might otherwise be considered:

XE — separate encounter. Distinct because it occurred during a separate encounter.
XS — separate structure. Distinct because it was performed on a separate organ or structure.
XP — separate practitioner. Distinct because it was performed by a different practitioner.
XU — unusual non-overlapping service. Distinct because it does not overlap the usual components of the main service.

Why does that matter? Because “these services were separate” is less informative than explaining why they were separate. When an X modifier accurately describes the circumstances and is accepted by the payer, it may provide greater specificity than modifier 59. Payer requirements can vary, however, so verify individual payer policies before creating a blanket billing rule.

The modifier 59 red flag

One pattern deserves particular attention.

Figure 3The workflow that should stop youPayment is not evidence the modifier was correct. If the loop never reopens the medical record, the practice has taught itself that appending a modifier is how you get a bundled claim paid — which is a compliance exposure, not a fix.

Payment does not necessarily mean the modifier was correct. A modifier should communicate what actually occurred during the encounter. It should be supported by the documentation and applicable coding rules — not added solely because it causes the claim to process differently.

If your team routinely adds modifier 59 after bundling edits without reviewing the medical record, that workflow deserves immediate attention.

How to audit your modifier 25 use

You do not need to review every encounter to identify a potential problem. Start with your data.

Establish your modifier 25 rate. For each provider, identify encounters in the last 12 months where an E/M service and a minor procedure were reported on the same date, then determine how frequently modifier 25 was appended to the E/M service.
Compare similar providers. Compare clinicians in the same specialty with reasonably similar patient populations and services.
Audit in both directions.Review encounters where the modifier was used — does the documentation support a significant, separately identifiable E/M service? And review encounters where it was absent — was there separately identifiable E/M work that was documented but potentially bundled because modifier 25 was not reported?

Figure 4Where to look firstIllustrative data. The share of eligible E/M-plus-procedure encounters carrying modifier 25, by provider. The rate alone proves nothing — two providers can legitimately differ. What it does is tell you whose charts to pull, in both directions.

Within the groupWorth investigating

The percentage itself does not tell you whether the coding is right or wrong. It tells you where to look. If one provider uses modifier 25 on 5% of applicable encounters while another uses it on 95%, that difference deserves investigation. It does not automatically mean either provider is wrong — perhaps their patient populations or workflows are genuinely different. But large variations are useful audit signals.

Auditing only claims with the modifier helps identify overuse. Auditing both sides helps identify overuse and underuse.

Do the same with modifier 59

Run a report of claims containing modifier 59, XE, XS, XP, or XU, and look for:

Providers with unusually high or low utilization
Procedure combinations that repeatedly require modifiers
Modifiers frequently added after an initial denial
Claims where the documentation does not clearly demonstrate why the services were distinct
Payers with significantly different payment behavior for the same procedure combinations

You may discover a coding education issue. You may also discover a payer-specific edit that your team has been handling manually for years. Both are worth knowing.

The $0 line deserves attention

Here is one of the simplest revenue cycle exercises a practice can perform: look for claims containing multiple billed lines where one line received a $0 allowed amount or $0 payment because it was bundled or included in another service. Then investigate why.

Some of those zero-dollar lines will be completely correct. The service may truly be bundled under NCCI edits, payer policy, global surgery rules, or another reimbursement methodology. But others may reveal missing modifiers, incorrect modifier placement, coding errors, payer processing issues, documentation opportunities, contract-specific reimbursement rules, incorrect units, or missed appeal opportunities.

Investigate the pattern, not the line

Do not automatically rebill every zero-dollar line. A $0 line is not proof that money was lost. It is a signal that deserves an explanation.

Check the remittance, not just the claim

One of the biggest mistakes in modifier auditing is looking only at submitted claims. The claim tells you what you asked the payer to pay. The remittance tells you what the payer actually did with it.

If your billing system marks a claim as “paid” because money was received, a partially bundled service may disappear from normal follow-up. Consider creating a report that identifies multiple services billed, at least one service allowed at $0, and no traditional denial workflow. That small report can uncover problems your standard A/R and denial reports were never designed to find.

Make the fix part of the workflow

Modifier education is important, but education alone rarely fixes a recurring problem. People get busy. Staff changes. Providers forget. Payer policies change.

For modifier 25, structure documentation so the separately identifiable E/M work is clearly distinguishable from the procedure documentation.
For modifier 59 and the X modifiers, make sure the documentation clearly identifies what made the services distinct.
At charge entry, flag encounters containing common E/M-plus-procedure or procedure-plus-procedure combinations for review.
Periodically compare modifier utilization across providers.

The goal is not a rule that says “always use the modifier,” nor one that says “never use the modifier.” The goal is to make sure someone asks the right question before the claim goes out.

Modifier issues rarely exist in isolation. An encounter where an E/M service was bundled may also be an encounter where the procedure itself was never captured. A provider who routinely avoids modifier 25 because of compliance concerns may also be selecting E/M levels below what the documentation supports. And a workflow that misses modifiers may also be missing units, administration services, supplies, or add-on codes.

When you find one pattern, look at the entire encounter. Sometimes the modifier is not the problem. It is simply the clue that leads you to the real problem.

Find this in your own data

If you want to know whether modifier mistakes are costing your practice money, do not start by reviewing thousands of charts. Start with three reports:

E/M + minor procedure encounters. Compare modifier 25 utilization by provider.
Procedure + procedure encounters. Review modifier 59 and X-modifier utilization and identify recurring code combinations.
Zero-dollar line report. Find multi-line claims where at least one service was bundled or allowed at $0, and determine why.

Then take a targeted sample back to the medical record. That is where billing data becomes actionable.

The objective is not to find more modifiers to add. The objective is to make sure every modifier you use is supported — and every modifier that should have been used was not missed. That protects both sides of the revenue cycle: appropriate reimbursement and appropriate compliance.

Common questions

When does modifier 25 apply?: Modifier 25 may be appropriate when a significant, separately identifiable E/M service is performed by the same physician or other qualified healthcare professional on the same day as another procedure or service. The E/M work must go beyond the usual evaluation associated with performing the procedure and must be supported by the documentation, medical necessity, and applicable payer requirements.
What is the difference between modifier 25 and modifier 59?: Modifier 25 is E/M service plus procedure. Modifier 59 is procedure plus procedure. Modifier 25 helps communicate that an E/M service was separately identifiable from another service performed that day. Modifier 59 helps communicate that two procedural services that might ordinarily be bundled were distinct under the applicable coding rules.
Should I use modifier 59 or an X modifier?: When an X modifier — XE, XS, XP, or XU — accurately describes why services were distinct and is appropriate under the payer's requirements, it provides more specific information than modifier 59 alone. Because payer policies differ, practices should verify requirements before establishing standard billing rules.
Does forgetting a modifier always cause a denial?: No. That is part of what makes modifier-related revenue leakage difficult to identify. Depending on the payer and edit involved, a service may be bundled, reduced, or allowed at zero rather than creating the type of denial your team routinely works. Reviewing line-level remittance data is therefore just as important as reviewing denial reports.
Is overusing modifier 25 risky?: Yes. Routine or unsupported use of modifier 25 can create compliance and repayment exposure. But avoiding modifier 25 entirely is not the answer either. The appropriate goal is accurate use based on the services actually performed, the documentation, coding guidance, medical necessity, and payer requirements.
How do I audit our modifier use?: Start with utilization data. Compare modifier usage among similar providers and identify significant outliers. Then review a sample of records in both directions — encounters where the modifier was used and encounters where potentially distinct services occurred without it. For modifier 59 and the X modifiers, also review whether the documentation clearly explains why the procedures were distinct.