Data Sheet

The Account Translation Utility 2.1.1(ATU) allows flexible routing of transactions to multiple portfolio files. Regular processing in Dataport is limited because all transactions from one custodian account number must be posted to one portfolio file. Dataport will not allow activity from one account to be split among several cli files. For example, when using Dataport, all activity for custodian account 123456 must go into the same cli file. Maintaining data that does not follow this one-to-one mapping requires manual intervention.

If, for example, you wanted the supervised assets for account 123456 to go into one cli file, and unsupervised assets for account 123456 to go into a different cli file, you would have to manually move the transactions out of the first cli file and into the second cli file.

ATU takes away the need for user intervention. It works as a pre-process to Dataport and translates the portfolio code based on user-defined criteria. The ability to run this process from an Axys script or from a batch file provides additional flexibility.

• ATU lets you translate account numbers based on Security Symbol, Security Type, or Asset Class.
• Because accounts that are not translated by ATU follow normal processing in Dataport, you only need to define the exceptions to the one-to-one, account-to-portfolio mapping.
• ATU works with any and all Dataport interfaces (Schwab, Fidelity, etc).

• Axys version 3.3 or higher
• Axys singler user or network version
• Windows NT, 2000, or XP
• Pentium 133Mhz PC
• 64MB RAM

Frequently Asked Questions

Case Studies: Link for Case Studies

For product support, click here.

Please contact our Webmaster if you have any questions or concerns regarding this web page.