A Type II Drug Master File (DMF) is the mechanism by which an API manufacturer shares proprietary manufacturing information with FDA without disclosing it to the sponsor companies that reference the file. This three-party relationship — DMF holder, sponsor, and FDA — is governed by 21 CFR 314.420 and FDA's Guideline for Drug Master Files. When it works correctly, the DMF enables multiple sponsors to rely on a single API source without duplicating confidential data. When it breaks, every application that references the DMF is at risk.
The break usually happens at the notification step. When an API supplier changes its process, site, or specifications, 21 CFR 314.420(c) requires the DMF holder to notify each affected sponsor in writing before making the change. Sponsors must then file supplements to their own applications. If the notification is late, incomplete, or absent, sponsors cannot update their applications in time, and FDA may find the DMF out of date during review.
This article is for regulatory affairs leads, CMC managers, quality leads, and CDMO oversight professionals who depend on DMF-referenced API sources. It identifies the most common DMF letter-of-authorization and notification traps, links each to the regulatory requirement, and provides corrective actions.
How the DMF system works
The three-party relationship
FDA's DMF guidance describes the structure clearly:
- DMF holder (typically the API manufacturer): Submits confidential manufacturing, process, and quality information to FDA. The DMF is neither approved nor disapproved; FDA reviews it only when a referenced application triggers review.
- Sponsor (NDA, ANDA, or BLA holder): References the DMF in its application by incorporating a letter of authorization (LOA) from the DMF holder.
- FDA: Reviews the DMF only in connection with a specific application that references it.
A DMF is voluntary. There is no statute or regulation requiring a DMF submission. However, in practice, most API manufacturers submit Type II DMFs because sponsors need a mechanism to reference proprietary API data without direct access to it.
Types of DMFs
| Type | Content | Typical holder |
|---|---|---|
| Type II | Drug substance (API), manufacturing process, controls | API manufacturer |
| Type III | Container closure materials and components | Packaging supplier |
| Type IV | Excipients, colorants, flavors | Excipient supplier |
| Type V | FDA-accepted reference information | Various |
Type I DMFs (manufacturing site information) were discontinued in 2000; that information is now submitted directly in applications. Type II DMFs are the focus of this article because they are the most common source of LOA and notification failures.
The letter of authorization
Under FDA's guidance, the LOA must include:
- DMF holder's name and address
- DMF number
- Specific sections of the DMF being authorized for reference
- Name and address of the authorized party (sponsor)
- Specific application number(s) the LOA supports
- Date, signature, and title of the authorizing official
The DMF holder must send a copy of the LOA to the sponsor. The sponsor must include the LOA in its application at eCTD section 1.4.2. If the DMF holder and the sponsor are the same company, an LOA is still required.
Trap 1: Stale or missing letter of authorization
The regulatory requirement
FDA's guidance states that the LOA must specifically identify the DMF content being referenced by date, volume, section, and page number. When a DMF is amended, previous LOAs may reference sections that no longer exist in their original form. If a sponsor files an application with an LOA that references outdated DMF content, FDA's reviewer cannot locate the referenced information and may issue a deficiency letter.
The common failure
The most frequent LOA problems are:
| Problem | Consequence |
|---|---|
| LOA references old DMF amendment that has been superseded | FDA reviewer cannot locate referenced data; review is delayed |
| LOA does not specify the correct application number | FDA cannot verify that the authorization applies to the pending application |
| LOA not included in the sponsor's application at eCTD 1.4.2 | FDA returns the application as incomplete |
| LOA signed by unauthorized person | FDA cannot verify authorization; requests replacement LOA |
| DMF holder changes name or ownership but does not update LOAs | Authorization chain is broken |
The GDUFA III impact
Under GDUFA III, Type II API DMFs are eligible for earlier review before ANDA submission. FDA's draft guidance Review of Drug Master Files in Advance of Certain ANDA Submissions Under GDUFA clarifies that DMF completeness directly affects ANDA filing timelines. If the LOA is stale, the DMF review is triggered but cannot be completed, and the sponsor's ANDA filing date is at risk.
Corrective action
Before every application milestone (IND filing, NDA/ANDA submission, supplement), request a current LOA from the DMF holder. Verify that the LOA references the most recent DMF amendment. If the DMF holder has changed names due to acquisition or restructuring, request an updated LOA on the current letterhead with a reference to the name change amendment in the DMF.
Trap 2: DMF holder fails to notify sponsors of changes
The regulatory requirement
21 CFR 314.420(c) states: "If the holder adds, changes, or deletes any information in the file, the holder shall notify in writing each person authorized to reference that information." FDA's guidance adds that "notice should be provided well before making the change in order to permit the sponsor/applicant to supplement or amend any affected application(s) as needed."
The notification timeline trap
The regulation does not specify a number of days for "well before." This ambiguity creates the most common trap in the DMF system:
- The API supplier decides to change a synthesis step, raw material source, or specification limit
- The DMF holder updates its DMF and submits the amendment to FDA
- The DMF holder sends notification to sponsors — but only after the change has been implemented at the manufacturing site
- Sponsors learn that their approved applications now reference a DMF that describes a different process than what is actually being manufactured
- Sponsors must file PAS or CBE-30 supplements to update their applications, but product has already been distributed
This sequence creates both a regulatory compliance gap (the approved application does not describe the current manufacturing process) and a potential safety risk (the change may affect product quality).
The magnitude of the problem
For API suppliers with dozens or hundreds of sponsors referencing their DMF, the notification obligation is substantial. Each change may require notification to every sponsor, and each sponsor must then determine the appropriate supplement category for its own application. A single API process change can trigger dozens of supplement filings across the industry.
Corrective action
Sponsors should include notification timing requirements in supply agreements and quality agreements with API manufacturers. The agreement should specify that the DMF holder must provide written notification at least 90 days before implementing any change that could affect the API quality attributes. This gives the sponsor time to assess the change, determine the supplement category, and file with FDA before the changed API reaches the market.
Trap 3: DMF amendment does not cross-reference correctly
The regulatory requirement
21 CFR 314.420(c) requires that any change to a DMF "describe by name, reference number, volume, and page number the information affected in the drug master file." The amendment must be submitted in duplicate and must be adequately cross-referenced to previous submissions.
The common failure
DMF amendments sometimes fail to provide sufficient cross-reference information. Common problems include:
| Failure | FDA's response |
|---|---|
| Amendment does not specify which sections of the DMF are affected | Reviewer cannot determine the scope of the change |
| Amendment references page numbers that have shifted due to previous amendments | Reviewer cannot locate the updated information |
| Amendment does not identify the sponsor applications affected | Reviewer cannot assess the change in context of specific products |
| Multiple amendments submitted without a cumulative summary | Reviewer must reconstruct the current state of the DMF from fragments |
The review consequence
FDA ordinarily does not independently review DMFs. Review occurs only when a sponsor's application triggers it. If the DMF is disorganized, with amendments that do not cross-reference correctly, the reviewer spends time reconstructing the file rather than evaluating the science. This delays the review of the sponsor's application.
Corrective action
Sponsors should request that DMF holders maintain a cumulative amendment log in the DMF. Before each application milestone, sponsors should ask the DMF holder to confirm that the DMF is current and that all amendments have been submitted and cross-referenced correctly.
Trap 4: Annual report and authorized-party list failures
The annual update requirement
FDA's DMF guidance requires DMF holders to submit an annual report that includes:
- An updated list of persons authorized to reference the DMF, identified by name, DMF number, and date
- Identification of any person whose authorization has been withdrawn during the previous year
- A statement that the list is current if there are no changes
The common failure
Many DMF holders neglect the annual update. When the authorized-party list becomes stale, FDA cannot verify which sponsors are currently authorized to reference the DMF. If a sponsor files an application referencing a DMF where the sponsor's authorization has not been confirmed in the annual update, FDA may request clarification before proceeding with review.
The inactive DMF trap
FDA's DMF list (current through March 31, 2026) identifies DMFs as active (A) or inactive (I). A DMF that has not been updated for an extended period may be marked inactive. If a sponsor references an inactive DMF, the review cannot proceed until the DMF holder reactivates the file. The sponsor has no control over this process and may not even know the DMF has been marked inactive.
Corrective action
Before each application milestone, check the FDA DMF list to confirm that the DMF is still active. Request confirmation from the DMF holder that the annual update has been submitted and that the authorized-party list includes the sponsor's current company name and application numbers.
Trap 5: DMF ownership transfers and acquisition disruptions
The regulatory requirement
DMF holders must notify FDA of name changes, acquisitions, or transfers of ownership. These changes should be submitted as administrative amendments to every DMF the holder owns. The DMF holder must also update the authorized-party list.
The common failure
When an API manufacturer is acquired, the new parent company may not immediately update all DMFs. Sponsors continue to reference DMFs under the previous holder's name. FDA's records show the old holder, and the authorization chain becomes unclear.
This situation is particularly dangerous when the acquired company's quality systems are integrated into the new parent's systems. Process changes may occur at the manufacturing site that are not reflected in the DMF because the administrative transfer has not been completed.
Corrective action
During due diligence for any API supply agreement, verify the current DMF holder's identity against FDA's DMF list. If the holder has been acquired, confirm that ownership transfer amendments have been submitted to all relevant DMFs. Request updated LOAs from the new holder.
Trap 6: Multiple DMFs for the same API and the cross-reference maze
The problem
Some API manufacturers maintain multiple Type II DMFs for the same drug substance — one for each manufacturing site, process version, or particle-size grade. Sponsors may reference the wrong DMF if they do not track which DMF corresponds to the API they actually purchase.
The common failure
A sponsor's ANDA references DMF A (API from Site 1). The API supplier later ships product from Site 2, which is described in DMF B. The sponsor's approved application now describes API from Site 1, but the drug product contains API from Site 2. This is a de facto unapproved manufacturing change.
Corrective action
Sponsors should maintain a register that maps each approved application to the specific DMF number, amendment date, and manufacturing site. Supply agreements should specify that the API supplier cannot change the manufacturing site without prior written notification and sponsor approval, regardless of whether the supplier has a second DMF for the alternate site.
Checklist: DMF and LOA management for each application milestone
| Element | Verified | Issue identified |
|---|---|---|
| DMF is active on FDA's DMF list | ||
| LOA is current and references latest amendment | ||
| LOA specifies correct application number | ||
| LOA is included in application at eCTD 1.4.2 | ||
| DMF holder has submitted annual update | ||
| Authorized-party list includes sponsor | ||
| DMF amendment cross-references are correct | ||
| Supply agreement includes notification timing requirements | ||
| DMF holder identity matches FDA records | ||
| Application maps to correct DMF for the API source used |
What to monitor
- FDA DMF list status: Check quarterly to confirm the DMF remains active. FDA updates the list quarterly; the current list is through March 31, 2026.
- DMF amendment history: Track all amendments to determine whether any affect the API specifications, process, or site described in the sponsor's approved application.
- API supplier change notifications: Every written notification from the DMF holder should trigger a supplement assessment within the sponsor's regulatory team.
- Authorized-party list accuracy: Confirm at each annual report cycle that the sponsor's authorization is correctly listed.
- Supply chain traceability: Verify that the API received matches the DMF-referenced source. Any discrepancy is a potential unapproved change.
Sources
- 21 CFR 314.420. Drug Master Files. https://www.ecfr.gov/current/title-21/chapter-I/subchapter-D/part-314/subpart-G/section-314.420
- 21 CFR 314.70. Supplements and Other Changes to an Approved Application. https://www.ecfr.gov/current/title-21/chapter-I/subchapter-D/part-314/subpart-G/section-314.70
- U.S. FDA. Guideline for Drug Master Files (DMF). https://www.fda.gov/drugs/drug-master-files-dmfs/guideline-drug-master-files-dmf
- U.S. FDA. List of Drug Master Files (DMFs). Current through March 31, 2026. https://www.fda.gov/drugs/drug-master-files-dmfs/list-drug-master-files-dmfs
- U.S. FDA. Drug Master Files (DMFs). https://www.fda.gov/drugs/forms-submission-requirements/drug-master-files-dmfs
- U.S. FDA. ANDA Submissions — Prior Approval Supplements Under GDUFA. https://www.fda.gov/media/89263/download
- Federal Register. Use of a Type V Drug Master File for Model Master File Submissions To Support ANDAs. January 2025. https://www.federalregister.gov/documents/2025/01/17/2025-01182/use-of-a-type-v-drug-master-file-for-model-master-file-submissions-to-support-abbreviated-new-drug
- U.S. FDA. Change in API Supplier: Drug Product Quality Tips. https://www.fda.gov/media/168954/download
- U.S. FDA. Draft Guidance for Industry: Drug Master Files. https://downloads.regulations.gov/FDA-2019-D-3989-0002/attachment_1.pdf
- Registrar Corp. A Comprehensive Guide to FDA Drug Master Files (DMF). 2025. https://www.registrarcorp.com/blog/drugs/drug-master-files/drug-master-file-dmf
- Celegence. Drug Master Files (DMFs): Types & Global Use. June 2025. https://www.celegence.com/drug-master-file-types-global-submission-requirements
- Assyro AI. Drug Master File: FDA DMF Submission Guide. May 2026. https://assyro.com/blog/drug-master-file-guide
- Outsourced Pharma. How to Use DMF Content to Support Your Application to the FDA. 2024. https://www.outsourcedpharma.com/doc/how-to-use-dmf-content-to-support-your-application-to-the-fda-0001
