Editing a Scheduled Transaction
How to edit a recurring ledger pattern and which changes affect future occurrences versus existing generated rows.
Open the scheduled transaction first, then choose Edit. The edit popup returns to the same tabbed structure as creation, centred on Transaction, Schedule, Linked Records, and Details. This is where you change the recurring pattern itself, not the individual ledger rows it has already created in the past.
Changes That Affect Future Occurrences
- Status: Changing the schedule to Inactive pauses future generation and clears the live next due date. Switching it back to Active lets Work Planner calculate a fresh next due date again.
- Starts On and Schedule: These fields control the recurrence engine. Changing them changes how future occurrences are calculated from this point onward.
- Amount, VAT, Payment Reference, and Description: These values flow into future generated ledger rows. They do not rewrite historical rows that were already created before the edit.
- Linked records: Job, derived customer, service, payment method, expense category, and vehicle changes apply to future occurrences rather than editing old ones behind the scenes. For customer-linked schedules, the customer follows the chosen job.
Past-Due Catch-Up
If you edit an active scheduled transaction so that its next due date sits in the past, Work Planner can catch up and create the missing occurrences up to today. That is helpful when you are correcting a schedule, but it also means start dates and patterns should be changed deliberately.
When Editing Is Restricted
Scheduled transactions still respect transferred customer and transferred job protection. If the linked records are no longer mutable in the current business context, Work Planner blocks the change rather than letting the recurring setup drift out of step with those records.
Related articles
- Creating a Scheduled Transaction: Useful if you want to compare the current setup against the original create flow.
- Scheduled Transaction Detail View: Shows what you should check before making changes.
- Recurrence Behavior: Explains the underlying generation rules in more detail.