Subscriptions and recurring expenses

Detection looks at your expense history and finds repeating merchant patterns over time. It combines description similarity, amount tolerance, and spacing between charge dates to decide whether something is likely recurring.

The system is keyword-aware and service-catalog-aware, so known subscription services can be recognized even when statement text varies slightly month to month.

Cycle detection uses date history across charges. This makes monthly plans less likely to be misread as weekly or quarterly when there are normal date shifts.

Amount matching allows small natural variation, such as exchange-rate drift or minor tax rounding. A service is not split into duplicates just because one month is slightly higher or lower.

When you edit and confirm a subscription, the system treats that record as user-controlled. Future detection should not overwrite your important edits such as service name, cycle, or amount.

If detection finds similar history later, it tries to match existing records first and update safely. It also avoids creating duplicates when an existing active or inactive row already represents the same service.

Renewal maintenance moves past-due subscriptions forward to the next valid renewal date. It uses your manual override date when one exists, otherwise it uses the current renewal value.

Maintenance can run from the Update button and also runs automatically when needed, so overdue renewal dates are corrected without constant manual cleanup.

For reminders, you can enable or disable notifications per subscription and set reminder lead time (for example same day, 2 days before, or 7 days before).

If you rename a service in Subscriptions, the app can suggest creating an automation rule from that new name. This is the same automation concept used in Review description edits.

Before opening the automation modal, the app checks whether an existing active automation already covers the keyword. If coverage already exists, it does not prompt you again.

You upload three months of expenses and the same service appears as "NETFLIX.COM", "Netflix", and "Netflix EU". Detection groups them, identifies a monthly pattern, and sets one subscription record with an estimated next renewal.

You then rename it to "Netflix Premium" and keep the cycle monthly. Later detection runs should keep that edited record instead of resetting it, and automations can be suggested so future uploads normalize to the same naming style.

Detection is strongest when you keep Review descriptions clean and upload data continuously by month.