2.11.2 Description

This topic provides a description of the primary correspondence change.

Introduced a new non-monetary transaction → CUSTOMER CHANGE CORRESPONDENCE (CUS_CHANGE_CORR)

Table 2-27 Parameter Code

Parameter Code	Default	Displayed	Required
Transaction Date		Y	Y
Relation Type Code	Primary (Refer existing lookup RELATION_TYPE_CD)	Y	Y
Comments		Y	N

Validations:

1. This transaction does not apply to 'Business only' accounts.
2. If the user selects the same customer/relationship, which does not exist on the account, while posting the transaction, the system shows an error → Customer already has Correspondence Permission / Customer relation doesn't exist on account.
3. If the user tries to change the relation where the 'Deceased Date' is not NULL, system raises an error "Cannot change the correspondence to deceased relation".
4. On successful posting of the transaction, the system sets the value as 'N' for existing relation and 'Y' for the new relation.
   1. Example: If the transaction changes the primary correspondence from PRIMARY TO SPOUSE, the system sets the flag value for relation PRIMARY = N and SPOUSE= Y.
5. Impact Handling:
   1. Handled the batch job related to letters to send for the relation to 'Primary correspondence'.
   2. If user is posting CUS_DECEASE_MAINT (Customer Deceased txn), system checks that if the primary correspondence is set to Y, and if the value is Y, change the primary correspondence to 'Primary' relation.
6. Servicing → Customer Details Screen (Read only field)

   Introduced a new field 'Primary Correspondence' as shown in the screen.

Description of the illustration customer-details.png