SuspenseScreen

Description

This business rule is used to create and control suspense records. Suspense records are used to track money. This business rule identifies where the money came from and allows for the money to be used as payment to various polices. A suspense record is used as a holding account until the money is applied or refunded. A unique suspense number is generated with the suspense record for identification purposes.

Additional Information: Suspense records are written to the suspense account(s) for the company's general ledger. These records temporarily hold transactions until an activity generates a process to disperse or apply the money. Once the respective activities are processed, the company's actual general ledger is updated. These transactions are specific to the inbound and outbound tracking of pieces of money received and disbursed by the insurance company.

For example, a customer may submit payments such as initial or additional premiums, service charges, etc., to the insurance company, along with the completed application. Within OIPA, processing activities like InitialPremium, AdditionalPayment would apply the money from the suspense account to the respective accounts. Similarly, processing activities like FreeLook -> Disbursement are used to disburse the money back to the customer from the suspense account.

SuspenseScreen Element/Attribute Table
Element/Tag Definition

Attribute

Element/Attribute Value and Description

<SuspenseScreen>

The opening and closing tag for the business rule.

 

 

<Fields>

Required Element:

Allows configuration of dynamic fields. See Fields Element.

 

 

<FixedFields>

Repeatable element:

Allows configuration of 'above the line' fields. See Fields Element.

String: The fields must correspond to a column in the AsAddressField database table.

<MultiFields>

Optional element;

Allows configuration of MultiFields in the screen. See MultiFields element for additional information.

 

MultiFields enables and allows screen with multiple sets of dynamic field values.

<Validation>

See Validation.

 

 

<Events>

See  Action/Events.

   

<ScreenMath>

See ScreenMath Element.

 

 

<GenerateAccounting>

Optional tag used when accounting trigger on dynamic suspense field is changed but accounting is only written only when someone saves the suspense item.

No value

 

<Tests>

     

<Test>

Allows dynamic field name and value to be configured.

 

Specific Expression

   

TYPE

Expression

Attribute of Test Element

 Suspense Screen Image

Suspense Record Screen

 XML Example

<SuspenseScreen>
<Fields>
<Field>
<Name>SortCompany</Name>
<Display>Company</Display>
<DataType>Combo</DataType>
<Query TYPE="SQL">SELECT.*.FROM AsFundClass</Query>
</Field>
<Field>
<Name>NIGOFunding</Name>
<Display>NIGO Funding</Display>
<DataType>Radio</DataType>
<Query TYPE="FIXED">
<Options>
<Option>
<OptionValue>01</OptionValue>
<OptionText>Yes</OptionText>
</Option>
<Option>
<OptionValue>00</OptionValue>
<OptionText>No</OptionText>
</Option>
</Options>
</Query>
<DefaultValue>00</DefaultValue>
</Field>
<Field>
<Name>ItemNumber</Name>
<Display>Work Item #</Display>
<DataType>Text</DataType>
</Field>
<Field>
<Name>FromContract</Name>
<Display>From Contract No.</Display>
<DataType>Text</DataType>
</Field>
<Field>
<Name>SystemDate</Name>
<Display>SystemDate</Display>
<DataType>Date</DataType>
<Calculated TYPE="SYSTEM"></Calculated>
<Disabled>Yes</Disabled>
<Hidden>Yes</Hidden>
</Field>
</Fields>
<SearchFields>
<Field>SuspenseNumber</Field>
<Field>PolicyNumber</Field>
<Field>EffectiveDate</Field>
<Field>LastName</Field>
<Field>Amount</Field>
</SearchFields>
<GenerateAccounting>
<Tests>
<Test TYPE="Expression">FieldGenerateAccounting='Yes'</Test>
</Tests>
</GenerateAccounting>
</SuspenseScreen>

XML Schema

<SuspenseScreen>
<Fields>
<Field></Field>
</Fields>
<SearchFields>
<Field>[Name of the SearchField]</Field>
</SearchFields>
</SuspenseScreen>