Form PF Schema Locked: What It Means and How to Prepare Before October 2026

On March 2, 2026, FINRA locked the amended Form PF XML schema. No further changes are permitted.

If your firm has been watching the Form PF amendment process from a distance, waiting to see how things evolve before committing resources, that window is now firmly shut. The schema you will file against on October 1, 2026 is the schema that exists today. There is no more room for the rules to change.

This is not a procedural footnote. It is a signal that the SEC and FINRA have moved Form PF from policy debate into operational execution. For buy-side firms, the question is no longer “what will be required?” It is “are we ready to deliver it?”

What “Schema Closed” Actually Means

The March 2 lock date was published in FINRA’s amended Form PF roadmap well in advance. It represents the point at which the XML schema — the technical blueprint governing how Form PF data must be structured, validated, and submitted — is finalized.

From this point forward:

• No new fields will be added or removed before October 1
• No data type revisions will be made to the schema
• No further schema feedback rounds will be opened
• The QA testing environment remains open through September, but the schema it tests against is now fixed

Any firm that submitted feedback before the January 30 deadline has had its input considered. But what FINRA has published is final.

Quick Recap: Where the March 2 Deadline Fits

No More Feedback. No More Adjustments.

One of the less-discussed aspects of the schema lock is what it eliminates: optionality. Until March 2, firms could reasonably wait and see if contested data elements would be revised or if FINRA would clarify ambiguous field definitions in response to industry feedback.

That optionality is gone. The schema is what it is. Firms that have not yet mapped internal data structures to the amended schema’s requirements are now operating with a fixed target and a shrinking runway.

Technical questions on implementation still route to FINRA. Policy and interpretation questions remain with the SEC. But neither will change the schema before October 1.

The Data Gap Firms Can No Longer Ignore

The amended Form PF is a materially different reporting obligation compared to what most firms have been filing under the legacy PFRD system. The schema lock makes it essential to understand exactly where your firm’s data estate stands against the new requirements.

Key areas where data gaps commonly surface:

• Leverage and exposure granularity: The amended form requires more disaggregated reporting across borrowing, counterparty exposure, and derivatives positions. Many firms source this from multiple systems that were never designed to produce a unified output.
• Liquidity metrics: The updated schema enforces stricter field definitions around liquidity classification and stress horizon assumptions, which may conflict with how internal risk systems currently categorize positions.
• Granularity in sub-asset classification: Firms will be required to realign existing sub-asset classifications with the updated taxonomy and report exposures at a more granular level, enhancing the precision and transparency of disclosures.
• NFA identifier alignment: The January 5 update standardized nfaId fields to nfaFirmIDType. Firms with inconsistent identifier management across entities need to resolve this before testing will produce clean outputs.
• Hedge fund adviser expansions: Quarterly reporting requirements for hedge fund advisers have been significantly expanded. For many, this represents a net-new data collection workflow.

The Road to October 1, 2026

With roughly six months remaining before production deployment, the QA environment is the most valuable asset available to firms right now. FINRA has kept it open through September specifically to allow end-to-end testing, but only firms that have completed data mapping and system configuration will be able to use it meaningfully.The practical sequencing firms should follow from here:

• Complete field-level mapping between internal data sources and the locked schema
• Identify and resolve data quality issues, particularly around NFA identifiers, exposure calculations, and liquidity classifications
• Configure or validate XML generation pipelines against the finalized schema structure
• Run QA submissions through the FINRA testing environment and address validation failures iteratively
• Align compliance, risk, and operations teams on new event-driven reporting workflows
• Conduct full end-to-end dry runs before the October 1 go-live

Once October 1 arrives, there is no parallel filing period. Legacy Classic IARD/PFRD will not be available for post-deadline filings. There is no safety net.

What Buy-Side Firms Should Be Doing Right Now

The schema lock removes uncertainty about what to build toward. But it also removes excuses for delay. Three concrete questions every firm should be able to answer today:

• Do we have a complete field-level mapping? Every element in the locked schema must be traceable to a defined internal data source. If gaps exist, they must be remediated, not deferred.
• Have we generated and validated a test XML submission? A clean QA submission against the FINRA testing environment is the only reliable proof that your system configuration is correct.
• Are our operational workflows aligned with the new event-driven requirements? Technology alone does not solve Form PF compliance. The people and processes that feed data into the filing system must be ready for the amended obligations, including rapid reporting triggers.

The firms that will be in the best position in October 2026 are those that treat the next six months as an active compliance execution phase, not a continuation of the wait-and-see stance that characterized the last two years of Form PF amendments.

How IVP Can Help

Indus Valley Partners has supported buy-side firms through regulatory reporting transitions for over two decades. The IVP Regulatory Reporting Solution is purpose-built for the operational complexity that Form PF’s amended XML framework introduces — covering data ingestion, validation, schema mapping, and submission workflows in a single integrated platform.

With the schema now locked, the focus shifts entirely to execution. IVP is ready to help firms accelerate that execution, from data mapping exercises to clean QA submissions and production readiness ahead of October 1.

With the SEC and CFTC’s final amendments set in stone and the FINRA XML schema officially locked, Indus Valley Partners hosted a live session on March 11 to help buy-side firms pivot from interpretation to implementation.

IVP regulatory experts Anurag Awasthi (Product Manager) and Shria Pandey (Associate Director) walked through the final Form PF schema, shared real-world validation errors and data gaps uncovered during QA testing, and presented a clear roadmap for compliance, operations, and reporting teams ahead of the October 1 deadline.

The session covered:

• Final Form PF Analysis: Material changes and amendments since January
• The XML Lock-in: Why validation rules leave no room for manual adjustments
• Testing Insights: Real-world data gaps and problem areas identified during QA
• Operational Readiness: Aligning your teams and tech stack for October
• Expert Q&A: Responses to the most pressing concerns from the live buy-side audience

Watch the Session Now

Don’t wait until October to find out you’re not ready. Contact Indus Valley Partners to see how the IVP Regulatory Reporting Solution can help your firm meet the October 1, 2026 Form PF deadline with confidence.