Purpose: Reports that are run and stored as part of a quarterly or month end process can be retrieved from the client document endpoint. These may then be presented to…
Purpose: Data produced by the proposal features in Orion’s Advisor Portal (Element) can be reviewed and downloaded through the API. This includes current and previous versions of a proposal. Simple…
Purpose: Creating and updating a prospect in the Advisor Portal (Element) for use with the New Account and Proposal process from outside of Element. This would allow you to gather…
Purpose: Sleeving registrations allows a single custodian account to be split into sub-accounts, which can then be assigned to different strategies. Orion’s sleeve features will automatically divide activity among the…
Purpose: The basic data for aggregated accounts (Plaid) linked to an Orion financial plan data can be retrieved from Orion’s API. Simple Use Case: Firm wants to pull outside accounts…
Purpose: Net Worth data can be retrieved from Orion’s API for Orion Planning, including assets and liabilities which are linked from Orion Connect or from aggregation (Plaid). Simple Use Case:…
Purpose: Orion has three primary types of report, standard or “canned” reports, legacy report builder reports, and report builder reports. Standard reports are pre-created by Orion for all advisors, while…
Purpose: When a client closes an account with their advisor, it is a best practice to cancel that account within Orion using the account cancelation functionality. This action will zero…
Purpose: The best practice for making key detail changes on an account in Orion is to use the Account Change functionality. While changes to account details can be applied directly…
Purpose: While the API provides several ways to query an entire list of a specific entity type, often being able search for a specific client, account, or even report can…