From EHR to ERA: tracing a claim through the revenue cycle

Four distinct systems carry a claim through a chain evaluated by at least two separate entities before money moves. Most practices understand that chain in broad strokes, but fewer have mapped every handoff point and the specific error types at each. An EFT deposit arrives three to four weeks after checkout.

Chart Completion and Coding

The revenue cycle starts when the provider signs the chart. Until then, it is a liability, not a billable service. Unsigned charts sit in queue 24 to 72 hours after the encounter. Each day in that queue is a day the claim has not started its journey. Coding lag is one of the most measurable contributors to extended days in accounts receivable.

Once the note is signed, the coding event occurs. With manual coding, a coder opens the chart, reviews documentation, assigns CPT and ICD-10 codes, and enters them into the billing module. With automated coding, code assignment happens the moment the chart is signed and writes directly to the billing module without human intervention in the initial assignment step. This is the first point where errors enter the claim: a missed code, wrong code, code that does not reflect the documented level of service, or a diagnosis code too vague to support the procedure billed.

Arintra assigns codes and writes them back to the EHR. It does not submit the claim. Code assignment belongs to Arintra; claim submission belongs to the practice and billing workflow. Codes appear in the billing module for review before submission, not as a submission trigger.

Claim Assembly and Clearinghouse Review

After coding, billing staff assembles the claim by verifying the provider NPI, facility NPI or place of service code, patient demographic information from registration, insurance information from the eligibility file, and coded encounter lines. The claim is formatted as an ANSI X12 837P electronic transaction and sent to the clearinghouse.

The clearinghouse performs two functions: format validation and payer-specific edit checking. Format validation confirms that the 837P is structured correctly and required fields are not empty. Edit checking runs against payer-specific rules loaded for each insurance relationship. Common edits catch missing modifiers for bilateral procedures, procedure codes requiring specific diagnosis code pairing, and claim header errors.

A rejected claim has not reached the payer. It failed in transit and must be corrected and resubmitted. That differs from a denial after payer adjudication. The timely filing clock continues running while a claim sits rejected, and commercial payers set that period at 90 to 180 days from the date of service. Practices without rejected-claim monitoring sometimes discover timely filing issues for claims they thought were in flight.

Eligibility and Coordination of Benefits

Before the claim reaches adjudication, the payer verifies that the patient was eligible for coverage on the date of service and applies coordination of benefits rules. Eligibility verification should happen before the encounter, not after. In practices without automated eligibility checking at scheduling or check-in, eligibility errors are found at the payer rather than at registration.

Coordination of benefits errors occur when a patient has more than one insurance and the claim is submitted in the wrong order, or when the primary payer EOB has not reached the secondary payer before the secondary claim is submitted. A significant dual-coverage population can make COB errors a persistent source of delayed payments and manual follow-up work.

Payer Adjudication

Adjudication is the payer's evaluation against the patient's benefit plan, provider contract rates, and payer's medical necessity policies. It is invisible to the practice until the result. The engine checks whether the service is covered under the plan, authorization was required and obtained, procedure and diagnosis codes are consistent with payer policy, and the allowed amount falls under the contracted fee schedule.

Denials at adjudication fall into several categories. Coding-related denials cite mismatched codes, missing modifiers, or procedures that are not covered under the patient's specific benefit plan. Authorization denials cite missing or expired prior authorization numbers. Duplicate denials indicate that a claim for the same service date and code has already been processed. Technical denials cite errors in patient demographics or provider information.

The key distinction between coding-related denials and technical denials is who can resolve them. For a coding denial, the coder and possibly the provider review documentation, then correct the code or write a corrected claim. For a technical denial, billing staff correct the data entry error or obtain missing registration information. Tracking denials by category directs correction work to the right team member instead of routing every issue through a single denial queue.

Benefits and ERA

After adjudication, the payer generates an EOB for the patient and an ERA for the practice. The ERA is transmitted as an ANSI X12 835 transaction. It lists claim lines processed, the allowed amount for each, the patient responsibility portion, and adjustments or denials with reason codes.

Remittance reason codes are standardized: CO-45: charge exceeds contract allowed amount; contractual adjustment should be taken. CO-4: claim inconsistent with coverage provisions for unspecified reason. PR codes: patient responsibility. CO-97: procedure included in allowance for another service, a bundling denial. The ERA contains information to resolve or write off each claim line, but only if billing staff reads at the code level rather than just recording the payment amount.

Manual ERA processing requires staff to work through remittance lines. Auto-posting matches ERA transactions to outstanding claims, applies adjustments, posts payment, and flags exceptions for human review. Exceptions are lines with unexpected denials or unusual adjustments. Letting auto-posting handle straightforward transactions while human review focuses on exceptions is where billing workflow efficiency is won or lost at scale.

Where Errors Compound

A multi-denial cycle can look like this: a claim is coded incorrectly, denied, corrected and resubmitted, denied again for a different reason, corrected again, and appealed 60 days after the original service date. It consumes far more administrative time than the payment it recovers is worth. These cycles are concentrated on claims where the original coding was ambiguous or documentation was thin.

Getting coding right at the first step, at chart completion, is not about avoiding work downstream. It is about ensuring that when a claim does have a problem, it is a genuine clinical or eligibility issue requiring judgment, not a documentation translation error that could have been resolved before the claim was assembled. The revenue cycle has enough unavoidable complexity without preventable rework at the front end.