EFT Bank Control
You use this program to capture and maintain details of EFT control information required within the system.
Menu and Toolbar
Field | Description |
---|---|
File | |
Save and Close |
This saves the details you entered or changed and returns to the previous screen. |
Close |
This returns you to the previous screen. |
New | This adds a new data record. |
Delete |
This deletes the data record currently displayed. |
Save | This saves the details you entered or changed. |
Bank | Indicate the bank for which you want to maintain EFT control information. |
Bank Details
Field | Description |
---|---|
Bank information | |
Bank |
Indicates the code of the bank you are currently maintaining. |
Bank name |
Indicates the description of the bank you are currently maintaining. |
Global statement narration |
Enables you to enter the text that must be displayed on the supplier's bank statement when you make an EFT payment to your suppliers. |
EFT options | |
Output EFT payments to XML format |
This must be enabled to create an XML file containing all the relevant EFT details from the Accounts Payable and Cash Book payment runs. The XML file is created by the EFT Payments Extract and EFT Payments Re-extract programs and includes supplier, beneficiary and bank information that can be used by a third party software developer to extract the information into the file format required by your bank.
|
Path location |
Client
This lets you create the XML file on the client machine. Server
This lets you create the XML file on the server. This only applies when running SYSPRO in a client/server environment. |
XML file path |
This indicates the full path name where the EFT payment file is stored. The path must exist. |
XML output structure |
By supplier
This lets you extract the total amounts paid to each supplier to the XML file. No individual supplier invoice details are extracted to the file. By invoice
This lets you extract all the invoice details making up the supplier totals to the XML file in addition to the total amounts paid to each supplier. |
Last XML file name |
This indicates the name of the last XML file that was created for this bank. |
Payment format information |
This section becomes available when the Output EFT payments to XML format field is enabled. |
Bank payment format |
This lets you select which payment format you require. The payment formats are created in the EFT File Format Maintenance program |
Format type |
This indicates the format type selected in the EFT File Format Maintenance program, which is either NACHA or CPA005. |
Company name |
This indicates your company name, which may appear on the beneficiary's statement. |
Payment location |
Client
This lets you create the XML file on the client machine. Server
This lets you create the XML file on the server. This only applies when running SYSPRO in a client/server environment. |
Payment file path |
This indicates the full path name where the EFT payment file is stored. The path must exist. |
Define Details |
Select this hyperlink to indicate the payment file details for NACHA and CPA batch payments. |
NACHA Details
This form is displayed when you select NACHA at the Bank payment format field.
The information entered on this form is saved in the EftBankCtl and EftBankExtra tables and will be the used to create the data record within EFT XML file.
Field | Description |
---|---|
NACHA Information |
|
Leading tax ID digit |
This is 1 by default, but can be set to any digit between 0-9, a space or be left blank. The Immediate Origin element in the file header consists of a preceding digit (usually 1 or blank) plus the company’s IRS tax reporting number. |
ABA routing number |
This lets you enter the routing number for the receiving financial institution. This is the company’s 9-digit routing number that consists of the four-digit federal reserve routing symbol plus the four-digit ABA institution identifier plus a check digit. This number is used in the Immediate Destination element in the file header which consists independent bank’s transit routing number preceded by a blank. |
IRS tax ID |
This indicates your company's federal IRS tax ID number |
Service class |
200 - ACH Entries Mixed
This is typically used and indicates that the payment file may contain ACH debits and credits (Accounts Payable invoice payments and credit notes). 220 - ACH Credits Only
This indicates that the payment file only contains ACH credits. 225 - ACH Debits Only
This indicates that the payment file only contains ACH debits. |
Use NACHA alternate ID |
Enable this field to use the value defined at the NACHA alternate ID field as the supplier ID (Suppliers). If this field is not enabled, the, the supplier ID number defaults to the Accounts Payable supplier number. |
Immediate origin |
This lets you specify the name of the initiating party, which will replace the default entry of the originating company name. If this field is left blank, then this defaults to the value at the Company Name form field. |
Bank account number |
This indicates the company’s routing number. |
Company identification |
This let you enter the 10-digit number assigned to your company by the bank. |
CPA Details
This form is displayed when you select CPA at the Bank payment format field.
The information entered on this form is saved in the EftBankCtl and EftBankExtra tables and will be the used to create the data record within EFT XML file.
Field | Description |
---|---|
Canadian EFT Information |
|
Routing record |
This lets you indicate the routing record. |
Processing center |
This lets you indicate the 5-character processing center. |
User number |
This is the user number that is supplied by the bank. |
Operation code |
This indicates the operation code that is used to identify the transaction. The operation code is typically 450. |
Company bank number |
This lets you specify the customer's account number. |
Bank leading character |
This indicates the bank leading character. |
EFT bank control |
This indicates the control number for EFT payments. |
EFT bank branch |
This indicates the bank branch for EFT payments. |
Fill character |
This indicates a trailer record fill character. |
Suppress return account no |
Enable this to suppress the return bank account number. |
Date to use |
This lets you select which date you want to use for the payment transaction. |
You can restrict access to the eSignature transactions within a program at operator, group, role or company level (configured using the Electronic Signature Configuration Setup program).
Electronic Signatures provide security access, transaction logging and event triggering that gives you greater control over your system changes.
Controls access to the Add or New function in the following programs:
- Browse on EFT Bank Control
- EFT Bank Control
Controls access to the Add function in the Bank Control Maintenance business object.
Controls access to the maintenance of banks in the following programs:
- Browse on EFT Bank Control
- EFT Bank Control
Controls access to the maintenance of banks in the Bank Control Maintenance business object.
Controls access to the Delete function in the following programs:
- Browse on EFT Bank Control
- EFT Bank Control
Controls access to the Delete function in the Bank Control Maintenance business object.
You can restrict operator access to programs by assigning them to groups and applying access control against the group (configured using the Operator Groups program).
You can restrict operator access to programs by assigning them to roles and applying access control against the role (configured using the Role Management program).
Notes and warnings
Deletion considerations
-
You cannot delete EFT control information for a bank if there are any EFT transactions in progress against the bank.
Custom form
-
A custom form containing extra information (e.g. relating to a batch of payments) can be created for each bank. If you select to create an XML file, then any information captured in a custom form is output to the XML file.
Avanti
- The Save form values as Default option on the short-cut menu in the listview is not available in SYSPRO Avanti.
Copyright © 2024 SYSPRO PTY Ltd.