Minnesota's PFAS in products law, known as Amara's Law (Minn. Stat. § 116.943), requires any manufacturer that sells, offers for sale, or distributes products containing intentionally added PFAS in Minnesota to report those products to the Minnesota Pollution Control Agency (MPCA). The Minnesota PFAS reporting deadline for initial reports is September 15, 2026, submitted through the state's PRISM portal.

This guide explains what the law requires, who is covered, how the filing works, and — for companies arriving in the final days — the minimum viable path to being considered in compliance. If you want to understand your exposure before you file, you can request a compliance risk assessment to map which products and suppliers carry PFAS risk.

Table of Contents

1. The September 15 Deadline: Where Things Stand Right Now

2. What Amara's Law Is and Why It Exists

3. Who Must Report

4. What Must Be Reported

5. How Filing Works: PRISM, Fees, and Timing

6. The Relaxed First-Report Standard (What It Actually Lets You Do)

7. What to Do If You Haven't Filed Yet

8. Enforcement and Non-Compliance Exposure

9. The Product Bans Running Alongside Reporting

10. After September 15: Annual Updates and Ongoing Obligations

11. How Certivo Supports Minnesota PFAS Reporting

12. FAQs

The September 15 Deadline: Where Things Stand Right Now

The initial Minnesota PFAS reporting deadline is September 15, 2026. The reporting deadline under Amara's Law, Minnesota Statute Section 116.943, has been delayed again, and initial reports on PFAS in products distributed or sold in Minnesota are now due on September 15, 2026. This is the second extension — MPCA moved the deadline from July 1, 2026, to September 15, 2026, on April 15, 2026, and then reaffirmed that deadline on June 15, 2026.

The point most companies miss: the option to buy more time is already gone. MPCA offered a single 90-day extension, but extension requests had to be postmarked by August 16, 2026. That date has passed. There is no "no PFAS extension" left to request for this reporting cycle, and there is no indication in current MPCA guidance of a further blanket delay. Manufacturers should treat September 15, 2026, as firm.

For the broader multi-state picture, see Certivo's overview of state PFAS regulations for manufacturers and the PFAS framework page.

What Amara's Law Is and Why It Exists

Amara's Law is Minnesota's PFAS pollution-prevention statute, passed in 2023 and named after Amara Strande. Minnesota's "Products Containing PFAS" legislation, Minn. Stat. § 116.943, imposes obligations on manufacturers, importers, and distributors of products containing intentionally added PFAS. It has two engines running in parallel: a reporting requirement and a phased set of sales bans.

The statute takes effect in stages between January 1, 2025, and January 1, 2032, building toward a general prohibition on nonessential PFAS use. The reporting obligation covered in this guide is the near-term deadline. The bans are a separate, ongoing track covered further below and on Certivo's PFAS chemical and hazmat compliance page.

"Intentionally added PFAS" is defined broadly. It captures any scenario in which PFAS is intended to be present in the final product to provide a specific function, which is why the law reaches far beyond obvious categories like nonstick cookware into electronics, industrial components, medical devices, and more.

Who Must Report

The reporting obligation is wide. The law defines "manufacturer" to include, depending on the situation, manufacturers, brand owners, importers, and distributors of products with intentionally added PFAS sold, offered for sale, or distributed in Minnesota.

That means the duty can land on your company even if you did not physically make the product:

🏭 Manufacturers producing finished goods or components containing intentionally added PFAS

📦 Brand owners whose name appears on a PFAS-containing product

🚢 Importers bringing covered products into commerce in Minnesota

🔗 Distributors selling or distributing covered products in the state

If your products reach Minnesota through any channel and contain intentionally added PFAS, assume you are in scope until you can document otherwise. This cross-industry reach is why aerospace, medical device, industrial equipment, and consumer goods companies are all affected. Understanding which products in your portfolio carry PFAS is a BOM-level material mapping problem before it is a filing problem.

Who must file Minnesota PFAS reporting under Amara's Law across the supply chain

Click on image to view full

What Must Be Reported

For each covered product or product component containing intentionally added PFAS, MPCA requires a defined data set. Required information includes 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 PFAS serves in the product; manufacturer and contact information; and other information required by MPCA rules. Greenberg Traurig LLP

MPCA built in flexibility on the hardest data point — concentration. Instead of providing exact concentrations, manufacturers can report PFAS levels within specified ranges, and total organic fluorine (TOF) content can be accepted if the amount of each PFAS is not known within applicable due diligence standards. One scope narrowing also applies: a 2026 amendment signed by Governor Walz excludes products manufactured before July 1, 2023, so manufacturers must report products manufactured after that date. TÜV SÜDRV Industry Association

Collecting PFAS identity and function data across a multi-tier supplier base is the bottleneck for most companies. Certivo's approach to automated supplier data collection and PFAS tracking across the supply chain is built for exactly this gap.

How Filing Works: PRISM, Fees, and Timing

Reports are submitted electronically. Reports must be submitted through PRISM, the PFAS Reporting Information System for Manufacturers, and each manufacturer must pay a one-time flat fee of $800 to support implementation costs. MPCA has indicated that reported information will generally be publicly accessible following a review period, except for information protected as a trade secret, and manufacturers may request waivers, extensions, and trade secret protection where available under the rules.

Practical sequencing matters in the final days:

1. Register in PRISM early. Account setup and the $800 fee are not steps you want to discover at hour eleven.

2. File at the product or product-category level as the rules allow, using concentration ranges or TOF where exact figures are unavailable.

3. Flag trade-secret data at submission rather than after.

MPCA has been layering on support materials and PRISM improvements to ease this. If your systems are still spreadsheet-based, Certivo's guidance on moving from spreadsheets to AI-powered compliance systems is a useful reference for the next cycle.

The Relaxed First-Report Standard (What It Actually Lets You Do)

This is the most important — and most misunderstood — point for anyone filing late. MPCA relaxed the due-diligence bar for this first reporting period. Manufacturers will be considered in compliance with Amara's Law if they provide all PFAS data available by the September 15, 2026, deadline and maintain records of efforts to obtain additional supply chain information. Reports can be updated annually as new information becomes available using PRISM's "copy report" feature, and guidance on this appears on page 5 of the Supplemental PRISM Guide.

In plain terms: September 15 is a "file what you have" deadline, not a "have everything perfect" deadline. The compliance test for this first cycle is (a) submit the data you currently possess and (b) keep a documented record of your efforts to obtain the rest. That is a materially different — and more achievable — standard than full, exact disclosure.

⚠️ This relaxed standard applies to the quality and completeness of the data. It does not waive the obligation to file by September 15. Submitting nothing is not covered by this flexibility.

Maintaining that "record of efforts" — who you asked, when, and what came back — is itself a continuous audit-ready documentation problem, and it is exactly the kind of time-stamped evidence trail that becomes your defense if MPCA later questions completeness.

Minimum path to meet the Minnesota PFAS reporting deadline before September 15

Click on image to view full

What to Do If You Haven't Filed Yet

If you are reading this in the final days before September 15 and have not filed, the extension route is closed but compliance is still reachable. Prioritize in this order:

✅ Confirm scope fast. Identify which of your products are sold or distributed in Minnesota and contain intentionally added PFAS. Exclude anything manufactured before July 1, 2023.

✅ Set up PRISM and pay the $800 fee now. Do not let account provisioning become the blocker.

✅ Report what you can substantiate today. Use concentration ranges or total organic fluorine where exact values are unknown — the rules permit it.

✅ Document your due-diligence trail. Save supplier requests, dates, and responses. This is what qualifies you under the relaxed first-report standard.

✅ Plan the annual update. Anything you could not confirm by September 15 gets refined in the annual cycle via PRISM's copy-report function.

The single biggest accelerator here is supplier data. If your PFAS declarations are scattered across email threads and PDFs, AI document parsing and certificate validation can extract and structure that data far faster than manual review. Not filed yet? You can speak with a compliance specialist about assembling a defensible first report quickly.

Enforcement and Non-Compliance Exposure

Amara's Law is not a guidance document — it carries real penalty authority. The MPCA may enforce Amara's Law under Minnesota Statutes §§ 115.071 and 116.072, which include civil penalties of up to $15,000 per day of violation.

Beyond direct penalties, non-compliance creates downstream commercial exposure that matters at the executive level:

⚠️ Market access risk — Products that should have been reported (or that fall under a ban) face sale and distribution challenges in Minnesota.

⚠️ Customer and OEM scrutiny — Retailers and OEMs increasingly require proof that suppliers meet state PFAS obligations before they will place orders.

⚠️ Public visibility — Because reported data becomes largely public after review, gaps and inconsistencies are visible to customers, competitors, and NGOs.

For CFOs and boards, the practical exposure is less about a single fine and more about repeated per-day penalty accrual, disrupted Minnesota sales, and the cost of a fire-drill response every reporting cycle. That argues for proactive, continuous compliance monitoring rather than deadline-driven scrambles.

The Product Bans Running Alongside Reporting

Reporting is only one half of Amara's Law. The other is a phased prohibition on selling PFAS-containing products, and it is already in force for some categories. Beginning January 1, 2025, eleven product categories — including carpets, cleaning products, cookware, cosmetics, and menstruation products — were prohibited from sale or distribution if they contain intentionally added PFAS, building toward a general ban on all PFAS-containing products by 2032 unless the product and its use are deemed "currently unavoidable."

A gap worth flagging for planning: MPCA has yet to promulgate rules governing what comprises a "currently unavoidable use," so companies should assess whether their business requires that they seek such a determination. Based on currently available regulatory guidance, manufacturers relying on PFAS for essential functions should track this rulemaking closely, because the "currently unavoidable use" pathway is what will determine market access as the 2032 general ban approaches. Certivo's PFAS and chemical risk management coverage tracks these developments.

After September 15: Annual Updates and Ongoing Obligations

Amara's Law is a recurring obligation, not a one-time filing. Subsequent reports are due yearly to MPCA on February 1. New products, product changes, and newly obtained supply-chain information all flow into the annual update through PRISM's copy-report function.

This is where the difference between reactive and continuous compliance compounds. Companies that treat September 15 as a single event will repeat the same fire drill every February. Companies that build a standing PFAS data backbone — supplier declarations, BOM-level substance mapping, documented due-diligence trails — turn each annual update into a refresh rather than a rebuild. For the strategic view of this shift, see Certivo's guide on why people-only compliance can't scale.

How Certivo Supports Minnesota PFAS Reporting

Minnesota PFAS reporting is fundamentally a supply-chain data problem: you cannot report PFAS identity, amount, and function without pulling accurate declarations from suppliers, then mapping them to the specific products you sell into Minnesota. That is the work Certivo is built to reduce.

Certivo operates as the system of record for product compliance, with CORA — its embedded regulatory intelligence — supporting the workflow end to end:

🤖 Automated supplier data collection through structured portals instead of email chains, so PFAS declarations arrive in a consistent, usable format.

📄 AI document parsing and certificate validation to extract PFAS data from test reports, SDSs, and declarations at scale.

🔗 BOM-level material mapping to connect substance data to the exact products and components in scope for Minnesota.

📊 Audit-ready documentation that time-stamps what you knew and when — the "record of efforts" the relaxed first-report standard requires.

Certivo does not eliminate your reporting obligation or make any company "audit-proof." What it does is reduce compliance surprises, speed evidence retrieval, and cut the response time for each reporting cycle. To see where your PFAS exposure sits across products and jurisdictions, request a compliance risk assessment.