Claim frequency code

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

The code tells the receiver what kind of submission this is

In a professional electronic claim, the Claim Frequency Type Code is CLM05-3 in 837P Loop 2300. It distinguishes original, replacement, or void intent where supported. Allowed values and paired fields depend on the adopted X12 guide and receiver instructions.

The X12 public 837 overview describes its claim and encounter uses; detailed rules belong to the licensed guide. The CMS adopted-standards page identifies Version 5010 as the adopted health-claim standard. For HIPAA-covered claims, use that standard and the applicable companion guide. A later X12 publication does not itself replace the adopted version.

The current NUCC 1500 Reference Instruction Manual labels paper-form Item 22 “Resubmission and/or Original Reference Number.” It uses 7 for replacement, 8 for void or cancel, omits Item 22 for an original, and directs users to payer instructions. These are not blanket 837P rules. The March 2026 CMS 837P guide linked for Noridian jurisdictions E and F, for example, requires CLM05-3 to equal 1 for that Medicare FFS route. Verify the payer, product, format, route, and current guide.

Status determines the available route

Before selecting a frequency code, identify the prior submission's actual state:

• Never transmitted: correct the charge or claim before first release.
• Rejected before adjudication: identify the receiver and artifact. A TA1 addresses interchange receipt, a 999 transaction-set syntax and structure, and a 277CA, when used, claim-level acknowledgment. Other reports may add layers. Use the prescribed rejection route.
• Accepted but not adjudicated: verify payer status through a portal or 276/277 when supported. Clearinghouse, TA1, 999, or 277CA acceptance does not establish final adjudication.
• Adjudicated with incorrect submitted data: use the payer's replacement, void, adjustment, reopening, or other permitted correction path.
• Adjudicated with accurate submitted data and a disputed decision: use the applicable appeal, reconsideration, or dispute route.
• Paid duplicate or overpayment concern: stop further billing and follow the payer, refund, recoupment, compliance, and legal workflow that applies.

CMS's professional-claim submission page describes batch, claim-level, and coverage or payment edits. Its Medicare example shows why rejection and adjudication need different handling. Other payers may define states and routes differently.

“Corrected claim” is a workflow description, not a universal replacement route. The valid action depends on the prior state, changed data, payer instructions, and whether the issue belongs in an appeal.

The original reference number creates the link

For an X12 837 replacement or void, the standard path requires the payer claim control number for the previously adjudicated claim in the original-reference field. X12's interpretation notes payer variation while an original remains pending; some payers use portal or adjustment routes. Follow the exact workflow. Never substitute a practice account number, clearinghouse number, batch ID, or authorization number.

The NUCC manual defines Item 22's original reference number as the identifier assigned by the destination payer or receiver. For Medicare electronic workflows, the CMS Fee-for-Service companion-guide page provides jurisdiction-specific instructions that supplement, but do not replace, the X12 guide.

Keep the original claim, payer control number, intended action, source evidence, later transaction, acknowledgments, adjudication, remittance, ledger entries, and disposition in one trace.

Use a release decision before changing the code

A controlled workflow can use eight questions:

1. Which claim version and service lines were sent?
2. Was it rejected, accepted, pending, adjudicated, paid, or denied?
3. What proves that state and payer claim number?
4. Is the problem transmission, claim facts, documentation, coding, payment, or payer decision?
5. Who may correct the source and approve the route?
6. Which payer instruction matches the product, format, status, and change?
7. Does the next action require a full claim, selected lines, original reference, attachments, portal, or appeal?
8. How will acknowledgment, adjudication, remittance, cash, balance, and reversal be verified?

Clinical facts and billing fields need separate owners. A clinician makes any permitted late entry, amendment, or correction under the practice's documentation policy, preserving the original content, author, date and time, and reason. A qualified coding or billing reviewer selects the claim route from verified source evidence. Software may display rules and flag conflicts; it should not turn a denial into a replacement or rewrite clinical content automatically.

Prevent duplicate release by matching the patient, payer, service dates, line set, original control number, frequency intent, transaction ID, and current state. Preserve retries and acknowledgments.

A fictional queue separates four paths

A fictional ABA practice reviews 12 claim exceptions that have reached the queue's defined review date. Four rejected claims lack payer claim control numbers and follow the applicable original-submission route. Three adjudicated claims have supported data errors and qualify for replacement. One adjudicated duplicate qualifies for void. Two accurate claims with disputed denials go to appeal. Two lack reliable status evidence and remain on hold.

All 12 records are assigned once: 4 rejected-original routes + 3 replacements + 1 void + 2 appeals + 2 status holds = 12. Four records are eligible for a frequency-code correction under the fictional payer rules: three replacements and one void. All four include the correct original payer control number, so reference completeness is 4 of 4, or 100%.

That result measures packet completeness, not payer acceptance, adjudication, or payment. The status holds remain visible, and the appeals stay outside the frequency-code denominator.

Reconcile the financial result

A replacement or void may lead to later reversal or correction reporting, offsets, recoupments, refunds, or patient-balance changes under payer rules. X12's interpretation explains the 835 reversal-and-correction process after finalized adjudication. The CMS EFT and ERA page explains that an ERA reports claim-payment adjustments while EFT moves funds. Reconcile remittances, deposits or offsets, the ledger, and permitted patient responsibility.

Useful measures include:

• route-determined rate: mature claim problems with a documented payer route divided by mature problems reviewed; report status holds separately
• original-reference readiness: replacement or void episodes with a verified payer claim control number divided by all such episodes due for release, including episodes held for a missing reference
• duplicate-correction episode rate: correction episodes with at least one competing or repeated transaction divided by correction episodes
• acknowledgment completeness by artifact: matched acknowledgments divided by acknowledgments of the same type due after its defined response window
• correction aging: elapsed time from the defined error or payer-state event to verified final disposition
• recurrence rate: claims with the repeated error divided by claims exposed to the same source rule and workflow version

Define maturity, exclusions, payer states, episode boundaries, and final disposition first. Segment by payer, product, format, problem, and route. Pair speed with accuracy and financial safeguards.

The manifest's CMS Electronic Billing and EDI Transactions page is a Medicare entry point for claim, status, remittance, and companion-guide resources. It does not supply one rule for every ABA payer.