Reconciliation states
A reconciliation starts as draft and moves through its own lifecycle.
| State | Meaning |
|---|---|
| Draft | Created. Items can be generated, reviewed and changed |
| Generating | The run is finding its disbursements. Transient |
| Approved | Reviewed and accepted; the figures are settled |
| Processing | Being taken through to completion |
| Completed | Finished |
| Cancelled | Abandoned |
Transitions
| Action | From → To |
|---|---|
| Generate | Draft → Generating |
| Complete / cancel generation | Generating → Draft |
| Approve | Draft → Approved |
| Unapprove | Approved → Draft |
| Begin processing | Approved → Processing |
| Cancel processing | Processing → Approved |
| Complete | Approved or Processing → Completed |
| Cancel | Draft or Approved → Cancelled |
Two of those are worth knowing:
Generating returns to Draft, not forwards. Generation is a data-gathering step, not a stage of approval — when it finishes, the run is a draft again with its items populated. A run sitting at Generating is working, not stuck at a decision.
Approval is reversible. Unapprove takes an approved run back to draft. This is not true of everything in BMS, and it is what makes it safe to approve a run and then find a problem.
Completion has conditions. Both begin processing and complete require every item on the run to be completable. A run that will not move on has an item that cannot, and that item is where to look.