> 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/faktura.md).

# FatturaPA：在发票行上显示属性

FatturaPA 是意大利电子发票格式。本页介绍如何在更改映射或发票预览之前检查行属性，例如采购订单编号。**检查当前生效的映射之前，请勿添加第二个 `PURCHASE_ORDER` 列：当前 Sandbox 映射中已经包含一个。**

## 查找三个 FatturaPA 文件

打开 **Settings → Document Types → E-Doc**，选择 **Invoice**，然后展开 **FATTURAPA**。当前列表中有三个不同的文件：

* **TRANSFORMATION (XSLT)** 读取源 FatturaPA XML，并生成规范化的发票数据。
* **PREVIEW (XSLT)** 根据这些数据生成可视化的 HTML/PDF 风格发票预览。
* **EXTRACTION PATHS (JSON)** 将规范化后的值映射到 DocBits 字段和表格列。

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-41e20b4d037818ee9c95cccc7579ac810d910fdb%2Fdbdc-173-fatturapa-list-en.png?alt=media" alt="English Sandbox E-Doc settings showing FATTURAPA with Transformation, Preview and Extraction Paths"><figcaption><p>英文 Sandbox 中当前的 FATTURAPA 文件列表。</p></figcaption></figure>

## 检查提取的行值

打开 **EXTRACTION PATHS (JSON)**。在生效版本中，找到 `tables` 数组及其中的 `columns`。Sandbox 当前显示的版本已包含 `{"name": "PURCHASE_ORDER", "path": "PURCHASE_ORDER"}`。编辑前，请在真实测试发票中检查该值。如果需要添加其他属性，请先在规范化数据中确认其值，然后在草稿版本中添加一个不同的列名及对应路径。

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-3f481eb9ad19e570677a6c6ad5da6d6e799424f5%2Fdbdc-173-fatturapa-json-en.png?alt=media" alt="FATTURAPA Extraction Paths JSON with active version and an existing PURCHASE_ORDER table column"><figcaption><p>生效的 JSON 提取映射中已包含采购订单列。</p></figcaption></figure>

## 仅在需要时更改转换或预览

如果缺少规范化后的值，请检查 **TRANSFORMATION (XSLT)** 以及应生成该值的源 XML 路径。此处的更改会影响后续映射和预览步骤所使用的数据。如果提取的值正确，但未显示在可视化发票中，请检查 **PREVIEW (XSLT)** 以及该模板中的相关表格行。这两个 XSLT 文件的用途不同。

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-050de0c981f7857bcfe4dbc64b9d0d5d6db1d2e2%2Fdbdc-173-fatturapa-transformation-en.png?alt=media" alt="FATTURAPA active Transformation XSLT producing normalized INVOICE data"><figcaption><p>转换会读取源 XML 并生成规范化的发票字段。</p></figcaption></figure>

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-8b2d1c92ec0bebd25acb383e99405689ee93562f%2Fdbdc-173-fatturapa-preview-en.png?alt=media" alt="FATTURAPA active Preview XSLT with HTML output and invoice table styles"><figcaption><p>预览控制发票的可视化输出。</p></figcaption></figure>

使用版本卡片上的铅笔图标准备更改。检查草稿，并使用一张有代表性的 FatturaPA 发票通过 **Preview** 进行预览。截图展示的是当前生效版本；在本次 Sandbox 会话中，没有保存草稿，也没有运行预览测试。

此前关于所有 E-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/global-settings/document-types/edi/faktura.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.
