
Minnesota's first PFAS product report is now behind most manufacturers. The harder challenge begins in 2027, when a second state โ New Mexico โ opens its own reporting system, Minnesota's annual cycle comes due, and a federal reporting window is scheduled to open. For compliance teams, the question is no longer "how do we file in one state," but "how do we report the same product data across several systems that don't talk to each other."
This guide maps what state PFAS reporting 2027 actually requires, by jurisdiction, and explains a practical operating model: collect and structure PFAS data once at the product level, then file it into each state's system. For a broader view of the obligations shaping this period, Certivo's PFAS framework overview tracks the regulations referenced below.
๐ Not sure which of your products trigger 2027 reporting? Book a free compliance risk assessment to map your PFAS exposure across states and product lines.
Why 2027 Is the Real Inflection Point
Through 2026, PFAS product reporting was effectively a single-state story centered on Minnesota. In 2027 it becomes a multi-jurisdiction, recurring obligation.
Three events converge:
New Mexico opens its first product reporting window, due January 1, 2027.
Minnesota shifts from a one-time initial report to an annual February 1 update.
The federal TSCA Section 8(a)(7) reporting window is scheduled to open, adding a parallel manufacturer/importer obligation.
The operational consequence is that the same underlying question โ which of our products contain intentionally added PFAS, and what's in them โ must now be answered in multiple formats, for multiple agencies, on different clocks. Teams that treated Minnesota as a one-off project will find the 2027 wave exposes the absence of a repeatable system.
New Mexico: The January 1, 2027 Reporting Deadline
New Mexico is the most significant new reporting requirement in 2027. It is built on the PFAS Protection Act (House Bill 212, 2025) and its implementing rule, 20.13.2 NMAC, administered by the New Mexico Environment Department (NMED).
What New Mexico Requires
Reporting: Manufacturers of products containing intentionally added PFAS sold, offered for sale, or distributed in New Mexico must report to NMED on or before January 1, 2027, through the New Mexico PFAS Reporting System (NMPRS).
Labeling: A PFAS label is required by January 1, 2027, applying to products manufactured after that date. New Mexico permits a label developed for another state where it satisfies New Mexico's intent, provided NMED is notified.
Phased bans: Prohibitions phase in across 2027 and 2028, building toward a broad ban on intentionally added PFAS by January 1, 2032, subject to limited exemptions and a Currently Unavoidable Use (CUU) pathway.
Fees: Reporting fees and late fees apply.
โ Scope reaches beyond New Mexico manufacturers. The obligation attaches to products sold into New Mexico, regardless of where they are made โ so an out-of-state manufacturer or a component supplier in the chain can be in scope.
For the definitive text and guidance, consult the New Mexico Environment Department directly, as rule details and FAQs continue to be updated.
Minnesota in 2027: From First Filing to Annual Cycle
Minnesota's Amara's Law (Minn. Stat. ยง 116.943) set the template, but its 2027 role is different from 2026.
The initial report was due September 15, 2026, after being moved twice from the original January 1, 2026 date. Manufacturers granted a one-time 90-day extension reported by December 14, 2026.
After the initial filing, Minnesota requires an annual report by February 1, making February 1, 2027 the next live Minnesota deadline.
A June 2026 amendment excluded products manufactured on or before July 1, 2023 from the reporting requirement, which narrowed scope for some manufacturers.
A proposed bill (HF4257/SF5092) could move the initial reporting date to July 1, 2027, but, based on currently available information, it remained in committee and should be treated as a proposal โ not a change in the law โ until enacted. Certivo's analysis of Minnesota's HF4257 proposal covers that bill in detail.
If your team is still assembling its Minnesota submission or preparing the annual update, the complete PRISM filing guide walks through the mechanics of the state's reporting portal.
Where Maine and Other States Fit
Maine is frequently grouped with Minnesota and New Mexico, but its reporting model is now different.
Maine repealed its broad "report every PFAS product" notification program. It retains reporting tied to Currently Unavoidable Use determinations and is moving toward a general prohibition on intentionally added PFAS by January 1, 2032, unless a CUU or statutory exemption applies.
Several states operate category-specific notification, registration, or labeling requirements rather than broad product reporting โ including Connecticut, Washington, California, Oregon, and Vermont. These are worth monitoring because they can pull specific product categories into scope on their own timelines.
For a full roadmap of how these state obligations interact, see Certivo's guide on tracking PFAS regulations across the U.S. and EU, which complements the broader 2026 state PFAS landscape overview.
The Federal Overlay: TSCA Section 8(a)(7)
State reporting does not replace the federal obligation. EPA's TSCA Section 8(a)(7) rule requires manufacturers and importers of PFAS (including PFAS in articles) to report on past activity.
Based on currently available regulatory guidance, the submission window is scheduled to open on January 31, 2027, or 60 days after a forthcoming final rule, whichever applies, covering PFAS manufactured or imported during 2011โ2022.
A scope revision affecting article importers and potential de minimis treatment has been under consideration, so the final applicability should be confirmed against EPA before relying on any exemption.
The practical point for executives: a manufacturer can face state product reporting (New Mexico, Minnesota) and a federal TSCA submission in the same quarter, drawing on overlapping โ but not identical โ data. Confirm the current federal position with the U.S. EPA.
Card summarizing state PFAS reporting 2027 deadlines for New Mexico, Minnesota, and TSCA
Click on image to view full
State PFAS Reporting at a Glance
The table below summarizes the active 2027 picture. Verify each requirement against the relevant authority before filing.
Jurisdiction | 2027 Obligation | System / Authority | Key Date |
|---|---|---|---|
New Mexico | First-time product reporting + labeling | NMPRS / NMED | January 1, 2027 |
Minnesota | Annual report (after Sept 2026 initial filing) | PRISM / MPCA | February 1, 2027 |
Maine | CUU-based reporting only (broad program repealed) | Maine DEP | Category-specific |
Federal (TSCA 8(a)(7)) | Manufacturer/importer reporting, 2011โ2022 activity | EPA | From January 31, 2027* |
*Or 60 days after the forthcoming final rule; confirm with EPA.
Card summarizing state PFAS reporting 2027 deadlines for New Mexico, Minnesota, and TSCA
Report Once, File Everywhere โ What It Really Means
The phrase is easy to misread. It does not mean a single submission legally satisfies every state. Minnesota's PRISM and New Mexico's NMPRS are separate systems, and โ based on currently available regulatory guidance โ it is not yet settled whether a Minnesota filing meets New Mexico's requirement. Treat them as distinct obligations.
What "report once" does mean is upstream of the filing:
โ Collect supplier and material data once, at the product and component level.
โ Structure it once into a normalized PFAS dataset tied to your bill of materials.
โ Map and format that dataset to each state's specific fields and system.
The data-gathering is the expensive, slow part. When it is done once and reused, each additional state filing becomes a formatting exercise rather than a fresh supply-chain campaign. This is where a centralized compliance data backbone changes the economics of multi-state reporting.
๐ Filing in two or three states this year? Book a compliance risk assessment to see how your existing PFAS data maps across New Mexico, Minnesota, and the states coming next.
The Data Problem Behind Every State Filing
Every state report ultimately asks the same hard questions, and manufacturers consistently hit the same obstacles:
โ Incomplete supplier responses โ suppliers return partial data, wrong formats, or nothing at all.
โ Intentionally added vs. present โ distinguishing intentionally added PFAS from trace presence requires component-level evidence, not blanket statements.
โ Scope churn โ amendments (such as Minnesota's July 1, 2023 manufacturing-date exclusion) change which products are in scope mid-cycle.
โ Documentation defensibility โ states expect records of the due-diligence effort, not just a submitted form.
Minnesota's own compliance standard illustrates the last point: a manufacturer is generally considered compliant if it provides all available PFAS data by the deadline and maintains records of its efforts to obtain additional supply-chain information. That makes automated supplier data collection and audit-ready documentation core to the filing, not afterthoughts. Certivo's work on PFAS supplier data collection for article importers addresses this collection bottleneck directly.
Building a Multi-State PFAS Reporting Workflow
A repeatable workflow turns the 2027 wave from a series of fire drills into a managed process:
Map products to jurisdictions. Identify which SKUs are sold into New Mexico, Minnesota, and other reporting states.
Run substance and threshold analysis at the BOM level. Flag intentionally added PFAS by component, using BOM-level compliance tracking.
Collect supplier evidence through self-service portals. Replace email chains with streamlined supplier documentation that validates responses on intake.
Normalize into one PFAS dataset. Store declarations, test reports, and certificates against each product.
Format to each state system. Generate the fields each agency requires from the single dataset.
Maintain audit-ready records. Preserve the due-diligence trail for each filing to stay audit-ready across frameworks.
This model also scales to the next obligations without a restart โ the same backbone supports multi-tier supply chain transparency as more states and product categories enter scope, an approach detailed in Certivo's guide to automating PFAS compliance across multi-tier supply chains.
Workflow for state PFAS reporting 2027 mapping one dataset to multiple state systems
Workflow for state PFAS reporting 2027 mapping one dataset to multiple state systems
Click on image to view full
How AI Reduces the Reporting Burden
Manual, spreadsheet-based reporting does not scale across states that report on different clocks. AI-native compliance automation addresses the two heaviest costs โ gathering data and keeping it current.
AI document parsing and certificate validation. Certivo's CORA intelligence extracts and validates PFAS data from supplier declarations, test reports, and certificates, flagging gaps at intake rather than during an audit.
BOM-level material mapping. CORA-driven analysis links substance data to specific components, so reporting is tied to products rather than blanket company statements.
Regulatory change monitoring. CORA's regulatory intelligence layer tracks amendments and new state deadlines, supporting continuous compliance monitoring instead of deadline-driven scrambles.
Positioned this way, Certivo acts as the system of record for PFAS reporting data and CORA as the embedded intelligence that keeps it current โ explored further across Certivo's product capabilities and its approach to managing compliance risk proactively.
Executive Takeaways
2027 is multi-state, not single-state. New Mexico (Jan 1), Minnesota (Feb 1 annual), and federal TSCA converge in one window.
New Mexico is the new first-time filing; Minnesota has moved to an annual cadence.
"Report once" is a data strategy, not a legal shortcut โ collect once, file into each system, and confirm whether any state accepts another's filing.
The bottleneck is supplier data and documentation defensibility, which is where automation delivers the most leverage.
Manufacturers that build a reusable PFAS data backbone now will absorb the 2027 wave โ and the states that follow โ without proportional increases in headcount or audit risk. That is the difference between reactive filing and continuous readiness, the core of effective state PFAS reporting 2027 preparation.
Ready to Map Your 2027 Exposure?
Certivo centralizes PFAS data at the product and BOM level, automates supplier collection, and keeps an audit-ready record for every filing โ so one dataset supports New Mexico, Minnesota, and the states coming next.
โก๏ธ Book a compliance risk assessment to understand your current PFAS reporting exposure across products and jurisdictions.
Kunal Chopra
Kunal Chopra is the CEO of Certivo, an AI-driven compliance management platform revolutionizing how manufacturers navigate regulatory challenges. With a career spanning over two decades, Kunal is a seasoned technology leader, 3x tech CEO, product innovator, and board member with a passion for driving transformative growth and innovation.
Before leading Certivo, Kunal spearheaded successful transformations at renowned companies like Beckett Collectibles, Kaspien, Amazon, and Microsoft. His strategic vision and operational excellence have led to achievements such as a 25x EBITDA valuation increase at Beckett Collectibles and a 450% shareholder return at Kaspien. He has a track record of turning challenges into opportunities, delivering operational efficiencies, and driving market expansions.


