Instead of creating the same transaction every time you need to originate it, you can set it up to recur, or generate on a predetermined calendar. Schedules allow you to specify when a transaction will generate. Examples of recurring transactions include payroll deposits, billing debits, and annuity/dividend payments. Common schedules might include rules such as every month on the 15th or every two weeks on Friday. One schedule may hold multiple rules, such as the 15th and last day of the month. Every time a recurring transaction is generated, the application automatically resets the transaction's effective date for the next scheduled occurrence.
Schedules may be added or deleted. To avoid altering the schedule of existing transactions, you cannot edit a schedule. Also, you cannot delete a schedule that is in use; you must first change the schedule of existing transactions. New schedules may be created from the Schedule List or from the Schedule drop-down list of a transaction.
Once you have created a schedule, you may set it up as the default schedule
for a category/subcategory. Transactions created for the group will use
this default schedule, although you may change it at the transaction level
if necessary.
If you need to edit the effective date on scheduled transaction(s), the application may assume the change is to initiate the payment ahead of the next recurring payment date. This can cause the application to set the subsequent, scheduled effective date to one later than you prefer. You may override this assumption when the application prompts you for confirmation of the date; verify the correct next scheduled effective date and select Save.