# Compliance status of an invoice changed API Reference

Delivered when the standing of an invoice with one tax system changes: the `status`,
`system_status` or `stamps` of one entry of its `compliance`. It is sent for every system,
VeriFactu included, and carries that entry as it is after the change. A change that leaves
the three as they were sends nothing.

`verifactu.status.updated` keeps being delivered for VeriFactu: subscribe to the one you
use.

**Recommended actions:**
- Route on `compliance.type` and branch on `compliance.status`; ignore a `type` you do not
  know.
- On `FULFILLED_NEEDS_FIX`, or on `REJECTED` for VeriFactu, tell the user and read the
  submission with `GET .../invoices/{invoice_id}/compliance-submissions` for the reason.
- On `REJECTED` for SII, you do not need to do anything: BeeL. sends it again and the
  reason is in `error_code`. If the customer's NIF or name is not in the AEAT census,
  sending it again leaves the status in `FULFILLED_NEEDS_FIX`. If the cause is in data
  that only you can correct, BeeL. contacts you.
- Keep the `stamps` you need, for example to print them.

**Always verify `BeeL-Signature` before processing.**


> Not rendered here (no operation matched this page) — see the full OpenAPI spec at https://docs.beel.es/api/openapi


---

Full OpenAPI spec: https://docs.beel.es/api/openapi