Skip to content
Nucleus Align
Book a call
Who We Serve
Services
No Surprises Act
Specialties
Resources
Company
Hospital and facility billing

Which Clearinghouse Edits Matter Most for UB-04 Claims?

The edits that matter most for UB-04 claims are the ones that mirror what your payers reject: required fields, cross-field rules and code validity. Turn those on as holds, turn payer-specific checks on from each payer's own manual, and tune the rest from your own rejection reports. This post gives the order and a way to decide which edits block a claim and which only warn.

Written by Salman Saeed, CEO and Co-Founder · Reviewed by a Certified Medical Coder ·
Revenue cycle analyst reviewing clearinghouse edit results and rejection reports for institutional UB-04 claims
Your own rejection report is the best list of which edits to switch on.

In short: rank edits by how often they would have caught a real rejection in the last 90 days, not by how many a tool offers. Hold the claim on required-field and cross-field failures, and let softer checks warn.

What Does a Clearinghouse Edit Actually Do?

A clearinghouse moves electronic claims between you and the payer. The Medicare Claims Processing Manual, chapter 24, section 40.2.2.3, says clearinghouses often perform general and payer-specific edits on claims. An edit is a test the claim must pass before it goes out. The institutional claim itself travels as an 837I, the X12 institutional claim transaction.

Edits come in layers, and the rejection you see depends on which layer caught the problem. Knowing the layers tells you where to look when a claim comes back.

LayerWhat it checksWhere you see the result
File and formatWhether the transmission is built to the X12 standardA 999 implementation acknowledgment, which can reject the whole transaction set
Claim levelWhether each claim has the data the payer requiresA 277CA claim acknowledgment, listing the claims accepted or rejected
Payer adjudicationCoverage, authorization, medical necessity and payment rulesThe remittance, with a CARC and RARC

Chapter 24, section 50.3.3, describes how a Medicare A/B MAC front end splits the first two layers. Errors that cannot be accepted reject the whole transaction set through the TA1 or 999. Errors that can be passed on are marked as "Accepted, but Errors Noted" and then reported claim by claim on the 277CA. Other payers publish their own companion guides, so read theirs.

Which Edits Should Come First?

There is no official ranking of edits by value. The order below starts with the fields the Medicare form instructions in chapter 25 call required. The edits themselves are advice; the field requirements are CMS's, and each commercial payer sets its own list in its manual.

PriorityEdit typeExamples from chapter 25Suggested setting
1Required fields presentFL 4 type of bill, FL 14 priority of admission or visit, FL 15 point of origin (except bill type 014X), FL 17 patient status, FL 56 billing NPI, FL 67 principal diagnosisHold
2Format and sequenceFL 67 as the full code with the decimal implied, FL 42 revenue codes in ascending order with 0001 on the total line, FL 18 to 28 condition codes in numerical orderHold
3Cross-field consistencyOccurrence codes 01 to 04 and 24 with a value code in FL 39 to 41 when another payer is involved. A surgical procedure code with an operating provider in FL 77. FL 74 procedure codes on inpatient claims onlyHold
4Service-line detailHCPCS in FL 44 and a line item date in FL 45 for every iteration of every revenue code on outpatient bills, with units in FL 46Hold
5Authorization and payer dataFL 63 authorization number when the payer assigned one and the services were preauthorized. Payer name and ID in FL 50Hold when the payer requires it, otherwise warn
6Coding editsNCCI procedure-to-procedure pairs and medically unlikely edits for outpatient hospital claimsWarn, then route to coding

NCCI procedure-to-procedure edits are not applied to facility claims for inpatient services, according to the NCCI Medicare Policy Manual introduction, so do not expect that edit to fire on an inpatient claim. Medically unlikely edits have a separate table for outpatient hospital claims, kept apart from the practitioner table.

When Should an Edit Hold the Claim and When Should It Warn?

A hold stops the claim until someone fixes it. A warn lets it go and records the flag. The test is the cost of being wrong.

  • Hold when the payer will return the claim as unprocessable, because a returned claim is not a denial and the clock keeps running. The CO-16 denial code page explains the return.
  • Hold when the failure changes payment, such as a wrong bill type or patient status.
  • Warn when the edit is a judgment call that coding should review but the payer's rule is not fixed.
  • Warn when you are testing a new payer-specific edit and do not yet know its false-alarm rate.

A hold that fires on valid claims trains staff to override it. An edit that never holds anything is not protecting you. Review both kinds each month.

How Do You Tune the Edits from Your Own Data?

1
Collect 90 Days of Rejections and Front-End Returns
Use the 277CA claim rejections and the remittance lines carrying CARC 16 with a RARC. Count by reason, by payer and by bill type.
2
Map Each Reason to an Edit
If the same missing field appears twenty times, there should be a hold that catches it before release. If no edit exists, request one or add a rule in your own system.
3
Set the Severity
Hold the ones that produced returns. Warn on the ones that only produced questions.
4
Test on a Sample
Run last month's rejected claims through the new settings, and run a clean sample to see how many valid claims the new hold would stop.
5
Review Monthly
Retire edits that fire on valid claims, tighten the ones that missed rejections, and log every change with a date so you can link a change to a drop in returns.
Example: Made-Up 90-Day Review

The counts are invented to show the method.

Claims submitted2,400
Rejected at the clearinghouse or payer front end168
Reason: principal diagnosis format or missing52
Reason: payer or subscriber ID32
Reason: occurrence code without a value code31
Reason: missing authorization number29
Reason: bill type or frequency mismatch24
Rejection rate168 of 2,400 = 7%

The three largest reasons, diagnosis format, payer ID and occurrence code, account for 115 of the 168 rejections. Those are the first three holds to build or tighten.

What Should You Ask a Clearinghouse About Its Edits?

  • Can you see the full edit list, and can you set each edit to hold or warn yourself?
  • Which edits are national and which are payer-specific, and how often does the payer list get updated?
  • How is a payer rule change communicated, and who tests it?
  • Can the clearinghouse report rejections by reason, payer and bill type?
  • Does it return the 999 and 277CA to you in a form your team reads daily?

Comparing tools by the number of edits advertised says little. The question is whether the edits that match your rejections can be switched on and tuned. The pre-bill checklist covers the manual review that sits in front of the scrubber, and the UB-04 form locators that cause rejections post lists locator rules in detail.

How Does Nucleus Align Work with Clearinghouse Edits?

We align each EHR, clearinghouse and payer portal workflow with verified team experience, standard claim validation, reconciliation controls and performance monitoring. Our UB-04 accuracy checks cover bill type, revenue codes, patient status, condition and occurrence codes, authorization requirements and payer-specific rules. See hospital and facility billing, the emergency medicine billing page, or book a call. More explainers are on the blog.

Written by Salman Saeed, CEO and Co-Founder
Reviewed by a Certified Medical Coder. Our editorial policy explains how every article is checked.
FAQ

Common Questions

Straight answers from the team that does the work.

Still have a question?

Ask a billing lead directly. A 20-minute call, Monday to Friday, 9am to 5pm Eastern.

01Which clearinghouse edits matter most for UB-04 claims?

Start with required-field edits such as bill type, patient status, principal diagnosis and billing NPI, then format and sequence edits, then cross-field rules such as occurrence codes with value codes. These mirror the Medicare chapter 25 requirements. Add payer-specific edits from each payer's manual and tune the rest from your own rejections.

02What is the difference between a 999 and a 277CA?

The 999 is an implementation acknowledgment about the file as a whole and can reject an entire transaction set. The 277CA is a claim acknowledgment that reports accepted and rejected claims one by one. Under Medicare chapter 24, errors that can be passed on are reported claim by claim on the 277CA.

03Should every edit be set to hold the claim?

No. Hold on failures that cause an unprocessable return or change payment, and warn on judgment calls. An edit that holds valid claims trains staff to override it, and one that never holds anything adds no protection. Review the hold and warn lists every month against your rejections.

04Do clearinghouse edits replace a coder or a pre-bill review?

No. An edit can test the format and consistency of fields, but it cannot read the chart. It will not tell you a diagnosis is unsupported or a charge was missed. Keep the human review in front of the edit step for coding and charge questions.

Talk to a Billing Lead.

A 20-minute call about your payers, volume and setup. Monday to Friday, 9am to 5pm Eastern.

  1. Step 1 of 3: Your details
  2. Step 2 of 3: Pick a day
  3. Step 3 of 3: Pick a time

Your details

Please do not include any patient information.