1. Implementing Payroll for Bahrain
  2. Overview of Reprocessing Rejected EFT Payments

Overview of Reprocessing Rejected EFT Payments

A bank can reject an Electronic Funds Transfer (EFT) payment because of:

  • Incorrect bank account details

  • Employee has closed their bank account without notifying the employer

Here's what you can do to reissue a check:

  • End date the employee's personal payment method

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

  • Void the payment and make an external payment against the rejected EFT payment.

Use the Process Bank Corrections File flow pattern from the Payroll Checklist work area to reissue check payments against rejected EFT payments.

Before you run the flow, complete these tasks.

  1. Transform the information returned by the bank into the requisite Object Group HCM Data Loader file format.

  2. Provide a unique name in the Object Group Name field each time you create an HCM Data Loader file.

  3. Load the Object Group HCM Data Loader file into the Oracle Web Center Content server.

Here's the list of payroll tasks the Process Bank Corrections File flow pattern includes:

Task Name

Description

1. Upload Bank Corrections File

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

Determines through this built-in logic whether the personal payment method needs end dating or updating. The logic is as follows:

  • 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 are blank, then the process end dates the Personal Payment Method.

This task uses the Payment Reference number to identify the Personal Payment Method linked to the bank account 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

Marks the original payments as void.

4. Make External Payments

Runs the external payment process to ensure that the payments voided in the previous task are paid externally.

5. Generate Check Payments

Runs the HCM Extract Report to retrieve the check 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 check number, if not available.

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

Note:

You can use the delivered default check 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.

Related Topics