> 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/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules.md).

# 电子发票验证

{% embed url="<https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/einvoice-validation/v1/en.mp4>" %}

**电子发票验证**页面（**Settings → E-Documents → E-Invoice Validation**，路径 `/settings/einvoice-validation`；早期称为 *Validation Rules*）用于控制 DocBits 如何验证收到的电子发票。该功能基于官方 **KoSIT XRechnung + ZUGFeRD** 规则集，以及验证器内部的发现代码，并允许您为所在组织覆盖每条规则的严重级别。

> 此页面适用于**电子发票**（XRechnung、ZUGFeRD、Factur-X）。它不同于**数据验证规则**，后者用于检查提取出的文档字段。

## 此页面包含的内容

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-b04a0a12110506714c8f04f3987a66d1a1636b5b%2Feinvoice-validation-settings.png?alt=media" alt="电子发票验证页面，其中包含按文档类型验证的表格"><figcaption><p>电子发票验证页面。<strong>Rules and policy</strong>标签页以<strong>Validation for each document type</strong>表格开头。示例组织。</p></figcaption></figure>

| 主题                                                                                                                                    | 功能                                                        | 适用对象      |
| ------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- | --------- |
| [验证设置和接受的版本](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules/validation-setup.md)               | 设置向导、接受的 XRechnung 版本、接受的配置文件，以及各严重级别的含义。                 | 组织管理员     |
| [规则严重级别](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules/validation-rule-severities.md)         | 规则表：更改所在组织每条规则的严重级别。                                      | 组织管理员     |
| [按文档类型验证](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules/validation-per-document-type.md)      | 启用验证（**Enabled**），并决定检查失败时是否阻止文档（**Blocking**）。每次更改都需要确认。 | 组织管理员     |
| [更改日志](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules/validation-change-log.md)                | 每次设置变更的记录：时间、操作人、规则以及变更前 → 变更后。                           | 组织管理员     |
| [被拒绝电子发票的错误屏幕](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules/validation-error-screen.md)      | 上传错误 XML 时显示的内容：说明、出错行和后续步骤。                              | 所有处理发票的人员 |
| [验证报告](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules/validation-report.md)                    | 发票验证失败时用户看到的内容：以通俗语言说明发现的问题。报告从文档中打开，而不是从此页面打开。           | 所有处理发票的人员 |
| [后续步骤和拒绝文档](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules/validation-next-step-and-reject.md) | 阅读报告后的操作、报告下载，以及 **Reject document**。                     | 所有处理发票的人员 |


---

# 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/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules.md?ask=<question>&goal=<user_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.