Complete a guarded month-end close
Purpose
A controller submits one close request whose durable execution validates the books and records the result.
How It Works
The controller opens the close dialog and reviews a fresh evaluation. They acknowledge the displayed warning outcomes and confirm the month by typing its label. The console submits a key that survives another attempt from the same dialog. The service creates the run and job together, then starts execution after saving them. A sequence problem or competing run returns a refusal. The job takes the month and evaluates readiness again. Required blocked, pending or error results release the month and identify the failure. Warnings alone allow execution to continue. Due revenue is recognized before finalization records the close and requests aging. Future-year generation follows that successful finalization. A failure can retain the period for recovery, depending on its step and committed revenue work. The product should enforce requester identity on repeated keys, as the recorded ruling requires.
Relationships
- Authorization establishes the permitted sequence at submission.
- Readiness supplies the execution re-check.
- Revenue, year completion and recovery explain the individual execution outcomes.
- Run tracking and the close record expose progress and retained evidence.