Key takeaways
- ✓Claims adjudication is the payer's review of an accepted claim to decide coverage, payment, adjustments, or denial.
- ✓A status such as processing or accepted is progress, not a promise that the claim will be paid.
- ✓A rejected claim needs a data or submission fix, while a denied claim has reached a payer decision.
- ✓Billing software can match technical responses to the claim and present a simpler timeline, so staff usually do not need to read raw EDI files.
- ✓Use the final remittance to post payment and adjustments, then investigate only when the result does not match the claim or payer rules.
A pharmacy can submit a professional medical claim successfully and still have no payment decision. That gap is where claims adjudication happens.
The sequence feels unfamiliar because it is different from a real-time prescription transaction. An NCPDP claim can return a pharmacy-benefit response at the counter. An 837P medical claim moves through acknowledgments, payer processing, status checks, and a later remittance. The medical benefit vs pharmacy benefit guide explains why those are separate billing lanes.
Accepted does not mean paid
An acknowledgment can prove that a file was readable or that a claim entered the payer's adjudication system. It does not prove coverage, medical necessity, network status, the allowed amount, or payment.
What claims adjudication means
Claims adjudication is the payer's process for applying the member's coverage, the provider's status, coding and billing rules, contract terms, cost sharing, and payment logic to an accepted claim. The result can be payment, partial payment, an adjustment, a request for more information, or a denial.
The word accepted matters. A claim that fails before it enters adjudication has not received a coverage or payment decision. Fixing that event is usually a correction-and-resubmission task guided by the acknowledgment, not an appeal of a denied service.
If you are working a prescription claim with a BIN, PCN, or point-of-sale reject code, use the pharmacy claim adjudication guide. The workflow below is for professional medical claims.
Two checks happen before adjudication
A pharmacy billing team does not need to memorize EDI transaction numbers. Many billing platforms translate the underlying reports into plain statuses such as processing, accepted, rejected, pending, paid, or denied and connect them to the claim automatically. The important skill is knowing what each status proves and what action, if any, comes next.
First check: Did the submitted file go through? (999)
The 999 is an implementation acknowledgment. It tells the submitter whether the electronic file passed the first technical checks. A rejected 999 can reject one transaction set or, in payer-specific workflows such as Medicare, the whole batch. Identify the affected scope and file error before looking for an individual claim in a payer portal.
Second check: Did this claim enter payer processing? (277CA)
After the file passes, a 277CA can report that a claim was forwarded, received, accepted into adjudication, or rejected by the entity issuing that acknowledgment. Treat only payer acceptance into adjudication, not clearinghouse forwarding or receipt, as confirmation that payer adjudication began. A rejected claim may have invalid or missing data even when the 999 accepted the file. Preserve the issuer and returned status details so the team can act on the right claim without losing its submission history.
CMS's March 2026 Medicare guidance says these two front-end editing levels can take up to three days for Medicare claims and warns against resubmitting while those edits are still running because that can create a duplicate. That timing is a Medicare example, not a universal deadline for every payer.
Track one claim through four checkpoints
1. Submit the 837P and save your claim identifier
Save the pharmacy's provider-assigned claim identifier, submission timestamp, payer, plan, location, clearinghouse route, and transmission result. X12 explains that the provider's claim identifier is the primary link between the 837 claim and its 277CA response, so it should be unique and durable.
2. Match the 999 and 277CA to the submission
Let the billing platform match these technical responses to the claim when it can. Staff should see the file result and claim result as separate timeline events, even if the interface uses simpler words. If the file failed, repair the transmission. If one claim failed, repair only that claim using the displayed reason or open the detailed report when the plain-language status is not enough.
3. Monitor the accepted claim inside adjudication
Once the payer accepts the claim into adjudication, preserve the payer claim control number when one is reported and the date of that acceptance. Use the payer's portal or a 276 request and 277 response to find the claim's current status. A pending status may call for patience, a specific document, or payer clarification. It does not justify a blind duplicate submission.
When a payer assigns and reports a payer claim control number on the 277CA, X12 expects it to match the 835. Reporting that number on the 277CA is situational, and split processing can create related new numbers, so preserve every reported control number rather than overwriting the first one.
4. Reconcile the final 835 remittance
The 835 reports final adjudication and payment information. Match it to the claim identifiers, then record the billed amount, allowed amount when reported, paid amount, patient responsibility, and every adjustment. Read the group code, Claim Adjustment Reason Code, and Remittance Advice Remark Code together before deciding whether to post, correct, appeal, or ask the payer for clarification.
Use the claim remit-code guide when the financial result needs deeper interpretation.
Keep claim follow-up in one place
Use the claim record, timeline, and notes already available in your billing platform so the next person can see what happened without reconstructing the submission across several portals. The platform may capture technical identifiers and match reports automatically. Staff only need a short, practical follow-up checklist inside the approved claim workflow.
- Can you identify the claim, payer, plan, pharmacy location, and service date?
- What plain-language status does the platform show, and when was it last updated?
- Does the status explain the problem and next action, or do you need the detailed acknowledgment or payer report?
- Is the claim waiting, rejected, pending, paid, or denied, and what evidence supports that label?
- Who owns the next action, what did they record in the claim note, and when should the claim be checked again?
- If the claim is final, do the billed, allowed, paid, adjusted, and patient-responsibility amounts reconcile?
Let software carry the technical detail
Billing platforms can connect acknowledgments, payer status reports, remittances, and changing claim identifiers behind the scenes. Keep those technical details available for support or reconciliation, but let the user-facing claim timeline, status, and notes drive ordinary follow-up.
When to act and when to wait
File rejected (999): fix the transmission
The batch did not pass the first technical check. Use the acknowledgment details to repair the file or transmission before resubmitting. Do not wait for an individual remittance that cannot arrive.
File accepted, claim response missing: verify the handoff
A readable file does not prove that this claim reached payer adjudication. Check the clearinghouse path and the payer's expected acknowledgment window. If the 277CA remains missing, contact the appropriate EDI support channel with the batch and provider claim identifiers.
Claim rejected (277CA): correct the claim
The claim did not enter adjudication. Correct the specific data problem, follow the payer's resubmission instructions, and connect the new transmission to the original claim history.
Payer accepted or later status pending: monitor it
Treat the claim as inside adjudication only after a payer-accepted A2 or equivalent payer acknowledgment, or a later 277 status showing it is pending. A0 forwarding and A1 receipt statuses mean the team should keep waiting for the downstream acknowledgment. Use the payer's written timing rules to decide when to check again, respond only to a specific request, and avoid duplicate submission while the claim is still active.
Remittance received (835): reconcile the decision
Post a matching result. Investigate a mismatch using the complete remittance, contract, claim, and service-date policy. A denial, underpayment, or unusual patient balance may call for correction, appeal, or payer clarification, but the codes and policy must determine that path.
Good billing software should make this easier by matching payer reports to the claim, translating technical events into useful statuses, and keeping the status history and staff notes together. DocStation supports 837P claim submission and resubmission, claim-level notes, and timeline history, so a pharmacy team can follow the work without treating raw EDI reports as the everyday interface. Then connect the work to the pharmacy revenue cycle management workflow.
Claims adjudication FAQ
What does claims adjudication mean?
Claims adjudication is the payer's process for applying coverage, provider, coding, contract, cost-sharing, and payment rules to an accepted claim. The final result is reported through the payer's status and remittance channels.
Does an accepted medical claim mean it will be paid?
No. A platform may show processing after the file passes its first technical check, then accepted after a payer acknowledgment says the claim entered adjudication. The underlying reports are commonly called a 999 and 277CA. Forwarded, received, or accepted statuses still do not prove coverage, the allowed amount, or payment.
What is the difference between a rejected claim and a denied claim?
A rejected claim did not pass a front-end check and generally needs a correction and resubmission. A denied claim reached adjudication and received a payer decision. Start with the plain-language status and reason in the billing platform, then open the detailed acknowledgment or remittance only when needed.
What is the difference between a 277CA and a 277 claim-status response?
A 277CA can show that an intermediary forwarded or received a claim, that the payer accepted it into adjudication, or that an issuer rejected it. A later 277 reports where a payer-accepted claim is in the payer's process. Billing software may translate both into a simpler claim timeline, but it should preserve the issuer and status distinction.
How long should a pharmacy wait before checking a medical claim?
Use the payer's written acknowledgment and processing rules, not one universal timeline. CMS says Medicare's first two front-end editing levels can take up to three days, but other payers may use different windows.
Why can a payer claim number change?
X12 notes that a payer may assign a different control number when it splits a claim during processing. Keep the original provider claim identifier, the first payer control number, and every later split-claim identifier together.
