GIR XML validator

GIR XML Validator

Validate GIR XML before export or review. The public GIR.WTF demo runs in the browser and checks XML syntax, GIR-style document structure, namespace presence, required technical fields and supported formats.

GIR.WTF handles the technical layer. The user and their advisers remain responsible for the underlying tax and legal positions, the reporting information and the final filing decisions.

Finance and tax professionals reviewing a GIR XML reporting workflow in a modern office

Validator demo

Validation points back to the technical issue.

Paste GIR XML or load the fictional sample, then run a browser-only technical check. The public validator helps users find missing input or format issues before export, while keeping the boundary clear: it validates technical structure, not a tax position.

Missing required technical fieldReporting period, filing entity and jurisdiction checks.

Belgian technical validationBelgian checks stay visible without claiming filing approval.

Public GIR XML ValidatorProcessed in your browser
Limit 20,000 chars

Demonstration data only: the sample uses a fictional group and entity.

Technical validation result

Valid technical structure

The public validator found a readable GIR-style XML structure, expected namespace, core fields and supported technical formats.

DTD and external entity guardNo DTD or external entity declaration detected.

XML syntaxOpening and closing elements form a readable XML structure.

GIR document structureRoot element gir:GloBEInformationReturn is recognised as a GIR-style XML root.

GIR namespace presenceThe root element exposes a GIR/OECD-style namespace declaration.

Required technical fieldsReporting period, filing entity and jurisdiction elements are present.

Date formatAvailable reporting-period dates use YYYY-MM-DD.

Jurisdiction formatAvailable jurisdiction values use a two-letter uppercase format.

GIR Studio validation dialog showing missing field findings before GIR XML export
Protected Studio check dialog: missing fields are translated into reviewable next steps before export.

What GIR.WTF does

Technical execution layer, not a tax opinion.

GIR.WTF combines guided GIR XML generation, browser-based technical validation, schema mapping, Belgian technical checks and XML export in one focused product workflow.

01

Public technical validation

The public validator is a lightweight technical check for XML syntax, GIR-style structure, namespace presence and core technical fields. It is product proof, not a full authority validator.

02

Required technical fields

Missing technical fields and invalid formats are surfaced before the user treats the XML package as ready for review.

03

Validation messages with context

A useful validation message should point to the technical issue, the relevant input and the next item to review. It should not pretend to decide a tax position.

04

Client-side public demo

The public demo runs client-side in the browser and does not send pasted XML to GIR.WTF. Full OECD GIR XSD validation and Belgian authority validation-rule execution are reserved for the controlled workflow.

Official sources

Built around authoritative technical materials.

GIR.WTF is implementation software. OECD and FPS Finance remain the authoritative sources for the GIR XML schema, Belgian materials and official filing context.

Finance reporting controls reviewed on a laptop and printed documents

Practical questions

Choose the path that matches the work in front of you.

Each focused GIR XML page starts from a concrete implementation problem: generating XML, validating structure, mapping the OECD schema, preparing Belgian context or reviewing validation-error behaviour.

Check XML syntax before XSD work

Malformed XML needs to be caught first because schema or Belgian validation checks are not meaningful until the document can be parsed.

Explain missing technical fields

The public demo points missing reporting-period, filing-entity and jurisdiction data back to the source input that needs review.

Separate demo checks from full validation

The public validator is intentionally limited; controlled workflows can go deeper into OECD GIR XSD and Belgian validation-rule execution.

Continue to the related workflow

Implementation evidence

Reviewed against technical source material.

The public pages show the same boundary as the product: official sources define the schema and Belgian filing context; GIR.WTF provides the technical workflow around structured input, validation messages and export preparation.

Workflow coverage

Focused GIR XML pages answer concrete implementation questions.

The hub, generator, validator, schema, Belgium and validation-error pages each connect practical implementation questions with source-linked context and clear next workflow steps.

Technical source review

OECD GIR XML schema 2026 planning stays source-led.

Teams preparing 2026 GIR XML work should verify the current OECD schema and user-guide source first. GIR.WTF adds a guided implementation layer around mapping, validation and export.

Belgian material review

Belgian GIR XML materials are treated as technical inputs.

FPS Finance forms, tools, XSD and validation-rule materials are linked as official sources. GIR.WTF keeps Belgian implementation checks separate from tax advice or filing guarantees.

Validation evidence

Public validation messages point to reviewable issues.

The browser demo exposes missing technical fields, malformed XML, unsupported document shape and format issues without sending pasted XML to the server.

Workflow coverage

High-intent GIR/GIRNOT workflows link back to the hub.

Generator, validator, schema, Belgian validation rules, GIRNOT Belgium and MyMinfin notification preparation all resolve into the central GIR XML workflow.

GIR XML workflow

One product, focused technical pages.

The GIR XML hub connects the practical implementation paths: generation, validation, schema readiness, Belgian technical context, GIRNOT, MyMinfin and validation-error detail.

Related implementation questions

GIR/GIRNOT paths connected to this hub.

These pages cover the common entry points for teams looking for GIR XML validation errors, OECD schema implementation, Belgian validation rules, GIRNOT and MyMinfin notification preparation.

FAQ

Direct answers for GIR XML implementation.

What does the GIR XML validator check?

The public demo checks supported XML syntax, GIR-style document structure, namespace presence, required fields and basic formats before XML export or review.

Does the public validator run full OECD or Belgian XSD validation?

No. The public demo is deliberately limited and client-side. Full OECD GIR XSD validation and Belgian authority validation-rule execution are not claimed by the public demo.

Does technical validation guarantee acceptance?

No. Technical validation does not guarantee authority acceptance or correctness of the reporting position.

Portal access

Prepare GIR XML without manual XML editing.

Request access to the GIR portal. The first step is technical GIR/GIRNOT scope, data-gap and XML-readiness intake without submitting confidential production data through the public form.

GIR XML generatorGIR XML validatorNo tax or legal advice