> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/readme-1/work-with-accounts/processing-payments-ar.md).

# Process payments to account

1. Look up the customer. Refer to [**Look up customers**](/readme-1/work-with-customers/customers-looking-up.md) for more information.
2. Tap **Customers** | **Payment to Account**. On the right of the Payment to Account screen, you can see the following account information:

* **Total Balance** shows the total amount of all open (unpaid) invoices.
* **Total Credit** shows the total amount of any unapplied (available) credit memos.
* **Balance Due** shows the difference between Total Balance and Total Credit (e.g., Total Balance - Total Credit = Balance Due).

{% hint style="info" %}
A credit memo is created if the customer returns an item (or items) that were purchased on account, or if the customer has accidentally overpaid an invoice. Credit memos can only be applied to open invoices.
{% endhint %}

3. Do one of the following:

* If the customer wants to pay for specific open invoices, tap the invoices to select them.
* If the customer wants to pay for all open invoices, tap the **Pay all** button.

4. (Optional) Select **Apply Credit** to apply any available credit memos to the selected invoices. The total amount of the applied credit memos displays in the **Applied Credit** field.

{% hint style="info" %}
If you do not select **Apply Credit**, the credit memos will remain available to apply to open invoices in the future.
{% endhint %}

5. (Optional) Tap in the **Payment Received** field and enter a different payment amount.

{% hint style="info" %}
The amount shown in the **Payment Received** field defaults to the total amount of all selected open invoices. However, if **Apply Credit** is selected, the amount shown is the difference between the selected open invoices and the applied credit memos. You can edit the amount in this field if the customer is giving you a different amount, e.g., they are making a minimum or partial payment on the selected invoices.
{% endhint %}

6. (Optional) Tap in the **Description** field and enter any comments about the payment.
7. Tap **OK**.
8. On the **Payment** screen, enter the enter the payment amount next to the relevant tender type.

{% hint style="warning" %}
A customer cannot make a payment to account using the account tender type. Follow your store's policies regarding what tender types are accepted for payments to account. For example, many stores do not accept payments to account by debit card or credit card because they are charged transaction fees on those tender types.
{% endhint %}

<div align="left"><figure><img src="/files/SscnFQHhaNF0eMhWqE80" alt=""><figcaption></figcaption></figure></div>

9. Tap **OK**.
10. Tap **Yes** to print the receipt.

{% hint style="info" %}
The receipt shows which invoices the customer paid for, how much they paid, and the remaining balance on those invoices (if applicable). The receipt also shows any unpaid invoices and the new balance owing on the account.
{% endhint %}

<div align="left"><figure><img src="/files/occu6drR3w4SZlAfKIHp" alt=""><figcaption></figcaption></figure></div>


---

# 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://docs.rmhpos.com/readme-1/work-with-accounts/processing-payments-ar.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.