Bank & brokerage connectorsBeta
Several bank and brokerage connectors work today — link an account and real transactions or holdings flow in through the same write path a manual entry uses. But this area is excluded from what the project vouches for: the ledger, budgeting, and investments core is held to one bar — real numbers, verified by the owner, over time — and syncing hasn’t cleared it yet.
Known, open correctness gaps
- A row flagged for your review can still count toward balances and net worth before you’ve reviewed it.
- A bank correcting an already-sent transaction (a pending charge settling differently) can be silently missed instead of applied.
- Deleting an imported transaction doesn’t always stop it reappearing on the next sync.
- Enable Banking is the newest and least battle-tested of the six aggregation providers here — several response fields are still being confirmed against real bank responses.
Treat a synced number like any unverified figure — worth having, not worth betting on without checking your real statement.
What’s available
| Type | Providers |
|---|---|
| Bank/card aggregation | SimpleFIN, Plaid, Lunch Money, Lunch Flow, YNAB, Enable Banking (EU-only) |
| Brokerage | Alpaca, Interactive Brokers (Flex Web Service) |
Each needs its own credentials (token, API key pair, or OAuth link) under Connectors.
Every connector here is read-only
No exceptions: a sync only pulls transactions or holdings in. No order-placement or money-transfer path is wired into any of them, and Lucius has no tool that could use one even if asked — see what Lucius can do. Interactive Brokers’ Flex Web Service token is read-only at the protocol level — it cannot place a trade even in principle. Alpaca’s key pair is an ordinary Alpaca credential that could trade through Alpaca’s own API if used elsewhere; this app simply never calls that endpoint — its Alpaca trading code was removed outright, not merely unused.
What to do instead, for now
Enter transactions manually or import a statement file (CSV, OFX, QIF, CAMT, MT940, XLSX, or a PDF/photo) — that path is part of the hardened core, where verification effort has actually gone.
Related pages
lucius/overview— what Lucius can do with your bookgetting-started/what-is-open-net-worth— hardened vs. still being built