EBS Autoclearing process for Multiple ACH payments in SAP

When APP program is sending the payment files (NACHA format) to bank, the files can have 100 or more individual vendor ACH payment items, but the bank only send a single debit transaction on the bank statement(BAI file) for the total ACH amount in the file. Automatic reconciliation does not take place to individual line itmes in ACH clear account.

Table of the Contents

Business Requirement

Auto clearing process for Multiple ACH payments in SAP.

PAL Logistics Company daily issue the multiple ACH payment files to Bank, which are contained the multiple ACH payments. But when PAL Logistics Company received BAI file which is contained the consolidate amount of ACH payment debit transaction. Once process the file in SAP the ACH clearing not able to match individual ACH payments with consolidation amount from BAI file.

Later, PAL Logistics Company manually clears ACH transaction in ACH clearing account by outside IT Vendor, which is cost effecting and time consuming.

This article is discussed about the procedure in SAP for implementation of DME reference number in EBS to get auto clear multiple ACH payments with consolidate amount from Bank.   Which is Cost saving and time saving for PAL Logistics Company.

Solution is DME Reference Number

The A/P Payment Program contained all of the ACH payments are associated with a single DME number. Finally, we need to ensure that we are passing the DME reference number to the bank as our payment reference number (DME) on the ACH file. The DME reference number, which is ten digits long, can be found in REGUT table based on Run Id and Run Date.

Obviously, this reference number must be sent back to us by the bank on the electronic bank statement (BAI file) with the lump sum ACH transaction. By activating the 19 DME Reference algorithm in EBS Configuration. The DME (19 DME Reference algorithm) then takes the single lump sum item from the bank statement (BAI file) and uses the DME reference number to find all of the open individual payment items related to it from the ACH payment run from the REGUT—> REGUH —> BKPF —> BSIS table.

System Behavior is indentify the individual ACH payments

GL 150006 ACH clearing account is contained individual Ach payments.

FBL3N:- Document  Header Text contained the Run date and Run id

BSIS table:- Header text shows Run date + Run id.

Configuration & Process in SAP

Parameter need  to set as below for Posting Rule – ACH

Algorithm need to active for 476 BTC as 019 Reference no

Payment program has been generated ACH file and the same get populate the DEM reference no (0000084517) in ACH file
header and below Even Functional module need to change with the help of ABAP consultant.

ACH file

Transaction:  OBPM1

Events can  be  changes as  per  client requirement  /  bank input  format  requirement.    In the above screen, additional events
created copying standard events with event number change in each group.  For exp.  If you want to change in ACH header line
format, you need to copy Event 20 and created new event number 21 in the header group to populate DME Reference number i.e. 20 as ZFI_PAYMEDIUM_SAMPLE_21 use Structure Field FPAYHX– RENUM in ZFI_PAYMEDIUM_SAMPLE_21  we can able
to get the DME ref.no.  on ACH file header record.

We can see the DEM Ref.number (0000084517) is contained the 4 ACH payments in Payment media FDTA transaction.

Whichreceived in bank BAI2 file contained DME Ref.number, which we have populated in  ACH file header.

Import the bank file into SAP:  T.code FF.5 we can seen DEM Ref.number as reference number in 16 line item to clear the multiple ACH payments with consolidate amount from BAI2 file.

FBL3n we can see the ACH clear account is auto-clear with consolidate value 40,000.00 with DME Ref.number (0000084517).

Conclusion Notes

Though EBS Auto Clearing process, customer can save the cost and time. Reducing the manual clearing process. Normally SAP customer has to pay for each BAI transaction to bank, as above example SAP customer having one consolidate BAI transaction instead of four BAI transactions in the bank file, so this is cost saving for SAP customers.