The ICH E2B(R3) Deadline Is Here: What Small Biotechs Need to Know About ICSR Intake

The April 1, 2026 FDA deadline for mandatory ICH E2B(R3) electronic ICSR submissions is no longer on the horizon. It is here.1 If your biotech is still collecting adverse events on paper, in a spreadsheet, or through an unstructured email process, you have a compliance gap that needs immediate attention.

This article explains what the requirement actually means, who it affects, what the most common operational failure point is (adverse event intake), and what your team can do right now. The sections added in October 2026 cover postmarketing files. They cite the AEMS electronic submissions page, the 6 April 2026 Federal Register notice, and the AEMS E2B(R3) data standards page.

What changed on 1 October 2026

On 6 April 2026 FDA published a notice, 10 91 FR 17284, about postmarketing individual case safety reports sent to the FDA Adverse Event Monitoring System (AEMS), formerly the FDA Adverse Event Reporting System (FAERS). Beginning 1 October 2026, those reports must use ICH E2B(R3) data standards when they are submitted through the Electronic Submissions Gateway Next Generation (ESG NextGen).

The products named in the notice are human drug products, biological products, and combination products led by a drug or a biologic. The AEMS electronic submissions page states the same date, and it says this announcement extends the previously recommended E2B(R3) implementation period by six months.1 The page states the extension and the 1 October 2026 date. That sentence does not name the earlier recommended end date.

FDA will keep accepting postmarketing ICSRs prepared with E2B(R2) through 30 September 2026, for companies that have not yet switched.1 10 Once a company has begun submitting in E2B(R3), FDA expects later ICSR submissions to use E2B(R3). The notice says FDA intends to stop accepting E2B(R2) for those products after 30 September 2026.

The notice also describes what E2B(R3) changes relative to E2B(R2). Examples in the notice are new, changed, and expanded data elements; seriousness assessed at the level of the event rather than only for the whole case; and attachments embedded in the ICSR rather than sent as separate files.10

E2B(R3) and E2B(R2) field changes

The searches E2B R3 and E2B R3 FDA are this standard. FDA and ICH print it as E2B(R3). The 6 April 2026 notice gives the examples above. The 21 February 2014 notice is the earlier FDA announcement of the E2B(R3) implementation guidance and of the appendix on backwards and forwards compatibility, which relates elements in the 2001 ICH E2B guidance to E2B(R3).12 The table stays inside those two notices. Element codes belong in the guidance files, not in a paraphrase.

The element rows are in the ICH E2B(R3) implementation guidance and the FDA regional implementation guide, which the 2026 notice incorporates.10 The ICH specification page is the council copy of the same family of files.2

This October rule is the postmarketing gateway rule. It sits beside the earlier IND rule on the same AEMS page. Since 1 April 2026, FDA has required commercial IND sponsors to submit premarketing study ICSRs electronically in E2B(R3) through ESG NextGen.1 Keep the two dates apart when you update an SOP. April is the commercial IND electronic file. October is the postmarketing file on ESG NextGen.

Who the postmarketing rule applies to

The notice applies to postmarketing ICSRs for human drug products, biological products, and combination products led by a drug or a biologic, submitted to AEMS, formerly FAERS, via ESG NextGen.10 The authority line in the notice points at the electronic submission paragraphs in the postmarketing regulations, including 21 CFR 314.80(g)(1) and 21 CFR 600.80(h)(1).

The notice says the E2B(R3) standard it announces applies to submission through ESG NextGen. Companies that send ICSRs through the Safety Reporting Portal are told, on the AEMS page, that no action is required for this change.1

A separate sentence on that page is easy to mix in by mistake. For bioavailability and bioequivalence studies that are exempt from an IND, electronic submission is voluntary, and FDA says those reports may still go on Form FDA 3500A to the mailbox named on the page.1 That sentence is about those studies. It is not the postmarketing rule.

ESG NextGen and the Safety Reporting Portal

FDA describes two electronic options for ICSRs.1 10

• ESG NextGen. Database to database transmission of XML using E2B standards. From 1 October 2026, postmarketing ICSRs on this path use E2B(R3) in AEMS, formerly FAERS. The technical documents are on the AEMS E2B(R3) data standards page.11
• Safety Reporting Portal. Applicants, and responsible persons at companies with reporting duties who do not have E2B capability, may enter premarketing ICSRs, postmarketing ICSRs, and attachments in a web form. FDA says an account request goes to the AEMS electronic submission contact and that activation takes about 7 to 10 business days. A company that already submits through ESG NextGen cannot use the portal for those ICSRs and attachments.1

The notice uses the same split. The portal is how applicants, specified nonapplicants, and responsible persons without ICH E2B(R3) capability can submit. The data standard in the notice is the gateway standard.10

ESG NextGen submission steps

These three steps are the Unified Submission Portal path in FDA’s own guides. They are gateway steps. They are not a statement that FDA endorses or certifies any vendor, including AE Connect. The safety database, or a person using the Safety Reporting Portal, still prepares the ICSR. SUSAR reporting is the IND clock for a case that is serious, unexpected, and suspected. The file format here is a separate question from that clock.

1. Register on the Unified Submission Portal. FDA’s AS2 account page says to register for an ESG NextGen account via the Unified Submission Portal. Open the Electronic Submissions Gateway Next Generation page, choose Industry USP Log In, accept the warning, and choose Register now. Complete the account, sign on, and enter the one time passcode from the registration email. The portal guide then collects company information. A new user uploads a signed Non-Repudiation Letter or creates one in the wizard. The first user at a new company is a Power User. A new user at an existing company waits for a Power User to accept the account. An agent, a CRO, or a consultant registers its own company and uploads an authorization letter.13
2. Send a test submission. In the portal, open Test Submission. On a first upload the guide prompts you to install the transfer tool, then you choose the file, the receiving center, and the submission type, sign, and submit. The ESG NextGen FAQ says test submissions are supported. A person who has never submitted through the older gateway may have to complete a test before production for a center and submission type that requires one. Accounts that moved from the older gateway already have production access and do not upload a test first. Which combinations require the test is on the Center Submission Types page.14
3. Read the acknowledgements (ACKs). The portal guide says test and production uploads receive ACK messages by email, and the same messages are in Submission History. ACK1 says whether the file uploaded into ESG NextGen. A failure at this step can be a virus scan or an incomplete upload. ACK2, when that submission type uses it, says whether the file reached the center. ACK3 and ACK4, when that submission type uses them, are the center response. Not every submission type receives every ACK. For CDER and CBER submission type AERS, the acknowledgements page lists ACK3 as an .ack file and says ACKs are not generated for an invalid file extension or for a file that is not encoded properly.15

FDA regional data elements and business rules

The notice incorporates the ICH E2B(R3) implementation guidance and the FDA regional implementation guide.10 The AEMS data standards page posts that regional guide for postmarketing ICSRs, together with an Excel file of FDA E2B(R3) core and regional data elements and business rules, forward compatible rules, and sample XML.11 Use the files on that page. This article does not copy their rows.

The same page says that on 6 March 2026 FDA announced availability of the E2D(R1) guidance on postapproval safety data, and that AEMS now accepts new values for data element C.5.4, the study type where the reaction was observed. The values named on the page are 4 for a patient support program, 5 for a market research program, and 6 for an organised data collection system with source data from a digital platform. The page uses that spelling. It also points to an ICH information paper that updates user guidance for C.1.3, type of report, and for C.5.4.11 Confirm the code list against the current file before a system stores the mapping.

Validation problems to avoid

FDA does not publish a numbered list of rejection codes on the pages cited here, so this section will not invent one. The failures that follow are the ones the notice and the AEMS pages describe.

• An E2B(R2) file on ESG NextGen on or after 1 October 2026. FDA says it will stop accepting E2B(R2) for the named postmarketing products after 30 September 2026.10
• A mix of standards after you have switched. Once you have submitted in E2B(R3), later ICSRs are expected to use E2B(R3).1
• Seriousness stored only on the case. The notice says E2B(R3) assesses seriousness at the event level.10
• Attachments sent outside the ICSR. The notice says E2B(R3) embeds attachments in the ICSR.10
• Skipping the regional rules. The business rules spreadsheet and the regional implementation guide are the FDA documents for core and regional elements.11 Run the FDA E2B(R3) validator, which the data standards page describes as a browser tool that checks a file and shows the result as the check finishes.

A checklist, and where AE Connect fits

Work the gateway question before you rewrite the intake form.

• Confirm whether postmarketing ICSRs go through ESG NextGen or through the Safety Reporting Portal.1
• If they go through ESG NextGen, plan the E2B(R3) file for 1 October 2026, and stop E2B(R2) after 30 September 2026.10
• If you have already sent one E2B(R3) ICSR, send the later ones in E2B(R3) as well.1
• Read the regional implementation guide and the business rules file, then run the FDA validator on a sample file.11
• Capture the reporter, the patient, the suspect product, and the event before anyone builds that file. The E2B(R3) checklist is the longer readiness list. The ICSR submission guide separates the message standard from the product. E2B(R3) case preparation is the product page for that step.

AE Connect is the intake workspace in front of that file. A person accepts or overrides the draft. Oracle Argus, ArisGlobal LifeSphere, and Veeva Vault Safety remain the system of record when you use them. How case text is handled is on the trust page. The FDA pages cited in this update do not name AE Connect, and they do not name any other vendor as a preferred way to report to AEMS, formerly FAERS.

What Is ICH E2B(R3) and Why Does It Matter?

ICH E2B(R3) is the international standard for the electronic transmission of Individual Case Safety Reports (ICSRs). Developed by the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH), it defines the data elements, XML structure, and message specifications required when submitting adverse event safety reports to regulatory authorities.2

The EMA has required E2B(R3) submissions for years. The FDA has now aligned with that global standard. Since 1 April 2026, the AEMS page says commercial IND sponsors who submit premarketing study ICSRs electronically through ESG NextGen must use E2B(R3). AEMS is the name FDA now uses for the database formerly called the FDA Adverse Event Reporting System (FAERS).1

The change was not sudden. On January 16, 2024, the FDA began accepting E2B(R3) electronic submissions and gave sponsors a 24-month voluntary transition period.1 On April 1, 2024, the FDA extended acceptance to premarketing IND ICSRs in E2B(R3) format. That voluntary window has now closed. The MedWatch 3500A PDF process that many small biotech IND sponsors have relied on for expedited IND safety reports is no longer an acceptable submission pathway under the final FDA guidance for IND safety reports.4

Who Is Actually Affected?

This is where many small biotech teams get confused. The requirement specifically impacts two groups under 21 CFR 312.32:5

If your team has been submitting IND safety reports by generating a MedWatch 3500A PDF, attaching it to a Form 1571 cover letter, and routing it to the FDA, that workflow must now be replaced. Your ICSRs need to be submitted electronically in E2B(R3) XML format through either the FDA Electronic Submissions Gateway (ESG) or the Safety Reporting Portal (SRP).

The Part Nobody Talks About: Adverse Event Intake

Most of the industry conversation around the E2B(R3) deadline focuses on the submission side: XML formatting, FAERS gateway accounts, ESG validation, regional data elements. Those are legitimate technical requirements.

But for small and mid-size biotechs, the bigger operational risk is upstream. It is the intake process.

An ICSR is only as good as the data captured at the point of first receipt. The E2B(R3) format asks for structured data elements across dozens of fields, including MedDRA-coded adverse event terms, structured product information, reporter qualification, patient demographics, and causality assessment.6 If your intake process is a phone call logged in a shared spreadsheet, or a free-text email forwarded to a drug safety inbox, you are not capturing the structured data you will need to build an E2B(R3) XML file.

The workflow problem looks like this in practice. A site coordinator calls your safety desk to report that a patient experienced Grade 3 liver enzyme elevation on Day 14 of Cycle 2. Someone takes notes. That note eventually gets handed off to a PV specialist who tries to reconstruct the case from memory and a partially filled CRF. The narrative is drafted, MedDRA coding is done manually, and the case is assembled in whatever system the team has available. The submission is prepared on a tight 7-day clock.

This is the reality for many small biotech programs. It is inefficient, error prone, and under the E2B(R3) requirement, it creates file rejections when the XML is submitted. A structured intake process solves this at the source. When intake forms capture the right data elements from the first point of contact, including the E2B(R3) fields the file asks for, the path from report receipt to the ICSR file becomes shorter and easier to explain in an inspection.

What Your Intake Process Needs to Support E2B(R3) Compliance

At minimum, your adverse event intake workflow should capture the following structured data at the time of report receipt:

Reporter Information

Name, profession, address, contact details, and reporter qualification (healthcare professional, consumer, other).

Patient Information

Age or date of birth, sex, relevant medical history, and concomitant medications.

Event Information

Adverse event description, onset date, duration, outcome, seriousness criteria (death, life-threatening, hospitalization, disability, congenital anomaly, other medically important condition), and expectedness assessment against the current Investigator Brochure.

Product Information

Suspect drug name, dose, route of administration, therapy start and stop dates, and indication for use.

Narrative

A structured free-text account of the case that will support the Section H narrative in the E2B(R3) ICSR.

If your intake form is not capturing all of these elements at the time of first contact, you will have data gaps that slow down case processing and create compliance risk.

Common Gaps at Small Biotech Programs

Based on 15 years of experience in pharmaceutical quality and pharmacovigilance across oncology, hematology, and neurodegenerative disease programs, the most common intake gaps at small biotech companies are:

• No standardized intake form. Reports come in through whatever channel is available: phone, email, site fax, CRF comment field. There is no structured process for capturing minimum required data elements at first receipt.
• Missing reporter qualification. Whether the reporter is a healthcare professional, a patient, or a family member materially affects the validity and processing of the ICSR. This is frequently not captured upfront.
• Unstructured event description. Free-text descriptions of adverse events without MedDRA-aligned language create extra work at the coding stage and introduce inconsistency across cases.
• No ESG account. Submitting to FAERS via the Electronic Submissions Gateway requires a pre-established account and WebTrader configuration.7 Many small sponsors have never set one up because they were submitting via PDF. Setting up an ESG account takes time and should not be done in the days before a deadline.
• No single case record. If the case lives in a shared spreadsheet or a general project tool, a later reviewer cannot see who changed a field. 21 CFR Part 11 describes electronic records and electronic signatures. This page does not claim that any product meets that regulation.9

A Practical Checklist for IND Sponsors

If you have an active IND and have not yet confirmed your E2B(R3) readiness, work through this checklist now:

• FDA ESG account created and WebTrader configuration tested7Required for database-to-database E2B(R3) transmission to FAERS
• E2B(R3) XML generation capability confirmedVia the safety database, a software platform, or a CRO
• Test submissions checked in the FDA staging environment7The FDA E2B(R3) validator reports rejection errors and warnings before transmission
• If using a CRO: written confirmation of E2B(R3) readiness obtainedCROs must independently confirm ESG connectivity and XML validation capability

• Structured AE intake form capturing all minimum E2B(R3) data elementsReporter info, patient demographics, event details, product info, seriousness criteria
• Clock-start date documented for every caseDay 0 is the date of first receipt of minimum criteria for a valid ICSR
• 7 calendar day and 15 calendar day reporting timelines tracked57 calendar days, from initial receipt: an unexpected fatal or life-threatening suspected adverse reaction (21 CFR 312.32(c)(2)). 15 calendar days, after the sponsor determines the information qualifies, to FDA and participating investigators (21 CFR 312.32(c)(1)): a serious and unexpected suspected adverse reaction, findings from other studies, findings from animal or in vitro testing, and an increased rate of occurrence of serious suspected adverse reactions.
• A named place for the case record, with a history of who changed it21 CFR Part 11 covers electronic records and electronic signatures. This page does not claim that any system is validated, certified, or compliant.

• Pharmacovigilance Plan updated to reference E2B(R3) submission pathMust reflect current FDA ESG submission method, not legacy MedWatch PDF process
• SOPs updated for E2B(R3) intake, processing, and submission workflowInclude clock-start criteria, triage, medical review, coding, submission, and follow-up
• Training completed for all staff involved in AE receipt and case processingDocument with date, content covered, and trainer or trainee signature

The Opportunity Inside the Compliance Requirement

The E2B(R3) transition is not purely a burden. It is an opportunity to modernize the way your safety data is captured, structured, and submitted, in a way that makes your program more defensible and more efficient.

Paper intake and ad hoc intake create backlogs, inconsistencies, and inspection findings. A structured intake layer that feeds the case record and the submission file reduces those risks and leaves the safety team more time for medical review and signal assessment.

For a small biotech, Oracle Argus, ArisGlobal LifeSphere, or Veeva Vault Safety can still be the system of record. AE Connect integrates a structured draft of the case with that database, and with any other safety database. It does not replace the database. See E2B(R3) case preparation.