PMDA eCTD v4.0 Mandate: The Complete Guide for 2026
Japan's PMDA is the first major regulatory authority in the world to mandate eCTD v4.0. As of April 1, 2026, all new drug submissions to PMDA must use the new format. Here's everything your regulatory team needs to know.
Table of Contents
What is eCTD v4.0?
The electronic Common Technical Document (eCTD) v4.0 is the next-generation standard for regulatory submissions, developed under ICH M8 guidelines. This is not a minor version bump — it represents a fundamental architectural shift.
Where eCTD v3.2.2 used a folder-and-file hierarchy with multiple XML files, v4.0 moves to a metadata-driven, message-based format built on the HL7 v3 Regulated Product Submission (RPS) standard. Think of it as moving from a filing cabinet to a database.
Why This Matters
Japan is the world's third-largest pharmaceutical market, valued at over $84 billion. Every global pharma company that sells or plans to sell drugs in Japan must submit through PMDA. And as of today, those submissions must use eCTD v4.0.
Japan is 2-3 years ahead of the FDA and EMA in mandating this standard. Companies that master v4.0 for PMDA submissions will be well-positioned when FDA (projected 2028-2029) and EMA (projected 2027) follow suit.
Key Differences: v3.2.2 vs v4.0
| Aspect | eCTD v3.2.2 | eCTD v4.0 |
|---|---|---|
| XML Structure | Multiple XML files (regional, index, study) | Single unified XML exchange message |
| Standard Basis | XML DTD backbone | HL7 v3 RPS schema (ISO IDMP aligned) |
| Document Reference | "Leaf" elements | "Context of Use" (CoU) with metadata lifecycle |
| Organization | Hierarchical table of contents | Flat structure with keywords & controlled vocabularies |
| Document ID | File paths | UUIDs and Object Identifiers (enables cross-submission reuse) |
| Metadata Corrections | Requires resubmitting files | Metadata corrected without resubmitting documents |
| Product Scope | Primarily pharmaceuticals | All regulated product types |
The most significant change is the shift from "leaves" to "Context of Use". In v3.2.2, documents were referenced by their position in a folder hierarchy. In v4.0, each document is tagged with metadata describing what it is, what it's for, and its lifecycle status. This enables powerful capabilities like cross-submission document reuse — submit a stability study once and reference it across multiple applications without resubmission.
Global Mandate Timeline
Japan is leading the world on eCTD v4.0 adoption. Here's where each major authority stands:
| Authority | Status | Mandatory Date |
|---|---|---|
| Japan (PMDA) | Mandatory | April 1, 2026 |
| EU (EMA) | Voluntary (CAPs) | ~Q3 2026 to 2027 |
| US (FDA) | Voluntary (CDER/CBER) | ~2028-2029 |
| Canada (Health Canada) | Planning | Mid-to-late 2026 |
| Australia (TGA) | Planning | Mid-to-late 2026 |
| Switzerland (Swissmedic) | Planning | ~2028 |
The practical implication: companies filing in Japan are now the global pioneers of eCTD v4.0. The lessons learned here will shape how the rest of the world transitions.
PMDA-Specific Requirements
Beyond the general eCTD v4.0 specification, PMDA has specific requirements:
Technical Requirements
- Full HL7 v3 RPS schema compliance
- Use of PMDA-specific controlled vocabularies
- SHA-256 checksum file (sha256.txt) must accompany the submission
- UTF-8 encoding mandatory
- UUID assignment required for all documents and sections
- Validated using a compliant eCTD v4.0 validator and viewer
Japan-Specific Submission Types
jp_initial_a: Study data + CTD-specified documents (combined)jp_initial_b: Study data onlyjp_initial_c: CTD-specified documents onlyjp_other: Used only when advised by PMDA
Language Requirement
Key summary documents must be submitted in Japanese. Review questions and responses are conducted in Japanese. This remains unchanged from v3.2.2 and continues to be one of the unique aspects of filing in Japan.
10-Step Preparation Checklist
Whether you're filing for the first time under v4.0 or transitioning an existing program, here's what your team needs to address:
- Gap analysis — Assess current systems against v4.0 requirements. Identify what needs upgrading.
- Software upgrades — Ensure your Document Management System and publishing tools are eCTD v4.0 compliant. Verify vendor upgrade paths.
- Controlled vocabulary synchronization — Implement automated CV updates aligned with PMDA-specific vocabularies.
- Schema validation testing— Test your submissions against PMDA's validation rules before filing.
- UUID management — Establish processes for UUID assignment and cross-submission document reuse tracking.
- Metadata strategy — Define sender-defined keywords and plan Context of Use mappings for your documents.
- Team training — Cross-functional training for Regulatory Affairs, QA, Data Management, and IT teams.
- Pilot submissions — Conduct test submissions to PMDA to validate your setup before a real filing.
- Gateway system readiness— Ensure connectivity to PMDA's submission gateway.
- Japanese language capability — Ensure your team has capacity for Japanese-language summaries and regulatory correspondence.
Common Pitfalls to Avoid
- Underestimating the metadata shift— v4.0 is not "v3.2.2 with a new wrapper." The Context of Use model requires fundamentally different thinking about document organization.
- Neglecting PMDA-specific vocabularies — Using generic ICH controlled vocabularies without PMDA-specific extensions will cause validation failures.
- Ignoring the Japanese language requirement — Key summaries must be in Japanese. Factor this into your timeline and resourcing.
- Dual-format maintenance burden — If you file in Japan (v4.0 mandatory) and the US/EU (still v3.2.2), you need to maintain both formats simultaneously. Plan your tooling accordingly.
- Late vendor coordination— Publishing tool vendors have been rolling out v4.0 support on different timelines. Confirm your vendor's readiness now, not at filing time.
What This Means for Your Team
The eCTD v4.0 mandate is live. If your company is filing in Japan, there is no more runway — your next PMDA submission must be in the new format.
But there's a silver lining: companies that get this right for Japan will have a significant head start when FDA and EMA follow suit. Japan's early adoption is effectively a proving ground for the global regulatory community.
For teams tracking PMDA approvals, review reports, and regulatory intelligence, having access to structured English-language PMDA data is more important than ever. Understanding how PMDA has handled previous submissions — including review timelines, data requirements, and approval conditions — is critical intelligence for planning your own v4.0 filings.
Stay ahead of PMDA regulatory changes
PharmaLens monitors PMDA approvals and translates review reports into structured English data. Join the waitlist for early access.
Join the WaitlistReferences
- PMDA eCTD v4.0 Implementation Guide (Appendix 1), March 2025
- PMDA eCTD v4.0 JP Check Items List v1.6.0.0
- Freyr Solutions: eCTD v4.0 in Japan — Navigating the 2026 Transformation
- DIA Global Forum: eCTD v4.0 — A Look at 2025 and Beyond
- Certara: 10 Things to Know About eCTD 4.0
Source: PMDA Website. This article is for informational purposes only and does not constitute regulatory advice.