RemitBench/Denial codes/N823

N823 remark code

N823 means a modifier on the line is wrong. It is there, and the payer will not accept it. That is a narrower problem than it sounds, and usually a quick one.

Where N823 sits on the line

Three fields, and only two of them move money. This is the part that stops offices posting from the wrong one.

Reason code 16 says nothing on its own, which is why the code list requires a remark with it. The CO-16 page covers that side, including the important difference between a claim that was denied and one that was never processed.

The two reason codes it is allowed to ride on

The industry combination table approves this remark with two reason codes, and only one of them is about your modifier.

Some payers go outside that table. One Medicaid plan's published list attaches this remark to reason codes 4 and 96 as well. That is not what the table says, and it is what the plan does, so check what you actually received rather than what should have arrived.

Why the payer sent it

Published payer code lists show five distinct shapes behind this one remark. Knowing which one you have decides how long the fix takes.

1. The modifier does not belong on that procedure

The most common case. The modifier is real, and it is not allowed with that code. One plan's list puts it plainly: the modifier is invalid for the procedure code. Another says the use of the modifier is incorrect for the procedure under coding or plan guidelines.

2. The modifier is not real

Mistyped, retired, or invented. Modifiers get deleted from the code sets, and software that was set up years ago keeps sending them. This is the fastest fix and the one most likely to be affecting other claims too.

3. The modifier conflicts with something else on the claim

Some modifiers cannot stand alone. One plan's list has a row saying a GK modifier cannot be submitted by itself, and that another line on the same claim has to carry a GA or a GZ. Another row limits how many lines may carry a particular modifier on the same date. Nothing is wrong with the modifier itself. The problem is the claim as a whole.

4. A pricing system rejected it

Outpatient, dialysis and surgery center claims run through their own pricing programs, and those programs have their own modifier rules. Several rows in one plan's list are pricer rejections rather than coding errors. These need the payer's billing guide for that claim type, not the general modifier rules.

5. Your own modifier told them to deny it

Two plans report lines carrying a GY or a GZ modifier under this remark. Those modifiers are how you tell a payer in advance that you expect the line not to be paid.

N823 and N822 are a pair, and payers blur them

The code list splits modifier problems in two. N823 is for a modifier that is present and wrong. N822 is for one that is missing. Both were added on the same day in 2019 and revised together that November. The revision widened them: the first wording covered only HCPCS modifiers, and the current wording covers any procedure modifier.

The split does not survive contact with real remittances. One health plan has a single row filed under N823 whose own message covers both cases at once: the required modifier is missing, or the modifier is invalid for the procedure code. Another has rows under N823 saying the modifier was not reported.

The clearest proof comes from two Medicaid plans owned by the same company and working from the same internal code list. Both publish a crosswalk. On one internal code meaning "this is not a valid modifier for this code", one plan sends N822 and the other sends N823. On a second code, they swap. Same company, same edit, opposite codes.

What to do next

1. Read the payer's own message

   It usually names the modifier or the rule. That sentence is worth more than the standard code beside it, and it tells you which of the five cases above you are in.

   If the message names a pricing program: you are in case four. Go to that payer's billing guide for that claim type. General coding rules will not help you.

2. Check whether the modifier is still a real modifier

   Ten seconds, and it rules out the easiest cause. If it was retired, find where your software is adding it and fix it there.

   If it is retired: check what else is going out with it right now. This kind of error is never on one claim.

3. Check the modifier against the procedure code

   Not every modifier goes with every code. Some codes already include what the modifier describes, so adding it contradicts the code itself.

   If the modifier does not fit: ask what you were actually trying to say, then find the modifier that says it. If nothing does, the line may simply not be separately payable.

4. Look at the whole claim, not just the line

   Case three hides here. A modifier that needs a partner line, or one that may only appear once per day, produces an error on a line that looks perfectly correct by itself.

5. Correct and resend

   Reference the original claim number and use that payer's corrected claim route. A plain new claim usually comes back as a duplicate.

   Watch the filing clock. A rejected claim generally does not stop the filing deadline. Work these ahead of older, quieter denials.

Codes N823 gets confused with

N823 against CARC 4

These two overlap enough to be worth a paragraph. Code 4 is a reason code with its own dollar amount, and it names one specific problem: the modifier and the procedure code do not go together. N823 is a remark, so it needs a reason code to carry the money, and it covers a wider range including retired modifiers, claim level conflicts and pricing rejections.

In practice which one you get depends on the payer, not on the error. Both mean look at the modifier.

When not to appeal

• The modifier was genuinely wrong. Correct and resend. That is faster and it is honest.
• The modifier was retired. There is nothing to argue about a code that no longer exists.
• The claim came back as unprocessable rather than denied. A claim that was never processed carries no appeal rights.
• You have not read the payer's message yet. An appeal that guesses gets the same answer back.
• You put a GY or GZ on the line yourself. You told the payer to deny it.

Appeal when you can show the modifier was correct for that procedure at that payer, and quote the rule that says so. Payer edits do go wrong, especially after a code set update in January. Those appeals win, and they usually fix the edit for everyone.

Does N823 show up in dental?

We found no evidence that it does, and saying so is more useful than guessing.

One large dental carrier publishes a mapping from its own processing policies to the standard codes, running to more than 900 policy rows across 354 pages. Neither N823 nor N822 appears in it anywhere. That is not proof that no dental plan has ever sent one, and it is the best published dental evidence available.

The reason is structural. Dental claims carry very few modifiers. The work is identified by tooth number, surface, quadrant and arch instead, and when those are wrong the payer sends one of the tooth and surface remarks listed on the CO-16 page.

The place a dental office does meet this code is on medical claims. Oral surgery, sleep appliances and anesthesia billed to a medical carrier are judged by medical rules, and medical rules run on modifiers.

Related codes

• RARC N822 The other half of the pair. A modifier that is missing rather than wrong, at least in theory.
• CO-16 The reason code this remark rides on, and why the work here is a correction rather than an appeal.
• CO-50 What the GY and GZ modifiers actually do, and why Medicare reports those lines with a different code entirely.
• CO-97 Where a correct modifier can lift a bundling edit, when the record supports it.
• RARC N130 The opposite kind of remark. It names nothing and sends you to the plan document.
• CARC 4 The modifier is inconsistent with the procedure code. The reason code version of this problem. No page yet.

Back to all denial codes