> For the complete documentation index, see [llms.txt](https://docs.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dispel.com/documentation/documentation-zh/ji-cheng-yu-guan-li/billing/delivery-and-acceptance-documentation.md).

# 交付与验收文档

Dispel 生成两份合同文件——交付证明和验收证明

## 概览

当 Dispel 服务期生效时，Dispel 会出具一份交付证明，记录已交付的内容及交付日期。当您的组织确认收到后，Dispel 会生成一份验收证明，记录该确认。

**Dispel 提供的内容**

* 一个 **交付证明**，在服务期开始日期出具，并发送电子邮件给指定的账单联系人。
* 一个 **验收证明**，当具有账单授权的用户在 Dispel 客户门户中确认交付时生成——或者，如果在 30 天内未收到确认，则根据《企业订阅协议》的默示接受条款出具。
* 每份文件都打印有文件完整性功能（SHA-256 载荷哈希、RFC 3161 时间戳令牌）和验证 URL。

{% hint style="info" %}
交付证明和验收证明与您的发票是分开的。它们用于证明服务已交付并已被接受；发票是用于付款的文件。
{% endhint %}

#### 交付证明

Dispel 会在服务期开始日期生成交付证明，并通过电子邮件发送给指定的账单联系人。

#### 验收证明

当具有账单授权的用户点击时，Dispel 会生成验收证明 **确认** 在 Dispel 客户门户中。如果在服务期开始后 30 天内未收到确认，则会根据默示接受条款出具验收证明。

## 常见问题

<details>

<summary><strong>这些文件与我的发票有什么不同？</strong></summary>

交付证明是 Dispel 对服务已交付的记录。验收证明是您组织对服务已收到的记录。

</details>

<details>

<summary><strong>我在哪里查看 Dispel 为我的账户签发的文件？</strong></summary>

在 Dispel 客户门户的“账单”页面上，与相应的服务期并列显示。

</details>

<details>

<summary><strong>我如何更改谁可以批准验收证明？</strong></summary>

任何您 Dispel 账户中的组织管理员都可以批准验收证明。

</details>


---

# 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.dispel.com/documentation/documentation-zh/ji-cheng-yu-guan-li/billing/delivery-and-acceptance-documentation.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.
