[{TableOfContents }]
!!!DEFINE BENEFIT PLAN
Benefit Plan Types define the major categories of plans for which the organization has specific coverage. Benefit plan types are usually broad categories like 'Health', 'Dental' and 'Life Insurance'.
\\
\\
Benefit Plan Types data is stored in the [P2K_BE_BENEFIT_PLAN_TYPES] and [P2K_BE_BENEFIT_COMPONENTS] tables.
\\
;[Plan Type|PLAN_TYPE_CODE]:This field holds the defined plan type code that uniquely identify the plan type. If the BSS module is being used the Plan Type will be displayed in the [WEBOEE] form. Plan_Type_Code is a mandatory 16-character alphanumeric field. 
;[Sequence|CALCULATION_SEQUENCE]:The Calculation Sequence field determines the order in which this plan type will be processed by payroll. This sequence is also used by the BSS module to determine the order the plan types are displayed to the employee in the election form ([WEBOEE]). If a sequence is not defined, the plan types will display in alphabetical order. Calculation_Sequence is a 5-digit numeric field provided but may be user altered.
;[Recipient Type|RECIPIENT_TYPE]:This field is used by the BSS module only. This can be used to define a recipient type if all of the plans linked to the plan type allow the same type of recipient to be enrolled. If an employee is only allowed to elect themselves in the plan, ‘Not Applicable’ should be used. If the plans allow for different participant types a recipient type can be defined at the coverage level.  The type of recipient defined will filter the list of benefit recipients available to the employee for that plan during the election period. The filtration is done by comparing the recipient type lexicon values to the stored values of the [relation lexicon|X_RELATION] in [IECT]. The system will check for a recipient type at the coverage first, if none are found it will then check the plan type to see if one has been defined at that level. If the system cannot locate a recipient type for either the coverage or plan type, all of the employee’s contacts defined in [IECT] will be listed for the employee to elect. The page [Benefit Recipient Matrix for Open Enrollment|BENEFIT RECIPIENT MATRIX FOR OPEN ENROLLMENT] shows which relation values fall under each of the recipient types. 

;[Plan Type URL |PLAN_TYPE_URL]:A URL can be defined to provide the employees with a link in to external documentation that may provide additional information on each plan within the plan type, or to a carrier’s website.  This will be displayed on the SS election form [WEBOEE] beneath the Election Intro ext.

;[Description|DESCRIPTION]:This is a description of the benefit plan type.  Description is an optional 50-character alphanumeric field provided.
;[Election Intro Text|ELECTION_INTRO_TEXT]:This field is used to include introductory text to the plans in the [WEBOEE] form.  This can be used to provide additional instructions to employees. Basic HTML tags can be used to tailor the look of the text. 

;[ACA Eligible|ACA_ELIGIBLE]:This toggle is set on for the medical plan type that will hold the benefit plans that will be used for ACA minimum coverage purposes.  

;[ACA SI|]:A toggle to identify if the plan meets Minimum Essential Coverage, as defined by the IRS Rules. You would only toggle on a self-only coverage if it meets that criteria. __This toggle is longer used - Self-insured categorization of a benefit plan is now determined SOLELY from the plan definition on [IBPN], the ACA Min. Values Self toggle__

!Benefit Components Usage 
;[BC Code|BC_CODE]:The BC Code is the unique identifier for the benefit component. BC_Code is a mandatory 16-character alphanumeric field provided.
;[Sequence|COMPONENT_SEQUENCE]:Sequence determines the order in which the benefit plan calculation process will process this benefit component. Component_Sequence is a mandatory 5-character numeric field provided.
;[Description|DESCRIPTION]:This field describes the purpose of the benefit component. Description is an optional 50-character alphanumeric field provided but may be user altered.
;[BC Action|BC_ACTION]:BC Action indicates the use of a benefit component. BC_Action is a mandatory fixed lexicon ([X_BC_ACTION]) you may use to look up the value.
;[Field Type|FIELD_TYPE]:This is the type of field for the information returned by the benefits component; valid entries (provided) are Char, Number, Date and Boolean. Field_Type is a mandatory fixed lexicon ([X_FIELD_TYPE]) you may use to look up the value.

!Plan Definitions
;[Plan|PLAN_CODE]:The plan code is a unique user-defined code identifying the plan to the organization. Plan_Code is a mandatory 16-character alphanumeric field you must manually enter.
;[Description|DESCRIPTION]:This is the description of the plan(s) associated with this benefit plan type. Description is an optional 50-character alphanumeric field you may manually enter.
;[Participation|PARTICIPATION_RULE]:The participation rule indicates whether participation in a benefit plan or coverage is mandatory or optional. The participation rule on the plan definition is used as a default entry to the benefit schedule. Only the participation rule from the benefit schedule is enforced. Participation_Rule is an optional fixed lexicon ([X_PARTICIPATION_RULE]).
;[Policy #|POLICY_NUMBER]:This field holds the insurance policy number assigned by the insurance carrier. Policy_Number is an optional 30-character alphanumeric field you may manually enter.
;[Last Remittance Date|LAST_REMIT_DATE]:The Last Remit Date field shows the date this plan was last remitted to the insurance carrier (or reconciled for internal plans). Each time the remittance process is run, this date is updated by the system to reflect the latest date processed. When a user runs remittances for a time period, the system checks there are no missing remittance periods since the last run. Last_Remit_Date is an optional date field that is system updated, but may be user altered.


----
![Notes|Edit:Internal.IBPT] 	
[{InsertPage page='Internal.IBPT' default='Click to create a new notes page'}]