A household with a current account, a joint account and a savings account needs more than a single combined number. It needs to know which account each record belongs to and which movements are simply money moving between its own accounts.
If you use Sure, BankSync's SimpleFIN connection can bring supported UK accounts into that ledger. Start with a small scope and deliberate account mapping; then build the household view on top.
The first useful result is simple: one source account maps to one intended ledger account, and a known payment appears in the right place.
Reviewed on 1 November 2026. Account names and figures below are illustrative.
Plan the account map
| BankSync source | Intended Sure account | Household purpose |
|---|---|---|
| Joint current account | Joint household current | Shared bills and day-to-day payments |
| Personal current account | Personal current | Only include if part of the agreed scope |
| Household savings | Household reserve | Track reserve movements separately |
| An unrelated business account | Not included | Keep outside this household access |
Use the right connection route
BankSync implements the SimpleFIN protocol over banks already connected to BankSync. It is not SimpleFIN Bridge, which is a separate service.
The BankSync SimpleFIN guide documents Sure's flow: create a named access in BankSync, enter its setup token in Sure's Settings → Providers → SimpleFIN panel, choose Save and connect, then link imported accounts from Accounts.
Use Sure's web app for setup and review. The project's client guide identifies the web app as its full application surface; other clients can expose a narrower feature set. Check your installed release if labels differ.
For UK banking, first verify the exact bank entity and account support in BankSync. The UK connection guide is the relevant source for coverage, consent and history limits.
Connect with a small, reviewable scope
Verify the bank in BankSync
Confirm the expected UK account is connected and reporting without an unresolved consent error.
Create named SimpleFIN access
As workspace Admin or Owner, open Settings → Developers → SimpleFIN and select the accounts Sure should receive.
Inspect Preview
Check the returned account list and any source errors before configuring the app.
Enter the token in Sure
Use the SimpleFIN provider panel and the BankSync-issued setup token.
Link the ledger accounts
Match each imported account to its intended Sure account, checking identity and currency.
Review a sample
Find a known payment and compare it with the bank before extending scope.
Check balances at a comparable moment
A bank's available balance can differ from a posted or ledger balance. A balance returned by an integration also has a source refresh time. Compare like with like before concluding that the app is wrong.
Record the account, currency, balance basis and date of the comparison. Check a few underlying transactions as well as the headline figure.
For an illustrative current account, £800 opening balance plus £1,500 received minus £1,100 paid gives £1,200. If Sure shows a different result, examine the starting position, missing records, duplicates and timing. Do not fix a difference by changing a real payment's amount without evidence.
A successful connection is evidence of connectivity. Reconciliation is the separate check that the ledger represents the account for the period you care about.
Review movements before interpreting spending
| Observed movement | Likely review question | Avoid |
|---|---|---|
| £200 current-to-savings transfer | Do both account legs exist and agree? | Counting the transfer as household consumption |
| Credit-card repayment | Is the purchase already in the card ledger? | Counting both purchase and repayment as spending |
| Refund | Which earlier purchase does it relate to? | Treating every incoming amount as wages |
| Repeated £25 payments | Are these distinct purchases? | Deleting one solely because the amounts match |
Keep household scope explicit
Decide together which accounts belong in the shared review. An app-level access should contain only the accounts needed for that purpose. BankSync's SimpleFIN access defaults to all accounts unless you choose a narrower scope.
Account scope at the source and user permissions in Sure are different controls. Scope determines what the app can fetch; Sure's own configuration determines what its users can see. Review both rather than assuming one replaces the other.
Name the access so you can identify it later, for example “Sure household ledger”. Keep tokens out of shared documents. If you change the account scope, inspect the next fetch and the existing app records separately; do not assume reducing access erases previously imported data.
Investigate at the layer that has the problem
If an account is absent from BankSync Preview, inspect the source connection and scope. If Preview includes it but the Sure ledger does not, inspect Sure's provider state and account mapping.
If a payment is missing from both, check its posted status and the available history. If the record exists but the household report excludes it, inspect the app's category, account and date filters.
Keep a simple review note: latest successful sync, last reconciliation date and open issues. That lets another authorised household member understand the state without seeing the connection secret.
The resulting ledger should make the household review easier: recent activity, transfers that need attention and balances whose dates are understood. More connected accounts are useful only when they remain explainable.