Skip to main content
Transactions

Setting Up Recurring Transactions

Some business expenses repeat on a regular schedule, VPS hosting, data feeds, software subscriptions. The Recurring feature creates each future entry for you automatically, so you don't have to add the same transaction by hand every month.

How It Works

When you save a transaction with Recurring turned on, it becomes the master for that series. The master is the only entry that holds the frequency and end date.

From there, the system creates a copy of that transaction at each interval — weekly, monthly, or yearly, whatever you set — up to the end date, or indefinitely if you leave the end date blank.

Every copy is a completely standalone transaction, with its own date and its own payment status. Generated copies start as Unpaid until you confirm the payment went through. The master keeps the recurring badge and frequency label, so it's always clear which row is the original source of the series.

Editing an Entry

Every row is independent, including past ones. Editing one entry only changes that entry — nothing else in the series is affected.

This means if a past entry didn't match what actually happened, you can fix it directly. For example, if VPS hosting is normally $50/month but one particular month's charge was actually $55, open that specific entry and change it to $55. Nothing about the master or any other month changes.

Changing the Amount Going Forward

If your cost changes — say VPS hosting goes from $50 to $60 — edit the next upcoming instance and change its amount to $60. Every instance generated after that point will use the new $60 amount. Instances that were already generated before you made the change stay exactly as they were, even if they're dated in the future.

Changing the master itself works the same way: updating the master's amount, frequency, or end date only affects what gets generated going forward. It never reaches back and rewrites entries that already exist in your Transactions list.

Stopping a Recurring Series

Open the master entry and either:

  1. Toggle Recurring off, or

  2. Set an End Date

Either way, the system stops generating new instances from that point on. Every instance already created stays in your records — stopping the series doesn't delete anything.

The Recurring Column

  • The master shows its frequency in the Recurring column (e.g. "Recurring: Monthly")

  • Generated instances show "No" in that column — they're standalone transactions that happen to have been created automatically, so they don't carry the recurring label themselves

The Recurring Filter Tab

The Recurring tab above the table shows only master entries — one row per series, not every instance it's generated. This is your management view: edit the amount, change the end date, or turn a series off, all from the master row shown here.

Generated instances still appear in your main All Transactions list like any other transaction — they just won't clutter this tab, since this tab exists for managing the series itself, not for viewing its output.

Common Recurring Costs

Monthly

  • VPS hosting

  • TradingView subscription

  • Data feed fees

  • News subscriptions

  • Trade journaling software

Annual

  • Software licenses

  • Domain renewals

  • Professional memberships

Income (less common)

  • Retainer fees

  • Affiliate payments

  • Coaching packages

Setting Up a Recurring Transaction

  1. Go to Transactions

  2. Click Add Transaction

  3. Fill in the standard details (name, type, amount, category, currency, date)

  4. Toggle Recurring on

  5. Set the Frequency (Weekly, Monthly, or Yearly)

  6. Optionally set an End Date — leave it blank if the series should continue indefinitely

  7. Save

That's it. The system takes it from there, creating each future instance for you on schedule. You don't need to add anything manually going forward unless an individual month's actual amount differs from what was generated.

Naming Tips

Use clear, specific names so the Recurring tab is easy to scan:

  • ✓ "TradingView Pro — Monthly"

  • ✓ "QuantVPS — Monthly"

  • ✗ "Software"

  • ✗ "Subscription"

Summary

  1. Turning Recurring on makes that entry the master for a series

  2. The system automatically generates each future instance on schedule, up to the end date or indefinitely

  3. Every instance is independent — edit any one of them, past or future, without affecting the rest

  4. Changing the master, or editing the next upcoming instance's amount, only affects what's generated from that point forward — it never rewrites entries that already exist

  5. Stop a series by toggling Recurring off or setting an end date on the master — existing instances are never deleted

  6. The Recurring tab shows masters only, so you can manage each series in one place without the generated instances cluttering the view

Still need help? Ask the team