Day 1 as a posting clerk

Outcome

By the end of your first day you have walked at least one ERA from RECEIVED to CLOSED, you have manually matched a low-confidence line, you have resolved one variance, and you have manually uploaded an out-of-band 835.

You are responsible for

• Watching the receivables inbox and posting incoming ERAs.
• Manually matching lines the auto-matcher cannot place.
• Reviewing variances (expected vs. posted) and either resolving them or accepting with a reason note.
• Manually posting payments that arrive outside an 835 (paper EOB, patient check, refund).
• Routing denied lines to the denials worklist (the platform does this automatically; you confirm).

Required scopes

Scope	What it lets you do
billing.receivable.read	View list / detail
billing.receivable.write	Confirm posting, manually match, resolve variance
billing.receivable.override	Force-match a low-confidence pairing
billing.payment.write	Post manual payments outside the 835 flow

Your first day, step by step

1. Sign in and open /receivables. The list defaults to active statuses (RECEIVED, REVIEW_REQUIRED, EXCEPTIONS). Sort by date descending.

2. Pick a RECEIVED row with the highest dollar count. The detail page opens on the Auto-matched tab. Each row shows claim ID, payer claim control number, billed, paid, and adjustments. Spot-check the totals against the 835 footer (in the Trace tab) — they should agree to the cent.

   Click Confirm auto-matched.

3. Work the Review tab. These are lines the engine matched at low confidence. For each:

   • Confirm if the suggestion looks right (member + amount + date range agree).
   • Reject if it doesn't — pushes the line to Unmatched.

4. Work the Unmatched tab with the Manual match dialog. Search by member, payer claim control, or amount; pick a candidate; confirm. The platform records who manually matched what for the audit trail.

5. Resolve one variance on the Exceptions tab. Common patterns:

   Pattern	Move
   Payer applied a different fee schedule	Either accept variance with note, or update contract and request corrected ERA.
   Modifier was downcoded	Tag the denial; auto-correct or appeal.
   Patient liability higher than expected	Confirm member's deductible / coinsurance is current via 2.4.

6. Click Post. The platform applies every confirmed line in one transaction — claims update, remittance_adjustment rows write, COB secondary builds (where applicable), denials emit to the worklist.

7. Try a manual upload. On the list page click Upload ERA, drop a test 835 your team has, and walk it through the same flow. See 4.1 — ERA inbox.

What "good posting" looks like

Walk left-to-right. Don't skip a tab — the platform won't let you post with unconfirmed Review or Unmatched rows, but it will let you post with unresolved exceptions; that's a habit you don't want to build.

Common Day-1 mistakes (avoid them)

Mistake	Better way
Confirming auto-matched without checking footer totals	Trace tab → footer → must equal sum of paid + adjustments.
Force-matching a line just to clear it	Use the override only when you have proof; it leaves your name on the audit row.
Closing an exception without a reason note	Variance reason is the only signal your supervisor has the next day.
Skipping Post because you're "almost done"	Half-posted receivables block the AR-aging report.

Your daily rhythm

• Morning: alert bell → newest RECEIVED rows → triage by dollar.
• Through the day: as alerts fire, walk and post.
• End of day: anything in EXCEPTIONS for > 24 hours? Hand off to the billing supervisor with notes.

Where to next

• 4.2 — Auto-matched tab for the confirmation rules.
• 4.4 — Unmatched & manual match for the matching playbook.
• 4.6 — Adjustments & variances for the variance taxonomy.