Minnesota PFAS reporting is now one of the most consequential product compliance obligations in the United States, and the clock is running. Under Amara's Law (Minn. Stat. § 116.943), any manufacturer that sells, offers for sale, or distributes products containing intentionally added PFAS in Minnesota must report those products to the Minnesota Pollution Control Agency (MPCA) through PRISM. Initial reports are due September 15, 2026. This guide explains the deadlines, the scope, the recent PRISM system enhancements, and the practical steps compliance teams should take now.

Book a compliance risk assessment to understand your PFAS exposure across products, components, and suppliers before the reporting deadline.

Key Takeaways

⏳ Initial Minnesota PFAS reporting is due September 15, 2026. Extension or waiver requests must be postmarked by August 16, 2026, and approved extensions push the deadline to December 14, 2026.

📌 Amara's Law (Minn. Stat. § 116.943) requires reporting of every product or component that contains intentionally added PFAS and is manufactured after July 1, 2023.

📊 Reporting is submitted through PRISM, the PFAS Reporting Information System for Manufacturers, with a one-time $800 fee per manufacturer and annual updates due each February 1.

🏭 The scope is broad, reaching electronics, automotive, aerospace, medical devices, appliances, textiles, packaging, and industrial equipment sold into Minnesota.

🔗 Supplier data is the bottleneck. MPCA accepts best-available data for the first cycle if manufacturers document good-faith due diligence and retain records for five years.

🤖 Manual PRISM preparation does not scale. Automated supplier data collection and AI document parsing are the practical route to a defensible, on-time submission.

What Minnesota's PFAS Reporting Requirement Covers

Amara's Law was enacted in May 2023 as Minnesota's PFAS pollution prevention statute. It has two functions: phased sales prohibitions on certain PFAS-containing products, and a broad reporting requirement that gives the state visibility into where intentionally added PFAS is used. The reporting rules were adopted in late 2025 after a two-year rulemaking process.

The obligation falls on the manufacturer, which the rule defines broadly. That includes the entity that produces the product, the brand owner that contracts production under its label, and the importer or first domestic distributor when the producer has no U.S. presence. For a fuller breakdown, see Certivo's Minnesota PFAS reporting PRISM filing guide.

Who Must Report

A report is required from any manufacturer of a product that is manufactured after July 1, 2023, sold, offered for sale, or distributed in Minnesota, including online-only sales, and contains intentionally added PFAS in the product or any component. Products manufactured before July 1, 2023 are excluded following a 2026 amendment to the law.

What Counts as Intentionally Added PFAS

Minnesota defines PFAS as a class of fluorinated organic chemicals containing at least one fully fluorinated carbon atom. This is a deliberately wide definition that captures fluoropolymers such as PTFE, which means most manufacturers selling into Minnesota will have at least some in-scope items. Effective PFAS and chemicals risk management starts with confirming which products and components fall inside this definition.

Minnesota PFAS Reporting Deadlines

The MPCA has moved the initial deadline more than once. The dates below reflect the current, confirmed schedule.

Manufacturers that need more time may request a one-time 90-day extension using form c-pfc1-29, or a waiver using form c-pfc1-30 where equivalent information is already publicly available and verifiable. Approval is not automatic, and both forms must be postmarked by August 16, 2026. Tracking these dates across a global portfolio is exactly where regulatory intelligence and horizon scanning matters, because Minnesota is one of many state deadlines converging in 2026 and 2027.

Minnesota PFAS reporting deadlines timeline through 2026 for manufacturers

Click on image to view full

What Is PRISM and How Recent Updates Changed Reporting

PRISM is the PFAS Reporting Information System for Manufacturers. It is a web application built by the Interstate Chemicals Clearinghouse (IC2), a program of the Northeast Waste Management Officials' Association, with funding from the MPCA. Manufacturers use PRISM to register, submit reports, and pay fees, and the public uses it to view reported data, excluding trade secrets, after an MPCA review period.

The MPCA has improved PRISM steadily since the December 2025 soft launch. The current documented release history runs from PRISM 1.0 (January 2026) through PRISM 1.1, 1.1.1, and 1.1.2 in early 2026, to PRISM 1.2 (April 2026). Practical enhancements delivered across these releases include the ability to accept and display up to 10,000 rows of data, up from 250, hundreds of additional PFAS chemical names, open text fields for component reporting, a direct template download button, and interface improvements that reduce data-entry errors. These changes ease system friction, but they do not reduce the underlying work of collecting accurate PFAS data from suppliers.

Struggling to consolidate supplier PFAS data before September 15? See how Certivo automates it. Speak with a compliance specialist.

PRISM Minnesota PFAS reporting upload capacity increased to 10,000 rows

Click on image to view full

What Must Be Reported

For each covered product or component containing intentionally added PFAS, Minn. Stat. § 116.943 and the adopted rules require:

✓ A description of the product or product category

✓ The PFAS chemicals used in the product or its components

✓ The amount or concentration range of each PFAS

✓ The function or purpose the PFAS serves

✓ Manufacturer and contact information

The rules allow useful flexibility, including grouping similar products, reporting concentration ranges instead of exact amounts, and allowing a group of manufacturers or an authorized representative to report together. This is where BOM-level compliance intelligence becomes decisive, because the reportable unit is the component, not just the finished product, and most manufacturers do not have PFAS resolved at that level.

Industries Affected by Minnesota PFAS Reporting

The reporting requirement reaches almost every discrete manufacturing sector selling into Minnesota:

• 🏭 Electronics and electrical equipment, where fluoropolymers appear in wiring, connectors, and boards

• 🏭 Automotive and industrial equipment

• 🏭 Aerospace and defense

• 🏭 Medical devices and household appliances

• 🏭 Consumer goods, textiles, apparel, and packaging

• 🏭 Chemical manufacturers, importers, and distributors supplying products into the state

Because PFAS is embedded deep in components, companies that consider themselves out of scope often are not. Certivo's analysis on state PFAS regulations for 2026 shows how quickly this exposure spreads across a product portfolio.

Reporting and Documentation Challenges

The MPCA system is not the hard part. Supplier data is. For a global manufacturer, the practical obstacles are consistent:

⚠ Multi-tier supply chains where PFAS presence is unknown below Tier 1

⚠ Unresponsive or overseas suppliers who cannot confirm PFAS content

⚠ Fluoropolymers and processing aids that suppliers do not flag as PFAS

⚠ Component-level data that finished-goods manufacturers have never collected

MPCA has addressed this directly for the first cycle. A manufacturer is considered compliant if it reports all available information by the deadline and retains documentation of its efforts to obtain missing data from suppliers. Under Minn. R. 7026.0080, due diligence means early outreach, multiple contact methods, clear communication of requirements, and continued requests until the information is known. Records must be kept for at least five years after a product leaves the supply chain. This is the discipline behind multi-tier supply chain transparency and automated supplier data collection.

Compliance Risks and Enforcement Exposure

Minnesota can direct manufacturers to test products for PFAS and to provide supporting documentation. Failure to comply can carry civil and criminal penalties under state law. Because most reported data becomes public after review, weak or incomplete filings are also visible to customers, competitors, and advocacy groups.

Compliance engineers should treat this as an audit-readiness problem across several audit types: internal reviews, customer and OEM audits, and MPCA regulatory inquiries. No platform can make an organization audit-proof, and no software eliminates the possibility of a finding. The realistic objective is audit-ready: reduce surprises and shorten response time when a question arrives. That depends on continuous audit-ready documentation, including time-stamped declarations, historic state tracking so you can reconstruct what was reported and when, and a clear evidence chain showing who provided each disclosure and on what authority.

If Your Products Contain No Intentionally Added PFAS

Manufacturers whose products do not contain intentionally added PFAS are not required to submit a report or create a PRISM account. This does not mean the obligation disappears. Companies should retain supplier certifications or other supporting documentation that substantiates the no-PFAS determination, because the MPCA can request it. In practice, defending a negative determination is its own evidence problem, and it benefits from the same supplier and contractor management rigor as an affirmative report.

Compliance Preparation Checklist

✅ Determine scope. Identify which products and components are manufactured after July 1, 2023, sold into Minnesota, and contain intentionally added PFAS.

✅ Collect supplier declarations. Request PFAS presence, identity, concentration, and function at the component level, and log every request.

✅ Retain no-PFAS evidence. Keep certifications for products determined not to contain intentionally added PFAS.

✅ Decide on an extension early. If data will not be ready, file form c-pfc1-29 or a waiver before August 16, 2026.

✅ Prepare PRISM data. Structure your dataset to use the expanded upload capacity and current chemical and function lists.

✅ File by the deadline. Submit best-available data by September 15, 2026, or December 14, 2026 if granted an extension, and keep updating annually by February 1.

For a self-check across PFAS, RoHS, REACH, and Prop 65 documentation, request Certivo's Customer Audit Readiness Scorecard when you speak with a compliance specialist.

How AI Reduces the Minnesota PFAS Reporting Burden

The gap between what Minnesota requires and what most manufacturers can produce by September 15 is a data-collection gap, not a form-filling gap. This is where an AI-native compliance platform changes the economics.

Certivo serves as a centralized compliance data backbone that connects products, components, and supplier evidence in one system. Automated supplier portals collect declarations at scale and chase missing data without manual follow-up. CORA-powered regulatory intelligence parses supplier certificates, test reports, and material declarations, extracts PFAS-relevant data, and flags gaps at intake rather than during an audit. Because Certivo maps results to the bill of materials, teams can answer product-level and component-level questions on demand.

Manufacturers that rely on spreadsheets and email will spend the coming weeks reacting. Certivo turns Minnesota PFAS reporting into a repeatable, documented workflow, with the evidence trail that supports a good-faith compliance position and the ongoing monitoring needed for annual updates and the next state deadline. That shift, from reactive filing to continuous readiness, is the difference between scrambling before each deadline and staying prepared across all of them.

Get complete visibility into your PFAS exposure across products and suppliers. Book a compliance risk assessment.

Minnesota PFAS reporting supplier data collection and PRISM submission workflow

Click on image to view full

Conclusion

Minnesota PFAS reporting is not a future problem. The September 15, 2026 deadline is close, the definition of PFAS is broad, and the reportable unit is the component. The organizations that will file confidently are the ones treating supplier data collection, documentation, and audit readiness as a system rather than a one-time exercise. Certivo gives compliance teams the automation, regulatory intelligence, and evidence trail to meet the Minnesota PFAS reporting requirement on time and to carry that readiness into the annual updates and the state deadlines that follow.