> For the complete documentation index, see [llms.txt](https://docs-fr.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-fr.docbits.com/administration-and-setup/settings/global-settings/document-types/edi/zugferd/zugferd-1-0.md).

# Mappage ZUGFeRD 1.0

## Aperçu

ZUGFeRD 1.0 était la version initiale du standard. Bien qu'elle soit ancienne, de nombreux documents utilisent encore ce format. DocBits offre un support complet pour l'extraction de données à partir des fichiers XML ZUGFeRD 1.0.

## Mappage des champs d'en-tête

### Identification de la facture

| Chemin ZUGFeRD CII                | Champ DocBits       | Champ Infor BOD    | Type   | Description                   |
| --------------------------------- | ------------------- | ------------------ | ------ | ----------------------------- |
| `ExchangedDocument/ID`            | `INVOICE_NUMBER`    | `DocumentID`       | STRING | Numéro de facture             |
| `ExchangedDocument/TypeCode`      | `INVOICE_TYPE_CODE` | `DocumentType`     | STRING | Code type de facture          |
| `ExchangedDocument/IssueDateTime` | `INVOICE_DATE`      | `DocumentDateTime` | DATE   | Date d'émission de la facture |

### Type et sous-type de document (piloté par TRA)

Parallèlement au `INVOICE_TYPE_CODE` brut, la XSLT TRANSFORMATION par défaut émet deux champs dérivés. ZUGFeRD 1.0 utilise le vocabulaire CII hérité, donc les XPaths diffèrent de la version 2.x :

| Champ DocBits      | Source (schéma 1.0)                                                                                                      | Logique                                                                    |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------- |
| `INVOICE_TYPE`     | `CrossIndustryDocument/HeaderExchangedDocument/TypeCode`                                                                 | UNCL 1001 `381` ou `261` → **Credit Note** ; tout autre code → **Invoice** |
| `INVOICE_SUB_TYPE` | `SpecifiedSupplyChainTradeTransaction/ApplicableSupplyChainTradeAgreement/BuyerOrderReferencedDocument/IssuerAssignedID` | Non vide → **Purchase Invoice** ; vide/absent → **Cost Invoice**           |

### Ventilation des taxes (classification par tranches)

Les blocs `ApplicableTradeTax` sont distribués sur trois tranches basées sur le taux (et non sur des index positionnels) : les champs au taux standard (`TAX_RATE` / `NET_AMOUNT` / `TAX_AMOUNT`) capturent les taux ≥ 19 ; les champs au taux réduit (`*_2`) capturent 0 < taux < 19 ; les champs au taux zéro (`*_3`) capturent taux = 0. Voir [Ventilation des taxes ZUGFeRD](/administration-and-setup/settings/global-settings/document-types/edi/zugferd.md#tax-breakdown-tier-classified) pour la liste complète des champs. (ZUGFeRD 1.0 utilise le vocabulaire CII hérité dans sa XSLT TRANSFORMATION, mais les règles de sélection de tranche ci-dessus sont identiques à 2.x.)

### Références de documents

| Chemin ZUGFeRD CII                    | Champ DocBits     | Champ Infor BOD   | Type   | Description                   |
| ------------------------------------- | ----------------- | ----------------- | ------ | ----------------------------- |
| `BuyerOrderReferencedDocument/ID`     | `PURCHASE_ORDER`  | `CustomerOrderID` | STRING | Numéro de bon de commande     |
| `ContractReferencedDocument/ID`       | `CONTRACT_NUMBER` | `ContractID`      | STRING | Référence du contrat          |
| `DespatchAdviceReferencedDocument/ID` | `DELIVERY_NOTE`   | `ShipmentID`      | STRING | Référence du bon de livraison |

### Informations fournisseur (vendeur)

| Chemin ZUGFeRD CII                                 | Champ DocBits        | Champ Infor BOD       | Type   | Description        |
| -------------------------------------------------- | -------------------- | --------------------- | ------ | ------------------ |
| `SellerTradeParty/ID`                              | `VENDOR_ID`          | `SupplierPartyID`     | STRING | ID fournisseur     |
| `SellerTradeParty/Name`                            | `VENDOR_NAME`        | `SupplierPartyName`   | STRING | Nom du fournisseur |
| `SellerTradeParty/PostalTradeAddress/Line1`        | `VENDOR_ADDRESS`     | `SupplierAddress1`    | STRING | Ligne d'adresse 1  |
| `SellerTradeParty/PostalTradeAddress/PostcodeCode` | `VENDOR_POSTAL_CODE` | `SupplierPostalCode`  | STRING | Code postal        |
| `SellerTradeParty/PostalTradeAddress/CityName`     | `VENDOR_CITY`        | `SupplierCity`        | STRING | Ville              |
| `SellerTradeParty/PostalTradeAddress/CountryID`    | `VENDOR_COUNTRY`     | `SupplierCountryCode` | STRING | Code pays          |

## Mappage des lignes d'articles

| Chemin ZUGFeRD CII                       | Champ DocBits  | Champ Infor BOD    | Type   | Description                    |
| ---------------------------------------- | -------------- | ------------------ | ------ | ------------------------------ |
| `AssociatedDocumentLineDocument/LineID`  | `POSITION`     | `LineNumber`       | STRING | Numéro de ligne                |
| `SpecifiedTradeProduct/BuyerAssignedID`  | `ITEM_NUMBER`  | `BuyerItemID`      | STRING | Numéro d'article de l'acheteur |
| `SpecifiedTradeProduct/Name`             | `DESCRIPTION`  | `ItemDescription`  | STRING | Description de l'article       |
| `BilledQuantity`                         | `QUANTITY`     | `InvoicedQuantity` | NUMBER | Quantité facturée              |
| `NetPriceProductTradePrice/ChargeAmount` | `UNIT_PRICE`   | `UnitPrice`        | AMOUNT | Prix unitaire net              |
| `LineTotalAmount`                        | `TOTAL_AMOUNT` | `ExtendedAmount`   | AMOUNT | Total de la ligne              |


---

# 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-fr.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.