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

# Riege Scope

Digicust integrates natively with Riege's [Scope](https://www.riege.com/). Just upload customs cases to Digicust. Digicust processes the case and sends the filled out customs declaration to your Scope system.

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

The Scope interface needs to be set up by Riege before getting started. If you are not using the interface already, ask your contact person at Riege.

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

   <figure><img src="/files/NoOLV8QW1tXXxg4m7EpB" alt=""><figcaption></figcaption></figure>

2. Customs cases are sent to Scope using SFTP. Ask Scope for your API credentials. Then input the following:<br>

   | Field         | Description               | Example             |
   | ------------- | ------------------------- | ------------------- |
   | DNS-Name      | SFTP Server               | ftp.XXX.riege.com   |
   | Port          | SFTP Port                 | 22                  |
   | Username      | SFTP Username             | XXX-scin-live       |
   | Password      | SFTP password             | \*\*\*\*\*\*\*\*    |
   | Inbound       | SFTP Path                 | ftp/incoming        |
   | Organisation  | Scope Organisation        | XXX                 |
   | Partner Code  | Scope Partner Code        | XXX                 |
   | Branch        | Scope Branch              |                     |
   | Configuration | Scope Configuration       | Standard            |
   | User ID       | Usually email of the user | <someone@domain.de> |
   | Template      | Scope template            |                     |

3. Save the execution strategy. Upload customs cases to said execution strategy and wait for cases to arrive in Scope.

4. The case should be filled-out and ready to hand in if Digicust has all information necessary. If not, try [Configure Execution Strategies](https://guide.digicust.com/guides/configure-execution-strategies) or set up [Rules & Templates](https://guide.digicust.com/features/rules-and-templates).

Happy automating with Digicust and Scope!

#### &#x20;  <a href="#troubleshooting" id="troubleshooting"></a>


---

# 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/riege-scope.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.