Document Control Configuration

Company-scoped singleton configuration for document and payment control.

📄️ Get the company document control configuration

Returns the singleton configuration and its ETag. A company without a persisted configuration returns 404.

📄️ Upsert the company document control configuration

Creates or partially updates the singleton configuration. Omitted or null scalar fields are left unchanged. Category lists omitted or null are left unchanged; send an empty array to clear a list. When a payment-control flag is true, the corresponding minimum charged percentage must be present in the final stored state. Category IDs must belong to companyId. Use If-Match with the ETag from GET for optimistic locking on updates.

📄️ Prototype a document control configuration

Returns non-persistent form defaults for a company that may not have a configuration row yet. Does not write to the database. Typical create flow: POST /new, then PUT / to persist.