– The Admin side of ACH handling: download batches, canceling.
Notes: For creating and downloading an ach batch, the follow process is used
- Show all the unique transactions that are not in a batch
- User selects the ones for the next batch.
- transhdr entries are marked with the processed information
- A new window/tab is opened and the batch report is shown and the ach file is downloaded
- The batch creation grid is refreshed. If user views history later, they can click an icon to download the ach file or view the batch report again ACH batch file and report are saved in /home/<cu>/admin/ach/
The batch id is an encoded string of the batch date/time.
The <cu>transhdr.transactioncode table has specific meaning
- For internal transfers it is the code sent to the core
- For ACH transactions use for determining the Service Class Code and Standard Entry Class Codes: Service Class Code: 1X = credit with respect to the RDFI 2X = debit with respect to RDFI 3X = mixed credit/debit with respect to RDFI Standard Entry Class Code X = P (PPD), C (CCD), W (WEB) PPD/CCD are for ACH feature; WEB is for External Transfer feature NOTE: It is possible in the future that the transhdr.transactioncode is just a flag to make sure the correct SSC and SEC are created, or to better identify certain transactions (e.g. micro deposits) for specialized handling. (Addendum: As of 10/05/2017 I think we are at this point. The code building the file will reflect this. "W" means it comes from the Scheduled/Transfer feature, "P" means it came from the micro deposit creation from the External Account feature, and "C" means it came from the "commercial" ACH feature.) This is because we might create two entries under one company for most external transfers but two separate companies with one entry each for an external transfer to make a loan payment at the CU. For this later case it is a "WEB" for the external account debit and a "PPD" for the loan payment. Additionally the micro deposit offset needs to move the money into the CU Admin configured account so we need to specifically be able to identify that <cu>transhdr entry. NOTE: When determining the local account number for the ACH record take the sub-account and add to the end of the account number and make sure any non-alphanumeric characters are removed.