Converting Your Advent Axys Database into Morningstar Office: Policy & Procedures

Morningstar Office Policy: Data Conversion Importing through the Conversion Completion Date

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1

Considerations for Data Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2What are the effects of adjustment transactions in Morningstar Office? - - - - - - - - 2What if NO pre-existing data/reconciliation issues exist in either the prior portfolio management system or the custodian files? - - - - - - - - 3What if pre-existing data/reconciliation issues exist in either the prior portfolio management system or with the custodian files? - - - - - - 4

Understanding the Database Conversion Process from Advent Axys to Morningstar Office

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5Does Morningstar offer a warranty for database conversions? - - - - - - - - - - - - - 5

Overview of the Data Conversion Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6What steps are involved in a database conversion? - - - - - - - - - - - - - - - - - -6Should I continue to import ongoing transactions before the converted database is available? - - - - - - - - - - - - - - - 6

Advisor Requirements for a Database Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7What files should I send to Morningstar before the conversion kickoff call? - - - - - - - 7What files should I send to Morningstar after the contract is signed? - - - - - - - - - 7How do I export the files from Advent Axys? - - - - - - - - - - - - - - - - - - - - - 8

Database Conversion Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 9What information is in scope for a database conversion? - - - - - - - - - - - - - - - 9What items are out of scope for a database conversion? - - - - - - - - - - - - - - 11

Version 2.0 i

Understanding the Post-Database Conversion Process from Advent Axys to Morningstar Office

Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 15What should I do before the database conversion is complete? - - - - - - - - - - - 16What will I receive when the database conversion is complete? - - - - - - - - - - - 16Should I continue to import while reconciling the converted data? - - - - - - - - - - 17How should I start working with the converted data? - - - - - - - - - - - - - - - - 17Why do I repeatedly see MsCash as a transaction for my accounts? - - - - - - - - - 18What reports should I use to compare data from Advent Axys to Morningstar Office? 18What do I do if the reports from Advent Axys don’t match the reports from Morningstar Office? - - - - - - - - - - - - - - - - - - - - - - - - 19How do I generate the Performance Summary report? - - - - - - - - - - - - - - - 20How do I generate the Portfolio Current Value by Security Type report? - - - - - - - 22How do I generate the Unrealized Gain/Loss report? - - - - - - - - - - - - - - - - 24How do I generate the Realized Gain/Loss report? - - - - - - - - - - - - - - - - - - 25How do I generate the Portfolio Cash Flows report? - - - - - - - - - - - - - - - - - 26

Version 2.0 ii

Morningstar Office Policy: Data Conversion Importing through the Conversion Completion Date

OverviewMorningstar’s data conversion team assists each Morningstar Office subscriber in bringing client data into Morningstar Office for the first time. This data could come from your current portfolio management system, custodian(s), or both. This document explains the policy followed by Morningstar’s data conversion team when importing client conversion data through the conversion completion date.

Note: Data cannot be converted from Microsoft Excel.

The data conversion team will identify a “conversion completed date” by which time client data will be available to each advisor in Morningstar Office. For the interim from the delivery of historical data files to the conversion completion date, the conversion team can also import into Morningstar Office data incurred during this time period.

In order to import converted data through the conversion completion date, the following three factors must be considered:

× Has the advisor provided Morningstar’s data conversion team a temporary third-party login authorization for each custodian the advisor uses?

× Does the advisor use Morningstar’s Back Office Services (BOS) team, and × Do data or reconciliation issues exist in either the advisor’s prior portfolio management

system or in the custodian files?

Disclaimer: Morningstar Office reconciles on share quantities, not market values. Methodology differences may exist between different portfolio management systems. Pre-existing data reconciliation issues may appear in Morningstar Office that are not displayed in other portfolio management systems. These pre-existing data reconciliation issues cannot be resolved by the database conversion process.

Version 2.0 1

Considerations for Data Conversions Overview

Considerations for Data Conversions

OverviewThis section explains how the data conversion policy applies to both advisors using Morningstar’s BOS team, and those who do not use this service. The policy for either group is based on whether data or reconciliation issues exist in either the advisor’s prior portfolio management system or the custodian files.

If issues do exist, advisors must also understand the effect of adjustment transactions (which will be used to reconcile the issues) on performance reports in Morningstar Office.

What are the effects of adjustment transactions in Morningstar Office?

In Morningstar Office, reports can be generated at both the client and the account levels. All performance report calculations, however, are reflected from the account level perspective. Entering adjustment transactions to reconcile the data will therefore affect Morningstar Office performance reporting for the affected accounts.

When comparing Morningstar Office reporting to the source portfolio management system note the following important points:

× The contributions and withdrawals at the client and account level will not match. × The performance return numbers will also differ. × Performance reporting time periods which exclude the month of the adjustment’s

transaction date will not be affected by the adjustment. × Prior to the data conversion, it is highly recommended that the advisor historically

reconcile all accounts through the current date. This will greatly assist in the data accuracy of since-inception performance reporting within Morningstar Office.

Version 2.0 2

Considerations for Data Conversions What if NO pre-existing data/reconciliation issues exist in either the prior

What if NO pre-existing data/reconciliation issues exist in either the prior portfolio management system or the custodian files?

For BOS clients, if no data or reconciliation issues exist in the advisor’s prior portfolio management system or custodian files, Morningstar’s data conversion team will import and reconcile the data from the last transaction date in the database backup through the current date. See the table below for more important points.

For advisors not utilizing Morningstar’s BOS team, the conversion process will be smoother if any unreconciled data is fixed (or temporary adjustment transactions are created) in the current portfolio system prior to providing a database for conversion. For non-BOS clients, if no issues exist with the data, Morningstar’s data conversion team will attempt to import the advisor's data through the current date, provided the conditions in the table below are met.

For BOS Clients For Non-BOS Clients

The conversion team will not import data past the conversion completion date; this will be the responsibility of the BOS team.

The advisor has provided all custodian import files in advance, and at least one week prior to the conversion completion date.

For BOS services, all custodian import sources must have the same last import date.

No pre-existing out-of-balance items exist.

For the importing gap period between the last import date (completed by the conversion team) through the BOS contract start date, advisors are responsible for saving their daily custodian import files. This will ensure no data gaps exist when BOS services begin.

The number of out-of-balance items do not increase upon importing additional data.

No data issues are present within the custodian import files the advisor provides to Morningstar’s data conversion team.

Data will not be imported past the conversion completion date by the data conversion team; this will be the responsibility of the advisor.

Version 2.0 3

Considerations for Data Conversions What if pre-existing data/reconciliation issues exist in either the prior port-

What if pre-existing data/reconciliation issues exist in either the prior portfolio management system or with the custodian files?

For BOS clients, if pre-existing data/reconciliation issues exist in either the prior portfolio management system or with the custodian files between the last transaction date in the database backup through the current date, note the important points in the table below.

For non-BOS clients, if issues exist with either the pre-existing data or the custodian import files, note the important points in the table below.

For BOS Clients For Non-BOS Clients

Morningstar’s data conversion team will enter adjusting transactions to reconcile the data, so back office services can begin sooner. The intention is to have adjustment transactions temporarily.

The advisor may choose to have Morningstar’s data conversion team enter adjusting transactions to reconcile the data and import through the current date. The intention is to have adjustment transactions temporarily.

This option will allow the advisor to utilize Morningstar Office sooner.

The data conversion team will provide a list of the previous out-of-balance items and adjusting transactions for the advisor to research.

The data conversion team will provide a list of the previous out-of-balance items and adjusting transactions for the advisor to research.

After the conversion is completed and the BOS contract has started, the advisor will have the opportunity to troubleshoot the pre-existing issues with the help of Morningstar’s various support teams.

If the advisor does not choose to have temporary adjustment transactions entered, additional data will not be imported by the data conversion team. It will be the responsibility of the advisor to resolve the pre-existing issues and to complete importing through the current date.

After the conversion is delivered, the advisor is responsible for resolving the pre-existing issues.

After the conversion is completed, the advisor will have the opportunity to receive training on how to troubleshoot the pre-existing data issues with the help of Morningstar’s various support teams.

The advisor may request extended assistance in troubleshooting and resolving pre-existing issues at an hourly rate.

After the conversion is delivered, the advisor is responsible for completing daily importing and resolving pre-existing issues.

The advisor may request extended assistance in troubleshooting and resolving pre-existing issues at an hourly rate.

Version 2.0 4

Understanding the Database Conversion Process from Advent Axys to Morningstar Office

OverviewThis document explains the process of converting transaction history from Advent Axys to Morningstar Office. The following topics are covered:

× Overview of the data conversion process × What the advisor must provide to Morningstar in order for a conversion to take place × What data Morningstar will convert to Morningstar Office, and × What items are out of scope.

Does Morningstar offer a warranty for database conversions?

Yes, once a database is converted and moved to the advisor’s login for Morningstar Office, the advisor signs off on the handoff. At that point, a 30-day warranty period begins, wherein the advisor must review and evaluate the data that was converted. A separate guide exists that covers the steps an advisor should take at this point in the process.

Version 2.0 5

Overview of the Data Conversion Process Overview

Overview of the Data Conversion Process

OverviewThis section provides an overview of the data conversion process.

What steps are involved in a database conversion?

To convert a database from Advent Axys to Morningstar Office, the following steps must take place:

1. The advisor fills out the Morningstar Office Back Office Services survey. This allows Morningstar to gather some preliminary data, and develop an initial quote for the service.

2. If the quote is accepted, the advisor provides the following, to allow Morningstar to confirm the price quote:

× Morningstar Office-supported import files from your custodian (these should be as of the database backup date)

× a database backup for an evaluation by Morningstar, and × a Reconciliation report from Advent Axys.

3. A pre-conversion call is held with your Morningstar Office Sales Rep, your CSC, and a member of the database conversion team, to evaluate the results of the initial analysis of the database.

4. A contract for the conversion is sent to the advisor. It will be countersigned by Morningstar.

5. The advisor submits the following to Morningstar: × a copy of the signed contract, and × a 50% deposit (paid by check or credit card).

6. If needed, Morningstar will contact you for an updated database from Advent Axys.7. The conversion is scheduled, and a delivery date is established.8. Morningstar converts the data in a test environment. Morningstar will coordinate the

ongoing import of custodian files.9. Morningstar checks the data quality, conducts reconciliation and performs any additional

importing for the converted data.10. The advisor’s Client Solutions Consultant (CSC) at Morningstar coordinates with the

advisor to move the converted data from the test environment to the advisor’s Morningstar Office login. The warranty period begins.

11. The advisor attends a session with an Import Specialist at Morningstar to learn the post-conversion importing process.

12. The advisor is invoiced for the balance due for the data conversion. The balance must be paid before the conclusion of the 30-day warranty period.

Should I continue to import ongoing transactions before the converted database is available?

Yes, you can continue to add these files, unless you custody your assets with TD Ameritrade or Charles Schwab. With those custodians, Morningstar can pull this data via third-party access. This process is a great opportunity for you to understand the import process while you are waiting for the conversion to complete. Note, though, that this imported data will be deleted when the converted data is moved to your live login.

Version 2.0 6

Advisor Requirements for a Database Conversion Overview

Advisor Requirements for a Database Conversion

OverviewThis section explains what an advisor must provide to Morningstar in order for a database conversion to take place.

What files should I send to Morningstar before the conversion kickoff call?

In order for a database conversion to take place, you must send in the following files before the conversion kickoff call takes place:

1. Advent Axys database files, including the following: × .cli (clients file) × sec.inf (securities file) × split.inf (securities splits file) × .pri (security prices file) × type.inf (security type file)

2. A Reconciliation report from Advent Axys as of the last transaction date of backup. This report will show any out-of-balance items compared to the advisor’s custodian’s record.

3. Custodian import files, as of the last transaction date in the database backup provided. These must be in the format supported by Morningstar Office.

If you custody assets with TD Ameritrade or Charles Schwab, Morningstar can collect this data on your behalf using third-part access.

What files should I send to Morningstar after the contract is signed?

Once the database conversion contract is signed, be sure to send the following:

1. Preferences for tax lot method and price source (custodian’s price or Morningstar’s price).

2. A spreadsheet with the Advent portfolio name in one column, and the corresponding custodian account number in the next column. Be sure to include any leading zeros in any applicable account numbers.

3. Reports for two or three high priority or complex accounts containing a variety or security and transaction types. Note the following about these accounts as well:

× At least one account should contain fixed income securities, if possible × The timeframe of the reports should be from the account’s inception date through

the last transaction date of the database files you provide. × Examples of these reports would be the Performance Summary report, and an

Appraisal report.4. If you wish to exclude any accounts from Morningstar Office, send those in a separate

spreadsheet.5. If you have combined multiple custodian accounts into one Advent portfolio, send that

data in a separate spreadsheet. Morningstar can provide a template of this spreadsheet.

After all of this content is received, the conversion process will begin. Your CSC will occasionally contact you throughout the conversion process, to update you on its status.

Version 2.0 7

Advisor Requirements for a Database Conversion How do I export the files from Advent Axys?

How do I export the files from Advent Axys?

The files in step 1 above need to be exported from Advent Axys. If you do not use the export function, Morningstar cannot read the files because they will be in Advent’s format.

To export the files, do the following:

1. Create a folder on your computer where you will export all the Advent files. For example, C:\Desktop\Morningstar Export.

2. Select all of your clients in Advent Axys.3. From the menu bar in Advent Axys, choose File…Export. The Export dialog box opens.4. In the Filenames and Extensions field, enter the path where your portfolio files are

located. This is most likely d:\Advent Axys3\exp\cli\*.cli; the *.cli acts as a wildcard to select all files with a .cli extension.

5. In the Directory to Export to field, enter the path to the folder you created in step 1. 6. From the Format drop-down field, be sure Tab-Delimited is selected.

7. Click OK.8. Repeat steps 1-6 for the rest of the file types you need. For step 3, use the table below

to reference what you should enter in the Filenames and Extensions field.

Note the values in these three fields

File Type What to enter in the Filenames and Extension field

Information d:\Advent Axys3\exp\inf\*.inf

Price d:\Advent Axys3\exp\pri\*.pri

Note the value change in this field

Version 2.0 8

Database Conversion Limitations Overview

Database Conversion Limitations

OverviewThis section explains which items from Advent Axys can be converted to Morningstar Office, and which items cannot be converted.

What information is in scope for a database conversion?

The following table summarizes the content that will be converted from Advent Axys into Morningstar Office:

Area Items Comments

Client Profile Information

× Name × Address × Phone Number × Social Security Number

For Active accounts, client profile data will be converted from the custodian import client and name files, not Advent Axys.

If the full client and account name file is not provided from the custodian import files, the data will be converted as provided. The advisor will be able to update the client profile information in Office after the conversion.

For Inactive accounts, the client profile will be converted from the Advent Axys client file, if included.

Version 2.0 9

Database Conversion Limitations What information is in scope for a database conversion?

Transactions

× Distribution reinvest transaction types

× Multiple fee types × Cost Basis × Deliver-in/Deliver-outs

vs Credits/Debits transaction types

For distribution reinvest transactions, the Advent Axys data may translate distribution reinvest transaction types into two transaction pairs. These transaction pairs are normally listed in the form of a Buy and a corresponding Distribution transaction type. The data is converted into Morningstar Office as provided. Please note that this will affect unrealized/realized gain and loss reporting within Office.

Multiple fee types (Misc. Fee, Loan Fee, Management Fee, etc.) within Advent Axys containing the transaction code epus are all converted as Management Fees within Office. Advent Axys transaction codes listed as exus are converted as Expenses within Office. Please be sure the Advent Axys transactions are coded accurately, so they are properly reflected within Office.

Per share cost basis data is only converted if provided within the actual exported Advent cli file.

“li” deliver-in or “lo” deliver-out transactions that contain the transaction setting code “Y” in the 53rd character row position inside the Advent client file will be converted as a Deliver-in or Deliver-out respectively.

“li” deliver-in or “lo” deliver-out transactions that contain the transaction setting code “N” in the 53rd character row position inside the Advent client file will be converted as a Credit of Security or Debit of Security respectively.

Prices × Transaction prices × Historical security

prices

Transaction prices and historical security prices are converted, if data is provided.

Area Items Comments

Version 2.0 10

Database Conversion Limitations What items are out of scope for a database conversion?

What items are out of scope for a database conversion?

The following table summarizes the content not converted from Advent Axys into Morningstar Office:

SecuritiesAll securities are converted as US dollars, if the database provides the currency value.

If the Advent Axys sec.inf file is provided, security names for user-defined securities, as well as data fields used to calculate accrued interest will be converted.

Data fields required to calculate accrued interest should be specifically selected in order to be converted via the Advent Axys security file. In Advent Axys, if the Use Security Type box is selected instead, the necessary datapoints will not be exported to the Advent Axys security file, and are not converted.

If the Advent Axys database contains transactions linked to securities labeled as “none” or “client,” these will be converted as out-of-pocket cash from the provided database files. Please review your data to verify the appropriate security for the affected transactions.

Area Items Comments

Area Items Comments

Client-Level Datapoints

× Any additional client-level datapoint not explicitly listed in the In Scope Conversion items, under the client profile information section.

× Client Last Name for Advent Axys accounts that do not have an active custodian account. The Last Name field must be listed in the Advent Axys client file as a separate field in order to be converted.

× Representative IDs × Client Types × Related Person/

Proprietary × Client Rank × Additional member

records and member information for the client record such as spouses, children, etc.

× Employer Information

The client is converted as the primary member record in Morningstar Office

Version 2.0 11

Database Conversion Limitations What items are out of scope for a database conversion?

Account-Level Datapoints

× Account Rank × Account Category × Account Open Date × Account Types × Account Funding Date × Billing Start Date × Account Closed Date × Termination Date × Termination Reason × Performance Start

Date × Block Trade Account

Number × Account Managed By × Account Registration

Data × Discretionary Account

Flag × Third Party Managed

Flag × Related Person/

Proprietary Flag × Block Trade Account

Number × Current Custodian × Business Type × Account Notes × Investment Strategy × Account Contact

n/a

Methodology Differences between Advent Axys and Morningstar Office

× Reinvestment Transaction Types

Morningstar Office does not use offsetting cash securities such as DVWASH, DVSHRT, and DVLONG to translate transactions into reinvestment transaction types such as Distribution reinvest, Long-term Capital Gain Re-invest and Short-term Capital Gain Reinvest.

The actual transaction type code must be labeled as a reinvestment transaction type in order to be converted as such.

Area Items Comments

Version 2.0 12

Database Conversion Limitations What items are out of scope for a database conversion?

Principal Paydown transactions from Advent Axys

Morningstar Office utilizes the industry standard in handling mortgage-backed security types, or a security having principal paydown transaction types.

Morningstar Office uses principal factors in the holding’s price calculation to decrease the original principal balance of the holding. Advent Axys adjusts the actual original principal amount to decrease the principal balance of the holding. With this methodology, the Advent Axys data does not contain complete information to process securities having principal paydown transaction types.

These transactions types are provided with a zero share quantity that cannot be processed within Morningstar Office. These affected securities will appear out-of-balance on the Morningstar Office Reconciliation report.

The affected holdings in the converted data will not match Advent Axys’ performance reporting results, due to the incomplete data in the Advent Axys files.

The unreconciled items can be resolved through deliver-in and deliver-out transactions to balance the holdings (as of the last transaction date of the converted data). These adjustments will affect performance reporting in the month the adjustments are entered.

The data being imported from the custodian source going forward from the converted data will not be affected by this scenario.

Area Items Comments

Version 2.0 13

Database Conversion Limitations What items are out of scope for a database conversion?

Version 2.0 14

Understanding the Post-Database Conversion Process from Advent Axys to Morningstar Office

OverviewThis document explains how to navigate the post-database conversion process after your data is moved from Advent Axys to Morningstar Office. Once your data is brought over, the warranty period begins, and you need to begin reviewing the data. The warranty period lasts for 30 days, and you should plan to use as much of this time as possible in reviewing and proofing the data for client use.

Morningstar’s goal in conducting a database conversion is to faithfully and fully reproduce your data from Advent Axys to Morningstar Office. However, this does not mean the data will automatically be ready to use on reports from Morningstar Office. Any issues that exist in Advent Axys will also exist in Morningstar Office.

Version 2.0 15

What should I do before the database conversion is complete?

While Morningstar is working on converting your database into Morningstar Office, you should work with your CSC to identify which Morningstar Office reports you will run for your clients. This is an important determination to make, because once the database conversion is complete you’ll want to run these reports and compare the data to the reports you generated from Advent Axys.

It’s also a good idea to spend some time working with your CSC to understand other Morningstar Office system settings. Note that although you can create a number of settings, you should not assign them to clients or accounts, as these records will be overwritten once the conversion is complete.

What will I receive when the database conversion is complete?

Once the database conversion is complete, Morningstar will send you an Excel spreadsheet with transactions that have been flagged for one reason or another. This spreadsheet will contain multiple tabs, highlighting data issues identified in the pre-conversion call, as well as ongoing items during the conversion. In sum, it will likely contain thousands of rows. Do not panic when you see this, as this volume is both typical and manageable.

One of your goals in the post-database conversion process is to steadily work your through these items, with the assistance of your Client Solutions Consultant (CSC) at Morningstar. Also, note that not all of these items will need to be resolved before you can begin producing reports from Morningstar Office. You will come to understand which of the flagged transactions represent hard warnings (which will prevent you from producing accurate reports), and which are for soft warnings (which might prevent you from successfully producing reports).

The following table covers other common issues to address from this spreadsheet:

Item Comment Worksheet Tab to Reference

Temporary Adjustment Transactions

You need to review temporary adjustment transactions that were entered as part of the conversion. These can affect contributions, withdrawals and performance returns reporting for the time period that includes the date of the adjustment.

Adjustment Transactions

Unreconciled Data

Unreconciled data appearing as out of balance should be reviewed and resolved in Morningstar Office. Be sure to address these issues before importing new data into Morningstar Office.

Custodian_Date_Unreconciled

Pre-Existing Data Issues

Pre-existing data issues found within the Advent Axys database should be reviewed prior to submitting issues to the data conversion team, to ensure that the issue was not pre-existing.

ADVIssues_

Version 2.0 16

Should I continue to import while reconciling the converted data?

You can continue importing during the warranty period, but you should first reconcile all out-of-balance items from the conversion spreadsheet. This will help avoid confusion as to whether out-of-balance items are a result of conversion issues, or new issues that develop during importing.

To help you reconcile the items appearing in the database conversion spreadsheet, reference these documents:

× Handling Import Warnings, and × Understanding Transaction and Report Warnings.

How should I start working with the converted data?

The first step should be to evaluate the content of the spreadsheet you received after the data conversion took place. Focus on resolving the following issues:

× Zero-quantity transactions × Missing transaction prices, and × Missing quarter-end prices.

An important question to consider here is whether you want the data on Morningstar Office reports to match that from your custodian, or from the Advent Axys database (where a discrepancy exists between these two sources). Your CSC will guide you on how to run the Security Price Missing report as of the previous quarter-end date.

Also, be sure to take note of the data source for transactions in an account. You can see this by opening an account, going to the Transactions page and scrolling all the way to the right. The Data Source column will tell you whether the data came from Advent Axys, Morningstar or your custodian.

Scroll to the far right in an account’s window to see this column

Version 2.0 17

Why do I repeatedly see MsCash as a transaction for my accounts?

As you work through your accounts, you will see MsCash (the value should be $0) listed among the transactions for your accounts. It is critical that you leave these untouched, and do not delete or attempt to merge away these items. These transactions did not originate in Advent Axys, but were inserted by Morningstar’s database conversion team to help reconcile your data. If you accidentally delete one of these transactions, or if you see it has a value of something other than $0, please contact your Client Solutions Consultant.

What reports should I use to compare data from Advent Axys to Morningstar Office?

The next step is to check for performance discrepancies between Advent Axys and Morningstar Office. Do this for one account at a time, rather than creating a batch report for all accounts. Choose a few significant accounts to work with; some of these should include fixed-income holdings.

Note: Eventually, you will check every account, via a global report.

When creating these reports, be sure to use the last transaction date contained in the database you sent to Morningstar for conversion.

Generate the following reports to check for discrepancies:

× Performance Summary Report × Unrealized Gain/Loss Report × Realized Gain/Loss Report × Portfolio Cash Flow, and × Portfolio Current Value.

These instances of MsCash are typical,and should be left alone

Version 2.0 18

What do I do if the reports from Advent Axys don’t match the reports from Morningstar Office?

If the values on the reports from Advent Axys do not match those from Morningstar Office, the solution lies in understanding what type of mismatch is occurring. Please reference the following table.

If this figure is wrong… Use this report to analyze it further…

IRR Performance Summary Report

TWR

Performance Summary Report

Performance by Account Report (if needed)

Performance by Security Report (if needed)

Market Value Portfolio Current Value

Cost Basis (Gain\Loss)Unrealized Gain\Loss Report

Realized Gain\Loss Report

Beginning Market Value Portfolio Current Value

Additions/Withdrawals Portfolio Cash Flow

Ending Market Value Portfolio Current Value

Version 2.0 19

How do I generate the Performance Summary report?

The Performance Summary report shows you not only what an account is worth on a particular date, but also how interest, dividends, fees and other factors influenced this sum. You can see returns on this report either as time-weighted returns (TWR) or using an internal rate of return (IRR).

To generate the Performance Summary report, do the following:

1. Go to the Portfolio Management tab, and click once on the Accounts page.2. Double-click the name of the account you want to work with in order to open it.3. In the Account window, use the menu bar at the top of the screen to select

Reports…Performance…Performance…Summary. The Report Options dialog box opens.

4. Update the Start Date and End Date fields.

Note: For the Start Date field in Morningstar Office, this date should be one day later than in Advent Axys. For example, in Advent Axys, the Start Date for a report will be 03/31, but in Morningstar Office the corresponding report should have 04/01 as the Start Date. This must be set this way due to a discrepancy in the way the two systems calculate return values.

Follow this path to generate the Performance Summary report

Version 2.0 20

5. Take note of the Return Type drop-down field; it can be set to Use IRR or Use TWR.

6. Additionally, the Return Period field provides options for checking other time periods, such as Trailing time periods.

7. Click OK to generate the report.

Note: If you see an alert asking if you want to see the warning message, be sure to click OK. This opens a Notepad file with information that may require attention. You should keep this Notepad file open as a reference, in case you find discrepancies on the report that need to be reconciled.

Be sure to update these fields with the correct dates

Take note of the Return Type

The message at top of the Notepad filetells you which item need attention

Version 2.0 21

How do I generate the Portfolio Current Value by Security Type report?

If you see an account’s market value is incorrect, you can use this report to troubleshoot the issue. The report shows you the number of units a client owns of each security, the cost of each unit, the market value of each security, and more.

You can generate the Portfolio Current Value report by security, security type or asset class. Security Type is recommended, as this is usually how custodians also present this data on a report.

To generate the Portfolio Current Value by Security Type report, do the following:

1. Go to the Portfolio Management tab, and click once on the Accounts page.2. Double-click the name of the account you want to work with in order to open it.3. In the Account window, use the menu bar at the top of the screen to select

Reports…Portfolio…Portfolio Current Value…By Security Type. The Report Options dialog box opens.

Follow this path to generate the PortfolioCurrent Value report

Version 2.0 22

4. Update the As of Date field. This should match the date of the report you are generating in Advent Axys.

5. Click OK to generate the report.

Note: If you see an alert asking if you want to see the warning message, be sure to click OK. This opens a Notepad file with information that may require attention. You should keep this Notepad file open as a reference, in case you find discrepancies on the report that need to be reconciled.

Be sure this field has the correct date

The message at top of the Notepad filetells you which item need attention

Version 2.0 23

How do I generate the Unrealized Gain/Loss report?

To generate the Unrealized Gain/Loss report, do the following:

1. Go to the Portfolio Management tab, and click once on the Accounts page.2. Double-click the name of the account you want to work with in order to open it.3. In the Account window, use the menu bar at the top of the screen to select

Reports…Portfolio…Unrealized Gain/Loss. The Report Options dialog box opens.

4. Update the As of Date field. This should match the date of the report you are generating in Advent Axys.

5. Click OK to generate the report.

Follow this path to generate the UnrealizedGain/Loss report

Be sure this field has the correct date

Version 2.0 24

How do I generate the Realized Gain/Loss report?

This report is usually run for an entire calendar year period. To generate the Realized Gain/Loss report, do the following:

1. Go to the Portfolio Management tab, and click once on the Accounts page.2. Double-click the name of the account you want to work with in order to open it.3. In the Account window, use the menu bar at the top of the screen to select

Reports…Portfolio…Realized Gain/Loss. The Report Options dialog box opens.

4. Update the Start Date and End Date fields.

Note: For the Start Date field in Morningstar Office, this date should be one day later than in Advent Axys. For example, in Advent Axys, the Start Date for a report will be 03/31, but in Morningstar Office the corresponding report should have 04/01 as the Start Date. This must be set this way due to a discrepancy in the way the two systems calculate return values.

5. Click OK to generate the report.

Follow this path to generate the RealizedGain/Loss report

Be sure to update these fields with the correct dates

Version 2.0 25

How do I generate the Portfolio Cash Flows report?

This report is used to troubleshoot the additions, withdrawals and net investment in your accounts.

To generate the Portfolio Cash Flows report, do the following:

1. Go to the Portfolio Management tab, and click once on the Accounts page.2. Double-click the name of the account you want to work with in order to open it.3. In the Account window, use the menu bar at the top of the screen to select

Reports…Portfolio…Portfolio Cash Flows. The Report Options dialog box opens.

4. Update the Start Date and End Date fields.

Note: For the Start Date field in Morningstar Office, this date should be one day later than in Advent Axys. For example, in Advent Axys, the Start Date for a report will be 03/31, but in Morningstar Office the corresponding report should have 04/01 as the Start Date. This must be set this way due to a discrepancy in the way the two systems calculate return values.

5. Click OK to generate the report.

Follow this path to generate the PortfolioCash Flows report

Be sure to update these fields with the correct dates

Version 2.0 26