Start with the actual event: an ERA that imported only some of its reported transactions. Assign a stable locator, record when the item entered the workflow, and name the remittance and cash-posting owner. The record should make sense to an authorized colleague who did not watch the event happen.
Gather the evidence before proposing an action: the original 835, import control report, remittance totals, accepted lines, rejected lines, and deposit trace. Preserve original wording, identifiers, and timestamps in approved systems. Retrieval time, event time, system-entry time, and review time answer different questions and should not be collapsed.
The easy mistake is assuming that a successful file status can coexist with missing service lines or an incomplete account posting. Mark each field as observed, externally reported, calculated, owner-interpreted, or unknown. If sources disagree, retain both values and route the conflict instead of silently choosing the tidier one.
For routine 2, define the unit before counting: claim version, service line, remittance line, deposit, account event, document, or queue item. Freeze the opening population and list late arrivals separately. Otherwise the denominator moves while the team is trying to explain it.
Support staff may retrieve permitted records, compare fields, reproduce documented arithmetic, index files, and draft a bounded factual question. The remittance and cash-posting owner retains decisions that change coding, clinical meaning, claim content, money, access, submission, legal interpretation, or external communication.
Use statuses that reveal the work: evidence gathered, conflict found, access blocked, awaiting owner, authorized action, or carried forward. A generic completed label is not enough unless the record says what changed, who approved it, and where the result can be verified.
Before close, have a second authorized reviewer repeat one ordinary item and one exception when available. Compare source selection, identifiers, timing, scope, and arithmetic. A disagreement often exposes an unstated assumption in the routine.
The close test is precise: file, batch, line, and deposit counts reconcile without netting away exceptions. Reconcile every opening item to a current state, give unresolved work one next actor and review date, and keep missing or inaccessible evidence visible in the count.
Keep protected information in approved tools and use only the minimum necessary locator in shared trackers. An access problem belongs with the access owner; it is never permission to borrow credentials or move sensitive records into an unapproved channel.
This September 9, 2026 guide is an administrative control, not a clinical, coding, coverage, contract, legal, or accounting determination. Its value is practical: it preserves what happened and delivers a well-bounded question to the person authorized to decide.