Why corrected claims are denied as duplicates
Payer reference numbers and clearinghouse record-matching rules both matter when a claim is corrected. A failure in either can leave the replacement unlinked to the original.
A replacement claim can carry frequency code 7 and still return as a duplicate. The payer's original claim number and the clearinghouse's record-matching rules serve different purposes. An error in either can leave the correction unlinked.
CARC 18 reports a duplicate claim or service. The code alone does not explain why the receiving system treated it that way. X12's current definition specifies OA as the usual group code, with a state workers' compensation exception.
First establish what happened to the original
A front-end rejection, an accepted but pending claim, and an adjudicated denial need different handling. Read the acknowledgment or remittance and the payer's instructions. Repeatedly resending an original while it is pending can create the duplicate you are trying to avoid.
| Evidence | What to do |
|---|---|
| Rejected before payer acceptance | Correct the error and follow the payer's original-resubmission instructions |
| Accepted and still pending | Check status before sending another claim |
| Adjudicated with an error in submitted data | Use the payer's correction or reopening process |
| Submitted data is correct; decision is disputed | Use the payer's reconsideration or appeal process |
Check the clearinghouse's record match
Claim.MD normally identifies updates using a combination of claim fields. It also offers matching on a stable remote claim identifier, sent as remote_claimid or REF*D9, when the account is configured for that behavior. Claim.MD's update rules describe both options.
Confirm the setting before relying on D9. Preserve the identifier used on the original submission. If historical transmission evidence is missing, reconcile the stored record before attempting an automated update. Other clearinghouses may use different rules.
Check the payer's replacement match
For UnitedHealthcare electronic replacements, frequency code 7 must travel with the original claim number, and the correction must include all originally billed services rather than only the changed line. UHC's correction guidance is a payer-specific example.
| Identifier | Purpose | Check |
|---|---|---|
| Clearinghouse record identifier | Update the record held by the intermediary | Use its configured matching rules; D9 is one supported method |
| Payer claim control number | Identify the adjudicated claim being replaced | Use the payer-assigned number, commonly carried in REF*F8 for an 837P replacement |
| Patient account number | Identify the account in the provider's system | Do not substitute it for a payer-assigned control number |
Start with the remittance for the claim being replaced; its payer control number is carried in 835 CLP07. A payer status response may also supply that number. Do not substitute an arbitrary acknowledgment trace. If sources conflict, reconcile the discrepancy before sending the correction.
Original Medicare has its own correction process
For clerical errors on Original Medicare Part B professional claims, check the MAC's reopening process. CMS separates reopenings from appeals. A commercial replacement workflow should not be applied indiscriminately to Medicare claims. CMS correction and redetermination guidance.
Medicare Advantage plans publish their own submission instructions. Institutional adjustment billing also differs from professional billing. Confirm the claim type and recipient before selecting the correction protocol.
How Foresight helps
Foresight's corrected-claim workflow uses receipt evidence and payer classification to choose the submission protocol. It resolves the payer control number from retained evidence and sends missing or conflicting identifiers to review. The clearinghouse identifier remains a separate requirement.
- 01Resolve the originalCheck receipt status, payer category, claim state, and control numbers.
- 02Prepare the correctionBuild the permitted submission with its original-claim linkage.
- 03Approve the previewA person reviews the specific claim prepared for transmission.
- 04Submit the approved versionThe workflow checks that the transmitted content matches the approved preview.
That gives the biller a concrete review: what changed, which original claim it replaces, and what will be sent. It also prevents a second submission route from bypassing an open correction case.
Keep the claim acknowledgment chain with the correction and verify the payer's correction deadline.
01Does every corrected claim need REF*D9?
No. D9-based record matching is a supported intermediary pattern, including a configurable Claim.MD option. Follow the actual clearinghouse and payer instructions.
02Should we add a modifier to clear the duplicate?
Only when the service and coding rules support it. A modifier cannot repair a missing original-claim link, and a duplicate message does not establish that a repeat service occurred.