IFT DP/PPfA Data Model Requirement for Fund Transfer

482 views April 8, 2021 December 29, 2021 0

PPfA/DPfA

This is a chart of the details that are entered within the PPfA to list what the available selections are for the Asset Rebalancing  feature. The PPfA modelling will match the DTCC as to what ACORD value types are allowed in ACORD driven fields. There are more values allowed within the ACORD structure, but we are unable to support them at this time due to DTCC having a limited code list. An attempt to transmit ACORD values unsupported by the DTCC will cause a transaction to be rejected.

 

Parameters
Parameter  Usage
(R=Required,
O=Optional,
O/C=Optional Conditional)
Data Type Valid Values Description
FeatureCode R String
Name R String
Description R String
SelectionRule R Integer
MaxNumInstances R String
FeatureMappingCode R Integer OLI_LU_OBJECTYPE 89 – Arrangement
ArrType R Integer OLI_LU_ARRTYPE 1 – Transfer
Sequence R String
FeatureConflict

FeatureCode

R String
FeatureOptProduct

 

ProductCode

R String
FeatureOptProduct

 

Name

R String
FeatureOptProduct

 

Description

R String
FeatureOptProduct

 

SaleEffectiveDate

R Date
FeatureOptProduct

 

SaleExpirationDate

R Date
FeatureOptProduct

 

NoNewMoneyDate

R Date
FeatureOptProduct

 

DefaultInd

R Boolean 0 – False

1 – True

FeatureOptProduct

 

RevokableInd

R Boolean 0 – False

1 – True

FeatureOptProduct

 

SignatureRequiredCode

R Integer OLI_LU_SIGNREQUIRED 1 – No Signature Required

2 – Signature is required with Application

3 – Required at Carrier before issue

4 – Electronic Signature

FeatureOptProduct

 

AgeCalculationType

R Integer OLI_LU_AGECALCMETH 1 – Age Next Birthday

2 – Age Last Birthday

3 – Age Nearest in days

4 – Age Nearest by Month/Date

5 – Natural Age is offset by a factor to compensate for gender in a non-sex-distinct mortality table, or to effect a substandard rating

FeatureOptProduct

 

ParticpantBasedon

R Integer OLI_LU_PARTICROLE 1 – Primary Insured

18 – Owner

27 – Annuitant

36 – Both Annuitant and Owner

42 – Owner if Person

FeatureOptProduct

 

MinContractAmt

R String
FeatureOptProduct

 

 

MaxContractAmt

R String
FeatureOptProduct/PaymentModeMethProduct

 

PaymentMode

R Integer OLI_LU_PAYMODE 1 – Annual

2 – Semi-Annual

3 – Quarter or Quarterly

4 – Month or Monthly

5 – Semi-Monthly (twice a month)

6 – Week or Weekly

7 – Be-Weekly (every two weeks)

8 – Day or Daily

9 – Single Payment

15 – Every 2 Months

 

The above values are what are allowed by DTCC, ACORD has more valid values but until they are supported at DTCC we cannot allow them.

 

FeatureOptProduct/PaymentModeMethProduct

 

PaymentModeMethDesc

R String
FeatureOptProduct

 

MaxNumDestinationInvestProd

R String
FeatureOptProduct

 

MaxNumInstances

R String
FeatureOptProduct

 

MinNumSourceInvestments

R String
FeatureOptProduct

 

MinNumDestinationInvestments

R String
FeatureOptProduct

 

Sequence

R String
FeatureOptProduct

 

ArrSubType

R Integer OLI_LU_ARRSUBTYPE 26 – Full Rebalance

27 – Fund Balance Transfer

28 – Percent of Contract Value Transfer

29 – Specified Amount Transfer

FeatureOptProduct/AllocTypeProduct

 

DestTransferAmtType

R Integer OLI_LU_TRNSFRAMTTYPE 3 – Percentage

 

FeatureOptProduct/AllocTypeProduct/

 

MarketingName

R String
FeatureOptProduct/DestInvestProduct

 

CarrierCode

R String
FeatureOptProduct/DestInvestProduct

 

ProductCode

R String
FeatureOptProduct/DestInvestProduct

 

MinAmt

R String
FeatureOptProduct/DestInvestProduct

 

MaxAmt

R String
FeatureOptProduct/DestInvestProduct

 

MinPct

R String
FeatureOptProduct/DestInvestProduct

 

MaxPct

R String
FeatureOptProduct/DateCollection

 

EffDateEntryRule

R Integer OLI_LU_DATECOLLECT 1 – Start Month and Year are Required

2 – Start Month and Year are Optional

7 – Do Not Collect Date

 

FeatureOptProduct/DateCollection

 

EndDateEntryRule

R Integer OLI_LU_DATECOLLECT 5 – Complete Date is required

6 – Complete Date is Optional

7 – Do Not Collect Date

9 – Number of Transfers or Complete Date Required

 

FeatureTransactionProduct PPfA valid fields and expected values

These are the fields needed to add the FeatureTransactionProduct itself to the PPfA for Fund Transfers.

Parameter  Usage
(R=Required,
O=Optional,
O/C=Optional Conditional)
Data Type Valid Values Description
TransAvailableDate R String
TransEndAvailable R String
TransType R Integer OLI_LU_TRANS_TYPE_CODES 102 – Fund Transfer
ArrType R Integer OLI_LU_ARRTYPE 1 – Fund Transfer
FeatureProdcuctInfo

FeatureCode

R String
FeatureProdcuctInfo

TransmissableInd

R Boolean 0 – False

1 – True

FeatureProdcuctInfo/ActionTypeAllowed

ActionTypeAllowed

R Integer OLI_LU_ACTIONTYPE 1 – Initiate/Add

 

FeatureProdcuctInfo/PolicyStatus

PolicyStatus

R Integer OLI_LU_POLSTAT 1 – Active

 

Fund Transfer DPfA Update Details

The DPfA modelling for In Force transactions will not change the product itself. If a Carrier/Distributor has the product on the PPfA/DPfA and Fund Transfer are modelled they will show in that system (adding the Fund Transfer modelling to the existing New Business or Subpay PPfA). The information read in the PPfA will determine what type of transactions are available for the user. You can setup a product and promote the product to allow Fund Transfer only if that is the way you want to proceed with a specific product (if not approved for New Business or Subpays).

<AllowedFeatureTransaction id=”_bff16922-94a2-49dd-9e72-c66bbc8212a8″>
<TransType tc=”102″>Fund Transfer (one time or automatic for investment or policy)</TransType>
</AllowedFeatureTransaction>

This content is restricted to registered users. iPipeline customers can login or register below. Please allow up to 24 hours for your account to be approved.

Was this helpful?