> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/invoicing/online-invoicing/invoice-content/orders/sale-and-refund-order.md).

# Sale and Refund Order

Each payment is shown as an individual row — partial&#x20;refunds on active orders appear as separate negative entries alongside the original payment. The service fee is only distributed to positive\
payments; refund payments carry no service charge.

If a refund is processed for a sale order, it will be listed in the Orders section as multiple line items. Fees are applied accordingly depending on the type.

For example, Order # 302 contains a sale payment for €22.43 which is applied a service charge and the appropriate card fees. Order # 302 is listed in a second line item as a refund of €5.00 was processed. This refund is applied the appropriate refund fee but no service charge.

<figure><img src="/files/4z5OzaFOspNy8WZuJZMA" alt=""><figcaption></figcaption></figure>


---

# 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.bossithq.com/invoicing/online-invoicing/invoice-content/orders/sale-and-refund-order.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.
