Scheduled transactions and the calendar

What a schedule is

A scheduled transaction is a template plus a rhythm: any transaction type, expense, income, transfer or loan repayment, with a Frequency and an interval multiplier (weekly with interval 2 means every two weeks). Each schedule chooses how occurrences enter: flip Enter Automatically and Endute creates the real transaction when it comes due, optionally a few days in advance via Enter Days in Advance; leave it off and due occurrences wait for your Enter Now. It starts off for every new schedule. A spending or income schedule on an account whose transactions come in from a bank connection never enters automatically, even with the switch on: we hold it for the bank. The bank's own transaction arrives and is matched to the schedule in review, which moves it on, whereas an entered occurrence would sit beside the bank's and count the money twice. Transfers and loan repayments still enter. The mobile app has no switch for it yet, so turn it on from the web. Schedules made from the future-date prompt enter automatically on the day, which is their whole point, except spending or income held for the bank, where the bank's transaction is matched to them instead.

On the web, a schedule held for the bank shows Waiting for bank rather than Overdue for a week after its due date: its bank transaction has not arrived yet, or is waiting in review. The app shows it as overdue. If you accepted the bank's transaction without matching it, the schedule moves on overnight when that transaction is on the same account, has the schedule's payee, is within 10% of a fixed amount (20% of an estimated one) and is dated within about a week of the due date. Otherwise it shows Overdue after that week: use Skip Next Occurrence to move it on, and fix the schedule's amount, payee or date so the next one matches. If you remove the account's bank connection, or it stays broken for more than 30 days, the switch applies again from the last date the bank sent transactions for, so nothing the bank already brought is entered twice.

Amounts come in two flavours. Fixed for the rent that never changes, and Estimated for the electricity bill that hovers around a number; estimated schedules still match their bank rows, and the imported amount wins.

Schedules meet the bank feed

When a scheduled payment's real counterpart arrives from your bank within a week of its due date, review flags it with a Match: Scheduled badge: one click links the imported row to the occurrence instead of creating a duplicate. This is the quiet payoff of scheduling: the bank feed confirms your predictions rather than competing with them.

Scheduled loan repayments and transfers match too, on the account the money leaves, when Enter Automatically is off (one that enters itself is matched to the transaction it entered). Confirming a loan repayment opens the loan repayment window with the loan, category and payee taken from the schedule and the interest worked out from the loan's rate; confirming a transfer opens the transfer window with the destination filled in. In the app, confirming books it straight away. A loan, or an account the money goes to, with its own bank connection or investment sync is left out: its own transactions arrive too.

A scheduled transfer with an estimated amount is recognised from its second month. The first time, accept the row as a transfer to the account the schedule pays into: the schedule still moves on to its next date and learns the bank's wording from that row. That needs wording that names where the money went, such as the card or account; a row that only says "Direct debit" or carries only your own name is not learned. A transfer accepted to a different account does not move the schedule on.

Managing the list

• Enter Now creates the next occurrence early; Skip Next Occurrence jumps over one without touching the rhythm.
• Deactivating pauses a schedule entirely; the Paused filter keeps them findable for reactivation.
• Closing an account offers to deactivate its schedules; reactivating the account does not reactivate them, so check here after reopening one.

The calendar view

The calendar lays occurrences on a monthly grid as coloured pills: red for expenses, green for income, blue for transfers, grey for loan repayments. A month at a glance answers the question budgets cannot: not how much, but when, which is what keeps a mid-month balance from being a surprise.

Bills your account cannot cover

Each upcoming payment is checked against the account it comes from. Endute projects that account day by day from its current balance and everything you have scheduled, both sides of your transfers included, and if the balance would go below zero on the due day the row carries an amber Short by marker. A summary above the list counts how many payments are affected. Hover the marker and it tells you what to do: how much to move into the account and by which day. Endute records money rather than moving it, so the transfer itself happens at your bank; once it arrives, the marker clears on its own.

A second, lighter marker, May run short, appears when scheduled money covers the payment but your usual spending would not leave enough. That number comes from your budgets, counted only against accounts we have actually seen that spending come out of, so a savings account that never pays for groceries is never warned about groceries. Both numbers assume income due on the same day arrives first, look ninety days ahead, and ignore credit cards, loans and paused schedules.

What next

Schedules power the cash flow forecast and pair naturally with subscription detection, which finds the recurring payments you have not scheduled yet.