Overview

Use the Process Bank Corrections File flow pattern from the Payroll Checklist work area to reissue cheque payments against rejected Direct Deposit payments. A bank can reject a direct deposit payment because of:

• Incorrect bank account details

• Employee has closed their bank account without notifying the employer

The process of reissuing a cheque involves:

• End dating the employee's personal payment method

• Inactivating the employee's bank account. You must inactivate the invalid bank account so that it's not used for future payments.

• Voiding the payment and making an external payment against the rejected direct deposit payment.

Before you run the flow, you must first transform the information returned by the bank into the requisite Object Group HCM Data Loader file format. You must provide a unique name in the Object Group Name field each time you create an HCM Data Loader file. You must then load the Object Group HCM Data Loader file into the Oracle Web Center Content server.

The Process Bank Corrections File flow pattern includes these payroll tasks:

1. Upload Bank Corrections File task stores the information entered in the Object Group HCM Data Loader file into the object group table. The bank information is stored in the object group table, under the 'Process Information Group' object group type in the payroll application.

2. Update Personal Payment Methods task determines, through built-in logic, whether the personal payment method needs end dating or updating. The logic is as given here:

   • If there is a value in the Replacement Bank Number, the Replacement Account Number, or the Replacement Account Type field, then the process updates the Personal Payment Method.

   • If any of the above mentioned fields is blank, then the process end dates the Personal Payment Method.

   This task uses the Payment Reference number to identify the Personal Payment Method that's linked to the bank account that has been identified as incorrect. It also inactivates the incorrect bank details to stop them being used in future payments.

   Note: The flow task doesn't create a new Personal Payment Method. You must create one manually.

3. Void Payments task marks the original payments as void.

4. Make External Payments task runs the external payment process to ensure that the payments voided in the previous task are paid externally.

5. Generate Cheque Payments task runs the HCM Extract Report to retrieve the cheque number and other information from the external payment record to produce the report output. The delivered HCM Extract Report has a built-in logic to generate the cheque number, if not available.

Steps 3-5 only run if you have to reissue an external cheque for a rejected payment.

Note: You can use the delivered default cheque template or configure the template to include additional attributes such as a company logo.

Since a payslip is already issued, this flow doesn't generate the payslip.