Live
The list wins. Checking, brokerage and credit-card balances are overwritten on every sync you confirm, because the source is the better record.
Setup · Getting your balances in
FinPlanTools holds no bank login and runs no feed. Every figure in your plan is one you or your assistant put there: one at a time when you ask for it, or a whole list at once. A list is shown to you as a diff and applied only when you confirm it.
Two ways in
Which one you want depends on how many accounts you keep, not on how your plan is set up. They write to the same place and you can move between them whenever you like.
"Set my savings account to $42,100." The assistant updates the account and hands you back your plan to save. There is nothing to connect and nothing to authorize, and for a plan with a handful of accounts this is the whole story. Correcting one number is the same sentence. There is no preview step on this route, because you named the change: the account is updated and the result handed straight back to you.
If you can get a machine-readable list of your accounts out of wherever they already live — an export you download, or another tool your assistant can call — your assistant can reconcile that whole list against your plan in one step. A row carries an id, a type, a balance and optionally a name — the shape Monarch's assistant connector returns. Anything your assistant can map into that shape works, because FinPlanTools reads the list offline and never reaches out to the source itself.
Both routes write to the same place: your plan, a JSON document you hold. Nothing is written to it without you saying so — see where your data lives.
What a reconcile does
A reconcile is a dry run by default: it compares the list against your plan, sorts every account into one of four buckets, and writes nothing. You read the diff and confirm it, or you don't.
| What it means | What happens to it | |
|---|---|---|
| Matched | A row whose FinPlan account is already known, because you linked the two once and the link was saved. | The balance difference is shown, and written only when you confirm. |
| Only in your list | An account your plan does not model yet. | Reported, never created for you. Adding it stays a decision you make, in the same conversation. |
| Only in your plan | An account the list did not carry — one you keep by hand, or one the source cannot see. | Reported, never touched. |
| Held back | Something the import cannot build on its own: a mortgage with no loan terms, a property with no details. | Surfaced, never dropped. For a mortgage or property, you supply the missing terms and it is written through the same checks as an account you create by hand. |
A reconcile only ever overwrites matched balances. It cannot create an account in your plan, and it cannot quietly remove one. A held-back mortgage or property is added only after you supply its missing terms, through the same checks as an account you add by hand. Everything else in the diff is a report for you to act on.
Who wins, per account
Each account carries one directive that decides whether a freshly-pulled balance is authoritative for it. It is set per account, so one setting never drags the rest with it.
The list wins. Checking, brokerage and credit-card balances are overwritten on every sync you confirm, because the source is the better record.
Refreshed, then flagged. A property estimate moves on every pull, so it is brought in and marked noisy rather than presented as exact.
Never overwritten. An account you maintain yourself is reported in the diff and left exactly as you wrote it.
Staying current
The point of syncing again is not the writing, it is knowing which figures have gone quiet. Every reconcile reports that first, before it offers to change anything.
A balance refreshed within the last 30 days reads as fresh, an older one as stale, and one that was never refreshed is counted separately — because "we have an old figure" and "we never had this figure" are different problems. The count arrives with the dry run, so it is the thing you read before deciding whether to confirm.
The first time you tell a reconcile which of your accounts a given source row is, that pairing is saved onto the account. Every later run matches on it, so a second pass asks you nothing you have already answered — and a row can be re-pointed or unlinked just as deliberately.
A spouse's account, a card you ignore, a mortgage you are not planning around: record it as knowingly excluded and the reconcile stops proposing it, while your plan still carries the note that it exists. The decision is durable rather than re-litigated every sync.
What is not here
FinPlanTools does not ask for a bank login and holds no connection to an account aggregator. There is no credential of yours for us to lose and no third-party link to break. The cost of that is the one above: somebody has to bring the numbers, and that somebody is you or your assistant.
There is no background job and no scheduled pull. A sync happens inside a conversation you are in, when you ask for one. A plan you have not opened in three months holds the balances you left in it — which is exactly what the freshness report is for.
If you use Monarch, connect Monarch's own assistant connector alongside FinPlanTools. Your assistant asks Monarch for the account list and hands those rows to the reconcile, with no export in between. FinPlanTools itself never calls Monarch and never sees your Monarch login: the connection is between your assistant and Monarch.
The tools behind this page: reconcile_with_monarch for the diff and the apply, link_account
and unlink_account for the crosswalk, exclude_account for what
you choose not to model, and complete_synced_account for a held-back mortgage
or property. Your assistant picks them; you never type one.
Setup is a few minutes and does not involve a single credential of your bank's. You can add accounts by hand first and bring in a list later, or never bring one in at all.