enhancing recurring payments

[throlan]

First of all, thank you for Yuvomi. I have been testing several self-hosted solutions for household budgeting and planning, and Yuvomi is by far the closest to what I was looking for.

One feature that would make recurring payments much more useful would be the ability to define when a recurrence ends.

Current situation

Recurring payments/subscriptions can have a frequency and a next payment date, but there does not seem to be a way to specify an automatic end.

Many household expenses are recurring but not permanent.

Examples:

• Rent ending when moving to another home
• Car lease for 36 or 48 months
• Loan repayments
• Furniture paid in 10 monthly installments
• Temporary subscriptions
• Insurance contracts with a known end date
• Temporary recurring expenses related to a project

Suggested implementation

When creating or editing a recurring payment/subscription, an "Ends" option could be added:

• Never
• On a specific date
• After X occurrences

For example:

Frequency: Monthly
Start date: 01/10/2026
Ends: On date
End date: 30/09/2030

or:

Frequency: Monthly
Ends: After 48 occurrences

Expected behaviour

Future budget projections should only include occurrences up to the defined end date / occurrence count.

Once the final occurrence has passed, the subscription could automatically become inactive or be marked as completed.

Why this would be useful

This would make Yuvomi much more suitable not only for traditional subscriptions, but also for general household financial planning.

It would allow users to accurately forecast expenses several months or years ahead without having to manually remember to disable recurring payments.

An optional end date would preserve the current behaviour for users who want subscriptions to run indefinitely.

Thanks for considering it!

[ulsklyc]

Thanks for the detailed suggestion, this is now implemented (PR #607).

Every subscription gets an Ends option:

• Never (default, unchanged)
• On a date
• After N payments

Renewals advance until the end is reached; the payment on the end date (or the N-th payment) is the last, after which the subscription is automatically marked completed and drops out of the monthly total and the renewal forecast, while staying visible with a distinct "Completed" state. Future projections only count occurrences up to the defined end, exactly as you described.

It will ship in an upcoming release. Closing as resolved, thanks again!