Quick answer: Does CE Mark help with FDA approval? Partly — but less than most manufacturers expect, and not in the way they expect. A CE Mark has no legal standing with the FDA. It does not shorten review, it does not substitute for any submission, and FDA grants clearance through a 510(k), not "approval" (approval is the PMA pathway for Class III devices). What does carry over is work product, not status. Your ISO 13485 quality system now maps directly onto FDA requirements, because the Quality Management System Regulation (QMSR) took effect on 2 February 2026 and incorporates ISO 13485:2016 by reference [1]. Your clinical data can be accepted under 21 CFR 812.28 if it meets good clinical practice conditions [4]. Your biocompatibility and electrical safety testing is often reusable. Your Clinical Evaluation Report, notified body certificate, and EU risk-benefit argument are not.

What FDA actually recognizes from your EU file

There is no mutual recognition agreement between the EU and the United States for medical device market authorisation. FDA does not read your notified body certificate. So the useful question is not whether CE Mark counts — it is which artefacts in your EU technical file can be reused as evidence in a 510(k), and which have to be rebuilt. Here is the honest short list.

Artefact from your EU file	Status at FDA
CE Mark certificate	No standing. Not evidence of anything.
Notified body assessment	No standing.
ISO 13485 certificate	Not accepted in lieu of FDA inspection — but the underlying system now maps to QMSR [1]
MDSAP audit report	Accepted as a substitute for routine FDA inspections [6, 7]
Clinical investigation data	Conditionally accepted under 21 CFR 812.28 [4]
Biocompatibility testing (ISO 10993)	Usually reusable if the standard version and endpoints match
Electrical safety / EMC (IEC 60601)	Usually reusable
Software lifecycle file (IEC 62304)	Usually reusable
Clinical Evaluation Report (MDR Annex XIV)	Not a 510(k) deliverable. Different argument entirely.
EU risk-benefit determination	No FDA analogue. Substantial equivalence replaces it.

The pattern: objective test evidence travels well. Regulatory conclusions do not. A biocompatibility report is a measurement. A Clinical Evaluation Report is an argument built to answer a European question. FDA is asking a different question, so the argument has to be rebuilt even when the underlying data is fine.

QMSR: the one place the ground genuinely shifted in your favour

This is the biggest change for CE-marked manufacturers in a decade, and many teams still haven't priced it in.

Until February 2026, FDA ran its own quality system regulation — the old QSR at 21 CFR Part 820 — which was structurally different from ISO 13485. If you held ISO 13485, you still had to build a parallel understanding of Part 820.

That gap has closed. The QMSR became effective on 2 February 2026 and amends Part 820 to incorporate ISO 13485:2016 by reference, along with Clause 3 of ISO 9000:2015 for terminology [1, 2]. FDA also retired the Quality System Inspection Technique (QSIT) on the same date and moved to a new inspection programme, Compliance Program 7382.850 [2].

For a manufacturer already certified to ISO 13485:2016, this is real, material advantage. Your QMS is now substantially the system FDA expects.

But three cautions, because this is where teams overcorrect.

First, incorporation by reference is not equivalence. The QMSR retains US-specific requirements layered on top of ISO 13485 — device labelling and packaging controls, complaint handling that interacts with Medical Device Reporting under 21 CFR Part 803, and records provisions that differ from the standard. Reading ISO 13485 alone will not tell you what those are.

Second — and this is the point most often missed — an ISO 13485 certificate is not accepted in lieu of an FDA inspection. FDA has been explicit about this. Certification proves a notified body or registrar assessed you. It does not give FDA its own basis for confidence.

Third, an MDSAP audit report is different. FDA accepts MDSAP reports as a substitute for routine surveillance inspections [6, 7]. The exceptions matter: for-cause inspections, compliance follow-up, and PMA pre-approval inspections are unaffected [7]. If you already hold MDSAP, you hold something FDA acts on. If you hold only ISO 13485, you don't.

That distinction — ISO 13485 certificate versus MDSAP report — is the single most valuable thing on this page for most CE-marked manufacturers, and it is routinely blurred in general comparison content.

Clinical data: what 21 CFR 812.28 actually requires

Most Class II devices going through 510(k) never need clinical data. If yours does, the rules for foreign data are specific and worth reading closely.

FDA will accept information from a clinical investigation conducted outside the United States if the investigation was well-designed and well-conducted and specific conditions are met [4]:

A statement that the investigation was conducted in accordance with good clinical practice, where GCP includes review and approval by an independent ethics committee and informed consent from subjects [5]
Supporting information as specified in 812.28(b) is provided
FDA is able to validate the data through an onsite inspection or other appropriate means, if it deems that necessary [4]

The GCP requirement applies to investigations that began on or after 21 February 2019 [5]. Older studies sit under different expectations.

Two things manufacturers consistently get wrong here.

Data quality is necessary but not sufficient. FDA has stated that beyond quality and integrity, the applicability of the investigation to the US population and to US medical practice must also be considered [8]. A study run entirely in one European country, in a care pathway that differs from US practice, can be methodologically impeccable and still draw questions on generalisability. That is not a data problem you can fix retrospectively.

Non-conforming data is not automatically dead. Under 812.28(e), FDA may still accept data from investigations that do not meet the paragraph (a) conditions, if it believes the data and results are credible and accurate and that subjects' rights, safety and well-being were adequately protected [4]. This is a real avenue. It is not a comfortable one to rely on by default.

The gap with no European equivalent: substantial equivalence

This is where CE-marked teams lose the most time, and it is structural rather than procedural.

Under EU MDR you demonstrate conformity with the General Safety and Performance Requirements and make a risk-benefit determination. It is an absolute argument about your device.

A 510(k) is a comparative argument. Under section 513(i) of the FD&C Act you must demonstrate substantial equivalence to a legally marketed predicate device: same intended use, and either the same technological characteristics or different characteristics that do not raise different questions of safety and effectiveness.

Nothing in your EU technical documentation is organised to make that argument. You have no predicate. You have no comparison table. You have no discussion of technological differences framed against a specific cleared device. Your CER argues your device is safe and performs; FDA asks whether it is equivalent to something already cleared.

Three consequences worth planning around:

Predicate selection is a strategic decision made early, not a formality. The predicate you pick determines your testing scope, your comparison framework, and often whether 510(k) is the right pathway at all. See our guide to choosing a predicate device.
Your EU indication may not survive translation. Indications for Use is a controlled statement with legal consequences at FDA. A broad European intended purpose frequently has to be narrowed to match an available predicate — or you accept a harder pathway.
If no adequate predicate exists, 510(k) is not your pathway. That points to De Novo. Our 510(k) vs De Novo vs PMA breakdown covers the decision.

Labelling and IFU: the rework nobody budgets

Your EU labelling was built to MDR Annex I Chapter III. FDA labelling requirements live in 21 CFR Part 801, with device-specific requirements layered on. Expect rework on:

Indications for Use as a standalone controlled document
US-specific warnings and precautions
Symbols usage, and whether a symbols glossary is required
Prescription-device statements
UDI under a different system from EUDAMED

None of this is intellectually hard. It takes longer than teams expect because inconsistencies between labelling, Indications for Use, and device description become highly visible during review.

Sequencing: what to do, in what order

A practical order of operations for a CE-marked manufacturer entering the US.

1. Confirm classification and pathway first. US classification is by product code and 21 CFR regulation, and does not map cleanly from EU class. A Class IIa device in Europe may be Class II in the US, or exempt, or something else entirely. Everything downstream depends on this answer.

2. Identify candidate predicates before you scope anything else. Testing scope follows the predicate, not the other way round.

3. Gap-analyse your existing evidence against the predicate's requirements. This is the step that converts your EU file from "documents" into "budget". You are asking, standard by standard: do I have this, is it the right version, does it cover the right endpoints, and does it apply to my final finished device?

4. Fill the gaps. Where testing is missing or the standard version is outdated, you engage the laboratory directly and integrate the results.

5. Build the substantial equivalence argument and assemble eSTAR.

6. Register your establishment and appoint a US Agent — before you commercially distribute, not before clearance. These are frequently confused and the sequencing error costs money. Establishment registration and US Agent designation are conditions of US commercial distribution, not prerequisites for a 510(k) decision. See our US Agent requirements guide.

Step 3 is where most of the pain sits. Mapping an EU technical file against a predicate's requirements means cross-referencing 510(k) summaries, recognised consensus standards, product-code-specific guidance and your own test reports — repeatedly, for every standard in scope. Complizen was built for that specific step: the platform indexes FDA's databases and guidance so the mapping is traceable to sources, and regulatory experts with direct FDA submission experience review the output before it goes anywhere near a submission.

What it costs at FDA in FY2027

These are the FDA fees. They are published, fixed, and the same for everyone — they are also usually the smallest line in an international manufacturer's US budget, well behind testing and internal time.

FY2027 rates apply from 1 October 2026 through 30 September 2027 [3]:

Submission	Standard fee	Small business fee
510(k) premarket notification	$28,653	$7,163
De Novo classification request	$191,020	$47,755
Premarket application (PMA)	$636,732	$159,183
513(g) classification request	$8,596	$4,298
Annual establishment registration	$13,785	$13,785

Four things to note, because each one catches foreign manufacturers specifically.

Small business status is worth 75% off the 510(k) fee. The threshold is gross receipts or sales of no more than $100 million for your most recent tax year, including affiliates [3].

Foreign businesses qualify differently. You cannot file a US tax return, so FDA requires a National Taxing Authority Certification — completed by, and bearing the official seal of, your country's national tax authority, showing gross receipts in both local currency and US dollars, with the exchange rate used and the collection dates [3]. This takes time to obtain and is a common source of delay.

Apply at least 60 days before the fee is due — and do not submit early. If you file your application before FDA has determined that you qualify, you must pay the full standard fee, and FDA states it will not refund the difference if you qualify later [3, 10]. If you want the reduced fee, wait for your Small Business Decision number before submitting [10]. This is the most expensive avoidable mistake in the entire fee process.

If your country has no national taxing authority, FDA will consider alternative evidence of gross receipts — end-of-year financial statements or shareholder reports, reviewed case by case [10].

Small business status expires annually. FY2026 qualification expires at close of business on 30 September 2026; you must re-qualify for FY2027 [3].

Note also that the establishment registration fee has no small business reduction. A hardship waiver exists but is discretionary and narrow [3].

Common mistakes

Assuming the notified body's assessment carries weight. It carries none. Every conclusion has to be re-argued in FDA's terms.

Submitting the Clinical Evaluation Report as clinical evidence. A CER is a European regulatory argument. The underlying data may be usable; the document is not a 510(k) deliverable.

Treating ISO 13485 certification as inspection cover. It is not accepted in lieu of an FDA inspection. MDSAP is a different matter [6, 7].

Registering the establishment before clearance because it seems logical. Registration and US Agent designation are distribution requirements, not submission requirements. Registering early starts an annual fee clock for no benefit.

Carrying the EU intended purpose across unchanged. Indications for Use has to be defensible against a specific predicate. Broad European wording frequently has to narrow.

Frequently asked questions

Does CE Mark help with FDA approval? Not as a credential — a CE Mark has no legal standing at FDA and does not shorten or substitute for any part of the process. It helps as a body of evidence. Your ISO 13485 quality system, biocompatibility and electrical safety testing, and software lifecycle documentation are often reusable. Your notified body certificate, Clinical Evaluation Report, and EU risk-benefit determination are not. FDA also grants clearance via 510(k) rather than approval, which is the PMA pathway.

Is FDA clearance the same as FDA approval? No, and the distinction is legally meaningful. Clearance is the outcome of a 510(k) premarket notification, based on demonstrating substantial equivalence to a legally marketed predicate. Approval is the outcome of a Premarket Approval application, which applies to Class III devices and requires a demonstration of safety and effectiveness in its own right. Most Class II devices are cleared, not approved. Describing a cleared device as "FDA approved" in marketing material is a compliance risk.

Does my ISO 13485 certificate satisfy FDA quality system requirements? The QMSR incorporates ISO 13485:2016 by reference as of 2 February 2026, so your system substantially aligns with what FDA expects [1]. But the certificate itself is not accepted in lieu of an FDA inspection, and the QMSR retains US-specific requirements layered on top of the standard. Alignment is not the same as automatic compliance.

Will FDA accept clinical data from a European study? It can, under 21 CFR 812.28. The investigation must be well-designed and well-conducted, conducted in accordance with good clinical practice including independent ethics committee approval and informed consent, and FDA must be able to validate the data if it chooses to [4, 5]. Separately, FDA considers whether the study is applicable to the US population and US medical practice [8].

What is MDSAP worth at FDA? More than ISO 13485 alone. FDA accepts MDSAP audit reports as a substitute for routine surveillance inspections [6, 7]. For-cause inspections, compliance follow-up inspections, and PMA pre-approval inspections are not covered [7]. If you sell into Canada you likely already hold MDSAP, since it is mandatory there for most classes.

Do I need a US Agent before I submit my 510(k)? No. A US Agent and establishment registration are required before you commercially distribute in the United States, not before you submit or before you receive clearance. Confusing the two leads teams to register early and pay an annual fee before they have anything to sell.

Can I use my EU intended purpose as my Indications for Use? Sometimes, but do not assume it. Indications for Use must be supportable against your chosen predicate. European intended purpose statements are often broader than the cleared indication of any available predicate, in which case narrowing is required — or the device needs a different pathway.

How much are FDA fees for a CE-marked manufacturer? The same as for anyone else. In FY2027 a 510(k) is $28,653, or $7,163 with small business status, plus a $13,785 annual establishment registration fee [3]. Foreign manufacturers qualify for small business status via a National Taxing Authority Certification rather than a US tax return, and must apply at least 60 days before the fee is due [3].

Does a CE-marked device need to repeat biocompatibility testing? Often not, if the testing was performed to the ISO 10993 series on the final finished device, the standard versions FDA currently recognises were used, and the endpoints match what the predicate and product code require. Gaps typically arise from outdated standard versions, testing on materials rather than finished devices, or endpoint coverage that satisfied a notified body but not the relevant FDA guidance.

What is the biggest hidden cost in going from CE Mark to 510(k)? Rebuilding arguments rather than repeating tests. Substantial equivalence, Indications for Use, and labelling all have to be constructed fresh against a US predicate, because nothing in an EU technical file is organised to make a comparative argument. Teams budget for testing and underestimate this.

Key takeaways

A CE Mark is evidence, not status. FDA gives it no legal weight, but the underlying test data in your technical file is frequently reusable — which is a real advantage over a first-time filer, just not the one on the certificate.

QMSR closed the quality system gap, but not completely. Since 2 February 2026, Part 820 incorporates ISO 13485:2016 by reference [1]. US-specific requirements remain layered on top, and an ISO 13485 certificate is still not accepted in lieu of an FDA inspection.

MDSAP is the credential FDA acts on. MDSAP audit reports substitute for routine surveillance inspections, with defined exceptions [6, 7]. This is the sharpest practical difference between the two certifications you might hold.

Substantial equivalence has no European analogue. Your CER argues absolute safety and performance; a 510(k) argues comparison to a predicate. That argument has to be built from scratch, and predicate choice drives everything downstream.

Sequence registration correctly. Establishment registration and US Agent designation are conditions of commercial distribution, not of clearance. Getting this backwards costs an annual fee for no benefit.

Working out which parts of your technical file transfer is a strategy question, and it is cheaper to answer before you start testing than after. Complizen's regulatory strategy engagement maps your device to a pathway, a product code, and a predicate shortlist, with a senior FDA expert reviewing every section. See how the strategy service works →

References

FDA — Quality Management System Regulation (QMSR). https://www.fda.gov/medical-devices/postmarket-requirements-devices/quality-management-system-regulation-qmsr
FDA — Quality Management System Regulation: Frequently Asked Questions. https://www.fda.gov/medical-devices/quality-management-system-regulation-qmsr/quality-management-system-regulation-frequently-asked-questions
Federal Register — Medical Device User Fee Rates for Fiscal Year 2027 (91 FR 48134, 30 July 2026). https://www.federalregister.gov/documents/2026/07/30/2026-15335/medical-device-user-fee-rates-for-fiscal-year-2027
eCFR — 21 CFR 812.28, Acceptance of data from clinical investigations conducted outside the United States. https://www.ecfr.gov/current/title-21/chapter-I/subchapter-H/part-812/subpart-B/section-812.28
FDA — Acceptance of Data from Clinical Investigations for Medical Devices. https://www.fda.gov/medical-devices/investigational-device-exemption-ide/acceptance-data-clinical-investigations-medical-devices
FDA — Medical Device Single Audit Program (MDSAP). https://www.fda.gov/medical-devices/cdrh-international-affairs/medical-device-single-audit-program-mdsap
FDA — Third-Party Inspection (Devices). https://www.fda.gov/medical-devices/postmarket-requirements-devices/third-party-inspection-devices
Federal Register — Human Subject Protection; Acceptance of Data From Clinical Investigations for Medical Devices (final rule, 21 February 2018). https://www.federalregister.gov/documents/2018/02/21/2018-03244/human-subject-protection-acceptance-of-data-from-clinical-investigations-for-medical-devices
FDA — Medical Device User Fee Amendments (MDUFA): Fees. https://www.fda.gov/industry/fda-user-fee-programs/medical-device-user-fee-amendments-mdufa-fees
FDA — Reduced or Waived Medical Device User Fees: Small Business Determination (SBD) Program. https://www.fda.gov/medical-devices/premarket-submissions-selecting-and-preparing-correct-submission/reduced-or-waived-medical-device-user-fees-small-business-determination-sbd-program
FDA — Device Registration and Listing. https://www.fda.gov/medical-devices/how-study-and-market-your-device/device-registration-and-listing
Federal Register — Medical Devices; Quality Management System Regulation Technical Amendments. https://www.federalregister.gov/documents/2025/12/04/2025-21955/medical-devices-quality-management-system-regulation-technical-amendments

Does CE Mark Help With FDA Approval? What Transfers to a 510(k) and What Doesn't