> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/entwicklerdokumentationen-business-central-dhl-connector/dhl-connector-entwicklerdokumentation/pages-page-extensions-und-reports/zoll-pages.md).

# Zoll-Pages

## 72242967 SOUDHL Customs Declaration

**Type:** Card · **Source:** SOUDHL Customs Data · **UsageCategory:** None

Modale Zollerklärung für ein Paket. Die Page selbst legt keinen neuen Kopf an und löscht ihn nicht; `SOUDHL Customs Mgt` stellt den Datensatz bereit.

### Layout

* Export Type und optionale Export Description
* Invoice No.
* Postal Charges und Currency
* Shipper/Consignee Customs Reference
* Completed
* eingebetteter Customs-Lines-Part über Package ID und Order No.

### Aktionen

* `Generate Lines from Package` ruft `GenerateCustomsLines` auf und ersetzt die Positionen aus Package Lines.
* `Confirm Customs Data` validiert über Customs Mgt und setzt `Completed = true`.

Die Page wird manuell aus der Paketkarte oder automatisch modal aus `EnsureCustomsReadyForUpload` geöffnet.

## 72242968 SOUDHL Customs Lines Part

**Type:** ListPart · **Source:** SOUDHL Customs Line

Felder:

* Item No.
* Description
* Quantity
* Unit Price
* Unit Weight (kg)
* HS Code
* Country of Origin

## Fachlicher Grund

Zolldaten können nicht zuverlässig nur aus dem Auftrag abgeleitet werden: relevant sind tatsächlich gepackte Mengen, Netto-Gewicht, deklarierter Preis, Zolltarifnummer und Ursprung. Deshalb existiert ein eigener bestätigbarer Paket-Snapshot.

## Hintergrundjobs

Ein nicht interaktiver Prozess kann die modale Page nicht verwenden. Integrationen müssen Customs Data/Lines dann vorab vollständig validieren und bestätigen.


---

# 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.solutioo.de/entwicklerdokumentationen-business-central-dhl-connector/dhl-connector-entwicklerdokumentation/pages-page-extensions-und-reports/zoll-pages.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.