No export button
Plenty of banks give you a clean CSV, and if yours does, close this tab and use it. We wrote this for the accounts that don’t, like the store card whose website shows a scrolling list and nothing else, or the HSA portal that only offers monthly PDF statements. Getting those into a budget sheet means retyping dates, merchants and amounts on a Sunday evening while the page reloads every time you scroll back too far.
Tiller and services like it pull bank feeds into a spreadsheet through an aggregator, and for the institutions they support that’s sturdier than anything reading a screen. dassi covers the gaps. It works in the browser you already use, so it reads the transactions page as you see it and types rows into the Google Sheet in the next tab.
A run, start to finish
You sign in to the bank yourself. The password stays in your password manager and the two-factor code is yours to type. With the transactions page and the budget sheet both open, you tell dassi something like: “Copy posted transactions since the last date in my sheet into the next empty rows, with date, merchant, amount and a category from my Categories tab, and stay read-only on the bank site.” It pages back as far as it needs, checks the sheet for rows that are already there so a rerun doesn’t double anything, writes the new rows, and marks every category it wasn’t sure of. “AMZN Mktp” alone could land in three of ours.
Then compare the total against the bank’s own figure for the period. Thirty seconds, and it catches most mistakes.
Leave pending transactions out. A restaurant charge changes when the tip posts, and some holds simply vanish.
Read-only, and who sees the numbers
Read-only here means paging and date filters. We’d put that sentence in the saved workflow and also flag every other click on the bank site for approval, so a surprise pop-up about a new savings account makes dassi stop and ask you instead of improvising.
The model sees what’s on the page: merchants and amounts, probably balances, maybe the last four digits of an account number, all sent to the AI provider you picked, or through dassi’s relay if you use included credits. So pick the model you trust with a bank statement. We’d start with our own key at a provider whose data terms we had actually read, or a local model if the computer can run one, and we’re still not sure there’s a right answer for everyone.
We’d keep this one manual
You can put it on a schedule. We wouldn’t. Bank sessions time out fast and most want a fresh two-factor code, so a scheduled run tends to stall at the sign-in page, and some banks’ online terms discourage automated access anyway. Once a week, started by you and moving at roughly the speed you’d scroll, feels right.
After that, Google Sheets formula suggestions can do the monthly totals. Nothing will make the coffee column look better.