> For the complete documentation index, see [llms.txt](https://wiki.dieagenturverwaltung.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/integrationen/pleo.md).

# Pleo

The Pleo integration can be found under Settings > Integrations.

Die Agenturverwaltung integrates the virtual card provider Pleo in the following bidirectional way:\
\
Jobs and cost categories from Die Agenturverwaltung are synchronized with Pleo as tags.

Employees can then scan/upload a receipt for their expense in the Pleo app and directly assign the job, the type of billability (cost type) and the cost category.

If receipts are later exported from Pleo, they are imported into Die Agenturverwaltung and there - if filled in in the Pleo app - automatically assigned to the corresponding job and the cost category.

<figure><img src="https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-La4YdZ1Gw5iHapqZfIo%2Fuploads%2FkjL6U1mevQZOYy801bwy%2FBildschirmfoto%202025-03-24%20um%2014.11.11.png?alt=media&amp;token=17c4ce24-dbba-4bee-8e22-3508768676f4" alt=""><figcaption></figcaption></figure>

### Post Pleo like a cash journal

In the Pleo settings of Die Agenturverwaltung a default contra account / creditor can be entered.\
If this is stored, the creditor number of the respective supplier contact is not posted, but the contra account stored here.

<figure><img src="https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-La4YdZ1Gw5iHapqZfIo%2Fuploads%2FqxwbEz2avgq3vkD2WNdP%2FBildschirmfoto%202025-03-24%20um%2014.11.17.png?alt=media&amp;token=340a2326-7125-4dc1-820d-80e4a195fca1" alt=""><figcaption></figcaption></figure>


---

# 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://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/integrationen/pleo.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.
