2.9.2 Description

This topic provides a description of the application edit based on suspicious flag.

  1. Introduced a new date field at the customer level, 'Suspicious'.
  2. Introduced 2 new non-monetary transaction 'BUS_SUSPICIOUS_MAINT & CUS_SUSPICIOUS_MAINT'.
    1. These transactions can be used for 2 reasons:
      • If the 'Suspicious' field is BLANK, the system stamps the transaction date.
      • If the 'Suspicious' field has some date (Non-Blank), the system removes the date in the field and makes it blank.
  3. The user can update the flag using the EDIT screen of 'Customer/Business Information' at servicing Stag and the system posts the transaction as a DIRECT UPDATE by posting a Customer Maintenance transaction.
  4. Alternatively, the user can update the field by posting the following non-monetary transaction(s).


Description of customer-information.png follows
Description of the illustration customer-information.png


Description of transaction-super-group.png follows
Description of the illustration transaction-super-group.png

Table 2-23 Transaction Codes

Parameter Code Default Value Sort Displayed Required
Transaction Date 1 Y Y
Relation Type Code Primary (Refer existing lookup RELATION_TYPE_CD) 2 Y Y
Comments 3 Y N
Actions on posting of the transaction:
  • System accepts posting of the transaction effective for today; this implies that the user cannot mark the account suspicious for any back dated and the flag date is effectively the date of posting transaction:
    • Since this is customer level field, the information captured for the given customer is displayed and applicable for all accounts attached to the customer number.
  • System validates the 'Relation Type' input while posting the transaction on the account. If the Relation Type selected in the transaction does not exist on account, system raises error - 'Selected relationship doesn't exist on account':
    • For 'Business Only' Account, system marks the 'Business' as Suspicious and doesn't need to validate the Relation Type selected while posting the transaction.
    • Different conditions for customers and business are posted, depending on the flagging of customer/business type.
  • On successful posting of a transaction, system stamps the transaction date in the 'Suspicious' field:
    • If the 'Suspicious' field is BLANK for selected customer, the system stamps the transaction date and open a condition on the account called 'Suspicious'.
    • If the 'Suspicious' field is having some date and condition already posted on the account, system verifies that if NONE OF CUSTOMERS attached to the account has 'Suspicious' flag ON, then it only removes the condition. If any of the joint customer has this flag value (some date), then the system will not remove this condition.

Note:

System allows posting of 'Suspicious' transactions on General Ledger date and the customer/business will be marked as suspicious as on the transaction date. But system gives the flexibility to mark suspicious for any back date using EDIT/ADD button of the customer/business information page.