> For the complete documentation index, see [llms.txt](https://old-manual.converia.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://old-manual.converia.de/en/attendees/manage-persons-and-attendees/managing-bookings-and-invoices/cancellation-at-a-glance/cancel-an-invoice.md).

# Cancel an invoice

Management -> Attendee Registration -> Invoices

If an invoice is to be canceled, e.g. because a participant cancels, we recommend ensuring that cancellation modalities have been set up.

In the event of a cancellation, the **invoice must always be canceled**. It is not sufficient to simply cancel the booking. Call up the invoice details and switch to the *Cancel* tab.

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FRggSxNAmBIadD4qtILOk%2Fimage.png?alt=media&amp;token=a19e8e77-f768-49fd-9641-d0246ea47c18" alt="Fig. 1: Cancel an invoice"><figcaption><p>Fig. 1: Cancel an invoice</p></figcaption></figure>

* If the specified cancellation fee differs from the current configuration, it makes sense to record the reason in a comment.
* Finally, the invoice must be updated; only then is the editing process completed and a new invoice document created.
* The comment function can be used to document changes or deviations for other users in the backend.
* No automatic emails are triggered when edits are made in the backend. If required, the participants can be informed via *booking info mail* (sent to the person who booked in, tab in the booking details) or *invoice info mail* (sent to the invoice recipient, tab in the invoice details).

{% hint style="info" %}
For ticketing customers: In the event of a refund, the process must be submitted to the Converia [Ticketing Service](/en/ticketing-processing-with-converia/general-information/who-is-responsible-for-cancelations-or-rebookings.md) next.
{% endhint %}