FDA Began Supporting eCTD v4.0 Forward Compatibility on 16 October 2026

On 16 October 2026 FDA published a notice in the Federal Register announcing that its support for forward compatibility for eCTD v4.0 electronic submissions begins on that date. According to the notice, forward compatibility allows FDA to process eCTD v4.0 submissions to applications that were originally submitted and established using eCTD v3.2.2. In practical terms, a sponsor with an application already running in the older format can now send subsequent sequences in the newer standard without starting a new application.

FDA’s eCTD web page states that CDER and CBER support forward compatibility for NDAs, BLAs, ANDAs, INDs and master files from 16 October 2026. The same page records that FDA will provide advance notice of when the agency will begin supporting electronic submission only in eCTD v4.0. The notice also restates that the version of eCTD currently supported by FDA is specified in the FDA Data Standards Catalog, so the Catalog remains the reference for which versions are accepted at any given time.

The announcement follows a period of optional use. FDA began accepting eCTD v4.0 for new applications on 16 September 2024, while continuing to accept eCTD v3.2.2 for all submission types. Until forward compatibility was available, sponsors who wanted to use v4.0 could do so only for applications that started in v4.0, which limited uptake for large existing portfolios.

eCTD v4.0 is the ICH successor to the v3.2.2 specification on which most electronic regulatory submissions are currently built. The CTD module structure that authors work with stays the same, but the technical exchange format, the lifecycle rules and the use of controlled vocabularies change, so v4.0 requires updated publishing tools, new validation rules and new working practices in regulatory operations teams.

Forward compatibility is the mechanism that links the two standards. Without it, a sponsor would have to maintain every existing application in v3.2.2 for the rest of its life, even after adopting v4.0 for new products. With it, an application established in v3.2.2 can move to v4.0 at a time the sponsor chooses, carrying its history forward. Because much of a sponsor’s submission activity consists of amendments, supplements and annual reports to established applications, this capability is a practical precondition for any eventual v4.0-only requirement.

In February 2026, RAPS reported that FDA and EMA officials were encouraging companies to pilot eCTD v4.0 and that FDA intended to have forward compatibility ready by autumn 2026. The October notice confirms that this capability is now in place for the application types listed.

eCTD v3.2.2 remains a supported format at FDA. The notice does not withdraw it and does not set a date after which only v4.0 will be accepted. Some consultancy publications have suggested that a v4.0-only requirement could arrive around 2029, but that is an industry forecast rather than an FDA position, and FDA had not published a mandatory date at the time of checking.

Forward compatibility under this notice is described for CDER and CBER and for NDAs, BLAs, ANDAs, INDs and master files. Sponsors working with other FDA centres or other submission types should confirm the position on FDA’s eCTD pages before planning a transition. Sponsors should also note that submission standards and the eCTD v4.0 technical conformance material have been revised during 2026, and the current versions on FDA’s eCTD resources page should be used rather than earlier copies.

The notice is a statement of technical support, not a new legal obligation. The underlying requirement to submit NDAs, ANDAs, BLAs and commercial INDs electronically in a format specified by FDA continues to rest on section 745A(a) of the Federal Food, Drug, and Cosmetic Act and the associated guidance on electronic submissions.

For regulatory operations teams, the main decision is when to move existing applications to v4.0. Moving early gives experience with the new message structure and controlled vocabularies while v3.2.2 remains available as a fallback. Moving later avoids disruption but concentrates the work closer to whatever mandatory date FDA eventually announces. Sponsors with global portfolios will also want to align their FDA plans with other regions, since Japan, the EU and other authorities are on different timetables.

Before sending a first forward-compatible sequence, sponsors should confirm that their publishing and validation software supports the transition from a v3.2.2 lifecycle into v4.0, test the conversion on non-critical sequences where possible, and check internal document management and metadata practices against the v4.0 specifications. Medical writers and authors are less directly affected, because document content and the CTD module structure do not change, but consistent document granularity and naming will make the move to v4.0 simpler.