Annul an invoice
Withdraw an issued invoice with a documented reason.
-
reasonis required here (3–500 characters); that is the only difference fromPOST /v1/invoices/{id}/void, which performs exactly the same operation and persists a placeholder when you omit it. -
Prefer this endpoint whenever the reason has to be traceable — the text you send is kept in the invoice audit trail and, when the company is enrolled in VeriFactu, becomes the
motivoof the AEAT cancellation record. -
The invoice moves to
annulledandvoided_atstarts reporting when that happened. -
The status is terminal and the operation is irreversible: there is no transition back to
sentordraft, and the correlative number of the series is neither released nor reused. -
Effect on AEAT. With VeriFactu enabled, annulling queues an anulación record to AEAT asynchronously: a
200means the invoice is annulled in Factuarea, not that AEAT has already processed it — poll the invoice for its VeriFactu status. -
The original alta record is not deleted or rewritten; AEAT keeps both entries, the issuance and its cancellation.
-
With VeriFactu inactive the annulment is purely internal and nothing is transmitted.
-
Annul or correct? Annulment withdraws the whole document and only works before payment; it produces no amending document, so it never restates an amount.
-
A corrective (
POST /v1/invoices/{id}/corrective) creates a new invoice that amends the original and is the only path for an invoice that is alreadypaidor that is only partly wrong. -
Limits: only
sentoroverduecan be annulled. -
A
draftis not annulled but deleted;paid,cancelledandannulledreturn 422. An invoice that is a corrective can never be annulled — issue a new corrective of the original instead. -
Use
GET /v1/invoices/{id}/can-annulto check eligibility, and whether a VeriFactu cancellation record will be created, before posting here.
In: header
Path Parameters
Headers
Client-generated opaque key (up to 255 characters; UUID v7 recommended) that makes retries safe: the first response is cached and replayed for repeats without re-executing the mutation. Reusing a key with a different body returns 409 idempotency_key_reused. See the Idempotency guide. Required on this operation: repeating it delivers an effect that cannot be taken back (an email sent, a file generated, a third-party call, a charge), so a request without this header is rejected with 422 idempotency_key_required before any business logic runs.
1 <= length <= 255Pin the API version (YYYY-MM-DD, Stripe-style date versioning) for this request; omit to use the key's pinned version, or the latest if none. Unsupported version → 400 unsupported_api_version; malformed → 400 parameter_invalid_format. The effective version is echoed in the Factuarea-Version response header. See the Versioning guide.
dateOperate on behalf of a child company (gestoría master key): pass its public id (UUID v7) and the request runs against that child's data without changing the key's scope, tier or environment (omit to use the key's own company). Invalid UUID → 400 parameter_invalid_uuid; unknown or non-owned id → 404 profile_not_found. See the Acting on behalf guide.
uuidRequest Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json