ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

United States — HIPAA, IRS and the absence of a federal B2B mandate

The United States has no national B2B e-invoicing mandate. Federal documentary compliance focuses on healthcare (HIPAA / X12), tax (IRS reporting), payments (NACHA / Fedwire) and state-by-state marketplace tax (Wayfair v. South Dakota, 2018).

Regulatory timeline

  • 21 August 1996 — Health Insurance Portability and Accountability Act (Public Law 104-191). Congress passes HIPAA; Title II introduces Administrative Simplification.
  • 17 August 2000 — Final Rule 45 CFR Part 162 (HHS). Formal adoption of ASC X12N as the standard transaction set for payers and providers; initial deadline set for 16 October 2002.
  • 16 October 2003 — Compliance Date. After a one-year extension via the Administrative Simplification Compliance Act, Covered Entities must use X12 4010A1 for all HIPAA transactions.
  • 17 January 2009 — HIPAA 5010 Final Rule (Modifications). Migration to ASC X12N 005010 enforced on 1 January 2012 to support ICD-10 and new operational transactions.
  • 23 March 2010 — Patient Protection and Affordable Care Act (ACA). Section 1104 extends the mandate to CAQH CORE Operating Rules for eligibility, claim status and EFT/ERA.
  • 21 June 2018 — South Dakota v. Wayfair Inc. (Supreme Court). Reversal of physical nexus for sales tax; opens the path to Marketplace Facilitator Acts across 45 states.
  • 20 July 2023 — FedNow Service launch by the Federal Reserve: 24/7 instant payments between participating banks, alongside RTP from The Clearing House.
  • 2024-2026 — ASC X12N 006020 test phase. HHS and CMS pilot the next HIPAA version through the Designated Standard Maintenance Organizations (DSMO); no switch-over date announced.

Technical schema

The HIPAA exchange standard is ASC X12 EDI, version 5010 (006020 in pilot). Each transaction is wrapped in an envelope:

  • ISA / IEA: interchange envelope.
  • GS / GE: functional group, code HC for healthcare, HP for payment advice.
  • ST / SE: transaction set, 837 for claims, 835 for remittance.

For IRS reporting, the official channel is FIRE (Filing Information Returns Electronically) or the newer IRIS (Information Returns Intake System) since 2023, in JSON and XML, for Forms 1099-MISC, 1099-NEC, 1099-K, 1099-INT and 1099-DIV.

Sample X12 837 Professional fragment:

texthipaa-837-professional.edi
ISA*00*          *00*          *ZZ*SUBMITTER  *ZZ*RECEIVER   *260516*1023*^*00501*000000001*0*P*:~
GS*HC*SUBMITTER*RECEIVER*20260516*1023*1*X*005010X222A1~
ST*837*0001*005010X222A1~
BHT*0019*00*0123*20260516*1023*CH~
NM1*41*2*Ediverse Demo Clinic*****46*123456789~
PER*IC*CONTACT*TE*5551234567~
NM1*40*2*INSURANCE PAYER*****46*987654321~
HL*1**20*1~
NM1*85*2*Ediverse Demo Clinic*****XX*1234567890~
N3*1 Main Street~
N4*Boston*MA*02115~
REF*EI*123456789~
HL*2*1*22*0~
SBR*P*18*******MC~
NM1*IL*1*Doe*John*A***MI*W123456789~
N3*100 Patient Lane~
N4*Boston*MA*02116~
DMG*D8*19800301*M~
CLM*CLAIM-2026-0042*250.00***11:B:1*Y*A*Y*Y~
HI*ABK:Z0000~
LX*1~
SV1*HC:99213*125.00*UN*1***1~
DTP*472*D8*20260515~
SE*22*0001~
GE*1*1~
IEA*1*000000001~

Submission flow

The standard HIPAA flow involves a clearinghouse: the provider sends the 837, the clearinghouse rewrites the envelope and routes to the payer, which returns an 835 (ERA — Electronic Remittance Advice) together with the EFT payment via NACHA ACH.

texthipaa-flow.txt
┌──────────────┐    ┌──────────────────┐    ┌──────────────┐
│ Provider     │───>│ Clearinghouse    │───>│ Payer health │
│ (EHR / PMS)  │X12 │ (Change Health,  │    │ plan         │
│              │837 │  Availity, etc.) │    │              │
└──────────────┘    └─────────┬────────┘    └──────┬───────┘
                              │                    │
                              │       835 ◄────────┘
                              ▼     remittance
                    ┌──────────────────┐
                    │ HIPAA transaction │   ← TA1/999 ack
                    │ envelopes (ISA/GS)│      synchronous
                    └──────────────────┘

Acknowledgements follow the X12 triple model: TA1 for ISA envelope syntax, 999 for X12 transaction-set conformance (replaces the legacy 997), 277CA for the business claim acknowledgement.

Validation

Common pitfalls

  1. No federal B2B mandate. European vendors often project their EN 16931 / PEPPOL experience onto the US market: no equivalent exists. The B2B market runs on PDF / EDI X12 850/810 negotiated bilaterally or via legacy VANs (Sterling, OpenText, GXS, TrueCommerce).
  2. Sales tax — marketplace facilitator. Since Wayfair (2018) and the California Marketplace Facilitator Act 2019, the platform (Amazon, Walmart, eBay) collects sales tax on behalf of the seller in 45 states. The economic-nexus threshold rule (200 transactions OR $100K revenue) must be tracked state by state.
  3. HIPAA Companion Guides per payer. The X12 5010 TR3 is the base, but each payer (BCBS, Aetna, UnitedHealth, Medicare) publishes a Companion Guide that restricts or extends some segments. Coding against the TR3 alone causes 277CA rejections in production.
  4. NPI vs Tax ID. The NPI (National Provider Identifier, 10 digits) is mandatory for Covered Entities but does not replace the Tax ID (EIN) nor the state Medicaid identifier. Confusing the three rejects the 837 with CSC=496 (NPI invalid for the submitter).
  5. FedNow vs ACH vs Fedwire. FedNow (instant, 24/7) and TCH RTP coexist with ACH (batch, 1-3 days) and Fedwire (wholesale, business day). Rail choice drives message format (ISO 20022 pacs.008 for FedNow and RTP, NACHA for ACH, FedLine for Fedwire) and cost.