How integration works
Worthune keeps one record per client household. Your data reaches it three ways: a one-time import of your book, ongoing updates from the systems and aggregator feeds you already use, and your own application writing through the API. Out of it come projections, decisions, a client picture, and a signal to your systems whenever something changes.
Last reviewed . For the exact calls behind each step, see the developer docs.
The household record
Everything starts with a household: the people in it, their accounts by tax type with balances, their income and spending, their debts, and the advisor responsible. That record is what the planning engine reads, what the client portal shows, and what the weekly checks watch.
The record is deliberately small. It holds balances by account, not the individual holdings or transactions inside them, and it holds birth years and relationships, not names, addresses or identifiers. Your custodian and your CRM keep those. The result is a record that is easy to fill, easy to keep current, and light on personal data.
Three ways data comes in
First, a one-time import. You export your book from the system you use today, map its columns to the household record once, run a dry run that lists every problem row, and then import for real. The guide on bringing your book in walks through it.
Second, ongoing updates. Balances change every day; the household record accepts small updates from your aggregator feed or your own nightly job, and every update is versioned so two systems can never overwrite each other silently.
Third, your own application. Anything your product does, creating a household, adding an account, recording a decision, goes through the same API your integration team already uses.
What comes out
Projections and coordinated strategies on demand. A client picture that shows the balance sheet, this year's income and spending, the newest decisions, and a data-quality report that names any missing field and what supplying it would unlock. A running history of decisions per household.
And a signal whenever something changes: your systems are notified the moment a household is computed, updated, archived or decided, and once a week you receive the list of plans that have gone stale. The guide on getting data out has the details.
What you never have to build
The planning math, the yearly updates to tax and benefit rules, the coordination between strategies, and the record that shows where a number came from. Those are the product. Your team owns the mapping from your systems to the household record and the screens your clients and advisors see, and the white-label kit gives you a head start on the screens.
Questions
Common questions
- Do we have to change the systems we use today?
- No. Worthune sits beside them. Your portfolio system, CRM and custodian feeds stay where they are; you map their exports to the household record once and keep sending updates on the schedule you choose.
- Does Worthune connect directly to our custodian?
- Not directly. Live balances arrive through an aggregator feed you already have, or through a file or nightly job from your own systems. Worthune does not hold custodian credentials, positions or transactions.
- How long does an integration take?
- A book can be imported in a day once the mapping is right. Keeping it current is a scheduled job your team already knows how to run. Client-facing screens take longer, and the white-label reference build is the fastest way to start.
Something not covered here? Write to support@worthune.com.