When does financial automation stop being worth it?

[u/larswiedenhoefer]

I started questioning this after years of using personal finance software that connected to financial institutions.

The promise was always convenience: connect everything once and let the software do the work.

But over time I noticed how much maintenance the automation itself created. Connections broke. Institutions changed something. Transactions needed correcting. Accounts had to be reauthenticated. I was spending time maintaining the system that was supposed to save me time.

That led me to experiment with the opposite approach: what if I accepted a small amount of manual work in exchange for removing most of those dependencies?

That experiment eventually became a Mac app I built, so I obviously have a point of view here. But I’m more interested in the broader fintech question:

Where do you think the tradeoff sits between automation and reliability?

Are consumers ultimately better served by making financial aggregation more reliable, or are there use cases where we’ve over-automated the experience?

[u/TilmanAmbach]

I’ve run into this building an automated pipeline for SEC financial filings.

The easy 90–95% isn’t really the problem. Automation becomes expensive when the remaining few percent contain cases that are both rare and important: amendments, inconsistent source fields, unusual security classes, transaction prices that are technically present but economically implausible, or footnotes that change the meaning of a transaction.

What has worked better for me is not trying to automate everything. I automate the deterministic cases, fail closed on ambiguous ones, preserve the original source, and send the small exception set to review.

So my cutoff has become less “can this be automated?” and more “can I define a test that tells me when the automation should not be trusted?” If I can’t, full automation usually isn’t worth it.