Private preview. We are building worklist with a small group of operations teams.Request early access
Glossary · Transactions

What are the 276 and 277 transactions?

The 276 asks a payer where a claim stands, and the 277 answers: pending, finalized and paid, denied, or waiting for more information. It replaces most status calls.

Example · fictional data
ST*276*0001*005010X212~The inquiry: a 276 claim status request.
TRN*1*INQ88231~Your trace number for this inquiry.
REF*EJ*CLM00419~The claim, by your patient account number.
DTP*472*RD8*20260310-20260310~Its date of service.
ST*277*0001*005010X212~The payer's 277 response.
STC*P1:20*20260402**188.00~April 2: pending and in process (P1), accepted for processing (20).
STC*F1:65*20260410**188.00*142.10~April 10: finalized and paid (F1), claim paid (65), $142.10.
A status inquiry for one claim and the payer's two answers over time: first in process, then paid.

Most claims are paid without anyone asking about them. The rest need follow-up, and the 276/277 pair lets a billing team ask a payer about a claim electronically instead of waiting on hold.

What the answer tells you

The 277 response uses category codes that map onto the next move:

  • P codes, pending: the claim is in process. Check again later.
  • F codes, finalized: F1 paid, F2 denied, and other final states. A denial without a remittance should be worked like any other denial.
  • R codes, requests: the payer needs something, such as medical records or information from the patient.
  • A4, not found: the payer has no record of the claim. Resend it with proof of timely filing.

When to ask

Asking too early wastes a transaction; asking too late wastes the filing window. A good rule is to check once a claim has gone past the payer’s usual time to pay, then on the date the payer’s own answer suggests. Not every payer supports the 276, and some answer only through their portal or by phone, so a status follow-up process needs a fallback for each.

277 or 277CA?

Same transaction family, different job. The 277CA acknowledges a claim once, right after it is submitted. The 277 answers a status question at any point afterwards.

Early access

Run your revenue cycle as workflows.

We are working with a small group of billing and operations teams to shape worklist. Tell us where your work gets stuck, and we'll show you how it would run.

One platform, every role

Operators

A worklist of exceptions, each ready to answer, fast and in bulk.

Team managers

Who works what, what is overdue, what nobody owns, and how good the work is.

Automation builders

Build, test, version and monitor workflows, rules and connections.

Owners and CFOs

The money and work that is stuck, why, what automation recovered and what it costs.

Practices and patients

Answer the one thing only you can answer, from an email link, without an account.

Billing companies

The same screens across every organization you serve.

Request a call back

Leave a number, we'll call you.

Tell us where your revenue cycle gets stuck. You get straight answers from the team, not a sales pitch.

Or reach us directly[email protected]