> For the complete documentation index, see [llms.txt](https://docs.revelator.com/pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revelator.com/pro/payments/exporting-payee-balances-for-external-payout-providers.md).

# Exporting Payee Balances for External Payout Providers

* You can download a report with all your Payees and their Balances from the Payees page[![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/69068476747/original/MKcZcqg6bjp4lHeTc5EJclAypPMt_WWaGA.png?1678033518)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/69068476747/original/MKcZcqg6bjp4lHeTc5EJclAypPMt_WWaGA.png?1678033518)
* You can then use this data to process Payouts in an external Payout Provider
* Once all your payments have been processed, do not forget to update your Revelator account with this information so that your payees' balances are updated accordingly. If you do not do this, then your payees' balances will not reflect any payments you have made to them and you will wind up paying them more than they are owed the next time around.
* We provide a template to batch import multiple Payment transactions. You can download this template from Payments > Activity > top right-side menu:

<figure><img src="https://3676652645-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MEiW8xrgQlP3-v0URKN%2Fuploads%2FTkv2IMseOAx3Io7tay8J%2Fimage.png?alt=media&amp;token=28805612-804d-465d-87b4-bfe8e7249682" 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://docs.revelator.com/pro/payments/exporting-payee-balances-for-external-payout-providers.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.
