The
EFT680 batch process has the capability to unencrypt a bank account number
if it has been encrypted.
This batch process creates a file containing pre-notification and deduction transactions to be sent to the bank. Typically, pre-notifications are created just once for individuals when their EFT order is established. If their transit number or account number changes, another pre-notification is created.
The source of this change can be either of the following:
· The bank informs the association through a notification of change or the rejected pre-notification transaction. In this case the association must run the EFT681 process to mark the individuals.
· The customer informs the association of a change. In this case the association must use the ORD001 – Order Entry – EFT tab to change the customer’s bank information (account/transit number) and mark the pre-note flag. Then the next run of EFT680 will generate another pre-notification transaction.
In addition to pre-notifications, the EFT680 application is used to create the actual deduction transactions which move money from the customer's account to the association's account. The EFT680 process creates a file as an ACH file.
When EFT680 is not able to successfully process an EFT scheduled payment successfully, the REJECTED_PAYMENT_FLAG on the scheduled payment is updated to ‘Y’ and the payment status is set to ‘PENDING’.
As of 7.4.1SP1, when there is no capacity available for the product on an order line that is being activated by EFT680, the process will not fail. Instead, the order will be displayed on the exception report.
The
EFT680 batch process has the capability to unencrypt a bank account number
if it has been encrypted.
Parameter |
Description |
Required? |
Organization |
The Organization ID for which you want to run the report. |
Read-only |
Organization Unit |
The Organization Unit ID for which you want to run the report. |
Read-only |
Run Mode |
Mode in which the report runs:
|
Yes |
Process Mode |
|
Yes |
Effective Date |
This is the date that will be treated as a pre-note date and also will be used to define the deduction date. This date is compared to the order_payment_schedule.due_date for selection of records to process. Records selected with have order_payment_schedule.payment_status_code='Pending' and a date <= the effective date. It will also be used as the batch date. |
Yes |
Subtitle |
The report subtitle as you want it to print as part of the report header. |
Yes |
Company |
The company number to run the report for. |
Yes |
Profile Code |
The bank profile code for the association's bank. |
Yes |
Batch ID |
When the process is run, a Direct Entry batch with application as EFT will be automatically created. Batch detail will have a transaction type of EFT and use the GL Account associated with the bank information defined for the company number. |
No |
Company Entry Description |
10 character term used in company/batch header record. |
Yes |
Job ID |
This parameter gives the ability to regenerate the data files and the report for the processed job. It works only with RESUBMIT mode. |
No |
Create Batch |
If Create Batch is set to 'N', parameter Batch is required. If Create Batch is set to 'Y', process will create a batch by the name specified. If left blank it will create a batch by itself. |
Yes |
Selection Criteria |
General selection criteria against Order_master/Order_detail. |
No |
Output File Location |
The path for the output file. |
No |
