> For the complete documentation index, see [llms.txt](https://docs.bluepro.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluepro.ai/plans-billing/refunds-and-voiding-an-invoice.md).

# Refunds & Voiding an Invoice

Mistakes and changes happen. BluePro gives you two different tools: **refund** (give money back after a payment) and **void** (cancel an invoice). This guide explains when to use each and how.

**Who this is for:** Office staff and owners handling billing corrections.

### Refund vs. Void — Which One?

* **Refund** — the customer already paid and you need to return some or all of it. The invoice stays in your records, marked Refunded or Partially Refunded.
* **Void** — the invoice shouldn't be collected at all (created in error, replaced, or cancelled). Voiding **deactivates the payment link** so no one can pay it.

> 💡 **Rule of thumb:** money already changed hands → **Refund.** No payment (or you're cancelling the whole thing) → **Void.**

### How to Refund

From the invoice, open **Refund**. You'll see how much is refundable, then:

1. Enter the **Refund Amount** — full or partial.
2. Choose whether to **notify the customer** by email and/or SMS, and add an optional note.
3. Confirm.

* **Card or bank payments** are refunded through BluePay back to the customer's original method.
* **Manual payments** (cash/check) are recorded as a refund in BluePro so your records stay accurate (you hand back the cash/check yourself).

> ⚠️ **Note — Card refunds can't be undone.** They process immediately to the customer's card. Double-check the amount first.

<figure><img src="/files/Ol2quDibTGd8qn6HcV0j" alt=""><figcaption></figcaption></figure>

After a refund, the invoice status updates to **Partially Refunded** or **Refunded**, and the customer gets a refund confirmation if you chose to notify them.

### How to Void

From the invoice, open **Void**. BluePro warns you: *"This will permanently void the invoice and deactivate any payment links. This action cannot be undone."* Confirm to set the invoice to **Void**.

<figure><img src="/files/jAGJiWVnefIQPcaXCJ0z" alt=""><figcaption></figcaption></figure>

> 💡 **Tip — Void kills the payment link.** If you sent a payment link and need to stop it from being paid (wrong amount, duplicate), voiding immediately disables it.

### FAQ

* **Can I refund part of a payment?** Yes — enter any amount up to the refundable total.
* **The customer paid cash — can I still refund in BluePro?** Yes, as a recorded manual refund (you return the cash; BluePro keeps the record straight).
* **What's the difference between Void and Archive?** Void cancels an invoice and disables its payment link; Archive just hides a finished invoice from your default list.
* **Will voiding refund a payment?** No — void is for invoices that shouldn't be paid. To return money, use Refund.
* **Does the customer find out?** Refunds can notify them by email/SMS; you choose.


---

# 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.bluepro.ai/plans-billing/refunds-and-voiding-an-invoice.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.
