> 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.md).
# 电子文档
DocBits 会根据官方标准——**XRechnung**、**ZUGFeRD** 和 **Factur-X**——验证收到的电子发票（e-invoice），并将发现的问题转交给相应的处理人员。**电子文档**设置组（位于**文档处理**下）包含以下页面：
* [**电子发票验证**](/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-report.md) — 发票未通过验证时用户会看到的内容：通俗易懂的问题说明、后续步骤，以及拒绝文档的选项。
* [**按文档类型验证**](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules/validation-per-document-type.md) — 管理员可按文档类型启用验证并设置是否阻止处理，同时查看变更日志。
* [**通知路由**](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/notification-routing.md) — 将验证问题分配给负责处理的 AI Workforce 代理。
这些设置共同决定收到的**电子发票中哪些情况算作问题**，以及**由谁处理**。
## 启用或停用电子发票验证
只有在**为文档类型启用电子发票验证**后，电子文档下的两个页面才会生效。开关位于文档类型本身，而不在电子文档菜单中。
前往**设置 → 文档类型 → 发票 → 高级设置**，然后打开**电子发票验证**部分。
---
# 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.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.
