Recurrence Behavior
How Work Planner calculates next due dates, catches up past occurrences, and handles inactive recurring transactions.
Recurring behavior in Work Planner is driven by the scheduled transaction itself. The system keeps a next due date, remembers the last processed date, and generates ledger rows until the recurring pattern catches up with today.
How Next Due Is Calculated
- Active schedules only: Inactive scheduled transactions do not keep a live next due date.
- First run: If nothing has been processed yet, the next due date starts from Starts On.
- After processing: Once an occurrence has been created, Work Planner calculates the next due date from the last processed date and the recurrence pattern.
Catch-Up Behavior
If an active scheduled transaction already has a next due date in the past, Work Planner can catch up by creating all missing occurrences through today. That is why editing old start dates or old patterns can generate several historical rows in one go.
What Each Occurrence Inherits
- Ledger type: The generated transaction uses the scheduled transaction's type.
- Links and values: Customer, job, service, payment method, expense category, vehicle, description, amount, VAT, net amount, and payment reference are all copied into the generated row.
- Schedule markers: Generated rows are marked as scheduled occurrences, with due, next due, and last done values populated from the recurrence engine.
Payment Fee Side Effect
Recurring payments can also create a payment fee expense when the linked payment method has fee rules. That means one recurring payment setup can generate both the payment row and its related fee expense over time.
Related articles
- Creating a Scheduled Transaction: Covers the fields that drive this behaviour.
- Editing a Scheduled Transaction: Useful when changes to the schedule are what triggered unexpected catch-up behaviour.
- Scheduled Transaction Detail View: Shows the dates and generated history this behaviour produces.