> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/integrations/integrations/cash/set-up-cash.md).

# Set up Cash

Connect **OutSmart** to **Cash** before you configure imports or exports.

You need a dedicated API user from your Cash environment.

{% stepper %}
{% step %}

### Create a Cash API user

Create a dedicated API user in your Cash environment.

Keep the **email address** and **password** available.

Use the Cash integration manual on the settings page if you need the exact steps.
{% endstep %}

{% step %}

### Open Software integrations

Go to **Settings → Software integrations**.

Open **Cash**.

Open **Settings**.
{% endstep %}

{% step %}

### Open the Cash login screen

If the integration is not connected yet, the login fields appear.

If you already connected before, the login fields stay available at the top.
{% endstep %}

{% step %}

### Enter the Cash login details

Enter your **Relation code**.

Then enter the **Email address** and **Password** of the Cash API user.

Click **Submit**.
{% endstep %}

{% step %}

### Check the connection

If the credentials are correct, OutSmart opens the Cash settings.

If not, you see **Gegevens API gebruiker niet geldig**.
{% endstep %}

{% step %}

### Choose the administration

Select the **Administration** you want to sync.

This decides which Cash company OutSmart uses.
{% endstep %}

{% step %}

### Configure imports and exports

Choose which data should move into OutSmart.

Then choose which work orders should move out to Cash.
{% endstep %}

{% step %}

### Save the setup

Click **Save**.

Your connection details and settings are then stored.
{% endstep %}
{% endstepper %}

### Before you save

Check these points first:

* the selected administration is the correct one
* the API user still exists and is active in Cash
* the relation code, email address, and password are correct

{% hint style="info" %}
The relation code is your Cash account number.
{% endhint %}

### Frequently asked questions

<details>

<summary>Where do I find my Cash relation code?</summary>

The relation code is your account number in Cash.

You can find it in your Cash environment or ask Use It Group support.

</details>

<details>

<summary>What is an API user in Cash?</summary>

It is a user account for system-to-system communication.

Create it in the Cash administration settings.

Use the Cash integration manual on the settings page for the exact steps.

</details>

<details>

<summary>Can I connect more than one administration?</summary>

No.

The integration works with one administration at a time.

</details>

<details>

<summary>What happens if the credentials are wrong?</summary>

OutSmart shows **Gegevens API gebruiker niet geldig**.

Check the relation code, email address, and password, then try again.

</details>

<details>

<summary>How do I update the credentials later?</summary>

Open the Cash settings again.

Enter the new credentials in the login fields at the top.

Then click **Submit**.

</details>

### Related topics

* [**Cash**](/integrations/integrations/cash.md)
* [**What is Cash?**](/integrations/integrations/cash/what-is-cash.md)
* [**Set up a software integration**](/integrations/integrations/set-up-a-software-integration.md)


---

# 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://knowledge.out-smart.com/integrations/integrations/cash/set-up-cash.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.