Finalize Phase
Overview
Finalize closes approved processing results and makes them available for downstream operational processes. It is the control point between reviewable calculation results and published payroll results.
Finalize Preconditions
The batch process aborts if the run does not meet these requirements:
| Requirement | Where to check |
|---|---|
No payments remain in Error or Identified status | Processing Statistics |
No payees remain Suspended by User or Suspended by System | Processing Statistics |
| All streams have been calculated, if stream processing is used | Processing Statistics / Stream Setup |
All process indicators are back to Normal | Payee Status |
What Finalize Does
- closes the open calendar group
- updates segment status to finalized states
- prevents routine recalculation of finalized results
- stamps the calendar group with a finalize timestamp
- marks the calendar group as no longer open
Status Impact
| Status | Meaning |
|---|---|
| Finalized | The calendar segment is closed and no longer open for change |
| Finalized - With Banking | Finalize completed and banking has already been run |
Once Finalize is complete, the calendar group is no longer open on run control and can participate in later retro processing from other groups.
What Finalize Deletes
The Finalize phase removes several temporary processing artifacts:
- warnings and error messages
- element resolution chains
- processed retro triggers
- iterative triggers, including unprocessed iterative triggers
It does not remove positive input, segmentation triggers, or unprocessed retro triggers. That distinction is important when you are deciding whether to finalize now or deal with outstanding trigger conditions in a later run.
What Remains Available After Finalize
Business results remain reviewable after Finalize through the result inquiry pages. What disappears are the transient processing aids such as Payee Messages and iterative trigger information.
Operational Checks Before Finalize
| Check | Why it matters |
|---|---|
| Exceptions reviewed | Avoid publishing known issues |
| Net pay validated | Protect payments and interfaces |
| Retro impact understood | Prevent accidental downstream adjustments |
| Sequence complete | Ensures dependent calendars finished successfully |
| Trigger backlog reviewed | Avoids losing visibility to still-important iterative activity |
Finalize must be run by itself, and it cannot be reversed.
Key Takeaways
- Finalize is both a status change and a business approval point.
- It closes the open calendar group and removes important transient diagnostics.
- Downstream processes should assume finalized data is authoritative.