> transactions will typically take a couple days to show up in the statement
Wait, in what century do you live that your online banking transaction overview doesn't have up to date data ? Also, your bank allows you to log in with just a username/password ?
A banking "statement" usually refers to a PDF you can download; the electronic version of the thing they'd previously send you by mail.
The online banking CRUD interface might have up-to-date data, but it isn't an API, and being behind some weird proprietary single-sign-on setup makes it pretty hard to scrape, too.
> Also, your bank allows you to log in with just a username/password ?
Yes, this is common in the US (and here in Canada, too.) We sometimes get asked for "security questions", but support for 2FA is extremely rare, and I don't think there's any bank in North America that requires 2FA to login to your online banking. (The "government or bank issues you a smart card that can be used for session encryption; bank issues you an adapter to plug it into your computer" thing doesn't happen here.)
> The online banking CRUD interface might have up-to-date data, but it isn't an API, and being behind some weird proprietary single-sign-on setup makes it pretty hard to scrape, too.
Regarding statement freshness, derefr already answered. Regarding username/password, in Brazil at least yes (sort of) - you log in with account number and a password, but it's sort of a "read-only password" - you can see statements and stuff with it, but if you want to actually move the money, a different password is required.
Trivia: this is used by a Mint-like company in Brazil called GuiaBolso - you give them just the "read-only password".
One of the key features of YNAB is using it to actually inform you before you make purchases. By having it near instant (manual, or by this method), your decisions are fully informed when you make them.
Yes, but a DB of "transaction notifications" your bank sent you could still be useful so you can reconcile/debug if needed, much like the actual bank statement.
I do agree that the DB could be removed from the system, adding the transaction directly from the SES-triggered event, and that would work for most cases.