A supplier file can name a product, article, chemical, mixture, site, quantity, study, date, lot, invoice, or shipment. It can also omit a relationship that a buyer needs to locate. A buyer needs a way to retain those sources without making the source sheet do work that belongs elsewhere. China supplier PFAS reporting evidence is a factual source map that links a buyer product or article to supplier documents, their visible dates, stated relationships, and open conditions. It does not decide chemical identity, PFAS scope, reporting status, whether information is known or reasonably ascertainable, compliance, health or environmental effects, importer role, import, sale, or release.
Start with the evidence boundary
A source map should identify who issued a document, what it names, when it was issued or received, and which buyer product, supplier product, or shipment it explicitly identifies. It should also make missing links visible. If a supplier declaration names a material but not a buyer version, write that limitation. If an invoice names a product and quantity but not a lot, preserve the invoice and state that the lot relationship is not identified in that source.
Do not turn a supplier declaration into a chemical finding. Do not turn an analytical report into a scope finding. Do not turn a company name on a freight document into an importer determination. These may be matters for technical, regulatory, legal, importer, quality, or commercial functions. The evidence sheet is a factual filing structure, not a decision record.
| Review subject | Source can state | Source does not decide |
|---|---|---|
| Buyer product or article | Buyer-controlled item and revision | Chemical composition or PFAS scope |
| Supplier material source | Supplier-stated name or code | Chemical identity or classification |
| Site or entity source | Name and address as shown | Manufacturer or importer status |
| Quantity or shipment source | Stated amount, lot, invoice, or movement | Reporting content, timing, or compliance |
| Study or declaration | Source title, date, and stated text | Health, environmental, or safety outcome |
Use EPA and eCFR pages as dated context
EPA identifies TSCA section 8(a)(7), 40 CFR Part 705, and related rule materials on its PFAS reporting and recordkeeping page.1 The page describes reporting and recordkeeping requirements and summarizes rule history. A buyer can preserve the page title, URL, access date, and quoted source scope. The buyer should not convert that record into a conclusion about what a supplier, importer, or buyer must report.
EPA’s April 2026 update states that the start of the reporting period moved to 60 days after the effective date of the agency’s forthcoming revision to the rule.2 That is dated agency information. In a source map, retain the publication date and the page text. Do not calculate a deadline, infer a current effective date, or decide whether the update applies to a specific product, article, supplier, or transaction.
The current Part 705 table of contents includes provisions on scope, definitions, substances, persons, activities, report information, article importer options, timing, recordkeeping, confidentiality, and electronic reporting.3 A buyer can use these headings to name source folders or fields. The record should not decide whether a substance or article falls under a term in the regulation, whether an activity is excluded, who is a reporting person, or what information is available to a particular party.
Give each supplier record a narrow purpose
Start each document row with its original purpose. A product specification may identify a supplier item and its revision. A bill of materials may list components. An invoice can identify a commercial transaction. A test report may state a sample label, date, and reported result. A safety data sheet can contain supplier-provided wording. A facility record can identify a company or location. None of these records is interchangeable.
When a buyer receives several documents with similar material names, retain the exact names rather than harmonizing them by assumption. A buyer SKU may differ from a supplier SKU. A commercial trade name may differ from a test sample name. A quantity on an invoice may differ from a quantity in a supplier declaration. The source map should display the difference, not erase it.
Preserve document dates and versions
Each source should carry an original issue date, revision date, received date, or capture date, whichever the source actually provides. Record the date type rather than relabeling it. A date shown on a supplier test report is not automatically the date of a shipment, a manufacturing lot, or a buyer review. A date on an invoice does not automatically establish material production timing.
Version control prevents old and new supplier declarations from being combined into one unsupported statement. Keep source files separately, record their version labels, and link a document to a buyer product revision only where the document states the connection. The result is an evidence map that lets a responsible owner see the source trail without treating it as a compliance answer.
Map product and article sources separately
The Part 705 source page uses defined terms within a stated regulatory context.3 A buyer source map can retain an item as a product, a supplier-described article, or another commercial description. It must not decide that a thing is an article for a particular rule. Store the supplier document that uses the term, identify its document date, and record the wording as shown.
A useful map begins with the buyer product/version and then links the supplier product source only when an identifier appears in both records or a source states the link. Link the supplier product source to a bill of materials, component record, sample record, packaging record, lot record, or shipment record only when the relationship is stated. A shared product name does not create a reliable association by itself.
| Association | Documents to retain | Gap to state |
|---|---|---|
| Buyer product to supplier item | Buyer SKU and supplier item source | Version or part-number link is absent |
| Supplier item to component | Item record and component source | Material relation is not stated |
| Product to article wording | Product description and article source | Regulatory meaning is not decided |
| Product to lot or shipment | Product, lot, invoice, and shipment sources | Lot or transaction relation is absent |
Keep chemical and mixture terms source-bound
A supplier may use a chemical name, trade name, CAS number, material code, concentration range, ingredient list, composition statement, or test-sample identifier. Enter the exact text, file name, date, and supplier entity. Do not rename a substance, identify an unlisted substance, calculate a mixture result, or decide whether a record describes a PFAS.
Part 705 includes terms and reporting provisions for its own stated purposes.3 The presence of a supplier material statement does not determine whether a component is within the part’s scope. The absence of a name in a file also does not establish that a substance is absent. The evidence record simply identifies the source and the stated or missing field.
The buyer source map can include a column for “supplier chemical wording” and another for “buyer owner.” That design keeps a supplier’s wording beside the original source while allowing the responsible technical or regulatory function to make any separate assessment it controls.
Record site, entity, and importer-related sources as stated
Supplier factory records, company registrations, export documents, invoices, purchase orders, and freight records can name entities and locations. Retain the exact legal name, address, role wording, document date, and transaction reference. Do not treat an address as proof of manufacturing, a named party as an importer, or a freight record as a determination of import status.
An entity can appear in different ways across sources. The supplier may be named on a quotation, a factory on a product record, and another party on a shipping document. The evidence map should show which source uses which name. When the relationship between those entities is not stated, flag the gap instead of filling it with an assumption.
Record quantities, uses, studies, exposure, and disposal sources without analysis
EPA describes information categories in its TSCA section 8(a)(7) materials, including uses, volumes, byproducts, environmental and health effects, exposure, and disposal.1 A buyer can retain a source that uses these words or contains related data. The buyer should not calculate a reportable amount, decide whether a data point is known or reasonably ascertainable, characterize a byproduct, interpret a study, assess an exposure, or judge a disposal practice.
A quantity may be stated in an invoice, commercial record, production sheet, packing list, or supplier declaration. Keep its unit, date, product description, and stated transaction context. A study may have a title, test material name, issue date, laboratory name, and stated observations. Keep the original document or link and state whether it names the buyer product, supplier item, lot, or component. The source map does not evaluate the study or turn its presence into a health, environmental, or safety outcome.
| Source category | Factual fields to record | Boundary |
|---|---|---|
| Quantity source | Value, unit, date, item, and transaction wording | Does not establish reporting volume |
| Use source | Supplier-stated application or function | Does not determine use category |
| Byproduct source | Exact source wording and date | Does not characterize the material |
| Study source | Title, sample name, issuer, and date | Does not interpret health or environmental effects |
| Exposure source | Source reference and stated context | Does not assess exposure or hazard |
| Disposal source | Source-stated route or description | Does not determine disposal compliance |
Treat lot and shipment sources as traceability records
A batch or lot source can identify a supplier-stated production run, item, date, or factory. A packing list, bill of lading, carrier record, invoice, or purchase order can identify a stated shipment or transaction. Preserve the sources separately because they may apply to different products, quantities, dates, or movements.
Do not use a lot number to declare a material’s identity or status. Do not use a shipping reference to decide whether a product may be imported, sold, disposed of, or released. The evidence map can show that a supplier source names a lot and an invoice source names a shipment. It cannot decide that they refer to the same material unless a source makes that relationship explicit.
Ask for records, not legal or technical conclusions
A factual supplier request can ask for product and article sources, composition or material wording, entity and facility sources, stated uses, quantity records, byproduct descriptions, studies, exposure or disposal sources, lots, invoices, shipments, version history, and contacts who can clarify a document. Request original documents or controlled copies with visible dates.
Do not ask the supplier to decide whether a substance is PFAS, whether a product is in scope, who must report, which information is known or reasonably ascertainable, whether a report is complete, whether a deadline applies, or whether a product complies with any requirement. Those questions seek a decision rather than a source and belong in separate controlled work.
Create a stated-relationship map
A stated-relationship map is a short table that points from one source to another without adding a conclusion. It can show that a supplier product specification names component C-04, that a material declaration names supplier item I-11, or that an invoice names shipment S-08. It should then state whether the files themselves identify a shared buyer product/version, lot, quantity, component, or transaction.
This type of map is useful because it distinguishes a visible source link from a presumed link. It does not create chemical, reporting, importer, or compliance conclusions. The buyer retains the original source documents so a responsible owner can see the basis for each entry.
| Map entry | Source-based statement | Open condition |
|---|---|---|
| Product to material document | Specification P-02 names supplier item I-11 | Buyer revision is not named |
| Material to lot source | Declaration D-04 names component C-04 | Lot is not identified |
| Lot to shipment source | Packing list L-06 names shipment S-08 | Material relation is not stated |
| Site to entity source | Factory source F-03 names location X | Commercial role is not stated |
| Study to component source | Study T-09 names sample M-01 | Sample-to-product relation is absent |
Write gaps as facts
A source gap should name the document and the information it does not contain. “Material declaration D-04 names supplier item I-11 but does not name buyer version V-03 or lot L-06” is clear. “Supplier has no PFAS information” is not clear because it assumes a scope and information standard that the source map does not decide.
The same approach applies to conflicting wording. A buyer may record that an invoice uses one product code and a declaration uses another. The record should not decide which code is correct. It should retain both files, state the difference, and name a responsible owner for a separate clarification or decision.
Keep decision records separate
A product or regulatory owner may need to assess a matter that sits outside the evidence map. The map provides source identifiers, visible data, dates, relationships, and gaps. It does not become the place where a buyer decides scope, reporting, recordkeeping, legal position, product status, importer status, import outcome, sale, or release.
EPA’s pages and Part 705 provide primary-source context.1 3 A buyer can cite those sources and retain dated copies. The buyer should not apply an EPA statement to a particular supplier file unless the qualified owner makes and records that separate assessment. The supplier-source record stays factual when a buyer preserves this boundary.
Use a compact source sheet
A compact sheet gives each file one row and places the decision boundary beside the source. It should be simple enough that a buyer can locate an original document later and narrow enough that no field invites an unsupported conclusion.
| Field | Example factual entry |
|---|---|
| Buyer product/version | Buyer SKU and controlled revision |
| Supplier product or article source | Supplier item name and original document |
| Chemical or mixture wording | Exact supplier text and source date |
| Entity or site source | Name and address as stated |
| Quantity, use, or study source | Source title, date, and stated field |
| Lot, invoice, or shipment source | Exact identifier and transaction reference |
| Stated relationship | Link only where a source states it |
| Gap or conflict | Missing field or differing wording |
| Buyer owner | Function responsible for a separate decision |
Hand off source records precisely
A handoff should include the buyer product/version, supplier entity, document title, source date, stated relationship, and open condition. Avoid summaries such as “PFAS reporting review needed.” A precise handoff would say that a supplier declaration names a component and date but does not name the buyer version, lot, shipment, or a link to another named source.
The receiving owner can then use the original evidence in the appropriate controlled process. The buyer’s source map should not predict the outcome. It should make the evidence trail easier to retrieve and keep the supplier relationship transparent.
Common source-control errors
Do not merge files from different product versions because the material name looks similar. Do not label a supplier declaration as a reporting result. Do not treat a missing source as proof that information does not exist. Do not read an EPA rule update as a deadline instruction for an individual buyer. EPA’s April 2026 update must remain tied to its page and stated date.2
Do not replace original source wording with a more confident summary. A term may have a defined meaning in Part 705, but a buyer source map is not the place to decide that the definition applies. File the original source, record its date and wording, identify any expressed relationship, and preserve the open condition.
Frequently asked questions
What is China supplier PFAS reporting evidence?
It is a buyer-side source map for supplier documents about products, articles, materials, sites, quantities, studies, dates, lots, invoices, and shipments. It preserves what each source states and any missing link. It does not decide PFAS status, reporting applicability, chemical identity, data availability, compliance, environmental or health effects, importer status, import, sale, or release.
Can a supplier declaration decide PFAS scope?
No. A declaration may identify supplier wording, an item, a material, a date, or a stated relationship. It does not decide PFAS classification, regulatory scope, an exception, reporting status, or an associated commercial result. Retain the original source and route any separate assessment to its responsible owner.
How should a buyer record an EPA deadline update?
Record the EPA page title, URL, published date, access date, and the wording it states. The April 2026 EPA update describes a changed reporting-period start tied to the effective date of a forthcoming revision.2 The buyer source map should not calculate dates or advise a supplier or buyer on timing.
Which source fields should be requested from a China supplier?
Request original product, article, material, chemical or mixture wording, entity, site, quantity, use, byproduct, study, exposure, disposal, lot, invoice, shipment, date, version, and stated-relationship sources. The supplier-source record should also identify what each source does not name. Keep requests factual and avoid asking the supplier for a classification, reporting, compliance, legal, import, sale, or release conclusion.
Preserve the source trail
A disciplined source map helps a buyer retrieve supplier files and see their stated links and gaps. It does not resolve a chemical, regulatory, environmental, health, legal, importer, import, sale, or release question. Supplier Ally can help buyers organize China supplier communications, product and factory records, material sources, document versions, quality files, and shipment records. Qualified buyer functions should retain control over separate PFAS, reporting, technical, legal, product, importer, commercial, and release decisions.
ES 
EN 