Pilot Program

SFRS is ready for pilot users who want a better machine format around existing XBRL workflows.

The current product position is:

Canonical JSON infrastructure for structured financial reporting, with XBRL/iXBRL interoperability.

The current non-position is:

Drop-in regulator-ready replacement for XBRL.

Who This Is For

• filing software vendors that already ingest or generate XBRL
• internal finance or reporting platforms that need a developer-friendly canonical layer
• data platforms normalizing public filings
• advisory or reporting operations teams that spend too much time on XML handling

What A Pilot Includes

• import a partner filing into canonical v2
• validate against the nearest supported profile
• export back to XBRL and iXBRL
• compare semantic preservation and workflow friction
• review gaps, unmapped concepts, and extension needs

What We Can Promise Today

• canonical fact-centric model with contexts, units, facts, dimensions, footnotes, and relationships
• profile-aware validation for sec-us-gaap-annual and ifrs-esef-annual
• package generation with a manifest and checksums
• corpus-backed regression testing on the currently supported milestone

What We Cannot Promise Yet

• regulator-ready submission parity
• broad corpus-backed compatibility across public filings
• complete taxonomy/disclosure support across every real-world filing profile
• zero manual review for production filing operations

Pilot Success Metrics

• import fidelity: % of facts, contexts, units, and dimensions preserved into canonical v2
• round-trip fidelity: semantic equivalence after XBRL -> canonical -> XBRL
• workflow reduction: time or code removed from XML/XBRL-specific handling
• defect discovery: unsupported facts, missing relationships, extension gaps, and profile failures found during the pilot

Recommended Pilot Shape

1. Pick one filing family.
2. Choose 3 to 10 representative filings.
3. Import them into canonical v2.
4. Review validation outcomes and round-trip behavior.
5. Record unsupported structures and required profile work.
6. Decide whether the partner wants deeper integration.

Deliverables

• pilot intake checklist
• fixture set or sample filings
• canonical import summaries
• validation results
• regenerated XBRL and iXBRL
• package manifests
• written gap report with next implementation priorities

How To Position It Externally

Use language like:

• “SFRS gives you a canonical JSON layer around your reporting workflow.”
• “You keep XBRL interoperability while gaining a developer-friendly internal model.”
• “The pilot is designed to measure fidelity and workflow reduction, not to skip filing controls.”

Avoid language like:

• “SFRS fully replaces XBRL today.”
• “SFRS is already approved for regulator submission.”
• “This removes the need for filing review.”

Next Step

Run the Demo Kit with one of the corpus fixtures, then swap in the partner’s filing set once we have permission and scope.