The mandate timeline
Published:
Updated:
This article explains the mandate timeline — the single, read-only history that brings together status changes, objection activity, and authority communications for a Strafmandat (penalty notice).
What the timeline shows
The timeline is a consolidated audit view. It merges three streams of events for a mandate into one list, ordered newest first. Viewing it requires the strafmandate:view permission.
| Source | What it records |
|---|---|
| mandate-status | Status transitions such as open to in_progress, or a move to resolved. |
| objection-status | Einspruch (objection) transitions: draft, submitted, authority response pending, and the final outcome. |
| authority-communication | Anhörung responses forwarded to the authority, shown as moving to forwarded. |
Reading an entry
Each timeline entry carries a consistent set of fields:
- From and to status — where the item moved from and to.
- Reason — the note attached to the change, or an automatically composed description for objection outcomes and authority forwards.
- Changed by — the user who made the change; automated worker entries carry a system actor.
- Changed at — the timestamp used to order the list.
- Source — which stream the entry came from (see the table above).
- Authority outcome — set to accepted or rejected for a recorded objection decision, or forwarded for an authority communication.
Automated deadline entries
Entries created by the scheduled deadline worker are labelled by what they represent, so you can tell them apart from manual changes:
- deadline-reminder — a reminder that a payment deadline is approaching.
- deadline-escalation — an escalation raised for non-response or a stale mandate.
- deadline-risk-alert — an at-risk alert raised when a deadline is imminent.
Note: These labels are derived from the reason text on each status transition, which is why automated activity reads clearly on the timeline without extra configuration.
How to use it
- Open the mandate and go to its timeline.
- Scan from the top for the most recent activity — the newest events, including replayed authority forwards, appear first.
- Use the source and authority-outcome fields to trace a specific thread, such as the full objection lifecycle or every authority communication.
Tip: Because authority communications show the channel and content hash in their reason, the timeline doubles as evidence of exactly what was sent to the authority and when.
Related
- The mandate status workflow and transitions
- Record an objection outcome
- Forward a notice to the authority (Anhörung)
- Calculating and tracking deadlines (Fristen)
AH
