Self-hosting a finance app gives you responsibility for the app and its stored records. A useful bank connection then needs a second discipline: knowing which accounts arrived, how fresh they are and what the totals mean.
Securo can use a BankSync-issued SimpleFIN token to read supported UK accounts already connected to BankSync. This guide takes you from that connection to a practical multi-account review.
Start with GBP current and savings accounts. Prove those records are understandable before adding foreign currencies, investments or a wider household scope.
Reviewed on 1 November 2026 against BankSync's documentation and Securo's official project documentation. Examples are illustrative.
Know which layer owns the question
| Layer | Question | Evidence |
|---|---|---|
| Bank connection | Is this UK account supported and authorised? | BankSync connection state |
| SimpleFIN access | Which accounts can this app fetch? | Named access and Preview |
| Securo instance | Did the app import and display the right records? | Account list and transaction review |
| Your review | Do balances and movements agree? | Comparable bank records and reconciliation notes |
Prepare Securo's SimpleFIN connection
Securo's official repository documents enabling SimpleFIN with the environment setting below. Apply configuration through your normal hosting process and use a current supported release.
SIMPLEFIN_ENABLED=true
Then use Accounts → Connect Bank → SimpleFIN in Securo. Obtain the setup token from BankSync, not from a separate Bridge connection.
The BankSync SimpleFIN guide explains that Securo's SIMPLEFIN_API_URL setting only affects where users are directed to obtain a token. For the BankSync route, follow that guide and paste the BankSync-issued token rather than replacing the setting with a guessed endpoint.
This article assumes Securo is already installed. Use the project's official documentation for deployment and application administration.
Connect and validate a small account set
Check the UK bank source
Confirm the intended account appears in BankSync and resolve any consent issue.
Create a scoped access
In BankSync Settings → Developers → SimpleFIN, create a named Securo access for the required accounts.
Inspect Preview
Check account identity, currency, balances and any reported errors.
Claim the token in Securo
Paste the once-only setup token into the SimpleFIN connection flow.
Inspect the resulting accounts
Look for unexpected duplicates or missing accounts before relying on the overview.
Compare known records
Check a recent posted payment and the balance date against the bank.
Compare balances with dates attached
A balance is a value at a point in time. If one account refreshed yesterday and another refreshed today, their sum is not necessarily a simultaneous snapshot.
BankSync's SimpleFIN Preview includes the response available to the app and reports upstream errors. Use that to separate stale source data from an app-side display or import issue. Repeatedly fetching an unchanged source does not make it more current.
For an illustrative household, a current account shows £1,200 and a savings account £3,000. The displayed total is £4,200, but record the dates before calling it today's position. If a £500 transfer is in flight between the accounts, one side may appear before the other.
The UK bank guide also explains pending-record behaviour and available history. Start your review with posted transactions and treat any pending view separately.
A practical multi-account review
| Check | Example question | Action |
|---|---|---|
| Completeness | Are both expected GBP accounts present? | Inspect scope and connection state |
| Freshness | Do the balance timestamps cover the same review point? | Label differences or wait for comparable data |
| Transfers | Does £500 out correspond to £500 in? | Review both legs before interpreting spending |
| Duplicates | Does a source account appear twice? | Investigate before aggregating |
| Currency | Is a EUR account being added to GBP? | Keep units separate or verify conversion |
| History | Does the report start before imported records? | Label the incomplete period |
Add currency complexity only when you can explain it
Securo supports multiple currencies, but a converted total depends on rate configuration and timing. Its official documentation warns that without the configured exchange-rate provider, cross-currency amounts can fall back to a 1:1 rate with a visual warning.
For a first review, keep GBP totals separate. If you later add EUR or USD, check the exchange-rate configuration and inspect a known conversion. A warning should not disappear into a polished chart.
Likewise, a UK bank account connection does not imply that every investment holding or pension will be available. Verify each source and data type rather than treating one successful current-account import as universal coverage.
Make the ongoing review operational
Keep a named owner for the Securo deployment and another clear responsibility for reviewing financial records, even if both roles belong to the same person.
Securo's automatic-sync documentation explains that scheduling is governed by its own worker configuration and polling behaviour. Check those settings rather than assuming a BankSync spreadsheet feed schedule controls Securo.
After an update or credential change, repeat the small acceptance check: expected accounts, known transaction, balance date and no unexplained duplicate account. If one bank has an error, do not treat the rest of the dashboard as proof that every source is current.
A useful overview exposes uncertainty. It should be easy to tell which numbers are current, which accounts need attention and which totals depend on conversion.