Minnesota has confirmed the August 16 PFAS reporting extension deadline, and manufacturers that need additional time should prepare their extension requests now rather than waiting for last-minute system alerts. The Minnesota Pollution Control Agency (MPCA) requires reporting for products containing intentionally added per- and polyfluoroalkyl substances (PFAS) that are sold, offered for sale, or distributed in Minnesota. The initial report due date is September 15, 2026. For manufacturers that cannot meet that date, extension requests must be postmarked no later than August 16, 2026. Because that date is a Sunday, a U.S. Postal Service postmark of August 15, 2026 is the effective deadline for mail-based requests. Approved extensions will set the report due date to December 14, 2026.
This is not a routine administrative reminder. The interplay between the August 16 extension cutoff, the September 15 reporting date, and the December 14 extended deadline creates unusual pressure for manufacturers, particularly those with complex product portfolios. Understanding who must file, what must be reported, and how the state will process those reports is essential to avoiding gaps in compliance during the final weeks of the reporting cycle.
The August 16 PFAS Reporting Extension Deadline: Who Must Act and What to Include
What is the August 16 PFAS reporting extension deadline? It is the final date for a Minnesota manufacturer to submit a request for additional time to complete its PFAS product report. Because August 16, 2026 falls on a Sunday, postal requests must be postmarked by August 15, 2026. The request must include a $300 check, and if approved, the manufacturer’s report becomes due on December 14, 2026.
This deadline applies to a broad set of companies. The reporting obligation is triggered by the product itself, not by the size of the business or its location. A manufacturer outside Minnesota is still subject to the requirement if the product enters the Minnesota market through normal commercial distribution channels. The state has made clear that the reporting obligation runs with the product, which means companies should review their current inventory, incoming purchase orders, and distribution agreements in light of the September 15 due date.
Which Products Are Covered by Minnesota’s PFAS Product Reports?
Any product manufactured after July 1, 2023, that contains intentionally added PFAS and is sold, offered for sale, or distributed in Minnesota is subject to the reporting requirement. The phrase “manufactured after July 1, 2023” is important: it reaches products that entered the state’s marketplace after that date, not only those produced in Minnesota. A product manufactured elsewhere but imported into Minnesota for retail sale is within scope if it contains intentionally added PFAS.
“Intentionally added” is the key trigger. PFAS that are present only as trace contaminants, background impurities, or unintended byproducts would not meet that standard. But PFAS added to a product or a product component to provide a specific characteristic, function, or performance benefit must be reported. This broad framing captures everything from textiles and cookware to electronics, packaging, personal care products, and other consumer goods. It also extends to components, which means a finished product assembled from multiple parts may contain a large number of separate PFAS entries.
Who Qualifies as a Manufacturer Under the Minnesota Rule?
The definition of “manufacturer” under the Minnesota reporting rule is broad and includes several distinct categories of companies:
- The entity that produces the product.
- The entity that contracts with another party to produce the product under its brand or label.
- If the producer or brand owner has no U.S. presence, the importer or first domestic distributor of the product.
This structure is designed to ensure that every product sold in Minnesota has a responsible party that can be held accountable for reporting. A company that simply places its name on a product but does not physically make it is still a manufacturer for reporting purposes. A foreign producer with no U.S. office will not escape the requirement; instead, the entity that brings the product into the United States and first distributes it in Minnesota assumes the obligation. Companies in distribution chains should therefore verify which party is expected to submit the PRISM report and what information will need to be shared among suppliers, brand owners, importers, and distributors.
What Is PRISM and How Does It Fit Into the Reporting Process?
PRISM, the PFAS Reporting Information System for Manufacturers, is the state’s central platform for collecting, processing, and publishing PFAS product data. Manufacturers must use PRISM to submit the detailed report on each PFAS-containing product, the specific PFAS present, and the function each PFAS serves in the relevant product component. PRISM also handles payment status and, when a manufacturer requests it, confidential business information protection.
As of August 10, 2026, 21,358 items were listed in PRISM. That number, while substantial, does not correspond to 21,358 products. Because the function of each PFAS intentionally added to a product component must be reported, a single product can produce multiple item listings. A shoe with a water-resistant textile, a flame-retardant foam layer, and a stain-resistant sole, for example, could generate several entries in PRISM even though it is only one product. This granularity means manufacturers should not assume the total item count reflects the actual number of products on the market. Instead, it reflects the volume of individual PFAS-component relationships that the state is tracking.
How the Extension Request Process Works: Postmarks, $300 Fees, and the December 14 Due Date
The extension process is tightly structured, and the date manufacturers submit their request matters more than they might expect. The MPCA has established August 16, 2026 as the postmark deadline for extension requests. But August 16, 2026 is a Sunday, and a U.S. Post Office will not provide a Sunday postmark. Manufacturers using the U.S. Postal Service must therefore mail the request early enough to receive a postmark of August 15, 2026. The practical effect is that Saturday, August 15, is the last day most postal customers can create a valid postmark.
Manufacturers should not interpret the Sunday date as a courtesy grace period. The MPCA’s language is explicit: requests must be postmarked no later than August 16, 2026, and postal users should be prepared to obtain an August 15 postmark. A request placed in the mail on Monday, August 17, would fall outside the stated window, regardless of whether the envelope was written over the weekend.
What Must Accompany an Extension Request?
Each extension request must include a $300 fee in the form of a check. The state has not described an electronic payment alternative for extension requests, so manufacturers should account for the time required to prepare and mail a physical check. The check must arrive with the request, not separately or after the fact. A request that is sent without the fee will not be considered complete, and the manufacturer may lose the benefit of the extension window.
In addition to the fee, manufacturers should make sure the request clearly identifies the company submitting it and the products covered by the requested extension. While the MPCA’s published guidance focuses on the postmark date and the fee, a well-organized request will reduce the likelihood of administrative confusion. Manufacturers with multiple legal entities, affiliated brands, or complex ownership structures should confirm that the request is submitted by the same registered entity that will file the PRISM report.
What Happens After an Extension Is Approved?
Manufacturers that receive an approved extension will have until December 14, 2026 to submit their PFAS product reports. This extended deadline is not an open-ended delay; it is a fixed, final due date for the reports. The extra time is intended to help manufacturers with large inventories, incomplete data, or unresolved supplier questions to complete their submissions, but it does not reduce the underlying reporting obligations. Every product component with intentionally added PFAS still needs to be identified, and the function of each PFAS still needs to be disclosed.
The extension process also creates a second operational timeline. A manufacturer that obtains an extension will need to manage its internal data collection over a longer period, but it will also be entering the reporting system later, when the MPCA may still be processing a backlog of September 15 submissions. Companies should build buffer time into their extended schedules and avoid treating December 14 as merely a soft target.
PRISM Public Contact and Billing Contact: What Every Registered Company Should Know
In its August 7, 2026 Daily Digest Bulletin, the MPCA provided important clarifications about how contact roles and public data will operate in PRISM. The first user for a manufacturer registered in the system will be designated as the company’s public contact and billing contact. This is the user who will appear on the manufacturer’s PRISM profile unless those roles are reassigned. The designation occurs automatically, not through an application or selection process, so the first person to log in and register the company may become the public face of the company’s PFAS reporting without intending to take on that role.
The public contact user has the ability to reassign the public contact and billing contact roles to other users registered under the company. This is an important administrative control. If the initial user is not the appropriate individual to handle public inquiries or billing responsibilities, the company should identify a different registered user and reassign the roles before significant reporting activity takes place. Leaving the default designation in place may result in public inquiries being routed to someone who is not prepared to answer them.
What Contact Information Will Be Public in PRISM?
The MPCA has stated that the contact information for each manufacturer’s designated public contact will be public data in PRISM. This is not a private internal record; it will be visible to anyone who accesses the system or requests public data on PFAS reporting. Manufacturers may use a compliance e-mail inbox, customer support e-mail address, or company hotline phone number as the public contact information. This gives companies flexibility to avoid publishing an individual employee’s direct personal contact details.
There is, however, a specific condition: the responsible person’s name must be included. A manufacturer cannot hide behind an anonymous inbox or a generic department label. The state wants the public to know which individual at the company is answerable for its PFAS reporting contact function. This requirement has privacy implications for companies that prefer to keep individual names out of public-facing systems. The solution is to designate a functional contact point, such as a compliance inbox, while still naming the responsible person associated with that inbox.
Manufacturers should also consider whether the public contact role is being handled by the right type of user. A customer service email address may be appropriate for product inquiries, but if the designated contact is also the billing contact, the company should ensure that invoices and payment notifications are directed to the right team. The PRISM role structure allows these responsibilities to be split, but only if a registered user actively makes the change.
21,358 Items in PRISM: Why the Item Count Matters
The item count in PRISM reflects the complexity of PFAS reporting in a way that many manufacturers do not anticipate. As of August 10, 2026, 21,358 items were listed in the system. This number is useful as a signal of how much work has already entered the pipeline, but it is not a measure of product count. The MPCA has explained that because the function of each PFAS intentionally added to a product component must be reported, the number of items will be greater than the number of products reported.
For a manufacturer with a single product, the reporting burden could still be significant if that product contains multiple PFAS in multiple components. A product may have a PFAS-based coating on one component, a PFAS-containing additive in another, and a separately treated inner layer. Each of those combinations represents an item in PRISM, and each requires disclosure of the function served by the PFAS. This means manufacturers cannot simply count their product SKUs and assume that is how many entries they need to create.
Why the Component-Level Approach Creates More Work
The component-level approach is intended to give regulators and the public a more accurate picture of where PFAS are present in Minnesota’s consumer economy. However, it also places a heavy burden on manufacturers to understand their supply chains at a level that may not have been documented previously. A final product manufacturer may know that a product contains PFAS, but may not know exactly which components contain PFAS, what specific PFAS is present, or what function it serves. The PRISM reporting structure forces companies to move beyond high-level claims and into detailed chemical substance identification.
Manufacturers should use the item count as a benchmark for their own internal reporting. If a company has identified far fewer items than expected for its product portfolio, it may not have completed the component-level analysis. Conversely, a company with a very large number of items should allow more time for data verification, supplier responses, and internal review before submission. The complexity of the item structure also explains why the MPCA expects publication delays as the reporting deadline approaches.
MPCA Review, Trade Secret Requests, and Publication Delays Before the September Deadline
Submitting a report in PRISM is not the same as having it publicly displayed. The MPCA will review each report before it appears in PRISM. That review includes the submitted report itself, any chemical trade secret requests, and the payment status for the applicable fees. Only after those elements have been reviewed will the report be published in the system. The MPCA has warned that publication times will become slower as the September 15, 2026 due date approaches.
The cause of the delay is straightforward: a high volume of submissions arriving near the deadline will create a backlog of reports waiting for review. The MPCA has said it is prioritizing assistance to users with support requests first, and will then shift its focus to publishing reports. This is a significant operational decision. Manufacturers that need help resolving technical issues in PRISM should expect their support matters to receive attention before the agency turns to the publication queue. Companies should not wait until the final days to test the system, upload data, or resolve payment problems.
When Is a Manufacturer Officially Compliant?
The MPCA has provided a practical compliance benchmark. Once a user’s report status is “submitted” and the payment status is “complete,” the manufacturer has completed the initial reporting requirements and is compliant with reporting requirements. This is an important clarification because it signals that compliance is not dependent on public display in PRISM. A manufacturer may have satisfied its obligation even if its report has not yet been published for viewing.
Manufacturers should document the moment their report reaches the “submitted” status and their payment is marked “complete.” This may require taking screenshots, saving confirmation emails, or generating internal records that demonstrate the timing of the submission. If the MPCA’s publication queue lags, those internal records may be the only evidence a manufacturer has to prove it filed on time. Waiting for the report to become visible to the public is not the right compliance strategy.
How Chemical Trade Secret Requests Fit Into the Process
The MPCA’s review process also covers any chemical trade secret requests. A manufacturer that wants to protect the identity of a PFAS or its concentration may need to make a trade secret claim as part of the submission. The MPCA will evaluate those requests during its review. This adds another layer to the review timeline, because trade secret claims cannot be resolved on the spot. Companies should ensure their trade secret documentation is complete and well-supported when the report is submitted, rather than expecting to supplement it after the review has begun.
The need for trade secret protection may conflict with the state’s interest in public transparency. The MPCA will have to balance the public data requirements of PRISM with the legal protections available for confidential chemical information. Manufacturers with genuine trade secret concerns should be prepared to justify their claims and should not assume that the mere assertion of confidentiality is enough to keep information private.
What Manufacturers Should Expect in the Final Weeks
As the September 15 deadline approaches, manufacturers should expect several operational challenges. First, system performance may degrade as more users log in and submit large datasets. Second, support response times may lengthen as the MPCA prioritizes assistance but works through a growing volume of requests. Third, publication of submitted reports will slow, meaning public-facing data will be less current than normal during the peak submission window.
None of these challenges changes the underlying reporting obligation. A manufacturer that waits until September 14 to begin entering large amounts of data faces a realistic risk of encountering a technical issue or payment problem that cannot be resolved before the deadline. The MPCA’s emphasis on the “submitted” status is useful, but it does not eliminate the need for early preparation. Companies should aim to submit well before September 15, even if they must work in phases, because a complete and accepted submission on September 14 is far more valuable than an incomplete draft on September 1.
The reporting structure in Minnesota represents a broader trend in state-level PFAS regulation: simple disclosure is giving way to detailed, component-specific, function-based reporting. The August 16 extension deadline is therefore not just a date on a compliance calendar. It is a turning point for manufacturers that still need to gather supplier data, map their products, identify every PFAS-containing component, and decide how to handle public contact roles and trade secret protections. The September 15 reporting date will then raise the pressure even higher. For companies that want to avoid a chaotic end to the reporting cycle, the time to act is now: complete the extension request if necessary, register the correct users in PRISM, confirm the public contact, and build a complete component-level inventory before the final deadline arrives.
