Importing bank statements

Climb never connects to your bank, but it happily reads what your bank gives you: export a statement file (CSV) from online banking and Climb matches it against your Logbook. It's the fast path through reconciling and the safety net that catches anything you forgot to log.

How an import works

Export a CSV from your bank's website or app for the account and date range you're checking. Every bank offers this, usually right next to the statement.
Upload it during reconcile. Climb lines up each statement row against your existing transactions and shows its best matches for review.
Approve the matches, fill the gaps. Matched transactions get cleared in bulk. Rows with no match are the ones you never logged; Climb creates them for you, you give each a category, done.

The result is an account where everything on the bank's record is in Climb, cleared, and ready to lock in as reconciled.

Climb learns your bank's names

Bank descriptions are ugly: AMZN MKTP US*2W4 is not how you think of Amazon. The first time you tell the importer what a description means, it remembers. Next month the same description resolves instantly, and imports get quicker every time as Climb learns your bank's vocabulary.

Import versus logging

Importing is a checkpoint, not a substitute for logging as you go. A budget you only import into tells you what happened weeks later; a budget you log into tells you what's safe to spend right now. Log in the moment, and let the import confirm you.