Firefly III

Setting up a household finance server

Install the Docker Compose stack on a home server or VPS, change DB_PASSWORD and MYSQL_PASSWORD before the first start and set a 32-character APP_KEY. Put a reverse proxy with TLS in front, because Firefly III does not enable TLS itself, and set TRUSTED_PROXIES to avoid broken links and CSP errors. Register the owner account, enable 2FA and leave registration closed unless other household members need their own separate administration. The cron guide explains the STATIC_CRON_TOKEN needed by the cron container.

Importing bank statements

Run the Data Importer next to Firefly III and create a non-confidential OAuth client with the importer's /callback URL. Upload a CSV or CAMT.053 export, assign a role to each CSV column, set the date format and choose a default asset account. Save the import configuration as JSON so later imports reuse it. Check duplicates and transfers between your own accounts after the first run, because imported and manually entered transactions usually do not match each other.

Automating categorization with rules

Create rule groups for recurring merchants, salary and transfers, then add triggers on description or amount and actions that set category, budget and tags. Test each rule against existing transactions before applying it, and use stop processing to avoid later rules overwriting earlier ones. Rule errors are not shown in the interface when rules run asynchronously, so check the logs or a configured notification channel.

Budgeting a month and reviewing reports

Set budget amounts for the calendar month, optionally as auto-budgets, and link withdrawals to them while entering or importing. Use the budget page to compare spent and remaining amounts per day, then open the default financial report for the month or year. Reports and the dashboard can show amounts converted into the primary currency, which depends on the exchange rates stored for each date.

Connecting other tools through the API and webhooks

Create a personal access token for scripts or an OAuth2 client for applications, and send requests with Accept: application/json. Webhooks can push new or updated transactions to a home automation system or a custom service; verify the signature header with the webhook secret before trusting the payload. Follow the API diff files and the developer newsletter, because objects and fields change between minor versions.

Backing up and upgrading

Back up the database, the upload volume and the exact environment, especially APP_KEY, then restore the backup once on a test system to prove it works. The backup guide warns that a missing Docker volume name creates an empty volume and can overwrite a good backup. Read the release notes before each upgrade, pull the new image or replace the archive, and clear caches as the 6.7.9 notes describe.