Recurrence rules

The recurrence options a scheduled transaction can use, and how end-of-month and weekend dates are handled.

A schedule’s recurrence decides which dates it produces. Set it in Settings > Scheduled Transactions. Refer to Schedule a transaction.

Frequencies

FrequencySetProduces
WeeklyThe weekdays it falls on, and an Every intervalOne date per chosen weekday, every N weeks
MonthlyA Day of month, or Last day of the month, and an Every intervalOne date per month, every N months
YearlyA month and a day within itOne date a year

The Every interval is what makes fortnightly and quarterly work: weekly every 2, monthly every 3.

Last day of the month

Choosing Last day of the month rather than day 31 is what keeps a month-end bill on month end.

SettingJanuaryFebruaryMarch
Day 3131 JanClamped31 Mar
Last day of the month31 Jan28 Feb31 Mar

Use it for anything due at month end. The dates then stay on month end rather than drifting to a day some months do not have.

Weekends

If it lands on a weekend decides what happens when a date falls on a Saturday or Sunday: keep the date, or shift it.

Match it to how the payment actually behaves. A direct debit that leaves on the next working day should shift, so your register agrees with your bank.

Start and end

Starts sets the first date. Ends can be a date, or nothing at all for a schedule that runs indefinitely.

The Preview lists the next few dates the recurrence produces, which is the check to make before saving. If it reports that the recurrence produces no dates, the settings contradict each other, most often a weekly schedule with no weekday chosen.

Amount matching

Separate from the recurrence, and it decides how a posted transaction is matched:

MatchMeaning
ExactThe amount never varies
ApproximateThe amount drifts around a figure
RangeThe amount falls between two bounds

Use Approximate or Range for utilities, so an imported transaction is still recognised as the scheduled one.

Next steps