> For the complete documentation index, see [llms.txt](https://guide.digicust.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.digicust.com/features/integrations/aeb.md).

# AEB

Digicust integrates natively with [AEB](https://www.aeb.com/de/index.php). Just upload customs cases to Digicust. Digicust processes the case and sends the filled out customs declaration to your AEB system.

Many of our clients use Digicust as a black box and just check warning messages within AEB before submitting the automatically created customs declaration to the authorities.

The AEB interface needs to be set up by AEB before getting started. If you are not using the interface already, ask your contact person at AEB or <support@aeb.com>.

### Setup

1. The setup is easy. Navigate to your execution strategy settings and select "Submission".<br>

   <figure><img src="/files/kI8ndu1v8pAJmC64rnFn" alt=""><figcaption><p>AEB seteup</p></figcaption></figure>
2. Customs cases are sent to AEB using REST protocol. Ask AEB for your API credentials. Then input the following:

| Field               | Description                                                         | Example                       |
| ------------------- | ------------------------------------------------------------------- | ----------------------------- |
| Client ident code   | Your AEB client ident code                                          | DIGICUST                      |
| Client name         | Your AEB client name                                                | DIGICUST                      |
| Client system ID    | Your AEB client system ID                                           | DEXTER                        |
| Endpoint            | The AEB API endpoint                                                | <https://rz3.aeb.de/test2ici> |
| Username            | Your AEB username                                                   | ASD                           |
| Password            | Your AEB password                                                   | \*\*\*\*\*                    |
| Profile             | Provide an AEB profile (similar to Digicust's execution strategies) | STD\_DE\_IMP                  |
| Organizational unit | Optional. Specify the organizational unit that you use within AEB.  |                               |

3. Save the execution strategy. Upload customs cases to said execution strategy and wait for cases to arrive in AEB.
4. The case should be filled-out and ready to hand in if Digicust has all information necessary. If not, try [Configure Execution Strategies](/guides/configure-execution-strategies.md) or set up [Rules & Templates](/features/rules-and-templates.md).

Happy automating with Digicust and AEB!

### Troubleshooting

If the AEB interface is not working as expected, do the following:

1. The AEB - Digicust interface is well-tested and in production with clients. However, in rare occasions it might happen that interface errors occur. Kindly forward any error messages to <support@digicust.com>. We are happy to help!


---

# 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://guide.digicust.com/features/integrations/aeb.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.
