> For the complete documentation index, see [llms.txt](https://developers.hyp.co.il/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.hyp.co.il/enterprise/documents-and-invoicing/cancellations-payouts.md).

# Invoicing for Cancellations and Payouts

In terms of invoicing, there are two kinds of transactions that stand out:

* For payouts, you create [regular invoices](https://developers.hyp.co.il/enterprise/documents-and-invoicing/issuing-invoices.md) with the `addCgInvoice` command.
* For cancellations, you create [refund invoices](https://developers.hyp.co.il/enterprise/documents-and-invoicing/refund-invoices.md) with the `refundCgInvoice` command.

## Cancellations

There is no such thing as a "cancellation invoice".

When a transaction is canceled, you account for it by issuing a [refund invoice](https://developers.hyp.co.il/enterprise/documents-and-invoicing/refund-invoices.md) that matches the original transaction invoice but is a credit rather than a debit.

Although there are separate commands for canceling and refunding (`cancelDeal` and `refundDeal`), there is only one command for document generation: `refundCgInvoice`.

## Payouts

[Payouts](https://developers.hyp.co.il/enterprise/additional-payment-scenarios/payouts.md) are credit transactions in which you pay the customer, regardless of the original payment.

For invoicing purposes, payouts are handled [just like regular transactions](https://developers.hyp.co.il/enterprise/documents-and-invoicing/issuing-invoices.md): you use the `addCgInvoice` command with the payout’s transaction ID (`tranId`).

The `refundCgInvoice` command does not apply to payouts: even though a payout is a credit transaction, it does not require a refund invoice.


---

# 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://developers.hyp.co.il/enterprise/documents-and-invoicing/cancellations-payouts.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.
