SuspenseScreen

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: Elements and Attributes

Element/Tag	Attribute	Definition
<SuspenseScreen>		The opening and closing tag for the business rule.
<Summary>		The opening and closing tags of the summary section of Suspense Summary
<Fields>		Wrapper element of Field Element
<Field>		Names the fields to be presented.
<Name>		Specifies the database column in which the field values are stored.
<Display>	BOLD ITALICS	Optional: Renders bold or italicized representations of a dynamic field’s contents.   Yes: Field contents will be bold and/or italicized. No: Contents will not have bold or italicized
<Group>		Required element if configured under Summary Tag This is the name of the group (table) that should be used to obtain the value. This is used only where source data may come from multiple tables (i.e., search screens).   Suspense | SuspenseField | Math
<SplitSuspense>		Indicates if the system will allow a suspense record to be split into sub, suspense records. If set to Yes, the Split button is displayed.   Literal values of "Yes" or "No" the default value is No
	COPYMASTERSUSPENSE	Indicates if the system predefined set of fields are to be copied from the Master suspense record to the sub suspense records when 'Split' is selected. If set to yes, all dynamic field values as well as these fixed fields are copied to the sub suspense record on load; ACCOUNTNUMBER, BANKNAME, BANKNUMBER, BATCHNUMBER, CHECKNUMBER, CLIENTNUMBER, COMPANYGUID, CURRENCYCODE, EFFECTIVEDATE, FIRSTNAME, LASTNAME, POLICYNUMBER.   Literal values of "Yes" or "No" the default value is No
<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.
<Name>		Defines the fixed field name to apply the display instructions to. The BatchNumber fixed field only executes the identifier calculation on load if the field is blank and the suspense record is a sub-suspense and not a master. Field is always system disabled for user entry and cannot be enabled. Field only appears if explicitly configured.   "BatchNumber" in addition to existing field names
<DataType>		Defines the data type of the field. BatchNumber is a string and saves as text   Text
<Events>		See  Action/Events.
<ScreenMath>		See ScreenMath Element.
<MathVariable>	<MathVariables>	Defines an individual MathVariable. Repeatable. New system value 'MasterSuspenseGUID' is availabled when record is a sub-suspense. Referencing the variable should be preceded by IsEmpty(MasterSuspense) to ensure the value is not null before using in expressions.   'MasterSuspenseGUID'
<GenerateAccounting>	No value	Optional tag used when accounting trigger on dynamic suspense field is changed but accounting is only written only when someone saves the suspense item.
<Tests>
<Test>		Allows dynamic field name and value to be configured.   Specific Expression
	TYPE	Expression Attribute of Test Element

XML Schema

<SuspenseScreen>

<Summary>

<Fields>

<Field>

<Name></Name>

<Display></Display>

<Group> Math | Literal</Group>

</Field>

..

..

</Fields>

</Summary>

<Fields>

<Field></Field>

</Fields>

<SearchFields>

<Field>[Name of the SearchField]</Field>

</SearchFields>

</SuspenseScreen>

XML Example

<SuspenseScreen>

<Summary>

<Fields>

<Field>

<Name>SortCompany</Name>

<Display>Company</Display>

<Group>SuspenseField</Group>

</Field>

<Field>

<Name>ItemNumber</Name>

<Display>Work Item #</Display>

<Group>SuspenseField</Group>

</Field>

<Field>

<Name>FromContract</Name>

<Display>From Contract No.</Display>

<Group>SuspenseField</Group>

</Field>

<Field>

<Name>SystemDate</Name>

<Display>SystemDate</Display>

<Group>SuspenseField</Group>

</Field>

</Fields>

</Summary>

<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>