Reprocess Requests

Guidelines on when to request claim reprocessing, common triggers, what information to include, and when a corrected claim or appeal is needed instead

Reprocess vs. Corrected Claim vs. Appeal

  • Reprocess: We adjudicate the same claim again because something on our side has changed (e.g., precert received, care event added, eligibility updated, COB form completed). The original billed data stays the same

  • Corrected claim: The provider needs to correct something in the original billing (e.g., wrong procedure code, NPI/TIN, service dates, or modifiers). The provider must submit a corrected claim (frequency code 7) through the 837 channel. Reprocessing cannot change what the provider billed

  • Appeal: The claim was processed correctly based on the available information and plan configuration, but the member or provider disputes the decision. This goes through the appeals process rather than reprocessing

Quick rule of Thumb:

  • Something changed in our records → Reprocess

  • Something is wrong in the provider's billing → Corrected claim

  • The decision itself is being disputed → Appeal

Reasons for Reprocessing and What to Attach

All reprocessing requests should include the claim ID and supporting information

Reason

What to Include

Precert now on file

Authorization number, issuing vendor, authorized dates/codes, and where it was sent. Confirm it covers the billed service (dates, codes, units, laterality). Emergency and urgent care categories are exempt, so verify the denial was actually precert related

Care event added

Provider NPI/TIN, care event action or rate, and applicable service dates. Care events can change tier, apply contracted pricing, or deny a claim

Preferred provider / direct contract

Contract or roster entry confirming the provider's status for the dates of service, not just their current network status

Related claim now on file

Related claim ID. Relevant when a claim was denied or held because another claim was missing or unresolved, including duplicate-check or accumulator scenarios

Eligibility updated

Updated coverage dates or termination reversal. Confirm eligibility has already been corrected before reprocessing

COB form completed

Completed COB form or updated other-insurance information, including the primary payer. These may also be identified through the internal COB reprocessing report

Accident form completed

Completed accident investigation form. Claims previously denied for injury-related reasons may be flagged by the accident reprocessing report once the form is submitted

When Not to Reprocess

  • No precert on file: If the required authorization still doesn't exist, reprocessing will produce the same result. The authorization needs to be obtained or the existing decision stands

  • Already paid through cash card or voucher: These payments have completed remittances tied to the original transaction. They require manual handling rather than standard reprocessing

  • Incorrect billed information: Wrong codes, NPI/TIN, dates, or modifiers must be corrected by the provider through a corrected claim (frequency code 7). Reprocessing the original claim won't fix the billing data

Reprocessing only changes how we adjudicate a claim based on updated information. It does not change what the provider billed or create missing authorizations, contracts, or forms. Before requesting reprocessing, confirm what changed, whether that change is already reflected in our system, and which claim needs to be re-adjudicated.

Was this page helpful?