Bills
Bills track your recurring payments — rent, utilities, subscriptions, loan repayments, and more. The app reminds you when payments are due, automatically advances due dates after each payment, and can even auto-pay bills by creating transactions on their due date.
Adding a Bill#
Navigate to Bills > Add Bill to create a new bill.
| Field | Description |
|---|---|
| Name | A descriptive name for the bill (e.g., "Electric Bill", "Netflix", "Mortgage"). |
| Amount | The expected payment amount. For variable bills, enter your typical or average payment. |
| Frequency | How often the bill recurs. See Frequency Options below. |
| Due Day | The day of the month (or week) the payment is due. |
| Start Date | Optional. The bill only occurs on or after this date — useful when a recurring cost changes mid-year: end one bill and start its replacement at a specific date. |
| Category | The spending category to assign when marking paid. |
| Account | The account the payment comes from. Required for auto-pay, and needed for "Mark Paid" to record a transaction. It must be an account you can post to, so not one shared with you read-only, and on a bill someone shared with you it must also be one the bill's owner can use, so the owner can still pay it. |
| Auto-Detect Pattern | A text pattern to match imported transactions against this bill (e.g., "NETFLIX" or "ELECTRIC CO"). When an import or bank sync brings in a matching transaction (amount within 10%, dated near the due date), the bill is automatically marked as paid with that transaction linked — no duplicate money movement, and the Bills Calendar ticks the month off. If the payment had already been marked paid, the bank's transaction takes its place; see When the bank transaction comes in later. A bill with no pattern is matched by its name instead, more strictly; see Bills with no pattern. |
| Exclude from Forecast | Marks the bill as extraordinary: transactions it generates are left out of forecast projections (they still affect your balance). |
| Create future transaction | On by default. Keeps a scheduled placeholder transaction for the bill's next due date, so upcoming payments appear in the transaction list and forecasts. Untick to opt this bill out — no placeholders are ever created for it, including after marking it paid. Toggling it on a saved bill takes effect immediately (the pending placeholder is created or removed). |
| Notes | Optional free-text notes about the bill. |
Tip: Setting an auto-detect pattern helps the app automatically recognize bill payments when you import bank statements, saving you from manually marking each one as paid.
Frequency Options#
| Frequency | Description |
|---|---|
| Weekly | Every 7 days on the same weekday. |
| Biweekly | Every 14 days (every other week). |
| Monthly | Once per calendar month on the due day. |
| Quarterly | Every 3 months. |
| Semi-Annually | Every 6 months. |
| Yearly | Once per year. |
| One-Time | A single payment with no recurrence. See One-Time Bills. |
| Custom | Select specific months of the year when the bill is due. Useful for bills like property tax or insurance that occur on an irregular schedule. |
A paid bill shows as Paid until a week before its next date, when it turns Due Soon. For a Custom bill that is a week before the next month it is due in, however far off that is, so an invoice due once a year does not offer Mark Paid again a month after it was paid.
One-Time Bills#
One-time bills represent a single expected payment — for example, an annual registration fee or a final installment. For a one-time bill the schedule fields give way to a single Due Date, and that date is taken literally: it can be in the past, so an invoice you are entering late stays due on its own date (and shows as overdue) instead of being rolled forward to next year. After you mark a one-time bill as paid, it automatically deactivates itself and stops generating reminders. It stays visible in the bills list (shown as Paid) while its payment can still be reverted, so Mark Unpaid remains reachable — see Marking Bills as Unpaid.
Switching a recurring or Custom bill to One-Time keeps the payment it already has. If the date you give it is the one the bill last paid, give or take a few days, the bill stays paid and Mark Unpaid still works on it. A later date, such as a final invoice after the last month you paid, is due as normal.
A one-time bill saved before the Due Date field existed may have been saved without a month. The app then made a date up for it, 1 January of the following year or the invoice's day in the following year, and that date can't be told apart from one you entered. Such a bill shows a Check date badge, and its edit form says the date was filled in for it. Pick the right date and save, and the badge goes.
Note: If you need to reactivate a one-time bill without reverting its payment, edit it and change the status back to active.
Auto-Pay#
Auto-pay removes the need to manually mark a bill as paid each period. When enabled, the app automatically creates a transaction in the linked account on the bill's due date via a background job. In an account you import statements into or sync from your bank, the transaction is pending until the bank's own transaction comes in and takes its place; it counts in your balance meanwhile. In an account you keep by hand it is cleared straight away.
How to Enable#
- Edit the bill and toggle Auto-Pay on.
- Ensure the bill has an Account set — auto-pay requires a linked account to create the transaction.
How It Works#
- A background job runs daily and pays each auto-pay bill that is due, by your own date rather than the server's (see Dates follow your timezone). A bill several payments behind catches up in one run, with each payment dated on its own due date, up to 60 payments at a time. Where the bank's transaction for one of those payments has already been imported from a statement, that transaction is used rather than booking a second payment beside it.
- When triggered, it creates a transaction in the linked account for the bill's amount and category.
- The bill's due date advances to the next occurrence automatically.
- Bills with auto-pay show an Auto-pay badge in the bills list.
When Auto-Pay Fails#
If the payment can't be recorded (for example, the linked account was deleted or is no longer shared with you), the bill is left unpaid, auto-pay is turned off, the bill shows a warning badge and you get a notification saying why. Fix the issue and turn auto-pay back on.
Tip: Auto-pay works best for fixed-amount bills like subscriptions or loan payments. For variable bills like electricity, consider marking them paid manually after confirming the amount.
Marking Bills as Paid#
Click Mark Paid on any bill to record the payment. This:
- Creates a cleared transaction in the linked account for the bill amount and category, dated today.
- Advances the due date to the next occurrence based on the frequency.
- Pre-creates a scheduled transaction for the next occurrence, so the upcoming payment is visible in the transaction list and forecasts (unless the bill's Create future transaction option is unticked).
- Shows an Undo notification for a few seconds, allowing you to reverse the action immediately — and even after the notification is gone, the payment can still be reverted with Mark Unpaid (see Marking Bills as Unpaid).
Mark Paid always pays the payment shown on the row, and only that one: a bill two payments behind takes two clicks. If the page has been open for a while and that payment has since been recorded, by an import, by auto-pay or by someone you share the bill with, the app says so and reloads the list instead of paying the next one. Skip does the same for a date that was already paid or skipped.
Each click counts once. Mark Paid, Skip and Mark Unpaid stay disabled until the action has finished, and the second click of a double click is ignored, so it cannot pay the next bill when the list moves under the pointer or answer the dialog the first click opened. The same payment sent from two tabs at the same moment is only recorded once.
Note: The pre-created transaction for the next occurrence is a placeholder, not a second payment. It carries a Scheduled badge, is shown in italics, and is not counted toward your current balance or the transaction list total. It stays that way until you pay the bill, even once its date has passed, because an unpaid bill hasn't moved any money. When you mark the next occurrence paid, this placeholder becomes the real payment — it is not duplicated. See Transaction Status for details. If you prefer not to see these placeholders at all, untick Create future transaction on the bill.
Marking a bill paid after its due date works the same way: the payment transaction is dated the day you mark it paid, and the due date still advances from the original schedule (a bill due on the 1st stays due on the 1st of the next month, even if you paid on the 2nd).
Editing a bill keeps its payments. Its next due date only changes when you change the schedule, such as the frequency, due day or start date, and then it moves within the same period: never back onto a payment already made or skipped, and never on past one still owed.
When Mark Paid is not offered#
Mark Paid, Skip and Mark Unpaid all write to the bill's account, and for a recurring transfer to its destination as well, so they are only offered when you can write to those accounts. On a bill someone has shared with you, the accounts have to be shared with you at Read & Write too, not only the bill. A bill with no account only needs the bill itself to be shared. The same goes for Record transaction and Mark Unpaid on the card of payments without a recorded transaction.
On your own bill, the buttons go when its account is one you can no longer write to, such as an account someone shared with you whose share has ended or turned read-only, and the bill says what to do instead: edit it and choose another account. A recurring transfer whose destination was let go, because the share ended, the account was closed or its owner reset their data, is refused with This bill uses an account you can no longer change. Edit the bill and choose another account. until you choose a new destination, and auto-pay stops for it in the meantime.
Dates follow your timezone#
Today, Due Soon, Overdue, this month's totals and the balances as of today all use your own date, from the timezone Nextcloud has for you, not the server's. A server usually runs on UTC, so without this a bill due today showed as overdue every evening in America, and a payment made just after midnight in Australia was missing from the balance until midday.
When the bill already has a payment#
If the bill already holds a payment for the date it is due, for example a transaction you filed under it with Link to bill, or the payment it had when an older version made it due again, Mark Paid asks about that before anything else, in a Payment already recorded dialog: This bill already has a payment on (date) (amount). Use that payment marks the bill paid on that payment's date and records nothing new. Record another payment carries on as normal, for a bill that really was paid twice, including the Existing Transaction Found dialog below when there are other candidates. Cancel leaves the bill as it is. A payment the bill made for its previous date does not count, even one made late.
When the payment is already in your register#
If transactions that plausibly match the bill (by amount or name, near the due date) already exist — for example from a bank import — an Existing Transaction Found dialog appears before anything is created. Choose link to attach the existing transaction to the bill (nothing is recorded twice), or Create a new transaction instead if none of the candidates is the actual payment. Only transactions in accounts you can write to are offered, so nothing in an account shared with you read-only can be linked. The dialog also offers "Don't create any transaction (just mark as paid)" — use this only when the payment genuinely should not appear in this account's register, because your tracked balance will not reflect the payment and will drift from your bank.
Whichever option you pick, the bill is marked paid and, unless it is a one-time bill, moves on to its next due date. The choice is only about this payment: whether a placeholder is pre-created for the next occurrence is decided by the bill's own Create future transaction setting, exactly as when you skip an occurrence. If you import your transactions and link or skip on most bills, you will still see the upcoming occurrence in the transaction list and forecasts — that is the placeholder for next time, not a bill left unpaid.
Important: If the bill has no account assigned (or the transaction cannot be created), the bill is still marked paid but no money movement is recorded — your account balance will not reflect the payment. The app shows a clear warning when this happens. Assign an account to the bill, or add the transaction manually, so your tracked balance stays in step with your bank.
When the bank transaction comes in later#
You can mark a bill paid, or let auto-pay pay it, before the statement that shows the payment arrives. When that statement is imported, or bank sync brings the payment in, the bank's transaction takes the place of the one the app booked, so the payment is only counted once. It has to carry the bill's Auto-Detect Pattern, be within 10% of the amount and fall near the due date, as for any imported payment.
Bills with no pattern#
A bill with no Auto-Detect Pattern is matched by its name. The bank's transaction has to:
- be in the bill's account (a bill with no account isn't matched),
- be the same amount to the penny,
- be within 5 days of the payment the app booked, or of the due date if the bill hasn't been paid yet (change this under Settings > Import & Export > Bill match window), and
- name the bill. Capitals and punctuation don't count, and whole words are compared, so "Octopus Energy" matches "OCTOPUS ENERGY", "Claude.ai" matches "ANTHROPIC* CLAUDE", and "Ee" matches "EE LIMITED" but not "COFFEE". A name the bank cuts short still matches, such as "Dwr Cymru Welsh Water" and "DWR CYMRU WELSH WA".
The bank's transaction then takes the place of the booked payment, or pays the bill if it was still waiting. If a transaction could be the payment of more than one bill, or two transactions could be the one payment, nothing is guessed: they are imported as they are, the import tells you how many, and you can match them from Find Duplicates on the Transactions page or with Link to bill in the transaction's menu. A different amount, even by a penny, is a different payment; if a bill's amount changes, update the bill or give it a pattern.
This works for every one of the bill's payments the statement holds, whichever order it lists them in. A weekly bill that auto-pay paid four times before you imported the month's statement has all four payments replaced by the bank's, each by the transaction nearest its own date. Anything you added to the payment the app booked moves across to the bank's transaction: a split with a shared-expense contact, receipts, tags and your notes.
A payment you have reconciled against a statement is never replaced. It stays as it is, and the bank's copy of it is not used to pay the next one instead.
Marking Bills as Unpaid#
Marked a bill paid by mistake? Every payment records what it changed, so the most recent one can be reverted properly at any time — not just while the Undo notification is showing. Click Mark Unpaid on the bill and confirm. This:
- Deletes the transactions the payment created (and the matching transaction on the destination account for transfers), including one added afterwards with Record transaction. A payment that was linked to an imported transaction unlinks it instead — money that genuinely left your bank is never deleted — and the pre-booked transaction it replaced comes back. If you already deleted a payment transaction yourself, the revert carries on without complaint. If the payment was reconciled against a bank statement, you are warned first, as the account will no longer match that statement.
- Rolls the due date back to what it was before the payment — a bill that advanced to next month comes back to this month.
- Reactivates a one-time bill, so it returns to your active bills instead of staying vanished.
- Restores the exact amount for statement-balance and other dynamic-amount bills. These amounts are read from the card's ledger at payment time and cannot be recomputed later, so the recorded value is put back as it was.
- Restores the remaining-payments counter where the bill uses one.
Auto-paid bills and bills matched from an import can be reverted the same way — useful when auto-pay fired for a payment that didn't actually happen. If auto-pay is still on, the confirmation reminds you that it may pay the bill again on its next run, so disable auto-pay first if the payment should not recur. Recurring transfers have the same Mark Unpaid action in the Transfers view.
Note: Only the most recent payment of a bill can be reverted, and the stored revert is discarded when you edit the bill's amount, schedule, or accounts — reverting after such an edit would restore values from before your change. Marking the bill paid again replaces the stored revert, and deleting a payment transaction by hand does not unmark the bill — use Mark Unpaid so the due date and bill state roll back together.
Payments the bank hasn't shown#
In an account you import statements into or sync from your bank, a card at the top of the Bills page lists the bill payments no bank transaction has turned up for a week on:
- A bill more than a week overdue with no payment found. Its placeholder stays scheduled and out of your balance. If the payment did go out, Mark Paid; if it was skipped, Skip; if the payments have stopped or moved to another account, Edit bill to end or change it.
- An auto-paid payment still pending. It counts in your balance, but no bank transaction has taken its place, perhaps because the bank took a different amount. Once you have checked it went out, It went out marks it cleared.
Payments without a recorded transaction#
If any bill was marked paid in the last 60 days without a transaction being created or linked, a warning card appears at the top of the Bills page listing those payments. Your account balance does not reflect them, so it will drift from your real bank balance until they are recorded. Click Record transaction on an entry to book the missing payment — it is dated the day the bill was marked paid, linked to the bill, and created on both accounts for transfers. Payments skipped with the Skip button are not flagged (skipping is explicitly "no money moved").
If the payment should not be recorded, because it was paid some other way or you removed the transaction on purpose, click Dismiss and the entry leaves the card. The bill stays marked as paid, and only that one payment is dismissed, so the next payment of the same bill without a transaction is flagged again. If the payment never happened at all, click Mark Unpaid instead, which reverts it in the same way as the button on the bill (see above): the due date rolls back and the bill is outstanding again. Mark Unpaid is only offered where the bill still holds its most recent payment.
Skipping a Payment#
Click Skip to advance the due date to the next occurrence without creating a transaction. This is useful when a payment is waived, already handled outside the app, or you simply want to skip a period. The bill then shows the date it is next due, not the payment before the one you skipped, and Undo on the message that follows puts the date back, along with Mark Unpaid for that earlier payment.
Note: Skipping does not create any transaction — it only moves the due date forward.
Bill Notifications#
Set a reminder to be notified a specified number of days before a bill is due. Reminders use the Nextcloud notification system, so they appear in your Nextcloud notification bell and can also be sent as push notifications if you have the Nextcloud mobile app configured.
To configure a reminder, edit the bill and set the Remind field to the number of days before the due date you want to be notified (e.g., 3 days before).
You get one reminder per due date, and one overdue notice if the bill is still unpaid once the date has passed. Paying a bill late does not hold up the next reminder, so a weekly bill paid a day late still gets its reminder for the following week.
Bills Calendar#
The Bills Calendar provides an annual overview of your bills — what has been paid, and what is still to come. Access it from Reports > Bills Calendar.
Each bill's row combines two things: the dates its schedule says it is due, and the payments actually recorded against it (the transactions created or linked when you marked it paid). A month with a payment is shown as paid and carries the amount you actually paid; a month still to come shows the expected amount. Each due date takes the payment nearest to it, so a payment made a few days late, due on the 30th and paid on the 2nd, counts for the month it was due, and a bill paid twice in one month shows both payments in that month instead of one of them spilling into the next. A payment with no due date near it appears as an extra paid month rather than being dropped. A due date paid more than once shows how many times on a small marker, such as 2×, and hovering a month lists each payment, the day it was made and, when that was another day, the due date it paid.
A bill with one date in the year, such as a yearly or one-time bill, takes the payments made within about two weeks of that date, or failing that the nearest one that could have paid it. For a one-time bill that is still due, that is only a payment made since it was last marked paid, so a final invoice after the bill's monthly payments stays due. Any other payment it has, such as the monthly payments of a bill later switched to One-Time, stays in the month it was made and is never counted as a second payment. A one-time bill that has already been paid stays in the calendar for the year it was paid in, even though paying it deactivated it, and one-time bills that share a name (several invoices from the same vendor) are shown as one row with a cell per invoice. A month is never shown as paid while the bill itself still lists that occurrence as due: paying a bill moves its next due date on a cycle, and the calendar only marks occurrences before that date. The one exception is a payment you have already filed under the bill with Link to bill for the date it is due now, which shows that date as paid. A one-time bill paid again after its date shows the second payment in the month it was made, and its tooltip names the date it paid.
A payment made in December for a date in January, or the other way round, is shown in the year it was made in; the other year shows that date muted, as paid elsewhere, and leaves it out of its totals.
A month the bill has moved past without a recorded payment, one you marked paid choosing Don't create any transaction, or skipped, is greyed out in italics rather than crossed out, and its tooltip says no payment was recorded: it is not owed, but nothing was booked for it either. Such months don't count towards the Monthly Totals, which add up what was paid and what is still due. A bill that was paid this year and has since stopped stays in the Active Only view. Nothing is drawn for months before a bill was created, unless its start date says the schedule began earlier, and a bill with nothing in the year is left out of the table; a payment linked from before then still shows as a paid month. The CSV and PDF exports print what each month shows.
Views#
- Heatmap — A color-coded calendar grid showing bill density by month. Darker cells indicate higher total amounts.
- Table — A detailed table listing each bill and its months, with paid months shown in
strikethrough. Hover a cell for Paid or Due. Includes a monthly totals row at the bottom, built from the paid amounts where there are payments and the expected amounts otherwise.
Filters#
| Filter | Options |
|---|---|
| Status | Active, Inactive, or All bills. |
| Account | Filter to bills linked to a specific account. |
| Include Transfers | Toggle whether inter-account transfers are shown. |
| Include budgeted spending | Toggle whether budgets you chose to show in the calendar appear (on by default). They are not shown when an account is picked or with Inactive Only, as a budget has no account and is never an inactive bill. |
Tip: The Bills Calendar is especially useful at the start of the year for understanding your fixed monthly obligations and planning cash flow.
Budgets in the Calendar#
Spending that isn't a bill, such as groceries, can be planned here too. Click the calendar button on a category's row on the Budget page and that budget gets its own row in the Bills Calendar, marked Budget, with the month's share of the budget in every month. A weekly, quarterly or yearly budget is turned into its share of a month. The rows count in the monthly totals, show as a lighter part of each bar in the chart, and are in the CSV and PDF exports as "category (budget)". Only the budget amount you set counts, never the category's bills, so nothing is counted twice.
Calendar Feed Subscription#
Bills can also appear in your real calendar — Nextcloud Calendar, your phone, Thunderbird — via a token-authenticated ICS subscription. Click Calendar feed in the Bills view to get your subscription URL. See Nextcloud Integration for details and security notes.
A budget shown in the Bills Calendar is in the feed too, as an all-day event on the 1st of each month titled "category budget: amount".
Split Templates#
For bills that should be divided across multiple categories (e.g., a utility bill split between electricity and water), you can define a split template. When the bill is marked as paid, the resulting transaction is automatically split according to the template's category allocations.
To set up a split template, edit the bill and configure the split categories and their amounts or percentages.
End Date and Remaining Payments#
You can optionally limit a bill's lifespan:
- End Date — The bill automatically deactivates after this date, even if it has remaining occurrences.
- Remaining Payments — Set a specific number of payments remaining. The count decreases each time the bill is marked paid, and the bill deactivates when it reaches zero.
These options are useful for installment plans, fixed-term subscriptions, or any payment with a known end point.
Related Features#
- Transactions — Each paid bill creates a transaction in the linked account.
- Forecast — Active bills are factored into balance forecasting.
- Dashboard — The Upcoming Bills tile shows bills due soon.
- Reports — The Bills Calendar provides annual bill overviews.
- Accounts — Bills are linked to accounts for payment tracking.
- Nextcloud Integration — Subscribe to bills as a calendar feed; see upcoming bills on the Nextcloud dashboard.
- The Bills view also proactively suggests recurring payments that aren't tracked yet — create them in one click or dismiss permanently.
Settings#
Bills do not have dedicated settings. Reminder notifications are delivered through the Nextcloud notification system and respect your Nextcloud notification preferences.