Connect Saxo Bank to Wolfora

Manual CSV imports work for a one-off history load. They fail as a weekly habit: missed files, wrong date ranges, and no automatic capture of new trades. An API connection keeps Wolfora closer to Saxo’s books without turning Wolfora into a trading terminal.

Saxo’s reporting is strong inside Saxo. The gap appears when you also hold a bank PEA, IBKR, Trade Republic history, or crypto. Connecting Saxo into Wolfora is about consolidation, not replacing Saxo’s execution tools.

Depending on your Saxo setup and the scopes available, Wolfora can import transactions and positions and reuse Saxo performance points — including official TWR / account value series when the platform exposes them.

The connection is read-oriented. Wolfora does not place orders on your behalf. Custody and trading stay on Saxo; Wolfora stores synced data for analytics in your Wolfora portfolio accounts.

Exact fields can evolve with Saxo OpenAPI capabilities. After the first sync, verify positions and a recent trade against Saxo’s own statements before you trust long-horizon charts.

In Wolfora, open Portfolio setup and choose Saxo. Complete the OAuth consent for the environment your account actually uses. Simulation and live are different worlds — keys and consents must match the account you care about.

Authorise only what you need for portfolio sync. Prefer least privilege. If Saxo presents environment or app choices, pick the live client that matches your funded account.

After consent, run a sync. Positions and history should appear under your Saxo-linked portfolio account in Wolfora. If nothing lands, check environment mismatch first (sim vs live), then re-consent, then support with a screenshot of the Saxo side error if any.

Label the Wolfora account clearly (for example “Saxo PEA” or “Saxo brokerage”) so PEA vs CTO semantics stay readable when you add IBKR or CSV accounts later.

If Saxo hosts your PEA, keep that legal wrapper in mind when you analyse tax — Wolfora consolidates numbers; it does not turn a PEA into a CTO. See the PEA vs brokerage guide for envelope strategy.

If you hold both a PEA and a CTO at Saxo (or PEA at a bank and CTO at Saxo), prefer separate Wolfora accounts that mirror those envelopes, then use the global portfolio view for totals.

Treat Saxo as source of truth for executions. If a fill looks wrong in Wolfora, compare with Saxo’s trade blotter before editing history by hand.

Re-sync after heavy trading days or corporate actions. Do not expect every corporate event to be perfect on day one — spot-check dividends and splits.

Combine with IBKR Flex or CSV imports for other venues so Saxo is one pillar of a multi-broker tracker, not a silo. Read the multi-broker overview if you are structuring accounts for the first time.

Complete OAuth only on the real Wolfora domain you trust. Phishing pages that mimic broker consents are a recurring finance risk — check the URL before approving.

If you rotate Saxo API apps or revoke access, re-connect in Wolfora promptly so sync does not silently stall while you keep trading.

Use separate Wolfora users only when you truly have separate households or mandates. Sharing one login across people blurs audit trails and portfolio ownership.

When you leave Saxo or close a sub-account, disconnect the integration in Wolfora so stale positions do not linger in consolidated allocation after the custodian is gone.

Saxo positions in Wolfora match Saxo’s open positions within normal FX/mark timing.

Recent fills appear without duplicate rows from a parallel CSV import of the same period.

Your global allocation chart includes Saxo plus every other venue you care about — not Saxo alone in a silo you still open three apps to interpret.