Transfers, duplicate accounts, and a dozen fixes [Originally posted 8/9/2026]

[bpowers]

Hello,

Two busy days on Earmarkr. The headline: recording a transfer is no longer a scavenger hunt, and a bank connection can no longer quietly duplicate an account you already track.

Here is everything that changed.

Transfers

Adding a transaction now starts with a choice: Payment, Deposit, or Transfer. Previously you could only say "money out" or "money in" — there was no way to tell Earmarkr "this moved money between two of my own accounts" without finding a separate button on the Transactions toolbar. Now it is right there in the Add transaction dialog.

Pick Transfer and the Payee box becomes From account and To account, and the dialog explains in plain language what that particular pair does to your budget — paying a credit card draws down its payment reserve, moving cash between two on-budget accounts is budget-neutral, and a loan or mortgage payment draws down that account's own payment category (filled in for you).

You can start a transfer from wherever you already are — an account's register, its settings page, the Accounts list (a button at the top, or each account's ⋯ menu), or the command palette. The account you are looking at is filled in as the "From" side, so you are not picking both accounts from scratch. The "To" account is never guessed; you always choose where the money is going.

Two bugs went away with the old form:

• Mortgage payments were not getting their payment category filled in, and the form then insisted on a category it never offered — so a mortgage payment was effectively impossible to record there.
• A typo in the amount made the save fail outright. Now the button simply stays disabled and tells you what to fix.

A transfer's details now name the account on the other side, with a link straight to it — "To Kohl's Charge" on the money-out side, "From Checking" on the money-in side. Working out which account a transfer paired with no longer means hunting for a matching amount in another register.

Bank connections and duplicate accounts

Connecting a bank now asks what each account should be before importing anything. It used to start importing immediately and create a brand-new account for everything it found — so if you already tracked your checking account or a card by hand, you ended up with two of it. Now you get a short setup step listing each account the bank found, with a suggested match already selected where we are confident and the reason shown so you can judge it. Matching the last four digits is a strong match; matching only the name is a guess.

If you close the page partway through, the connection waits with a "Finish setup" button on the Connections page. It imports nothing until you finish, and you can disconnect it with nothing left behind.

If you already ended up with the same account twice, you can now merge them. Account settings has "Merge into another account" in the Danger zone. Pick the account to keep and you will see exactly what will happen first: how many transactions, balance snapshots and reserve movements move, the resulting balance, and any special cases. Nothing is deleted and the balance is the sum of the two — but it cannot be undone, so read the summary before confirming.

Your transaction register

Transactions now show where they came from. A small icon before the payee marks anything that arrived from outside — a bank building for a bank connection, a page for a statement file or the YNAB import. Anything you typed yourself stays unmarked, so the register stays quiet. Open a transaction and its details spell it out in a sentence; if a sync matched a transaction you had already entered, it now says so, so a merged row no longer looks like one that went missing. There is also a new "Any source" filter for when you want to see only what you typed.

You can delete several transactions at once. Tick the rows and use Delete in the selection bar. Before it runs, it tells you how many rows, the net total, whether any are transfers (the other leg goes too) or splits, and whether any came from a bank connection and might return on the next sync. Protected rows — reconciled transactions, an account's starting balance, individual split parts — are skipped and counted rather than blocking the batch. Deleting is permanent, so from 100 rows up you have to type DELETE to confirm.

Fixes and polish

• Paying a credit card from checking no longer reports "Failed to save." The payment had actually gone through, but the error stopped your budget from updating, so the card's payment category still showed the full amount set aside. Payments you entered before this fix have been recalculated — no need to re-enter them.
• Every account dropdown is grouped by type and sorted A–Z instead of listing accounts in the order you added them. Headings for Checking, Savings, Credit card, Cash, Loan, Mortgage, Investment and Other, alphabetical inside each. Your Accounts list and sidebar may look reordered the first time you open them.
• The ⋮ actions menu no longer runs off the bottom of the screen. On a category near the bottom of the Budget screen, Delete and the "Move to group" list were out of reach. The menu now opens upward when there is not enough room below, and scrolls if it is taller than the window.
• Closed accounts no longer appear in account dropdowns when adding a transaction or recording a transfer — including as the destination of a transfer. They are unchanged and still visible on the Accounts screen with "Show closed" on.
• The "Card Ledger" button in a transaction's details now only appears on credit-card transactions. On a checking or savings row it used to open the all-cards overview and lose your place in the register.

As always

Every one of these is written up in What's new inside the app, with step-by-step instructions for anything that moved. If something here does not behave the way it reads, please tell us — the reports we get are what these two days were made of.

Thanks for testing,
Bradley