A health insurance claim can pass through several administrative stages. Technical acceptance, payer review, and a final payment decision are separate events.
The exact path varies by payer, plan, provider, transaction method, and claim. Staff should use the payer's current instructions rather than assume every claim follows one fixed sequence.
How does a health insurance claim begin?
The provider creates a claim from approved registration, clinical, and billing information. The claim represents what the provider is submitting for payer review.
The treating provider owns the clinical record and clinical decisions. Administrative staff should not add facts that the record does not support. They should also avoid changing clinical information simply to pass an edit or seek a different result.
Before submission, a defined review may compare the claim with its source records. The review can check items such as:
- The patient and plan information used for the claim
- The provider and service-location information
- Dates and other required claim data
- Required references to authorization or referral information
- The destination and transaction method required by the payer
These checks reduce preventable data problems. They do not determine coverage, medical necessity, or payment.
What happens during validation and routing?
A submitted claim may pass through technical checks before payer adjudication. It may travel through a clearinghouse, a direct connection, a portal, or another payer-approved route.
A practice system or intermediary may flag missing fields, invalid formats, or routing problems. The payer may perform its own intake checks. A failed intake can produce a rejection or another technical response, depending on the workflow.
Passing those checks means only that the transaction reached a later stage. It is not proof that the patient's plan covers the service. It is not authorization, adjudication, or a promise of payment.
The response should identify the claim and the stage involved. Staff should retain acknowledgments and match them to the correct submission. That record helps distinguish a transmission issue from a later payer decision.
How does payer review or adjudication work?
After intake, the payer applies the rules relevant to the submitted claim. Those rules may come from the member's plan, payer policy, provider agreement, and other applicable requirements.
The payer may compare the submitted information with available eligibility, authorization, coordination, policy, and contract data. It may also request records or other information. A request is not itself approval or denial.
The payer's review can produce different claim-level or service-line results. A result may include payment information, an adjustment, nonpayment, or a request for another action. Staff should not predict the result from an earlier eligibility response or technical acceptance.
| Stage | What it can show | What it does not prove |
|---|---|---|
| Practice review | Required data appears present | The payer will accept the claim |
| Routing or intake | The transaction reached a system stage | The service is covered |
| Status response | Available processing status | A final financial decision |
| Adjudication | The payer applied its rules to the claim | That every later dispute is resolved |
| Remittance | Reported financial and adjustment information | That posting and follow-up are complete |
What do status and remittance information mean?
Status information describes an available processing state, while remittance information reports adjudication details. Neither should be interpreted without the claim, payer, and date.
A status response can help staff locate a claim or learn whether payer action is pending. It may not contain the complete financial explanation. A later notice can add or change information as the payer completes its process.
As a Medicare example only, CMS explains that after Medicare processes a claim, an electronic or paper remittance reports final adjudication and payment information, including claim or line adjustments. See the CMS remittance guidance. This Medicare example should not be generalized to every payer.
Staff should read the complete payer notice. Claim-level and line-level information can differ. A payment on part of a claim does not explain every other line.
What should staff do after a payer response?
Staff should reconcile the response with the submission and route each open item through the applicable process. The correct action depends on the full notice and verified facts.
A controlled review can include these steps:
- Match the response to the correct claim and submission record.
- Confirm whether the response concerns intake, status, or adjudication.
- Compare claim-level and line-level details with the submitted claim.
- Review payer instructions, current policies, and the applicable agreement.
- Ask the treating provider about clinical questions or record changes.
- Assign and document the next permitted administrative action.
Possible routes can include correcting verified data, providing requested information, checking status, or using a payer review process. Staff should not assume resubmission is always appropriate. A duplicate submission can create a separate problem.
For example, a practice receives a response about one claim. Staff first identify it as an intake response, not an adjudication notice. They compare it with the submitted file, confirm a routing value from an approved source, and follow the payer's current correction instructions. The example predicts no coverage, timing, or payment result.
Frequently asked questions
Is claim acceptance the same as approval?
No. Acceptance can refer only to successful intake or transaction validation. Coverage and payment decisions occur under the payer's later review process.
Is a rejection the same as a denial?
Not usually. A rejection commonly concerns intake or transaction processing. A denial commonly follows payer adjudication. The actual notice and payer definitions control the response.
This guide is general administrative information, not legal, medical, coding, privacy, security, or coverage advice, and not a promise that any claim will be accepted, adjudicated by a certain date, covered, or paid. Processes vary by payer, plan, provider, claim, service, system, agreement, state, and date.
