Review a penalty notice's financial summary and history
This article shows you how to read the financial summary, the payment list, and the financial history of a Strafmandat (penalty notice) so you can see at a glance what is owed, what has been paid, and who changed it. All three views require the strafmandate:view permission.
The financial summary
The financial summary gives you the headline numbers for a single notice. It combines the current payment position with the notice's cost allocation.
| Field | Meaning |
|---|---|
| Payment status | unpaid, partially_paid, paid, or overpaid — derived from total paid versus required amount. |
| Total paid amount | The sum of all payments recorded against the notice. |
| Required amount | The fine amount (Betrag) captured on the notice's core detail. |
| Outstanding amount | Required amount minus total paid, floored at zero (it never shows a negative balance). |
| Cost allocation | The department, project, and optional driver the notice is allocated to. |
Note: Because the outstanding amount is floored at zero, an overpaid notice shows an outstanding balance of 0. Use the payment status column to tell "fully paid" apart from "overpaid".
The payment list
The payments view lists every payment booked against the notice, newest first by paid-at date. Each row shows:
- Amount — the value of that payment, in EUR.
- Paid at — the date the payment was made (falls back to the record date if no paid-at date was captured).
- Payment method — how it was paid.
- Reference — the payment reference or booking number.
The list also repeats the computed payment status and the running total so you can reconcile the individual rows against the summary.
The financial history
The financial history is an audit view of every financial change on the notice, newest first. It covers two kinds of operations:
- record-payment — a payment was booked.
- update-cost-allocation — the department, project, or driver allocation was changed.
Each entry shows the operation, the timestamp, the actor (user ID and email where available), and a changed-values summary describing what was recorded — for example the amount, paid-at date, method, and reference for a payment, or the new department/project/driver for an allocation change.
Tip: Use the financial history when a total looks wrong. Because it lists every payment and allocation change with the actor, you can trace exactly which entry introduced a discrepancy rather than guessing from the summary alone.
Who can see this
The summary, payment list, and history are read-only reporting views gated by strafmandate:view. Recording payments and updating allocations use the same permission, while editing a driver's Flensburg points is separately gated by strafmandate:manage.
Related
- Record a payment on a penalty notice
- Allocate a penalty notice to a cost center or driver
- Run management analytics and export reporting data
