> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/feature-references/features-and-products-references/smart-suggestion/using-smart-suggestion/corrections-voids-suspends-and-refunds.md).

# Corrections, Voids, Suspends and Refunds

| Scenario on the POS                                       | Verified Behaviour                                                                 |
| --------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| Void Line on an item added from the panel                 | Upsell lines void like any other line; totals recalculated                         |
| Void the whole ticket after an upsell                     | Full void supported after upsell acceptance                                        |
| Press Void while the panel is on screen                   | Void takes precedence; panel handled cleanly                                       |
| Press Error Correct while the panel is on screen          | Last line corrected; suggestion flow remains stable                                |
| Suspend the sale while the panel is on screen             | Sale suspends; panel state does not block the suspend                              |
| Suspend then recall a sale involving upsell               | Recall restores the basket; suggestion behaviour consistent on recall              |
| Refund transactions, including suspend/recall of a refund | The Suggestion Panel does not interfere with refund flows                          |
| Accept an upsell with the Subtotal Required flag enabled  | 'SUBTOTAL REQUIRED' shown at tender; a second Total refreshes and tender completes |


---

# 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.verifone.com/feature-references/features-and-products-references/smart-suggestion/using-smart-suggestion/corrections-voids-suspends-and-refunds.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.
