In this section you need to enter the
information required by your bank in the relevant fields.
The required fields for the format selected will be displayed and must be entered.
Per format you will be asked to enter certain data that is applicable to your bank format only. These fields will be enabled for you to enter the relevant data.
Some of these fields you will need to obtain
from your bank. For example: For the format STDBEST you will need to obtain the
Company Code from Standard Bank.
Use Optional Fields: Select the Use Optional Fields checkbox to make use of Optional Fields 1 to 5. These can be used when setting up the statement descriptions and in the customization of the file name.
Choose from the Output options where you want the EFT file to be delivered to.
EFTXpress supports FTP and SFTP with password, with Key File and with 2 factor authentication.
If the bank allows you can upload directly to their FTP/SFTP site or you can use this option internally.
If you select encryption, the file will be
encrypted before it is uploaded.
Field |
Value |
Destination |
Select from the following Output Options:
|
Local |
On Premise will write the file to the directory setup in Export Path. Web UIs will download the file to the default download directory. |
FTP |
Host
Name: IP Address or name of the FTP Server FTP/SFTP Directory: |
SFTP with Password |
Host Name: IP Address or
name of the FTP Server FTP/SFTP Directory: Upload Directory Required By Bank |
SFTP with Key File |
Host
Name: IP Address or name of the FTP Server FTP/SFTP
Directory: |
SFTP 2FA |
Host
Name: IP Address or name of the FTP Server Key Password: Enter the password used to create the key FTP/SFTP
Directory: Upload Directory Required By Bank |
The directory for the Private Key Files need to be a shared directory as all the Users who post and generate EFT batches must have access to it. Restrict access to users who don't generate EFT Files. Use UNC in the file path if the key file is on a shared network.
If you are using the Web UIs, the user needs to have access to the key file.
It is recommended you copy the key files into the Sage 300 Shared Data folder, as access to the Shared Data folder is required for the web screens to work.
The full file path to the Private Key File can be copied from the shared directory in the File Explorer.
Example: enter "/EFTFiles" to upload to the folder EFTFiles
on the FTP server
Note: This applies to both SFTP with Key File and SFTP
2FA
SSH keys are made up of two keys - a public key and a private key.
The
file name for the public key is *.pub. You upload the public key to the FTP
server (e.g. the bank's FTP site or your FTP Site).
You upload the private key to the FTP client (e.g. the Sage 300
Server)
You need to use an OpenSSH key using the RSA format.
You can use Putty Key Generator, Windows key generator - ssh-keygen -m PEM or
your choice.
You can use the Test button to test the SFTP setup.
The
file ‘’PSEFTTRFRTEST.TXT’’ will be created when selecting the Test button and
uploaded.
A message will be displayed if the upload is successful or failed. The log
file ‘’PSEFTSecure.log’’ will be updated. This file is in the cbXX
directory.
Check the log file if the Test failed.
Note: A common error when using SFTP with key file is
to use the wrong key file or a key file in the wrong format. See Key file
setup.
FTP:
Error transferring file via FTP: The underlying connection was closed: The server committed a protocol violation.
Solution: Incorrect port
SFTP with Password:
SFTP with Password File transfer failed: 'count' must be non-negative. Parameter name: count
Solution: Incorrect password