New transaction form: default account and required fields

The new transaction form tries to open on the correct account immediately.

Usually, this is the account you used for the last similar transaction. This memory is separated by type: expenses, income, transfers, and debts remember their own accounts. Otherwise, entering one salary payment would mess up the default selection for all subsequent expenses.

If there's no such memory yet (first entry, new device), the default active account in your base currency is substituted — not a savings or credit account.

Accounts are listed: first in the base currency, then others, sorted alphabetically within each group. Other accounts don't disappear: if you've moved and sometimes pay from an old account, it's still there — just lower down. For transfers in the second field ("To"), accounts of the same currency as the source account are shown at the top.

Under the account field, "Quick select" chips may appear — accounts you've used in the last month for this type of transaction, with the most frequent ones first. One tap instead of opening the list.

Once you select an account manually, the app stops changing it — even if you later switch the transaction type. Nothing will "shift" under your hands while you fill out the form.

Archived accounts are not offered in the list. An exception is a transaction that is already on such an account: when editing it, the account remains visible, otherwise the field would become empty.

If "Save" does nothing

You clicked "Save," but nothing happened — it means the form is waiting for something. The field preventing saving is highlighted with a red border, the page scrolls to it and places the cursor in it, and a line with an explanation appears at the bottom of the window. As soon as you fill in that field, the highlight and message disappear on their own — you don't need to click "Save" again just to check.

Before the first click on "Save," nothing is highlighted: an unfilled form you are still working on is not an error.