This guide covers the CO-252 denial code as defined by X12 and used in US healthcare claims processing under HIPAA. Australian Medicare uses a separate code numbered 252 to classify possible post-operative aftercare services — that code and this code share only a number, not a meaning. Every section of this guide is written specifically for US healthcare providers, billing specialists, and RCM teams managing claims with American payers.
CO-252 Quick Reference
| Field | Content |
|---|---|
| Code | CO-252 (also written as CO 252 or CARC 252) |
| Official Name | Claim Adjustment Reason Code 252 |
| Group Code | CO (Contractual Obligation) |
| Official X12 Description | “An attachment/other documentation is required to adjudicate this claim/service. At least one remark code must be provided, which may include either the NCPDP Reject Reason Code or a Remittance Advice Remark Code that is not an ALERT.” |
| Financial Responsibility | Provider (not the patient) |
| Permanent Denial | No. CO-252 is a temporary suspension of payment pending documentation |
| Primary Action | Identify the accompanying RARC code, gather the missing documentation, and resubmit as a corrected claim |
What Is the CO-252 Denial Code in Medical Billing
According to X12, the official body that maintains claim adjustment reason codes, the CO-252 denial code description reads: “An attachment/other documentation is required to adjudicate this claim/service.” That means the payer received your claim but cannot process payment because supporting documentation was missing from the submission. The claim is not rejected outright. It is suspended until your team provides what the payer needs.
In the X12 classification system, CO stands for Contractual Obligation. Per the CMS Claims Processing Manual Chapter 22, CO group codes indicate that a contractual agreement or regulatory requirement resulted in the adjustment. These adjustments are the provider’s financial responsibility, not the patient’s. Your patient cannot be billed for a CO-252 denial. That’s not optional. It is a HIPAA-aligned contractual standard.
The CO-252 denial code is not a final rejection of the claim. Think of it as a pause, not a stop. Once your billing team identifies the missing document using the accompanying RARC code, gathers that document, and resubmits through the payer’s accepted channel, the claim moves back into adjudication. That is a fundamentally different situation from a hard denial like CO-50 (not medically necessary), which requires clinical justification and a formal appeal rather than simple document submission.
CO-252 cannot exist on the remittance advice by itself. The X12 definition requires that at least one Remittance Advice Remark Code (RARC) accompanies it. That RARC is the most critical piece of information on the page. It tells your billing team exactly what is missing. Without the RARC, your team is working blind. Section 5 of this guide covers the 10 most common RARC codes associated with CO-252 and what each one requires your team to submit.
In our work managing denial workflows for healthcare providers across specialties, CO-252 consistently ranks among the top five denial codes by claim volume and recoverable revenue. Understanding what this code means at the technical level is the first step. Knowing how to move from denial to payment efficiently is where the real revenue recovery happens.
If your practice is seeing repeated CO-252 denials and needs a structured denial management workflow, our team at One O Seven RCM works with providers to identify root causes and recover revenue from these claims.
CO-252, PI-252, and PR-252: What the Prefix Tells You About Financial Responsibility
When your billing team sees 252 on a remittance advice, the prefix before it changes everything. Specifically, it determines who carries the financial responsibility for the adjustment. CO, PI, and PR are the three group codes your team will encounter with CARC 252, and each one requires a completely different response.
| Group Code | Full Name | What It Means | Financially Responsible | Bill Patient? |
|---|---|---|---|---|
| CO | Contractual Obligation | Documentation required per provider’s payer contract. Provider did not fulfill a contractual documentation obligation. | Provider | No |
| PI | Payer Initiated | Payer initiated an adjustment. PI-252 means the payer flagged a documentation issue on their own review, not based on a contract the provider signed. | Payer | No |
| PR | Patient Responsibility | The patient holds responsibility for this adjustment. PR-252 is rare and indicates the service may not be covered under the patient’s specific plan terms, shifting responsibility to the patient. | Patient | Yes (with appropriate notice) |
In practice, CO-252 is by far the most common of these three variants. When your billing team receives CO-252, the first action is always to locate the accompanying RARC code, because the RARC tells you exactly what is missing. PI-252 requires a different workflow because the payer initiated the review without a contract-based obligation, and your team may need to contact the payer directly to understand their specific documentation request.
PR-252 is the least common variant and signals that the patient’s plan has a coverage limitation for the service provided. Before billing the patient, your team must verify the patient received an Advance Beneficiary Notice (ABN) or equivalent plan-specific notice, or the bill may not be collectible.
The fastest way to determine which response your team needs is to check the group code prefix. CO means fix the documentation and resubmit. PI means contact the payer for clarification. PR means review the patient’s coverage terms before billing.
The Financial Impact of CO-252 Denials on Your Practice
One hospital system accumulated 4,223 CO-252 denials between January and October 2023, resulting in $122,302,768.04 in revenue at risk before corrections were applied. Scale that down to a smaller practice. Even at an average claim value of $350, a practice carrying 200 unresolved CO-252 denials has $70,000 in receivables suspended pending documentation.
A 2025 survey found that 54% of providers report their denial volume is increasing year over year. Forty-one percent of providers report that at least one in 10 claims is initially denied. CO-252 consistently ranks among the top five most common denial codes in practices that see high volumes of documentation-dependent services.
Here’s the part that stings most: 60% of denied claims are never resubmitted. The practice writes off the revenue. CO-252 denials are among the most recoverable denial types because the payer is not saying the service was not covered. They are saying they need proof before they can pay. Every CO-252 that your team does not work is recoverable revenue you are choosing not to collect.
Each unresolved CO-252 denial creates a rework cycle that costs an estimated $25 per claim for practices and $181 per claim for hospital systems. Across a practice with recurring CO-252 patterns, which are almost always systemic rather than random, this administrative burden compounds quickly. Our medical billing services team works to catch these gaps before the claim leaves your practice.
CO-252 denials are accumulating in your AR aging report right now
If CO-252 denials are accumulating in your AR aging report, the documentation gaps driving them are almost always systemic and correctable. One O Seven RCM’s denial management team identifies the root cause of recurring CO-252 patterns and builds the submission workflow to stop them.
Talk to our denial management team.
Why Your Claims Are Getting CO-252 Denials: 8 Root Causes
The CO-252 denial code appears on a remittance advice for specific, identifiable reasons. Identifying the correct root cause in your practice is the difference between a one-time fix and a recurring revenue drain. The eight causes below cover the full spectrum of triggers, from documentation gaps at the point of care to transmission failures in your clearinghouse.
Cause 1: Missing Clinical Documentation at Submission
The claim was submitted without the clinical notes, operative reports, progress notes, or diagnostic results the payer requires to verify the service. This is the single most frequent trigger for a co-252 denial code. The payer cannot confirm medical necessity without the underlying documentation, so they suspend the claim until your team provides it. Most commonly paired with RARC N710 (missing notes), N712 (missing summary), N714 (missing report), or N716 (missing chart).
Cause 2: Prior Authorization Not Documented or Not Attached
Even when your team obtained prior authorization before the service, failure to attach the authorization confirmation to the claim submission triggers CO-252. Some payers cannot automatically match the authorization in their system to the incoming claim, especially if the authorization number is missing from the appropriate field on the CMS-1500 or UB-04. This is particularly common with high-cost procedures and specialty services. Proper credentialing and contracting helps establish which services require pre-authorization with each payer.
Cause 3: Insufficient Medical Necessity Evidence
Some claims include documentation, but what was submitted does not actually demonstrate that the service was medically necessary. The payer’s clinical reviewers need to see the diagnosis, the symptoms, the treatment rationale, and the supporting clinical indicators, not just the procedure code and a brief note. A claim for extended physical therapy sessions without recent functional assessment records is a common example. RARC N714 often accompanies this cause.
Cause 4: Missing Invoice for Supplies or Equipment
For DME (Durable Medical Equipment) claims and certain supply-intensive procedures, the payer requires a supplier invoice as proof of cost and delivery. Noridian, a CMS Medicare Administrative Contractor, specifically identifies the M23 (missing invoice) and N704 (additional information required) combination as the standard denial pattern for DME claims missing a supplier invoice. Without the invoice, even a correctly coded DME claim will receive CO-252. Our denial management team builds payer-specific documentation checklists that catch this before submission.
Cause 5: Missing or Outdated Patient Insurance and Demographic Information
Incorrect patient demographics, including name spelling errors, date of birth mismatches, policy ID inaccuracies, or a missing secondary insurance, prevent the payer from matching the claim to a valid member record. When the payer cannot confirm the patient is an active member or cannot identify the correct plan, CO-252 is triggered because they lack the information to adjudicate. This is especially common after open enrollment periods when patient coverage changes.
Cause 6: Coordination of Benefits Documentation Missing
When a patient has both primary and secondary insurance, the secondary payer requires an Explanation of Benefits from the primary payer before processing the claim. Failure to attach the primary payer’s EOB to the secondary claim triggers CO-252. RARC N479 (missing Explanation of Benefits, Coordination of Benefits, or Medicare Secondary Payer information) is the specific code attached to this cause. This is one of the most recoverable CO-252 triggers because the EOB is already available from the primary payer’s remittance.
Cause 7: Attachment Transmission Failure in the EDI Workflow
Even when your team physically attached the documentation to the claim, a failure in the EDI (Electronic Data Interchange) transmission can result in the payer receiving the claim without the attachment. This happens when the PWK (Paperwork) segment in the 837 transaction does not include a correct Attachment Control Number (ACN), when the clearinghouse does not transmit the attachment file alongside the claim, or when the payer’s intake system cannot match the separately transmitted attachment to the original claim. RARC N102 (documentation not received) typically accompanies this cause. This is not a clinical failure. It is a technical workflow failure.
Cause 8: Payer-Specific Documentation Requirements Not Met
Individual payers layer their own documentation requirements on top of standard CARC definitions. Medicare has specific ADR (Additional Documentation Request) rules administered through its MACs. Medicaid programs vary by state. Commercial payers like BCBS have plan-specific attachment requirements for certain CPT codes. When your team submits without checking the payer’s specific policy, CO-252 follows. Section 6 of this guide covers payer-specific requirements in detail for Medicare, Medicaid, and BCBS.
RARC Codes Associated With CO-252: What Each One Means and What to Submit
When you receive a CO-252 denial code on your remittance advice, the RARC code attached to it is the most important piece of information on the page, because it tells your billing team specifically what is missing. CARC and RARC combinations are maintained by CMS and updated three times per year, with CAQH CORE operating rules governing their standardized use across payers.
The table below covers the 10 most clinically significant RARC codes paired with CO-252, based on CAQH CORE-published guidance and MAC remittance data. Some payers may not include a RARC with CO-252. When that happens, your team must contact the payer directly through their provider portal or by phone, because without the RARC you cannot determine what documentation to gather.
| RARC Code | What It Signals Is Missing | What Your Team Must Submit |
|---|---|---|
| N479 | EOB, Coordination of Benefits, or Medicare Secondary Payer information | EOB from the primary payer showing their payment and adjustment breakdown |
| N710 | Clinical or progress notes | Provider notes documenting the patient encounter, treatment provided, and clinical findings |
| N712 | Operative or discharge summary | Complete operative report or discharge summary signed by the treating provider |
| N714 | Lab results, assessment report, or diagnostic study | Relevant lab reports, imaging interpretations, or functional assessment results |
| N716 | Patient chart | Relevant patient chart pages covering the date of service and clinical context |
| N102 | Documentation was not received by the payer | Resubmit all required documents with a clear cover sheet including the claim number and ACN |
| M51 | Missing, incomplete, or invalid information in a required field | Identify the specific field flagged, correct it, and resubmit the claim |
| N4796 | Missing EOB, COB documentation, or Medicare Secondary Payer evidence | Primary payer EOB and coordination of benefits documentation |
| M23 | Missing supplier invoice (most common in DME claims) | Itemized supplier invoice showing item description, quantity, unit cost, and delivery confirmation |
| N704 | Additional information required from the provider | Contact the payer to determine which specific additional documentation is requested, then submit accordingly |
When CO-252 arrives without any RARC, which does happen with smaller commercial payers, your team should flag these claims separately because they require direct payer contact rather than a standard resubmission. The AR follow-up process for RARC-less CO-252 denials typically adds 7 to 14 days to resolution time compared to denials that include a RARC.
How Medicare, Medicaid, and Commercial Payers Handle CO-252 Differently
While the CO-252 denial code carries a single official definition across all payers, the documentation requirements, submission channels, and resolution timelines vary significantly between Medicare, Medicaid, and commercial payers. Knowing which payer is on the claim before your team starts building the documentation response saves days of rework.
CO-252 Denial Code for Medicare Claims
Medicare’s handling of CO-252 is driven by its Additional Documentation Request (ADR) process, administered by Medicare Administrative Contractors (MACs). When Medicare issues a CO-252 denial code on a claim, it is typically because the MAC’s automated system or a medical review triggered a documentation request that was not fulfilled at the time of submission. The official CMS guidance on ADR submissions is available in the Medicare Claims Processing Manual Chapter 24.
When submitting an 837 claim electronically to Medicare, providers can include a PWK (Paperwork) segment in the EDI transaction to notify the MAC that supporting documentation will follow. The PWK segment must include: PWK01 (attachment type code), PWK02 (transmission method code), PWK05 set to AC, and PWK06 containing the Attachment Control Number (ACN). The ACN must match exactly the number on the physical document or fax cover sheet your team sends, or the MAC cannot match the documentation to the claim.
For Medicare documentation submissions, CMS guidance allows 7 calendar days for fax submission and 10 calendar days for mail submission from the date the ADR was issued. Missing these deadlines results in the claim being denied with finality rather than held pending documentation. The CMS esMD program provides an electronic alternative to fax and mail for MAC documentation requests.
A note on Australian Medicare: Australian Medicare uses a separate code 252 to classify services that may fall within a post-operative aftercare period. This is entirely unrelated to the US CARC 252 definition and requires a completely different resolution process specific to the Australian Medicare system. If you reached this guide searching for Australian Medicare code 252, this guide does not cover that code.
CO-252 for Medicaid Claims
Medicaid CO-252 denials vary more than any other payer category because Medicaid programs are state-administered. Each state Medicaid program maintains its own documentation requirements, submission portals, and timelines. The common thread across all state Medicaid programs is that medical necessity documentation must be contemporaneous, meaning it must reflect what was known and documented at the time of the service, not reconstructed after the denial.
For Medicaid claims, your team should check the specific state Medicaid fee schedule and coverage policy for the procedure code on the denied claim before gathering documentation. Some states require prior authorization evidence as part of the CO-252 response even when the service category would not typically require prior authorization under Medicare or commercial plans.
CO-252 for BCBS and Major Commercial Payers
Blue Cross Blue Shield plans and other major commercial payers, including Aetna, UnitedHealthcare, Cigna, and Humana, frequently use automated attachment matching systems. When a CO-252 denial arrives from a commercial payer, the first step is to confirm whether the payer’s portal shows an attachment status. BCBS plans in particular have specific portal submission requirements, and faxing documentation without the correct claim reference number in the cover sheet header prevents the payer’s system from matching the document to the claim.
Commercial payer CO-252 denials are most commonly triggered by missing prior authorization confirmation, missing clinical notes for services over a plan-specific dollar threshold, and missing specialist referral documentation for HMO and managed care plans. Your team should review the payer’s specific LCD (Local Coverage Determination) or plan coverage policy for the denied CPT code before submitting documentation, because submitting the wrong document type generates a second denial and resets the timeline.
Managing payer-specific CO-252 workflows is one of the most resource-intensive denial management tasks a billing team faces.
One O Seven RCM’s denial management specialists maintain payer-specific documentation workflows for each major payer category, so your team does not have to rebuild the process from scratch for each denial.
Talk to our denial management specialists.
How to Fix a CO-252 Denial: An 8-Step Resolution Guide for Billing Teams
Resolving a CO-252 denial is a documented, repeatable process, not a judgment call. Practices with a written resolution protocol recover these claims significantly faster than those working each denial from scratch. The eight steps below apply to any CO-252 denial regardless of payer, specialty, or claim type, with payer-specific adjustments noted at the steps where they apply.
Step 1: Read the Entire EOB or ERA Before Doing Anything Else
The first action is not to pick up the phone or open the EHR. It is to read the complete Explanation of Benefits or Electronic Remittance Advice for the denied claim. Specifically, your team must locate the RARC code attached to the CO-252. The RARC is the payer’s specific documentation request, and every subsequent step depends on knowing exactly which RARC code is present. Teams that skip this step and assume they know what is missing frequently resubmit the wrong documentation, creating a second denial and resetting the clock.
Step 2: Separate Denials With a RARC From Denials Without One
Not every CO-252 denial arrives with a RARC attached. If the denial includes a RARC, your team has a specific documentation target and can proceed directly to Step 3. If the denial does not include a RARC, your team must contact the payer directly through their provider portal or by phone before gathering any documentation, because submitting random documentation without knowing what the payer needs wastes time and does not resolve the denial. Flag RARC-less CO-252 denials in your denial tracker as payer-contact required. Our AR follow-up team handles exactly this type of payer outreach.
Step 3: Pull and Verify the Specific Documentation Requested
Once the RARC identifies the missing document type, pull that specific document from the EHR, paper chart, or documentation system and verify three things before attaching it. First, the document covers the exact date of service on the denied claim. Second, the document contains the provider’s signature or authentication where required. Third, the document supports medical necessity for the specific CPT code billed, not a related service or a nearby date. Submitting a document that does not match the claim’s date of service or procedure generates a new denial reason.
Step 4: Label the Documentation Using a Standardized Naming Convention
Payers using automated document matching systems require clearly labeled attachments to match them to the correct claim. Use this naming convention for every document your team submits: ClaimID followed by PatientLastName followed by PatientFirstName followed by CPTCode followed by DocumentType followed by DateOfService as a PDF filename. Example: 12345-Smith-John-27447-OperativeReport-2025-07-12.pdf. Sending an unlabeled document or a full chart dump significantly increases the risk of the payer failing to match the attachment to the claim.
Step 5: Submit Through the Payer’s Preferred Channel With a Cover Sheet
Submission channel matters as much as document quality. The channel hierarchy: payer portal upload is fastest and most reliable, followed by clearinghouse electronic attachment via X12 275 transaction, followed by fax with cover sheet, and finally mail. For fax and mail submissions, your team must include a cover sheet that contains the provider name and NPI, patient name and date of birth, original claim number, claim date of service, and a one-line description: “Resubmission for CO-252 denial, Claim [number], DOS [date]. Attached: [document type]. Provider: [name] NPI: [number].”
Step 6: Resubmit as a Corrected Claim, Not a New Claim
Do not submit a new claim. A new claim submission for a previously denied claim triggers a duplicate claim denial and creates a second denial event on the same service. For CMS-1500 professional claims, use Frequency Code 7 in Box 22 to indicate a corrected claim. For UB-04 facility claims, use a Type of Bill ending in the digit 7, for example 117 for inpatient, to designate a replacement claim. Reference the original claim number in the appropriate field. This designation tells the payer to replace the original denied claim with the corrected version containing the new documentation.
Step 7: Track the Resubmission in a Denial Tracker
Every CO-252 resubmission must be logged in a structured denial tracker before the team moves to the next claim. Minimum required fields: claim ID, patient name, date of service, CPT code, denial code (CO-252), RARC code identified, documentation missing, who gathered the documentation, submission method used, date submitted, confirmation number received, follow-up date, and resolution outcome. This tracking data is the source of pattern analysis that lets your practice identify which providers, CPT codes, or payer combinations are generating systemic CO-252 denials. Our revenue cycle management service builds this infrastructure for your practice.
Step 8: Follow Up and Escalate to Peer-to-Peer Review if Needed
After resubmission, wait the payer’s standard processing period and then follow up using the payer’s portal status tool or by phone. When calling, state the claim number, patient name, date of service, and the resubmission date. Ask for a reference number for the follow-up call. If the payer confirms receipt but the claim shows no movement after the standard adjudication window, escalate to a peer-to-peer review request. A peer-to-peer review is a direct clinical discussion between your treating physician and the payer’s medical reviewer. It is most appropriate when the CO-252 denial involves a medical necessity dispute alongside the documentation issue rather than a pure paperwork gap.
If your billing team does not have a written CO-252 resolution protocol, every denied claim takes longer than it needs to.
One O Seven RCM builds denial-specific resolution workflows for practices and health systems that recover CO-252 revenue systematically rather than case by case.
Contact our team to schedule a denial review.
When and How to Appeal a CO-252 Denial: Timelines, Process, and Sample Language
Resubmitting a corrected claim with documentation resolves most CO-252 denials. When the payer denies the claim a second time after receiving documentation, the resubmission path is closed and the formal appeal process begins. Understanding when to shift from resubmission to appeal saves your team from submitting corrected claims indefinitely while the denial ages past the filing deadline. Every payer has a specific appeal timeline, and missing it results in permanent forfeiture of the claim regardless of whether the documentation is correct.
Appeal Timelines by Payer Type
Medicare:
Federal regulations require that initial redetermination requests be filed within 120 days of the date on the Medicare Remittance Notice. Second-level appeals to a Qualified Independent Contractor must be filed within 180 days. For claims valued above the threshold, providers may escalate to an Administrative Law Judge hearing. CMS publishes the current appeal threshold amounts annually. Confirm the current threshold before deciding whether to escalate. Per the CMS Claims Processing Manual Chapter 22.
Medicaid:
Medicaid appeal deadlines are state-specific and typically range from 30 to 90 days from the date of denial. Your team must review the specific state Medicaid provider manual for the applicable plan before initiating appeal. Some states require an informal reconsideration step before a formal appeal can be filed.
Commercial Payers:
Commercial payer appeal timelines vary by contract, with most plans requiring initial appeals within 30 to 180 days of the denial date. BCBS plans and UnitedHealthcare typically require appeals within 90 days, while smaller regional plans may enforce 30-day windows. Confirm the specific timeline directly from the denial notice or the payer contract because using the wrong timeline is the most common reason recoverable CO-252 appeals are permanently lost.
When to Appeal vs. When to Resubmit
Resubmit as a corrected claim when the denial was caused by missing documentation that your team can now provide and the original claim has not been adjudicated with a final disposition. File a formal appeal when the payer has issued a final denial after receiving documentation, when the payer claims the documentation was insufficient despite your team’s submission of complete records, or when the payer’s internal timelines for reprocessing have expired without resolution. Never submit a new claim when either resubmission or appeal is available. A new claim creates a duplicate denial event and may extend the AR aging well past the appeal window.
Sample Appeal Letter Language
The language below provides the structural framework your team should adapt for CO-252 appeals after a payer has rejected the resubmission. Replace all bracketed fields with actual claim-specific information before submission.
Provider Name: [Practice or Facility Name]
NPI: [10-digit NPI]
Tax ID: [Provider Tax ID]
Payer Name: [Insurance Company Name]
Claim Number: [Original Claim Number]
Patient Name: [Patient Full Name] | Date of Service: [DOS] | CPT Code(s): [Procedure Code(s)]
Re: Formal Appeal of CO-252 Denial
To the Appeals Department: We are formally appealing the denial of the above-referenced claim, denied under CARC CO-252 with [RARC code] indicating [RARC description]. We have attached the following documentation: [List each document by name, date, and authoring provider]. The attached records demonstrate that the services rendered on [Date of Service] were medically necessary based on [brief clinical rationale]. We respectfully request this claim be reprocessed for payment in the amount of [billed amount]. If additional clinical review is required, we request a peer-to-peer review at your earliest availability. [Signature block]
Submit this language through the payer’s designated appeal portal or fax line, not through the standard claims submission channel. Always retain a timestamped copy of every appeal submission and document the reference number provided by the payer’s intake system. Our AR follow-up services team manages the full appeal lifecycle for practices that cannot absorb this volume.
The 2026 HIPAA Attachments Rule and What It Changes for CO-252 Denials
On March 20, 2026, CMS published the final rule for Administrative Simplification: Adoption of Standards for Health Care Claims Attachments Transactions and Electronic Signatures, designated CMS-0053-F. This rule is the most significant regulatory change affecting CO-252 denial workflows since HIPAA’s original transaction standards were adopted. For the first time in US healthcare billing history, there will be a HIPAA-adopted, standardized electronic pathway specifically designed for submitting the documentation that triggers CO-252 denials. Read the CMS fact sheet on CMS-0053-F for the full regulatory text.
What CMS-0053-F Adopts: The Technical Facts
CMS-0053-F adopts two specific X12 transactions as the HIPAA standard for claims attachments: the X12N 275 (Additional Information to Support a Health Care Claim or Encounter, Version 006020X314) and the X12N 277 (Health Care Claim Request for Additional Information, Version 006020X313). X12 issued a formal statement applauding the final rule in March 2026.
CMS-0053-F Key Specifications:
| Field | Detail |
|---|---|
| Rule Designation | CMS-0053-F |
| CMS Fact Sheet Date | March 20, 2026 |
| Effective Date | May 26, 2026 |
| Compliance Deadline | May 26, 2028 |
| Transactions Adopted | X12N 275 (Version 006020X314) and X12N 277 (Version 006020X313) |
| Scope | Health care claims attachments and electronic signatures |
| Prior Authorization | Not included in this final rule |
The X12 275 transaction is the standardized electronic method for a provider to submit supporting documentation to a payer, the equivalent of what billing teams currently do through fax, mail, or portal uploads. The X12 277 transaction is the standardized method for a payer to request additional information from a provider. In plain terms, the X12 277 will eventually replace the informal CO-252 denial notice as the payer’s formal electronic request for documentation, and the X12 275 will be the standardized response.
What This Means for Your CO-252 Workflow Right Now
The May 26, 2026 effective date means the rule is now in force, but the compliance deadline of May 26, 2028 means payers and providers have until that date to fully implement the standardized transactions. During the transition period, your team should not expect payers to stop issuing CO-252 denials in the traditional format. The existing remittance advice and resubmission workflow remains in effect until payer systems are updated.
Practices that begin preparing now by understanding the X12 275 transaction structure and ensuring their practice management system or clearinghouse is on a roadmap for 006020 compliance will face fewer disruptions during the transition. The rule adopts HL7 clinical document standards including C-CDA for the clinical content of attachments, meaning your EHR’s document export format may need to be verified against the 006020 implementation guide. RCM partners with active knowledge of the 006020 timeline are a significant operational advantage right now. Our revenue cycle management team tracks this rollout actively.
CARC and RARC code lists are updated three times per year by CMS, as confirmed in the CMS Claims Processing Manual Chapter 22. Verify RARC code currency before building denial resolution checklists. Using an outdated RARC in an appeal or resubmission cover sheet signals to the payer that the billing team is not current on coding standards.
Preventing CO-252 Denials Before Claims Leave Your Practice
The most efficient CO-252 denial management strategy is the one that prevents the denial from being issued in the first place. Every prevented CO-252 saves your team the rework time, the documentation gathering effort, the resubmission cycle, and the cash flow delay. The prevention system below is built around seven specific process controls that address each of the eight root causes identified in Section 4.
Control 1: Build a Payer-Specific Documentation Requirement Library
Before your team submits any claim to a new payer or for a new procedure type, create a written record of that payer’s specific documentation requirements for that CPT code. Store this library in your practice management system and update it whenever a denial reveals a requirement that was not previously captured. A single documented denial that updates the library prevents every future CO-252 denial for that payer-CPT combination across your entire billing team.
Control 2: Implement a Pre-Submission Documentation Checklist
Complete this checklist before every claim is submitted. This is the most direct prevention tool for CO-252 denials in medical billing.
- Clinical notes for the date of service are attached and signed by the treating provider
- Diagnosis codes (ICD-10) align with and support the procedure codes (CPT) on the claim
- Prior authorization number is documented in the correct field of the CMS-1500 or UB-04 if the payer requires it for this procedure
- Referral documentation is attached if the payer requires a referral for specialist services
- Secondary insurance EOB is attached if this is a coordination of benefits claim
- Supplier invoice is attached if the claim involves DME or supply-intensive procedures
- All required modifiers are present and correctly applied
- NPI, Tax ID, and provider taxonomy code are correctly populated
- Attachment Control Number is recorded if documentation is being transmitted separately
- Payer-specific documentation requirements for this CPT code have been verified against the current payer policy
This checklist should be embedded in your claim submission workflow, not consulted after a denial, because a post-denial checklist review adds rework that was entirely avoidable.
Control 3: Configure Claim Scrubbing Rules for Documentation Triggers
Your practice management system or clearinghouse claim scrubbing tool should have custom rules that flag claims for documentation review before submission. For example, a scrubbing rule that holds any claim for CPT codes that historically trigger CO-252 in your practice until a documentation attachment is confirmed catches the gap before the payer does. Work with your billing software vendor or clearinghouse to build these rules based on your practice’s historical denial data.
Control 4: Conduct Monthly CO-252 Pattern Reviews
Your denial tracker from Section 7 becomes the source for monthly pattern analysis. Group your CO-252 denials by provider, by CPT code, by payer, and by RARC code, and look for repetition. A CO-252 denial that appears three or more times for the same provider, procedure, and payer combination is a workflow failure, not a documentation accident, and it requires a process change rather than another individual resubmission.
Control 5: Train Clinical Staff on Documentation Standards at the Point of Care
CO-252 denials that originate from insufficient medical necessity evidence are ultimately a clinical documentation failure, not a billing failure, and they must be addressed at the point of care, not in the billing department. Regular brief training sessions for treating providers that connect specific CPT codes to the documentation elements payers require reduce medical necessity CO-252 denials at their source. This is particularly effective for physical therapy, mental health, and orthopedic surgery where documentation requirements are both stringent and frequently incomplete at submission.
Control 6: Verify Prior Authorization Status Before Every High-Cost Procedure
Establish a protocol that requires confirmation of prior authorization status before any procedure above a defined dollar threshold is performed. Link this protocol to your front-end intake process so that a claim cannot enter the billing workflow without a verified authorization record for applicable services. Review your payer contract terms governing prior authorization requirements with each payer annually.
Control 7: Establish a Clean Submission Standard for Attachment Transmission
Every documentation attachment must leave your practice with three pieces of information attached: the original claim number, the patient’s name and date of birth, and the Attachment Control Number (ACN) if one was assigned. Without these identifiers, the payer’s intake system cannot match the document to the claim, and the CO-252 denial stands even though the documentation exists. Make this a written standard in your billing department procedures, not an informal practice.
CO-252 Denial Code Scenarios Across Medical Specialties
While the CO-252 denial code description is the same regardless of specialty, the specific documentation that payers require varies significantly across procedure types. Understanding your specialty’s most common triggers allows your billing team to build targeted prevention protocols rather than generic checklists. The six specialty scenarios below represent the highest-volume CO-252 denial contexts based on procedure complexity, documentation intensity, and payer scrutiny levels.
Surgical and Orthopedic Practices
Surgical claims are among the highest-risk categories for CO-252 because payers routinely require operative reports for any procedure above standard complexity. A claim for CPT 27447 (total knee arthroplasty) submitted without the operative report, anesthesia record, and pre-operative evaluation will generate CO-252 from virtually every payer. The operative report must match the CPT code billed specifically. The complexity, technique, and approach documented in the report must correspond to the code description.
Most common trigger documents for surgical CO-252 denials: operative report, pre-operative evaluation notes, pathology report when tissue is removed, and anesthesia record.
Physical and Occupational Therapy
Physical therapy and occupational therapy claims trigger CO-252 when functional assessment data, specifically the objective measures that justify treatment frequency and duration, is missing from the claim submission. A claim for extended rehabilitation sessions requires documentation showing the patient’s baseline functional status, measurable treatment goals, and progress toward those goals at the time of the billed session. Payers administering Medicare therapy benefits apply a heightened documentation review threshold for claims approaching the therapy cap, making contemporaneous assessment records essential for every session claim.
Most common trigger documents: functional assessment scores, progress notes with objective measurements, therapy plan of care signed by the treating provider, and physician referral or plan of care certification.
Mental Health and Group Therapy
Mental health claims, particularly for group therapy billed under CPT codes 90853 and 90849, trigger CO-252 when the session notes do not identify the individual patient within the group context and document their specific participation and clinical response. Billing group therapy units correctly and avoiding CO-252 denials requires session documentation that names the patient, documents their individual therapeutic response, and links the session to the patient’s individualized treatment plan. Payers increasingly require the treatment plan to be on file and current, not just referenced, for ongoing mental health billing.
Most common trigger documents: individual session notes within group format, signed and dated treatment plan, diagnosis-specific medical necessity documentation, and prior authorization confirmation.
Radiology and Diagnostic Imaging
Radiology and imaging claims trigger CO-252 when the clinical order from the referring physician is missing or when the documented diagnosis does not establish the medical necessity for the imaging modality billed. A claim for an MRI of the brain under CPT 70553 requires a referring physician order that documents the specific symptoms or clinical indications that make the imaging medically necessary, not just a diagnosis code on the claim.
Most common trigger documents: referring physician order, clinical indication statement, and in some cases the radiology report itself when the payer requests post-service documentation review.
Durable Medical Equipment (DME)
DME claims have a higher base rate of CO-252 denials than almost any other specialty category because they require a Certificate of Medical Necessity (CMN), a physician order, proof of delivery, and in many cases a supplier invoice. Any one of these can be missing at submission. Noridian specifically identifies the CO-252 plus M23 plus N704 combination as the standard denial pattern for DME claims missing a supplier invoice. A complete DME claim submission requires all four document categories to be present simultaneously.
Most common trigger documents: Certificate of Medical Necessity (CMN), signed physician order, proof of delivery receipt, and itemized supplier invoice with unit cost and delivery confirmation.
Hospital Outpatient and Facility Billing
Hospital outpatient claims submitted on UB-04 forms trigger CO-252 when condition codes, occurrence codes, or revenue code-specific documentation requirements are not met, and when the clinical notes do not establish the outpatient level of care rather than an inpatient or observation level. Facility billing teams must verify that the revenue code and CPT code combination on each service line corresponds to the documentation available in the patient record before submission.
Most common trigger documents: discharge summary or outpatient visit note, procedure documentation matching the revenue code, and authorization documentation for outpatient procedures that require pre-approval.
CO-252 Compared to Related Denial Codes Your Team Should Know
CO-252 does not exist in isolation. It frequently appears alongside or in sequence with other denial codes. Understanding how it compares to related CARCs helps your billing team build a more accurate denial management priority system. The comparison below covers the denial codes most frequently co-occurring with or confused with the CO-252 denial code.
| Code | Full Description | Common Cause | Who Resolves | Appealable? | Resolution Path |
|---|---|---|---|---|---|
| CO-252 | Attachment or documentation required to adjudicate | Missing clinical notes, operative reports, authorization, or invoices | Billing specialist | Yes, after resubmission fails | Gather missing documents, resubmit as corrected claim using Frequency Code 7 |
| CO-16 | Claim lacks information or has submission error | Missing or invalid data in required claim fields (NPI, diagnosis, modifier) | Billing team | Yes | Correct the specific field error, resubmit |
| CO-50 | Not medically necessary | Service not supported by the diagnosis or clinical documentation | Physician and billing team | Yes, with clinical justification | Submit Letter of Medical Necessity with supporting clinical evidence |
| CO-45 | Charge exceeds fee schedule or contracted amount | Billed amount is above the payer’s contracted rate for the service | Billing specialist | Limited | Write off the contractual adjustment; verify fee schedule alignment |
| CO-97 | Service included in another previously adjudicated service | Unbundling or duplicate billing of a component procedure | Medical coder | Yes, with modifier documentation | Review NCCI edits, apply correct modifiers (59, XS, XU, XP, XE) if appropriate |
| M127 | Missing patient medical record for the service | Payer requested the full medical record to support claim adjudication | Billing specialist | Yes | Submit the complete medical record for the date of service with a cover sheet |
CO-45 is the only code in this table that is generally not correctable through documentation. It represents a contractual rate adjustment that your practice must write off as a standard adjustment rather than work as a denial. M127 deserves specific attention because it often appears as a companion code to CO-252 when the payer has moved beyond a single document request to requesting the complete medical record. Practices with recurring M127 denials alongside CO-252 should audit their clinical documentation completeness at the point of care rather than treating each denial individually. Our denial management team runs exactly this type of pattern audit.
A Note on CO-253: Medicare Sequestration
CO-253 is a distinct code from CO-252 and represents a mandatory 2% reduction in Medicare payments under federal sequestration law as established by the Budget Control Act of 2011. Unlike CO-252, CO-253 is not a denial that can be appealed or corrected. It is a mandatory contractual adjustment that providers must write off, and it applies to all Medicare fee-for-service claims for dates of service from April 1, 2013 through 2032.
Frequently Asked Questions About the CO-252 Denial Code
What does the CO-252 denial code mean?
CO-252 means a payer has suspended payment on your claim because required documentation or an attachment was not included with the submission. The official X12 description states: “An attachment/other documentation is required to adjudicate this claim/service.” This is not a permanent denial. The claim can be reprocessed once your team submits the missing documentation through the payer’s accepted channel. The CO prefix indicates that the financial responsibility for resolving this denial belongs to the provider, not the patient.
What is the CO-252 denial code description in full?
The full CO-252 denial code description as published by X12 is: “An attachment/other documentation is required to adjudicate this claim/service. At least one remark code must be provided, which may include either the NCPDP Reject Reason Code or a Remittance Advice Remark Code that is not an ALERT.” The accompanying RARC code identifies the specific document type that is missing.
What is the reason code 252 for Medicare?
For Medicare claims, reason code 252 indicates that the Medicare Administrative Contractor (MAC) requires an attachment or supporting documentation before the claim can be adjudicated. Medicare resolves CO-252 through its Additional Documentation Request (ADR) process. Providers have 7 calendar days to respond by fax or 10 calendar days by mail from the ADR issuance date. Electronic submission is available through the CMS esMD system. Missing these ADR response deadlines results in a final denial that cannot be reversed through the standard resubmission process.
Is CO-252 a permanent denial?
CO-252 is not a permanent denial. It is a temporary suspension of claim payment pending receipt of required documentation. Once your billing team identifies the missing document using the accompanying RARC code, gathers the correct documentation, and resubmits through the payer’s accepted channel, the claim moves back into adjudication. The denial becomes permanent only if the resubmission window expires without a response or if the payer issues a final denial after reviewing submitted documentation.
What is the difference between CO-252, PI-252, and PR-252?
The prefix before 252 determines who carries financial responsibility. CO-252 (Contractual Obligation) means the provider must resolve the documentation gap and the patient cannot be billed. PI-252 (Payer Initiated) means the payer flagged the claim on their own review, and your team should contact the payer for clarification. PR-252 (Patient Responsibility) is rare and indicates the patient may be billed, but only after verifying the patient received appropriate coverage notice such as an Advance Beneficiary Notice. Section 2 of this guide provides a full comparison table for all three variants.
What RARC codes come with a CO-252 denial?
The most common RARC codes paired with CO-252 are N479 (missing EOB or coordination of benefits), N710 (missing clinical notes), N712 (missing summary), N714 (missing report or lab results), N716 (missing patient chart), N102 (documentation not received), M51 (missing or incomplete information), N4796 (missing EOB or Medicare Secondary Payer evidence), M23 (missing supplier invoice for DME claims), and N704 (additional information required from the provider). Section 5 of this guide provides the complete RARC table with specific submission instructions for each code.
Can I bill the patient for a CO-252 denial?
No. Because CO-252 carries the CO (Contractual Obligation) group code, the financial responsibility for the adjustment belongs to the provider. Billing the patient for a CO-252 denial violates the terms of the provider’s contract with the payer and may constitute a HIPAA violation. The only exception is PR-252, where the patient responsibility group code is present, and even then, billing is only appropriate after verifying the patient received appropriate advance notice of potential cost-sharing.
How long does it take to resolve a CO-252 denial?
A CO-252 denial that includes a RARC code and involves readily available documentation typically resolves within 14 to 30 days of resubmission, depending on the payer’s standard adjudication timeline. Denials without a RARC code require direct payer contact before documentation can be gathered, which adds 7 to 14 days to the process. Medicare ADR responses that miss the submission window require a formal appeal, extending the timeline to 60 to 120 days depending on the level of appeal. Practices with a written CO-252 resolution protocol consistently achieve faster resolution times than those working each denial without a defined process.
What does the 2026 HIPAA attachments rule change about CO-252?
The CMS final rule CMS-0053-F, effective May 26, 2026 with a compliance deadline of May 26, 2028, establishes X12 275 and X12 277 Version 6020 as the HIPAA-adopted standards for claims attachments. When fully implemented, X12 277 will be the standardized electronic request for additional information from payers, replacing the informal CO-252 denial notice for documentation requests. X12 275 will be the standardized electronic submission method for providers responding with documentation. During the transition period through May 2028, existing CO-252 remittance workflows remain in effect while payers and providers implement the new standardized transactions.
What is the co 252 denial code reimbursement impact on a practice?
A single CO-252 denial suspends the full billed amount until documentation is received and the claim is reprocessed. Across a practice with regular CO-252 volume, this can suspend tens of thousands of dollars in AR simultaneously. One hospital system had $122,302,768 in revenue at risk from 4,223 CO-252 denials in a single year. For smaller practices, even 50 unresolved CO-252 denials at an average claim value of $400 represent $20,000 in suspended reimbursement. The reimbursement impact is recoverable, but only if the denial is worked within the payer’s resubmission window.
How One O Seven RCM Helps Healthcare Providers Recover and Prevent CO-252 Denials
Managing CO-252 denials at scale requires more than knowing what the code means. It requires a structured denial management workflow, payer-specific documentation libraries, trained specialists who understand RARC codes at the claim level, and the capacity to monitor resubmission status across dozens or hundreds of open denials simultaneously. Most billing teams working co 252 denial code medical billing environments are doing so reactively, working denials after they accumulate rather than preventing them at the point of submission. At One O Seven RCM, we build the front-end prevention protocols and the back-end recovery workflows simultaneously, so your practice stops losing revenue to the same denial code month after month.
Denial Management:
Our denial management team identifies the root cause of your CO-252 pattern, whether it is a documentation gap at the clinical level, a coding error, a prior authorization failure, or an EDI transmission issue, and builds the correction at the source.
Medical Billing:
Our medical billing services team verifies documentation completeness before every claim submission, applying payer-specific checklists that prevent CO-252 denials before they are issued rather than correcting them afterward.
AR Follow-Up:
For CO-252 denials that require direct payer contact, appeal filing, or peer-to-peer review coordination, our AR follow-up team manages the full resolution cycle and tracks every open denial to its final disposition.
Revenue Cycle Management:
Our full revenue cycle management service integrates denial prevention, claims submission, AR follow-up, and reporting into one continuous workflow so that CO-252 denials and every other denial type are identified, worked, and resolved as part of your standard revenue cycle, not as a backlog.
Ready to Stop CO-252 Denials From Blocking Your Revenue
CO-252 denials are preventable, recoverable, and manageable, but only with the right documentation standards, payer-specific workflows, and denial tracking infrastructure in place. Practices that treat CO-252 as a one-off documentation problem instead of a systemic workflow indicator continue to see the same denial repeat across providers, procedure types, and payers. One O Seven RCM builds the system that stops that cycle.
Our team works with healthcare providers across specialties to reduce denial rates, accelerate cash flow, and recover revenue from CO-252 denials and every other denial type your practice encounters. Whether you need a full revenue cycle management partner or targeted support for denial management and AR follow-up, we build the solution around your practice’s specific billing environment.
Contact One O Seven RCM today to schedule a denial review and learn what your CO-252 pattern is costing your practice in recoverable revenue.