Skip to main content
Recurring transactions keep future months useful without repeated data entry.

Supported patterns

PatternUse case
DailyRare daily expenses or transfers.
WeeklyWeekly groceries, allowance, or income.
Every 2 weeksBiweekly paychecks or bills.
Twice monthlySemi-monthly income or recurring payments.
MonthlyRent, mortgage, utilities, subscriptions, debt minimums.
YearlyInsurance, memberships, annual renewals, tax payments.

Default horizon

When no end date is set, CalBudget creates future occurrences for roughly 12 months from the transaction date.

Semi-monthly behavior

Semi-monthly schedules use the selected day of month and a second day roughly 15 days apart. For example, a transaction on the 1st can create a second monthly occurrence around the 16th.

What to make recurring

  • Paychecks
  • Rent or mortgage
  • Utilities
  • Insurance
  • Subscriptions
  • Loan or credit card minimums
  • Savings transfers
  • Repeated planned spending

Editing a recurring series

Choose the narrowest scope that matches reality:
  • Edit one occurrence if this month is unusual.
  • Edit future occurrences if the bill changes going forward.
  • Edit all occurrences if the original rule was wrong.

Avoid duplicate recurring rows

If a bill appears twice, check whether:
  • The original transaction and generated occurrence both exist.
  • The import flow created a second recurring rule.
  • A series was duplicated by editing all instances incorrectly.
Use the recurring group or transaction title to identify duplicates.