Fix a statement that doesn't tie

When HQ imports a statement it checks the transactions against the statement's own running balances. If they don't add up, the statement row gets a doesn't tie badge (hover it to see exactly which stretch is off).

1. On Ledger › Banking › Statements, click the doesn't tie badge.
2. The fix screen shows only the spans that don't balance, each with a live rows net X · bank moved Y · gap ±Z readout.
3. Fix each row: Swap in/out turns money in into money out (or the other way round) when the scan read the direction wrong, Edit corrects an amount, ✕ deletes a row the scan invented, and + Add a missing row enters one the scan skipped. Deleting asks you to confirm first, and names the row it is about to remove.

You can also start from Ledger › Health. The A statement doesn't add up card lists each statement by account and period (for example RBC Chequing, 1–31 Mar 2026) with the rows where its running balance breaks, and Fix this statement beside it opens the same fix screen.

Each span turns green (✓ ties to the cent) as you go, and the badge clears once the whole statement balances. HQ fixes the clear-cut sign flips automatically at import; this screen is for the ones it couldn't resolve on its own. On a credit card or line of credit it also turns a statement the right way round when every row was read with the opposite sign, and the statement's notes say how many rows it re-signed.

A bank statement read the opposite way round

On a bank account, a statement whose money in and money out read the opposite way round from its balances is held instead of fixed. Three things fit it exactly, and the running balance alone can't say which:

• the scan swapped the deposits and withdrawals;
• the account was overdrawn and the bank printed its balances without a minus sign;
• it isn't a bank account at all, but a credit card or line of credit filed under one.

So HQ changes nothing: it swaps no rows, and it matches and codes none of the lines on that import. When the statement comes in through an Add paperwork drop that records statements by itself, it waits for you instead of being recorded. Committing that account yourself on the review screen still records it, so check the lines first. The statement's notes say what happened.

Check the lines against the statement itself:

• If the deposits really are showing as money out, use Swap in/out on each row in the fix screen.
• If it is a card or a line of credit, Move the statement onto that account (named as it is under Banking › Accounts), then open the statement and press Re-extract.
• If the account was overdrawn that month, the lines are right as they are, but HQ can't confirm that by itself. The statement stays held and keeps showing as not adding up, and nothing marks it as checked. One-click reconciliation won't start from it; a newer statement that adds up can.

Rows HQ found but didn't add

Sometimes the statement has a transaction your books don't. HQ only adds it for you when it's sure: if a payment of the same amount is already recorded within a few days, adding another would double-count the money, so it asks you instead. Those show at the top of the fix screen as rows on the statement that aren't in your books, each listed next to the transaction that looked like a match.

Compare the two and pick one:

• Add this row: they're different payments (two invoices to the same supplier, say). The row is added to the statement and the gap closes.
• Already in my books: it's the same payment, recorded on a slightly different date. Nothing is added, and the statement stops counting it as missing.

If the match shown is labelled this statement, it's almost certainly the same transaction with the date read differently, choose Already in my books.