Can a Test Report Be Transferred? A Transfer Map, Explained

Start with the conclusion: "a report can transfer" and "a certificate can transfer" are two different things. A report is the technical basis; a certificate is market access. In the majority of cases the only thing you can transfer is the report — the certificate is what does not move.

That sounds like wordplay, but it decides how your launch schedule and your budget are laid out. Take the same product: with a CE-RED report in hand, the UK market can be done by changing the standard references and issuing a UK DoC. But the CE certificate in your hand will not become a UK access document, however you phrase it. The reverse holds too: an FCC report can support Canada ISED, while the FCC certificate itself carries no effect in Canada.

One level further down, a transfer also falls into three tiers: "just change the documents", "add a few delta tests", "redo the whole set". A lot of projects fail precisely because a retest-tier route was scheduled as a document change — quoted as a conversion, actually requiring retesting, the timeline slips, and peak season is gone.

The table below compares the common routes, 11 of them, covering the UK, Canada, Australia, Saudi Arabia, Korea, China, the Philippines, Taiwan, India and Russia. The determinations come from the rules currently in force at each market's authority; actual execution is subject to the current requirements of the target country's authority.

The table carries only three time figures: 1-2 weeks, 3-6 weeks, and about 50%. These are verified orders of magnitude; for your specific product, an actual delta assessment still applies.

First separate report from certificate: one sells technology, the other sells access

A report is test evidence: sample, standard, test items, data, verdict, closing with a laboratory conclusion. Its value lies in "this data is real", which is why another market can take it as the basis for approval — provided that market recognises this standards system, this laboratory, and this batch of samples.

A certificate is an access conclusion: issued by the authority or a body it designates, bound to the applicant entity, the model and the critical components, and sometimes also to the factory and a validity period. Its value lies in "this market allows you to sell", so it inherently carries territoriality: move to another country and the issuing body no longer has jurisdiction.

Once the two are separated, a lot of confusion disappears:

• A CB certificate into China CCC: it can cut test cost and time by about 50%, but the CCC report must be issued by a CNCA-designated Chinese laboratory. CB gives you data and a basis for judgement, not an access conclusion.
• A CE-RED report into UK UKCA: the report can be converted directly, by changing the standard references to BS EN and then issuing a UK DoC. What transfers here is the technical file; the compliance act that lands is that DoC.
• A mainland CNAS report into Taiwan: not even the report layer holds — it must be issued by a locally recognised laboratory in Taiwan, and certificates are likewise not mutually recognised. This is one of the few cases where even the "technical basis" is not accepted.

Why some countries require local testing

When a market comes with a "retesting required" label, clients often ask: our report was issued by a CNAS laboratory and the data is sound, so why can't it be used?

Because this is not a technical question, it is a question of the access regime. Four reasons stack up:

One, the regulatory system is independent. Russia/EAEU has its own conformity assessment system, not attached to the EU or IEC mutual recognition framework, so reports have to be produced from inside that system. China SRRC works to Chinese standards, and some spurious emission limits are stricter than FCC or CE — the same data set simply does not line up when applied.

Two, laboratory accreditation is designated. India BIS requires testing to be completed at a BIS-recognised laboratory in India; Taiwan BSMI / NCC requires issuance by a locally recognised laboratory in Taiwan. This is not "we don't trust your data" — it is the regulatory chain requiring the testing act to happen inside its own traceable scope.

Three, the certificate holder has a residency requirement. Russia/EAC requires a certificate holder inside the EAEU. The Philippines NTC is comparatively relaxed: the certificate holder can be the applicant company itself — one region, two approaches, and the difference sits exactly on this rule.

Four, who owns the liability chain. When a report is accepted, the accepting party is endorsing that data. It will only endorse on the condition that the laboratory is inside its regulatory field of view and that someone can be found if something goes wrong.

So when you hit "local testing required", do not keep arguing at the technical level. Confirm three things first: the laboratory accreditation requirements of the target market, the entity requirements for the certificate holder, and whether the standard version matches your report. Only once those three line up is it time to discuss test items. For the related rules see the Taiwan BSMI/NCC knowledge base, the India BIS/WPC knowledge base and the Russia EAC knowledge base.

Why CB is treated as a "universal base document"

The IECEE CB scheme is a mutual recognition arrangement built on IEC standards: certification bodies in member countries recognise each other's test results. Its position is clear-cut: the universal base document for the safety part.

How much that base document saves depends on how the target market takes it:

Three points on using it, all of them learned the hard way in practice:

• CB covers safety, not EMC or RF. For products with Bluetooth or WiFi, CB does not solve the RF part of RED, nor FCC Part 15. Expecting one CB to carry every project is a common starting point for a broken schedule.
• The CB certificate must cover the specific model and critical components. Change the power supply, transformer, optocoupler or enclosure flame rating, and the original certificate's scope may no longer hold — you then need to assess whether retesting is required.
• CB is a "reduction", not an "exemption". Korea assesses the sufficiency of the report, China requires the report from a designated laboratory, and Saudi Arabia follows SABER platform rules. What you save is test volume, not compliance steps.

On the Korea route, read this alongside the KC knowledge base and our Korea KC certification service; for Saudi Arabia, see the SABER knowledge base.

Three transferable types: document changes, delta testing, regional recognition

The transferable cases, ordered by workload from lightest to heaviest, come roughly in these three types.

Type one: same standards system, different market — largely document changes

A CE-RED report into UK UKCA is this type. The technical standards share an origin, so the approach is to change the standard references to BS EN and then issue a UK DoC. The workload sits at the document layer: the standards list, the signing entity on the DoC, and the technical file archive.

But there is a one-way valve here: UKCA cannot be used in reverse for the EU. After Brexit the two systems run in parallel, and the EU does not recognise UKCA. A product that has done the UK market and then goes back to sell in the EU still has to follow the CE route. This gets asked a lot, and the answer is blunt: it cannot.

Type two: same technical origin, add delta testing

An FCC Part 15 report into Canada ISED belongs here — almost directly reusable, with Canada delta testing added, and roughly 1-2 weeks of incremental work. Both markets rest on a similar RF regulatory logic, and the differences concentrate in specific clauses: frequency bands, power limits, labelling and local representative requirements.

A CE report into Australia RCM has a similar structure, but note the layering: ACMA accepts CE reports, which handles the EMC and radio parts; the safety part runs through EESS and needs CB plus AS/NZS deltas. One CE report cannot settle both RCM tracks at once. The detail is in the RCM knowledge base.

Type three: regional recognition arrangements — the saving is in the process

An IECEE CB certificate into Saudi SABER is the typical case: accepted, substantially simplified, usually cut to 1-2 weeks. What you save is not test items but approval round-trips and repeated documentation.

A CE / FCC report into the Philippines NTC is also this type: usable, review takes about 3-6 weeks, and the certificate holder can be the applicant company. That is friendlier on entity arrangements — no need to route through a local agent holding the certificate.

Four types that do not transfer: stop re-arguing at the technical level

These four carry high communication cost and high rework rates, and their common thread is either "the report layer does not hold" or "the certificate must be issued locally".

Taiwan BSMI / NCC

A mainland CNAS report is not directly usable: it must be issued by a locally recognised laboratory in Taiwan, and certificates are not mutually recognised either. That means it is not a matter of adding a few test items — the testing act itself has to happen inside a locally recognised laboratory. When scheduling, count sample shipment, local testing and certification issuance as three separate blocks; do not estimate it as a "conversion". See the BSMI/NCC knowledge base.

India BIS

CE / FCC reports are not directly accepted; testing must be at a BIS-recognised laboratory in India. But there is an exception within the same country: WPC ETA can accept FCC / CE / ETSI reports. So India has to be split by product line — the BIS line retests, the WPC ETA line can build on the report. Quoting the two lines as one project is a common misjudgement. See the BIS/WPC knowledge base.

China SRRC

FCC / CE reports cannot be cited directly; SRRC works to Chinese standards, and some spurious emission limits are stricter. The same sample with enough margin on the FCC side may not have enough under SRRC limits, and remediation is routine. Budget for remediation and retest rounds inside the plan on these projects. See the CCC/SRRC knowledge base.

Russia EAC

A CE report cannot be transferred directly. Russia/EAEU has an independent conformity assessment system; testing is required at an EAEU-recognised laboratory, and an in-country EAEU certificate holder is required, subject in detail to current Russian regulations. On this route both conditions bite at once — the report and the certificate holder — and missing either one blocks the way. See the Russia EAC knowledge base.

The right order for a transfer: seven steps, and the wrong order wastes money

Order matters more than effort. I have seen far too many projects run the testing first, then discover the standard version was wrong or the certificate entity was wrong, and start over.

The inventory in step 2 is the step that is easiest to skip on the whole chain, and it directly shapes the conclusion. Pull out at least these five items:

• The standard numbers and version years cited in the report
• The issuing laboratory's name and accreditation scope (CNAS, CBTL, local recognition, etc.)
• The list of models covered by the report, and whether it matches the models on the packaging, nameplate and manual
• The critical component list: power supply, transformer, wireless module, antenna, battery
• The report issue date, and whether the product has had a board revision since

The word "written" in step 4 needs emphasis. A verbal "that should be fine" is recognised by nobody when a problem appears. Have the target market's body or laboratory issue a written confirmation stating which reports are accepted, which items must be added, and who issues the result — that document saves a great deal of explaining during a project review.

A few pitfalls that sink a project on first contact

Pitfall one: using a CE report directly as UKCA

No BS EN reference change, no UK DoC, just the CE certificate with a new cover page submitted. It fails at the document layer, and the moment review checks the standard references it shows. The conversion act itself is light, but it cannot be skipped.

Pitfall two: assuming UKCA can be converted back to CE

One-way valve. Do the UK, then return to the EU, and you go through CE again. If both markets are on the plan, build the base along the CE line from the start and then extend to UKCA — the cost structure is more sensible that way.

Pitfall three: treating CB as an all-purpose base document

CB is safety; it does not cover EMC or RF. For wireless products, CB solves only the safety block, while the RF part of RED and FCC Part 15 both still need separate arrangements.

Pitfall four: the report's standard version is already superseded

The report itself was genuinely issued, but the standard version it cites has been replaced. The target market reviews against the version in force, so an old-version report may be asked for supplementary testing or reissue. Put the version year in its own column during the inventory, rather than finding out at submission.

Pitfall five: models and critical components are not covered

The report names only the main model while the packaging shows five or six derivatives; or the power supply supplier changed and the critical component list in the report no longer matches. Both turn "transferable" into "supplementary testing required".

Pitfall six: ignoring the certificate holder and local representative

Russia/EAC requires a certificate holder inside the EAEU; the Philippines NTC allows the applicant company to be the holder. Both are "can the report be used" questions, yet with different entity arrangements the project structure is entirely different. Confirm this before quoting, not before issuing.

Pitfall seven: reading "report accepted" as "no local body involved"

Saudi Arabia accepts CB but still follows SABER platform rules; Australia's ACMA accepts CE reports but the safety part still needs CB plus AS/NZS deltas; China CCC can use CB to cut about 50% but the report must come from a CNCA-designated laboratory. What is accepted is the data, not the process.

How to plan for lower cost: test once, reuse across markets

Cost savings do not happen at the quotation negotiating table; they happen at product definition and test planning.

One, plan by standards family, not by country. List the target markets in full at product definition and find their standards intersection. Run safety along the IEC 62368-1 line and do CB first; lay out EMC and RF along the two main lines of CE-RED and FCC Part 15. With that base built, changing references for the UK, adding deltas for Canada, using CB simplification for Saudi Arabia and waiving the majority of safety testing in Korea all become additions on top of the same base document.

Two, delta testing before full redo. Where deltas can be added, do not retest everything. FCC into ISED at roughly 1-2 weeks of incremental work follows exactly this logic. Conversely, Taiwan, India BIS, China SRRC and Russia EAC simply do not offer a "delta" option — schedule the full test cycle honestly into the plan.

Three, count the rework cost. The test fee is only one line on the books. What is genuinely expensive is rework: board changes, retesting, rescheduling, missing the season. Getting the route right once saves more than price-shopping between laboratories.

Four, keep documents and hardware in step. Model, critical components, nameplate, manual and report — all five have to line up with each other. This costs nothing and blocks a large share of rejections.

For running several markets in parallel, see the certification services overview, EU CE/RED, USA FCC/UL and Saudi SABER lines, combined according to the product's actual configuration. If you have already done one market, first check customer cases for a structurally similar route.

The action checklist before a transfer — confirm each line, then discuss the quote:

Related reading: FCC ID or SDoC, CE self-declaration or notified body, the knowledge base overview and all articles. For product-side configurations see product solutions and Bluetooth earphones.