Why recurring transactions matter
If you pay for Figma every month, you have two choices: type the same $15 expense into Money OS on the same day every month, or set it up once as a recurring transaction and never think about it again. The second option is why this feature exists.
Recurring transactions are for anything that repeats on a predictable schedule — software subscriptions, retainer income from a client, monthly rent, payroll, or a weekly freelancer payment. Set it up once; Money OS generates the actual transaction automatically when it’s due.
Setting up a recurring transaction
- Go to Recurring in your workspace sidebar.
- Click New Recurring Transaction.
- Fill in:
- Type — Credit (money in) or Debit (money out)
- Description — what it is, e.g. “Adobe Creative Cloud” or “Client X Retainer”
- Amount — the fixed amount that recurs
- Account — which account this transaction posts to
- Category — for reporting and budget tracking (optional but recommended)
- Interval — Daily, Weekly, or Monthly
- Next Run Date — the next date this should generate a transaction
Once saved, Money OS automatically creates a matching transaction on each scheduled date, exactly as if you’d logged it manually — it shows up in your transaction list, counts against any budget in its category, and appears in reports.
What counts as “recurring” vs. what doesn’t
Use recurring transactions for anything with a fixed amount and fixed schedule: subscriptions, rent, retainers, payroll. If the amount varies each time (like a utility bill), log it manually each month instead — a recurring schedule with the wrong amount will silently misstate your budget and reports every cycle until you catch it.
Interval behavior
- Daily — generates a transaction every day. Rarely useful outside of automated systems; most teams use Weekly or Monthly.
- Weekly — generates on the same day of the week as the next-run date you set.
- Monthly — generates on the same day of the month. If you set a next-run date of the 31st and a month has 30 days, Money OS runs it on the last day of that shorter month.
Editing and stopping a schedule
Open any recurring transaction from the Recurring list to change its amount, category, or interval — useful when a subscription price changes. To stop it permanently, delete the schedule. This does not touch transactions it already generated; your historical ledger stays intact.
How this affects budgets and reports
Every transaction a recurring schedule generates is a normal transaction — it counts against category budgets the same way a manually logged expense does, and it appears in every report (Expense Summary, P&L, Cash Flow) exactly like any other entry. There’s no separate “recurring” bucket to check; it’s just part of your ledger.