> 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/administration-and-setup/settings/global-settings/document-types/edi/zugferd/zugferd-1-0.md).

# ZUGFeRD 1.0 Mapping

## Overview

ZUGFeRD 1.0 was the initial version of the standard. While it is older, many documents still use this format. DocBits provides full support for extracting data from ZUGFeRD 1.0 XML files.

## Header Field Mapping

### Invoice Identification

| ZUGFeRD CII Path                  | DocBits Field       | Infor BOD Field    | Type   | Description        |
| --------------------------------- | ------------------- | ------------------ | ------ | ------------------ |
| `ExchangedDocument/ID`            | `INVOICE_NUMBER`    | `DocumentID`       | STRING | Invoice number     |
| `ExchangedDocument/TypeCode`      | `INVOICE_TYPE_CODE` | `DocumentType`     | STRING | Invoice type code  |
| `ExchangedDocument/IssueDateTime` | `INVOICE_DATE`      | `DocumentDateTime` | DATE   | Invoice issue date |

### Document Type & Sub-Type (TRA-driven)

Alongside the raw `INVOICE_TYPE_CODE`, the default TRANSFORMATION XSLT emits two derived fields. ZUGFeRD 1.0 uses the legacy CII vocabulary, so the XPaths differ from 2.x:

| DocBits Field      | Source (1.0 schema)                                                                                                      | Logic                                                                    |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------ |
| `INVOICE_TYPE`     | `CrossIndustryDocument/HeaderExchangedDocument/TypeCode`                                                                 | UNCL 1001 `381` or `261` → **Credit Note**; any other code → **Invoice** |
| `INVOICE_SUB_TYPE` | `SpecifiedSupplyChainTradeTransaction/ApplicableSupplyChainTradeAgreement/BuyerOrderReferencedDocument/IssuerAssignedID` | Non-empty → **Purchase Invoice**; empty/missing → **Cost Invoice**       |

### Tax Breakdown (Tier-classified)

`ApplicableTradeTax` blocks are distributed across three rate-based tiers (not positional indexes): standard-rate fields (`TAX_RATE` / `NET_AMOUNT` / `TAX_AMOUNT`) capture rate ≥ 19; reduced-rate fields (`*_2`) capture 0 < rate < 19; zero-rate fields (`*_3`) capture rate = 0. See [ZUGFeRD Tax Breakdown](/administration-and-setup/settings/global-settings/document-types/edi/zugferd.md#tax-breakdown-tier-classified) for the full field list. (ZUGFeRD 1.0 uses the legacy CII vocabulary in its TRANSFORMATION XSLT, but the tier-selection rules above are identical to 2.x.)

### Document References

| ZUGFeRD CII Path                      | DocBits Field     | Infor BOD Field   | Type   | Description             |
| ------------------------------------- | ----------------- | ----------------- | ------ | ----------------------- |
| `BuyerOrderReferencedDocument/ID`     | `PURCHASE_ORDER`  | `CustomerOrderID` | STRING | Purchase order number   |
| `ContractReferencedDocument/ID`       | `CONTRACT_NUMBER` | `ContractID`      | STRING | Contract reference      |
| `DespatchAdviceReferencedDocument/ID` | `DELIVERY_NOTE`   | `ShipmentID`      | STRING | Delivery note reference |

### Supplier (Seller) Information

| ZUGFeRD CII Path                                   | DocBits Field        | Infor BOD Field       | Type   | Description    |
| -------------------------------------------------- | -------------------- | --------------------- | ------ | -------------- |
| `SellerTradeParty/ID`                              | `VENDOR_ID`          | `SupplierPartyID`     | STRING | Supplier ID    |
| `SellerTradeParty/Name`                            | `VENDOR_NAME`        | `SupplierPartyName`   | STRING | Supplier name  |
| `SellerTradeParty/PostalTradeAddress/Line1`        | `VENDOR_ADDRESS`     | `SupplierAddress1`    | STRING | Address line 1 |
| `SellerTradeParty/PostalTradeAddress/PostcodeCode` | `VENDOR_POSTAL_CODE` | `SupplierPostalCode`  | STRING | Postal code    |
| `SellerTradeParty/PostalTradeAddress/CityName`     | `VENDOR_CITY`        | `SupplierCity`        | STRING | City           |
| `SellerTradeParty/PostalTradeAddress/CountryID`    | `VENDOR_COUNTRY`     | `SupplierCountryCode` | STRING | Country code   |

## Line Item Mapping

| ZUGFeRD CII Path                         | DocBits Field  | Infor BOD Field    | Type   | Description         |
| ---------------------------------------- | -------------- | ------------------ | ------ | ------------------- |
| `AssociatedDocumentLineDocument/LineID`  | `POSITION`     | `LineNumber`       | STRING | Line number         |
| `SpecifiedTradeProduct/BuyerAssignedID`  | `ITEM_NUMBER`  | `BuyerItemID`      | STRING | Buyer's item number |
| `SpecifiedTradeProduct/Name`             | `DESCRIPTION`  | `ItemDescription`  | STRING | Item description    |
| `BilledQuantity`                         | `QUANTITY`     | `InvoicedQuantity` | NUMBER | Billed quantity     |
| `NetPriceProductTradePrice/ChargeAmount` | `UNIT_PRICE`   | `UnitPrice`        | AMOUNT | Net unit price      |
| `LineTotalAmount`                        | `TOTAL_AMOUNT` | `ExtendedAmount`   | AMOUNT | Line total          |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/edi/zugferd/zugferd-1-0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.