Skip to main content

N61 Remark Code: Rebill Services on Separate Claims

N61 means the payer wants the services rebilled on separate claims. Something about the combination, such as different dates spanning benefit periods, locations, providers, or claim types, prevents the payer from processing them together.

Quick facts

Code
N61 (RARC N61)
Status
Active In use since January 1, 2000.
Code set
Remittance Advice Remark Codes (RARC)
Group codes
  • CO (Contractual Obligation): The claim is denied as a billing format issue the provider must fix. It is not a patient balance.
  • OA (Other Adjustment): Some payers report it as another adjustment, meaning the claim could not be processed as structured.
Official description
Rebill services on separate claims.
X12 Remittance Advice Remark Codes, retrieved September 25, 2026
Last verified
against the official X12 list.

What N61 means

A claim is supposed to hold services that share certain characteristics, such as the same patient, billing provider, and often the same benefit period or place of service. When a claim mixes services that the payer’s system must process separately, it may return the whole claim with N61 and ask you to break it up.

N61 is a general instruction. It frequently appears with CARC 16, CARC 239, or CARC 268, which hint at the reason for the split.

Common causes

  • Dates of service cross the patient’s coverage start or end date.
  • Services span two calendar years or benefit years.
  • Services at different locations or with different CLIA numbers were combined.
  • Services by providers with different billing arrangements were combined on one claim.
  • Services for different benefit types, such as medical and behavioral health carve-outs, were combined.

How to fix it

  1. Figure out the split by reading the paired CARC and comparing dates, locations, and providers across the lines.
  2. Create separate claims so each contains only services that belong together.
  3. Carry over all required data, including diagnoses, authorizations, and referring providers, to each new claim.
  4. Submit them as new claims unless the payer asks for a replacement or void process.
  5. Track timely filing, since the new claims should go out promptly.

How to prevent it

Configure your billing system to split claims automatically at coverage changes, year boundaries, and location changes. Monthly or recurring services are especially prone to these splits, so review them before release.

Codes that may appear with N61

  • CO-16 (Claim/service lacks information or has submission/billing error(s).): A submission error, specifically how services were grouped on the claim.
  • CO-239 (Claim spans eligible and ineligible periods of coverage.): The claim spans eligible and ineligible coverage periods, so separate claims are needed.
  • CO-268 (The Claim spans two calendar years.): The claim spans two calendar years and should be split by year.
  • N62 (Dates of service span multiple rate periods.): Dates of service span multiple rate periods; resubmit separate claims.
  • N74 (Resubmit with multiple claims, each claim covering services provided in only one calendar month.): Resubmit with one claim per calendar month.
  • N93 (A separate claim must be submitted for each place of service.): A separate claim is needed for each place of service.
  • N63 (Rebill services on separate claim lines.): Rebill on separate lines of the same claim instead of separate claims.

N61 FAQ

Does N61 tell me how to split the claim?

Not directly. Look at the CARC and any other remark codes, and at what differs among the services, such as dates, locations, or providers. If it is still unclear, ask the payer.

Should the new claims be replacements?

Usually each split portion goes as a new claim, since the original was not processable. Some payers want the original voided first, so follow their instructions.

Will splitting look like duplicate billing?

Not if each claim contains different services or dates, and the original was denied. Keep the N61 remittance on file to explain the resubmission.