---
title: "Check annulment eligibility"
method: GET
path: "/companies/{company}/invoices/{invoice}/can-annul"
tags: ["Invoices"]
---

# Check annulment eligibility

`GET /companies/{company}/invoices/{invoice}/can-annul`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/companies/{company}/invoices/{invoice}/can-annul`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Check whether an invoice can be annulled and whether a VeriFactu cancellation record will be created; call before `/annul`.
- `can_annul` is the verdict without `revert_collections`.
- If only live payments block it, `requires_collection_reversal` is `true` with `active_collections_amount`.

## Path parameters

- `company` string, uuid, required
- `invoice` string, uuid, required

## Headers

- `Factuarea-Version` string, date

## Response `200`

- object
  - `data` CanAnnulInvoice, required: Result of the pre-cancellation validator of an invoice: whether it can be cancelled, the blocking reasons (when it cannot), whether the cancellation will create an additional VeriFactu record and whether its live payments are the only obstacle (`requires_collection_reversal`). `can_annul` is the verdict of `POST .../annul` WITHOUT `revert_collections`.
    - `can_annul` boolean, required: Whether the invoice can be annulled in its current status.
    - `reasons` string[], required: Blocking reasons when `can_annul` is `false`. Empty `[]` when the invoice can be cancelled.
    - `will_create_verifactu` boolean, required: Indicates whether the cancellation will generate a cancellation record in VeriFactu.
    - `info` string[], required: Additional informational messages about the cancellation (non-blocking warnings). Empty `[]` when there are none.
    - `requires_collection_reversal` boolean, required: `true` when the live payments of the invoice are the ONLY obstacle to annulling it: `POST /v1/companies/{company}/invoices/{invoice}/annul` with `revert_collections: true` would succeed. `can_annul` stays `false` in that case, because it is the verdict without `revert_collections`. `false` when there are no live payments or when something else also blocks the annulment.
    - `active_collections_amount` number, required: Amount, in euros, of the live payments of the invoice — what `revert_collections` would revert. `0` when there are none.

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`).
- `404`: The requested resource does not exist or belongs to another company.
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)