User manual

Planned transaction form

Back to home

Planned transaction form

This page is used to define regular income, expense, or transfer rules that either generate transactions automatically or create planned occurrences for your review.

Main fields

Scheduling mode

Mode Behaviour
Simple Repeats at the chosen frequency. Generates transactions automatically each day.
Once A single occurrence at the start date. Frequency is not required.
Custom dates Explicit list of dates you pick. Occurrences within the next 60 days are generated.
Custom rule Visual rule builder — choose frequency, interval, day pattern, weekday, or yearly date.

Field visibility per mode:

Field Simple Once Custom dates Custom rule
Frequency
Amount mode Fixed only
Start date auto-derived
End date
Lead days
Custom dates list
RRULE builder

In Once mode the amount mode is automatically set to Fixed, and the end date and lead days fields are hidden.

In Custom dates mode the start date field is hidden — it is automatically derived from the earliest date in your list.

Mode Behaviour
Fixed Every occurrence uses the template amount. Shown with (~) in the list for Variable.
Variable You enter the actual amount when confirming each occurrence.

Type

Income or Expense, selected via a visual button toggle. Affects the account label and the sign of generated transactions.

Custom rule builder (Custom rule mode only)

A visual editor based on RFC 5545 RRULE:

  • Frequency — Monthly / Weekly / Daily / Yearly
  • Interval — e.g. every 2 months, every 3 weeks
  • Monthly patterns:
    • By day of month — fixed day 1–28 or last day of month
    • Bi-monthly — two fixed days per month (e.g. 1st and 15th)
    • By weekday position — e.g. first Monday, last Friday
  • Weekly — checkboxes for each day of the week
  • Yearly — specific month and day

A live preview shows the next upcoming occurrence dates as you adjust the settings.

Custom dates list (Custom dates mode only)

Click + Add date to add individual dates. Each date generates one planned occurrence. The start date is derived automatically from the earliest entry.

Frequency

Only visible for SIMPLE mode. Defines the repetition interval (Daily / Weekly / Biweekly / Monthly / Quarterly / Yearly).

Amount

The template amount (in major currency units, e.g. 99.90). For Variable mode this is an estimate.

Description

A required short label so the rule stays recognizable later.

Start date

Must be tomorrow or later. Sets the first occurrence date.

End date

Optional. The rule stops generating after this date.

Next occurrence

(Edit only) Fine-tune the next scheduled run date if you need to shift the cycle.

Reminder lead days

How many days before the due date a reminder email is sent (default: 3, range: 0–30). Set to 0 to disable email reminders for this rule.

Account and category

Generated transactions will use these values.

Tags

Optional. Tags assigned here are applied to every transaction generated by this rule.

Active

If disabled, the rule stays saved but no new transactions or planned occurrences are generated.

Related pages

Table of contents
1. Introduction
CaeliBudget is a workspace-based financial management application.
3. Workspaces
A *workspace* is the isolated unit that owns your accounts, categories, transactions and tags. A user can belong to multiple workspaces (e.g. *Household*, *Business*), and every membership is bound to a **role**.
Create or edit a workspace
This page is used to create a new workspace or update the core settings of an existing one.
Workspace onboarding
This page guides you through the first setup steps of a newly created workspace.
Workspace members
This page manages the list of users who can access the workspace and their roles.
9. Dashboard
After sign-in your home screen is the **Dashboard**: a consolidated view of your workspace's balances, spending split, budgets, savings goals and most recent transactions.
4. Accounts
An *account* represents a concrete money-holding instrument inside a workspace: bank account, cash, credit card, savings, etc. Every transaction is bound to exactly one account (a transfer touches two — source and destination).
Create or edit an account
This page is used to add a new account or update the settings of an existing one.
5. Categories
Categories let you classify transactions so statistics, budgets, and exports can group them meaningfully.
Create or edit a category
This page is used to create a new category or fine-tune an existing one.
Category statistics
This page shows the detailed activity of a selected category.
4. Transactions
A transaction is the atomic unit of CaeliBudget: every income, expense or transfer is stored as one transaction.
4.1 Create a new transaction
This page is used to quickly and accurately record a new income, expense, or transfer between accounts.
Import transactions from CSV
This page is used for bulk transaction upload from a CSV file.
7. Planned transactions
A *planned transaction* is a template that either automatically generates **real transactions** at a fixed cadence, or pre-generates **planned occurrences** that you confirm before they are booked.
Planned transaction form
8. Budgets
A *budget* defines a cap (or target) for one category over a period of time. CaeliBudget continuously shows where you stand against it.
Budget form
This page is used to create or edit a budget linked to a category.
14. Savings goals
The Savings Goals module helps you separate money reserved for specific targets from day-to-day spending. Each goal is linked to a dedicated virtual account that sits beneath a savings account.
Tag list
This page shows all tags available in the workspace.
Create or edit a tag
This page is used to create a new tag or update an existing one.
Profile page
This page is used to manage your own user details and password.
Accessibility

Adjust display preferences for better readability and usability.

Keyboard shortcuts

A limited desktop-oriented shortcut set. Disabled by default.

Focus a field, then press Ctrl + Alt + Shift + a letter or digit. Press Backspace or Delete to clear the binding.
Active only on desktop or installed desktop PWA environments.
Full accessibility manual