> 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/validation-setup.md).

# 验证设置和已接受的版本

本页介绍设置向导、已接受的 XRechnung 版本，以及 [电子发票验证](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules.md) 页面中已接受的配置文件。只有组织管理员可以更改这些设置。

## 验证设置

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-af7b13279778012f6df574e62a7282a6acfb6a12%2Feinvoice-setup-versions.png?alt=media" alt="验证设置和已接受的版本"><figcaption><p>验证设置和已接受的 XRechnung 版本</p></figcaption></figure>

**验证设置**卡片显示当前的验证配置文件（例如 *B2G — 公共部门接收方*）。点击 **编辑答案** 可重新运行设置向导，并更改要依据哪个标准进行验证。

## 已接受的 XRechnung 版本

**已接受的 XRechnung 版本**区域列出所有 XRechnung 版本。勾选你接受的版本——CustomizationID 不在此列表中的文档会在执行任何其他检查前被拒绝，并返回 `VAL-VERSION-NOT-ALLOWED`。列表为空表示“全部接受”。每个版本都会标记为 **当前**、**已弃用** 或 **已停止支持**，并显示其发布日期。

## 已接受的配置文件和严重级别模型 <a href="#accepted-profiles-and-severity-model" id="accepted-profiles-and-severity-model"></a>

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-c7b460b5516b1cbee6cae17d765d18169f9a171d%2Feinvoice-profiles-severity.png?alt=media" alt="已接受的配置文件和严重级别说明"><figcaption><p>已接受的配置文件，以及各严重级别的含义</p></figcaption></figure>

选择要接受的**配置文件**（BASIC WL、BASIC、EN 16931 / COMFORT、EXTENDED、XRECHNUNG (CIUS)），使用 **全部接受** / **清除**，然后点击 **保存**。

每条验证规则都有一个**严重级别**，用于决定规则触发后的处理方式：

| 严重级别        | 效果                                     |
| ----------- | -------------------------------------- |
| **FATAL**   | 立即停止处理。不再检查后续层；文档进入错误状态。               |
| **ERROR**   | 拒绝该文档。仍会显示该文档上的其他发现；如果已启用供应商通知，则会触发通知。 |
| **WARNING** | 显示在验证报告中，但文档会照常通过工作流处理。                |
| **INFO**    | 仅记录在审计日志中。不会影响用户，也不会拒绝文档。              |

### 向导会更改什么

页面下方的**验证设置**卡片会打开一个包含**编辑答案**选项的向导。该向导会替换组织的整套规则覆盖项。保存前，DocBits 会向你发出警告。请仔细检查**审核并应用**步骤。

下一步：[规则严重级别](/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)。


---

# 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/validation-setup.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.