---
title: "Cancel Ar Invoice"
method: POST
path: "/companies/{company_id}/ar/invoices/{invoice_id}/cancel"
tags: ["ar-invoices"]
---

# Cancel Ar Invoice

`POST /companies/{company_id}/ar/invoices/{invoice_id}/cancel`

## Request

- Base URL: `https://app.zeno-works.ch` (the document declares no server; this is the origin it was published from)
- URL: `https://app.zeno-works.ch/companies/{company_id}/ar/invoices/{invoice_id}/cancel`
- Auth: none declared

Void an issued invoice: reverse its posting through the guarded storno door, then
mark it ``cancelled``.

The reversal mirrors the invoice's VAT postings negated, unwinds its recognition
schedules and cancels its open item — so a cancelled invoice leaves nothing standing
in the MWST-Abrechnung or the aging.

``body.posting_date`` dates the reversal; omitted, it reuses the invoice's own posting
date. Refusals: **422** when the invoice is not ``issued`` or its open item is already
partly/fully paid (credit it instead of cancelling); **409** when the reversal date
falls in a ``filed``/``paid`` VAT period, or when the accounting period covering it is
closed — **re-send the cancel with a ``posting_date`` in an open VAT period to clear
either**; **422** when an already-posted recognition installment would have to be
reversed into a closed accounting period, which a ``posting_date`` does *not* clear
(reopen that period instead).

## Path parameters

- `company_id` string, required
- `invoice_id` string, required

## Headers

- `authorization` string, nullable

## Cookies

- `access_token` string, nullable

## Request body

- ArInvoiceCancel: ``POST …/ar/invoices/{id}/cancel`` body — optional, all fields optional. ``posting_date`` dates the **reversal** of the invoice's posting (omitted: the invoice's own posting date). It exists so the guarded reversal's filed-VAT-period 409 — *"pass a posting_date in an open VAT period instead"* — can be cleared from this door in one call, instead of leaving the invoice permanently ``issued``.
  - `posting_date` string, date, nullable

## Response `200`

Successful Response

- ArInvoiceDetailOut
  - `doc_type` 'invoice' | 'credit_note'
  - `counterparty_id` string, nullable
  - `issuer_profile_id` string, nullable
  - `issue_date` string, date, required
  - `due_date` string, date, nullable
  - `service_period_start` string, date, nullable
  - `service_period_end` string, date, nullable
  - `currency` string
  - `language` string, required
  - `payment_terms_id` string, nullable
  - `invoice_discount_kind` 'none' | 'percent' | 'amount'
  - `invoice_discount_value` string
  - `footer_text` string, nullable
  - `legal_text` string, nullable
  - `notes` string, nullable
  - `credited_invoice_id` string, nullable
  - `id` string, required
  - `status` 'draft' | 'issued' | 'cancelled', required: Editorial lifecycle owned by ``ar_invoice`` (paid/overdue are derived on read from the linked ``gl_open_item``, not stored here).
  - `origin` 'human' | 'system' | 'ai' | 'api' | 'mcp' | 'chat': What KIND of actor posted a journal entry — the attribution flag. Two axes in one vocabulary, because the column answers one question — *can a reader take this as a person's own judgement?* **Authorship** — the value says who composed the booking: * ``ai`` = the AI-accountant composed it (an autonomous post, or a one-click accept where the content is still the accountant's proposal); * ``system`` = a mechanical/background ``SystemPrincipal`` post (migrations, close automation, deterministic seeds). **Channel** — the value says which surface a person's own action arrived through, because "a ``UserPrincipal`` acted" is NOT the same claim as "a person decided". All four are derived from the request edge by :func:`~invoiage_db.repos.gl_posting._resolve_origin`: * ``human`` = an interactive browser session (cookie/JWT auth). The only value that asserts a person was looking at the screen; * ``mcp`` = an API-key request carrying the mcp shell's ``X-Zeno-Surface`` marker — a connected agent, which MAY be relaying a person and may not; * ``api`` = any other API-key request (a script, an integration, an agent calling the REST api directly). Not provably a person either; * ``chat`` = the built-in CFO chat relaying a person's approval in-app. Its *authored* bookings stamp ``ai``; ``chat`` is only for the relay. Widening this vocabulary is a **one-way door on rollback**: the PG type is a native enum converted at load (``pg_enums._pg_enum``), so an api whose Python enum lacks a value raises ``LookupError`` reading any row that carries it. See the ``0112`` migration.
  - `document_no` string, nullable
  - `commercial_document_id` string, nullable
  - `snapshot_document_id` string, nullable
  - `net_total` string, required
  - `vat_total` string, required
  - `gross_total` string, required
  - `payment_status` string, nullable
  - `open_amount` string, nullable
  - `is_overdue` boolean
  - `posting` ItemPostingOut: The ledger projection of one ingested document — the posted/not marker. Present only on the surfaces that project it (the item lists and the item detail read, ZCT-848); everywhere else ``ItemOut.posting`` stays ``None``, which means "not computed here", NOT ``unposted``. Never branch on a missing value. It answers "is it in the journal?", not "may I code it?": a coding row posted without an entry, or an expense-receipt routing row, reads ``unposted`` here while coding the item is still refused as already booked (``gl_autopost.coding_blocker``). ``accounts`` is filled only for :attr:`ItemPostingStatus.posted` and holds **every** operating leg, largest first — a document split across three expense accounts has no single answer, and silently showing the first line would be a lie. It may legitimately be empty (an entry with only control/VAT legs).
    - `status` 'posted' | 'reversed' | 'held' | 'unposted', required: Where an ingested document stands in the general ledger (ZET-98/103/108). Deliberately NOT a boolean: a boolean collapses four states a treuhänder has to tell apart, and "not posted" alone cannot say *why*. - ``posted`` — a coding decision for this document points at a journal entry whose ``status`` is ``posted``. This is the only value that means "it is in the ledger"; :attr:`ItemPostingOut.accounts` says where. - ``reversed`` — the document was booked and that entry was reversed. The ledger no longer carries it, so it is **not** posted (ZET-95), but it is a materially different state from "never touched": it needs re-booking. - ``held`` — the AI accountant produced a coding proposal that did not clear the autonomy policy and is waiting for a human. Nothing is in the ledger. - ``unposted`` — everything else: no coding decision at all, a shadow-mode decision (``assist``: it *would* have posted but did not), or a decision of a kind that books nothing.
    - `journal_entry_id` string, nullable
    - `accounts` ItemPostingAccountOut[]
      - `account_id` string, required
      - `code` string, required
      - `name` string, required
      - `amount` string, required
    - `coding_pending` boolean
    - `filed_with` ItemFiledWithOut: The booking a re-ingested COPY of an invoice was filed with (ZEN-1, ZCT-945). The coder's dunning linkage (``ap_dunning.try_link_ap_document``) recognises a second upload of an invoice that is already booked and files it against that booking's open item instead of booking it twice. It writes no decision, so the copy's own projection is ``unposted`` and the lists used to read "Not posted" — to the reader the AI looked as if it had stopped posting. This names the booking the copy belongs to. Set only where "already booked" is TRUE (:func:`services.item_posting.posting_map`): an advisory, non-reminder, non-collision link whose holder entry is posted, and — for the weaker payment-reference tier — only for a copy dated like the booked invoice. ``gross`` / ``currency`` are the BOOKED document's; ``amount_differs`` says the copy prints another total or currency, so the reader checks the booking rather than trusting the badge (the linker matches amounts within a band, not exactly).
      - `journal_entry_id` string, required
      - `entry_no` string, nullable
      - `entry_date` string, date, required
      - `match_tier` string, required
      - `gross` string, required
      - `currency` string, required
      - `amount_differs` boolean
  - `sent_at` string, date-time, nullable
  - `last_sent_to` string, nullable
  - `issued_at` string, date-time, nullable
  - `created_at` string, date-time, required
  - `updated_at` string, date-time, required
  - `lines` ArInvoiceLineOut[]
    - `line_type` 'product' | 'service' | 'text' | 'section' | 'discount'
    - `sort_order` integer, required
    - `group_label` string, nullable
    - `product_id` string, nullable
    - `item_code` string, nullable
    - `description` string, nullable
    - `quantity` string, nullable
    - `unit_price` string, nullable
    - `unit_label` string, nullable
    - `account_code` string, nullable
    - `vat_code_id` string, nullable
    - `line_discount_kind` 'none' | 'percent' | 'amount'
    - `line_discount_value` string
    - `service_period_start` string, date, nullable
    - `service_period_end` string, date, nullable
    - `id` string, required
    - `net_amount` string, required
    - `vat_amount` string, required
    - `gross_amount` string, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/zeno-works/apis/zeno-api.md) · [All operations](https://skmtc.dev/zeno-works/apis/zeno-api/llms.txt) · [OpenAPI document](https://skmtc.dev/zeno-works/apis/zeno-api/revisions/1eb93dde146c?raw)