> 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/transactions-tendering-store-credit.md).
# Tender a sale 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. Enter all of the items in the transaction.
3. Tap **Transaction** | **Tender Sale**. You can also press **F12** or **Enter**.
4. On the **Tender** screen, enter the tender amount next to the account tender type.
{% hint style="info" %}
The name of the account tender type is customizable and may vary by store. Your store may call it Account, Store Charge, Charge Account, Credit Line, or something else. In the example below, it's called Store Charge.
{% endhint %}
5. Tap **OK**.
{% hint style="info" %}
On the **Register Transaction** screen, you can see the customer's next payment due date, their current balance due, and their available credit. Follow your store's policies regarding sharing this information with the customer.
{% endhint %}
6. Tap **Finish**.
7. (Optional) Print or email the customer's receipt.
---
# 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/transactions-tendering-store-credit.md?ask=&goal=
```
`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.