> 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-per-document-type.md).

# 每种文档类型的验证

管理员可针对每种文档类型决定 DocBits 是否验证收到的电子发票，以及检查未通过时是否阻止该文档。每项更改都会经过确认并写入[更改日志](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules/validation-change-log.md)。

> 只有**组织管理员**可以更改这些设置。其他用户只能只读查看该表，或无法看到该表。

## 表格

前往 **设置 → 电子文档 → 电子发票验证**。**规则和策略**选项卡首先显示 **每种文档类型的验证**表格。

<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>每种文档类型各占一行，包含已启用和阻止开关。示例组织。</p></figcaption></figure>

| 开关      | 功能                                                                                                                                                |
| ------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **已启用** | DocBits 会验证此文档类型的每份收到的电子发票，并保存[验证报告](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules/validation-report.md)。 |
| **阻止**  | 如果发现错误，则停止处理该文档，并将其状态设为 **错误**。关闭阻止后，DocBits 会保存报告并继续处理该文档。只有在**已启用**的情况下，才能开启**阻止**。                                                             |

如果某种文档类型设有子类型覆盖项，表格中会显示相关说明。

## 更改设置

1. 选择要更改的开关。
2. DocBits 会显示 **确认验证更改**，其中包含文档类型和更改内容，例如 *报价：已启用 → 开启*。

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-1a43d73798aba2e26e6e65db85f081d2133d98af%2Feinvoice-validation-confirm.png?alt=media" alt="确认验证更改对话框"><figcaption><p>每项更改都需要确认</p></figcaption></figure>

3. 阅读说明：\*\*已保存的报告不会更改。\*\*此更改仅适用于新的检查，包括重新启动文档处理时执行的检查。
4. 选择 **确认更改**，或选择 **取消**以保留原设置。

如果您没有相应权限，DocBits 会提示需要组织管理员，且不会进行任何更改。

## 相关页面

* [电子发票验证](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules.md)
* [更改日志](/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-setup.md)
* [验证报告](/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.md#enable-or-disable-e-invoice-validation)


---

# 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-per-document-type.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.