> For the complete documentation index, see [llms.txt](https://helpwith.salesorder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpwith.salesorder.com/sales/customer-refunds.md).

# Customer Refunds

See [Customer Refunds ⛭](/setup/configuration/customer-refund.md)

<details>

<summary>Media</summary>

<img src="/files/J287xL4U1ozzJwqiLpzE" alt="" data-size="line">[Customer Refunds](https://salesorder.wistia.com/medias/beiap1l2n4)

</details>

<mark style="color:orange;">Sales > Customer Refunds</mark>

#### When to Refund a Cash Sale

A Customer Refund document is directly related to a sales activity.

If a customer returns an Item, the Customer Refund document records the following:

* The return of the Item(s)
* The corresponding amount paid back to the customer
* The method used to pay (Cash, Check, Card etc)
* The source account you paid the money from

If the above is related to a Cash sale, the cash sale document would be used to create the Sales Refund document.

#### When to Refund a Credit

This is when you wish to convert an outstanding Customer Credit note or credit balance to cash. Examples can include: when either the Customer has overpaid you or a previous credit has been applied to a Customer’s account and they wish to receive that credit as cash.<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 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://helpwith.salesorder.com/sales/customer-refunds.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.