NJ Medicaid Claims Rejection Codes: The Top 10 Denials Costing Home Care Agencies Revenue (and How to Fix Them)

A rejected Medicaid claim is not just a delayed payment — it is a fully-loaded operational cost. Your aide already delivered the service. You already paid the labor. You already booked the receivable. When the rejection lands two weeks later, you have already absorbed every cost of the visit and you are starting the work over from scratch.

For most New Jersey home care, MLTSS, and HCBS agencies we work with, the largest preventable revenue leak is not unbillable hours or unfilled shifts — it is the 8–14% of clean-looking claims that come back rejected for reasons the agency could have caught before submission.

This guide breaks down the ten rejection codes we see most often on NJ Medicaid and MCO remittances, the root cause behind each, and the workflow controls that prevent them from recurring. If you fix even three of these, you typically recover 4–6% of net revenue within a single billing cycle.

How NJ Medicaid Rejections Actually Flow

Before the codes themselves, it helps to remember the path a claim travels — because rejections happen at three different layers and each layer demands a different response.

1. Clearinghouse / front-end edits. Your claim is rejected before it ever reaches the payer. These never appear on an 835 remittance. You see them in the clearinghouse report or in HHAeXchange's pre-billing scrub.
2. Payer acknowledgment (277CA). The MCO (Horizon NJ Health, UnitedHealthcare Community Plan, Aetna Better Health, Wellpoint, Fidelis) accepts or rejects the claim at the EDI gateway. A 277CA with status A7 means the claim was rejected and never adjudicated.
3. Adjudication (835 remittance). The claim was adjudicated and denied. You receive a Claim Adjustment Reason Code (CARC) and often a Remittance Advice Remark Code (RARC) explaining why.

The fix for a 277CA rejection (resubmit a corrected claim) is fundamentally different from the fix for an 835 denial (correct and resubmit, or file a formal appeal within the MCO's window — typically 90 days for NJ MCOs, 180 days for FFS).

Operational rule of thumb: if you cannot tell at a glance which layer rejected a given claim, your revenue cycle reporting is the first thing to fix. Everything downstream depends on it.

The Top 10 Rejection Codes We See on NJ Medicaid Claims

The codes below are a mix of CARC (standard X12 reason codes), RARC (remark codes), payer-proprietary codes, and HHAeXchange / Sandata pre-billing rejections. We have ordered them by dollar impact, not frequency.

1. CARC 16 + RARC N290 / N257 — "Missing/incomplete/invalid rendering provider info"

What it means: The NPI, taxonomy, or Medicaid ID of the rendering provider (often the aide or the supervising nurse) is missing, expired, or does not match what the MCO has on file.

Root cause in NJ: The most common version of this in MLTSS is a caregiver whose NJ Medicaid provider enrollment lapsed at the annual revalidation, or an aide who was added to the roster after the agency's last 837P loop was tested.

Fix: Pull the rendering provider from the rejected claim and verify against the NJ Medicaid Provider File and the MCO's roster. Re-enroll if needed, then resubmit. The corrected claim does not need an appeal — it just needs the loop 2310B / 2420A NPI to match payer records.

Prevention: A monthly cross-check between your aide roster and the NJ Medicaid Management Information System (NJMMIS) catches lapsed enrollments before they reach payroll.

2. CARC 197 — "Precertification/authorization/notification/pre-treatment absent"

What it means: The service was rendered but no active authorization covers the date or units billed. This is the single most expensive denial in MLTSS and DDD because it almost always means hours have already been paid out.

Root cause in NJ: Three patterns dominate:

• Authorization expired mid-week and the office did not renew before the visit was billed.
• Units exhausted — the member had 20 hours/week approved but received 22 because of a weekend coverage swap.
• Wrong service code — the auth is for T1019 (personal care) but the claim was submitted as T1020 (per diem), or for the wrong DDD service code under the Fee-for-Service Manual.

Fix: Stop the bleeding first. Pull every open auth for the affected member, recalculate available units, and decide whether to bill against another active auth, request a retro-auth (most NJ MCOs allow this within 14 days for MLTSS personal care), or write off the over-utilization.

Prevention: This is a scheduling problem masquerading as a billing problem. Real-time authorization checking at the moment a visit is scheduled — not after it is delivered — eliminates 80–90% of CARC 197 denials. See our deeper breakdown in NJ DDD Units & Authorizations Guide.

3. CARC 18 — "Exact duplicate claim/service"

What it means: A claim for this member, date, and service has already been submitted.

Root cause in NJ: Surprisingly, this is rarely operator error. The most common cause we see is the EVV-to-billing handoff firing twice — once on visit completion, once on payroll close — when both processes export to the billing engine without a deduplication key.

Fix: Identify which of the duplicate claims paid and void the other. Do not appeal — there is nothing to appeal against.

Prevention: Use a deterministic claim ID (member ID + DOS + service code + start time) as a uniqueness constraint at the billing-engine entry point. If your billing tool cannot enforce this, push the check upstream into your visit-to-claim adapter.

4. CARC 109 — "Claim/service not covered by this payer/contractor; you must send to the correct payer"

What it means: The claim was sent to an MCO that does not have the member on their roster as of the date of service.

Root cause in NJ: NJ FamilyCare members change MCOs frequently. A member who was on Horizon NJ Health in March may be on Aetna Better Health in April. If your EVV system caches the member's payer assignment, you will keep billing the wrong MCO.

Fix: Re-verify the member's MCO assignment for the date of service via NJMMIS Eligibility Verification or 270/271 EDI. Resubmit to the correct payer.

Prevention: Run a 270 eligibility check the morning of (or the day before) every scheduled visit. The cost of automating this is trivial compared to the cost of a single rebilled month.

5. CARC 96 + RARC M51 — "Non-covered charge(s); missing/incomplete/invalid procedure code(s)"

What it means: The HCPCS or CPT code billed is not on the member's benefit plan, or the modifier combination is invalid for that code under the NJ Medicaid fee schedule.

Root cause in NJ: This shows up constantly with the U modifiers used in NJ MLTSS personal care (T1019 U1, T1019 U2, etc.) and in DDD where service codes have changed multiple times since the iRecord / iSelect overhaul.

Fix: Check the modifier against the active NJ MLTSS Personal Care Services fee schedule and the DDD Fee-for-Service rate file. Correct and resubmit. Do not resubmit without the modifier change — the payer will reject again with the same code.

Prevention: Centralize your service-code-to-authorization-type mapping in one place that your scheduler, EVV system, and billing engine all reference. Drifted mappings between systems are the underlying cause.

6. CARC 252 + RARC N657 — "An attachment/other documentation is required to adjudicate this claim or service"

What it means: For certain higher-acuity services (skilled nursing under MLTSS, behavioral supports under DDD), the MCO is asking for a plan of care, nursing note, or service log before paying.

Root cause in NJ: Horizon NJ Health and Aetna Better Health both began requiring attachments for T1001–T1003 and certain DDD codes more aggressively starting in 2024. Many agencies still submit these as if they were professional claims with no documentation.

Fix: Submit the required attachment via the MCO provider portal or the 275 transaction, referencing the original claim's payer claim control number (PCN).

Prevention: Tag any service-code/payer combination that requires attachments in your billing rules so the claim is held until documentation is uploaded. Submitting without the attachment and waiting for the denial wastes 30+ days.

7. HHAeXchange Pre-Bill Rejection: "Member not found" / "Member ID mismatch"

What it means: This one never reaches an MCO — HHAeXchange rejects the claim during the pre-bill scrub because the member's Medicaid ID, MCO assignment, or contract on the agency's side does not match the master member record.

Root cause: Eligibility files drift. An MCO may transmit the member's new ID, but the agency's HHAeXchange instance still holds the prior one.

Fix: Detailed troubleshooting in our member-not-found errors in HHAeXchange post — but the short version is to re-sync the member from the MCO contract, then re-export the visit.

Prevention: Schedule a nightly job that diffs the MCO 834 / eligibility roster against your HHAeXchange member master and queues mismatches for review before the next billing batch.

8. CARC 29 — "The time limit for filing has expired"

What it means: You missed the timely filing window. For most NJ MCOs that is 180 days from date of service for initial submission and 90 days from denial for resubmission, though contract terms vary.

Root cause in NJ: Almost always a workflow gap, not an oversight. Claims sit in a "hold" or "review" status in the billing engine and no one is watching the aging queue. By the time someone runs the report, the window has closed.

Fix: File a timely-filing exception with the MCO. You will need to prove the claim was either submitted on time and rejected for a payer-side issue, or that an extraordinary circumstance applied. Approval rates are below 30%.

Prevention: A daily aging report with three buckets — < 60 days, 60–120 days, > 120 days — sent to a named owner. Anything that crosses 120 days should trigger an alert, not just appear in a list.

9. CARC 27 — "Expenses incurred after coverage terminated"

What it means: The member's Medicaid eligibility ended before the date of service.

Root cause in NJ: Annual redetermination is the biggest driver. Members who fail to return paperwork or whose income changes lose eligibility, often without immediate notification to providers. The 12-month continuous eligibility unwinding in 2023–2024 also produced a surge of these.

Fix: Verify whether the member regained eligibility (many do, within 90 days). If so, the date of service may now be covered retroactively and the claim can be resubmitted. If not, the visit is unbillable and should be written off — but the underlying eligibility issue should be raised with the member's care manager.

Prevention: Daily 270/271 eligibility checks for every active member, with status flips surfaced to the scheduler the same day.

10. Payer-Proprietary "MA130" / "Invalid CLIA / EVV mismatch"

What it means: The EVV record submitted via Sandata Aggregator or the MCO's EVV feed does not match the billed claim — usually because the start/end times, GPS coordinates, or service code disagree.

Root cause in NJ: NJ's Sandata Aggregator cross-checks every personal care claim against the corresponding EVV record. If the billed units exceed the verified visit duration (rounded per the agency's contract), or if the visit is missing entirely, the claim is denied even after MCO adjudication.

Fix: Pull the EVV log for the date of service, identify the variance (most often a missed manual entry where an aide forgot to clock in/out), correct the EVV record via the agency's exception workflow, and resubmit both the EVV record and the claim. Detailed walkthrough in Reduce EVV Denials in New Jersey.

Prevention: EVV exception management is its own discipline. Treat unmatched EVV records as a daily standup item with a 48-hour SLA for cleanup. Anything older than that compounds.

The KPI That Matters: First-Pass Acceptance Rate

If you measure only one number on your billing dashboard, make it first-pass acceptance rate — the percentage of claims that adjudicate cleanly on the first submission, with no rejection at any of the three layers above.

Industry-acceptable for home care and HCBS in NJ is 94–97%. Below 90% you are losing real money. Above 97% you are probably either small enough that the office knows every claim by name or you have invested in the workflow controls described below.

A simple report worth running weekly:

Layer	Volume this week	First-pass acceptance	Top 3 reasons
Clearinghouse
277CA
835 adjudication

Most billing tools give you the raw 835 data but make you stitch together the clearinghouse and 277CA layers yourself. That stitching is where most operations stop tracking — and where most of the recoverable revenue is hiding.

Workflow Controls That Prevent the Top 10

A handful of upstream controls eliminate the majority of the codes above before a single claim is sent:

1. Real-time authorization checks at scheduling. Catches CARC 197 before the visit is even booked.
2. Daily 270 eligibility loop per active member. Catches CARC 27 and CARC 109 before they happen.
3. Service-code-to-modifier mapping in a single source of truth. Catches CARC 96 across scheduling, EVV, and billing.
4. EVV exception queue with a 48-hour SLA. Catches MA130 and Sandata-aggregator denials.
5. Aging report with named owners and threshold alerts. Catches CARC 29 before timely filing expires.
6. Nightly diff between MCO eligibility and your member master. Catches HHAeXchange member-not-found rejections.
7. Deterministic claim IDs at the billing-engine entry point. Catches CARC 18 duplicates.
8. Attachment-required flag per service-code/payer combination. Catches CARC 252.

Each of these is a small, boring piece of plumbing. None of them is glamorous. Together, they typically take an agency from 88–91% first-pass acceptance to 95–97% inside two billing cycles.

Where Most Agencies Get Stuck

The pattern we see most often: agencies have every one of the controls above scattered across spreadsheets, payer portals, and the heads of two or three veteran billers. When those people are out, the controls evaporate.

The fix is not buying a bigger billing system. It is making the controls explicit, ownable, and visible in a single operational view — so the next person who covers the role can run the same plays. We wrote about that organizational pattern in more depth in Why NJ Providers Are Abandoning Spreadsheets and Ownable CareOps vs Black-Box SaaS.

Resources & References

• NJ Medicaid Provider File (NJMMIS)
• NJ Department of Human Services — MLTSS Provider Resources
• NJ DDD Fee-for-Service Manual
• X12 Claim Adjustment Reason Codes (CARC)
• X12 Remittance Advice Remark Codes (RARC)
• CMS EVV Requirements
• Sandata Aggregator — New Jersey

Closing Thought

Rejections are rarely a billing problem. They are scheduling, eligibility, credentialing, and EVV problems that surface in billing. The agencies that get to 97% first-pass acceptance are the ones that stop chasing denials and start fixing the upstream workflows that generate them.

If you would like a free first-pass acceptance audit on a sample 90-day window of your NJ Medicaid claims — including the top 3 leak sources specific to your agency — reach out to Via Lucra. We will return a written report inside two weeks with the highest-ROI fixes prioritized.