Configuring underwriting issues and multicurrency

In the base configuration, certain underwriting rules handle multicurrency. An underwriting rule that handles multicurrency has the following features:

Field

Description

Comparator

Value Comparator set to At least or At most. These values correspond to the codes Monetary_GE or Monetary_LE, respectively.

DefaultValueAssignmentType

Set to OffsetAmount.

DefaultValueOffsetAmount

Not equal to 0.

ValueFormatterType

Optional. Set to MonetaryAmount to format the value as an amount and currency in the user interface.

The PATotalPremium underwriting rule is an example that shows multicurrency. In PolicyCenter, you can view this underwriting rule in Administration > Business Rules > Underwriting Rules. In the Personal Auto line of business, the evaluator Gosu class (PA_UnderwriterEvaluator.gs) determines whether to raise PATotalPremium underwriting issues.

As with other underwriting issues, the code that creates the issue determines the value for the issue. PolicyCenter displays this value in the underwriting screens, therefore consider keeping the value (and approval) in the original currency. In the base configuration, the value comparator for monetary issues does a conversion between currencies, if needed. This conversion enables you to specify authority grants in a single currency per issue, yet have that grant to apply to all currencies for the issue. Then PolicyCenter determines whether or not to raise an underwriting issue. The UWIssueValueComparatorWrapper class in the gw.job.uw package uses the MonetaryGEValueComparatorWrapper and MonetaryLEValueComparatorWrapper classes to convert the currency and compare monetary values.

See also