Test Report vs Type Approval: What Is the Difference?

Why the distinction matters

A PDF carrying a laboratory logo, an approval communication and a photograph of an E-mark are often collectively called a “certificate”. That shortcut hides the most important questions: who issued the document, what exactly was assessed, which type or family is covered, and what legal function the evidence performs.

In Vietnam, test reports, type-approval/certification documents, ECE/EC documentation, COP evidence and batch/quality documents can serve different purposes. A dossier may contain many files and still lack the evidence required for the specific regulatory route.

What to check

• Issuer and role: laboratory/technical service, approval authority, Vietnamese testing body or certification body.
• Object: one tested sample, a type/family, a production site or a shipment/batch.
• Regulatory scope: QCVN or UN Regulation, series of amendments, tests performed, variants, extensions and exclusions.
• Result: measured/pass-fail test result versus an approval/certification decision.
• Validity: issue date, amendment, extension, supersession or withdrawal status.
• Traceability: approval number, report number, part number, drawing revision, marking, manufacturer and plant.
• Applicant requirement: whether the document must be issued to the importer concerned.
• Procedural use in Vietnam: primary evidence, conditionally usable foreign evidence, supporting evidence or evidence requiring additional confirmation.

Regulatory basis

FACT

A test report and a type approval perform different functions. Under the UNECE framework, the approval authority issues the approval communication, the technical service conducts testing in accordance with the applicable UN Regulation, and the approval mark identifies the approval on the product where required by that Regulation.

LEGAL REQUIREMENT

Under Circular 55/2024/TT-BGTVT, Article 3 distinguishes test reports for vehicle safety, emissions, components and energy consumption; Article 4 addresses testing of representative samples; and Article 5 defines the certification dossier. Under Circular 54/2024/TT-BGTVT, Articles 3 and 10 and Annex XX distinguish component test reports, foreign test reports, confirmation by a testing body and quality certificates. These instruments must be read together with effective amendments. Applicable component QCVNs define type criteria, technical documentation, sample quantities and the testing body’s responsibility for preparing the test report.

Expert interpretation

The practical questions are different:

• Test report: “What specimen was tested, how, and with what result?”
• Type approval: “What type was approved, by whom, and within what scope?”
• Vietnam dossier: “Which evidence is admissible for this product and this procedure?”

A report may be narrower than an approval because it records specific samples or tests, while the approval may cover defined variants or extensions where the approval mechanism permits. Conversely, a technically detailed report does not itself create an approval decision. The review must trace the chain from the approval communication or certificate to the approval number, test report, annexes and drawings, and finally to the physical sample and its actual marking.

EXPERIENCE-BASED INSIGHT

LotusTSE does not stop at checking whether a test report or certificate is present. We review the complete traceability chain: physical product → type/family → technical characteristics → approval mark → test report → approval communication/certificate → intended scope of use in Vietnam. Mismatches in model/type, part number, drawing revision, factory, series of amendments, marking or scope are often more significant than a checklist that merely shows a file as available. LotusTSE commits only to deliverables within its control—such as an evidence register, inconsistency list and gap analysis—and does not guarantee the conclusion or processing time of any external authority or organization.

Common risks

• Using a report for a similar sample as evidence for the actual type.
• Ignoring the series of amendments or extension history.
• Failing to verify the approval authority/technical service or validity status.
• Confusing a shipment/quality certificate with a type approval.
• Losing traceability between report number, part number and drawing revision.

Recommended approach

1. Build an evidence register with issuer, role, document number, date, scope, product identity, regulatory route and validity.

2. Check bidirectional consistency between approval, report, annexes/drawings and the physical product.

3. Mark unresolved items as NEEDS VERIFICATION rather than inferring from file names.

4. Confirm the intended use of foreign evidence with the relevant testing body or certification authority, according to its role, before relying on that evidence as the primary or substitute document in a project.

Related LotusTSE services

Homologation dossier review; component certification support; UNECE evidence review; test planning and technical coordination.

Knowledge Graph

Related QCVN: QCVN 28, 32, 33, 34, 36, 78, 113, 125 and the applicable vehicle QCVN.

Related procedure: Circular 54/2024; Circular 55/2024; Circular 45/2026 and effective amendments.

Related Knowledge: P1 UNECE evidence in Vietnam; P3 E-mark; P10 report scope vs certification scope; P12 reading UNECE approval scope.

Structured-data recommendation: Article + DefinedTerm for Test Report, Type Approval, Approval Mark and COP.

NEEDS VERIFICATION

The exact approval communication or approval form, applicable series of amendments and extension, validity or withdrawal status, and intended scope of use must be verified for each UN Regulation and each project. The status of a specific approval must be checked against the relevant database or with the competent authority.