Let’s get you unstuck.

Open your Nextcloud address in a browser to check that it is reachable. In the app, use an HTTPS address, your Nextcloud username, and a valid app password. Check that the Budget app is enabled on the server and provides the required API. Contact your Nextcloud administrator for server or certificate issues.

Check the selected user profile and account, then refresh the view. Clear search, date, category, type, status, and receipt filters. Load older transactions as needed; the app loads the list in pages.

Check your Nextcloud first to see whether the transaction already exists. Do not create a second transaction while the result is unclear. For new transactions, use the existing saved request to review and retry the same data. Restored requests are not sent automatically.

Available features depend on your Budget version, API, and permissions. Transfers require other open accounts in the same currency. Global tags are available for your own accounts; shared accounts have restrictions. Some fields of split transactions and transfers must be edited in Nextcloud.

Saved profiles and credentials are stored in Apple Keychain. The app connects directly to the Nextcloud address you provide. See the privacy policy for more information.

You can find Budgetwerft on the App Store. For questions or feedback, use the email contact on this page.

Local text recognition supports iPhone, iPad, and Mac; searchable PDF creation also takes place on the device. No additional cloud OCR service is required. The receipt is uploaded to your own Nextcloud when you save. Review recognized details before using them in a transaction.

These additions are part of the development status as of October 28, 2026. Availability depends on your installed app version and the version released on the App Store. Camera capture is available on iPhone and iPad. Local text recognition also supports Mac.

These overviews are part of the development status as of October 28, 2026. They require a compatible app version and Budget API. Check the published App Store version and the Budget version on your server. The app explains when the required server feature for upcoming payments is unavailable.

The app displays failed receipt and category requests separately. Use the option to retry loading, and check your connection and selected user profile. Switching profiles or signing out clears the temporary receipt cache.

If the transaction list does not include receipt status, the app checks available receipts through an additional request and temporarily caches the result. A failed request shows a warning; it does not confirm that no receipt exists. Check your connection and refresh the view.

Check the active profile settings, where you can allow or disable these three actions separately. Your Nextcloud permissions and available API features also apply. Local profile settings do not replace server-side access controls.

API-Debug is directly below “Sign out” in the accounts menu. It helps with read-only API requests. Remove personal financial information and credentials before sharing the output.