Is your XML file sound?
Drop your disclosure file here – it is checked against the rules of the format right away, and you see, line by line, where something does not fit. Free, as often as you like.
Fix it yourself
The Disclosure XML Editor shows the same findings where they arise – and you change them there, without writing XML.
See the editorHave it done
Send us your report as Word, Excel or PDF – you get the finished, checked XML file back. Fixed price by size, from three working days.
See the pricesWhat is checked – and what is not
Structure, nesting and attribute values are checked: whether the elements belong to the format, whether they sit in the right place and whether the values are permitted. What is not checked is whether the figures are right or whether you have disclosed everything you must – that stays with you and your tax adviser. Only the response on submission is binding.
The nine kinds of error the format knows
The disclosure format is strict: it prescribes which elements exist, in what order they appear, how often, and which values their attributes may take. Every finding falls into one of these nine classes – here is what they mean.
- 1Not well-formed
- The file is not valid XML – a tag is unclosed, a quotation mark is missing, an ampersand sits unescaped in the text. The checker reports this first, with line and column, because it cannot reach the content otherwise.
- 2Wrong root element
- The Federal Gazette and the Company Register expect different root elements. A file made for one will not pass at the other – the most common reason a “finished” file is rejected.
- 3Unknown element
- An element the format does not have. Usually introduced by other tools that invent their own names, or by pasting from HTML.
- 4Not allowed here
- The element exists, but not in this position. A paragraph inside a table cell, for instance, or a heading inside the announcement header.
- 5Wrong order
- The announcement header requires logo, company name, registered office, title, subtitle – in exactly that order. Swap two and you have formally valid XML and a rejected submission.
- 6Too often, too rarely, missing
- Company name exactly once, subtitle at most once, logo at most once. At most nine images in the whole document. Such limits are part of the schema and are enforced on submission.
- 7Text where none belongs
- Some elements may contain only other elements, no text of their own. A single space between two tags is enough to break this – and it is invisible in an editor.
- 8Invalid attribute value
- Attributes accept only certain values: alignment only left, center, right; vertical only top, middle, bottom; emphasis only Hauptgruppe, Gruppe, Untergruppe, Zwischensumme, Summe, Hauptposition, Z-Kopf or keine. Images only as GIF or JPG. “Left” with a capital L is already wrong.
- 9Wrong namespace
- Every element must be in the format’s namespace, not just the root element. An inconspicuous xmlns="" on a paragraph or a table takes the element out – name and structure are right, and the file is still rejected. An editor shows nothing of this, only the source does.
Common questions
What does the check cost?
Nothing. No sign-up, no limit – you can check the same file as often as you like until it passes.
Is my file uploaded?
No. The check runs entirely in your browser; the document does not leave your computer. Only five numbers about the check itself are transmitted – file size, character and element count, result, target. No content, no file name, no IP address, no cookie. Open your browser’s network panel and you will see exactly that.
Are these the same rules the Federal Gazette applies?
They are the rules of the published schema: structure, nesting, order and permitted attribute values – the same rules the Disclosure XML Editor applies. Only the response on submission is binding, but what passes here will not fail there on structure.
Do you check whether my figures are correct?
No. What is checked is the file, not the financial statements. Whether the balance sheet adds up, or whether you have disclosed everything you must, is for you and your tax adviser. It is expressly not a statutory audit under § 316 HGB.
Federal Gazette or Company Register – which target?
Each expects a different root element. The checker detects it from your file and sets the target accordingly; you can switch it above if you want to check against the other one.
My file has findings – what now?
Every finding names the line and the path within the document. Small things you can fix in any text editor. If you would rather not: the Disclosure XML Editor shows the same findings where they arise – or send us the report as Word or Excel and get the finished file back.