Save a Unit’s Policies and Currency Setup
What It Does
A unit save carries its complete ordinary configuration and loaded version. Founding choices remain fixed. Newer fee, direct write-off and supported-currency groups have explicit preservation behavior for older clients that omit them.
The Flow
When Something Fails
Each database stage shares one replacement transaction. Validation, locks, a stale version or a dependency refusal prevent the whole save. The batch count can miss posting that happens concurrently, so the guard is not a complete concurrency guarantee. Omission also differs across groups: templates reset to built-ins, while the specified policy groups are preserved.
Open Design Questions
The method guard needs a concurrency decision before it is relied on as a financial safeguard. The console still has no controls for tender fees or direct write-off treatment.