Skip to main content

N379 Remark Code: Claim and Line Information Don't Match

N379 means information reported at the claim level does not agree with the information on the service lines. Common examples are a claim total charge that doesn't equal the sum of the lines, or claim dates that don't cover the line dates.

Quick facts

Code
N379 (RARC N379)
Status
Active In use since December 1, 2006.
Code set
Remittance Advice Remark Codes (RARC)
Group codes
  • CO (Contractual Obligation): The claim was denied or rejected for an internal inconsistency the provider can fix. The patient is not billed for this adjustment.
Official description
Claim level information does not match line level information.
X12 Remittance Advice Remark Codes, retrieved September 25, 2026
Last verified
against the official X12 list.

What N379 means

A claim has two layers: claim-level information that applies to the whole bill, and line-level information for each service. The two have to agree. N379 says they don’t, so the payer can’t trust either layer enough to process the claim.

N379 almost always explains CARC 16. The fix is mechanical, but you have to find which value is off.

Common mismatches

  • Charges. The claim total (box 28 on the CMS-1500) doesn’t equal the sum of the line charges in box 24F.
  • Dates. On institutional claims, the statement period doesn’t include every line’s service date. On professional claims, claim-level dates such as hospitalization dates conflict with line dates.
  • Providers. A rendering provider at the claim level conflicts with a different one at a line, in a way the payer doesn’t accept.
  • Paid amounts. On secondary claims, the claim-level prior payer paid amount doesn’t equal the sum of line-level prior payments.
  • Diagnosis pointers referencing diagnoses that aren’t listed at the claim level.

How to fix it

  1. Open the claim as sent (or the clearinghouse report) and compare the claim-level totals and dates with the lines.
  2. Recalculate totals after any line edits and confirm the statement or claim dates span all lines.
  3. For secondary claims, reconcile claim-level and line-level COB amounts against the primary remittance.
  4. Correct the data and resubmit: a corrected claim with frequency code 7 if the payer adjudicated it, or a new claim if it was rejected. See claim rejection vs denial.

How to prevent it

Rebuild the claim from the charges rather than editing claim totals by hand. Pre-submission checks in Claims Validator can compare claim-level totals and dates with line data before the file goes out.

Codes that may appear with N379

  • CO-16 (Claim/service lacks information or has submission/billing error(s).): The claim has a submission or billing error; N379 says the claim and line data conflict.
  • M54 (Missing/incomplete/invalid total charges.): Used when total charges are missing or invalid.
  • N345 (Date range not valid with units submitted.): Says a line's date range is not valid with the units submitted.
  • N64 (The 'from' and 'to' dates must be different.): Says the from and to dates must be different.

N379 FAQ

What are the most common claim and line mismatches?

Total charges that don't add up, claim statement dates that don't include every line date, and claim-level diagnosis or provider data that conflicts with line-level entries.

Is N379 a rejection or a denial?

Often it's caught at the front end as a rejection, but some payers adjudicate and deny with N379. If the claim was never accepted, send a new claim rather than a corrected one.

Why would my system create a mismatch?

Editing a line after the claim was built, deleting a line without recalculating the total, or manually overriding claim dates are common causes.