# The VeriFactu status webhook reports a new rejection reason and the real previous status

`verifactu.status.updated` is also sent when a rejected record is rejected for a different reason, and `previous_status` now carries the status of the record it replaces.

Oct 16, 2026 · Improved

Two changes to `verifactu.status.updated`. The payload keeps its shape.

## What else changed

- **A new reason for a rejection sends a webhook.** While a record stays `REJECTED`, a different `error_code` or public `error_message` now triggers a delivery with `previous_status` and `new_status` both `REJECTED`. Handlers that assume the status always changes should accept this case.
- **`previous_status` follows the invoice, not only the record.** It is the status of the invoice's record of the same `operation` just before the change, also when a new submission replaces a rejected one. It is omitted only on the first notification of each `operation`, so the first notification of a cancellation still has no `previous_status`.

## Where to go next

- [VeriFactu status webhook](/webhook-events/onVeriFactuStatusUpdated)
- [Submission states](/verifactu/submission-states)

---

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