> 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-rule-severities.md).

# 规则严重性

每条验证规则都有一个严重性级别。您可以更改组织中每条规则的严重性。本页面属于 [电子发票验证](/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-49fe972c228828f7d8363711f93b3fcd0140f3b7%2Feinvoice-rule-table.png?alt=media" alt="验证规则表"><figcaption><p>包含每条规则严重性覆盖设置的完整规则表</p></figcaption></figure>

规则表列出了所有验证规则（总计超过 1,600 条）。您可以按 **Layer**、**Profile** 或 **Version** 筛选，也可以按代码或字段搜索。对于每条规则，您都可以通过下拉菜单覆盖 **Severity**，使其符合组织的政策——例如，将规则从 `ERROR` 调低为 `WARNING`，这样该规则就不会再拒绝文档。

\[FATAL]、\[ERROR]、\[WARNING] 和 \[INFO] 的含义请参阅[验证设置和接受的版本](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules/validation-setup.md#accepted-profiles-and-severity-model)。更改后的严重性也会显示在[验证报告](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules/validation-report.md)的 **Your organisation** 列中。


---

# 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-rule-severities.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.
