Features from source data to filing

Built for the reporting process

Taxxor Disclosure Manager is not a loose collection of functions. Every feature falls into one of four groups — consistent data, control and audit, designed output, validation and compliance — exactly the places where a reporting cycle loses time and certainty.

One source, always consistent

Figures and text live once in the system and feed every output channel. Consistency is not an after-the-fact checking round — it is a property of the architecture.

  • Direct data connections to source systems — SAP S/4HANA, SAP BW, LucaNet, Excel or a custom connector. The report draws on system data, not on a spreadsheet that gets re-uploaded every cycle.
  • Changes propagate to every channel: adjust a figure and the PDF, the iXBRL, the web version and Word all use the same new value — no manual data syncing.
  • Shared sections and multiple hierarchies per project: the same content in the annual report, the web version or another document — reuse a table or passage without copying it.

Control and audit

The auditor’s questions — where does this figure come from, and what changed since the previous version? — are recorded by the platform itself, as the report takes shape.

  • Versioning: capture intermediate versions for internal or external review rounds and see exactly what changed since.
  • Data lineage: reports that trace every figure in the output back to its source, including the XBRL tag. That saves detective work during the audit.
  • Roll-forward: start the next reporting period from the previous one — structure, text and tagging carry over, the figures move on to the new month, quarter or year.
  • Track-changes output per section, chapter or for the complete document: one overview of what changed.
  • Audit trail with Auditor View: every change recorded — what, when, by whom — and opened up to the auditor in a dedicated timeline view.
  • Review rounds happen inside the report itself: highlight text or figures and leave a comment on the section. Access rights can be set per project, output channel or section.

Designed output

The same source produces not just the filing, but the report as it is actually read — in brand style, in every channel.

  • Write and edit in WYSIWYG: the editor shows the report as it will be published, layout and all.
  • Two PDFs from the same content: print-ready for the printer and a version for online publication and download.
  • MS Word and MS Excel as standard output formats — export a section, a chapter or the complete project.
  • Multilingual content: the report in multiple languages from the same structure, with translations tied to the same figures.
  • Design built on web technology (HTML and CSS): every output in brand style, using technology designers already know.
  • Integrated charts drawn from the tables in the report: when the data changes, the chart changes with it.

Validation and compliance

In Taxxor DM, validating is not a final step before filing — it is part of the writing.

  • Built-in XBRL validations: the report is validated during authoring against the loaded taxonomy and the regime’s validation rules — issues surface while working, not at the portal.
  • Any taxonomy: NT (SBR), SBR-wonen, ESEF, SEC and ESRS. The XBRL generator is taxonomy-agnostic and loads any XBRL model, so a new or updated taxonomy does not require new software.
  • Users create extension elements themselves, inside the platform, for the items a taxonomy does not cover. No XBRL consultant or third party is involved, and an iXBRL filing that requires an extension taxonomy comes out of the report itself.
  • Complete filing packages: the submission leaves the platform as a validated package, ready for the receiving regulator or portal.

In practice

Azerion

From annual report to quarterly release

Azerion files ESEF Inline XBRL and publishes the designed annual report off the same figures — and brought out its Q3 2024 results from the same platform.

Want to see how this fits together?

  1. See the features in a demo — on an example report.
  2. Set up together: connect source data, port the brand style, load the taxonomy.
  3. Write, validate and file — from the same source.