Day 1 as an AR analyst

Outcome

By the end of your first day you can read the AR aging buckets, you have followed up on at least one >60-day claim using a 276 status inquiry, you have triaged the timely-filing watch, and you have a spreadsheet of "claims worth chasing this week" tagged for the team.

You are responsible for

• Watching AR aging and days-in-AR (DAR).
• Triaging timely-filing alerts before they expire.
• Sending 276 claim status inquiries on aged claims and acting on the 277 response.
• Setting follow-up cadence on outstanding receivables.
• Escalating to the supervisor when a payer-specific pattern emerges (delays, mass denials, mass underpayment).

Required scopes

Scope	What it lets you do
billing.claim.read	View claims and balances
billing.denial.read	See denial context on aged claims
billing.claim-status.write	Send 276 inquiries
reports.read.financial	AR & DAR widgets
reports.read.operational	Timely-filing report

Your first day, step by step

1. Read the AR aging chart at /ar/aging. The default view buckets by 0-30, 31-60, 61-90, 91-120, 121+. Sort by aged-amount descending. The chart drill-throughs are linked to the underlying claims list — click any bar to land on the filtered list.

2. Pick the largest claim in the 61-90 bucket. Open it. Read the Submission tab — when did the 277CA arrive? Is the claim ACCEPTED or SUBMITTED? If only SUBMITTED, the payer hasn't acknowledged yet — that's worth a 276.

3. Send a 276 inquiry. From the claim detail click Send 276. The platform builds the X12 276, sends it to the same trading partner the 837 went out on, and waits for the 277. The Submission tab tracks both documents. See 6.4 — Claim status inquiry (276/277).

4. Open the timely-filing watch at /ar/timely-filing. Filter by < 14 days. Each row shows the payer's filing window, the claim's date of service, and days remaining. Decide for each:

   Days remaining	Action
   14+	Watch.
   7-14	Set follow-up due date today; chase the payer.
   0-7	Escalate; rebuild as a corrected claim if the original wasn't accepted.
   Negative	Already expired — write off (with reason) or appeal.

5. Build a "to chase this week" list. From /claims filter age >= 45 AND balance > 0 AND status NOT IN (PAID, WRITE_OFF), sort by balance descending, save the view (chip in the toolbar). Tag each row with followup-this-week.

The AR diagram

Common Day-1 mistakes (avoid them)

Mistake	Better way
Sending a 276 on a claim that's never been accepted	Resubmit the 837 first; 276 is for already-accepted claims.
Setting a follow-up date but not a reason	Future-you needs the reason; the field is right there.
Writing off an expired-filing claim without an appeal attempt	Many payers accept timely-filing exception appeals; check before writing off.
Chasing the payer before the 277CA arrived	Wait the partner's SLA; chasing earlier just makes the payer's queue longer.

Your daily rhythm

• Morning:
  1. Aging chart.
  2. Timely-filing watch (filter < 14 days).
  3. 276 responses from yesterday's inquiries.
• Through the day: send 276s, set follow-ups, tag.
• End of day: hand the supervisor a one-line summary of any payer-level pattern.

Where to next

• 6.1 — AR aging — full filter playbook.
• 6.2 — Days-in-AR KPI.
• 6.4 — Claim status inquiry (276/277).
• 6.5 — Follow-up cadence.