How it works
Map once, report infinitely
A document-driven approach tags a finished document, at the end of the process. Taxxor Disclosure Manager turns that around: the report starts as structured data, and that data flows through the writing, the design and every output format — so figures, text and tags cannot drift apart.
Three disciplines, in parallel, on the same report
A report is the work of three disciplines: data, text and design. In a document-driven process they wait for each other — the text waits for the figures, the layout waits for the text, and every late change means going back to the start. Taxxor DM gives each discipline its own workflow on the same structured content, so experts work in parallel instead of in sequence.
- DATA
Finance teams load figures straight from the source systems — SAP S/4HANA, SAP BW, LucaNet, the Excel plugin or a custom connector — and map them once to the reporting requirements. That mapping is reused automatically for every future report, and every value stays traceable to its source through data lineage. No spreadsheet re-uploaded every cycle.
- COPY
Authors draft and review the report text section by section, in multiple languages where needed. Figures in the text are references to the data — not retyped copies — so a changed value carries through to every sentence it appears in. Versions, comments and track changes keep review rounds manageable.
- DESIGN
Designers capture the brand in a report design package: styling rules and templates built on web technology, set up once and applied to every channel. Sections are shared across channels, so the web version is not a second project next to the PDF — it is the same content in a different form.
That keeps a change just before filing manageable: adjust the figure at the source, regenerate, and every format is up to date — while the audit trail and track changes record what changed, when and by whom. And the next reporting round does not start from zero: roll-forward stages the report for the next month, quarter or year, with mappings, structure and design intact.
From source to every output
Every output comes from the same generation step. What is in the iXBRL filing is also in the printed PDF and on the website — because they are generated from the same structured content, not because someone cross-checked them.
The XBRL engine
Underneath the platform sits an in-house engine that can read any XBRL taxonomy. A taxonomy is the machine-readable definition of what a regulator or requesting authority wants to receive: which concepts, how they relate, and which validation rules apply. Taxxor DM treats that definition as data, not as a built-in assumption. New rules therefore do not mean new software: load the new or changed taxonomy, and the platform renders valid XBRL or Inline XBRL against it.
-
Dutch Taxonomy (NT)
for filing and submission via SBR, such as the annual accounts with the Dutch Chamber of Commerce (KvK).
-
ESEF
the annual financial report of listed companies as Inline XBRL.
-
SEC
20-F reporting in Inline XBRL for foreign private issuers.
-
ESRS
sustainability tagging under CSRD, standalone or integrated in the financial annual report.
-
Every next version
annual NT releases and taxonomy updates are loaded as data, into the same engine.
-
Extensions and block tagging
taxonomy extensions and block tagging in the same environment, so no separate project when a mandate requires deeper tagging.
-
Built-in validation
the report is validated against the rules of the loaded taxonomy before filing.
See the process from source to filing
- Walk through the full process in a demo: from source connection to generated filing.
- Set up the first mapping together for the reporting type at hand.
- Generate the first report — every next report starts where this one left off.