valo
Resource

Portfolio Sync

Valo portfolio sync imports read-only broker and exchange data into one portfolio record. It is designed to keep holdings, cash, performance, tax views, and Sonny analysis working from the same reconciled source of truth.

Access model
Read-only

Valo does not request trading, transfer, or withdrawal permissions. If a provider key allows those permissions, create a narrower key before connecting.

How it works

From provider data to portfolio records

01

Connect read-only data

Use the minimum read permissions needed for balances, positions, trades, and ledger entries. Valo cannot place orders, transfer assets, or withdraw funds.

02

Preview before import

Valo shows imported assets, transactions, cash, and provider balance differences before they become part of your portfolio records.

03

Keep records current

New activity can be pulled into the same portfolio over time, preserving tax wrappers, currencies, and manual adjustments you have already made.

Synced records

What Valo brings into sync

Sync is more than a holdings snapshot. The imported records feed performance charts, allocation, cash tracking, tax calculations, and the portfolio context Sonny can analyse.

  • Holdings and current balances where the provider exposes them
  • Filled trades, fees, and ledger rows used to build transaction history
  • Account wrappers such as ISA, SIPP, and GIA where the provider data supports them
  • Cash balances and currencies for portfolio-level net worth and FX views
  • Provider sync logs, errors, and balance differences that need review
Provider coverage

Current sync options

Native API coverage depends on what each provider exposes. Valo keeps provider-specific caveats in the API Limitations page so this list can stay focused on the sync options available to users.

SourceTypeStatusNotes
Trading 212
Stocks & ETFsAPI syncInvest and Stocks ISA accounts can import account data, positions, and filled order history where the beta API exposes them.
Kraken
CryptoAPI syncSpot balances, trade history, and ledger-backed activity are imported. Advanced activity can still need manual review.
CSV import
FallbackManual importCSV and manual entries fill gaps where a broker is not yet connected or where an API omits older or specialist activity.
Controls

Safety and review points

Broker credentials are stored encrypted and used only for the sync features you choose.
Withdrawal, transfer, and trading permissions should never be granted to a Valo connection.
Imported activity remains reviewable, so provider omissions do not silently become taxable trades.
Disconnecting a provider stops future syncs while leaving already imported portfolio records under your control.

Need provider-specific detail?

Review current importer caveats before relying on a first sync for tax or performance checks.

API Limitations