A Appendix : Handling Metro II Account Statuses

Following are the steps involved in updating the Metro II specific account status for an account and reporting the same in Metro II reporting file.

Step-1: Once system runs the daily batch TXNDDT_BJ_100_01 (SET-TPE) BILLING / DUE DATES PROCESSING, it updates the Metro II account status in ACCOUNTS table i.e. ACCOUNTS. ACC_CRB_ACC_STATUS_CD. Metro II specific account status update details are explained in the below table.

Step-2: When system executes the batch job CBUUTL_BJ_100_02 (SET-ODD2) to populate the METRO_II_DATA table for an account, column MET_BASE_ACCOUNT_STATUS will be updated with the current Metro II account status available in the ACCOUNTS table explained above.

Step-3: Once Metro II reporting file generation batch CBUUTL_BJ_100_03 (SET-ODD2), system creates the reporting file and account status will be populated as part of the base segment field ‘17A – Account Status’.

Following table explains the Metro II account status update process during the billing / due date batch processing.

Table A-1 Metro II account status update process

S.No Metro II Account Status Code(s) Update Processing in OFSLL
1 11, 71, 78, 80, 82, 83 and 84
In case of accounts with ‘ACTIVE’ status and difference between account active date and oldest due date is –
  • Less than 30 - Status is 11
  • Less than 60 - Status is 71
  • Less than 90 - Status is 78
  • Less than 120 - Status is 80
  • Less than 150 - Status is 82
  • Less than 180 - Status is 83
  • Greater than 180 - Status is 84
2 13: Paid or closed account/zero balance
  • Account balance is zero
  • Account status is either ‘PAID OFF’ or 'CLOSED:PAID OFF'
3 95: Voluntary surrender; there may be a balance due
  • Account status is ‘ACTIVE’
  • Account collateral type ‘Vehicle’ and collateral sub type is ‘Personal Property Vehicle’. In OFSLL, this is being set at the loan/lease product selected for the account.
  • Post an ACCOUNT EVENT NOTIFICATION non-monetary transaction with event type as ‘VOLUNTARY REPOSSESSION’, then system will automatically post the following call activity. If user post the above transaction then user need not to post this call activity again for ‘Voluntary Repossession’ account condition before processing any payment as part of the Repo which makes account balance to zero

    Action: VRP

    Result: Any of the values displayed

    Reason: Any of the values displayed

    Condition: REPOSSESSION

  • Mark account collateral repossession status is ‘VOLUNTARY’
  • In case, if consumer is not responsible for the remaining balance on the account after the sale of the merchandise or there is no deficiency balance
    • System will refer a new condition ‘Not Liable for Payment’ which should open through manually or using ACCOUNT EVENT NOTIFICATION non-monetary transaction with new event type as ‘Customer Not Liable for Payment’.
    • System will post the following call activity
      • Action: VRP
      • Result: Customer Not Liable for Payment
      • Condition: REPOSSESSION
Note(s):
  • In case customer is not using OFSLL Collections module, system updates the collateral repossession status to ‘VOLUNTARY / INVOLUNTARY’ while posting the Call Activity transaction subject to the system parameter ‘METRO_WITHOUT_COLL_IND’ is enabled and value is set as ‘Y’.
  • In case customer is using OFSLL Collections module, marking of the account collateral repossession status to ‘VOLUNTARY / INVOLUNTARY’ can be done using the OFSLL Collection Module functionality ‘Repossession’. In this case it is recommended that system parameter ‘METRO_WITHOUT_COLL_IND’ need not be enabled.
4 96: Merchandise was repossessed; there may be a balance due
  • Account status is ‘ACTIVE’
  • Account collateral type ‘Vehicle’ and collateral sub type is ‘Personal Property Vehicle’. In OFSLL, this is being set at the loan/lease product selected for the account.
  • Post an ACCOUNT EVENT NOTIFICATION non-monetary transaction with event type as ‘IN-VOLUNTARY REPOSSESSION’, then system will automatically post the following call activity.
  • If user post the above transaction then user need not to post this call activity again for ‘In-voluntary Repossession’ account condition before processing any payment as part of the Repo which makes account balance to zero. Following is the call activity posting details –

    Action: IVR

    Result: Any of the values displayed

    Reason: Any of the values displayed

    Condition: REPOSSESSION

  • Mark account collateral repossession status is ‘IN-VOLUNTARY’
Note(s):
  • In case customer is not using OFSLL Collections module, system updates the collateral repossession status to ‘VOLUNTARY / INVOLUNTARY’ while posting the Call Activity transaction subject to the system parameter ‘METRO_WITHOUT_COLL_IND’ is enabled and value is set as ‘Y’.
  • In case customer is using OFSLL Collections module, marking of the account collateral repossession status to ‘VOLUNTARY / INVOLUNTARY’ can be done using the OFSLL Collection Module functionality ‘Repossession’. In this case it is recommended that system parameter ‘METRO_WITHOUT_COLL_IND’ need not be enabled.
5 61: Account paid in full, was a voluntary surrender
  • Account status is 'CLOSED:PAID OFF'
  • Account collateral type ‘Vehicle’ and collateral sub type is ‘Personal Property Vehicle’. In OFSLL, this is being set at the loan/lease product selected for the account.
  • User needs to post a call activity for ‘Voluntary Repossession’ account condition before processing any payment as part of the Repo which makes account balance to zero. Following is the call activity posting details –

    Action: VRP

    Result: Any of the values displayed

    Reason: Any of the values displayed

    Condition: REPOSSESSION

    Collateral status is ‘VOLUNTARY’

  • Mark account collateral repossession status is ‘IN-VOLUNTARY’
Note(s):
  • In case customer is not using OFSLL Collections module, system updates the collateral repossession status to ‘VOLUNTARY / INVOLUNTARY’ while posting the Call Activity transaction subject to the system parameter ‘METRO_WITHOUT_COLL_IND’ is enabled and value is set as ‘Y’.
  • In case customer is using OFSLL Collections module, marking of the account collateral repossession status to ‘VOLUNTARY / INVOLUNTARY’ can be done using the OFSLL Collection Module functionality ‘Repossession’. In this case it is recommended that system parameter ‘METRO_WITHOUT_COLL_IND’ need not be enabled.
6 63: Account paid in full, was a repossession
  • Account status is 'CLOSED:PAID OFF'
  • Account collateral type ‘Vehicle’ and collateral sub type is ‘Personal Property Vehicle’. In OFSLL, this is being set at the loan/lease product selected for the account.
  • User needs to post a call activity for ‘In-voluntary Repossession’ account condition before processing any payment as part of the Repo which makes account balance to zero. Following is the call activity posting details –

    Action: IVR

    Result: Any of the values displayed

    Reason: Any of the values displayed

    Condition: REPOSSESSION

  • Collateral status is NOT ‘VOLUNTARY’
7 64: Account paid in full, was a charge-off
  • Account status is 'CHGOFF'
  • Account deficiency balance is less than or equal to zero
8 97: Unpaid balance reported as a loss (charge-off)
  • Account status is 'CHGOFF'
  • Account deficiency balance is NOT zero
9 93: Account assigned to internal or external collections
  • User has to post the account event notification non-monetary transaction (ACC_EVENT_NOTIFY) with event type as ‘AAC’ and it will post an account condition ‘ACCOUNT ASSIGNED TO INTERNAL OR EXTERNAL COLLECTIONS’.
  • If the above mentioned non-monetary transaction is posted on the account, system will not report the account status codes based on the number of days outstanding / delinquency days and will report the status code as ‘93’.
  • To close the above mentioned account condition user can post the account event notification with event type as ‘COLL_CANCEL’.
10 62: Account paid in full, was a collection account While posting the ‘PAID OFF’ monetary transaction on an account, system will check whether an active ‘ACCOUNT ASSIGNED TO INTERNAL OR EXTERNAL COLLECTIONS’ exits and if so will report the status code as ‘62’.
11 DA: Delete entire account (for reasons other than fraud)
  • User has to manually ‘VOID’ the account first.
  • Post voiding the account, user has to post the account event notification non-monetary transaction (ACC_EVENT_NOTIFY) with event type as ‘DELETE_ACCOUNT’ and it will post an account condition ‘DELETE ACCOUNT-NON FRAUD’.
  • If the above mentioned non-monetary transaction is posted on the account, system will not report the account status codes based on the number of days outstanding / delinquency days and will report the status code as ‘DA’.
12 DF: Delete entire account due to confirmed fraud (fraud investigation completed)
  • User has to manually ‘VOID’ the account first.
  • Post voiding the account, user has to post the account event notification non-monetary transaction (ACC_EVENT_NOTIFY) with event type as ‘DELETE_ACCOUNT_FRAUD and it will post an account condition ‘DELETE ACCOUNT-FRAUD’.
  • If the above mentioned non-monetary transaction is posted on the account, system will not report the account status codes based on the number of days outstanding / delinquency days and will report the status code as ‘DF’.
13 89: Deed received in lieu of foreclosure on a defaulted mortgage; there may be a balance due.
  • User has to post the account event notification non-monetary transaction (ACC_EVENT_NOTIFY) with event type as 'DIL_COMPLETED' and it will post an account condition 'DEED IN LIEU COMPLETED'. System allows only If the Portfolio Type is `I’ & Account Type should be 6D or 0A.
  • If the above mentioned non-monetary transaction is posted on the account, system does not report the account status code as 89.
  • For this, account status should be 'Active'.