> 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-next-step-and-reject.md). # 下一步并拒绝文档阅读[验证报告](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules/validation-report.md)后，报告会告诉您接下来该怎么做。您也可以拒绝该文档。 ## 接下来要做什么

**Assessment** 用一句话说明发票是否符合要求。**Next step** 区块会告诉您该怎么做： | 结果 | 下一步 | | ----------- | ----------------------------------- | | 至少有一个**错误** | 请发件人提供更正后的发票，或者拒绝该文档。更正后的发票属于一份新文档。 | | 只有**警告** | 您可以继续处理该文档。 | 报告末尾的按钮： * **Reject document**：打开拒绝对话框（见下文）。 * **Report (HTML)** 和 **Report (XML)**：下载报告，例如发送给供应商。 * **Close**（或 **Back to document**）：返回文档。 ## 拒绝文档

已填写报告中原因的 Reject document 对话框 — 原因会根据报告中的错误自动填写。您可以编辑该内容。

1. 在报告中，选择 **Reject document**。 2. 检查 **Reason**。DocBits 会根据报告中的错误填写原因。您可以编辑文本。 3. 选择 **Reject document** 进行确认。状态会变为 **Rejected**。原因会保存为备注，报告会保留在文档中。选择 **Cancel**，即可保持文档现状。 > 只有获准编辑文档的用户才能看到 **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/validation-next-step-and-reject.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.