Correct an imported or captured penalty notice

Notices that arrive through OCR or CSV import often need a correction — a missing vehicle, a wrong amount, or a placeholder violation type. This article shows how to edit an imported penalty notice (Strafmandat) and the one rule that stops an edit.

Why imported notices need corrections

Imported notices are complete enough to be tracked, but they may still need finishing:

• OCR-confirmed notices start in Intake status with the violation type set to the placeholder ocr_imported. OCR maps only the case reference, date, location, and amount, so the vehicle and country are usually still blank.
• CSV-imported notices start in open status with all core fields populated from the file, but a typo in the source spreadsheet can still slip through.

Before you start

You need the Strafmandate module permission (strafmandate:view), which the SystemAdmin and FleetManager roles have by default. Open the notice you want to fix from the mandates list.

Edit the notice

1. Open the notice detail and switch to edit.
2. Correct or complete the core fields — violation type, date occurred, location, amount, vehicle, Aktenzeichen (authority case reference), and country code.
3. If the notice is international, turn on the international option and complete the authority name, city, postal code, and street address.
4. Save.

When you save, the system applies the same validation as manual creation: the violation type, location, Aktenzeichen, and country must be present, the amount must be greater than zero, a vehicle must be selected, and the date must be set. The country code is upper-cased and text fields are trimmed automatically.

Tip: For an OCR draft, the fastest path to a complete record is to set the real violation type (replacing ocr_imported), pick the vehicle, and enter the country code — those are the fields OCR cannot fill for you.

The terminal-state rule

A notice in the terminal resolved status cannot be edited. If you try, the save is rejected with "Mandate cannot be edited in terminal state." Make every correction before you resolve the notice. If the notice does not exist, you will instead see "Mandate not found."

Fixing a whole batch

If many rows in a CSV import were wrong, it is usually cleaner to fix the source file and re-import than to edit each notice by hand:

1. Correct the values in your CSV.
2. Run a dry run to confirm the rows now pass validation.
3. Commit the import. Rows whose Aktenzeichen and vehicle already exist are detected as duplicates and skipped, so you will not create doubles for notices that imported correctly the first time.

Note: Editing a notice is logged. Financial and status changes have their own dedicated actions elsewhere in the module and are not part of the core-detail edit.

Related

• Review and confirm OCR-extracted data
• Bulk-import penalty notices from CSV
• Required fields on a penalty notice
• Preview a CSV import with a dry run