Settings

Configure user preferences, data management, and admin settings to customize the Budget app for your workflow.

Overview#

The Settings page provides control over localization, number formatting, colours, budget periods, notifications, import behavior, security, and data management.

Access settings via Settings in the sidebar navigation. There is no Save button: each setting is saved as soon as you change it, and a short Saved appears beside it. If a setting cannot be saved, an error is shown and the field goes back to the value that is stored. The row of buttons at the top of the page jumps straight to each section.

Localization#

Configure how the app displays regional information:

  • Default Currency - Choose from 45+ world currencies (e.g., USD, EUR, GBP, JPY). This sets the default currency for new accounts and display formatting throughout the app.
  • Date Format - Select your preferred date display format (e.g., DD/MM/YYYY, MM/DD/YYYY, YYYY-MM-DD).
  • First Day of Week - Set whether your calendar week starts on Sunday, Monday, or Saturday. Affects weekly reports and date pickers.

Tip: The currency setting only affects display formatting and new account defaults. Existing accounts retain their configured currency.

Number Format#

Control how numbers and amounts are displayed:

  • Decimal Places - Choose between 0 and 5 decimal places for currency display. With 0, amounts are shown without decimals everywhere in the app, although amount fields still accept decimals when you type them
  • Decimal Separator - Select . (period) or , (comma)
  • Thousands Separator - Select , (comma), . (period), or a space

A live preview shows how your formatted numbers will appear with the current settings (e.g., 1,234.56 or 1.234,56).

Note: These settings affect display only. Stored values always use full precision internally.

Colours#

Choose the colours the app uses for money in and money out:

  • Default - The usual green for money in and red for money out.
  • Colour-blind friendly (blue and orange) - Blue for money in and orange for money out, chosen to stay easy to tell apart with red-green colour blindness. Under this choice, budgets close to their limit show a yellow bar, so a budget near its limit still looks different from one that is over. Warning text uses a darker gold so it stays readable.
  • Custom - Pick your own colour for money in and for money out, separately for the light and the dark theme. If a colour is hard to read against that theme's background, Hard to read on this background appears next to it. You can still keep the colour.

A preview under the choice shows a positive amount, a negative amount and a small budget bar in the colours you picked.

The colours are used wherever the app shows good and bad in green and red: amounts and balances, spent and remaining figures, budget bars, notifications and status messages, and the charts on the Dashboard and in Reports. The change takes effect straight away, with no reload, and charts already on screen are redrawn. When your device switches between light and dark, the colours for that theme are used.

PDF exports show negative amounts in your light-theme money-out colour, since they are printed on white paper. If that colour is too light to read on white, the PDF uses a darker shade of it.

Note: The colours are a personal setting. Each person picks their own, and people you share accounts or budgets with keep theirs.

Budget Settings#

Configure how your budget periods work:

  • Default Budget Period - Set the default time period for budget tracking (monthly, weekly, etc.)
  • Budget Cycle Start Day - Choose a day of the month (1-31) for when your budget month begins. Useful if your pay cycle doesn't align with calendar months.
  • Budget categories from their bills - On by default. A category with no budget of its own uses the monthly total of its recurring bills and income as its budget, marked auto on the Budget page. Turn it off to budget only the amounts you set yourself. Bills keep working the same either way. See Automatic Budgets from Recurring Items.
  • Months in dashboard charts and reports - Calendar months (the default) or Budget periods. Only makes a difference once the Budget Cycle Start Day is something other than 1. See below.

Tip: If you get paid on the 15th, setting the budget start day to 15 means your budget period runs from the 15th of one month to the 14th of the next.

Months in Dashboard Charts and Reports#

The Budget page always works in budget periods. This setting decides whether the dashboard charts and the month-by-month reports do the same. With Budget periods and a start day of 26, a salary paid on 26 September counts towards October, as it does on the Budget page. With Calendar months it counts towards September.

Budget periods are used in:

  • the dashboard's Income vs Expenses and Spending by Category charts
  • the trend in the Summary Dashboard report
  • the Cash Flow report's months
  • the Category by Month report

The report presets (This Month, Last 3 Months, Year to Date, Last Year) then cover whole budget periods, and a line under each of these charts says which day the periods start on. Exports and scheduled reports of these reports follow the same choice. The Year over Year report and the Budget Digest stay on calendar months. See Reports and Dashboard.

Notification Settings#

Toggle notifications for budget events:

  • Budget Alert Notifications - Send a Nextcloud notification the first time a category reaches your alert threshold in a budget period, and a second one if it later goes over budget. That is the most you will get per category per period; a category that drops back under the threshold is forgotten, so it can alert again if it climbs back (on by default)
  • Budget Alert Threshold - The percentage of a category's budget at which it starts showing on the Budget Alerts tile (default 80%). Set it to 100% to be alerted only when a category actually goes over budget, rather than when it's merely approaching the limit
  • Forecast Warning Notifications - Send a notification when the six-month forecast projects your combined balance below zero, naming the month it happens and the figure it falls to. At most one a month, since the projection is a trend estimate that shifts as new transactions land, and only once the forecast has at least three complete months and ten transactions to go on (on by default). See Forecast
  • Unusual Spending Alerts - Notify when a category runs well above its 6-month typical spending. Median-based with a minimum-amount floor and at most one alert per category per month (on by default)
  • Budget Digest - Opt-in weekly or monthly summary (income vs spending, budget status, upcoming bills, goals, unusual spending, new bill suggestions) as a Nextcloud notification, optionally also by email. Its income and spending match the Cash Flow report for the same dates and your own accounts: transfers between your accounts are left out, and other currencies are converted to your base currency. Unusual spending here covers the period the digest reports on - the finished week or month - compared with your six-month typical spending scaled to that period's length, so it is not the same figure as the live alert above. Digests are sent one user at a time, spread across the background job (cron) runs, so on a server with many users they do not all go out at the same moment

Receipts#

  • Receipts folder - Where uploaded receipts are filed in your Files, as a path relative to your Files root. The default is Budget/Receipts; click Browse… to pick any folder from your Files (or type a path such as Applications/Budget) to keep Budget's files alongside other apps'. Year and month subfolders (<year>/<month>/) are created underneath whichever folder you choose. Changing the folder only affects receipts uploaded from then on — ones already attached stay where they are, because the app never moves or deletes your files. The web form, the API and receipt scanning all use the same setting.

Scheduled Reports#

Have the previous month's summary report delivered automatically at the start of each month:

  • Monthly Report to Files - Saves a PDF into Budget/Reports/<year>/ in your Files; a notification links to it
  • Monthly Report by Email - Emails the PDF as an attachment (requires the Nextcloud instance to have a working mail server)

Both can be enabled independently; with both off the feature is inactive.

Import Settings#

Configure behavior for transaction imports:

  • Auto-Apply Import Rules - Whether import rules categorize transactions during file imports (CSV, OFX and QIF). This sets how the Apply import rules for categorization box on the import screen starts for each new file, and unticking that box leaves the rules out of that one import, preview included
  • Default Export Format - Set the default file format for data exports
  • Bill match window (days) - How many days either side of a bill's payment an imported transaction can be and still be matched to a bill that has no auto-detect pattern, by its name. 5 unless changed, from 1 to 30; the amount always has to match to the penny. See Bills with no pattern

Note: Rows already imported are always skipped as duplicates. Tick Import flagged duplicates too on the import screen to bring them in anyway.

Import Folder#

Choose a folder in your Files and add a subfolder for each account, and the statements dropped into them are imported in the background, or held for you to review first. Check now looks in them straight away rather than at the next 15-minute check. Files already in a subfolder when you set it up are left where they are. See Import folder for how it works and what happens to each file.

Quick Add Page and System Info#

These two panels now live on the Help & Docs page rather than in Settings — see Help & Docs.

Data Migration#

Tools for moving your data between instances:

  • Export - Downloads all your budget data as a single ZIP archive. It contains everything the app stores for you: accounts, categories, transactions (including splits, tags and the links joining transfer pairs), bills and recurring transfers, tags and tag sets, recurring income, savings goals, assets and their value history, pensions with contributions and snapshots, interest-rate history, manually set exchange rates, import rules and templates, saved reports, net-worth and budget history, reconciliation history, debt payoff scenarios, shared-expense contacts with shares and settlements, and your settings. The archive is built a little at a time and downloads as it is written, so a large ledger exports in the same way as a small one.
  • Import - Upload a previously exported archive to restore your data. Importing replaces all existing Budget data for your user, and every cross-reference is rewired to the new instance's ids, so tagged, split and linked transactions come back exactly as they were. Every account setting comes back too, including a wallet address, the interest settings and the date the account was last reconciled. Restoring also works on PostgreSQL, where earlier versions failed with an "invalid input syntax for type boolean" error. Bank sync connections are kept and follow your accounts through the restore; one whose account isn't in the backup is unlinked, and the restore says how many it had to unlink, so you can choose their accounts again on the Bank Sync page. Import rules come back with their groups, saved reports keep their account and tag filters, and the dashboard's tile filters, hidden categories and account order, along with your muted budget alerts, point at the restored accounts and categories. Archives from older app versions import fine; they simply contain less. An archive made by a newer version of Budget than the one on the server shows a warning first, as some of its data may not come back.

A backup made by Budget 2.54 or older is repaired as it is restored, in the same way the update to 3.0 repairs existing data: bill payments it had booked ahead but not yet paid go back to pending, so the money is not taken off the balance twice.

A shared-expense contact linked to a Nextcloud user keeps that link only if you could link that person yourself under the server's sharing settings. Where the restore has to remove a link the contact itself is kept, and the message at the end of the restore says how many links were removed.

A few things deliberately stay out of the archive (the manifest inside it says so too): bank-sync connections (the agreement with your bank is tied to the old instance and must be set up again), shares with other users (they reference accounts on the old server), receipt files (they live in Nextcloud Files — copy them across with your files), the private link to your bills calendar feed, and the automatically fetched exchange-rate cache. Because bank connections, shares and the feed link are not in a backup, restoring one does not touch the ones you already have: your own restore keeps your feed link, and a new account gets a link of its own.

A backup that unpacks to more than 200 MB for any one file inside it, or more than 500 MB in total, is refused with a message saying which limit it went over. A real backup is far smaller than this; the limit is there so that a damaged or malicious file cannot run the server out of memory. A backup that has been damaged or edited by hand, so that one of the files inside it is not in the format Budget expects, is refused with a message naming that file, and nothing is changed.

Repair Data#

Scans your data for inconsistencies and shows you exactly what it found before changing anything. Nothing is altered until you press Fix Selected Issues, and every category can be unticked.

Click Scan for Issues to run it. Each category that found something is listed with a count; click a heading to see the individual items.

CategoryWhat it looks for
Duplicate Auto-Generated TransactionsPayments the app recorded twice for the same bill or recurring transfer. This includes the ones older versions left: a pre-booked payment that went through on its date and was then marked paid again, two payments of a bill you have since deleted, and pairs whose amounts differ because the bill's amount changed in between. For a recurring transfer both sides are removed together, and only where you can change both accounts. For a one-time bill paid twice the newer payment is offered, and the bill stays paid on the older one. Only the rows the app is sure of come ticked, so check the others in the account first. One of each pair is always kept, and a deleted row takes its splits, tags and attachments with it. A row you have checked and want to keep can be ignored (see below).
Bills With Stuck Due DatesActive bills whose next due date has fallen into the past and stopped advancing.
Paid One-Time Bills Still ActiveOne-off bills paid by their date, with the paid date or a recorded payment within a few days of it, but never deactivated, so they keep appearing as due.
Income Received Early but Still ExpectedRecurring income an older version marked received a day or two early but left waiting for that same payment, so it shows as overdue and Mark Received would record it again. Repairing moves each one on to its next date and adds or deletes nothing. Updating to this version does this by itself, so this category finds the ones a backup restored later brings back.
Future Transactions Not Marked as ScheduledTransactions dated in the future that were marked cleared, so their amounts were counted in today's balance.
Debts Recorded as Being in CreditCredit cards, loans, mortgages and lines of credit holding a positive balance, which the app reads as money owed to you rather than money you owe. See below.
Split Transactions Carrying a CategorySplit transactions that also hold a category of their own, left behind by an older version of bulk edit or by a rule run. A split keeps its categories on its parts, so it should not carry one. Only the stray category is removed — the split and every part of it are left as they are.
Account Balance InconsistenciesAccounts whose stored balance no longer matches the sum of their transactions. Always recalculated last, after the other fixes.

Ignoring a duplicate#

Not every row under Duplicate Auto-Generated Transactions should be deleted. An old double may already be allowed for in your balance, for example by a correction you entered to make the account match the bank, and deleting it then would put the balance out by the same amount. Press Ignore on a row like that and it is no longer listed, counted or ticked, and it is never deleted. It stays ignored on later scans.

Ignored rows are folded away at the bottom of the category under ignored rows. Open it and press Stop ignoring to bring a row back to the list, unticked. Ignored rows go with your data in an export and restore, so they stay ignored on a new server.

Debts Recorded as Being in Credit#

This one asks you a question rather than simply fixing things, because only you know the answer.

A debt account holding a positive balance is usually a mistake — a statement balance typed in without a minus sign, which makes the app count the debt as money you have and inflates your net worth by twice the amount. But it can also be perfectly correct: if you have overpaid a credit card, the issuer really does owe you.

The scan lists each affected account with what it reads now and what it will read afterwards, largest first. Every account is ticked by default, since the mistake is the common case.

Untick any account you really have overpaid. Those are recorded as genuine credits, kept exactly as they are, and left out of every future scan — so the category empties out rather than asking you again.

Note: repairing an interest-bearing loan that was recorded in credit will also restore its interest accrual. Interest is only accrued on a balance the app sees as a debt, so an affected loan will not have accrued any, and its accrued figure will change once the balance is corrected.

Reset All to Defaults#

In the Danger Zone at the bottom of the page, Reset All to Defaults puts every setting on the page back to its default after asking you to confirm. Your accounts, transactions and other data are not touched.

Factory Reset#

Permanently delete ALL your budget data:

  • Removes everything of yours in Budget: accounts, transactions (with their splits and tags), categories, tag sets and tags, bills and recurring transfers, recurring income, savings goals, projects, assets, pensions with their contributions (recurring ones included) and snapshots, interest rates, manually set exchange rates, import rules and import templates, saved reports, net-worth and budget history, reconciliation history, debt payoff scenarios, shared-expense contacts and settlements, and your settings
  • Also removes what a backup never holds: the shares you have granted to other people, your bank connections and their links to your accounts, your Enable Banking keys, and the request keys stored for API clients
  • Ends each GoCardless and Enable Banking connection at the provider too, once your data has gone, so the bank stops sharing your account data. A provider that can't be reached is noted in the Nextcloud log and doesn't stop the reset. Clear sample data does the same
  • Keeps shares other people have granted to you, as those belong to them
  • Leaves your receipt files in your Nextcloud Files; only their links to transactions are removed
  • Audit logs are preserved for security purposes
  • Requires explicit confirmation before proceeding
  • Cannot be undone

Warning: Factory reset is irreversible. Consider exporting your data first if you might need it later.

Admin Settings#

These settings are only visible to Nextcloud administrators:

  • Enable Bank Sync - Toggle the Bank Sync feature on or off for all users on the instance. An experimental feature warning is displayed when this section is visible.
  • Receipt scanning - Choose which OCR provider reads photographed receipts, or leave it off. Off by default, and while it is off no receipt image is sent anywhere. The choice is server-wide, and the API key is stored encrypted and never shown again after saving. See Receipt Scanning.

Note: Admin settings affect all users on the Nextcloud instance, not just the administrator's own account.

Users Deleted from Nextcloud#

When a Nextcloud user is deleted, Budget removes their data along with them: their accounts, transactions, bills and everything else they kept in Budget, the shares they granted and the ones granted to them, and the links other people's shared-expense contacts had to them. The removal is all or nothing, so if it fails part way, none of their data is removed and it can be run again. Their GoCardless and Enable Banking connections are also ended at the provider once their data has gone. The access other people gave them is still taken away straight away in that case. Background jobs such as auto-pay and the digest also skip any user who no longer exists.

Users deleted before Budget 3.0 left their data behind. To find it, run this from the Nextcloud directory as the web server user:

occ budget:purge-deleted-users

On its own the command changes nothing. It lists each deleted user who still has Budget data, with the number of rows left in each table. Check the list, then run the command again with --force to remove that data. --user limits it to the users you name, and can be given more than once:

occ budget:purge-deleted-users --user bob --user carol --force

A user who exists is always left alone, and each user is checked again just before their data is removed. A user from an external user backend such as LDAP can look deleted while that backend is unreachable or switched off, so compare the list with your user directory before using --force. A user the backend could not give an answer for is reported and left alone.

If an Update Did Not Finish#

Nextcloud applies an app's database changes as part of upgrading the app and records each one as done. Occasionally that goes wrong — the files are updated but the database is not, a change is recorded as applied yet its column is not there, or a file never reached the server. Nothing complains at first, because reading a missing column just gives an empty value; the first sign is a save failing with the database's own words, such as Unknown column 'amount_type'.

The usual cause is two app updates running at the same time. Nextcloud applies each database change by comparing the whole database with a snapshot taken when the step started, and removes anything the snapshot did not have, so when two apps update at once each can take out a column the other has just added — and the Apps page's Update all starts every app's update at the same time. The update that added the column is recorded as done, yet the column is gone.

Budget checks for this itself. On every page load it compares the live database with every column the app writes, and if anything is missing it shows a banner at the top of the app, reports an error in Settings → Administration → Overview, and adds the same detail to the error a failed save shows. The message lists what is missing by table and column.

Budget also repairs it itself. After its own database changes on every update, and whenever the app is enabled, it checks its tables and re-runs the change behind anything missing. So the fix is any one of:

  • Update the app, when a newer version is available.
  • Disable and enable the app from the Apps page. Nothing else on the instance is affected and no command line is needed.
  • From the Nextcloud directory as the web server user: occ app:disable budget && occ app:enable budget, or occ maintenance:repair.

Each change checks before acting, so re-running one that did apply changes nothing, and only the table structure is restored — a data step from an earlier update is never run twice. If the message says no update on the server adds the column, the app's files are incomplete: reinstall the app, then enable it. If the schema cannot be read at all, the check stays quiet rather than guess.

Note: Repair Data above fixes data — duplicates, stuck bills, balances. It cannot add a missing column, so it is not the tool for this.

  • Bank Sync - Automatic transaction imports from external banks
  • Receipt Scanning - Turning photographed receipts into transactions
  • Import - Manual transaction import from files
  • Exchange Rates - Multi-currency support configuration