Recurring transactions

Scheduled lists your recurring and upcoming transactions: rent, subscriptions, salary… Create a recurrence instead of re-entering the same transaction every month.

Creating a recurrence

Enter the first occurrence and its frequency: once, daily, weekly, monthly, yearly — or set dates, when the instalments follow no cadence at all.

Two fields name the operation:

• Payee — the merchant, whoever you bought from.
• Financed by — the payment plan provider, when there is one: PayPal, Klarna, Alma… This is not the payee. On your bank statement the line will often show the provider rather than the merchant; keeping them apart lets you read “DELL” while still recognising “PAYPAL” when the money leaves. The field is free text: type a new name and it exists.

Dates that follow no cadence

A pay-in-instalments plan announces dates that nothing computes. A real example: 21 September, then 21 October, 20 November and 19 December — thirty days, thirty days, then twenty-nine. No monthly rule lands on those: the closest one would place the last instalment two days late, and your forecast would be wrong by that much.

The set dates frequency stores the dates exactly as announced, one per instalment. There is then no interval, no day of month and no weekend behavior to choose — the date written is the date meant. The end is derived: four dates make four occurrences, and the row shows where you stand, “2 of 4”.

Pasting a payment plan from an email

The Paste button at the top of Scheduled saves you from re-typing what the message already shows.

Paste the summary, click Analyse, and review before anything is written.

What Arca can read

Every line must carry a date and an amount. Everything else is free: the order of the two, the language, whether a currency symbol is there at all, bullets, tabs.

What varies	Examples that work
Order	$287.25 on 21 October 2026, or 21/10/2026 then 287.25
Date	on 21 October 2026, 21/10/2026, 21.10.2026, (21/09/2026), due today
Currency	287.25 €, 287,25 EUR, $287.25, or nothing at all
Shape	bullet list, tab-separated columns, full sentence
Language	English and French — due today as well as dus aujourd'hui
Thousands	1,234.56, non-breaking space included

Three real blocks, exactly as you paste them:

$287.25 due today
$287.25 on 21 October 2026
$287.25 on 20 November 2026
$287.25 on 19 December 2026

On shipping date (22/09/2026)  52.50 €
22/10/2026  52.50 €
21/11/2026  52.50 €
21/12/2026  52.49 €
Order total (taxes and shipping included)  209.99 €

1st instalment on 30/09/2026: 410.33 €
2nd instalment on 31/10/2026: 410.33 €
3rd instalment on 30/11/2026: 410.34 €

The last one is the most telling: uneven month ends, a different final cent. No cadence produces it — which is exactly what set dates are for.

What Arca refuses to guess

A line without a date, or without an amount, is not interpreted. It is counted under Not recognised, stays visible, and creates nothing.

That rule — and only that rule — is what keeps totals out: “Order total: 209.99 €” carries no date, so it is never taken for an instalment. No word is recognised along the way: Arca does not know what “total” means, and that is deliberate. A reader that knew one merchant’s vocabulary would never know the next one’s.

An amount without two decimals is not enough either when the currency is missing: in “Instalment no. 2”, the 2 stays a number, never $2.00.

The review step

At the top, what will be created: the number of dates, their span, and the total — which follows whatever you uncheck. Every line can be corrected, date and amount, and unchecked.

Two signals stop you:

• an amber border on the amount: it was read without a currency symbol. That is a weak signal, and Arca says so rather than letting you assume it is certain;
• a line unchecked on arrival: it is worth the sum of all the others, so it is almost certainly a total — even when it carries a date, like “Total on 21/12/2026”. Nothing is removed: check it back if you were right.

The button counts what it will create: “Create the plan · 3 instalments”.

If the first instalment is today

That is the case of a deposit paid at purchase time. On creation, Arca looks for a transaction on the account with the right amount within two days and links it — your already imported payment is not duplicated. If it finds none and Create the transaction automatically is ticked, it records one.

If you paid but the transaction does not exist yet, uncheck the first line: nothing will be written for it.

A message confirms what happened and offers Undo — one gesture removes the plan, the payee created along the way and the recorded transaction.

Weekend behavior

If an occurrence falls on a weekend, choose the behavior:

• Keep — the date doesn’t change,
• Move earlier — shift to the last business day before,
• Move later — shift to the next business day.

Ending the recurrence

A recurrence can end never, after N occurrences, or on a given date.

The status of each recurrence

Every row carries its status. It is computed as it is read, never stored somewhere it could go stale:

• Paid — a transaction from this cycle is attached to it,
• Due — that’s today,
• Upcoming — within two weeks,
• Missed — the date has passed and nothing has settled it,
• Scheduled — further out than that,
• Completed — it no longer produces anything.

When the number of occurrences is known — an “after N” recurrence, or set dates — the row also shows where you stand: “2 of 4”.

Recurrences are grouped under This month, then Later; completed ones wait behind a fold, collapsed by default. At the top, two figures sum up the month: what is paid this month — the total of the transactions actually attached, not of the expected amounts — and what is left to pay. The bar joining them carries one segment per recurrence, as wide as its amount: filled when it is settled, hollow otherwise.

Post, skip, complete

A row’s ⋯ menu only offers what makes sense for that row:

• Post now — records this occurrence’s transaction, on its expected date. If a matching transaction already exists, it is attached rather than duplicated,
• Skip this occurrence — moves on to the next date without recording anything, for a month where the charge never happened,
• Complete — the recurrence stops and joins “Completed”,
• Reopen — puts it back in service,
• Edit and Delete.

Every one of these can be undone with ⌘Z (Ctrl+Z on Windows and Linux), and a message says so as it happens.

Recording the transaction, or only announcing it

In the form, Create the transaction automatically decides whether Arca records the transaction for you on the expected date. Unchecked, the recurrence only announces: it shows as “due”, then “missed”, and Post now records it whenever you choose.

The amount can be Exact or About, with a tolerance in percent. An electricity bill never lands twice on the same cent: without a tolerance, Arca does not recognise yours and adds a line next to it.

Attaching a transaction to a recurrence

Arca attaches a transaction to its recurrence on its own when it falls within two days of the expected date, on the right account and for the right amount. A charge taken earlier than planned, or for an unexpected amount, stays on its own — and the recurrence ends up adding a second line next to it.

From the register, a row’s ⋯ menu (or a right-click on the row) then offers:

• Link to a schedule — the list of active recurrences, filtered from the start on the transaction’s account. Each line shows its status, its amount, and the gap between its date and the date of the transaction you are attaching. If the right one doesn’t exist yet, Create a schedule opens the form already filled in from the transaction.
• View schedule and Unlink schedule, once the transaction is attached.

An attached transaction won’t be duplicated any more: the recurrence treats that date as settled. Unlinking frees the transaction, without reopening dates that have already passed.

The same menu also offers Create a rule from the transaction and Duplicate (a copy dated today, not cleared).

Detected subscriptions

Below the recurrences, Regular payments found lists the payees your transactions show as being charged regularly, and that no recurrence covers yet. The detection runs on your device: nothing is sent anywhere.

Each line gives the median interval between charges and how many times it was seen. The amount on the right is the cost over a year, and the yearly total for the whole list appears in the header.

• Track opens a new recurrence, pre-filled with the payee, the amount and the next date,
• Ignore removes the line for good; a message offers Undo right after.

Seeing your schedules on a calendar

The Calendar, right under Scheduled in the sidebar, shows your schedules on a month grid, occurrence by occurrence. See reading the calendar for its legend and its actions.