Skip to content
FonteumPublic-records evidence
Fonteum Data GlossaryTech

What is Electronic Remittance Advice (ERA)?

Electronic Remittance Advice (ERA) is the HIPAA-standard X12 835 transaction a health care payer sends a provider to explain how submitted claims were paid, denied, or adjusted, using standardized reason codes. Payers must transmit ERAs to providers who request them electronically, and ERA data drives payment reconciliation in Medicare and commercial accounts-receivable workflows.

Source file
Not reported
Published
Not reported
Retrieved
Not reported
Snapshot
Not retained for this reference page
Data as of
Not reported

Full name: Electronic Remittance Advice

Short explanation

An Electronic Remittance Advice (ERA) is a HIPAA-standard electronic document (ASC X12 835 transaction) that a health care payer sends to a provider explaining payment decisions on submitted claims. ERAs specify which services were paid, denied, or adjusted and include standardized reason codes. Under HIPAA, payers must transmit ERAs to providers who request them electronically. ERA data is the primary mechanism for providers to reconcile Medicare and commercial insurance payments in accounts receivable management systems.

Last updated: 2026-07-11Reviewed by: Dr. Jennifer Montecillo, MDGullas College of Medicine, 2019. Non-practicing medical reviewer.

How it’s used

  • CMS PECOS Medicare Provider Enrollment: Medicare ERA transactions are routed to the provider's enrolled PTAN/NPI, making PECOS enrollment the prerequisite for receiving electronic Medicare remittance data.
  • ASC X12 835 transaction standard: the ERA is the HIPAA-mandated 835 transaction, the standardized payment-decision format payers must support under Administrative Simplification.
  • EDI 837 claim pairing: each ERA answers a submitted 837 claim, closing the claim-to-payment loop keyed to the provider's NPI and PTAN.

Frequently asked questions

What is an ERA?
An ERA (Electronic Remittance Advice) is an X12 835 transaction that a payer sends electronically to a provider explaining how a claim was processed and paid.
What is an X12 835?
X12 835 is the HIPAA-standard EDI transaction set for health care payment and remittance advice — the technical format underlying ERA.
How is ERA different from EOB?
An ERA is a provider-facing payment reconciliation document in X12 835 format. An EOB is a member-facing informational document in human-readable format.

What’s on file, by the numbers

Platform snapshot · 2026-08-30

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
16fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Request access