Skip to main content
The Practice
Billing operationsNovember 16, 2026

Therapy Claim Status Tracking: Find the Stalled Claim Before It Ages Out

How a therapy practice finds out where a submitted claim sits before the remittance arrives: the 999, 277CA, and 276/277 checkpoints, a weekly status routine, and what automation can and cannot do.

Callie Editorial 15 min read
The revenue-cycle issue
Where is it?

Action required

Denial recovery queue

01 · Classify

Eligibility, coding, documentation

02 · Correct

Fix the root record

03 · Respond

Resubmit or appeal on time

Reason → owner → deadline → evidence → outcome

At a glance

What you’ll leave with

  • A claim passes three checkpoints before the remittance: the file acknowledgment (999), the claim acknowledgment (277CA), and the payer status (276/277). Each one answers a different question.
  • A rejected claim never entered the payer system, so it has no status to check. Find rejections on the acknowledgment reports, fix them, and resubmit.
  • Automation can ask for status and sort the answers. A person still has to act on a pending claim that waits for records, and on a claim the payer cannot find.

Therapy claim status tracking is the work between two moments: the claim leaves your billing system, and the remittance comes back. Most practices treat that gap as waiting time. It is the time when a claim can fail without a sound. A file the clearinghouse never forwarded, a claim the payer rejected at the front door, a claim that sits pending because the payer asked for records nobody saw: none of these shows up as a denial. Each one shows up weeks later as an old balance on the aging report.

This article covers that gap. The EOB and payment-posting guide starts where this one ends, when the payer has decided. The claim-denial workflow covers what to do with a decision you disagree with. Here, the question is simpler and earlier: where is the claim right now, and does it need a person?

The definition

What is therapy claim status tracking?

Therapy claim status tracking is the routine check of where each submitted claim sits between submission and payment: rejected at the front door, accepted and in process, pending for more information, or finalized. The goal is to find a stalled claim while you can still fix it inside the payer’s filing limit. A practice tracks status with clearinghouse reports, payer portals, phone systems, and the HIPAA 276/277 claim status transaction.

The reason to track status, and not wait for the remittance, is that a claim can only fail loudly after the payer decides. Before that, the failure modes are quiet. A missing payer ID, a subscriber ID that does not match, or a batch that never left the clearinghouse produces no denial and no EOB. The claim never becomes a claim in the payer’s system, and the filing clock keeps running. For Medicare, federal rules set that clock at one calendar year from the date of service; commercial and Medicaid limits are set by each contract or state program and are often shorter.

The path

Where does a claim go after you click submit?

A submitted claim passes through checkpoints in order. The clearinghouse or payer first checks that the file is readable and returns a 999 acknowledgment. Next, it checks each claim against the HIPAA format and returns a 277CA claim acknowledgment that accepts or rejects it. Only an accepted claim enters adjudication and gets a payer control number. From there, the payer’s 277 status response reports it as pending or finalized, and the 835 remittance closes it.

CMS describes the Medicare version of this path in plain terms. The Medicare Administrative Contractor (MAC) runs front-end edits and issues a 999; an error at that stage rejects the whole batch. Claims that pass then go through implementation-guide edits, and a claim with an error there is rejected by itself on the 277CA. CMS says these two editing steps can take up to three days, and it warns providers not to resubmit during that time, because a resubmission creates a duplicate claim. A claim that clears both steps gets an Internal Control Number (ICN) for Part B.

The checkpoints between submission and remittance

CheckpointThe question it answersWhere you see itWhat to do when it fails
999 acknowledgmentWas the file readable?Clearinghouse report or EDI mailboxFix the file-level error and resend the batch. No claim in a rejected batch reached the payer.
277CA claim acknowledgmentDid each claim pass the format edits and enter the payer system?Clearinghouse rejection reportCorrect the field the report names and resubmit that claim as new. A rejection is not a denial and has no appeal.
276/277 status, portal, or phoneWhere is the accepted claim in adjudication?Clearinghouse status screen, payer portal, IVRAct on the category code: wait, send records, or call the payer.
835 remittance (ERA)What did the payer decide and pay?ERA or paper EOBPost it, or route a variance or denial to its own workflow.

The clearinghouse guide explains how to judge rejection reports and why a rejection differs from a denial. For status tracking, the one rule to keep is this: a claim without a payer control number has no status to check. If the 277CA rejected it, the payer portal will not find it, and the next step is a correction, not a phone call.

The options

How do you check the status of a therapy insurance claim?

To check the status of a therapy claim, first confirm the 277CA accepted it and note the payer’s claim number. Then use one of four paths: the payer’s secure portal, the payer’s phone or IVR system, your clearinghouse status screen, or an electronic 276 request that returns a 277 response. The portal is fastest for one claim. The 276/277 is best for a batch, because software can send and read it.

CMS lists the same four paths for Medicare: the MAC’s interactive voice response (IVR) phone system, the MAC’s internet portal, direct data entry for some providers, and the 276/277 transaction. CMS recommends the electronic route because software can generate 276 requests on its own and post 277 responses to patient accounts without manual entry. Its MLN booklet also notes that a 277 response can take up to 24 hours, and that you should ask your software vendor or billing service whether it offers the transaction and whether it charges for it.

Commercial and Medicaid payers each run their own portal and phone line, and access often needs a separate login per payer. The front desk usually captures where to check status during intake; the eligibility verification workflow includes that field in its payer checklist, so the information is ready when a claim needs it.

The standard

What is the 276/277 claim status transaction?

The 276/277 is the HIPAA standard for claim status. The 276 is the provider’s electronic question about a claim, and the 277 is the health plan’s answer. HHS adopted the X12 version 5010 of this transaction for all HIPAA-covered entities, and since January 1, 2013, federal operating rules require health plans to give providers real-time online access to claim status. The answer arrives as standardized codes, so software can read it across payers.

The codes are what make the transaction useful. Each 277 response carries a claim status category code, maintained by X12, that groups the answer into families. The A codes are acknowledgments: A1 means the payer received the claim, which X12 notes does not mean accepted; A2 means the payer accepted it into adjudication; A3 and the A6 to A8 codes mean the payer rejected it. The P codes mean pending: P1 is in process, P2 is pending payer review, and P3 means the payer is waiting for information it already requested from the provider. The F codes mean finalized: F1 paid, F2 denied, F4 adjudicated with no payment forthcoming. A more detailed claim status code rides with each category to say why.

The centerpiece

What weekly routine keeps claims from stalling?

A weekly claim status routine works in a fixed order. Clear every acknowledgment rejection first, because those claims are not filed yet. Then compare accepted claims against the time each payer normally takes to pay, and request status only for the claims past that point. Sort the answers by category code, act on each pending reason, and log what you did, so the next pass starts with a clean queue.

  1. 01

    Work the acknowledgment reports before anything else

    Open the 999 and 277CA reports from every batch since the last pass. Each rejected claim gets corrected and resubmitted as a new claim. Until it is accepted, it has no payer control number, so no status check can find it.

  2. 02

    Record the payer control number for each accepted claim

    Copy the payer claim number (for Medicare Part B, the ICN) into the claim record. Every later portal search, phone call, and appeal starts from this number, and a call without it costs time.

  3. 03

    Check status only after the payer’s normal processing time

    Know how long each payer takes to pay a clean claim. For Medicare, CMS tells providers to wait at least 14 days for an electronic claim and 29 days for paper before they check payment status. For other payers, read the provider manual or your own payment history.

  4. 04

    Request status in one batch, not one call at a time

    Send 276 requests for every claim past its expected date, or run the clearinghouse status refresh. Use the portal or phone only for the claims the batch cannot answer.

  5. 05

    Sort the answers by category code

    Finalized claims (F codes) wait for the remittance and go to posting. In-process claims (P1) wait one more cycle. Claims pending for provider information (P3) or with a request code (R) go to a person today. A claim not found (A4) goes back to step one.

  6. 06

    Act on every pending reason with a deadline

    Send the requested records or answer the request through the channel the payer names, and note the date sent. Compare each open claim against its timely filing limit, and work the claims nearest that limit first.

  7. 07

    Log the cause, then fix the step upstream

    Write down why each stalled claim stalled. A pattern, such as one payer that always asks for the plan of care, belongs in the front-end process, not in next week’s status queue.

Worked example, fictional

One week of claim status at a two-therapist PT clinic

The clinic, payers, and claims below are invented for illustration. The clinic submitted claims for a week of visits to Medicare Part B and two commercial payers. It runs the routine above every Tuesday.

The acknowledgment pass

The 999 reports show every batch was readable. The 277CA report shows one rejection: a commercial claim with a subscriber ID that does not match the payer’s records. The biller corrects the ID from the insurance card on file and resubmits it as a new claim. It is the only claim with no payer number, so no status check would have found it.

The status batch

The clearinghouse sends 276 requests for every accepted claim past each payer’s normal payment time. Most return F1 (paid) and go to the posting queue. Two Medicare claims return P1 (in process) and are still inside the payment floor, so they wait. One commercial claim returns P3 with a status code that asks for medical records.

The claim that needed a person

Nobody at the clinic saw the records request. It went to an old fax number on the payer’s file. The biller sends the plan of care and the visit notes through the payer’s attachment process, records the date, and updates the fax number on the payer account. Without the status check, this claim would have stayed pending until the payer closed it for lack of a reply.

The upstream fix

The log shows this payer asked for the plan of care on two claims this quarter. The clinic now confirms the payer’s records-request address at intake and checks whether the payer wants the plan of care with the first claim. The status queue the next Tuesday is shorter.

The tools

What does claim status automation actually do?

Claim status automation sends 276 requests or clearinghouse status checks on a schedule, reads the 277 codes that come back, and updates each claim in your billing system without manual lookups. Good tools also pull in 999 and 277CA acknowledgments and flag claims that have no response. Automation does not decide what a pending claim needs, send medical records, or argue with a payer. A person still owns those steps.

This is the work CMS had in mind when it recommended the electronic route: software that generates status requests on its own and posts the responses to patient accounts. The value is in the sorting. When every accepted claim carries a current category code, the person who works the queue sees only the claims that need judgment: the P3 that waits for records, the A4 the payer cannot find, the claim that has sat at P1 well past the payer’s normal time.

Some tools sell this as a separate claims status or claims communication product, and some build it into the EHR or clearinghouse. In Callie, claims are filed from the billing claim queue, and statuses sync from the clearinghouse in the background. Each claim moves through Submitted, Sent to payer, and Processed, and keeps an event timeline from draft to adjudication. Whatever tool you use, the human steps in the routine above stay the same.

The evaluation

What should you ask a vendor about claim status tracking?

Ask a vendor to show, on a live account, how a claim moves from submission to remittance: where 999 and 277CA rejections appear, how often status refreshes, which payers return 277 responses through its connection, and what the screen shows when a payer does not respond. Ask what each part costs, including per-claim or per-inquiry fees. Do not accept a demo with only paid claims.

Field checklist

09 items

Questions to ask before you buy a claim status tool

  • Where do 999 and 277CA rejections appear, and does the rejected claim show the exact field to fix?
  • Does the tool send 276 requests itself, or does it only display statuses the clearinghouse pushes?
  • How often does status refresh, and can we trigger a refresh for one claim?
  • Which of our payers return 277 responses through your connection, and what happens for a payer that does not?
  • Does each claim show the payer’s category and status codes, or only a summary label? Can we see both?
  • How does the tool flag a claim with no response, or one pending past a date we set per payer?
  • Does the payer claim number (for Medicare Part B, the ICN) appear on the claim record?
  • Is claim status included in the price, or billed per claim, per inquiry, or as an add-on? Ask for it in writing.
  • Who on your team helps when a payer’s status responses stop arriving?

The answers tell you how much of the routine the tool does for you and how much stays on your staff. They also connect to the bigger picture: status tracking is the earliest place to stop a claim from becoming an old balance. The accounts receivable guide covers what to do with balances that already aged.

“A denial tells you what went wrong. A stalled claim tells you nothing until you ask.”

Quick answers

Therapy claim status tracking: FAQ

How do I check the status of a therapy insurance claim?

First, confirm on the 277CA report that the payer accepted the claim, and note its claim number. Then check the payer’s secure portal, call its IVR line, look at your clearinghouse status screen, or send an electronic 276 request. The portal is fastest for one claim; the 276/277 is better for a batch.

What does a claims status communication platform actually do?

It asks payers for claim status on your behalf, usually with the HIPAA 276/277 transaction, and shows the answers in one place. It can flag rejected, pending, and missing claims. It cannot send records, correct a claim, or decide on an appeal. A person still acts on what it finds.

What is the difference between a 277CA and a 277?

The 277CA is a claim acknowledgment: it says whether each claim passed the format edits and entered the payer’s system. The 277 is the response to a 276 status request: it says where an accepted claim sits in adjudication. A claim rejected on the 277CA has no status to request.

How long should I wait before I check a claim’s status?

It depends on the payer. For Medicare, CMS tells providers to wait at least 14 days for an electronic claim and 29 days for a paper claim before checking payment status. For other payers, use the provider manual or your own payment history to set a date per payer.

Should I resubmit a claim that has no status yet?

Not until you know the payer never received it. CMS warns that resubmitting a Medicare claim during front-end editing creates a duplicate. Check the 999 and 277CA reports first. Resubmit as a new claim only after a rejection or an A4 “not found” response that you confirmed.

Does claim status tracking cost extra?

It depends on the vendor. Some include it in the EHR or clearinghouse price, and others charge per claim, per inquiry, or as an add-on. CMS advises providers to ask their software vendor or billing service whether it offers the 276/277 and whether it charges for it. Get the answer in writing.

Primary sources

Bibliography / 7
  1. 01Checking Medicare Claim Status (MLN3171902)Centers for Medicare & Medicaid Services
  2. 02Claim Status Request and ResponseCenters for Medicare & Medicaid Services
  3. 03Operating Rules for Eligibility and Claims StatusCenters for Medicare & Medicaid Services
  4. 0445 CFR Part 162, Subpart N: Health Care Claim StatusElectronic Code of Federal Regulations
  5. 0542 CFR 424.44: Time limits for filing claimsElectronic Code of Federal Regulations
  6. 06Claim Status Category CodesX12
  7. 07Claim Status CodesX12

Written by Callie Editorial

Published November 16, 2026

Educational content, not legal, billing, or patient-specific clinical advice.