Plan Data Specification — XML
Purpose of this Document
Morningstar Investment Management LLC uses XML format to receive plan level information for Morningstar Retirement Manager data collection. This document outlines the specific data points as well as the format for each.
General Information
General Data Collection Process and Delivery Method
Morningstar will assign your firm a Client code. You will prepare the batch XML file to our specifications and include your internal plan identifiers as well as the fund lineups in each plan. Files are uploaded to Morningstar using the ftp service (ftp.morningstar.com). There will be a separate folder for each client’s files.
Update Procedures and Data Validation
On an ongoing basis, we must receive complete transfers of all plan-level data for any plans that have changes. Even if only one data item is updated all data should be included for the changed plans. Ultimately, you control how often you update your data.
Naming Convention
One XML file can contain multiple plans. We recommend the following file naming conventions:
- We recommend using the file name “ClientID_plan_date.xml”. ClientID is the code that Morningstar creates.
- When sending test files, please use file names that differentiate them from Production Files, such as “ClientID_plan_date_test.xml.
- If a single file is very large (e.g., larger than 100MB), you may split the data into several files named “ClientID_plan_date_1.xml”, “ClientID_plan_date_2.xml” etc, by appending sequence numbers to them. Use the same file names for each subsequent update.
File Processing
We will automatically retrieve production batch files from the FTP server. Production files for Morningstar Retirement Manager will be loaded to the database on a daily basis (or less frequent basis, depending on how frequently you send your files). If test files need to be loaded from the FTP site, please let the contact at Morningstar know, and the files will be loaded, as it is not an automated process. If the batch file does not conform to our schema, or if there are errors in the XML syntax, the batch import process will fail, and the file will not be imported. Additionally, the batch import process will generate error reports for the following events: if any funds in the batch file are not found in our database or if the plan does not meet compatibility requirements. The Morningstar team will work with you to identify and resolve any processing errors that occur.
The plan batch import process will also generate error reports for critical plan data that is missing or invalid. The Morningstar team will send these error reports to you so that they may be corrected.
Important Notes
- Only those fields marked “required” are required fields. However, we recommend that you provide us with all the requested data, as it greatly enhances the user experience.
- You should validate your data transfers against the schema that has been made available to you via your client team to ensure that they are well formed and valid.
- Any string longer than the length limit will be considered an error, and the plan would appear in the error report in the output directory on the FTP site.
- If you have no value on your system for a particular data element, either omit the element tag or send a NULL value, but do not send a zero. Zero will be treated by our system as a value.
- The XML file(s) should follow the sequence defined in the schema.
How to Read the XML Schema
You will receive a file of the schema for the Morningstar Retirement Manager XML Plan Data Specification called PlanBatchImport_3.1.xsd. The purpose of the schema is to explain which elements may appear in the XML file, how they will appear, and what the elements’ contents are. You will also receive a schema to be used in conjunction with the PlanBatchImport_3.1.xsd called CommonTypes_3.1.xsd. The purpose of the CommonTypes_3.1.xsd schema is to define common data types that are used throughout the PlanBatchImport_3.1.xsd schema.
Element Descriptions:
In the schema, there will also be a brief text description of what the element is. This description will appear with the following syntax:
<xs:annotation>
<xs:documentation>description</xs:documentation>
</xs:annotation>
Validating the XML File with the Schema
The XML document sent by the client will be validated against the schema that is sent to the client during implementation.
Plan Level Data: Detailed Element Descriptions
In order to provide a meaningful analysis of retirement income goals and investment recommendations for Morningstar Web Applications and offline processes, we recommend that you provide us with as much of the requested information as possible. Please note the following:
- Some data points are required in the schema and must be included in the batch file. These fields will be indicated in the “Required?” field. Other fields are optional, and will be indicated as such. Some elements are not needed. When this is the case, “N/A” will appear in the column.
- Throughout this specification, "Strategy Report" is used as the name for the marketing piece used to encourage participants to enroll in the managed accounts (Managed by Morningstar) service.
- Some data points that have a significant impact on retirement income projections and/or recommendations are required if they are applicable to the plan. These fields will be designated as such in the ‘Comments’ column. We understand that some of these data points may not be available on your recordkeeping system. If you are unable to provide one of these fields, we recommend that you determine a reasonable default value (if a default value is appropriate for the specific data element) and add that value to the batch file for the field. In the event that this approach will not work, the Morningstar team will work with you to evaluate other possible solutions.
- Some data points may be required in other special situations and are specified accordingly in the ‘Comments’ column.
- The ‘Displayed’ column will indicate whether that field can be auto-populated in the Morningstar interface for Morningstar Web Applications.
- For any items that have an ‘Element Type’ of ‘Boolean’, the values of true/false or 1/0 can be used.
- Unless otherwise specified in the ‘Comments’ column, the element is applicable for all types of plans.
- Throughout this specification, some data points refer to “Roth” contributions, which are a newer, post-tax contribution type that receives tax-advantaged status when money is withdrawn in retirement. This contribution type is only available to certain 401(k), 403(b), and 457(b) plans that choose to offer this option. (This is not to be confused with contributions to a Roth IRA). Roth contributions can be collected as a separate contribution type or bundled.
Detailed Element Descriptions
| Element Name | Path in Schema | Former name | Element Description | Element Type | Element Type Requirements | Default | Example | Required? | Displayed? | Feature | Comments |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Provider Level Identifier: | |||||||||||
| ClientID | PlanDefImportRequest | COMPANYID | Your company’s plan ID | string Alphanumeric (4 character min, 10 characters max) | AAAA | Required | N | Provider Level Identifier: | Morningstar assigns this value. The same client ID will be used across all products. ClientID must begin with a character in the alphabet and cannot begin with a numerical value. | ||
| TPA Level ID: | |||||||||||
| TpaID | ExtPlanDefinitionType | TPAID | Third Party Administrator ID | string Alphanumeric | Aaaaaa | Optional | N | TPA Level ID: | This field is optional when there are TPAs. The client may choose to send this field when a TPA has multiple plans under it. The client determines this value. It is best to use a descriptive name that identifies the TPA. Please Note: If a TpaID value is sent for the plan in the plan batch file, the same value must also be sent for TpaID in the participant file for any participants in that plan. | ||
| Plan Identifiers and Global Data Elements: | |||||||||||
| PlanID | PlanDefinition/PlanUpdate | PLANID | Your internal plan identification code | string Alphanumeric | 001 zvfz | Required | N | Plan Identifiers and Global Data Elements: | The client determines this value. It is an internal identifier used to distinguish individual plans. 50 characters is the maximum character length for this field. | ||
| TestPlan | PlanDefinition/PlanUpdate | TESTPLAN | Indicates whether the plan is a test plan | Boolean | FALSE | true/false | Optional | N | Plan Identifiers and Global Data Elements: | This field is used for calculations in the Measurement Module. If it is a test plan, the plan will not appear in the Measurement Module. This field can also be used for billing purposes. | |
| PlanName | PlanDefinition/PlanUpdate | PLANNAME | Plan name | string Alphanumeric (Less than 100 characters) | See comments | XYZ Company 401(k) | Optional | Y | Plan Identifiers and Global Data Elements: | This field is not required for Web Applications, but if it is not sent, plan names would appear in the Measurement Modules or on billing reports; instead the PlanID will be listed. Also, within the web interface, there are several locations where the plan name appears. If plan name is not sent, the plan type will appear in its place as the default. There may be confusion in the case of multiple plans of the same type if this occurs. This field is required for the Strategy Report. | |
| PlanStatus | PlanDefinition/PlanUpdate | PLANSTATUS | Is the plan active? | Boolean | TRUE | true/false | Optional | N | Plan Identifiers and Global Data Elements: | This field is used for clients to activate or deactivate plans. If "PlanStatus" is sent as "false", the plan is no longer eligible to participate in Retirement Manager. Only one transmission with PlanStatus equal to false is needed by Morningstar for plan deactivation. | |
| Type | PlanDefinition/PlanUpdate | TYPE | Type of plan | string Alphanumeric | 401K Thrift ProfitSharing MoneyPurchase 403B Sup403B 457B 401A NonQual SIMPLE_IRA SEP_IRA TradIRA RothIRA RolloverIRA NonQualifedVA TaftHartley | 401K | Required | N | Plan Identifiers and Global Data Elements: | All elements provided for the plan must pertain to the type of plan indicated by the ‘Type’ element. If a data element is applicable for only some plan types, those plan types will be listed in the ‘Comments’ column for that data element. If no particular plan types are indicated, then the data element is applicable for all plan types. | |
| ServiceOption | PlanDefinition/PlanUpdate | PRODUCTTYPE and MODULE | Service options available to that plan | string Alphanumeric | QualMRP OnlineAdvice OnlineCallCenter Proposal OnlineGuidance RID NoMatch CustomModels | QualMRP | Required | N | Plan Identifiers and Global Data Elements: | Service options are indicated at the plan level (using this field). When OnlineAdvice is selected, the participant is responsible for implementing the advice recommendations and any ongoing monitoring/rebalancing. When OnlineGuidance, Morningstar provides an asset allocation deemed most appropriate based on the information provided. The participant is responsible for making his or her own investment selections. When “OnlineCallCenter” is set up as a service option, other service options should also be specified to determine what services will be presented in the site. For example, if a plan lists the “OnlineCallCenter”, “OnlineAdvice”, and “QualMRP” service options, the Advice and Managed Accounts services will be offered in the site when a Call Center representative logs in on behalf of the participant. The “Proposal” and “Statement” service option values refer to the Proposal product. Although “Proposal” is the preferred value to send for this field, either of those values may be sent to indicate that the plan is set up for the Proposal. When “RID” is sent as a service option, no other service option can be sent along with it. RID is the Retirement Income Director and includes a professional money management service offered by Security Benefit to help manage investments in your account. Please Note: Proposal is a sub-product of Managed Accounts. It can not be sent by itself and must always be sent along with the 'QualMRP' service option. If the user has the option to flip between guidance and advice, both the OnlineAdvice and OnlineGuidance service options must be sent. The client configuration will indicate which way the user will default, whether it be starting with Guidance and having the option to flip to Advice or vice versa. | |
| Eligibee | PlanDefinition/PlanUpdate | ELIGIBEE | Total eligible employees in the plan | int Numeric | 200 | Optional | Y (displayed in reports) | Plan Identifiers and Global Data Elements: | Required when fees are participant based. Used for reports and billing purposes, where fees are participant based. This field contains the number of employees who are eligible to participate in the plan, including those who actively participate and those who do not. | ||
| Enrollee | PlanDefinition/PlanUpdate | ENROLEE | Total enrolled employees in the plan | int Numeric | 180 | Optional | Y (displayed in reports) | Plan Identifiers and Global Data Elements: | Used for Measurement Module only, as a comparison tool to indicate the number of eligible employees versus the number actually enrolled. | ||
| EnableLoan | PlanDefinition/PlanUpdate | LOAN | Does the plan allow loans? | Boolean | See Comments | TRUE | Optional | N | Plan Identifiers and Global Data Elements: | If no, all displays relevant to participant loans will be omitted from the interface, even if information is sent for loans at the participant level. The default is True for: 401(k), Thrift, Basic 403(b), 457(b), 401(a) and TaftHartley. The default is False for: Profit Sharing, Money Purchase, Supplemental 403b, Traditional IRA, Roth IRA, SEP IRA, SIMPLE IRA, Rollover IRA, NonQual and Non Qualified VA. If a value other than False is sent for these plan types, that value will be overwritten and set to False. | |
| EnableContributionChanges | PlanDefinition/PlanUpdate | N/A | Indicates whether the transaction will include any contribution information | Boolean | Account value or true | TRUE | Optional | N | Plan Identifiers and Global Data Elements: | EnableContributionChanges can be stated at either the plan or participant level. If not sent in the plan, and is sent as true at the participant level, then contribution detail will be included in the transaction. Vice versa if not sent in the plan, and is sent as false at the participant level, then contribution detail will not be included in the transaction. If sent as false in the plan and as true in the participant file, the plan level flag overrides the ppt level and contribution detail will not be included in the transaction. If sent as true in the plan and as false in the participant file, then the ppt level flag overrides the plan level and contribution detail will not be included in the transaction. If not sent in either the plan or participant level, we will assume a default of true and contribution detail will be included in the transaction. If EnableTransaction is false at the client or plan level, then EnableContributionChanges in the plan or participant level will be ignored. | |
| DisableProgressReport | PlanDefinition/PlanUpdate | N/A | indicates whether the plan enables the Progress Reports to show in the UI or not | Boolean | NULL | true/false | Optional | N | Plan Identifiers and Global Data Elements: | The DisableProgressReport fields should have the following attributes: Optional in Plan XML's Can be sent as 'true' or 'false' The assumption here is that if DisableProgressReport = 'true' is sent, the plan wants Progress Report not to show in the UI. Otherwise, Progress Report will be shown in UI. This is enabled as a global, optional field in plan schema. This additional field will serve to direct the API/UI settings for plans that enable this. This field will be used to overwrite the current custom setting to hide Schwab plan progress report. When Progress Reports are disabled by this flag (DisableProgressReport="true"), Progress Report notification emails for participants will be turned off as well. | |
| ShowProgramFees | PlanDefinition/PlanUpdate | N/A | indicates whether the plan enables to show program fees on the UI or not | Boolean | NULL | true/false | Optional | N | Plan Identifiers and Global Data Elements: | The ShowProgramFees fields should have the following attributes: Optional in Plan XML's Can be sent as 'true' or 'false' The assumption here is that if ShowProgramFees = 'false' is sent, the plan wants fees not to show in the UI. Otherwise, fees will be shown in UI. We need to add this globally as an optional field in plan schema. All program fees are recorded in the databse when sent. This additional field will serve to direct the API/UI settings for plans that enable this. This field will be used to overwrite the current custom setting to hide Schwab plan fees. | |
| EnableMSInvestmentProfileType | PlanDefinition/PlanUpdate | N/A | Indicates the type of Investment Profiles displayed/not-displayed in the UI. | Int | Default to 2 | 0 1 2 | Optional | N | Plan Identifiers and Global Data Elements: | Enable MSInvestmentProfileType needs to be compatible with ShowMSInvestmentProfile at the Client Config level. Used to designate whether or not we display FINRA, Non-Finra, or no Investment Profile reports. Supported Plan Level Values ShowMSInvestmentProfile Plan Level ‘Enable IR Value’ True 0, 1, 2 False 0 Key: 0 – No MSInvestmentProfile to be displayed 1 – FINRA MSInvestmentProfile to be displayed 2 – Non-FINRA MSInvestmentProfile to be displayed | |
| DeferralFormat | PlanDefinition/PlanUpdate | N/A | The contribution format the plan allows. | String | RateOrAmount | Rate Amount RateOrAmount | Optional | Y | Plan Identifiers and Global Data Elements: | Drives the display of contribution format in the Retirement Manager user interface. Applies to inside account employee contributions only (pretax, post-tax and Roth). - If a plan only allows % contributions, then “Rate” should be sent for DeferralFormat. Only % will be displayed for contribution format in Retirement Manager. - If a plan only allows $ contributions, then “Amount” should be sent for DeferralFormat. Only $ will be displayed for contribution format in Retirement Manager. - If a plan allows both % or $ contributions, then “RateOrAmount” should be sent for DeferralFormat. The Retirement Manager user interface will display the contribution format sent in the participant xml in this case. “RateOrAmount” is the default, so if DeferralFormat is not sent in the plan xml we will assume the plan allows both % or $ contribution formats which is our standard logic. Does not apply to the following plan types: TradIRA, RothIRA and NonQualVA. Please note, both rate and amount will be sent back in the transaction regardless of this setting. | |
| DeferralFormatCatchUp | PlanDefinition/PlanUpdate | N/A | The catch-up contribution format the plan allows. | String | RateOrAmount | Rate Amount RateOrAmount | Optional | Y | Plan Identifiers and Global Data Elements: | Drives the display of catch-up contribution format in the Retirement Manager user interface. Applies to inside account employee catch-up contributions only (pretax and Roth). - If a plan only allows % catch-up contributions, then “Rate” should be sent for DeferralFormatCatchUp. Only % will be displayed for catch-up contribution format in Retirement Manager. - If a plan only allows $ catch-up contributions, then “Amount” should be sent for DeferralFormatCatchUp. Only $ will be displayed for catch-up contribution format in Retirement Manager. - If a plan allows both % or $ catch-up contributions, then “RateOrAmount” should be sent for DeferralFormatCatchUp. The Retirement Manager user interface will display the catch-up contribution format sent in the participant xml in this case. “RateOrAmount” is the default, so if DeferralFormatCatchUp is not sent in the plan xml we will assume the plan allows both % or $ catch-up contribution formats which is our standard logic. Does not apply to the following plan types: TradIRA, RothIRA and NonQualVA. Please note, both rate and amount will be sent back in the transaction regardless of this setting. | |
| FundEffectiveDate | PlanDefinition/PlanUpdate | N/A | Indicates the date at which a client would like a new plan lineup to be live. | Date Numeric | 2015-12-06 | Optional | N | Plan Identifiers and Global Data Elements: | Format is YYYY-MM-DD This feature should be used when a client has changes to a plan lineup (fund changes) and does not want any user interruption to their services. If a plan contains an effective date greater than or equal to the current date +1, RM will override any existing plan with a future fund effective date. If a plan contains an effective date less than or equal to the current date, this will be implemented as the new current lineup (standard processing and implementation time will apply). The Fund Effective Date flag can be applied to all service options (Managed Accounts, Advice and Guidance). | ||
| PrimaryPlanID | PlanDefinition/PlanUpdate | N/A | Identifier used to distinguish all sub plans associated with the same master plan. | String | Plan-0010 | Optional | N | Plan Identifiers and Global Data Elements: | This should be the planID for the master plan used to tie together sub plans. 50 characters is the maximum length for this field. | ||
| Address1 | PlanDefinition/PlanUpdate/Address | ADDRESS1 | Provider, Plan, or TPA Address Line 1 | String Alphanumeric | 123 Main Street | Required only for Managed Accounts | Y (displayed in Proposal and Progress Report) | Plan Identifiers and Global Data Elements: | A return address is required for the Proposal and the Progress Report. Provider, plan, or TPA level values may be sent in these address fields. This field does not need to be sent in the plan batch file if we have a return address set up at the client level and it can be configured to pull from either the plan or client level for non-integrated advice following the logic below. For non-integrated advice: If configured to pull from the plan level - The return address shown on the reports will be the address sent in these fields. If address is not sent in the plan XML file, the address we have set up at the client-level will be displayed. If we have more than one address, we will determine which one to display using the following hierarchy: 1 –address sent in plan batch file, 2- address set up at client-level. So, for example, if we have an address from both sources, the address sent in the plan batch file will override the client-level address. If configured to pull from the client level – The return address shown on the reports will always be the address we have set up at the client level. For integrated advice: The return address will always be pulled from the client-level regardless of the configuration setting above. - Only addresses in the United States, Puerto Rico, Guam, the US Virgin Islands, the District of Columbia, American Samoa and the Federated States of Micronesia are allowed. We also accept Military postal abbreviations. - 100 characters is the maximum character length for this field. | ||
| Address2 | PlanDefinition/PlanUpdate/Address | ADDRESS2 | Provider, Plan, or TPA Address Line 2 | String Alphanumeric | Floor 4 | Optional | Y (displayed in Proposal and Progress Report) | Plan Identifiers and Global Data Elements: | See ADDRESS1 Limit of 50 characters | ||
| Address3 | PlanDefinition/PlanUpdate/Address | ADDRESS3 | Provider, Plan, or TPA Address Line 3 | String Alphanumeric | Suite 404 | Optional | Y (displayed in Proposal and Progress Report) | Plan Identifiers and Global Data Elements: | See ADDRESS1 Limit of 50 characters | ||
| City | PlanDefinition/PlanUpdate/Address | CITY | Provider, Plan, or TPA City | String Alphanumeric | Chicago | Required only for Managed Accounts | Y (displayed in Proposal and Progress Report) | Plan Identifiers and Global Data Elements: | See ADDRESS1 Limit of 50 characters | ||
| State | PlanDefinition/PlanUpdate/Address | STATE | Provider, Plan, or TPA State | String Alphanumeric | IL | Required only for Managed Accounts | Y (displayed in Proposal and Progress Report) | Plan Identifiers and Global Data Elements: | See ADDRESS1 | ||
| Zip | PlanDefinition/PlanUpdate/Address | ZIP | Provider, Plan, or TPA Zip Code | String Alphanumeric | 60606-1234 | Required only for Managed Accounts | Y (displayed in Proposal and Progress Report) | Plan Identifiers and Global Data Elements: | See ADDRESS1 | ||
| WebURL | PlanDefinition/PlanUpdate | WEB | Provider, Plan, or TPA Website Address (URL) | String Alphanumeric | www.planprovider.com | Required only for Managed Accounts | Y (displayed in Proposal and Progress Report) | Plan Identifiers and Global Data Elements: | This element is used for the Proposal and the Progress Report. For the Proposal and Progress Report, either a web address (URL) or a phone number is required to display as contact information for participants receiving these reports. Provider, plan, or TPA level values may be sent in the WebURL field. However, this field does not need to be sent in the plan batch file if we have a web address set up at the client-level and it can be configured to pull from either the plan or client level for non-integrated advice following the logic below For non-integrated advice: If configured to pull from the plan level - The web address shown on the reports will be the web address sent in this field, or the web address we have set up at the client-level. If we have more than one web address, we will determine which one to display using the following hierarchy: 1 –web address sent in plan batch file, 2- web address set up at client-level. So, for example, if we have a web address from both sources, the one sent in the plan batch file will override the client-level web address. If configured to pull from the client level – The web address shown on the reports will always be the web address we have set up at the client level. For integrated advice, the web address will always be pulled from the client-level. | ||
| Phone | PlanDefinition/PlanUpdate | PHONE | Provider, Plan, or TPA Phone Number | String Numeric in format xxx-xxx-xxxx | 800-444-4321 | Required only for Managed Accounts | Y (displayed in Proposal and Progress Report) | Plan Identifiers and Global Data Elements: | This element is used for the Proposal and the Progress Report. For the Proposal and Progress Report, either a web address (URL) or a phone number is required to display as contact information for participants receiving these reports. Provider, plan, or TPA level values may be sent in the Phone field. However, this field does not need to be sent in the plan batch file if we have a phone number set up at the client-level and it can be configured to pull from either the plan or client level for non-integrated advice following the logic below. For non-integrated advice: If configured to pull from the plan level - The phone number shown on the reports will be the phone number sent in this field, or the phone number we have set up at the client-level. If we have more than one phone number, we will determine which one to display using the following hierarchy: 1 – phone number sent in plan batch file, 2- phone number set up at client-level. So, for example, if we have a phone number from both sources, the one sent in the plan batch file will override the client-level phone number. If configured to pull from the client level – The phone number shown on the reports will always be the phone numberwe have set up at the client level. For integrated advice, the phone number will always be pulled from the client-level. Please send phone numbers only in the format shown in this example. | ||
| EnableAssetAllocationFund | PlanDefinition/PlanUpdate | N/A | Does the plan use the lifestyle funds solution? | Boolean | Default to client configuration flag | true | Optional | N | Plan Identifiers and Global Data Elements: | This field is used to indicate whether the plan will use the lifestyle funds (also referred to as asset allocation) solution. Funds identified as asset allocation funds in a plan that uses the lifestyle fund solution will not be included in the fund selection or in model portfolios. If a plan uses the lifestyle fund solution, the link to refer participants to those funds will only be displayed for the Managed by You service option, not the Managed by Morningstar service option. Note - if this flag is not sent in the plan XML file, the value in the client configuration file for this flag will be used. If this flag does not exist at the plan level or client level, the default is True. | |
| Discretionary | PlanDefinition/PlanUpdate | DISCRETIONARY | Indicates the plan offers an employer discretionary match | Boolean | false | true/false | Optional | Y | Plan Identifiers and Global Data Elements: | This field is used to indicate whether or not a generic text message should be displayed to the user informing him/her that there is an employer contribution that is discretionary. Used in UI only. | |
| EnableRetail | PlanDefinition/PlanUpdate | N/A | Indicates if the IRA is retail (vs employer sponsored) | Boolean | false | true/false | Optional | Y (The RM5UI verbiage is differet for retail IRAs) | Plan Identifiers and Global Data Elements: | This field is used to indicate whether an IRA is retail or not. When true it means the IRA isr retail and when false it means the IRA is employer sponsored. The wording of the RM5UI will change accordingly (i.e. won't say your "Employer's Plan" if the IRA is retail). TradIRA will also show preTax language on the UI when this field is set to true. | |
| EnableOAGuidance | PlanDefinition/PlanUpdate | Indicates whether the plan allows for asset allocation guidance on outside accounts | Boolean | FALSE | true/false | Optional | N | Plan Identifiers and Global Data Elements: | This field is used to indicate whether the plan will show asset allocation guidance on outside accounts. This flag is also available in the client configuration table. The default for the plan is "false" meaning to not show asset allocation guidance on outside accounts. If the value is set to "true" at the plan level asset allocation guidance will be turned on for outside accounts. | ||
| HasNonCoreFunds | PlanDefinition/PlanUpdate | Indicates if the plan includes non-core funds | Boolean | false | true/false | Optional | N | Plan Identifiers and Global Data Elements: | This field is used to indicate if the plan includes non-core funds. In the UI, if a participant is enrolled in a plan and the HasNonCoreFunds = true, the Cancel Service option is disabled and the participant is instructed to opt-out on the RK side. | ||
| feeIgnoreBit | PlanDefinition/PlanUpdate | Used to ignore fees at either the plan level, client level, or both. | Boolean | FALSE | true/false | Optional | N | Plan Identifiers and Global Data Elements: | This can be used to ignore fees at either the plan level, client level, or both.The various settings of the feeIgnore bit determine what fees are used to calculate the plan.AppliedClientProgramFee data point. | ||
| EnableSpillover | PlanDefinition/PlanUpdates | Indictes if the plan allows for contribution spillover | Boolean | FALSE | true/false | Optional | N | Plan Identifiers and Global Data Elements: | This field is used to indicte whether the plan allows for tax advantaged inside accounts contributions to spillover into the inside post-tax account when the 402g IRS limit is hit. This is for the purposes of modeling and advice. Contributions sent back in the transaction will be what the participant sent to us. | ||
| hasCombinedThreeTier | PlanDefinition/PlanUpdate | Indicates if the plan includes a combined three tier CombinedTaxContri node | Boolean | FALSE | true/false | Optional | N | Plan Identifiers and Global Data Elements: | When hasCombinedThreeTier is set as true in plan file and loaded into Batch, In CaponeNewDev..planInfo table column, hasCombinedThreeTier should be set to 1. Plan loading should be succssful when hasCombinedThreeTier attribute is not sent in plan file. | ||
| ThirdPartyIntegration | PlanDefinition/PlanUpdate | Indicates if the plan supports a ThirdPartyIntegration | Boolean | Optional | N | Plan Identifiers and Global Data Elements: | This is the parent node and used in combination with 'MethodologyProvider' and 'ProviderID' to designate a different Third Party engine is to be called when a participant in the plan with this node enrolls or is rebalanced. This node was implemented to support target date fund product solutions. Plans offering the target date fund product solution offering must provide valid 'ThirdPartyIntegration' node and the two child elements, 'MethodologyProvider' and 'ProviderID' to support successful participant enrollment and rebalance in the target date fund solution. | ||||
| MethodologyProvider | PlanDefinition/PlanUpdate | Indicates if the plan supports a ThirdPartyIntegration | Boolean | Optional | N | Plan Identifiers and Global Data Elements: | This is a child field of the 'ThirdPartyIntegration' parent node and used to support target date fund product solutions. Plans offering the target ate fund product solution must include the 'ThirdPartyIntegration' node, the 'MethodolgyProvider' element and valid 'ProviderID' element. | ||||
| ProviderID | PlanDefinition/PlanUpdate | Indicates if the plan supports a ThirdPartyIntegration | String | PIMCO | Optional | N | Plan Identifiers and Global Data Elements: | This is a child field of the 'ThirdPartyIntegration' parent node and used to support target date fund product solutions. Plans offering the target ate fund product solution must include the 'ThirdPartyIntegration' node, the 'MethodolgyProvider' element and valid 'ProviderID' element. Clients will be given a ProviderID during implementation of the target date fund product solution for the specific asset manager providing the funds in the target date product offeirng. The ProviderID string value is to be used in the plan schema to indicate the asset manager engine is to be called when a participant is enrolled or rebalanced inthe plan. | |||
| AnnuityProvider | PlanDefinition/PlanUpdate | Indicates if the plan is supporting a separate annuity provider | String | Optional | N | Plan Identifiers and Global Data Elements: | This has been added to the plan schema for future use. Any value inserted in this node will be ignored until the product and tech architecture of the solution is finalized. Comments will be updated when there are more details about how the intent of this field and how to use. | ||||
| Fund Lineup and Other Fund-Related Data Elements: Tickers or Cusips or the Internal Ids of Funds in the Plan: | |||||||||||
| TransactionID | PlanDefinition/PlanUpdate/SecList/Sec PlanDefinition/PlanUpdate/AnnuityList/Annuity | N/A in old dtd | Identifier that should be sent back in the transaction. | String Alphanumeric | ABC1234 | Required | N | Fund Lineup and Other Fund-Related Data Elements: Tickers or Cusips or the Internal Ids of Funds in the Plan: | This field will indicate what ID should be sent back for the client for a particular security. If the client wants the ticker back, for example, the ticker will appear here. Any identifier can be sent here. The TransactionID should be unique for each security. A Ticker, Cusip, MorningstarID and/or mapped CusFundID must also be sent for each security. Ticker and/or Cusip must be used for all public funds; MorningstarID or CusFundID must be used for all custom funds or variable annuities. When sent for an annuity, the ID is used to map annuity’s underlying fund to a fund in our database. | ||
| MorningstarID | PlanDefinition/PlanUpdate/SecList/Sec PlanDefinition/PlanUpdate/AnnuityList/Annuity | N/A in old dtd | Internal MorningstarID for variable annuities and custom funds covered | String Alphanumeric – 10 character limit | SPUSA04JPX | Optional | N | Fund Lineup and Other Fund-Related Data Elements: Tickers or Cusips or the Internal Ids of Funds in the Plan: | MorningstarID is an internal Morningstar fund identifier that represents variable annuities or certain client custom funds covered. The MorningstarID values will be mapped in the Morningstar database and provided to the client for use. MorningstarID should not be used for public funds where a Ticker or Cusip is available. See Fund Hierarchy Note for details on evaluating fund identifiers. When sent for an annuity, the ID is used to map annuity’s underlying fund to a fund in our database. | ||
| Cusip | PlanDefinition/PlanUpdate/SecList/Sec PlanDefinition/PlanUpdate/AnnuityList/Annuity | CUSIP | CUSIP of a fund in the plan | String Alphanumeric | 922908108 | Optional | N | Fund Lineup and Other Fund-Related Data Elements: Tickers or Cusips or the Internal Ids of Funds in the Plan: | To identify the investment options offered in the plan, we need an identifier sent in the plan file for each investment option. The field sent does not need to be consistent for all options sent. For example, if a tickerless fund is in the plan, Cusip may be sent for that fund and Ticker for the remaining funds. For public funds, it is required that either Ticker or Cusip must be sent, not CusFundID or MorningstarID. See Fund Hierarchy Note for details on evaluating fund identifiers. When sent for an annuity, the ID is used to map annuity’s underlying fund to a fund in our database. | ||
| Ticker | PlanDefinition/PlanUpdate/SecList/Sec PlanDefinition/PlanUpdate/AnnuityList/Annuity | TICKER | Ticker of a fund in the plan. | String Alphanumeric | FMAGX | Optional | Y | Fund Lineup and Other Fund-Related Data Elements: Tickers or Cusips or the Internal Ids of Funds in the Plan: | To identify the investment options offered in the plan, we need an identifier sent in the plan file for each investment option. The field sent does not need to be consistent for all options sent. For example, if a tickerless fund is in the plan, Cusip may be sent for that fund and Ticker for the remaining funds. For public funds, it is required that either Ticker or Cusip must be sent, not CusFundID or MorningstarID. See Fund Hierarchy Note for details on evaluating fund identifiers. When sent for an annuity, the ID is used to map annuity’s underlying fund to a fund in our database. | ||
| CusFundID | PlanDefinition/PlanUpdate/SecList/Sec PlanDefinition/PlanUpdate/AnnuityList/Annuity | EXTFUNDID | Internal fund ID as identified by plan. | String Alphanumeric (<=40 characters) | ABC1234 | Optional | N | Fund Lineup and Other Fund-Related Data Elements: Tickers or Cusips or the Internal Ids of Funds in the Plan: | This field is required for custom funds or any funds for which no Cusip or Ticker exists. This includes custom funds covered, custom funds not covered, and mapped Money Market, Stable Value, and GiCs. Please note that CusFundIDs for custom funds must also be provided to Morningstar ahead of time so that they can be added to the Morningstar database. This field is required for plans sending users with different fund line-ups by service option. This field will be used to identify funds available for recommendations based on applicable service option. Funds used for Managed Accounts will be sent with an appendix of _MBM. For example, 81116P832_MBM. See sample below. If the fund line up is the same for all service options, an appendix is not needed. We will assume the fund is applicable to all available service options. If there is any difference between the fund line ups, an appendix of _MBM, must be sent to identify funds used for Managed Accounts. CusFundIDs and the mappings they represent must be the same for all plans within a provider. For public funds, only Ticker and/or Cusip should be used, not CusFundID or MorningstarID. For plans sending users with different fund line-ups by service option, the public fund identifier would be sent in the CusFundID field, with an appendix of _MBM for Managed Account funds. Ticker and/or Cusip data elements should NOT be sent for Managed Accounts funds, if utilizing this feature. See Fund Hierarchy Note for details on evaluating fund identifiers. When sent for an annuity, the ID is used to map annuity’s underlying fund to a fund in our database. | ||
| ClosedFundList | PlanDefinition/PlanUpdate/SecList/Sec | N/A | Indicates whether or not the fund should be added to the closed fund list. | Boolean | FALSE | FALSE | N | Fund Lineup and Other Fund-Related Data Elements: Tickers or Cusips or the Internal Ids of Funds in the Plan: | When set to true, the fund will be added to the closed fund list automatically. This eliminates the manual process of alerting operations that a fund should be added to the closed fund list. When set to false, the fund will not be added to the closed fund list and is eligible to be used in portfolio creation. | ||
| FFAFee | PlanDefinition/PlanUpdate/SecList/Sec | N/A | Any fund level specific fee | Decimal Numeric | 15 | Optional | N | Fund Lineup and Other Fund-Related Data Elements: Tickers or Cusips or the Internal Ids of Funds in the Plan: | FFA Fees can be sent as positive values, indicating the fee of the fund, or negative values, indicating a rebate fee for the fund. | ||
| Brokerage and Company Stock: | |||||||||||
| EnableBrkg | PlanDefinition/PlanUpdate | BROKERAGE | Does the plan have a self-directed brokerage account option? | Boolean | See Comments | FALSE | Optional | N | Brokerage and Company Stock: | If no, all displays relevant to self-directed brokerage accounts will be omitted from the interface, even if information is sent for brokerage at the participant level. This does not apply to the Proposal. The default is True for: 401K, Thrift, 403B, Sup403B, 457B, 401A, and NonQual. The default is False for: Profit Sharing, Money Purchase, Traditional IRA, Roth IRA, SEP IRA, SIMPLE IRA, Rollover IRA, Non Qualified VA, TaftHartley. Except for TaftHartley, if a value other than False is sent for these plan types, that value will be overwritten and set to False. | |
| EnableCompanyStock | PlanDefinition/PlanUpdate | STOCKFLAG | Does the plan have company stock? | Boolean | See Comments | TRUE | Optional | N | Brokerage and Company Stock: | If no, all displays relevant to company stock will be omitted from the interface, even if information is sent for company stock at the participant level. This does not apply to the Proposal. The default is True for: 401K, Thrift, Profit Sharing, Money Purchase, 401A, and NonQual. The default is False for: 403b, Supplemental 403b, 457b, Traditional IRA, Roth IRA, SEP IRA, SIMPLE IRA, Rollover IRA, Non Qualified VA and TaftHartley. If a value other than False is sent for these plan types, that value will be overwritten and set to False. | |
| DisableCoStockSellOff | PlanDefinition/PlanUpdate | N/A | Indicates whether to retain all company stock or use standard RM sell off logic | Boolean | FALSE | FALSE | Optional | N | Brokerage and Company Stock: | If this flag is set to true, company stock is retained at the participant level, but taken into account when giving advice. Company stock does not need to be sent over as frozen at the participant level when this is set to True. If this flag is set to false, standard RM sell off logic is used. | |
| ShowUIOptionToSell | PlanDefinition/PlanUpdate | N/A | Indicates whether or not the participant has the option to edit company stock sell off in the UI | Boolean | TRUE | TRUE | Optional | N | Brokerage and Company Stock: | ||
| TransactionID | PlanDefinition/PlanUpdate/CSList/CS | N/A | Identifier that should be sent back in the transaction for company stock. | String Alphanumeric | ABC1234 | Required | N | Brokerage and Company Stock: | This field will indicate what ID should be sent back for the client for a particular company stock. If the client wants the ticker back, for example, the ticker will appear here. Any identifier can be sent here. A Ticker, Cusip or CusFundID must also be sent for each security. The TransactionID should be unique for each security | ||
| Cusip | PlanDefinition/PlanUpdate/CSList/CS | STOCKCUSIP | CUSIP of company stock in the plan | String Alphanumeric | 94949494 | Optional | N | Brokerage and Company Stock: | To identify the investment options offered in the plan, we need an identifier sent in the plan file for each investment option. The field sent does not need to be consistent for all options sent. For example, if a tickerless stock is in the plan, Cusip may be sent for that stock and Ticker for the remaining stocks. See Company Stock Fund Hierarchy Note for details on evaluating company stock identifiers. In the CSList, if an unrecognizable cusip (and no ticker) is sent for a company stock, we will assume that it is a privately held company stock, and will not error out the stock. If the company stock is not recognizable in our database, based on the identifier(s) sent, we will use our default stock style category of 50% small-cap growth/50% small-cap value for that stock in our asset mix x-rays. | ||
| Ticker | PlanDefinition/PlanUpdate/CSList/CS | STOCKTICKER | Ticker of company stock in the plan | String Alphanumeric | MSFT | Optional | N | Brokerage and Company Stock: | To identify the investment options offered in the plan, we need an identifier sent in the plan file for each investment option. The field sent does not need to be consistent for all options sent. For example, if a tickerless stock is in the plan, Cusip may be sent for that stock and Ticker for the remaining stocks. See Company Stock Fund Hierarchy Note for details on evaluating company stock identifiers. In the CSList, if an unrecognizable ticker is sent for a company stock, we will assume that it is a privately held company stock, and will not error out the stock. If the company stock is not recognizable in our database, based on the identifier(s) sent, we will use our default stock style category of 50% small-cap growth/50% small-cap value for that stock in our asset mix x-rays. | ||
| CusFundID | PlanDefinition/PlanUpdate/CSList/CS | N/A in old dtd | Internal company stock ID as identified by plan. | String Alphanumeric (<=40 characters) | ABC1234 | Optional | N | Brokerage and Company Stock: | See Company Stock Fund Hierarchy Note for details on evaluating company stock identifiers. If the company stock is not recognizable in our database, based on the identifier(s) sent, we will use our default stock style category of 50% small-cap growth/50% small-cap value for that stock in our asset mix x-rays. If CusFundID is used for any company stocks within CSList, that particular security cannot also have ticker or cusip. Only CusFundID must be sent. Also, if CusFundID is used for company stock, it should be mapped ahead of time in the client configuration file to CSTK. For plans sending users with different fund line-ups by service option, the list of company stocks sent under the CSList node would apply to all service options available for the plan. Company stock should not be sent with _MBM for Managed Accounts. | ||
| SecurityName | PlanDefinition/PlanUpdate/CSList/CS | N/A in old dtd | Name of the company stock | String Alphanumeric up to 75 characters | Stock name | Stock ABC | Optional | Y | Brokerage and Company Stock: | This will display in place of the stock name in the interface if it is sent. If a plan has more than one company stock that has the same Ticker, Cusip or CusFundID, the SecurityName must also be sent for display purposes. Also, if there is a privately held company stock, the SecurityName should also be sent. | |
| Employer Match Data Elements: | |||||||||||
| EnablePreTaxMatch | PlanDefinition/PlanUpdate | EMPLOYERMATCHFLAG | Does the plan have an employer pre-tax and/or Roth match? | Boolean | See Comments | TRUE | Optional | N | Employer Match Data Elements: | If no, all interface data points relevant to employer contribution are omitted, even if information is sent for pre-tax/ Roth match at the participant level. This includes profit sharing. The default is True for: 401K, Thrift, Profit Sharing, Money Purchase, 403b, 457b, 401a, NonQual, SEP_IRA, TaftHartley and SIMPLE_IRA. For SEP and SIMPLE IRA, the value must be True; if a value other than True is sent, that value will be overwritten and set to True. The default is False for: Supplemental 403b, Traditional IRA, Roth IRA, Rollover IRA and Non Qualified VA. If a value other than False is sent for these plan types, that value will be overwritten and set to False. | |
| EnablePostTaxMatch | PlanDefinition/PlanUpdate | N/A | Does the plan have an employer post-tax match? | Boolean | See Comments | TRUE | Optional | N | Employer Match Data Elements: | If no, all interface data points relevant to employer contribution are omitted, even if information is sent for post tax match at the participant level. The default is True for: 401K, Thrift, 403B, 401A, and NonQual. The default is False for: Profit Sharing, Money Purchase, Supplemental 403b, 457b, Traditional IRA, Roth IRA, Rollover IRA, TaftHartley, SEP IRA, SIMPLE IRA and Non Qualified VA. If a value other than False is sent for these plan types, that value will be overwritten and set to False. | |
| ThreeTier node | PlanDefinition/PlanUpdate/PreTaxContriRules/EmployerMatch or PlanDefinition/PlanUpdate/PostTaxContriRules/EmployerMatch | MATCHTYPE = 1 | Tiered employer match (x% of the first y% of salary contributed) | Node | Optional | N | Employer Match Data Elements: | If ThreeTier is used, then use the following data elements within EmployerMatch/ThreeTier: Tier1/Rate Tier1/Perc Tier2/Rate Tier2/Perc Tier3/Rate Tier3/Perc This field is used with plan types 401K, Thrift, 403B, 457B, 401A, and NonQual. | |||
| EmployerContri | PlanDefinition/PlanUpdate/PreTaxContriRules/EmployerMatch or PlanDefinition/PlanUpdate/PostTaxContriRules/EmployerMatch/ThreeTierPlusEmpContri | This corresponds to the PERCSALARYMATCH field when MATCHTYPE = 2 or 3 | Non-match employer contribution (percentage of employee’s salary) | Decimal Numeric | 4 | Optional | Y | Employer Match Data Elements: | You should always provide employer non-match contribution, if applicable. Match can either be stated at participant or plan level. Any match information provided in the participant-level XML file will override plan-level match information. This element should be stated as a percent of annual salary. This field is currently used with the following plan types: 401K, Thrift, MoneyPurchase, ProfitSharing, 403B, 457B, 401A, and NonQual. Note: Any percent of salary employer contribution for profit sharing and money purchase plans can be sent in this field. | ||
| ThreeTierPlusEmpContri node | PlanDefinition/PlanUpdate/PreTaxContriRules/EmployerMatch or PlanDefinition/PlanUpdate/PostTaxContriRules/EmployerMatch | MATCHTYPE = 3 | Combination of tiered match and non-match employer contribution | Node | Optional | N | Employer Match Data Elements: | If ThreeTierPlusEmpContri is used, then use the following data elements within EmployerMatch/ThreeTierPlusEmpContri: Tier1/Rate Tier1/Perc Tier2/Rate Tier2/Perc Tier3/Rate Tier3/Perc EmployerContri DollarContri This field is used with plan types 401K, Thrift, 403B, 457B, 401A, and NonQual. If no employer match information is provided at either the plan or participant level, this is the default match type displayed in the user interface. | |||
| ThreeTier node | PlanDefinition/PlanUpdate/CombinedTaxContri/EmployerMatch/ThreeTier | MATCHTYPE = 6 | Tiered employer match on pre and post contributions(x% of the first y% of salary contributed) | Node | Optional | N | Employer Match Data Elements: | If ThreeTier is used, then use the following data elements within CombinedTaxContri/EmployerMatch/ThreeTier: Tier1/Rate Tier1/Perc Tier2/Rate Tier2/Perc Tier3/Rate Tier3/Perc This field is used with plan types 401K, Thrift, 403B, and 401A. | |||
| DollarContri | PlanDefinition/PlanUpdate/PreTaxContriRules/EmployerMatch or PlanDefinition/PlanUpdate/PostTaxContriRules/EmployerMatch | This corresponds to the EMPDOLLARMATCH field when MATCHTYPE = 4 | Annual dollar employer contribution | Decimal Numeric | 1000 | Optional | Y | Employer Match Data Elements: | You should always provide employer non-match contribution, if applicable. Match can either be stated at participant or plan level. Any match information provided in the participant-level XML file will override plan-level match information. This element should be stated as an annual dollar amount. This field is currently used with the following plan types: 401K, Thrift, MoneyPurchase, ProfitSharing, 403B, 457B, 401A, NonQual, and SEP_IRA. Note: Any employer contribution dollar amount for profit sharing and money purchase plans can be sent in this field. Note: This field is now available (March 28, 2015) for use in the ThreeTierPlusEmpContri node so that Dollar Contributions can be used in tangent with tiered matching. | ||
| Perc | EmployerMatch/ThreeTier/Tier1 or EmployerMatch/ThreeTierPlusEmpContri/Tier1 or CombinedTaxContri/EmployerMatch/ThreeTier/Tier1 | TMATCH1 | Employer match percent for the first tier of the employer match formula (%) | Decimal Numeric from 0-999 | 100 | Optional | Y | Employer Match Data Elements: | You should always provide employer match information, if applicable. Match can either be stated at participant or plan level. Any match information provided in the participant-level XML file will override plan-level match information. This data element, along with the next 5 data elements, is used to send the match formula for up to three tiers. These data elements will be used in the following format: - Tier1/Perc percent for the first Tier1/Rate percent, then Tier2/Perc percent of next Tier2/Rate percent, and Tier3/Perc percent of next Tier3/Rate percent. - Example of tiered employer match using all fields: 100% of the first 5% of salary contributed; 50% of the next 3%; 50% of next 5%. This field is used with plan types 401K, Thrift, 403B, 457B, 401A, NonQual, SIMPLE_IRA. | ||
| Rate | EmployerMatch/ThreeTier/Tier1 or EmployerMatch/ThreeTierPlusEmpContri/Tier1 or CombinedTaxContri/EmployerMatch/ThreeTier/Tier1 | TRATE1 | Rate for the first tier of the employer match formula (%) | Decimal Numeric from 0-100 | 5 | Optional | Y | Employer Match Data Elements: | See Tier1/Perc | ||
| DollarLimit | EmployerMatch/ThreeTier/Tier1 Or EmployerMatch/ThreeTierPlusEmpContri/Tier1 Or CombinedTaxContri/EmployerMatch/ThreeTier/Tier1 | The dollar value for the first tier of the employer match formula ($). A choice should be made in each tier for DollarLimit or Rate | Decimal Numeric 0-1000 | 250 | Optional | Y | Employer Match Data Elements: | ||||
| Perc | EmployerMatch/ThreeTier/Tier2 or EmployerMatch/ThreeTierPlusEmpContri/Tier2 or CombinedTaxContri/EmployerMatch/ThreeTier/Tier2 | TMATCH2 | Employer match percent for the second tier of the employer match formula (%) | Decimal Numeric from 0-999 | 50 | Optional | Y | Employer Match Data Elements: | See Tier1/Perc Tier2 does not apply to SIMPLE_IRA | ||
| Rate | EmployerMatch/ThreeTier/Tier2 or EmployerMatch/ThreeTierPlusEmpContri/Tier2 or CombinedTaxContri/EmployerMatch/ThreeTier/Tier2 | TRATE2 | Rate for the second tier of the employer match formula (%) | Decimal Numeric from 0-100 | 3 | Optional | Y | Employer Match Data Elements: | See Tier1/Perc Tier2 does not apply to SIMPLE_IRA | ||
| DollarLimit | EmployerMatch/ThreeTier/Tier2 or EmployerMatch/ThreeTierPlusEmpContri/Tier2 or CombinedTaxContri/EmployerMatch/ThreeTier/Tier2 | The dollar value for the second tier of the employer match formula ($). A choice should be made in each tier for DollarLimit or Rate | Decimal Numeric 0-1000 | 250 | Optional | Y | Employer Match Data Elements: | ||||
| Perc | EmployerMatch/ThreeTier/Tier3 or EmployerMatch/ThreeTierPlusEmpContri/Tier3 or CombinedTaxContri/EmployerMatch/ThreeTier/Tier3 | TMATCH3 | Employer match percent for the third tier of the employer match formula (%) | Decimal Numeric from 0-999 | 50 | Optional | Y | Employer Match Data Elements: | See Tier1/Perc Tier3 does not apply to SIMPLE_IRA | ||
| Rate | EmployerMatch/ThreeTier/Tier3 or EmployerMatch/ThreeTierPlusEmpContri/Tier3 Or CombinedTaxContri/EmployerMatch/ThreeTier/Tier3 | TRATE3 | Rate for the third tier of the employer match formula (%) | Decimal Numeric from 0-100 | 5 | Optional | Y | Employer Match Data Elements: | See Tier1/Perc Tier3 does not apply to SIMPLE_IRA | ||
| DollarLimit | EmployerMatch/ThreeTier/Tier3 or EmployerMatch/ThreeTierPlusEmpContri/Tier3 or CombinedTaxContri/EmployerMatch/ThreeTier/Tier3 | The dollar value for the third tier of the employer match formula ($). A choice should be made in each tier for DollarLimit or Rate. | Decimal Numeric 0-1000 | 250 | Optional | Y | Employer Match Data Elements: | ||||
| DollarCap | PlanDefinition/PlanUpdate/PreTaxContriRules/EmployerMatch Or PlanDefinition/PlanUpdate/PostTaxContriRules/EmployerMatch | DOLLARCAP | Displays dollar limit on match ($) | Decimal Numeric | 1500 | Optional | Y | Employer Match Data Elements: | This field should always be sent, if applicable. DollarCap can either be stated at participant or plan level. DollarCap information provided in the participant-level XML file would override plan-level match information. This element is only applicable to pre- and post-tax tiered match types (ThreeTier or ThreeTierPlusEmpContri). This field is currently used with the following plan types: 401K, Thrift, 403B, 457B, 401A, and NonQual. | ||
| CombinedPercLimit | PlanDefinition/PlanUpdate/PreTaxContriRules/EmployerMatch Or PlanDefinition/PlanUpdate/RothContriRules/EmployerMatch Or PlanDefinition/PlanUpdate/PostTaxContriRules/EmployerMatch | The percent (%) of the participant’s salary eligible for employer match rules. This percent includes employer match amounts in all tiers. | Decimal Numeric | 5 | Optional | Y | Employer Match Data Elements: | ||||
| CombDollarCap | PlanDefinition/PlanUpdate | N/A in old dtd | Displays combined dollar limit on pre-tax and post tax match ($) | Decimal Numeric | 2000 | Optional | Y | Employer Match Data Elements: | This field should always be sent, if applicable. CombDollarCap can either be stated at participant or plan level. CombDollarCap information provided in the participant-level XML file would override plan-level match information. This element is only applicable to pre- and post-tax tiered match types (ThreeTier or ThreeTierPlusEmpContri). This field is currently used with the following plan types: 401K, Thrift, 403B, 457B, 401A, and NonQual | ||
| Pre-Tax Contribution, Post-Tax Contribution & Combined Pre/Post-Tax Flags: | |||||||||||
| Rate | PlanDefinition/PlanUpdate/PreTaxContriRules/Default/MaxContri or PlanDefinition/PlanUpdate/CombinedTaxContriRules/PreTaxDefault/Default/MaxContri | MAXCONTRI | Maximum pre-tax and/or Roth employee contribution the plan allo |