> 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/adding-payee-advances.md).

# Adding Payee Advances

### Here is how to input payee advances

Revelator supports two ways of adding advances:

1. On the Contract level 
2. On the Payee level.<br>

**1. Contract Level: Input an advance to the Payee**&#x20;

Option 1: Treat the contract advance as a payment transaction to the Payee:

* After a Payee has been created by being added to a Contract&#x20;
* Go to Royalties > Payees > and Select your Paye
* Click on Payee > Transactions > Add transaction > Payment&#x20;
* Enter the advance payment as a positive amount AND select the contract from the Associated contract field

Option 2: Use the contract advance as the Payee’s opening balance:

* On the Contract, enter the Payee advance as a negative amount in the Payee's Starting balance field

**2. Payee Level: Input a general advance to the Payee only**&#x20;

* After a Payee has been created by being added to a Contract&#x20;
* Go to Royalties > Payees and Select your Payee
* Click on Payee > Transactions > Add transaction > Payment&#x20;
* Enter the advance payment as a positive amount and save

<br>


---

# 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/adding-payee-advances.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.