> ## Documentation Index > Fetch the complete documentation index at: https://docs.guito.pt/llms.txt > Use this file to discover all available pages before exploring further. # Recurring movements > Detect and track subscriptions, rent, and salaries, and see the upcoming forecast charges in your cash flow. The **Recurring** section gathers everything that repeats at regular intervals: subscriptions, rent, salaries, and other fixed expenses and income. guito detects these series in your real movements, projects the upcoming charges into your cash flow, and can alert you when an expected payment doesn't show up. A recurring series is a forecast, not a movement: it shows what's coming, but never writes anything into your accounts. If you'd rather have the movement written automatically, create a [**scheduled transaction**](/en/features/scheduled) instead. The Recurring section is part of the Plus plan. ## Where to find it Select **Recurring** in the sidebar, under the **Activity** section. The top, under **Upcoming movements**, brings together everything with money going out or coming in over the next few days: forecast recurring charges, scheduled movements and credit instalments, in one list ordered by date. When two things fall on the same day, the larger one comes first. Below, everything that repeats appears in two groups, **Expenses** and **Income**. Rows that are no longer charging are dimmed and say why; the ones recorded automatically carry a **Scheduled** mark. Each series' details show the monthly and yearly equivalent: a yearly subscription appears converted to its cost per month. Monthly charges keep their original day. A series starting on January 31 falls on February 28 (29 in a leap year), then March 31. ## How recurring series appear A recurring series can be created in two ways: detected by guito or added by you. ### Detected by guito guito regularly scans your real movements for charges that repeat with a consistent amount and rhythm. When it finds candidates, it shows a card at the top of the Recurring page ("We found recurring charges in your movements") with the suggestions: * **Confirm** adds the suggestion to your recurring series, already linked to the history of charges that produced it. * **Dismiss** removes the suggestion. You can undo right away if you change your mind. When you open a movement that matches a detected pattern, you will also see a **Looks recurring** suggestion in its details, with the option to confirm it from there. ### Added by you Use the **Add** button in the top-right corner and enter the subscription, rent, salary, or other recurring movement you want to track. On a manual account with a fixed amount, the **Recording** question decides which one you get: **Only count on it** creates a recurring series; **Record automatically**, the preselected option, creates a [**scheduled transaction**](/en/features/scheduled) instead. You can also turn an existing movement into a recurring series: open it and choose **Make recurring**. guito prefills the details and links that movement to the series, building its history. ## A recurring series never writes a movement If you want guito to write the movement automatically, use a [**scheduled transaction**](/en/features/scheduled) instead. If both point at the same payment, your forecast balance won't count it twice — but keeping both is double the upkeep, so pick only one way to track each payment. In **Transactions**, a movement already linked to a recurring series carries the recurring mark next to its name, on every list. Turn on the **Forecast** toggle to see the charges not yet confirmed, out to the end of next month, labelled "Predicted". When the real charge arrives from your bank or is entered by hand, guito automatically links it to the series and the forecast row gives way to the real movement, with no duplicates. A movement recorded by a scheduled transaction isn't linked this way: it lands in the account as a normal movement, just carrying the scheduled mark. Small variations in the amount (a price increase, for example) are still recognised as the same series. ## A fixed amount or a range Not every expense lands on the same number. When you create a recurring series, the **Amount** field asks what kind of amount it is: **Fixed amount**, for rent or the gym, or **Range**, for electricity or groceries, where you enter both numbers: €18.00 **up to** €24.00. A range changes three things: * **It is never recorded automatically.** With no exact number to write, the movement always waits for the real charge, even on a manual account. Only a fixed amount lets you choose between the two, under the **Recording** question (see [Scheduled transactions](/en/features/scheduled)). * **The amount shown is the middle of the range**, written without cents (for example, €21), so it reads as an estimate rather than a promise. That's the number counted toward the monthly equivalent in the series' details. It also drives the forecast balance until three real charges have been matched to the series; from then on, guito forecasts the average of those charges instead. * **Record asks for the amount.** Once the expected date has passed on a manual account, the **Record** button doesn't write the middle of the range: it opens a box for what actually left the account. ## Exact amounts and estimates guito doesn't always know the exact amount of a charge that hasn't happened yet, and the way it writes the number tells you which of the two it is. * **Without cents** (for example, €21) is an estimate: a bill that varies from month to month, like water or electricity, or the middle of a range you declared. It's the most likely number, not a promise. * **With cents** (for example, €9.99) is an exact amount: a charge that has already happened, an amount you typed, or a credit instalment. In sentences, and for anyone using a screen reader, an estimate is read as "about €21". ## What guito says about a charge Until the expected date arrives, a recurring series shows only the day. From then on, and only while the charge hasn't appeared, it gains one of these words: | What you see | What it means | | - | - | | Expected today | The expected day is today and the charge hasn't arrived. It may well arrive during the day. | | Not arrived yet | The expected day has passed, but within what is normal for this series. A bill that usually leaves two days later isn't missing because of that. | | Missing | The expected day has passed, along with the margin this series usually takes. It's the only wording that says a payment really is missing. | | Learning this series' rhythm | The charges guito has seen don't line up with the recorded frequency. Rather than give you a wrong date, it prefers not to give one until it works the rhythm out. | The margin before a charge is called missing is worked out from each series' own history, and isn't the same for all of them: one that always leaves on the same day is called missing sooner than one that moves around. ## Missed payments: Record or Dismiss When the expected date passes without a matching charge, the forecast row is flagged as **due**. On a manual account, that row shows two options: * **Record** creates the real movement with the series' details, so you don't have to enter it by hand. If you declared a range, guito asks for the amount first: type what actually left the account and confirm. * **Dismiss** says that movement didn't happen. The forecast stops appearing and no movement is created. It only affects that cycle: next month is still forecast. An **Undo** appears right after, in case you didn't mean it. On automatically synced accounts, neither option appears, because the real charge arrives from the bank and is linked automatically; recording it by hand would create a duplicate. If a scheduled transaction already recorded the same bill, guito treats that cycle as paid without creating another movement or using it to learn the series' rhythm. Matching requires the same merchant, compatible amount and date, and a unique pairing. Different bills with similar amounts stay separate. ## Charges outside the range When you declared a range and the real charge comes in above or below it, the movement is still linked to the series. What's in doubt is the range, not the movement, and that's what the question under the movement, in **Transactions**, offers to settle: * **Update to €18.00–€31.40** widens the range until it covers this charge. The amount shown becomes the middle of the new range. * **Not this one** unlinks this movement from the series. It stays in the account like any other; it just leaves the series' history. * **Just this month** keeps the range as it is and stops asking about this movement. ## Missed-payment reminders Edit the series and turn on **Missed-payment reminders** to get an email when an expected payment doesn't show up. Reminders are off by default and configured per series. Each reminder ends with a link, **Stop this type of email**, that turns them off for that series only. See also [email notifications](/en/account/email-notifications). ## Pausing and inactive series Resuming keeps the original payment day and forecasts from the resume date onward. It does not ask you to record payments from the paused period. * **Pause:** you can pause a series that is charging or hasn't started yet (for example, a subscription you suspended but don't want to delete) from its details: in the list, click the row and use **Pause**. Paused series stop counting toward the forecast, and you can resume them whenever you want, in the same place. * **Inactive:** when a series stops charging for several consecutive cycles, guito automatically marks it **inactive**. It stops producing forecasts but keeps its history. * **Where they go:** a series that is not charging stays in the list, in the same place, just dimmed, and doesn't count toward the forecast until it charges again. The reason sits under its name: | Reason | What it means | | - | - | | Paused | You paused it and can resume it whenever you want. | | Not started | Its start date hasn't arrived yet. | | Ended | It passed the end date you set. | | Inactive | It stopped charging for several consecutive cycles. | | On hold | Scheduled transactions only: the account has since been connected to a bank. | ## Small amounts Recurring series under €1 per charge are grouped into a single row, **Small amounts**, at the end of the active list, and don't appear under **Upcoming movements** or in [notifications](/en/features/notifications). Missed-payment reminder emails don't change: if you turned them on for one of these series, they still arrive. They're almost always cent-sized dividends or stamp duty, detected from your movements, and they were taking the place of bills that matter. Open the row to see them all: they're still there, with their full history, and you can rename, pause or delete any of them as before. Nothing is deleted or permanently hidden, and the forecast balance still counts them. The grouping only applies to series guito detected. A scheduled movement or a credit instalment you created is never grouped, however small the amount: you're the one who wrote it down. ## Edit or delete Click a series to open its details, where you can see its charge history and insights (such as annual cost and lifetime spend), make changes, or delete it. The range is editable here too. The fields open with what you typed (for example, €18.00 up to €24.00) rather than the midpoint: widen it if your bills went up, or tighten it if they settled. To go back to a fixed amount, switch the kind to **Fixed amount**: the second box disappears and the number left in the first one is what gets saved. If a recurring item ended up on the wrong side, say a salary saved as an expense, edit it and pick **Expense** or **Income** in the **Type** field. The amount stays; the category is kept only if it exists for the new type, otherwise choose another. ## Related pages Templates guito records on its own, with the amount you set. Where the forecast rows and the Record button appear day to day. Connect your accounts so movements arrive automatically. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.