8.2 Scenario 2 – This scenario results in an exception due to mismatch of balances
Production
- Pmt Hold condition exists on an Account
- Payment applied, payment goes into PAYMENT_ERROR
- Pmt Hold removed on the same day
- Payment reapplied from Payment Maintenance > Suspense screen. Payment successfully applied to the account as a PAYMENT_NONCASH
- Payment Hold condition reapplied
Test
- Since the final state of the account is a PMT HOLD condition no change will be made to the account in test
- Consequently the payment will go into a PAYMENT_ERROR and will not get applied to the account
In this scenario the account balances DO NOT match.
Phone Pay Fee
Currently in Production One time Phone Pays created during the day are picked up by the SET-CBT-ACH0 > ACCOUNT ACH PROCESSING JOB in the middle of the day (3:15 pm). This job creates the Phone Pay fee (FPHP) (The payment batch is created by the same job). The payments, which post later in the day, get allocated to the FPHP.
On the test environment, the tool posts transactions including Phone pay payments for the entire day. The SET-CBT-ACH0 > ACCOUNT ACH PROCESSING JOB runs AFTER the tool posting is complete. When the payment hits the account, the FPHP is not present on the account. This results in: -
$7 - additional Principal (ADV) being paid
$.01 – less interest being accrued since additional principal has been paid
Parent topic: Testing Tool Exceptions