Troubleshoot imports and bank connections

Work through the most common reasons a CSV, provider migration, or bank-feed import does not behave as expected.

CSV looks misaligned

Re-check the date, description, and amount mapping first. Split debit and credit layouts are a common source of confusion.

PocketSmith or YNAB export does not preview

Check that the source selector matches the file. YNAB ZIP exports need a register file inside the ZIP. PocketSmith ZIP exports need a transaction file inside the ZIP. If you only have a transaction CSV or TSV, choose the matching source and upload that file directly.

Bank connection flow fails

Connection problems often come from the upstream bank flow or a redirect configuration issue. The callback route can only finish the flow that the bank connection has already started correctly.

Imported data lands in the wrong category

That usually points to rules or category structure, not to the import transport itself.

For PocketSmith and YNAB export-file imports, check the imported source category shown in review. Dolla creates missing source categories at confirm time, but a category you manually select in review overrides the imported source category for that transaction.

If the row was matched by a Smart Rule, click the Matched pill during import review to inspect or edit the rule before saving the import.

I saved the wrong import

If it was the latest CSV, PocketSmith, or YNAB import and the saved-import banner is still visible, use Undo import from that banner. Undo removes that import and its saved transactions. Older imports and non-CSV-tab sources need manual cleanup from the Transactions page.