Ensuring corporate integrity: our compliance-first workflow

Shaping the future of our new compliance-first workflow

We are developing our compliance-first reporting workflow, and we are doing so in close collaboration with our customers, under the project name of Digital One.

By working with existing banking clients and other compliance-driven teams in real reporting scenarios, we have been able to validate ideas early, understand where friction appears in practice, and refine workflows around how teams actually create, review, and prepare structured reports.

That feedback loop matters. It helps us focus not just on feature delivery, but on the value we bring to reporting teams: faster creation of ESEF-ready XHTML, richer and more intuitive navigation, easier verification of applied tags, and a more unified workflow without constant tool switching.

What we have validated together

The capabilities already delivered for Digital One project reflect a practical, compliance-led approach. Authoring ESEF-ready XHTML is made faster, with better downstream tagging reliability, avoiding structural errors. Along with inline XBRL tagging, this new workflow enables work with images inside reports, making complex narratives clearer and more understandable. Tagged elements are now visible directly in the editor, making it easier to verify coverage, understand report structure, and reduce the risk of accidental edits that weaken tagging intent.

Just as importantly, this new workflow now operates as a native workflow within CtrlPrint. That gives teams a unified environment for compliance and reporting work, with stronger coordination between design and compliance and less time lost to switching between disconnected tools. Project Digital One also brings spreadsheet-driven reporting closer to the core workflow, allowing teams to use Integrate Excel sources inside the editor instead of relying on manual handoffs.

As the platform develops further, the same value logic continues. We are working toward clearer handling of contexts, units, and dimensions in tagging workflows, stronger native support for ESEF and ESRS taxonomies, eliminating transfer errors between compliant and designed outputs, faster production and revision cycles, and more controlled collaborative review with a strong audit trail.

Why the compliance-first model matters

The strategic perspective is larger than any single feature. A compliance-first reporting workflow creates a governed source for structured content, data, and taxonomy first, then lets that source power multiple downstream outputs.

Adobe InDesign connection is coming in first, closing the loop for compliant designed reports. That is the logic behind our compliance-first workflow: build and control reporting content once, keep it aligned with compliance requirements, and make it available wherever the reporting process needs it next.

In practical terms, this supports a single-source-of-truth model with unprecedented flexibility over time. Structured reporting outputs can be generated from the same governed foundation, designed reporting workflows can stay connected instead of drifting away from approved source content, and the platform can evolve toward future API connections with web publishing systems and other content distribution platforms.

That combination of control, traceability, and output flexibility is what makes the compliance-first approach strategically important for the next phase of corporate reporting.