Create Local Monthly Allowance Accounts When Needed

Context

Customers need a reset calendar, while provisioning should not pre-create unused accounting rows.

Decision

Create one allowance period per organization’s local month from configured limits or defaults, retaining charges, holds and running counts without a scheduled reset or departmental allocation.

Alternatives Considered

Use a common UTC month: It resets at a boundary that can differ from the customer’s local calendar.

Run a monthly reset schedule: It adds a job whose absence can block the next period.

Split allowance by department: There is no implemented cost-centre allocation model in this module.

Consequences

AI provisioning performs no allowance creation. Workspace purge removes scoped periods. UTC reporting and local periods have a recorded unresolved boundary assumption. Historical periods remain inspectable and correctable.