I think "Smart import" answers your first question. But entities is a great question.

My own unanswered question:

Can this work offline?

I spend a lot of time in areas with no signal. So I am uncomfortable with apps that require a connection to a remote server to work with my own data. Besides connectivity issues, there is also the possibility of a poorly-timed service outage, or an eventual permanent shutdown. Bottom line, I have a strong preference for what I call the "KeePass" model: local-first encrypted data, that can be optionally synced for convenience.

Yes, it actually can! We do not have native apps, but you can install a PWA on any platform, including mobile and desktop. It will work in offline thanks to Service Workers.

The app itself is 100% rendered on the client side, so we are in that sense local-first. We use backend solely for data sync and authorization.

I can't decide if that answers my question or not. Maybe you can clarify.

If I start up the PWA with no connectivity (assuming I've previously run it where it can sync data) it will have the data already? The full data set, or just whatever subset was previously rendered? And will it be usable without a connection for authorization, or will it be locked?

It will have the full dataset and all features. Whatever you expect from a real offline mode :)

1. you can import bank statements. We aim to support all the banks our users have. 2. since we encrypt every bit of data on the client side, we cannot differentiate transactions from categories. So entity is anything you create within the product. Most often, it's a transaction.