IPC-1752A: Materials Declaration Management

Overview#

IPC-1752A is the electronics industry's common machine-readable form. A supplier uses it to tell a customer what substances and materials are inside a part.

Why it exists#

Manufacturers must prove products meet rules like RoHS and REACH, which requires composition data from every supplier. IPC-1752A defines one structured format everyone can produce and consume, so data flows up the chain and tools can validate it automatically.

How the data flows#

A declaration turns scattered supplier knowledge into a validated file the customer can act on. The same pattern works for electronics, articles, or conflict minerals.

Key concepts#

• Requester / Supplier. Data flows from the supplier, who knows the composition, to the requester, who needs it.

• Two form types.

  1. A substance / compliance declaration reports compliance to lists like RoHS, REACH SVHC and JIG, plus which listed substances are present.
  2. A Full Material Declaration (FMD) gives a complete breakdown down to the homogeneous material level.

• Declaration classes (Class A to D). Disclosure increases with the class:

  • Class A — a compliance query and reply: does the part meet a defined list of questions (RoHS, REACH and the like)?
  • Class B — the amount of each material grouping in the product.
  • Class C — a product-level composition summary, declared against lists such as JIG-101 and the REACH SVHC list.
  • Class D — a full material declaration down to the homogeneous material level.

  (Older IPC-1752 used a numeric Class 1 to 6 scheme; current IPC-1752A uses A to D.)

Data format#

• It is XML-based, with a published schema for automatic validation.
• It was originally delivered as an Adobe PDF form with embedded XML. Modern platforms generate and ingest the XML directly.
• It carries substance identities by CAS number, mass or percentage, regulatory lists, and exemptions claimed.

What the XML looks like#

A trimmed Class D (full materials) declaration. Tap a highlighted line to see what each element carries.

<?xml version="1.0" encoding="UTF-8"?>

<IPC1752 xmlns="http://webstds.ipc.org/175x/2.0">

  <Header documentID="DOC-00123" version="2.0">

    <Requester>

      <Company name="Acme Electronics Inc." uniqueID="000000000" uniqueIDType="DUNS"/>

    </Requester>

    <Supplier>

      <Company name="Component Maker GmbH" uniqueID="000000001" uniqueIDType="DUNS"/>

      <Authority name="A. Engineer" title="Compliance Mgr" date="2026-05-01"/>

    </Supplier>

  </Header>

  <ProductInfo>

    <Item itemNumber="IC-555-SOIC8" itemName="Timer IC, SOIC-8"

          mass="78.0" massUnitOfMeasure="mg"/>

  </ProductInfo>

  <MaterialInfo>

    <SubSectional name="D">

      <HomogeneousMaterial name="Molding compound" mass="55.0" massUnitOfMeasure="mg">

        <Substance level="I" category="Lead and lead compounds"

                   name="Lead" issuingAuthority="CAS" substanceID="7439-92-1"

                   substanceMass="0.0050" substanceMassUnitOfMeasure="mg"

                   concentration="0.0091"/>

      </HomogeneousMaterial>

    </SubSectional>

  </MaterialInfo>

</IPC1752>

How it relates to other standards#

• It is part of the IPC-175x family. IPC-1754 extends the same approach to aerospace, defense and other articles.
• It can declare against the IEC 62474 Declarable Substance List, which harmonizes what must be reported.

Note: This is an educational summary maintained by the Pareo team. Confirm class definitions, field names and version differences against the official published standard.