The direct answer: E2B(R3) is a shared standard, but EudraVigilance and FDA each add their own implementation guide, business rules, gateway and clocks. A file that is valid for one region is not automatically accepted by the other. To submit to both, configure your safety database with region-specific profiles (partner, message header, regional data elements, validation rules), keep one single source case record, and test each pathway separately. Timing matters: FDA's postmarketing E2B(R3) requirement took effect on 1 October 2026, and commercial IND sponsors had to use it from 1 April 2026.
What Changed at FDA, and When
| Pathway | E2B(R3) status (per FDA) |
|---|---|
| Postmarketing ICSRs (drugs and biologics) | FDA began accepting E2B(R3) on 16 January 2024. From 1 October 2026, ICSRs submitted via ESG NextGen must use E2B(R3). E2B(R2) was accepted through 30 September 2026 only |
| Premarket / IND safety reports | E2B(R3) accepted since 1 April 2024; mandatory for commercial IND sponsors from 1 April 2026 |
| System naming | FDA is consolidating its reporting systems into the FDA Adverse Event Monitoring System (AEMS), replacing the FAERS name |
| No E2B capability? | The web-based Safety Reporting Portal (SRP) remains an option, as manual entry |
Practical points: once you start submitting in R3, FDA expects all submissions on that standard, and you cannot expect to move back and forth. The EU side is already settled: ISO/ICH E2B(R3) has been mandatory for ICSRs in EudraVigilance since mid-2022, with an EU ICSR Implementation Guide setting EU-specific requirements on top of the ICH specification.
Both agencies now expect E2B(R3) for these submissions, so the practical question is no longer whether to move to R3 but how to configure one safety database to serve both regions. The steps below cover that.
Same Standard, Different Rules
Both regions build on ICH E2B(R3) (ISO 27953-2). Where they differ is what the standard leaves to regional implementation:
| Area | What to check for each region |
|---|---|
| Regional data elements | FDA defines its own additional elements and mandatory/optional status on top of ICH. The EU implementation guide has its own EU-specific requirements |
| Business and validation rules | Each agency validates incoming files against its own rules. Files failing a rule are rejected with an acknowledgement |
| Message header and routing | Different sender and receiver identifiers, batch structure and gateway configuration |
| Gateway and connectivity | EudraVigilance gateway or web trader versus FDA ESG NextGen: separate accounts, certificates and testing |
| Terminology and dictionaries | MedDRA version handling, substance and product identification (EU uses IDMP-based identification and its own product dictionary) |
| Report types and classification | Expedited, periodic, premarketing, postmarketing and study report categories differ by region |
| Follow-up and amendment handling | Rules for versioning, nullification and re-submission |
| Combination products and local criteria | Region-specific identification of report categories |
The key operational lesson: "ICH-compliant" does not mean "accepted everywhere". Ask your vendor to confirm in writing which regional implementation guide version each profile supports.
Different Clocks, Different Triggers
A single case can create obligations in both regions with different timelines. The table below is a starting point; check the underlying regulation for your product and scenario.
| EU (MAH, postmarketing) | FDA | |
|---|---|---|
| Serious reactions | 15 calendar days from when the MAH first has minimum valid-case information | Postmarketing: 15-day alert reports for serious, unexpected adverse drug experiences (21 CFR 314.80) |
| Non-serious | 90 calendar days | Included in periodic reports rather than expedited |
| Clinical trials (SUSAR / IND safety report) | SUSARs to EudraVigilance under the clinical trials framework | IND: 7 calendar days for unexpected fatal or life-threatening suspected adverse reactions, 15 days for other serious unexpected suspected adverse reactions with a reasonable possibility of causal relationship (21 CFR 312.32) |
| Receiving system | EudraVigilance | FDA AEMS (formerly FAERS), via ESG NextGen |
Your database should calculate due dates per region and per case, based on seriousness, expectedness against the right reference document (the IB or label for the region) and the date of first awareness. A case that is "expected" under the EU SmPC might be "unexpected" against the US label.
Configuration Plan: Seven Steps
- Inventory what you must send where. Products, studies, countries, and the agencies that apply: FDA (IND and/or postmarketing), EudraVigilance (MAH and/or sponsor), others.
- Create separate regulatory profiles in the safety database: one per agency, each with its own partner, sender ID, schema, validation rules and reporting rules. Avoid one global profile with exceptions.
- Keep one master case. Regional differences should sit in region-specific fields, and not in duplicate cases. Define how region-specific data (labelling, expectedness, report category) is stored and versioned.
- Maintain dictionaries per region where required, and manage MedDRA upgrades with impact checks on both pathways.
- Set up gateways and test. Obtain accounts and certificates, run test messages to each agency's test environment, and confirm acknowledgements are processed and reconciled automatically.
- Validate. Include dual-region scenarios in your validation: same case, different outcomes by region, follow-ups, nullifications, rejected files and re-submissions.
- Write the SOPs and train. Who monitors acknowledgements per region, who corrects rejections, how rejection and late-submission deviations are recorded.
Check that the new setup is described in your PSMF and, for clinical trials, in your safety management plan.
Common Mistakes
- Treating FDA as "just another recipient" of the EU file
- Not testing rejections: the first real rejection arrives under deadline pressure
- Using EU expectedness (SmPC) for FDA assessments, or the reverse
- Forgetting follow-up and nullification rules differ by agency
- Leaving MedDRA upgrades unplanned for one pathway
- Assuming the vendor has already updated to the latest FDA specifications
- Having no named owner for acknowledgement reconciliation
Is Dual Reporting Realistic for a Small Biotech?
Yes, and many US biotechs entering the EU face exactly this. The decision is between operating the dual configuration yourself and outsourcing it to a PV partner. If you do it yourself, the workload is mostly in setup, testing and ongoing monitoring of agency specification changes. If you outsource, ask the partner for evidence rather than assurances: region-specific profiles, successful test messages to both agencies, and a documented process for handling acknowledgements and rejections. See also our EU market entry guide and EudraVigilance registration guide.
Key Takeaways
- FDA's postmarketing E2B(R3) requirement began on 1 October 2026 (IND sponsors: 1 April 2026), so both regions are now R3.
- Same standard, different implementation: separate profiles, rules, gateways and tests are needed.
- Clocks and expectedness are region-specific: calculate them per region.
- One master case plus region-specific profiles is a cleaner design than duplicated cases.
- Test rejection handling and acknowledgement reconciliation before you need them.
Frequently Asked Questions
Is E2B(R3) mandatory for FDA postmarketing reports?
Yes. FDA announced that, from 1 October 2026, postmarketing ICSRs submitted through ESG NextGen must use E2B(R3), after accepting E2B(R2) through 30 September 2026. FDA has accepted R3 since January 2024.
Can the same E2B(R3) file go to both EudraVigilance and FDA?
Not reliably. Both build on ICH E2B(R3), but each region has its own implementation guide, regional data elements, validation rules and routing. Generate region-specific messages from a single master case.
Is FAERS still the name of the FDA system?
FDA is moving to the FDA Adverse Event Monitoring System (AEMS), which replaces the FAERS name. Many industry documents still say FAERS.
What do I report to FDA for an IND safety report?
Sponsors must report serious and unexpected suspected adverse reactions for which there is a reasonable possibility that the drug caused the event, within 15 calendar days (7 calendar days for unexpected fatal or life-threatening reactions), under 21 CFR 312.32.
Next Step
Have questions about configuring your safety database and gateways for EudraVigilance and FDA? See our Safety database set-up and maintenance pages, or contact us.
Related reading: EU market entry; Right-sized PV system for EU market entry.