> 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/global-settings/document-types/edi.md).

# 电子单据

{% embed url="<https://youtu.be/AxrHNEmmXtg>" %}
DocBits 电子发票教程：处理 XRechnung / ZUGFeRD (Factur-X)、验证数据并自动化工作流
{% endembed %}

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-5d4f8542a3e3b1307da6e86831d03718db7e7b2e%2FBildschirmfoto%202024-05-08%20um%2009.49.21.png?alt=media" alt=""><figcaption></figcaption></figure>

#### 概览

在 DocBits 中，EDI 设置提供了用于定义和管理 EDI 消息结构与格式的工具，这些消息对应于各种文档类型，例如发票或采购订单。这些设置支持自定义 EDI 消息，以符合不同贸易伙伴和行业的特定标准与要求。

#### 主要功能和选项

1. **EDI 配置元素**：
   * **结构描述符**：定义 EDI 文档的基本结构，包括使 EDI 文档有效所需的分段顺序、必填字段和限定符。
   * **转换**：指定将文档数据转换为 EDI 格式消息时应用的转换规则。这通常包括指定文档字段到 EDI 分段和元素的映射。
   * **预览**：允许管理员查看转换后的 EDI 消息效果，以便在传输前确保准确性。
   * **提取路径**：显示用于从文档中提取值的路径，这些值随后用于填充 EDI 消息。
2. **XSLT 编辑器**：
   * 用于编辑和验证转换过程中使用的 XSLT（可扩展样式表语言转换）。XSLT 是一种功能强大的语言，专为将 XML 文档转换为其他 XML 文档或 HTML、文本等其他格式，甚至其他 XML 结构而设计。

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-0158be01aff262cf2a79dd6e20a8adda35b04349%2FBildschirmfoto%202024-05-08%20um%2009.49.59.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/global-settings/document-types/edi.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.