Why?

• Streamline your portfolio management by creating transactions en masse for your manual accounts!

Common Use Cases
Import missing history on your live downloading accounts
Maintain your manual accounts with ease by adding in all your transactions with one import

 

What?

Use the Transaction Add import to create transactions en masse for a single account or multiple accounts simultaneously within the same import template. Generally, transactions should only be manually created for accounts that are manually maintained at your firm. It is not a best practice to manually create transactions for accounts that are actively downloading into Orion. 


Please Note: This import is only available to advisor level users. To use the Transaction Add import, the following privileges must be enabled for your role within the Manage Users app .

• Transactions - Edit checkbox  (Located under the Records tab > Portfolio section)
• Transaction Add  (Located under the Actions tab > Custom Imports section)

For more information on editing privileges, review the Manage Users: Roles and Privileges article. 

How?

Complete and Process the Import Template

For detailed instructions on how to download, process, and troubleshoot a custom import, review the New Custom Imports Tool section of the Custom Imports Overview article.

Review the Transaction Add Import Guide for examples and an explanation of how to fill out the template. Review the Transaction Add Import Guide and Transaction Type Guide sheets on the attached spreadsheet. For efficiency, only fill in the applicable columns that need to be updated and leave the remaining columns blank. Please note, some fields require one or the other to be populated. This is notated in the Transaction Add Import Guide sheet under the Explanation column for each field. 

To download the import as an Excel file, click the  button from the preview page within the link.


This spreadsheet also includes three troubleshooting sheets that provide an explanation of each error or warning message and how you can resolve each message. Please Note: If a transaction row has an error, that transaction will not be created. If a transaction row has a warning, that transaction will still be created, but it is best practice to review the warning before processing the import. 
 

• Troubleshooting Initial Import Messages: These messages indicate why certain data did not import. You will need to enter the data into the grid again before being able to continue.
• Troubleshooting Warning Messages: These messages will not prevent the import but require reviewing information that should be addressed before importing.
• Troubleshooting Error Messages: These messages will prevent an Import from processing successfully and will require correction.