Off-Cycle Processing
Overview
Off-cycle processing handles payments that do not fit the standard production cycle, such as corrections, terminations, urgent advances, or one-off settlements.
Typical Use Cases
- individual payment corrections
- urgent final settlements
- advance payments
- replacements for failed payment scenarios
- small-population supplementary settlements
Calendar And Group Design
Off-cycle processing still uses calendars and calendar groups, but the design goal changes:
- smaller and more intentional populations
- tighter review and approval controls
- clearer naming so operators can distinguish off-cycle from the regular monthly run
- separation from open on-cycle groups for the same payees
Because a payee can belong to only one open calendar group at a time, off-cycle timing must be coordinated with any active on-cycle calendar group for that payee.
Design Considerations
| Topic | Guidance |
|---|---|
| Population | Keep it narrow and intentional |
| Grouping | Use separate off-cycle groups for audit clarity |
| Controls | Add tighter approval and review checkpoints |
| Downstream handling | Confirm banking and GL expectations differ where needed |
Operational Pattern
- define or select the appropriate off-cycle run type
- create a tightly scoped calendar or listed-payee calendar
- confirm no conflicting open group exists for the payee population
- calculate, review, and finalize promptly
- push the published results through banking or GL only after the correction intent is confirmed
Key Takeaways
- Off-cycle processing is operationally exceptional and should stay that way.
- Open-group rules matter more here than in standard production.
- Reuse of on-cycle logic is fine, but control boundaries should remain distinct.