| AccountingStatement Inquiry | OLI_TRANS_INQACCTNG | 225 | To provide the ability to obtain an extract of accounting information | |
| AccountingStatement Transmittal | OLI_TRANS_TRNACCTNG | 1225 | To provide the ability to send an extract of accounting information | |
| Activity Inquiry | OLI_TRANS_INQACT | 217 | Used to return activities to the requester. | |
| Activity Maintenance | OLI_TRANS_CHGACT | 187 | This transaction is used to create, update, or delete Activity information. | |
| Activity Search | OLI_TRANS_SRCACT | 305 | Use specified criteria to query for one or more Activity objects. | |
| Activity Transmittal | OLI_TRANS_TRNACTIVITY | 1217 | The need to "push" an Activity to one or more "Parties". This transaction is needed to push activity information out. This will be used to transmit activity. This is not in response to an inquiry, but rather the distribution of information so that receiver can take any required action that may be needed. | |
| Address Maintenance | OLI_TRANS_CHGADR | 181 | This is a maintenance transaction which allows a user to change an address for either a Party or a Grouping. | |
| Address Standardization Submission | OLI_TRANS_STNDADDR | 209 | This message is used to standardize an address based on the rules of the message
recipient. | |
| Any Authorized or Supported Transaction | OLI_TRANS_ANY | 9999 | Used to indicate when any transaction may be used. In Authorization/AdministrativeTransaction used to indicate all supported transaction may be used. This value is allowed ONLY for AdministrativeTransaction. | |
| Appointment Non-Renewal Report | OLI_TRANS_UPDAPPNOTE | 412 | A report from a carrier or distributor identifying producers for whom they are not renewing appointments See Licensing and Appointment Implementation Guide for additional information. | |
| Appointment Renewal Submission | OLI_TRANS_UPDAPPREN | 411 | A producer's request for renewal of an appointment. See Licensing and Appointment Implementation Guide for additional information. | |
| Appointment Submission | OLI_TRANS_UPDAPPREQ | 410 | A producer's appointment request. See Licensing and Appointment Implementation Guide for additional information. | |
| Appointment Termination | OLI_TRANS_UPDAPTERM | 413 | A producer's request to have their appointment terminated. See Licensing and Appointment Implementation Guide for additional information. | |
| Arrangement Administration | OLI_TRANS_UPDARR | 107 | The purpose of this transaction is to Setup/Update/Delete/Cease/Suspend/Restart an Arrangement (Automatic Scheduled Financial Activity). | |
| Arrangement Inquiry | OLI_TRANS_INQARRANGEMENT | 215 | The purpose of this transaction is for the request and response of Arrangement Information. For this transaction, an arrangement is a recurring scheduled financial event. The arrangement inquiry can be for all arrangement information or for a specific established arrangement. | |
| Attachment (Note) Inquiry | OLI_TRANS_INQATTCH | 239 | Attachment (Note) Inquiry transaction. | |
| Attachment (Note) Submission | OLI_TRANS_UPDATT | 506 | To add an Attachment (note) to a contract. A note may be added to a contract as a result of a client request, an underwriter note. It is not a physical file that is being attached. . An Attachment aggregate with an AttachmentBasicType of 1 - This attachment is text only. Used for comments, notes, etc and the appropriate AttachmentType should be used to communicate the note. | |
| AuditEntry Transmittal | OLI_TRANS_TRNAUDITENTRY | 1250 | | |
| Bank Information Inquiry | OLI_TRANS_INQBANK | 230 | | |
| Billing Extract Transmittal | OLI_TRANS_BILLTRNSMTL | 1801 | To interface between a billing engine and billing processing system. | |
| Billing Information Administration | OLI_TRANS_CHGBIL | 184 | To change billing information on an in force or pending policy. | |
| Billing Information Inquiry | OLI_TRANS_INQBIH | 208 | To request billing information. | |
| BillingStatement Inquiry | OLI_TRANS_INQBIL | 207 | To request a billing statement. | |
| BusinessProcessDef Transmittal | OLI_TRANS_TRNBUSPROCDEF | 1238 | Providing details about a business process and one or more related message services
provided by an organization. Information provided includes details such as: status, ACORD
TransType it is based on, contact information and so forth. | |
| Case Status Inquiry | OLI_TRANS_STANOT | 125 | | |
| Case Status Notification | OLI_TRANS_TRNCAS | 1125 | The transmittal parallel of Case Status Notification Request. This message provides new business or inforce Holding information related to changes in status. | |
| Case Survey Submission | OLI_TRANS_CASESUBMIT | 180 | Used to submit contract information for survey usage such as those produced by LIMRA. | |
| Claim Status Inquiry | OLI_TRANS_CLAIMSTATINQ | 820 | This is a Claim Status Inquiry. It is intended to communicate the status of a claim from the carrier to the agent(s) on a policy. This message is intended to be used as an Inquiry to allow the sender to request a claim status from the carrier, with the expectation of a Response. | |
| Claim Status Notification | OLI_TRANS_TRNCLAIMSTAT | 1820 | This is a Claim Status Notification. It is intended to be used as a Transmittal to provide claim status updates on a policy. No response is required from the receiver of the message. | |
| Client Needs Determination Submission | OLI_TRANS_NEEDSDET | 116 | | |
| CodeList Inquiry | OLI_TRANS_CODELISTINQ | 237 | | |
| Commission Calculation Extract Submission | OLI_TRANS_COMMCALC | 701 | This transaction is used to interface with a commission calculation subsystem (engine) to calculate commissions. Commission events occur that need to determine commission payable. There may be many things that need consideration in the calculation. | |
| CommissionStatement Inquiry | OLI_TRANS_INQCOM | 206 | | |
| CommissionStatement Transmittal | OLI_TRANS_TRNCOM | 1206 | Used to transmit commission information. | |
| Death Inquiry | OLI_TRANS_DEATHINQSVC | 890 | This is a Death Inquiry Service Transaction that is used to do a search on Death Notification services, such as the Social Security Administration's Death Master File (DMF), or other databases or vital record sources to see if a potential match appears for any deceased owners and or insured/annuitants. | |
| Disbursement Transmittal | OLI_TRANS_DISBURSETRNSMTL | 1220 | A common message to disburse payments. | |
| Discrepancy Transmittal | OLI_TRANS_DISCREPANCY | 1112 | This transmittal is used to relay data discrepancies. It is not intended to systematically change the affected data, only to notify interested parties that differences have been detected and may need to be resolved. | |
| DistributionAgreement Inquiry | OLI_TRANS_DISTAGRINQ | 234 | This transaction allows the sender to request that information relating to a specific DistributionAgreement be returned. | |
| DistributionAgreement Search | OLI_TRANS_DISTAGRSEARCH | 311 | Use specified criteria to query for one or more DistributionAgreement objects. | |
| DistributionAgreement Transmittal | OLI_TRANS_TRNDISTAGR | 1234 | Used to transmit details for a Distribution Agreement. The Distribution Agreement is the focus of the message. This message will include all relevant elements related to the distribution agreement. | |
| DistributionAgreement Update | OLI_TRANS_DISTAGRUPDATE | 170 | This transaction allows the sender to request an update of information relating to a specific DistributionAgreement in the receiver's system. | |
| Document Delivery Instructions Submission | OLI_TRANS_NOTIFICATION | 189 | This will set notifications for a party. The associated TransSubType indicates whether it's for the party in general or based on their relationship to a holding. | |
| EMailAddress Maintenance | OLI_TRANS_CHGEMA | 183 | To change one of the email addresses for a party | |
| Endorsement Administration | OLI_TRANS_CHGEND | 504 | Adding, updating, and deleting an endorsement to a contract. Endorsements are added to a contract to reflect a change or to limit claim liability. | |
| Fee and Expense Inquiry | OLI_TRANS_FEEEXPENSEINQ | 241 | Used to request information on Fees and Expenses for a specific PolicyProduct. | |
| Fee and Expense Transmittal | OLI_TRANS_TRNFEEEXPENSE | 1241 | This message provides a method for an insurer to communicate detailed product disclosure and fee information sufficient for receiving systems to support recipient needs for regulatory requirement such as the DOL Fiduciary Ruling. | |
| Financial Activity Administration | OLI_TRANS_CHGFIN | 185 | Used to record various financial activities such as premium or loan payments. | |
| Financial Activity Inquiry | OLI_TRANS_INQFIN | 213 | | |
| Financial Activity Transmittal | OLI_TRANS_TRNFIN | 1213 | This transmittal "pushes" a Financial Activity. | |
| First Notice of Loss Submission | OLI_TRANS_FIRSTNOTICE | 810 | This message provides the Receiver with a notification that the Requestor has been contacted regarding an event that has occurred relating to an insured entity, which may result in a Claim being filed under one or more Holdings. It does not create the Claim, but merely functions as the notification of the possibility of a Claim. Actions that result from the receipt of this notification are expected to vary by product and carrier. | |
| FormInstance Inquiry | OLI_TRANS_FORMINSTANCEINQ | 229 | Used to retrieve detailed FormInstance information. | |
| FormInstance Maintenance | OLI_TRANS_UPDFORMINSTANCE | 510 | Allow for the updating, addition, or deletion of objects and elements within the FormInstance object. | |
| FormInstanceRequest Submission | OLI_TRANS_DOCPREP | 500 | To request copies of a physical document (not just the FormInstance information) | |
| FormInstance Search | OLI_TRANS_FORMINSTANCESEARCH | 310 | Use specified criteria to query for one or more FormInstance objects. | |
| Fund Allocation Change | OLI_TRANS_FA | 101 | This is a Fund Allocation Change for either an investment or a policy. | |
| Fund Transfer Administration | OLI_TRANS_FT | 102 | This is a Fund Transfer that can be one time or automatic and may be used for either an investment or a policy. | |
| General Requirement Order Administration | OLI_TRANS_GENREQ | 121 | This transaction can be used to order one or more requirements. | |
| General Requirement Status/Results Inquiry | OLI_TRANS_GENRES | 122 | This transaction can be used to request the status and results (if available) pertaining to one or more requirements. | |
| General Requirement Status/Result Transmittal | OLI_TRANS_TRNREQRUESULT | 1122 | It is needed to push the status and results (if available) for one or more requirements to the recipient. | |
| General Requirement Status Inquiry | OLI_TRANS_INQREQUIREMENT | 123 | To obtain status for one or more requirements. | |
| General Requirement Status Transmittal | OLI_TRANS_TRNREQ | 1123 | It pushes the status of the requirement out to the recipient. | |
| Generic Data Maintenance | OLI_TRANS_BLKTRN | 191 | The purpose of this transaction is to provide a generic mechanism to allow the sender to request that OLifE data be added, updated, or deleted by the receiver. The "DataRep" attribute of the OLifE aggregates is used to indicate which action is to be taken for each entity within the transaction. It was envisioned that this transaction would be utilized in applications such as database synchronization, although its scope is not limited to that. The specific context in which this transaction will be used must be predetermined by the trading partners that deploy it. | |
| Group Enrollment Submission | OLI_TRANS_EMPLOY | 130 | The purpose is to submit employee enrollment data to a carrier. The stream may contain one or more employees' enrollment data. | |
| Grouping Inquiry | OLI_TRANST_INQGRP | 205 | Used to inquire and receive detailed Grouping information. | |
| Grouping Search | OLI_TRANS_SRCGRP | 306 | Use specified criteria to query for one or more Grouping objects. | |
| Grouping Transmittal | OLI_TRANST_TRNGRP | 1205 | Used to transmit detailed grouping information. | |
| Holding Change | OLI_TRANS_CHGHLD | 502 | This transaction is used to correct data that was entered erroneously or to make changes to data for miscellaneous reasons. It provides a generalized method of changing data between systems, typically within an insurer carrier system(s). | |
| Holding Inquiry | OLI_TRANS_INQHLD | 203 | | |
| Holding Product Inquiry | OLI_TRANS_HOLDPRODINQ | 233 | Holding Product Inquiry supports the retrieval of detailed Product Information such as that returned in a PolicyProduct Inquiry or an InvestProduct Inquiry, but identifies the information by its relationship to a particular Holding. This Transaction differs from the existing Product Inquiry transactions in that it allows the request to contain Holding information, and it will use that information to identify and return the detailed Product information. | |
| Holding Search | OLI_TRANS_SRCHLD | 302 | Use specified criteria to query for one or more Holding objects. | |
| Holding Status Change | OLI_TRANS_CHGSTA | 505 | This transaction is used to update Policy status information. This transaction is used for changing the status of a contract. A New Business Contract status change can be an underwriter giving approval to issue the contract, or indicating that they are finished with reviewing the case and it is sent to another area of the New Business department for additional processing. As a result of the underwriter approval or the receipt of all "pending" requirements additional system processing may be generated. | |
| Holding Transmittal | OLI_TRANS_TRNHLD | 1203 | This transaction pushes the holding information out. Used for policy downloads. | |
| Illustration Submission | OLI_TRANS_ILLCAL | 111 | | |
| InvestProduct Inquiry | OLI_TRANS_INQINP | 202 | Used to request detailed product information for an investment product. | |
| InvestProduct Search | OLI_TRANS_SRCINP | 303 | Use specified criteria to query for one or more InvestProduct objects. | |
| InvestProduct Transmittal | OLI_TRANS_TRNINVPRD | 1202 | This transaction is used to transmit invest product information. This is not in response to an inquiry but rather a distribution of information so that receiver can update stored investment product information. | |
| InvestProduct Update | OLI_TRANS_CHGINP | 108 | Change an investment product | |
| Invoice Administration | OLI_TRANS_INVOICESUBMIT | 118 | | |
| Invoice Status Transmittal | OLI_TRANS_TRNINVOICESTATUS | 1119 | Used to transmit the status of an invoice. | |
| License Submission | OLI_TRANS_LICENSEREQ | 129 | License Request - New - is used to initiate a license request where the insurance carrier does not know the producer, and the insurance carrier is the sponsoring carrier, where applicable. This request includes information to perform a license request. This transaction also assumes a status update as a response transaction. | |
| Licensing Inquiry | OLI_TRANS_INQLIC | 211 | Used to return licensing information for a party that is a producer. | |
| Life Reinsurance Activity Reporting Transaction (LREACT) | OLI_TRANS_LREACT | 551 | | |
| Life Reinsurance Facultative Transaction | OLI_TRANS_LREFAC | 552 | | |
| Loan Processing Submission | OLI_TRANS_LOANPROC | 509 | | |
| MIB Follow-up | OLI_TRANS_MIBFOL | 403 | | |
| MIB Follow-up Request | OLI_TRANS_MIBFOLREQ | 404 | This transaction is to be used to request and receive any Follow-up data MIB is holding relative to a specific MIB Service. | |
| MIB Inquiry | OLI_TRANS_MIBINQ | 401 | To request information from any supported MIB transactional database service. | |
| MIB Update | OLI_TRANS_MIBUPT | 402 | To provide updates to any supported MIB transactional database services. | |
| New Business Policy Number Submission | OLI_TRANS_NBPOLNUM | 106 | For systems that may not use a tracking ID to process a New Business application and that require a policy number be defined in the New Business application, this message can be used to acquire the policy number. | |
| New Business Submission | OLI_TRANS_NBSUB | 103 | New Business Submission for a policy | |
| Obtain Results Inquiry | OLI_TRANS_OBTAINRESULT | 192 | Used in an architectural environment that supports a pending response and a subsequent completed response that must be obtained through a separate request. | |
| Other | OLI_OTHER | 2147483647 | | |
| Paramed Report Order Submission | OLI_TRANS_PARORD | 104 | Paramed Report Order Request | |
| Paramed Requirements Results Inquiry | OLI_TRANS_PARNOT | 124 | | |
| Paramed Requirements Results Transmittal | OLI_TRANS_TRNPARAMED | 1124 | | |
| Party Inquiry | OLI_TRANS_INQPAR | 204 | | |
| Party Maintenance | OLI_TRANS_CHGPAR | 186 | This transaction is used to update Party information. It can also be used to delete a Party from a holding or add a new Party to a subsystem. Any object that is a child of Party, such as Address, Email Address, Person may be included in this request. There are granular transactions or TransSubType's to do the same things as can be done with this general transaction. | |
| Party Search | OLI_TRANS_SRCPAR | 301 | Use specified criteria to query for one or more Party objects. | |
| Party Transmittal | OLI_TRANS_TRNPARTY | 1204 | Used to transmit detailed party information. For example, used for a client list download or transmitting Distributor Party detail. | |
| Payment Submission | OLI_TRANS_PAYMNT | 508 | This transaction is for the purpose of applying, reversing, refunding the various types of payments and loan repayments, or to request these functions. This transaction is applicable to all product lines. The Arrangement type or Financial Activity type is used to identify the type of payment that is being requested. The use of Financial Activity or Arrangement is determined by their definition. | |
| Pharmaceutical Profile Inquiry | OLI_TRANS_PHARMP | 601 | | |
| Pharmaceutical Profile Transmittal | OLI_TRANS_TRNPHARM | 1601 | Used to transmit pharmaceutical information. | |
| Phone Maintenance | OLI_TRANS_CHGPHN | 182 | To change one of the phone numbers for a party | |
| Policy Administration | OLI_TRANS_POLICYADMIN | 113 | A basic transaction enabling active policy changes on both the policy itself as well as participants on a contract. It also provides a method for attaching requisite paperwork (forms) that may be required to accomplish change requests. This is a general message for light/mid-weight changes to a policy (basic field policy admin). For more complicated and robust activities, such as complex arrangement administration, other existing or future messages may be more appropriate. | |
| Policy Administration Inquiry | OLI_TRANS_POLADMININQ | 115 | An inquiry transaction to obtain the policy information needed specifically to perform basic policy administration activities. | |
| Policy Administration Transmittal | OLI_TRANS_POLADMINTRN | 1115 | A transmittal transaction to provide the policy information needed specifically to perform basic policy administration activities. | |
| Policy Application Notification | OLI_TRANS_APPNOT | 1114 | Used to notify the recipient that an application has been received. | |
| PolicyProduct Inquiry | OLI_TRANS_INQPRP | 201 | Used to request an inquiry for specific detailed product information for a policy product. | |
| PolicyProduct Search | OLI_TRANS_SRCPRP | 304 | Use specified criteria to query for one or more PolicyProduct objects. | |
| PolicyProduct Transmittal | OLI_TRANS_TRNPOLPRD | 1201 | Provides a means for sharing Product detail and rules. | |
| PolicyStatement Inquiry | OLI_TRANS_HOLDINGSTMTINQ | 235 | | |
| PolicyStatement Transmittal | OLI_TRANS_HOLDINGSTMTTRNS | 1235 | This transaction is used to send a statement for a holding that is based on the FinancialStatement section of the model. | |
| Poll for Notifications Inquiry | OLI_TRANS_INQNOT | 210 | The purpose of this transaction is to poll the carrier for any outstanding notifications | |
| Populate Form Submission | OLI_TRANS_POPFORM | 117 | This transaction provides Holding and related modeled data and requests that one or more forms be completed using that data. The desired forms are specified via a Relation object with RelationRoleCode set to OLI_REL_POPFORM. | |
| Producer (Re) Assignment Submission | OLI_TRANS_AGENTREASSGNMT | 161 | This transaction will support the assignment or reassignment of an agent or servicing representative (Producer) to a particular holding. | |
| Producer Inquiry | OLI_TRANS_PRODINQ | 228 | | |
| Producer Transmittal | OLI_TRANS_TRNPRODINQ | 1228 | This transaction provides a method of transmitting a variety of Producer inquiry messages. It is the transmittal (or "push") version of the 228 Producer Inquiry transaction. Similar to the 228 Producer Inquiry transaction, the 1228 Producer Transmittal transaction can be used to send different types of producer data. The 1228 Producer Transmittal transaction uses a subset of the TransSubType values used in the 228 Producer Inquiry transaction as not all the 228 Producer Inquiry TransSubType values lend themselves to a transmittal type transaction. | |
| PVT_CSC Financial Statement Request | OLI_TRANS_FINSTMTREQ | 226 | This transaction does not appear in the TXLife Specification Guide and therefore is an undocumented part of the standard. Consistent implementation of this transaction is unlikely without TXLife documentation. It is expected that the original submitter (WG or member) will be adding TXLife documentation in a forthcoming MR. | |
| PVT_WG Appointment Inquiry (Status) | OLI_TRANS_INQAPP | 223 | This transaction does not appear in the TXLife Specification Guide and therefore is an undocumented part of the standard. Consistent implementation of this transaction is unlikely without TXLife documentation. It is expected that the original submitter (WG or member) will be adding TXLife documentation in a forthcoming MR. | |
| PVT_WG Appointment Status Transmittal | OLI_TRANS_TRNAPP | 1223 | This transaction does not appear in the TXLife Specification Guide and therefore is an
undocumented part of the standard. Consistent implementation of this transaction is
unlikely without TXLife documentation. It is expected that the original submitter (WG or
member) will be adding TXLife documentation in a forthcoming MR.Last update: 2003-06-03 Last update version: 2.7.92 Last update MR: 02-2.01.LA1 | |
| PVT_WG Pre-arranged Non-Financial Transactions | OLI_TRANS_PREARRNONFIN | 561 | This transaction does not appear in the TXLife Specification Guide and therefore is an undocumented part of the standard. Consistent implementation of this transaction is unlikely without TXLife documentation. It is expected that the original submitter (WG or member) will be adding TXLife documentation in a forthcoming MR. | |
| PVT_WG Replacement Processing Inquiry | OLI_TRANS_INQREPLACE | 128 | This transaction does not appear in the TXLife Specification Guide and therefore is an undocumented part of the standard. Consistent implementation of this transaction is unlikely without TXLife documentation. It is expected that the original submitter (WG or member) will be adding TXLife documentation in a forthcoming MR. | |
| PVT 05 | OLI_TRANS_INQPVT05 | 218 | | |
| Pvt CSC | OLI_TRANS_CHGMSC | 501 | | |
| Pvt CSC | OLI_TRANS_CSC507 | 507 | | |
| PVT CSC New Business Changes | OLI_TRANS_XXXXXX | 109 | | |
| PVT Inforce Search of Archived Document | OLI_TRANS_SRCARCDOC | 309 | | |
| PVT Inforce WG Inquiry for Archived Document | OLI_TRANS_INQARCDOC | 222 | | |
| PVT INFORCE WG Search for Available Reports | OLI_TRANS_INQDOC | 219 | | |
| Replacement Processing Status Transmittal | OLI_TRANS_TRNREPLACE | 1128 | This would be sent by the Delivering Carrier to the Receiving Carrier anytime the status
on a Replacement is updated | |
| Replacement Processing Submission | OLI_TRANS_REPPRO | 127 | | |
| Replacement Status Inquiry | OLI_TRANS_REPNOT | 126 | | |
| Requirements Inquiry | OLI_TRANS_INQREQ | 216 | The 216 Requirements Inquiry is a transaction that will return to the end user detailed information regarding a requirement or requirements for a specific contract that reside on a new business administration type system based off a request made. This TXLifeRequest can request Requirements by a Requirement Code (ReqCode), Requirement Status (ReqStatus), RequestedDate. | |
| SecurityCredential Maintenance | OLI_TRANS_SECCREDMAINT | 520 | | |
| Settlement Submission | OLI_TRANS_FINSET | 140 | Provide for financial settlements between trading partners | |
| SystemMessage Inquiry | OLI_TRANS_INQMSG | 214 | Used to receive detailed System Message information. | |
| SystemMessage Maintenance | OLI_TRANS_CHGMSG | 188 | This transaction is used to update or delete System Message information. | |
| SystemMessage Transmittal | OLI_TRANS_TRNSYSMSG | 1214 | The purpose of this transaction is to serve as the transmittal version of the existing 214 (System Message Inquiry) transaction and transmit System Messages. | |
| System Status Inquiry | OLI_TRANS_SYSTEMSTATUS | 227 | Use this transaction to check for operation of the transaction processor in a B2B environment. | |
| Tabular Data Inquiry | OLI_TRANS_INQTBL | 221 | Given a unique tabular data (XTbML) identifier, the message returns the detailed table data. This transaction will allow organizations to automate the acquisition of up-to-date tabular data from the authoritative source of that information. | |
| Tabular Data Search | OLI_TRANS_SRCTBL | 321 | Use specified criteria to query for one or more XTbML objects. | |
| Tabular Data Transmittal | OLI_TRANS_TRNTBL | 1221 | Transmits ("pushes") a single tabular data (XTbML) file to the receiver of the message. This transaction will allow organizations that are the authoritative source of tabular data to automate the distribution of that information to clients that have a need or desire to use the data. | |
| Underwriting Action Administration | OLI_TRANS_UNDACT | 151 | This transaction is used to update Policy Information as a result of underwriting action. For example, a substandard rating can be added to a coverage, LifeParticipant, CovOption (supplemental benefits). | |
| UnderwritingGuidelines Inquiry | OLI_TRANS_INQUNDGDLNS | 240 | Used to request an inquiry for specific detailed information for underwriting guidelines constructs. | |
| UnderwritingGuidelines Transmittal | OLI_TRANS_TRNUNDGDLNS | 1240 | This transaction will allow a Carrier to publish Underwriting Guidelines to assist agents in appropriately placing clients in the correct underwriting class. | |
| Underwriting Risk Denial | OLI_TRANS_DECRSK | 503 | This transaction is used to deny a specific coverage, supplemental benefit or all coverages on a specified person. This is commonly referred to as "Declining Risk". | |
| Undocumented DeliveryInfo Transaction | OLI_TRANS_DELIVERY | 110 | This will set document delivery instructions for a party. The associated TransSubType indicates whether it's for the party in general or based on their relationship to a holding. | |
| Values Inquiry | OLI_TRANS_INQVAL | 212 | When used in conjunction with TransSubTypeCode 21207 (OLI_TRANSSUB_POSITIONS), it can be
used to implement a "positions inquiry" message. | |
| Values Transmittal | OLI_TRANS_TRNVAL | 1212 | This is the "push" version of the "Values Inquiry" message. | |
| Withdrawal Submission | OLI_TRANS_WITHDR | 105 | Used to withdraw money from a holding. Used only for one-time withdrawals. Recurring withdrawals are supported via Arrangement Administration (107). | |