V5 Ultimate
Guide

TSCA PFAS Section 8(a)(7) reporting readiness

EPA's PFAS reporting rule under TSCA §8(a)(7) (40 CFR Part 705) requires every US manufacturer or importer of per- and polyfluoroalkyl substances (PFAS) at any time between January 1, 2011 and December 31, 2022 to file a one-time retrospective report through EPA's CDX/CISS system. The reporting window opened July 11, 2025 and closes October 13, 2026 (small-manufacturer-of-PFAS-only article importers have an extra six months). There is no de minimis exemption and no volume threshold — even a single import of a PFAS-containing article triggers the obligation. This guide maps the rule and a defensible reporting path.

Start free trial Free trial, no credit card, onboard in days, not months.

Who must report — the broad scope

Anyone who manufactured (including imported) any PFAS, or any article containing PFAS, for any commercial purpose between January 1, 2011 and December 31, 2022 must report. The PFAS definition is structural — any substance with at least one fully fluorinated carbon meeting the definition at 40 CFR 705.3 — and currently captures ~1,462 substances on EPA's published list plus any other substance meeting the structural definition. Articles in scope: imported finished goods, components, packaging, lubricants, coatings, sealing tape, semiconductor wafers, textiles, cookware, medical devices, fluoropolymers. No de minimis, no volume threshold, no R&D exemption beyond the narrow research-and-development carve-out at §705.10.

Data elements per submission

For each PFAS and each reporting year (2011-2022), report: chemical identity (CASRN, EPA accession, or structural identifier for confidential/UVCB substances), categories of use (industrial processing, commercial product, consumer product, article import), production volumes by year, byproducts, environmental and health effects data 'known or reasonably ascertainable' (the §8(a) standard — diligent inquiry inside the company plus available external sources), worker exposure data, and disposal methods. Joint submissions are allowed: a supplier can submit identity/effects data confidentially with EPA and let downstream filers reference it by joint-submission number. Small manufacturer exemptions are narrow — only article importers below $12M annual revenue with PFAS-containing articles get a 6-month deadline extension, not a substantive exemption.

The deadline cliff and 'known or reasonably ascertainable'

Reporting window: July 11, 2025 to October 13, 2026 (April 13, 2027 for the small-article-importer subset). 'Known or reasonably ascertainable' is the §8(a) diligence standard — file knowledge of corporate management, technical staff, document control, plus reasonable inquiry of suppliers and review of publicly available information. It is not a forensic reconstruction obligation, but a thin file ('we asked once, supplier didn't reply') will not survive EPA challenge. Penalties under TSCA §16 are up to ~$53,000 per violation per day (adjusted annually for inflation), with each PFAS-year combination treated as a separate violation.

Confidential business information and joint submissions

Confidentiality claims must be substantiated under TSCA §14 (specific harm-from-disclosure justification, signed certification, redacted-and-unredacted versions). Generic 'confidential' claims fail. Joint submissions reduce burden: the primary submitter (often the PFAS manufacturer) files identity, effects, and exposure data; downstream importers reference the joint-submission number and only file their own production volumes and use categories. Cross-reference does not extinguish the importer's filing obligation — the importer still files a §705 submission, but with reduced content.

A 120-day TSCA §8(a)(7) readiness path

Days 1–20: scope determination (purchase, customs, R&D, and article-import records 2011-2022); PFAS-substance screen against EPA list and structural definition. Days 21–60: supplier outreach campaign for joint-submission numbers and §14 CBI alignment; gap-fill from SDS, technical data sheets, public literature. Days 61–90: per-year, per-substance reporting matrix build; internal review for 'known or reasonably ascertainable' completeness. Days 91–105: CDX/CISS account, registration, draft submissions. Days 106–120: senior management review, CBI substantiation, file via CDX before October 13, 2026.

Standards covered in this guide

Each standard, retailer code or assurance scheme referenced above has its own deep-dive page with scope, audit detail and common pitfalls.

Where this lives in V5 Ultimate

The clauses above aren't theoretical — every one maps to a shipped module and an industry profile. Jump to the parts of the product that turn this guide into evidence on a Monday morning.

Industries this hits hardest

Frequently asked

Are imported articles in scope?
Yes. Article importers are explicitly in scope under 40 CFR 705.10 — there is no article exemption. Coated metal, textiles, semiconductors, medical devices, cookware, packaging, and lubricants all commonly contain PFAS and pull importers into §8(a)(7) reporting.
Is there a volume or de minimis threshold?
No. A single instance of manufacture or import of any quantity of any PFAS between January 1, 2011 and December 31, 2022 triggers reporting. EPA explicitly declined to set a volume threshold.
What if our supplier won't tell us if the article contains PFAS?
Document the inquiry, the escalation, and the response (or non-response). 'Known or reasonably ascertainable' is a diligence standard — a documented good-faith supplier outreach with no positive PFAS confirmation supports a 'no report' position for that supplier. A thin or undocumented inquiry does not.
Can we claim our reported data confidential?
Yes, but only with substantiated §14 CBI claims — specific harm-from-disclosure justification, signed certification, and redacted-and-unredacted versions. Chemical identity confidentiality requires generic-name proposal and structural class disclosure.

See it on your shop floor.

Free trial, no credit card, onboard in days, not months.

Spot something off? .