> 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/advanced-transaction-tasks/transactions-voiding.md).
# Void transactions
Sometimes you will need to void a transaction after you tender it. For example, you might void a transaction if the customer realizes they used the wrong credit card to pay for the purchase and they want to put the purchase on a different card. Follow your store's policies and procedures for voiding transactions.
You cannot void part of a transaction. When you void a transaction, the entire transaction is voided. If you need to refund part of a transaction (for example, to remove items or change quantities), you should recall the transaction for return.
{% hint style="info" %}
You cannot void transactions if the option **Do not allow to return or void entries from transaction** is selected for your user account. Voided debit card transactions are processed as returns. This is because the funds have already been deducted from the customer’s bank account and cannot be voided.
{% endhint %}
1. Tap **Transaction** | **Recall Transaction** | **Recall for Void**.
2. Look up the transaction by doing one of the following:
* Enter the transaction number, customer name, or account number (or a combination) and press **Enter**.
* Scroll through the list of transactions until you find the correct one.
3. Tap the transaction to select it and tap **Add**.
4. If prompted, tap the appropriate reason code to select it and tap **OK**.
5. Confirm that the tender amounts and tender types match the original transaction.
The tender amounts appear as negative amounts (with parentheses around the amount).
6. Tap **OK**.
---
# 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/advanced-transaction-tasks/transactions-voiding.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.