Fix a statement that doesn't tie

When Talisk 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: Flip reverses a wrong debit/credit sign, Edit corrects an amount, ✕ deletes a row the scan invented, and + Add a missing row enters one the scan skipped.

Each span turns green (✓ ties to the cent) as you go, and the badge clears once the whole statement balances. Talisk fixes the clear-cut sign flips automatically at import; this screen is for the ones it couldn't resolve on its own.

Rows Talisk found but didn't add

Sometimes the statement has a transaction your books don't. Talisk 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.