Skip to content
SageFin

Recurring bills and subscriptions

SageFin looks through your transactions for things that repeat — subscriptions, regular expenses, bills, a standing transfer — and offers each one to you before treating it as real. That offering is the number beside Recurring in the sidebar, and it is a queue rather than a warning.

The number is a queue, not a problem

It counts merchants SageFin thinks repeat and you have not yet had a look at. It goes up as new patterns appear and down as you work through them.

Nothing breaks if you never do. Your transactions, budgets and reports are unaffected by an unreviewed queue; what you lose is the forecast, because SageFin will not tell you a bill is coming until you have agreed it is a bill.

What SageFin looked for

Pattern matching, not a model reading your data. Something becomes a candidate when:

Most of the time the gaps alone are not enough. A few more rules decide the harder cases:

If you mark a merchant as recurring yourself, the last two rules do not apply to it: your word outranks the pattern. A suggestion SageFin made before these rules existed, that one of them now turns down, is taken out of the queue if you had not touched it.

The Recurring pill beside a merchant in Settings → Merchants means exactly this page's answer: the merchant has a confirmed bill here, or you marked it recurring yourself. A merchant that merely turns up in two different months does not get the pill, and one you marked as not recurring never does, whatever its charges look like.

That is the whole of it. It is deliberately mechanical, which is why it is offered for review rather than applied.

When it looks

SageFin looks again each time new transactions have been categorized, which happens in the background after every bank sync. Right after you connect a bank, a whole history arrives at once and is categorized a batch at a time, so recurring charges can keep appearing for a while rather than all at once. While that is still going on, Recurring says Still looking for recurring charges and how many transactions are waiting.

Three payments are needed before most patterns count, so a monthly bill cannot be spotted until there are about two months of history. When your history is shorter than that, the page says how far back it goes and that more may appear. Once SageFin has been through enough history and found nothing, All recurring says so, with the date it looked back to.

Checking now

You do not have to wait for a sync. Add recurring → Check for recurring now on the Recurring page (the + on the phone) runs the same check straight away and says what it found. Under it, Last checked 34 minutes ago is when SageFin last looked, whether because somebody pressed it or because a sync brought new transactions, and it is kept with your household's data. It is the same pattern matching as above, so it never sends anything to an AI model. It can be run once a minute; a second press inside the minute says how long to wait. Until the first check has been recorded, the line says it also checks after every sync instead.

Charges that had already stopped

A new bank connection can bring years of history, and that history is full of subscriptions you ended long ago. SageFin does not ask you to review those. A pattern counts as still going while its last payment is within two of its own periods of today, plus a week for slow posting: about two months for a monthly charge, two weeks for a weekly one, and two years for a yearly one. A pattern whose last payment is older than that is filed as ended. It is not put in the queue, and it is not forecast.

Ended charges are listed under Ended at the bottom of All recurring, on the web and in the phone app, with the month of their last payment. If you still pay one, Turn back on confirms it, and it goes into the forecast like any other. If a new payment for an ended charge arrives, SageFin offers it for review again by itself.

A suggestion still waiting in the queue moves to Ended the same way once it has missed two periods. A charge you have already confirmed is never filed as ended, even when its payments stop. It shows under Stopped arriving instead, because you said it was yours.

Pending charges

A charge your bank shows as pending is not counted as a payment until it posts, so it never marks a month as paid. It does count as the bill arriving: a bill whose charge for this month is pending is not overdue for this month, is not filed as ended, and is not listed under Stopped arriving. A pending charge also takes its bill's category, so it does not post under another one.

Apple Card charges come from your phone, and Apple Wallet usually shows a charge as pending on the day it is made. When it posts, the next sync from your phone updates the same transaction in SageFin, and it then counts toward its bill.

Reviewing one

Open Recurring and choose Review now in the banner, or Review beside the filters. The review shows one item at a time, with where you are, such as 3 of 29. The up and down buttons, or the ↑ and ↓ keys on the web, move between items.

Three filters choose what you step through, each with its count:

Each item shows its name, which you can change, its type, frequency, merchant and amount, and when the next payment is expected. Under that are the payments it matched, each with the account it was on.

A suggested name

When a bill arrives under statement text such as "Ysi*giles Road Self St", the item may show Suggested name with a plainer one, here Giles Road Self Storage. SageFin's AI made it from the merchant's name alone: no amount, account or date was sent.

Nothing is renamed until you choose Accept, and a name you set yourself is never replaced: a merchant or bill you have named is not given a suggestion. Each merchant is asked about once. The suggestions are made only while Let SageFin read my transactions and receipts with AI is on in Settings → Preferences, and only after someone in the household has said SageFin may use AI.

Why we think this repeats

Each item says in one sentence why SageFin thinks it repeats, for example 3 charges of $12.99 from Vpn on Checking, about monthly on the 11th. Found Oct 29. It is worked out from the payments listed beneath it each time you open the review. A payment that is listed but not counted, such as one at a very different amount, is usually the thing that is wrong.

What each answer does

After each answer the review moves to the next item you have not answered yet, and when there are none left it closes and takes you back to the page. Use the arrows to step back to one you answered and change it.

The reason decides what SageFin may ask about later:

Anything offered again comes back to review as a question, never confirmed for you, and only while the payments are still arriving. Say no again and that answer is the one SageFin keeps.

The reason is kept with the item in your household's data until you turn it back on or confirm it. It is also noted, without the merchant's name, to help improve how recurring payments are found.

If you change your mind about one you dismissed, open one of its transactions and choose Mark merchant as recurring from the actions menu. The same item comes back to Recurring, confirmed.

When nothing is left to review you get You're all caught up, and the badge disappears.

The recent transactions are examples, not the full list

They are there to show you what the pattern matched, not to be an audit of it. If you want every transaction for a merchant, the transactions page with a search is the honest tool for that.

Why a savings transfer is offered as a subscription

Because a monthly transfer to savings and a monthly gym membership look identical to a pattern matcher: same name, same amount, same interval.

They are not the same thing to you, which is the entire reason there is a review step. Dismiss the transfer and it stops asking.

A transfer between your own accounts counts once

When both accounts are linked, a transfer shows up twice: once leaving the account it is paid from, and once arriving at the account it is paid to. A monthly loan payment, for example, appears as a payment out of checking and as a credit on the loan account. SageFin counts it as one recurring item, on the account the money leaves. The credit on the other account is not offered as a second one.

This works from the transfers SageFin has matched up, so it applies once the two sides of a payment have been paired. You can see the pairing on either transaction's details. SageFin does not decide from names alone that two transactions are the same payment. If you had already confirmed or edited the receiving side as its own recurring item, it stays as you left it. Mark it as not recurring if you want only one.

You may also notice that transfers are left out of the monthly recurring total. That is deliberate — money moving between your own accounts is not money going out — and it is why a transfer confirmed as recurring can appear in the list without changing the figure at the top.

After you have confirmed some

Confirmed streams become a forecast: what is due, roughly when, and how much. That is what the Recurring page is actually for — the review queue is just how things get into it.

Each one keeps a next expected date, moved forward by its own rhythm every time it is seen again — including a payment you put in the series yourself from a transaction's details, when it came through under a different name. A stream that stops arriving does not disappear on its own; if you cancel a subscription, mark it as no longer recurring so the forecast stops expecting it.

Your edits stay

If you change a stream's name, amount, frequency, type, category, payment account or next date, that is what it keeps. SageFin goes on reading your transactions after every sync, but it does not overwrite what you set. A next date you set holds until a newer payment arrives, and then the forecast moves on from that payment.

When a merchant's name changes

Your bank sometimes sends a payment with only its statement text, such as "YSI*GILES ROAD SELF ST", and adds a proper merchant name later. A rule of yours, or an edit on the transaction, can rename it too. A recurring item found from the statement text keeps its payments whatever they are called afterwards. Its name follows what the transactions show now, unless you named it yourself.

If one bill was showing up twice on Recurring, once under the statement text and once under the new name, SageFin puts the two back together the next time it reads your transactions. What you set on either one is kept: the name, amount, frequency, type, category, payment account, next date, whether you confirmed it, and any payment you put in it yourself. If you turned one off and confirmed the other, the bill stays on. If you only turned it off, it stays off.

One merchant, two bills

When a merchant charges two amounts side by side, Recurring shows two items under the same name, each with its own amount, its own next date, and its own Stopped arriving when that plan ends. Before, two plans were one item at an amount neither charged, forecast from whichever charged last.

An item you had already confirmed or edited keeps everything you set on it. It becomes the plan nearest its amount, and the other plan arrives in the queue as a new item for you to decide. If you had marked the merchant Not recurring because it is not a bill, it stays one item and nothing new is offered. If you said it was two things merged, the two plans are offered separately.

If they are really one bill, merge them. On the web, open the item with Edit merchant details or View merchant; on the phone, tap it. Choose Merge… beside the other amount and confirm. Every charge of both then counts as one bill, and SageFin will not split them again. Only two items of the same merchant can be merged, and only two next to each other in amount. To undo it, open the merged item and choose Split again: SageFin checks straight away and separates them by amount once more.

Credit card bills

Each linked credit card has its bill on the Recurring page, under Credit cards, on the web and in the phone app. There is nothing to set up: the figures come from your card issuer through your bank connection, the same ones the payment-due reminders use.

Card bills count in the month's totals at the top of the page and in the Credit cards column of the Upcoming and Paid totals. An overdue bill stays on the current month until it is paid.

The Recurring card on the Dashboard, on the web and in the phone app, lists them too, with the same status and due date, and counts what is still owed on them in its remaining due figure. A card with no balance shows a dash there and is left out of that figure, with a line saying so.

Your card issuer reports only the current bill, not a history, so a card's earlier bills do not appear when you look back at a past month. Hiding a card on the Accounts page takes its bill off the Recurring page too.

A card with no bill

Some cards are listed with Reconnect this card to see its bill. Their bank was connected before SageFin asked for permission to read card bills. Choose Reconnect and approve the request, and the bill appears after the next sync. If a card says This bank does not share card bills, its bank does not offer them, and reconnecting will not change that.

Apple Card is not listed. Apple Wallet does not give SageFin a statement balance for it.

Adding one SageFin did not find

Some things repeat without looking like it — a yearly bill you have only paid once, a merchant whose name changes slightly each time. Add recurring → Add manually on the Recurring page (the + on the phone) lets you pick the merchant yourself, and it goes straight in as confirmed.

What this is not

It does not pay anything. SageFin reads; it cannot pay a bill, cancel a subscription, or move money. A forecast is a list of what is coming, not an instruction to anybody.

It is not connected to your biller. The rhythm comes from your own transaction history, so a change in date shows up after the first payment at the new date, and a change in price after the second payment at the new price — not before. Credit card bills are the exception: their amount and due date come from your card issuer.