> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/document-processing/e-documents/validation-rules.md). # E-Invoice Validation {% embed url="" %} The **E-Invoice Validation** page (**Settings → E-Documents → E-Invoice Validation**, path `/settings/einvoice-validation`; earlier called *Validation Rules*) controls how DocBits validates incoming e-invoices. It is based on the official **KoSIT XRechnung + ZUGFeRD** rule set plus the validator's in-house finding codes, and lets you override the severity of each rule for your organization. > This page is for **e-invoices** (XRechnung, ZUGFeRD, Factur-X). It is not the same as **Data Validation Rules**, which check extracted document fields. ## What is on this page
The E-Invoice Validation page with the table Validation for each document type

The E-Invoice Validation page. The tab Rules and policy starts with the table Validation for each document type. Example organisation.

| Topic | What it does | Who | | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------- | | [Validation setup and accepted versions](/administration-and-setup/settings/document-processing/e-documents/validation-rules/validation-setup.md) | The setup wizard, the accepted XRechnung versions, the accepted profiles and what each severity means. | Organisation administrators | | [Rule severities](/administration-and-setup/settings/document-processing/e-documents/validation-rules/validation-rule-severities.md) | The rule table: change the severity of each rule for your organisation. | Organisation administrators | | [Validation for each document type](/administration-and-setup/settings/document-processing/e-documents/validation-rules/validation-per-document-type.md) | Turn validation on (**Enabled**) and decide whether a failed check stops the document (**Blocking**). Every change needs a confirmation. | Organisation administrators | | [Change log](/administration-and-setup/settings/document-processing/e-documents/validation-rules/validation-change-log.md) | Every change of the settings: when, who, which rule, from → to. | Organisation administrators | | [The error screen for a rejected e-invoice](/administration-and-setup/settings/document-processing/e-documents/validation-rules/validation-error-screen.md) | What you see when you upload a wrong XML: the explanation, the faulty line and the next step. | Everyone who processes invoices | | [Validation report](/administration-and-setup/settings/document-processing/e-documents/validation-rules/validation-report.md) | What a user sees when an invoice fails: the findings in plain language. It opens from the document, not from this page. | Everyone who processes invoices | | [Next step and reject a document](/administration-and-setup/settings/document-processing/e-documents/validation-rules/validation-next-step-and-reject.md) | What to do after you read the report, downloads of the report, and **Reject document**. | Everyone who processes invoices | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.docbits.com/administration-and-setup/settings/document-processing/e-documents/validation-rules.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.