BankInfo
objectBank name
ABA number
Account Number
TaxInformation
objectCurrent Contribution Amount
Prior Contribution Amount
tax year
Total Cost basis amount
Pre Tefra basis amount
Post Teefra basis amount
Post 88 Amount
Payout
objectApplication
objecte-App submitted date to Zinnia (with pattern “yyyy-mm-dd”).
Match pattern:([0-9]{4})-([0-9]{2})-([0-9]{2})
Example:2023-12-19
Zinnia Unique idenitifer for a case. [Derived by Zinnia]
Example:1234567
Zinnia Identifier for a client.[Derived by Zinnia]
Example:ZIN_ABC
Zinnia Unique Identifier for a case.[Derived by Zinnia]. This is not required for Paper Apps , only eApps.
Example:0ca10708-4b53-464c-b745-355c8f6f0edb
Zinnia Unique Identifier for a case.[Derived by Zinnia]. This is required for Paper Apps, not eApps and will be sent via Orion Application.
Example:CA0123456789
An identifer that represents Transmitting Company which is of 4 char.
Example:1234
Transmitting Company Name
Example:ABC
Receiving Company Name, Derived by Zinnia based on the set up in Zinnia Systems.
Example:ABC
The NSCC assigned membership ID for the firm initiating the transactions.Only applicable for DTCC cases.
Example:0075
Name of the Submitter (Settling Firm).Only applicable for DTCC cases.
Example:LPL
Identifier assigned by a clearing firm/service provider to a firm that clears business through them.Only applicable for DTCC cases.
Example:0075
Name of associated firm.Only applicable for DTCC cases.
Example:LPL
External ID in MCS [Zinnia Commission System] that belongs to the Firm. firmExternalId or firmTaxId or firmNPN is mandatory.
Example:Q01530
9 digit Tax ID in MCS [Zinnia Commission System] that belongs to the Firm. firmExternalId or firmTaxId or firmNPN is mandatory.
Match pattern:\d{9}
>= 9 characters<= 9 characters
Example:123456789
NPN in MCS [Zinnia Commission System] that belongs to the Firm. firmExternalId or firmTaxId or firmNPN is mandatory.
Example:294128
Agent submit date (with pattern “yyyy-mm-dd”).
Match pattern:([0-9]{4})-([0-9]{2})-([0-9]{2})
Example:2023-12-19
Application Signed County, Only for Florida if required by Business Processing System for running rules.
Example:Dade
Product code assigned by Zinnia Admin system
Example:111
Application Signed Date (with pattern “yyyy-mm-dd”).
Match pattern:([0-9]{4})-([0-9]{2})-([0-9]{2})
Example:2023-12-19
Client Agreement Date/Issue Date (with pattern “yyyy-mm-dd”).
Match pattern:([0-9]{4})-([0-9]{2})-([0-9]{2})
Example:2023-12-19
The date in which the Agent first proposes to the client the use of an insurance product, which may or may not be in response to an engagement/planning process. (with pattern “yyyy-mm-dd”).
Match pattern:([0-9]{4})-([0-9]{2})-([0-9]{2})
Example:2023-12-19
The start (run) date of the illustration or quote (with pattern “yyyy-mm-dd”).
Match pattern:([0-9]{4})-([0-9]{2})-([0-9]{2})
Example:2023-12-19
The ID for the illustration or quote.
Example:12345
This date represents when the natural owner electronically signed the application and any supporting documentation. (with pattern “yyyy-mm-dd”).
Match pattern:([0-9]{4})-([0-9]{2})-([0-9]{2})
Example:2023-12-19
This date represents when the joint owner electronically signed the application and any supporting documentation. (with pattern “yyyy-mm-dd”).
Match pattern:([0-9]{4})-([0-9]{2})-([0-9]{2})
Example:2023-12-19
This date represents when the Annuitant electronically signed the application and any supporting documentation. (with pattern “yyyy-mm-dd”).
Match pattern:([0-9]{4})-([0-9]{2})-([0-9]{2})
Example:2023-12-19
This date represents when the joint Annuitant electronically signed the application and any supporting documentation. (with pattern “yyyy-mm-dd”).
Match pattern:([0-9]{4})-([0-9]{2})-([0-9]{2})
Example:2023-12-19
This date represents when the trustee/representative electronically signed the application and any supporting documentation. (with pattern “yyyy-mm-dd”).
Match pattern:([0-9]{4})-([0-9]{2})-([0-9]{2})
Example:2023-12-19
This date represents when the Beneficiary electronically signed the application and any supporting documentation. (with pattern “yyyy-mm-dd”).
Match pattern:([0-9]{4})-([0-9]{2})-([0-9]{2})
Example:2023-12-19
This date represents when the Spouse electronically signed the application and any supporting documentation. (with pattern “yyyy-mm-dd”).
Match pattern:([0-9]{4})-([0-9]{2})-([0-9]{2})
Example:2023-12-19
Stores the IGO date. It is mandatory when contract have trust Date (with pattern “yyyy-mm-dd”).
Match pattern:([0-9]{4})-([0-9]{2})-([0-9]{2})
Example:2023-12-19
Unique Identifier against an e-App application. First 4 letters represent the receiving company, next 3 letters represent the firm, next 8 positions represent the date eApp is submitted, next 10 positions represents the sequential number of the eApps from the eApp instance.
>= 25 characters
Example:XXXXEDJ041120240000000001
Version for that case - 3 digits, incremental if same case if submitted more than once in case of errors.
Example:000
Unique number of the policy.
Example:000
Contract State. State code
Allowed values:AAAEAKALAPARAZCACOCTDCDEFLGAHIIAIDILINKSKYLAMAMDMEMIMNMOMSMTNCNDNENHNJNMNVNYOHOKORPARISCSDTNTXUTVAVTWAWIWVWY
Example:NJ
Solicitation State. State code
Allowed values:AAAEAKALAPARAZCACOCTDCDEFLGAHIIAIDILINKSKYLAMAMDMEMIMNMOMSMTNCNDNENHNJNMNVNYOHOKORPARISCSDTNTXUTVAVTWAWIWVWY
Example:NJ
Qualification Codes
Allowed values:IRAREGIRASPSLIRAROLLNONQUALROTHIRAIRASIMPLE403B401K401A457BPENPLNHR10KEOGHINHERITIRANONQUALSTRPLNINHERITROTHIRA401GROTH401KROTH403BEDUIRAPROFSHRPLNMONEYPURCHPENSPLNTARGTBENFTPLNCUSTIRACUSTROTHIRACUSTROLLIRAQUALIFIED401SCHEDA412EROTHIRACONVCORPDEFERCOMPCORPPENSCUSTINHERITIRACUSTINHERITROTHIRACUSTSARSEPIRACUSTSIMPLEIRACUSTSPOUSALIRACUSTIRASEPCUSTQLACIRADEFAULTGROUPTSAIRASEPNON457DEFCOMPIRAQLACUGMAUTMAVULNQ
Example:IRAREG
Describes whether the case is custodial or not
Allowed values:YESNO
Example:YES
To determine whether the request is via eApp or Paper App
Allowed values:ELECTPAPER
Example:ELECT
To determine whether the Suitability request is via eApp or Paper App. Select NA if Suitability is not being done via Zinnia.
Allowed values:NAELECTPAPER
Example:ELECT
To determine whether the OFAC request is being sent electronically to Zinnia. Select NO if OFAC is not being done via Zinnia electronically.
Allowed values:NOYES
Example:YES
Commission Options will be provided by Zinnia for the respective Product
Example:A
Brokerage Identification Number
Example:ABC0DF
Tele privileges value
Allowed values:NONEALLEXCONLYQTONLYOWNONLYAGTONLYDIARYNT
Example:NONE
signatureMethod
Allowed values:NONEVOICESIGNPADWETSIGBIOCLICKTHRU
Example:NONE
documentControlNumber is an NSCC data point, Will be derived by Zinnia.
Example:1000ABC00000000000
totalAttachmentCount expected in Attachment payload
Example:1
Time when the case is received within ETP
Example:2025-06-26T00:00:00.000Z
Show Child Parameters
Show Child Parameters
funds that sums upto 100%
>= 1 items
Show Child Parameters
feature for any feature/rider selected by user
>= 0 items
Show Child Parameters
roles that sums every role option to 100%
>= 1 items
Show Child Parameters
specialPrograms if any recurring transaction needs to be set up
>= 0 items
Show Child Parameters
payouts if it needs to be set up for the policy
Show Child Parameters
Derived by Zinnia
Example:Error 1
PolicyValues
objectFed marital status
Allowed values:DEFSNGLMRRDHOHQUALWIDOWWITHDEPCHILDDOMESTICPARTNERDIVORCED
Example:MRRD
State marital status
Allowed values:DEFSNGLMRRDHOHQUALWIDOWWITHDEPCHILDDOMESTICPARTNERDIVORCED
Example:MRRD
Show Child Parameters
Contribution type
Allowed values:NAEMPVOLEMPDISC
Example:EMPVOL