Status 409
The invoice can't be annulled
fiscal_document_annul_refused
When it happens
The invoice cannot be annulled. code is the reason: not_an_invoice — the document is not an invoice; not_issued — the invoice is not issued: a rejected one is reissued, a pending one is cancelled with the order; provider_disabled — the fiscal module of the store is off; already_voided — the invoice is already annulled or its note waits to be issued; nothing_to_void — the sale was refunded in full and the credit notes cleared the invoice. current.status is the document status, current.annulling_document_id is the current annulling note for already_voided.
What to do
already_voided — follow the note current.annulling_document_id. A retry does not fix the other reasons.
Can’t find the answer, or the error keeps coming back? Write to us and quote the X-Request-Id from the response so we can find the request. Contact us
Endpoints that return it
Response body
application/problem+json · ConflictProblem
typestringrequiredMachine type of the problem: a stable code to branch on, such as insufficient_scope. Every type has a page in the error catalog.
titlestringrequiredShort summary of the problem in the language of the request.
statusintegerrequiredHTTP status of the response.
detailstringExplanation of this occurrence in the language of the request.
currentobjectThe record as it is now, the fields the conflict is about: on_hand for stock_on_hand_changed, status for rejected order changes, status and order_id for a closed draft.
external_idstringFor external_id_in_use and external_id_archived — the taken external ID.
consent_kindstringFor consent_required — the kind of consequence to agree to.
consequencesmap of integerFor consent_required — what will change: kind of data → number of records.
- Minimum:
- 0
consent_tokenstringFor consent_required — fingerprint of the shown consequences. Repeat the request with consent[<consent_kind>]=<consent_token>.
variant_idintegerFor consent_required of a variant line in a product write — the variant: the consent is given by changing that variant (PATCH /v1/variants/{variant}).
limitintegerFor plan_limit_reached, address_book_full, bulk_operation_queue_full and webhook_endpoint_limit_reached — the limit.
- Minimum:
- 0
fieldstringFor customer_contact_in_use — the contact that belongs to another customer: phone or email.
- Values:
phoneemail
existing_customer_idintegerFor customer_contact_in_use — the customer the contact belongs to.
receivedintegerFor upload_offset_mismatch — bytes the upload has received: the offset to continue from.
- Minimum:
- 0
operation_statusstringFor bulk_operation_finished — the status the operation finished with.