Versioned replacements with explicit omission rules

Context

Staff editors replace records they have read. Some newer fields must survive saves from editors that do not expose them, while other optional fields need a way to be cleared.

Decision

Record replacement requires the version read and applies the supplied record with documented omission exceptions. Default-purpose assignment and clearing are separate writes without an expected version.

Alternatives Considered

Offer partial configuration updates. The examined configuration routes provide replacement operations, and existing editors and status actions send complete records.

Preserve all omitted values. This proposed approach would require another explicit mechanism to clear optional settings.

Clear every omitted value. An editor that lacks newer fee and write-off controls would otherwise erase those stored choices.

Consequences

A stale replacement is refused so staff can reload the current record.

Omitted unit and statement template choices restore built-in selection; wholly omitted fee groups and policy switches preserve their stored values.

Clients may return accepted read-only properties; the service ignores those properties when saving.