The CO-246 Code Explained: A Triage Guide for Non-Payable Reporting Lines

How many line items on your aging report right now carry CO-246? If you had to pull the report to answer, you already know where this is going. Most billing teams treat CO-246 as background noise, a code that shows up, pays nothing, and gets ignored. That works fine right up until it doesn't. Here is the short answer to the question. The majority of CO-246 lines on your report are exactly what they claim to be, informational rows that were never going to pay. The payer is acknowledging the line, not denying it. But a minority of those lines sit on top of real, collectible revenue that got coded or mapped wrong somewhere upstream, and the practices that lose money on CO-246 are the ones that never separate the two groups. This post gives you a working triage. Three questions, asked in order, sort every CO-246 line into 'post it and move on' or 'fix the claim and rebill.' You will also get the posting rules that keep these lines from polluting your AR, because a report clogged with zero-pay informational rows is a report that hides the balances you can still collect. One framing note before we start. CO-246 belongs to a small family of codes that are not denials in the normal sense. Handle it with your standard appeal workflow and you will waste time. Ignore it completely and you will occasionally eat a payable service. The skill is knowing which lines are which.

The official CARC text reads: 'This non-payable code is for required reporting only.' Twelve words, and two of them do all the work. Non-payable means the line was never priced for payment. Required reporting means the payer is returning the line because a mandate, a program rule, or a claim structure obligates them to acknowledge it on the remittance. Notice what the text does not say. It does not say the service was denied. It does not say medical necessity failed, or that a modifier was missing, or that the patient owes the balance. A true CO-246 line carries no patient responsibility and no appeal path, because there is nothing to appeal. The payer processed the line exactly as the claim asked them to. The CO group code trips people up. CO stands for contractual obligation, and on most codes in our denial code library that group code means the provider absorbs the difference. On 246 the group code is close to meaningless in dollar terms, since the billed amount on a reporting line is typically zero or symbolic to begin with. That is the theory. In practice, remittances are messier, because CO-246 also appears when something upstream went sideways, and the remittance looks identical in both cases. The code cannot tell you which situation you are in. Your triage has to.

Legitimate CO-246 lines cluster into four patterns. Informational reporting lines. Some payer programs and federal mandates require the payer to return specific line items on the remittance even though no payment attaches. The line exists so both sides have a record that the service or data element was reported. Quality reporting line items. Practices that submit quality data codes on claims will see those codes come back with CO-246. The code did its job the moment the payer received it. Zero dollars is the correct outcome. Zero-pay service lines the payer acknowledges but does not price. Certain services get reported for completeness, and the payer's system confirms receipt without assigning an allowable. The acknowledgment is the entire transaction. Bundled reporting rows tied to a paid line. Sometimes a claim carries a row that exists to support or document another service on the same claim. The paired line gets priced and paid, and the reporting row comes back as CO-246. As long as the paid line paid correctly, the claim performed as intended. Read those four again and one thread stands out. In every legitimate case, nobody at the practice expected a check for that specific line. That expectation, or the absence of it, is the hinge for everything that follows. When a CO-246 lands on a line you billed expecting an allowable, you are looking at the exception, and the exception is where the money is.

Run every CO-246 line through three questions, in this order. Most lines exit at question one in about ten seconds. Question one: did we expect payment on this line? Pull the charge and check what was billed. A zero-dollar quality code, an informational row, a data-only line, none of those expected payment, and the CO-246 confirms normal processing. Post it and move on. But if the line carries a real charge amount tied to a real service, a service your fee schedule prices and your contract covers, the answer is yes, and you keep going. Question two: does a payable equivalent code exist? This is where most of the recoverable money hides. A service sometimes gets reported with a non-payable code when a payable equivalent exists for the same clinical work. Wrong code choice at charge entry, an outdated charge master row, a crosswalk that mapped the service to the reporting code instead of the billable one. Check the code set for the service you actually performed. If a payable code describes it accurately, the fix is a corrected claim, and the revenue is real. Question three: is the paired line paid correctly? For bundled reporting rows, the CO-246 line is only fine if its partner paid. Find the paid line it supports, verify the allowed amount against your contract, and confirm the payment posted. A CO-246 row next to an underpaid or missing primary line means the claim needs attention even though the 246 itself is behaving. Two outcomes, and only two. Lines that pass triage post as zero-pay informational and never touch your worklist again. Lines that fail question one and then surface a problem at question two or three go to a biller for claim correction. Note the word correction. You cannot appeal CO-246 as CO-246, because the payer applied it exactly as the claim instructed. The remedy is a corrected claim, resubmitted with the payable code, which restarts adjudication on the right footing.

If a CO-246 line fails triage, one of three upstream failures put it there. Wrong code combinations come first. A claim built with a reporting code where the encounter supported a payable service means the payer never saw a billable line at all. The remittance looks clean, the code behaves exactly as documented, and the practice quietly forfeits the allowable. Nobody flags it, because nothing was denied. The second failure is a payable equivalent nobody selected. Code sets change every year. A code that paid last year can shift status, or a new payable code can appear for work your team is still reporting the old way. Charge masters and EHR favorites lists preserve stale choices indefinitely unless somebody audits them. Payer mapping errors are the third and rarest. Occasionally the payer's own system maps a payable service to the reporting code. This is the one variant where the fix runs through the payer rather than through a corrected claim, since your claim was right and their adjudication was not. Call, get the mapping acknowledged, and request reprocessing. One pattern deserves special attention. The same wrong code fails the same way on every claim it touches, so one recoverable CO-246 line almost always has dozens of siblings. When triage surfaces one, pull that code across your last six months of remittances before you fix anything, then batch the corrections. Finding the root cause once and fixing it everywhere beats rediscovering it one remittance at a time.

Payment posting is where CO-246 either stays harmless or starts lying to you. Three rules keep it honest. Post CO-246 lines as zero-pay informational adjustments. The line closes with a specific adjustment code your reporting can isolate later, the balance goes to zero, and the claim's paid lines post normally around it. Never write these lines off against expected revenue. A write-off says 'we expected this money and accepted the loss.' On a legitimate CO-246 line, no money was expected, so a write-off distorts your net collection rate and your adjustment trending in the same stroke. Worse, on a line that failed triage, a write-off buries recoverable revenue under a code nobody reviews. Never leave CO-246 lines sitting as open AR. This is the most common failure and the most corrosive. Open zero-pay lines age like any other receivable. Sixty days later your aging report shows a swollen 61-90 bucket full of balances that were never collectible, your team burns follow-up time touching them, and the genuinely collectible balances get less attention because the worklist is bloated. If months of this have already bent your aging out of shape, a structured AR recovery cleanup separates the noise from the money faster than working the list line by line. The test of good posting is simple. A month after the remittance, could you pull every CO-246 line, see it closed at zero, and confirm none of it counted against expected collections? If yes, your books are telling the truth.

Initial denial rates hit 11.8 percent in 2024, per Kodiak Solutions, and HFMA benchmarks show up to 65 percent of denied claims are never resubmitted. CO-246 sits in an odd corner of those numbers. Counted naively, it inflates your denial rate with lines that were never denials. Ignored entirely, it feeds the never-resubmitted pile with the minority of lines that deserved a corrected claim. So handle it in both directions. Exclude confirmed informational CO-246 lines from your denial rate calculation, or your trending will overstate the problem and dull the signal from denials that matter. Then route the triage failures into your standard rework queue with everything else. At an average rework cost of 25 dollars per claim, per MGMA, the math on batch fixes is friendly. One root-cause correction to a charge master row can prevent hundreds of future touches. The habit to build is small. Every remittance run, someone asks the three questions of every CO-246 line above a dollar threshold you set. Ten minutes, most days. The payoff is an AR report you can trust and a denial rate that measures reality. If your team does not have those ten minutes, or the backlog has already grown into the aging, our denial management services team runs this exact triage as part of standard remittance review. Either way, stop letting a reporting code write itself into your revenue numbers unchallenged.