EFTProcessing Orchid Training Guide
EFTProcessing Orchid Training Guide
Getting Started
EFT Processing streamlines payment and collection processes. It transfers Sage 300 receipts and pay-
ments through to the electronic funds transfer functionality of your banking software and lets you print
and/or email remittance advices to A/P Vendors and A/R Customers.
Orchid EFT Processing includes a number of system defined file formats for a variety of banks. Additional
bank formats can be added in a user defined file.
To get started with EFT Processing, you need to install, activate and enter license details.
You can then configure EFT Processing.
Note: EFT Processing includes a French translation if the Sage 300 user is set to French language.
Refer to EFT Help for more details and training guide: https://help.orch-
id.systems/sage300addons/Content/Product-Home/EFT-Processing.htm
Review details below:
Table of Contents
Getting Started 2
Tutorials 17
Approving changes of EFT Vendor/Customer/Employee details 17
Setup SFTP Output Destination 19
To setup SFTP as an output destination: 20
SFTP with Password: 20
SFTP with Key File: 21
SFTP 2FA with Key File and User Name / Password: 22
Key file setup Tips 23
Testing the FTP Configuration 24
Setup and Use EFT Clearing Bank 25
When to use a Clearing Bank in EFT Processing A/P 25
Setup 25
Processing A/P Payments: 26
Steps for Setting Up BPAY (for use in Australia) 28
Setup EFT 42
EFT Options 43
Overview 43
A/P Tab 43
A/P Email Tab 44
A/R Tab 44
A/R Email Tab 44
Primary File Type 44
Default Advice Tab 45
Payroll Tab 45
Payroll Email Tab 45
Global FSN Tab 46
Updates Tab 46
EFT Processing Email Tab 47
Email Field details 47
Basic Authentication SMTP: 47
Microsoft Graph: 48
Send Email copy 48
Examples 49
Using Sage Company Profile Settings 49
Using Sage Company Profile details 49
Limit per Session/Minute 49
Troubleshooting Sending emails 50
EFT Banks Form - Overview 50
When to print 91
How to print 91
Customer Report 91
EFT Employee Report - Features 92
Tip:
Programs are installed in the Sage 300 program folder, in the ELXXA subfolder, where EL is the 2-letter
code for the Orchid module and XX depends on the Sage 300 version you are running:
Example: EL68A for EFT Processing version 2021, EL69A for Version 2022, EL71A for Version 2024.
Note: REGACC is run automatically as part of the installation process. If some files are locked during
the installation, the re-boot is required to unlock all files and complete the installation.
Important! If you install Sage 300 on each workstation, as well as the server, then you must do the
same with EFT Processing. In this case, repeat the above steps for each workstation.
Requirement! Web Screens for EFT Processing are only available if you have a subscription license for
EFT Processing and are running Sage 300 version 2021 and above.
For information on activating modules, refer to the Sage 300 System Manager online Help (choose the
Help menu on the Sage 300 desktop) or review the chapter, Setting Up Security, in the System Manager
Administrator Guide
LICENSE DETAILS
To start using EFT Processing, you need a valid serial number and license file.
If you don't have a valid license for EFT Processing, you only see the License screen.
Refer to EFT Processing License Screen on the facing page for details.
Note: This applies to Sage 300 versions 2019 and above. You need a serial number to install
an older version.
After you install the software, you need to activate EFT Processing in one company using Sage 300
Administrative Services > Data Activation.
There are two options to enter the license details:
USE A 30 DAY TRIAL LICENSE FILE
To generate a 30-day trial license file, enter the serial number provided for your module and Save the
details.
Note: The license applies to all the Sage 300 databases for the same installation. You only need to
enter the license details in one company.
Tip: If installing with a 30 day grace period, additional re-installations will not extend the grace period.
MINIMUM REQUIREMENTS
You need to use the same version for the core Sage 300 modules and EFT Processing. For example,
EFT Processing version 2024 requires Sage 300 System Manager version 2024.
Additional specific Sage 300 modules may be required to enable all functionality. Refer to Orchid Sys-
tems's website for details ( https://www.orchid.systems).
Requirement! Web Screens for EFT Processing are only available if you have a subscription license for
EFT Processing.
LICENSE SCREEN
You use the EFT Processing license screen to enter serial number and activation code.
When to use:
After a new installation or an upgrade to a newer version of Sage 300.
After a subscription renewal, enter the activation code with the new expiry date.
View the components of the Orchid module you are licensed for.
How to use:
Enter the license details, click the Add button to create the license file.
Restart the Sage desktop to enable the new license.
Enter a valid serial number - Serial Number depends on Module, Sage 300 Version and Edition.
Tip: If you install a 30-day trial, enter a valid activation code before the trial expiry date to continue
using the application.
Note: In the four weeks before the expiry date, users receive a warning message when logging into
Sage 300 (weekly for the first three weeks and daily in the last week). If you don't renew before the
expiry date, the software will become read-only.
Important! If the Sage 300 Version or Edition change, a new Serial Number and activation
If the company name registered with Sage changes, a new Activation Code must be requested from
Orchid Systems.
Tutorials
In addition to getting started steps for EFT AP/AR and EFT Payroll, you can review the EFT Processing
tutorials below to enhance the security of your implementation.
A/R TAB
Create a Security Group ENTER in Sage 300 Administrative Services, for users who can only add/edit
bank account details
Create a separate Security Group APPROVE for users who can approve bank account details.
How to use
When a user in the ENTER group updates details on the EFT Record, the status reverts to "Entered" .
A user in the APPROVE group needs to set the record to "Active".
Approvers can use the EFT Audit Logs (Inquiries and Reports) to see what needs approving.
Note:
Status needs to be Active to use the record (EFT Vendor, Customer or Employee) in the Create
EFT File process.
Tip:
When using an internal FTP, many companies enforce separation of duties to further
enhance security. A common scenario can be as follows:
User 1 creates the EFT File. User 1 does not have access to the SFTP Site
User 2 does not have access to create the EFT File, but does have access to the SFTP
Site to upload the file to the Bank
User 3 has to approve the file in the Banking Software. User 3 does not have access to
create the EFT File or to the SFTP Site.
Note: This applies to the Payments and Refunds, Receipts and Payroll options. Refer to Out-
put Destination: on page 132 in the EFT Bank setup topic.
Tip: If you are not using the default SFTP Port 22, you can add the port at the end of the
hostname, separated by : (semi-colon), for example 123.123.70.70:2222
Tip: To upload through EFT, do not use characters such as: ? = * in the password.
Upload To Folder: "/" if you are uploading to the root directory, or "/xxx" if uploading to a folder on
the FTP server.
Example: enter "/EFTFiles" to upload to the folder EFTFiles on the FTP server
Note:
This file needs to be in a shared directory on the server that all EFT Users who use Create EFT
File must have access to. Restrict access to users who don't create EFT Files.
If the key file is on a network share, use UNC in the file path.
Tip:
When using the EFT Processing web screens, the user configured in IIS to run the web
screens needs to have access to the key file. You can copy the key file in the Sage 300
Shared Data folder, as access to the SharedData folder is required for the web screens to
work.
Copy the full file path from File Explorer to the Key File field as there is no Browse files but-
ton on the web screens.
Upload To Folder: "/" if you are uploading to the root directory, or "/xxx" if uploading to a folder on
the FTP server.
Example: enter "/EFTFiles" to upload to the folder EFTFiles on the FTP server
Tip: To upload through EFT, do not use characters such as: ? = * in the password.
Note: This file needs to be in a shared directory on the server that all EFT Users who use
Create EFT File must have access to. If it’s on a network share, use UNC in the file path.
Key File Password: Enter the Password applied to the key file. This is recommended to
protect the file, but is optional.
Upload To Folder: "/" if you are uploading to the root directory, or "/xxx" if uploading to a folder on
the FTP server.
Example: enter "/EFTFiles" to upload to the folder EFTFiles on the FTP server
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.
The Header & Footer row should look like this:
Tip:
Using PuTTY Key Generator to generate the private key
Review the log file and check the details you have entered.
Tip: One of the most 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 Tips on the previous page
Tip: If unsuccessful, we recommend you install an FTP client, for example Filezilla, on the
workstation where you will be running "Create EFT File". You can then use the FTP client to
test the credentials you are using, and upload a test file to the required folder. If it works
with an FTP client, but not with EFT Processing, contact your Sage 300 partner for support.
Setup
If you choose "Clearing Bank" for the EFT Bank Type– you have to select the Bank for which this clearing
account is for on the EFT Banks setup screen. (Refer to For Bank on page 131 in the EFT Bank Setup
Screen).
The Clearing Bank and the regular bank are both created in Bank Services.
Note:
If your company uses Multi-currency, In Bank Services, Banks Options > Processing, check that the
Transfer Adjustment G/L Account is configured correctly.
If it is blank, you will receive an error message when creating an EFT file for the clearing bank and the
transfer will not be created:
Transfer Adjustment GL Acct cannot be blank.
Note:
EFT clearing account balance should always be 0.00.
Payments in the EFT clearing will always be available to be reversed as that account will never be recon-
ciled and posted.
Note:
Clearing bank is only available with EFT AP Payments. It is not available with AR Receipts or Payroll
transactions.
In Accounts Receivable, you can choose whether or not Deposits are posted to the bank as one entry
or individual entries. The "clearing bank" feature is not relevant for AR Receipts. You must post AR
Receipt batches to the regular bank account, and set up the EFT File Type on the regular bank account
in EFT Banks.
Your payments would most probably be a combination of EFT and BPAY payments so you will need the
following setup:
In EFT Setup > Options > AP Tab > Check the box that says “Allow multiple banks for vendors”
Save the changes
Upgrade Steps
If upgrading from prior version, check the user formats and custom forms, Upgrading EFT Processing Key
Steps on page 40
Step 1: Install EFT Web Screens. Refer to Install EFT Web Screens on page 61.
Note: If you are already using EFT Processing for A/P and/or A/R, some steps may have been com-
pleted previously.
Step 3: Configure Bank/banks where the EFT payments will be generated from: EFT Banks Form - Over-
view on page 50
Step 5: Optionally, configure Email Messages to send advices to employees: Email Messages Setup on
page 57
Step 6: Optionally, update the EFT Payroll Advice form. Designing EFT Processing Forms on page 59
Tip: If upgrading from prior version, check the user formats and custom forms, Upgrading
EFT Processing Key Steps on page 40
Note:
EFT Payroll does not support CP/UP "Selection List" employee level security. Create EFT File, Print EFT
Remittance Advice and the EFT Payroll Log show all employees net pay details.
Lists of the Bank codes and other information you will use to set up the bank in EFT processing.
Determine where to save the EFT Files and how to upload. This can be on a network folder (you will
need a secure File path and naming convention), or a SFTP site (your own or provided by the bank)
Bank detailed specifications help select the correct bank format and upload details.
Customer EFT details
Vendor EFT details
You may be able to import EFT Processing Setup data. Refer to Sage 300 documentation for gen-
eral steps to import in Sage 300.
See Importing EFT Details on page 58
Review the security features options you want to implement in EFT Processing. EFT Security Features on
page 37
ADDING SECURITY
If your Sage 300 system requires user passwords and security profiles, you need to assign user security to
EFT Processing forms.
Approve Customer/View Unencrypted Bank Details - set a Customer's Bank details to Act-
ive/Inactive and view unencrypted Customers bank account details. Can only update the Active field, can-
not update other Customer bank details.
Options – add/modify EFT Options
View Audit Log – can view the audit log of changes to EFT Vendors & Customers details
Clear Audit Log – can view and clear the audit log of changes to EFT Vendors & Customers details
View EFT Log – can view the audit log of EFT Files created
Clear EFT Log – can view and clear the audit log of EFT Files created
Create Receipt Batch – can run EFT Create Receipt/Refund Batch
Select Remittance Advice Layout – can choose a different EFT Remittance advice at the time of
running
Edit Vendor EFT Details Setup – add/modify/delete EFT Vendor setup details.
Edit Customer EFT Details Setup – Add/modify/view EFT Customer setup details.
Receipt Selection Code Setup – can create and amend Receipt/Refund Selection Codes
Amend Receipt Exclusions – can amend Create Receipt Batch Customer/Document exclusion list
Update Invoice Due Dates – can update Invoice Due Dates
Delete Inactive Records – can run Period End Processing – purge inactive EFT Vendor and EFT
Customer records
View Unencrypted Bank Account Details – view EFT Banks unencrypted bank account details
Edit Vendor Remittance Password - can view& edit unencrypted vendor remittance password
Edit Customer Remittance Password - can view& edit unencrypted customer remittance pass-
word
Edit Employee Remittance Password - can view& edit unencrypted employee remittance pass-
word
Print/Email Payroll Stubs/slips - Security group required to be able to Print/Email paystub-
s/payslips in EFT Payroll.
Tip: If you want a user to View unencrypted details and be able to Edit details, you need to select both
Approve/View Unencrypted Vendor Bank Details" and "Edit Vendor EFT details Setup". Same with Cus-
tomer and Employee Bank Details.
Note:
EFT Payroll does not support CP/UP "Selection List" employee level security. Create EFT File, Print EFT
Remittance Advice and the EFT Payroll Log show all employees net pay details.
Tip: Only add a few users to a security group that can recreate files.
Tips:
For information on activating security and setting up security groups, refer to the System Manager
online Help (choose the Help menu on the Sage 300 desktop)
If you want users to be able to change the print destination, permission to Change Print Destination
must be assigned from the Administrative Services permissions list in the Security Groups form.
Audit logging
Audit logging is enabled in EFT Processing out of the box.
Details of any changes to Vendor/Customer/Employee records are recorded in an audit log, including
the Sage 300 user who did the change. There is also a detailed audit log of EFT Files created, including
the account details in the file and if records were skipped.
Audit log inquiries and audit log reports should be reviewed periodically.
EFT Options
Some EFT Options relating to EFT Vendors, Customers and Employees enhance the security of the pay-
ment processes:
Note: The Sage 300 ADMIN user can view unencrypted values.
Refer to EFT Options Screen Guide on page 97 and Adding Security on page 33 for details.
File security
File output destination
You need to use Network security to protect the file that is created. In many cases, the user who has
rights to create the EFT File in EFT Processing doesn't have access to upload and approve the file in the
banking software.
Using SFTP
Many people create an FTP site - where the person creating EFT files has no access. Only the users who
upload the file to the banking software have access to the FTP Site.
You can configure the EFT Banks to send the EFT files using SFTP, with a password or a key file.
Refer to Setup SFTP Output Destination on page 19 and the EFT Banks screen guide for details.
Note: Some banks provide access to their SFTP site, and EFT Processing can upload to the
File format
EFT Processing supports encryption using the MD5 algorithm as well as the SHA-256 algorithm
Note: Support for SHA-256 algorithm is only available in the latest product updates of EFT Processing
v2016 and above.
Many bank files contains control totals pertaining to the number of rows, total value of debits, total value
of credits so it is also hard (but not impossible) to change the file without the file becoming invalid.
Other banks actually contain a hash total on the amounts – which is very hard to manually change
without the file becoming invalid. If you were to edit the file manually, unless you knew the formula, the
file would be rejected by the bank.
More recently, some EFT file formats also include ‘security question & answer’ fields that require encryp-
tion at the time of file creation. They are also supported in EFT Processing.
This is something that should be discussed with your particular bank.
Note: Bear in mind that the banking software which imports these files usually has levels of security
and authority levels which can be defined. Typically the cheque signatories would be given the
“approval” level. So instead of reviewing the source documentation and signing cheques, as they
would have done in the past, they would review the source documentation and approve the EFT trans-
fer. This ensures that only approved payments are made and that the banking system reflects what
went through Sage 300 (Accpac).
Positive Pay:
EFT Processing supports Positive Pay files. Transitioning from paper cheques to secure electronic pay-
ments removes the opportunity for cheque fraud. Where payment by paper cheque is still required, EFT
Processing can still help reduce the risk of cheque fraud by generating ‘Positive Pay’ files for participating
banks. (The bank won’t honour presented cheques unless they match details on these files.)
A Positive Pay Format is a file format for check payments where the bank requires a file that contains the
check number, check date, amount, and vendor name. EFT Processing supports a number of Positive Pay
file formats for various banks.
Advanced options
You can also consider using Extender for more advanced encryption and approval options.
Refer to EFT & Other Orchid Modules
Tip: You need to do this in all companies and for all users who need access to the Process Flows,
including ADMIN.
Note: Only the ADMIN user and users who have the required security authorization can assign process
flows. For more information about security authorization, see "Administrative Services Security" in the
System Manager help.
Step 1: Run the EFT Processing installation program for the same version as the System Manager ver-
sion.
Example: If you upgrade from Sage 300 version 2023 to version 2024, you need to install
EFT Processing version 2024. This will create EL71A folder in your Sage program directory.
Step 3: Follow the prompts to confirm the file location of the Sage 300 programs and shared data dir-
ectory (these should be defaulted from the earlier Sage 300 System Manager installation).
Step 5: Enter the Serial Number and Activation Code in the EFT Processing License Screen.
User formats
Step 1: Transfer the custom format to the new version (or new server):
Locate the userformats.ini file in the Sage 300 programs directory, or customization dir-
ectory, in the previous version or old server;
Copy it over to the EL69A directory in the programs directory (or customization directory if
you are using customization directories).
Example: If you are upgrading from version 2021 to version 2022, you need to copy the
files from EL68A to the EL69A folder.
Step 2: Generate a test EFT File and compare the output to a file generated with a previous version.
Investigate discrepancies.
Tip:
If there is no userformats.ini file, then the customization must have been done in the formats.ini file. In
prior versions, it was possible although not recommended as changes can be overwritten when
installing a product update.
In the latest product updates, the formats.ini file includes a hash calculation to ensure the file is not
tampered with. If the file is amended in anyway, it cannot be used in Create EFT File and you will
receive an error message.
In this case:
Copy the format section into a new text file called userformats.ini
Save this file into the EL71A program (or customization) directory as required
Custom Forms
If you use Custom Forms for remittance advices, copy them to the new ELxxA>ENG folder or the cus-
tomization directory.
Test the custom layout.
Tip: Test sending emails. If the upgrade is done on a new server, you may need to adjust the details
used to send emails.
Copy the previous payslip report to the new version's directory (or redo changes based on the new
default Sage 300 report.
Export a range of EFT Employee email address
Import a tester's email address
Run the Print Payroll Payslip process.
Check the email subject and body , the attached PDF Content.
Confirm that the PDF password matches the formula/employee password
Re-import the EFT Employee email address
Setup EFT
EFT processing requires to setup Bank details, EFT Vendor details to process A/P Payments, EFT Cus-
tomer details to process A/R Receipt / Direct debits and A/R Refunds, and Message templates to email
remittance advices.
EFT Options 43
EFT Processing Email Tab 47
EFT Banks Form - Overview 50
EFT Vendors Overview 52
EFT Customers Form 53
EFT Employees 55
EFT Setup - Receipt/Refund Selection Codes 56
Email Messages Setup 57
Importing EFT Details 58
Designing EFT Processing Forms 59
Warning!
After the initial setup, you can change any of the selections and information you entered in
Before changing any of the settings or other information in the EFT Banks form, make sure
you understand the impact the options have on processing with your Bank.
EFT OPTIONS
BEFORE YOU START
Before setting up EFT Processing (A/P and A/R), gather vendors and customers bank details and
email addresses to send advices.
Before setting up EFT Processing (Payroll), gather employee bank details and email addresses to
send advices.
Overview
On the EFT Processing Options screen, you can select options that specify how EFT files are generated
and how documents are emailed.
For details on each Tab, EFT Options
A/P Tab
For details, A/P Tab Fields and Controls on page 97
Select whether an EFT file can be created for a range of AP Payment batches..
Allow unposted AP Payment batches to be selected.
Select whether or not payments for Vendors not defined in EFT Processing are skipped without
generating an error.
Make selective payments from an AP Payment batch.
Select whether a File Sequence Number or Batch Number is used when creating the output file
Select default EFT Vendor status
Select whether to encrypt Bank details.
Select whether and how to password protect remittance advices.
A/R Tab
For details, A/R Tab Fields and controls on page 102
Select whether an EFT file can be created for a range of AR Receipt batches..
Allow unposted AR Receipt batches to be selected.
Select whether or not receipts for Customers not defined in EFT Processing are skipped without
generating an error.
Make selective receipts from an AR Receipt batch.
Select whether a File Sequence Number or Batch Number is used when creating the output file
Select whether to encrypt Bank details.
Select whether and how to password protect remittance advices.
Using a primary bank, field names can be tailored to the bank and optional extra fields can be enabled
for Vendors, Customers and Employees.
Payroll Tab
For details, Payroll Tab Fields and Controls on page 110
Select whether an EFT file can be created for a single Payroll Pay period or from a range of payroll
Pay periods.
Select whether or not payments for Employees not defined in EFT Payroll are skipped without gen-
erating an error.
Make selective payments from a Payroll Pay Period.
Select the default employee record status for new records.
Select the default primary bank for EFT Payroll files. If blank on the Employee setup,
then the EFT file type defined in EFT Options will be used in formatting the
EFT Employee screen.
Select whether to encrypt Bank details.
Select whether and how to password protect remittance advices.
Define the name of a SMTP server and associated e-mail user, password etc to send payroll
advices using SMTP.
If details are left blank and the SMTP Details are filled in EFT Options > A/P Email, EFT Processing will use
the EFT A/P Email details.
If both A/P Email and Payroll Email details are blank, EFT Processing will use the Sage 300
System Manager configuration.
Refer to EFT Processing Email Tab on the facing page for details on the fields and examples of
SMTP configuration.
Updates Tab
NOTIFY ME WHEN THERE ARE NEW UPDATES IN EFT PROCESSING
Users can now "subscribe" to notifications of updates.
By Default, this option is not selected for end-user serial numbers
The check is stored in the registry and it applies to this Windows user on this computer.
If selected, when starting Sage it will check if there are product updates available for EFT Processing
If there is a new update, and the user hasn't previously been notified of it, then the Options screen
will open automatically on the Updates tab and display details of the new updates.
Tip: The “administrator” or “super user” or “owner” of Sage 300 should have this option
Note:
If you cannot view the Tab you require, check your activation code and which components of the mod-
ule have been purchased.
Depending on the components you are licensed to use, some features described here may not be avail-
able for you to use. Some functionality of EFT Processing is only active if you have purchased the
required module component.
The license screen displays what components of the EFT Processing module are included in the activ-
ation code.
Email Service
SMTP (Simple Mail Transfer Protocol). You can use your own SMTP server, or an
SMTP service.
Microsoft Graph. This service sends email via Microsoft Office 365. It is generally used
when SMTP Basic authentication is not enabled in Office 365.
Refer to Office 365 and Microsoft Graph
If you leave the SMTP details blank in EFT Processing> Options Tab, the Sage 300 default way of sending
emails will be used. However, the program cannot verify that the email has been sent and cannot report
the number of emails sent. If you want to use the ability to password protect the PDF attached to emails
in EFT Processing, you need to use EFT's SMTP options. Refer to Using Sage Company Profile Settings on
page 49
Tip: You can specify a port number after filling in the email server details. After the
email server name, enter “:xx” i.e. colon xx where xx is the port number
required. Example: smtp.domain.com:587
Email User and Email Password: Enter a correct combination of Email user and pass-
word
Note: If using multi-factor authentication and App password, enter the App pass-
word you create in he Email Password field. Refer to Using Orchid Modules with
Office365 App Passwords on page 115
Email Comes From: Enter the email address to be used when sending email.
Note: Depending on the SMTP server you use, this address may need to
match the one you enter in the Username field, or may not work unless
you set up an email alias. Consult your SMTP server documentation for
Microsoft Graph:
This service sends email via Microsoft Office 365 where basic authentication is not enabled to use SMTP.
Refer to Office 365 and Microsoft Graph
Tenant ID. Enter the tenant ID (alternatively called the directory ID) from your Microsoft 365
account.
Client ID. Enter the client ID (alternatively called the application ID) from your Microsoft 365
account.
Client Secret. Enter the client secret from your Microsoft 365 account.
Tip: This is actually the secret value, not the one called Secret ID. It is the one that
you only see once when you first create the client secret.
From Email Address. Enter the email address to be used when sending email.
Examples
Refer to the examples below for detailed settings with commonly used mail providers, such as Office 365
and Gmail.
It will use SMTP or Microsoft Graph depending on the option selected on the Company Profile,
If the details are not filled in, it will use Microsoft Outlook if installed on the client machine.
For more details, refer to Emailing from Sage 300 in Sage 300 documentation.
Important!
If you want to use the ability to password protect the PDF attached to emails in EFT Processing, you
need to use EFT's SMTP options.
Similarly, if you want to save a copy of the Payslip/paystub in the directory configured on the EFT
Setup> Options > Default Advice Tab, you need to fill in the A/P Email or the Payroll Email SMTP
details. If emails are sent using default Sage's configuration through Outlook, a copy of the file will not
be saved.
If you are getting errors relating to "exceeding limits" when sending email remittance advice, you can
configure the options to Number of emails per minutes or Number of emails per session to match the
requirements of your email server.
Defaults to "None".
Choose Per Minute if your email server has a limit per minute when sending
SMTP emails (e.g. Office 365).
Choose Per Session if your email server has a limit per session.
Enter the number of emails to send per minute or per session.
When printing Advices and if the number of advices is greater than the limit, EFT will send the number
entered in the limit, then pause if "per minute" is selected or Disconnect and start a new session if using
"Per session" is selected.
Example: Limit per minute: If you set the limit to 30 per minute and you email 50 remittance advices,
EFT Processing will send the first 30, pause for a minute, send the next 20, and will then display the res-
ult.
Example: Limit per session: If you set the limit per session to 10 and you select to Print/Email a batch
of 50 remittance advices, EFT Processing will make a connection to the SMTP Server, send 10 emails (1
to 10), disconnect, then reconnect, send the next 10 emails (11 to 20), disconnect, connect again, send
the next 10 emails (21 to 30), disconnect, etc. When all emails are sent, it will display the delivery res-
ults.
Note: If you set the number of emails to 0 (per minute or per session), the emails will be
sent with no limits (the same way as with the "None" option)
Note: The field labels are renamed for different banks depending on the bank formats setup in Format-
s.ini, when the file type is selected on the Payments and Refunds Tab, Receipts Tab or the Payroll Tab
See Also
If using a clearing bank to facilitate bank reconciliation, refer to Setup and Use EFT Clearing Bank on
page 25.
If you upload the file to a FTP Site (yours or one provided by the bank), Setup SFTP Output Destination
on page 19.
For details on how to use each field, view EFT Banks Setup Screen on page 130
Note: If the EFT File format includes the File Sequence Number, you generally select the
"File Sequence Number" option to name the file. If you select Batch Numbering to name the
file, EFT Processing uses the batch number as the [FSN] value.
Batch Number : the file will be called APbbbb.{ext} or ARbbbb.{ext} where bbbb is the batch number
being exported.
Pay Period End Date YYYYMMDD: for EFT Payroll files
Fixed File Name : User defined file name using any characters plus the following variables in the file
name :
{yyyy} for the year, {mm} for the Month, {dd} for the Day
{bbbb} up to 4 numbers for the batch number
{N} gives you a running number starting from 0 each day. This is often used in conjunction with
batch number to keep track of the number of exports in a calendar day.
{S} gives you a running sequence number for the selected bank- You can use up to 4 numbers for
the file sequence number. You typically use this option instead of batch number for a unique num-
ber per file.
{entry} for the entry number, this works with option that each entry to be generated in a single file.
Example: You can use up to 4 digits for {B}, {S} and {N}
Example for Batch Number 2
{b} for 1 digit, e.g. 2
{bb} for 2 digits, e.g. 02
{bbb} for 3 digits, e.g. 002
{bbbb} for 4 digits, e.g. 0002
Global Sequence 1..10. You are able to share a Global File Sequence number between multiple
banks if required. EFT Processing will increase the global file sequence number used by one after cre-
ating the file.
Note: If the EFT File format includes the Global File Sequence Number, you need to select the "Global
File Sequence Number" option to name the file.
Receipts Tab
Use this Tab to configure how EFT Processing creates files for Direct Debit Transactions
Payroll Tab
Use this Tab to configure how EFT Processing creates files for payroll payments.
Important! Before changing any of the settings or other information in the EFT Banks
form, make sure you understand the impact the options have on processing with your
Bank.
Choose Vendor number from the Finder or type the Vendor code
Remit To (Optional) : Use this when you have A/P Vendors with different bank account details for
different transactions. When creating the A/P Payment, you can select the appropriate Remit-to
code (and therefore the correct bank details. This applies to the Vendor's bank account details.
File Type (Optional): The “file type” on the EFT Vendor allows you to specify different bank
account details for your EFT vendors/EFT customers depending on the bank or file type you are
using to make EFT Payments.
Note: This field is only available if the "Allow multiple Vendor bank account Details,
one per EFT File type" is ticked in EFT Setup > Options> A/P Tab.
Tip: If you only make EFT transactions from one bank account and only have one EFT File Type
in use, do not select this option and use the default EFT File Type. This simplifies the data entry
and reduces the risks of duplicate account details.
Delivery Method and Email To: Configure how to send remittance advice.
Status needs to be Active to use the record (EFT Vendor, Customer or Employee) in the
Create EFT File process.
Example:
You can control who is allowed to make vendors “active” and “inactive” using the
Approve/View Unencrypted Vendor Bank Details security group.
Refer to tutorial on Approving changes of EFT Vendor/Customer/Employee details on
page 17
Tip: When importing EFT Vendors, EFT Customers and EFT Banks, you should not
import the Encrypted Bank Branch and Account number and Credit Card Number
These fields should only be set using the associated views, and set to the cal-
imported. Fields starting with X (binary XBSBNO and XACCNO) shouldn't be in the
import file.
Choose Customer number from the Finder or type the Customer code
File Type (Optional)
Note: This field is only available if the "Allow multiple Customer bank account
Details, one per EFT File type" is ticked in EFT Setup > Options> A/R Tab
The “file type” on the EFT Customer allows you to specify different bank account details for
your EFT vendors/EFT customers depending on the file type (or Bank File Type) from which
you are depositing for EFT Direct Debits.
For your EFT Direct Debits, if you
Note: You can use the Credit Card Tab to use Credit card details to generate the Direct
Debit file. The fields are encrypted in the database, but please note that EFT Processing
module is not PCI compliant and that Orchid takes no responsibility for the use of asso-
EFT EMPLOYEES
Use this form to add EFT details for Employees defined in Sage 300 Payroll (US or Canada).
Main Fields
For detailed field description, see EFT Employees- Setup Screen on page 144
File Type is Optional . If you leave this field blank, then EFT will use the file type that has been
assigned in EFT Options > Payroll Tab > Primary Bank.
Status : select one of Entered, Active or Inactive. You can only include "Active" Employees when
you create EFT File
You can control who is allowed to make Employees “active” and “inactive” using the Approve
/View Employee Bank Account Details security group. See Step 2, Adding Security on page 33
Tip:
You can import new EFT Employees from the File > Import Menu. You cannot update details of exist-
ing EFT employees through import.
When importing EFT Banks, EFT Vendors, EFT Customers and EFT Employees, you should not import
the Encrypted Bank Branch and Account number and Credit Card Number fields (fields containing an
"X"). These fields should only be set using the associated views, and set to the calculated encrypted
value. EFT Import functionality prevents such fields to be imported. Fields starting with X (binary
XBSBNO and XACCNO) shouldn't be in the import file.
Tip: In most cases, the last rule should be set to Calculation Type "% Net Pay " and Percent = 100.
This means that any amount remaining after the previous rules have been applied will be trans-
ferred to the account set in that line. If the pay is to be paid to a single account, you only need to
enter one line with "% Net Pay" as the Calculation Type and set the Percent to 100
Example:
In the screenshot below, EFT Payroll will create a line in the file for $300 to CIBC and the remainder of
the pay will be transferred to RBC.
If the pay is $250 for the week, only one line will be created. If the pay for the period is $400, it will cre-
ate 2 lines, one for $300 and one for $100.
Note: (*) Field names might be different depending on the Default Bank File Type set up in
EFT Options > Payroll Tab for EFT Processing (Payroll) or File Type entered on the
Steps To Setup
For detailed field and controls description, EFT Setup- Receipt/Refund Selection Codes - Field List on
page 162
Note:
Email subject can also include variables
For example, Payment from {COMPANY_NAME} will replace {COMPANY_NAME} with the Sage 300
company name defined in Company Profile.
Example:
You can use the following sample e-mail messages for the different types of advices in
EFT Processing. Copy and paste into the Email Message screen.
Refer to Sample EFT Email Messages on page 160
Open the appropriate EFT Setup form for the type of data you want to export.
Example: To export EFT Vendors, open the EFT Vendors Setup form.
Tip: You can save your choices as a template for the next time you import records.
Tip: For information on the file formats and file layouts that Sage 300 accepts, you can create an
import file template by exporting a few records of the type you want to import.
Note:
When importing EFT Vendors, EFT Customers, EFT Employees and EFT Banks, you should not import
the Encrypted Bank Branch and Account number and Credit Card Number fields (fields containing an
"X"). These fields should only be set using the associated views, and set to the calculated encrypted
value. - EFT Import functionality prevents such fields to be imported. Fields starting with X (binary
XBSBNO and XACCNO) shouldn't be in the import file.
It is recommended to remove credit card details fields when importing bank accounts: , these fields
must be removed from the import file ‘CCNUMBER’, ‘CCECP’, ‘CCNAME’ and ‘XCCNUMBER’.
When importing EFT Employees, you can only insert new records. You cannot update existing employ-
ees as the records include header and details information.
EFT Processing installs with the following A/P remittance advice formats, with different payment for-
mulas:
ELPAY01 – payment date is based on the date when the EFT file was created/generated.
ELPAY02 – payment date is based on the the Batch Date.
ELPAY03 – payment date is based on the Batch Entry Date.
ELPAY05 – payment date is based on the effective date selected when the EFT file was cre-
ated/generated. This only applies if the EFT format you use supports effective date.
ELREC01 – payment date is based on the date when the EFT File was created/generated.
ELREC02 - payment date is based on the receipt entry date.
ELREF01 – payment date is based on the date when the EFT File was created/generated.
ELREF02 - payment date is based on the refund entry date.
Note: EFT Processing web screens rely on the Sage 300 web screens being installed and configured.
Available screens 60
Install EFT Web Screens 61
Using EFT Web Screens 62
AVAILABLE SCREENS
With the July 2023 release, the following screens are available in the web screens:
EFT Setup
Options
Banks
Customers
Vendors
E-mail Messages
EFT Transactions
Transfer Details
Transfer Created
Print Advices
Audit Log
Receipt Batch Audit Report
Update Invoice Due Date Audit Report
Banks
Customers
Vendors
Requirement! Web Screens for EFT Processing are only available if you have a subscription license for
EFT Processing.
Check your existing codes on the EFT License screen. If you have a subscription code, you can view the
expiry date. EFT Processing License Screen on page 13
Tip: Contact your Sage 300 business partner if you have a perpetual licence and want to run the web
screens. They can organise a switch to a subscription licence.
Note:
No serial number / license required if the customer has not purchased Extender. ADMIN only has
access to the Extender Options and License screens.
If the customer has a license for Extender (Configurator, Developer or Runtime, Perpetual or Sub-
scription), web screens are enabled.
Setup Tips
EFT Options : Default Advice finders - You can use the finder to select the AP Remittance Advice.
For the AR Remittance Advices finders, please type the Advice name or use the classic desktop screens to
use the Finder.
Refer to EFT Options Default Advice Fields and Controls on page 107
Output destination
On the web screens, there is no finder to select a file path. If you choose File as the Output Destin-
ation, you need to copy and paste the file path. The file path needs to be a folder that the network user
has access to.
When using the web screens, the network user is not the user logged in the machine. It is the user con-
figured in IIS Authentication for the Sage 300 site. It can be the default IUSR account, or a configured net-
work user. It can also be configured on the Application Pool Identity.
Note: To use File in EFT Banks, check the user configured in IIS and ensure it has rights to the
folder used in EFT Banks. Use UNC Path and IP Address to ensure that the folder name exists for the
network user configured in IIS.
Example: If you use c:\Temp, is it looking for the C drive of the App server (which users won't have
rights to).
If you want to save the EFT File to a local file, choose “Download” and EFT will use the browser’s down-
load settings to save the file locally.
Depending on your browser settings, the file will be saved in your default Download folder or the
browser will prompt you to select a location.
Tip: Use SFTP if you don't want to download the file to a local machine or to the server. EFT Processing
will upload the file directly to the configured SFTP Site. When using SFTP with Key file, copy the key file
in the Sage 300 Shared Data folder to ensure the network User configured as the IIS website or Applic-
ation pool Identity has access to it.
Refer to EFT Vendors Overview on page 52 for more details on EFT Vendor setup.
Your logon profile to the network gives you access rights to the directory where the files have
to be created (as set in EFT Banks setup).
Confirm which Payment , Receipt or Refund batch number you want to use.
Enter Details
Batch Type: Select whether you want to process a Payment , Refund or a Receipt batch.
From Batch: & To Select a batch number or range of batch numbers to be exported (using the Finder).
Tip: Use the drill down icon to open the batch screen and check it if required.
File Type: defaults to the file type of the bank entered in the Payment/Refund/Receipt batch selected.
Note: You can only select a range if "Allow EFT File creation from a batch range" is set to Yes
on the EFT Options > A/P Tab. If using a range, the file type will be the bank layout of the
first batch selected.
Note: Description and Reference appear on the vendor bank statement if a variable ref-
erence is included in the bank's file.
If a vendor is not defined: Select Skip the vendor... if you want the file export to continue
without errors and skip the transaction or
Display an error and abort to generate an error and abort the export if the vendor/customer is
not defined in EFT processing.
Note: You can only select "Skip the vendor and continue the export" if the option is selected
on the EFT Options > A/P Tab.
Include in EFT File: If using Selective payments to select or remove a payment from a posted batch:
Select All entries in the batch to include all entries in the selected batches, or
Entries that I select to include only selected entries.
If selected entries is chosen, click the Selected Entries button and ensure you select (x) all the entries you
wish to include in the EFT file. Only those marked entries (x in the Include in EFT File) column will be trans-
mitted to the bank.
Tip: You can use the Select All and Deselect All buttons to assist in transaction selection.
Tip: When using the web screens, you can use the Space bar or Double Click to toggle the
selected / deselected entries.
Note:
You can only select entries for A/P Batches if "Allow Selective Payments from an A/P Batch
?" is set to Yes on the EFT Options > A/P Tab.
You can only select entries for A/R Batches if "Allow Selective Payments from an A/R Batch
?" is set to Yes on the EFT Options > A/R Tab.
Effective Date: This field is only available in certain user file formats.
Note: It is usually used in userformats.ini when they want to control when the payment date
should be. Note that we don’t store this effective date anywhere in the EFT audit logs.
You can then submit the file via your desktop banking software.
If your bank supports SFTP, EFT Processing can upload the file directly using the bank's SFTP
details configured in EFT Banks Setup Screen on page 130
Note: The screen displays the EFT file path from the EFT banks setup for the bank
associated with the batch. If you don't have access to the file (drive not mapped
on a server, user security does not have rights to the directory), EFT processing
Tip:
To save the settings used regularly, use the standard Sage 300 functionality in the Settings
Menu > Save Settings As Default.
Save Settings saves the following fields: Description, Reference and Skip/Display error for
each batch type.
Recreating a file
If the file has already been exported, you are prompted to re-create the file.
For details, refer to Recreating an EFT file on the next page
EFT Processing :
makes a single entry in the EFT File for each AR Refund Entry regardless of the number
of banks entered on the AR refund entry.
assumes all the entries in the batch / file are for the same bank which is derived from
the first AR Refund entry
Because EFT Processing creates only one entry in the EFT File for AR Refunds, the selection of the
amount and the bank to use is based on the following logic :
Use the check amount bank if the check amount is not zero, otherwise
Use the cash amount bank if the cash amount is not zero, otherwise
Use the first c.c. bank if there are cc entries
Tip: It is recommended for processing EFT payments for AR Refunds that you
Create the refund based on one amount only per entry (either Check, Credit Card or Cash)
Use the same bank for all AR Refunds in the same Refund Batch.
If you need to refund some amounts from the Cheque Payment and another amount to the
CC Bank, you will need to create a separate AR refund entry in a new batch.
Note: This is a new security option in the latest EFT product updates for Sage 300 versions 2019 and
above (October 2021).
Depending on the file naming in EFT Bank configuration, recreating the file will overwrite the file or cre-
ate a new file.
Tips:
If using File Sequence Number, you can reset the number in EFT Banks to reuse a sequence.
If using Global Sequence Number, you can reset the number in EFT Options.
Note:
If you get an error "This EFT File has already been created", the user doesn't have rights
to "recreate EFT File".
Related tasks
Note: You must create at least one receipt selection code in EFT Processing Setup before
Tip: You can update the invoice Due Date if required to ensure the invoice can be selected
in the "Create Receipt Batch" run. Refer to Update Invoice Due Date on page 73
How to use
The default values are determined by the Receipt/Refund Selection Code. You can amend the values for
the specific receipt batch you need to create.
See EFT Setup - Receipt/Refund Selection Codes on page 56
Enter a Receipt/Refund Batch Date .
Update the default batch and entry descriptions if required.
Select "Create" to generate the batch.
Note:
You can create a single receipt per invoice, or group all outstanding invoices in a single receipt per
customer:
Select Yes if you want separate receipts per outstanding invoice,
Select No to include all invoices in a single receipt per customer.
Note: If the customer's net balance is in credit, you can then use "Create A/R Refund batch" to create a
refund applied to the pending credit transactions.
Tips:
You need to select at least one of Credit Notes, Prepayments or Unapplied Cash on the Documents
Tab.
When creating Zero value A/R Receipt batches, EFT Processing evaluates the credit balance based on
the selection parameters. Invoice and other debit balances are applied to the credit balance until the
balance is zero.
If the credit balance is greater than the Debit balance, the most recent credit transaction will end up
with a pending balance. If the debit balance is greater than the credit balance, the most recent debit
transaction will end up with a pending balance.
Tips:
When creating A/R Refund batches, ensure A/R Receipt batches are posted before
When creating A/R Refund, if you only want to refund customers with a net credit bal-
ance, set the From Customer Balance to the lowest negative number you want to
Payment Type:
The payment type "CASH or CHECK" configured on the Payment Code in Accounts
You can amend the payment types before posting the A/R Refund batch if you don't
Important! All remittance advices can only be sent (emailed, printed or previewed) if the EFT file has
been created first, as details come from the EFT Audit Logs.
Check the Delivery method and email address used in EFT Vendor setup ( EFT Customer for
AR Advices). Refer to EFT Vendors - Setup Screen on page 137 for details.
Check Email Message templates. Refer to Email Messages Setup on page 57
Update account information by entering, importing, and posting batches.
Submit the batch via EFT using the EFT Transactions > Create File option
Tip: Choose Browse (click the Browse button or press the Alt and B keys together) if you are not sure
of the name of the form, then select the form from the list that appears.
EFT Processing installs with the following A/P remittance advice formats, with different payment for-
mulas:
ELPAY01 – payment date is based on the date when the EFT file was created/generated.
ELPAY02 – payment date is based on the the Batch Date.
ELPAY03 – payment date is based on the Batch Entry Date.
ELPAY05 – payment date is based on the effective date selected when the EFT file was cre-
ated/generated. This only applies if the EFT format you use supports effective date.
ELREC01 – payment date is based on the date when the EFT File was created/generated.
ELREC02 - payment date is based on the receipt entry date.
ELREF01 – payment date is based on the date when the EFT File was created/generated.
ELREF02 - payment date is based on the refund entry date.
Tips: To set Default Advice Form, use Default Advice Tab in EFT Options Screen
Guide on page 97
Message ID: This field appears when you select Customer/Vendor for the Delivery Method.
Select the code for the e-mail message you want to send with these statements.
Note: To set up messages for AP remittance advice, AR Direct Debit Advice or AR Refund
Advice, refer to EFT Setup - Messages.
Additional options
Remit-To Address/Details. This field appears when you select Customer/Vendor for the Delivery
Method and you have selected A/P Payment batch from the Print option.
Tip:
Select this option if you want to use the Remittance address / e-mail addresses on the remittance
advice.
If Delivery Method in A/P Vendors is set to Email (contact), EFT will use the email address in the Remit-
to contact Tab.
If Delivery Method in A/P Vendors is set to Email (eEndor), EFT will use the email address in the Remit-
to Address Tab.
If there is no remittance code on an individual payment, the vendor address / e-mail details will be
used as per the A/P Vendor delivery method.
From Batch .. to Batch. Select the batch range you wish to print/deliver.
From Entry … to Entry. If you select only one batch, you can select an entry range within the batch.
Only the selected entries will be printed/delivered
Tip: If you select more than one batch, you cannot select an individual entry within the
batches, all entries will be printed/delivered.
Check this box if you want to send an email...: Use this to resend an email, for example if you have
updated an email address after sending the first email.
Tip: This option is only enabled if you configure Email details in EFT Options > AP Email. If
you are using Sage Company Profile or Outlook, EFT can't check if the email has already
been sent.
Click Print
If you need additional copies of Remittance Advices, or earlier processing was halted, simply repeat the
process.
After printing/emailing EFT Remittance/Direct Deposit advices, a list of which remittance advices which
were not sent/printed, and the reason why, is displayed.
FOR MORE DETAILS ON REASONS:
Note: When printing Advices with number of advices greater than the limit, EFT will send
the selected number, then pause if "per minute" is selected or Disconnect and start a new
session if using "Per session" is selected. This is configured in EFT Options. Limit Sending of
If a password has been entered in the EFT Vendor’s Remittance Password field, then
this password will be applied to the remittance PDF document.
If a password has not been entered in the EFT Vendor’s Remittance Password field, then
the EFT Options \ AP Password Formula will be used to generate a Vendor-specific pass-
word to be applied to the remittance PDF document.
If no password formula exists for either of those fields, then the PDF document will not
be encrypted.
If a User Password and Master Password both exist, then encryption of the PDF doc-
ument will take place using both passwords.
If a User Password exists, but no Master Password exists, then encryption of the PDF
document will still take place, using the User Password only.
If no User Password exists, then no encryption of the PDF document will take place,
whether or not a Master Password exists.
Refer to:
Password Examples on page 152
Password Formulas on page 148
If a password has been entered in the EFT Customer’s Remittance Password field, then
this password will be applied to the remittance PDF document.
If a password has not been entered in the EFT Customer’s Remittance Password field,
then the EFT Options \ AR Password Formula will be used to generate a Customer-spe-
cific password to be applied to the remittance PDF document.
If no password formula exists for either of those fields, then the PDF document will not
be encrypted.
If a User Password and Master Password both exist, then encryption of the PDF doc-
ument will take place using both passwords.
If a User Password exists, but no Master Password exists, then encryption of the PDF
document will still take place, using the User Password only.
If no User Password exists, then no encryption of the PDF document will take place,
whether or not a Master Password exists.
Refer to:
Password Examples on page 152
Password Formulas on page 148
Refer to Visual Process Flow for key steps of using EFT processing - Payroll. Assigning Visual Process
Flows
Your logon profile to the network gives you access rights to the directory where the files have to
be created (as set in EFT Banks setup).
Note: Typically, if you only run Generate Payroll once for a Payroll End Date, then these two fields can
be left with the default values. Alternatively, if you run Generate Payroll more than once for a Payroll
End Date, then you should use the From/To Check/Cheque Number fields to separate the transactions
required for each file.
For examples of steps to create EFT Payroll files depending on how you process the payroll, see Create
EFT Payroll File - Example processes below
Choose Create to create the file.
You can then submit the file via your desktop banking software.
Recreating a file
If the file has already been exported, you are prompted to re-create the file.
For details, refer to Recreating an EFT file on page 68
Important!
If you have already created a file for the Bank/Pay Period End Date, you will receive a warning to con-
firm that you really want to re-create the file. If the files include the same employees, the remittance
advice will include details from both files. It is suggested to send the remittance advices from the
"View'Clear Payroll log" in EFT Periodic Processing and select an individual EFT file creation number.
See details in View/Clear Completed EFT Payroll Logs on page 167.
Note: The screen displays the EFT file path from the EFT banks setup for the bank asso-
ciated with the batch. If you don't have access to the file (drive not mapped on a server,
user security does not have rights to the directory), EFT processing cannot create the file.
Example:
If you run Weekly pays with a Payroll Period End Date of 31st March, you may:
If you then prepare the Fortnightly pays with a Payroll Period End Date of 31st March, you may
And when preparing the Monthly pays with a Payroll Period End Date of 31st March, you may
Alternatively, if you want one single EFT file for the Payroll Period End date, then you would do the above
steps “Run your pays” to “Post the cheques” for each individual pay run.
You would then create a single EFT Payroll File, leaving the defaults for the From and To Cheque num-
bers.
This report is used to create Payroll Advices (for EFT Files created from Payroll run). It includes details of
the payment bank accounts, amount and date, but no details about the payroll.
The advices can be printed (if you select Delivery method = Print destination) or emailed (if you select
delivery method Employee).
You can print and reprint Payroll Advices for the individual employee based on a Pay Period End Date
range selection.
Orchid EFT Processing comes with two sample remittance advices for Payroll:
ELPR01.rpt: The report shows the check date. The report uses a SQL Command.
ELPR02.rpt: This report uses the Payroll period end date (new in July 2023 for versions 2021 and
above).
You can use one of the default reports or change it to suit your company's requirements, as described in
the appendix on customizing forms in the System Manager User Guide.
Tip: To email a payslip/paystub with pay details from Sage 300 payroll, refer to EFT Print Payroll Stub-
s/Slips on page 84
Tips: For details on the Sample Remittance Advice included in EFT Processing, see Default
Tips: For more information, see the appendix on customizing forms in the System Man-
Use Report. Select the name of the statement form to use. Choose Browse (click the Browse but-
ton or press the Alt and B keys together) if you are not sure of the name of the form, then select
the form from the list that appears.
Message ID. This field appears when you select Employee for the Delivery Method. Select the
code for the e-mail message you want to send with these statements.
To set up messages for Payroll advice, refer to EFT Setup - Messages.
From Pay Period End Date ... to Pay Period End Date. Select the pay range you wish to
print/deliver. If you select more than one pay period, you cannot select an individual employee,
all entries will be printed/delivered.
From Employee… to Employee. If you select only one batch, you can select an employee range
within the batch. Only the selected entries will be printed/delivered
3. Click Print.
If you need additional copies of Advices, or earlier processing was halted, simply repeat the process.
Note: After printing/emailing EFT Payroll advices, a list of which advices were NOT sen-
Tip: When printing Advices with number of advices greater than the limit, EFT will send the
selected number, then pause if "per minute" is selected or Disconnect and start a new ses-
Tip:
The EFT Option "Use Remittance Advice Password" on the Payroll Tab comes into effect when emailing
Employee advices and related documents.
For details, see Using password to protect Payroll Advices and other Payroll PDF for Employees on
page 89
Note:
User needs to be in a EFT Security group that has rights to "Print/Email Payroll Stubs/slips".
User needs to be the same user who is running the Payroll Print Checks function. This means a user can
only Print/Email payslips for employees that they have access to in Canadian/US Payroll.
1. Calculate Payroll
2. Run Payroll Checks/Cheques process.
3. Most users choose to Print the checks for Payroll to assign a Cheque Number.
4. Do not answer the question "were all cheques printed successfully?" and leave the
Payroll Print Checks screen open
5. Run EFT Print Payroll Stubs/Slips with the Print Checks /Cheques screen still open, before posting
the cheques.
Note: This is required as Create Payroll EFT File requires content from the payroll temporary tables.
Tip:
The pay stubs are grouped by Delivery Method and then processed per employee.
EFT first processes all employees configured with Mail delivery method option - if you set the
print destination to Printer, then EFT will print all pay stubs in one go.
EFT then processes all employees with Email option. While the emailing is in process, the user
can open any other Sage 300 screen and continue working.
EFT print/email screen can be left open in the background. The screen might flicker when it sends an
email, but it no longer acts as the main focus.
IF YOU DON'T NEED TO INCLUDE THE CHEQUE NUMBER ON THE FORM, YOU CAN
USE THIS METHOD
After using Print Checks/Cheques, and assigning Cheque Numbers you answer “No” to “Check-
s/Cheques printed successfully”.
In this case, the cheque numbers are not assigned and the payslip form must be amended as per
below.
The report must be amended to allow Bank Register entries with a “Printed” status (9). To do this, in
the default Pay Slip Crystal Report, in the Record Selection formula you must remove the line :
‘{BKREG.STATUS} = -1.00 or {BKREG.STATUS} = -2.00 ) and’
This line only allows records with status = -1 (Advice Not Printed) and -2 (Not Printed).
Important! You can only Print/Email Payroll Stubs/Slips if you leave the Print Cheques screen open or
answer "No" to the "Were all checks printed successfully?".
Once you answer YES, the cheques/checks are posted and are not available to be reprinted/emailed.
Delivery Method: Select Employee to email payslips where the employee's Delivery
method is set to EFT Email or Payroll email. It will print payslips if the Employee's deliv-
ery method is set to Mail.
Select Print destination to print/print preview all payslips regardless of the delivery
method.
Use Report: Select the required C/P or U/P sample Payroll Stub.
Message ID: Select the email Message ID for the template subject and body of the
email to be sent to the Employee
Select the required range for Payroll Period End Date
Select the required range for Employees
Select “Check this box if you want to send an email even if an email has already been
sent for this entry” to resend all Payroll Stubs in the selection criteria.
Click “Print” to send the emails.
Note:
If the Payslip/Paystub Print Directory from EFT Options \ Default Advices tab is filled in, EFT Processing
will:
required
If a Remittance Advice Password formula was entered on the EFT Employee, then this
password will be applied to the generated PDF, the PDF will be attached to the email,
the body and subject of the email will be based on the required “Message ID”
If an Employee Master Password was defined on the EFT Options \ Payroll Tab, then the
Employee Master Password will also be applied to the generated PDF.
The email address defined on the EFT Employee will be used
Configuration references
EFT Options -
Select Report filename - Payroll Payslip/stub report on page 108
Password protect - Use Remittance Advice Password? on page 111
Email Configuration - Payroll Email Tab field and controls on page 112
EFT Employees -
Configure email addresses - Refer to Delivery Method on page 145
The Use Report will default to the email Message ID on EFT Options \ Remittance
Advice tab, or the user’s Preferences if used previously
Select the email Message ID for the template subject and body of the email to be sent
to the Employee
Select the required Year
Select the required range for Employees
Click “Print”.
All employees in the range selected will be emailed their Relevé 1s. The email address from the EFT
Employee will be used. If you have enabled the PDF password for EFT Remittance Advices on EFT
Options \ Payroll Tab, then
If a Remittance Advice Password formula was entered on the EFT Employee, then this
password will be applied to the generated PDF, the PDF will be attached to the email,
the body and subject of the email will be based on the required “Message ID”
If an Employee Master Password was defined on EFT Options \ Payroll Tab, then the
Employee Master Password will also be applied to the generated PDF.
The email address defined on the EFT Employee will be used
Use Report defaults to the report selected on EFT Options > Default Advice tab
Select the email Message ID for the template subject and body of the email to be sent
to the Employee
Select the required Year. If no year is entered, the screen displays an error message and
no processing takes place.
Select the required range for Employees
Click “Print”.
All employees in the range selected will be emailed the T4s report if there has been activity in the selec-
ted year.
The email address is the email address from the EFT Employee.
The PDF will be attached to the email, the body and subject of the email will be based on the
required “Message ID”
If you have enabled the PDF password for EFT Remittance Advices on EFT Options \ Payroll Tab,
then the PDF has a password.
Note: For details on using Password to encrypt PDF, refer to Using password to protect
Payroll Advices and other Payroll PDF for Employees below
If a password has been entered in the EFT Employee’s Remittance Password field, then
this password will be applied to the remittance PDF document.
If a password has not been entered in the EFT Employee’s Remittance Password field,
then the EFT Options \ Payroll Password Formula will be used to generate a Employee-
specific password to be applied to the remittance PDF document.
If no password formula exists for either of those fields, then the PDF document will not
be encrypted.
If a User Password and Master Password both exist, then encryption of the PDF doc-
ument will take place using both passwords.
If a User Password exists, but no Master Password exists, then encryption of the PDF
document will still take place, using the User Password only.
If no User Password exists, then no encryption of the PDF document will take place,
whether or not a Master Password exists.
Important!
If you want to use the ability to password protect the PDF attached to emails in EFT Processing, you
need to use EFT's SMTP options.
Similarly, if you want to save a copy of the Payslip/paystub in the directory configured on the EFT
Setup> Options > Default Advice Tab, you need to fill in the A/P Email or the Payroll Email SMTP
details. If emails are sent using default Sage's configuration through Outlook, a copy of the file will not
be saved.
Refer to:
Password Examples on page 152
Password Formulas on page 148
Detail information including Bank, Bank Name, BSB Number, Account number, Account name, Pay-
ment reference
Accounts Payable details including payment reference, file path, file extension, EFT File type
Accounts Receivable details including payment reference, file path, file extension, EFT File type
Payroll details, including payment reference, file path, file extension and EFT File type.
When to print
Print the report when you change vendor EFT/ bank details.
How to print
1. Choose EFT Vendor in the EFT Setup Reports folder, or choose File, Print from the Ship-Via Codes
form
2. Click Print
CUSTOMER REPORT
This report lists the Bank details of customers setup in EFT Processing.
For instructions on printing the report, see EFT Customer Setup Report — printing.
Employee number, Employee name, Bank Name, BSB Number, Account Number, Account name,
Payment Reference
The Entry Number of the EFT File created - if selected entries were exported. This field will be
blank if the entire batch was exported
The Bank Code of the EFT File created
The Entry Number of the EFT File created - if selected entries were exported. This field will be
blank if the entire batch was exported
The Bank Code of the EFT File created
Vendor ID
Vendor name
Payment Amount
Customer name
Customer Account Name
Customer ID
Customer Name
The new value (the value of the field after the amendment)
Date
Time
User
Customer Name and Number
Document Number
- Date
- Time
- User
- Customer Name and Number
- Original Document Date
- Amended Document Date
- Original Discount Date
- Amended Document Date
The Entry Number of the EFT File created - if selected entries were exported. This field will be
blank if the entire batch was exported
The Bank Code of the EFT File created
The Entry Number of the EFT File created - if selected entries were exported. This field will be
blank if the entire batch was exported
The Bank Code of the EFT File created
Employee ID
Employee name
Payment Amount
Important! Some fields and screens may be displayed only if you have an activation code that
includes both EFT Processing (A/P and A/R) and EFT Processing (Payroll).
A/P Tab
Use the A/P Tab to configure EFT Options to create Payment Files
A/P TAB FIELDS AND CONTROLS
If set to "No", you may only select a single AP Payment batch for file creation.
If set to "Yes", you may select a range of AP Payment batches using the finders. One
EFT file will be created for the range of batches selected and the bank will default to
the bank code of the first batch in the range.
If you select "Yes" both posted and unposted AP Payment batches will be displayed
via the Finder.
If you select "No", only posted AP Payment batches will be displayed via the Finder.
Skip the vendor and continue the export - selecting this option enables a tick box on the
EFT Create File screen which will allow you to determine whether an error is generated for each
run. EFT Create File will ignore all transactions for AP Vendors which have not been defined in
EFT Vendors and produce a file for those AP Vendors which have been defined in EFT Vendors.
Display an error and abort the export - selecting this option will generate an error message
for each AP Vendor which is not defined in EFT Vendor and abort the export. The EFT Vendor
can then be added and the file export resumed.
Select this option to allow selective records from an A/P Payment batch to be transmitted
via EFT.
Allow Multiple Vendor bank account details, one per EFT File Type
Select this option to allow multiple vendor bank account details, per EFT file type.
Tip: If you only make EFT transactions from one bank account and only have one EFT File
Type in use, do not select this option and use the default EFT File Type. This simplifies the
data entry and reduces the risks of duplicate account details.
Select the appropriate action for duplicate Branch/Account numbers for EFT Vendors:
Ignore: no validation
Warning: you can enter duplicate details, but users receive a warning message.
Error: you cannot enter duplicate details.
Select this option to encrypt bank details on the Sage 300 screens. When the Encryption
option is selected:
Users with "View only" security rights will only see the last 4 digits of the Vendor
Bank & Account details.
Any pre-existing records in EFT Vendor will be encrypted.
When generating an EFT File to upload to the bank, the unencrypted values will auto-
matically be inserted into the file.
Note: When you first select the "Encrypt" option, all existing bank details are
encrypted.
Tip: When using the option to Encrypt details, use Sage 300 Security Groups
for EFT and include a limited number of users in a group with rights to
Select this option if you wish to password-protect a Remittance Advice when emailing it to
the Vendor.
Important! The option to add a password to the PDF is only available if send-
ing emails through EFT SMTP. So you need to configure the A/P Email server
details.
Password Formula
Enter the formula for the password the Vendor will use to open their Remittance Advice PDF.
(See Password Formulas on page 148 for more details.)
Tip: You can view the auto-generated password for each Vendor in EFT Vendors.
Enter the master password for all Vendors' Remittance Advices, if required. If used, any
encrypted PDF can be opened using either the Vendor’s password or the Master password.
Email Service
SMTP (Simple Mail Transfer Protocol). You can use your own SMTP server, or an
SMTP service.
Microsoft Graph. This service sends email via Microsoft Office 365. It is generally used
when SMTP Basic authentication is not enabled in Office 365.
Refer to Office 365 and Microsoft Graph
SMTP FIELD DETAILS:
Email Server : smtp.domain.com:587 Enter the details of the SMTP Server you want to
email from. The default port is generally port 587 with TLS.
Tip: You can specify a port number after filling in the email server details. After
the email server name, enter “:xx” i.e. colon xx where xx is the port number
required. Example: smtp.domain.com:587
Email User and Email Password: Enter a correct combination of Email user and
password
Note: If using multi-factor authentication and App password, enter the App
password you create in he Email Password field. Refer to Using Orchid Modules
with Office365 App Passwords on page 115
Email Comes From: Enter the email address to be used when sending email.
Note: Depending on the SMTP server you use, this address may need
to match the one you enter in the Username field, or may not work
unless you set up an email alias. Consult your SMTP server doc-
MICROSOFT GRAPH
Microsoft Graph:
This service sends email via Microsoft Office 365 where basic authentication is not enabled to use
SMTP.
Refer to Office 365 and Microsoft Graph
Tenant ID. Enter the tenant ID (alternatively called the directory ID) from your Microsoft
365 account.
Client ID. Enter the client ID (alternatively called the application ID) from your Microsoft
365 account.
Client Secret. Enter the client secret from your Microsoft 365 account.
Tip: This is actually the secret value, not the one called Secret ID. It is the one
that you only see once when you first create the client secret.
From Email Address. Enter the email address to be used when sending email.
Configure limits when sending emails: (None / Per Minute / Per Session)
If you are getting errors relating to "exceeding limits" when sending email remittance advice,
you can configure the options to Number of emails per minutes or Number of emails per ses-
sion to match the requirements of your email server.
Defaults to "None".
Choose Per Minute if your email server has a limit per minute when sending
SMTP emails (e.g. Office 365).
Choose Per Session if your email server has a limit per session.
Enter the number of emails to send per minute or per session.
When printing Advices and if the number of advices is greater than the limit, EFT will send the
number entered in the limit, then pause if "per minute" is selected or Disconnect and start a
new session if using "Per session" is selected.
Example: Limit per minute: If you set the limit to 30 per minute and you email 50 remittance
advices, EFT Processing will send the first 30, pause for a minute, send the next 20, and will
then display the result.
Example: Limit per session: If you set the limit per session to 10 and you select to Print/E-
mail a batch of 50 remittance advices, EFT Processing will make a connection to the
SMTP Server, send 10 emails (1 to 10), disconnect, then reconnect, send the next 10 emails
(11 to 20), disconnect, connect again, send the next 10 emails (21 to 30), disconnect, etc.
When all emails are sent, it will display the delivery results.
Note: If you set the number of emails to 0 (per minute or per session), the emails
will be sent with no limits (the same way as with the "None" option)
-A/R Tab
Use the A/R Tab to specify options to use when creating A/R Files to process Direct debit and
AR Refunds files.
A/R TAB FIELDS AND CONTROLS
Select this option, to allow or disallow the selection of a range of AR Receipt batches from
the EFT Create File form.
If set to "No", you may only select a single batch for file creation.
If set to "Yes", you may select a range of AR Receipt batches using the finders. One
EFT file will be created for the range of batches selected and the bank will default to
the bank code of the first batch in the range.
Select this option if you wish both posted and unposted AR Receipt batches to be dis-
played by the Finder on the EFT Create File form.
If you select "Yes" both posted and unposted AR Receipt batches will be displayed
via the Finder.
If you select "No", only posted AR Receipt batches will be displayed via the Finder.
Select this option to control what happens when a customer is not defined in EFT Cus-
tomers.
Skip the customer and continue the export - selecting this option enables a tick
box on the EFT Create File screen which will allow you to determine whether an error
is generated for each run. EFT Create File will ignore all transactions for AR Cus-
tomers which have not been defined in EFT Customers and produce a file for those
AR Customers which have been defined in EFT Customers.
Display an error and abort the export - selecting this option will generate an error
message for each AR Customer which is not defined in EFT customers and abort the
export. The EFT Customer can then be added and the file export resumed.
Select this option to allow selective records from an A/R Receipt or Refund batch to be
transmitted via EFT.
Allow Multiple Customer bank account details, one per EFT File Type
Select this option to allow multiple Customer bank account details, per EFT file type.
When creating the EFT File, EFT will use the bank account details for the specified EFT File
Type if it exists. If there is no entry for the Customer and EFT File Type combination, then it
will use the default bank account details for the Customer (ie where the EFT File Type is
blank).
Tip: If you only make EFT transactions from one bank account and only have one EFT File
Type in use, do not select this option and use the default EFT File Type. This simplifies the
data entry and reduces the risks of duplicate account details.
Select "Entered" to enable 2-step approvals of EFT Customer details. Refer to Approving
changes of EFT Vendor/Customer/Employee details on page 17 for details.
Select the appropriate action for duplicate Branch/Account numbers for EFT Customers:
Ignore: no validation
Warning: you can enter duplicate details, but users receive a warning message.
Error: you cannot enter duplicate details.
Note: When you first select the "Encrypt" option, all existing Customers' bank
Tip: When using the option to Encrypt details, make sure that you use Sage
300 Security Groups for EFT so that only a limited number of Admin users can
Select this option if you wish to password-protect a Remittance Advice when emailing it to
the Customer.
Important! The option to add a password to the PDF is only available if send-
ing emails through EFT SMTP. So you need to configure the A/P Email or
Password Formula
Enter the formula for the password the Customer will use to open their Remittance Advice
PDF. (See Password Formulas on page 148 for more details.)
Tip: You can view the auto-generated password for each Customer in EFT Customers.
Enter the master password for all Customer Remittance Advices, if required. If used, any
encrypted PDF can be opened using either the Customer’s password or the Master pass-
word.
Email Service
SMTP (Simple Mail Transfer Protocol). You can use your own SMTP server, or an
SMTP service.
Microsoft Graph. This service sends email via Microsoft Office 365. It is generally used
when SMTP Basic authentication is not enabled in Office 365.
Refer to Office 365 and Microsoft Graph
Refer to EFT Processing Email Tab on page 47 for details to configure the fields.
Tips:
If left blank, EFT Processing will use the SMTP Details on the A/P Email Tab.
If A/P Email tab SMTP details are also blank, Sage 300's configuration to send emails will be used.
BSBNumber
AccountNumber
AccountName
APPaymentReference
ARPaymentReference
BSBNumber
AccountNumber
AccountName
PaymentReference
The following applies to the Encryption option on EFT Options A/R, A/P and Primary
Bank.
When the "Encryption" option is ticked, users with "View only" security rights
will only view the last 4 digits of the bank details. The audit log for EFT files gen-
erated when Encryption is ticked will also show only the last 4 digits of the
bank details.
You can setup Users in a security group that includes the right to view "Unen-
crypted Details" (There are separate groups to View Unencrypted Vendor Bank
Details, View Unencrypted Customer Bank Details and View Unencrypted Bank
Account Details). Refer to Adding Security on page 33
When the EFT File is generated, the unencrypted values will automatically be
inserted in the file.
If the Encryption option is selected after you have entered some EFT Cus-
tomers or Vendors Bank Details, the existing records in EFT Vendors and
EFT Customers setup will be encrypted. However, the audit log for files gen-
erated before Encryption was selected will not be encrypted. You will need to
purge the audit log files if you want to remove all unencrypted data.
Tip: When importing EFT Vendors, EFT Customers and EFT Banks, you should not
import the Encrypted Bank Branch and Account number and Credit Card Number
fields (fields containing an "X"). These fields should only be set using the asso-
ciated views, and set to the calculated encrypted value. - EFT Import functionality
prevents such fields to be imported.
Important! If a user does not have the security to "Select Remittance Advice Layout",
To set one of the defaults, click the browse button and browse the network to find the
appropriate Crystal form.
To set one of the defaults, click the browse button and browse the network to find the
appropriate Crystal form.
To set one of the defaults, click the browse button and browse the network to find the
appropriate Crystal form.
This form is used when sending Payroll Remittance Advices. To set one of the defaults, click
the browse button and browse the network to find the appropriate Crystal form.
Refer to EFT Payroll Print Remittances Advices on page 82
Enter or browse to find the relevant Sage 300 CP or UP Payslip/stub report from the rel-
evant CPxxA or UPxxA directory (e.g. CPCHK4A.RPT in the CP68A folder if you run version
2021).
Enter the UNC path for the parent directory where the Payslip/stub PDF files are to be
saved. EFT Processing will automatically create a subfolder for each Sage 300 Company
and a sub-folder for each Employee ID.
Note:
If you select "Use Remittance Advice Password" option on the Payroll Tab, the password
is used to save a copy of the PDF payslips.
However, the pdf attached to payroll emails (both payslips and remittance advice) only
has a password if you send emails through EFT SMTP and you have configured A/P Email
Server or Payroll Email server details in EFT Options. Attached PDF files don't have a pass-
word when using Sage SMTP Server or Outlook.
Enter or browse to find the CTR1BLK.RPT Sage 300 Payroll Relevé 1 report from the rel-
evant CTxxA directory (e.g. CT73A\ENG\CTR1BLK.RPT). This applies only to Canadian
Payroll.
Enter or browse to find the CTT4BLK2..RPT Sage 300 Payroll T4 report from the relevant
CTxxA directory (e.g. CT73A\ENG\CTT4BLK2.RPT).This applies only to Canadian Payroll .
Enter or browse to find the CTT4A..RPT Sage 300 Payroll T4As report from the relevant
CTxxK directory (e.g. CT73K\ENG\CTT4A.RPT).This applies only to Canadian Payroll .
EFT Processing includes remittance advice Crystal Reports in the ELxxA>ENG folder. You can
also use Sage 300 Customization Directories.
DETAILS OF EFT PROCESSING ADVICE FORMATS:
EFT Processing installs with the following A/P remittance advice formats, with different pay-
ment formulas:
ELPAY01 – payment date is based on the date when the EFT file was cre-
ated/generated.
ELPAY02 – payment date is based on the the Batch Date.
ELPAY03 – payment date is based on the Batch Entry Date.
ELPAY05 – payment date is based on the effective date selected when the EFT file
was created/generated. This only applies if the EFT format you use supports effective
date.
ELREC01 – payment date is based on the date when the EFT File was cre-
ated/generated.
ELREC02 - payment date is based on the receipt entry date.
ELREF01 – payment date is based on the date when the EFT File was cre-
ated/generated.
ELREF02 - payment date is based on the refund entry date.
Global FSN
This tab allows you to assign a Global File Sequence Number (FSN) across all EFT banks.
GLOBAL FSN FIELDS AND CONTROLS
The Global FSN setup is used if you want to issue a single File Sequence Number across multiple
banks. You have 10 Global File System Numbers that you can allocate to multiple banks on the EFT
Banks screen. Allocating the same Global File System Number to 3 banks (for example), will result in
AP Payment Batches or AR Receipt batches from all 3 banks being allocated a sequential number
from the same source number.
Note: If the EFT File format includes the Global File Sequence Number, you need to select the
"Global File Sequence Number" option to name the file.
Global FSN 1 .. 10
Payroll Tab
Use the Payroll Tab to configure EFT Options to create Payroll Files
PAYROLL TAB FIELDS AND CONTROLS
Allow EFT file creation from a payroll pay period end range?
Select this option, to allow or disallow the selection of a range of Payroll pay periods from
the EFT Create Payroll File form.
If set to "No", you may only select a single Payroll pay period for file creation.
If set to "Yes", you may select a range of Payroll pay periods using the finders. One
EFT file will be created for the range of Payroll pay periods selected and the bank will
default to the bank code of the first pay period selected.
Select this option to control what happens when an employee is not defined in EFT Employ-
ees.
Skip the employee and continue the export - selecting this option enables a tick
box on the EFT Create Payroll File screen which will allow you to determine whether
an error is generated for each run. EFT Create Payroll File will ignore all transactions
for Employees which have not been defined in EFT Employees and produce a file for
Employees which have been defined in EFT Employees.
Display an error and abort the export - selecting this option will generate an error
message for each Payroll Employee which is not defined in EFT Employees and abort
the export. The EFT Employee can then be added and the file export resumed.
Select this option to allow selective records from a payroll pay period to be transmitted via
EFT.
Select Entered, Active or Inactive as the default employee status. Use security to control
who can make employees active in Payroll.
Select this option to encrypt Employee's bank details on the Sage 300 screens. When the
Encryption option is selected:
Users with "View only" security rights will only see the last 4 digits of the Employee
Bank & Account details.
Any pre-existing records in EFT Employee will be encrypted.
When generating an EFT File to upload to the bank, the unencrypted values will auto-
matically be inserted into the file.
Note: When you first select the "Encrypt" option, all existing bank details are
encrypted.
Tip: When using the option to Encrypt details, make sure that you use Sage
300 Security Groups for EFT so that only a limited number of Admin users can
Primary Bank
The Primary bank is used as the default file type on the Employee Setup Screens for field
labels.
You can add up to 50 extra fields for Employee.
Select this option if you wish to password-protect PDF Files attachments (Remittance
Advice and payslip/stub) when emailing PDF to the Employee.
This option is also used to password protect the Payslip/stub file saved if you configure a
Print folder in the EFT Options > Default Advice Tab.
only available if sending emails through EFT SMTP. So you need to configure
Password Formula
Enter the formula for the password the Employee will use to open their Remittance Advice
PDF. (See Password Formulas on page 148 for more details.)
Enter the master password for all Employees' Remittance Advices, if required. If used, any
encrypted PDF can be opened using either the Employee’s password or the Master pass-
word.
Email Service
SMTP (Simple Mail Transfer Protocol). You can use your own SMTP server, or
an SMTP service.
Microsoft Graph. This service sends email via Microsoft Office 365. It is generally used
when SMTP Basic authentication is not enabled in Office 365.
Refer to Office 365 and Microsoft Graph
Refer to EFT Processing Email Tab on page 47 for details to configure the fields.
Tips:
If details are left blank, EFT Processing will use the SMTP Details on the A/P Email Tab.
If they are both blank, EFT Processing uses the default Sage 300 method of sending e-mail via
Microsoft Outlook client or SMTP Details on Sage 300 Advanced ERP Company Profile.
To use Office 365 to email from Orchid modules and to use Document Management Link and SharePoint
integration, users need to create an APP password for use in the Orchid module, as supported by
Microsoft.
For details, refer to Using Orchid Modules with Office365 App Passwords on page 115
Note:
The details below are left in the documentation if your Office 365 setup supports basic
SMTP Authentication and App Passwords.
Email Server -> smtp.office365.com:587
Email User -> username@samplecompany.com
Email Password -> Enter Password
If using Multi-factor Authentication and App Password, enter the App passwordl.
For details, see Using Orchid Modules with Office365 App Passwords on page 115
Encryption: TLS
TLS Version
You don't select a specific TLS version. Orchid uses the .Net SmtpClient class to send emails.
The SMTP Client uses the protocol configured on the operating system, based on the
.NET version installed.
The email function supports Ssl3, Tls1.0, Tls1.1, Tls1.2 and Tls1.3.
Microsoft has recently stopped support for TLS1.0 and TLS1.1. Support for TLS 1.2 was
added to Orchid modules in April 2020 and applies to Sage 300 versions 2018 and above.
Important! If you have any issues emailing, please ensure you download and install the
latest product update for your Sage 300 version.
Useful Links
Here is a link to Microsoft documentation on how to allow applications to send email via Office365.
http://technet.microsoft.com/en-us/library/dn554323.aspx
Using Gmail
Since May 2022, you cannot disable 2-step authentication in the Gmail settings and you need to use App
Password.
Email Server: smtp.gmail.com:587
Email User: username@gmail.com
Email Password: App password you create for the user emailing.
Encryption: TLS
Note: In some older versions of Orchid modules, for Google mail to be setup in
Outlook/other email application/device (as recipient in CC/BCC), the Google email setting
When using any other email that has Transport Layer Security (TLS) encryption along with SMTP, you
can prefix the email server field with “TLS:”.
For eg. TLS:securemail.server.net
Using SendGrid
IF USING SENDGRID
Using Hotmail
CONFIGURE EMAIL WHEN USING HOTMAIL OR MICROSOFT OUTLOOK.COM
Email Server -> smtp.live.com:587
Email User -> username@hotmail.com
Email Password -> Enter Password
Encryption: TLS
Key Steps
Generate an App Password in Office 365.
Refer to the Microsoft Help for details. The exact steps depend on your Office 365 subscription type.
Below is a relevant example:
https://docs.microsoft.com/en-us/azure/active-directory/user-help/multi-factor-authentication-end-
user-app-passwords
Legacy Authentication
If you are getting an error such as "The sign-in name or password does not match one in the Microsoft
account system", and you have checked the basic account details, your site in Office 365 may be blocking
Legacy authentication.
Refer to Office365 and Legacy Authentication on the next page for detailed steps.
EMAIL TROUBLESHOOTING
Failure sending mail
If you get the error message “Failure sending mail” – check that you have entered the correct details in
Port
If the default port for email (25) is not in use, ensure the port is included in the Email server field
separated by a semi-colon (:). For example smtp.office365.com:587 if port “587” is being used for
e-mail.
Legacy Authentication
If you are using MFA and App password in Office 365, but are still receiving errors when testing the
SMTP email, ensure that Legacy Authentication is not blocked. Refer to Office365 and Legacy Authentic-
ation on page 120.
TLS Version
You don't select a specific TLS version. Orchid uses the .Net SmtpClient class to send emails. The
SMTP Client uses the protocol configured on the operating system, based on the .NET version installed.
The email function supports Ssl3, Tls1.0, Tls1.1, Tls1.2 and Tls1.3.
Microsoft has recently stopped support for TLS1.0 and TLS1.1. Support for TLS 1.2 was added to Orchid
modules in April 2020 and applies to Sage 300 versions 2018 and above.
Important! If you have any issues emailing, please ensure you download and install the latest product
update for your Sage 300 version.
Ensure the virus checker and firewall on all machines where e-mails are to be sent from. They must
be set to exclude “..\EL6xA\sendmail.exe”
If you get a File missing error, check that the anti-virus is not deeming the sendmail.exe a virus
threat.
SMTP Server may include configuration to expect a valid client certificate from the server-
/workstations where Sage is installed. Once the certificate is installed on the client, emails can be
sent.
You are able to send emails to internal email accounts, but not to external email accounts, the most likely
cause is that your email server requires a valid username /password for sending to external addresses
and the details entered are not correct.
Note: Check your email server to see if it requires a username/password. Some require it to be blank,
for some it does not matter.
Note: Some email servers will allow you to log on as a certain user and send email as anyone, others
will only allow you to send email as the logged on user. So if you log on as "Joe", but try to send as
admin@testdomain, some email servers won't allow it.
The numbering will be then based on Global FSN in the EFT Option.
As below it is stating that the next running number is 9.
When Create EFT file is run for payment batch, it will get the next sequence number as the file name.
The subsequent file run either from AR Receipt Batch for the same bank code or RBC bank code, it will
share the same Sequence Numbering.
in EFT Setup > Options > Primary File Type Tab or File Type entered on the EFT Vendor or
Customer screen.
Use this screen to setup EFT bank details for banks setup in Sage 300 Bank Services and configure how to
generate EFT files for Payments/Refunds, Receipts and Payroll files.
Tip: Use the Finder to select a bank already configured in EFT Banks, use the Zoom button to select a
bank from Bank Services.
BANK CODE
Enter a Bank Code as defined in Bank Services.
BANK NAME
The name of the bank account, up to 60 characters.
BANK TYPE
Select "Regular" for EFT to process the transaction
Select "Clearing Bank" If you want the AP Payment batch to post to Bank Services in total,
as a single entry per EFT Payment.
See Setup and Use EFT Clearing Bank on page 25 for details on how to process your payments
using a clearing bank.
FOR BANK
This field is enabled if the "Clearing Bank" bank type has been selected. By clicking on the
search button, select which bank code is applicable.
BSB NUMBER
Type the banking industry code that identifies this bank.
If EFT Processing Options / Primary Bank / Encrypt Bank BSB/Acct. No. is selected, you will only
see the last 4 digits of the details entered.
ACCOUNT NUMBER
Type the number of the bank account (assigned to the account by your bank). The number
can be up to 22 characters.
ACCOUNT NAME
Type the name of the bank account .
EXTRA FIELDS
Depending on the File Type selected below and the formats.ini file, up to 10 additional fields
can be configured.
TYPE TAG
This applies to ISO20022 file types only, depending on the bank specifications.
if there is an originator ID, update this field with ‘Othr’.
If there isn’t an Originator ID, update this field with ‘BIC' or 'BEI’ and set the OrgID field with the
BIC code.
Tip: This is particularly relevant when using EFT web screens as the user may not have access
to the server.
SFTP: You need to fill in the FTP Host Name and credentials to connect to the FTP site.
When using SFTP, you can select to enter user name and password or SFTP with Key file or
both.,
Select SFTP -2FA if your bank uses 2 factor authentication and requires both a username and
password and a key file.
Refer to Setup SFTP Output Destination on page 19 for details on setting up SFTP to send
EFT files.
Tip: Use the Test SFTP File Upload button to test before uploading a file.
Key File:
If you select Key File then you enter the key file filename and (optionally) a password for the
file. The key file should be either on a local drive (eg c:) and will need to be copied to each com-
puter running the Create EFT function, or on a network share.
The key file can have a password too if required by the bank.
File Naming:
File Sequence Number: the file will be called the File Sequence number on the bank, and
after using the file sequence number, EFT Processing will increase the file sequence number by
1.
Note: If the EFT File format includes the File Sequence Number, you generally
select the "File Sequence Number" option to name the file. If you select Batch Num-
bering to name the file, EFT Processing uses the batch number as the [FSN] value.
Batch Number : the file will be called APbbbb.{ext} or ARbbbb.{ext} where bbbb is the batch
number being exported.
Pay Period End Date YYYYMMDD: for EFT Payroll files
Fixed File Name : User defined file name using any characters plus the following variables
in the file name :
{yyyy} for the year, {mm} for the Month, {dd} for the Day
{bbbb} up to 4 numbers for the batch number
{N} gives you a running number starting from 0 each day. This is often used in con-
junction with batch number to keep track of the number of exports in a calendar day.
{S} gives you a running sequence number for the selected bank- You can use up to 4
numbers for the file sequence number. You typically use this option instead of batch
number for a unique number per file.
{entry} for the entry number, this works with option that each entry to be generated in a
single file.
Example: You can use up to 4 digits for {B}, {S} and {N}
Example for Batch Number 2
{b} for 1 digit, e.g. 2
{bb} for 2 digits, e.g. 02
{bbb} for 3 digits, e.g. 002
{bbbb} for 4 digits, e.g. 0002
Global Sequence 1..10. You are able to share a Global File Sequence number between
multiple banks if required. EFT Processing will increase the global file sequence number used
by one after creating the file.
Note: If the EFT File format includes the Global File Sequence Number, you need to select
the "Global File Sequence Number" option to name the file.
Tip: Use UNC Path so that all users and workstations can access the folder. If using mapped
drive, there is a risk that some users have a different drive mapping.
Note: The field name may be re-labelled based on the EFT format for the selected file type.
FILE SEQUENCE NO
If the file name is set to "File Sequence Number", this number is updated when you create the
EFT file.
Important! Users who Generate the EFT File need to have security rights to update EFT Bank
(as the FSN is stored on the EFT Bank record).
Tip: If you need to reexport a file, set the file sequence number back by 1 to generate the file
with the same number.
RECEIPTS TAB
Use the Receipts Tab to configure EFT Files generated for A/R Receipt Batches.
Output Destination:
SFTP: You need to fill in the FTP Host Name and credentials you want to use.
Refer to Output Destination: on page 132
File : No additional parameters needed. Enter the File path and extension
below.
File Naming:
Choose Same as Payments to use the settings on the Payments and Refunds Tab
or You can select the file name from the following
File Sequence Number: this uses the File Sequence Number on the EFT
Banks Payments & Refunds tab or Receipts Tab, and adds 1 to it.
Batch Number: from the Batch number entered
Fixed Name: you can type in the file name at the end of the EFT File Path,
and can include the variables highlighted on the right hand side of the screen.
Variables include the current date and time, the batch number, the file
sequence number and fixed text.
Global Sequence 1..10: this gives you 10 File Sequence Numbers that
can be used across multiple banks.
Tip: Use UNC Path so that all users and workstations can access the folder. If using mapped
drive, there is a risk that some users have a different drive mapping.
FILE SEQUENCE NO
If the file name is set to "File Sequence Number", this number is updated when you create the
EFT file.
If the file name includes {s}, this number is updated when you generate the EFT file.
Important! Users who Generate the EFT File need to have security rights to update EFT Bank
(as the FSN is stored on the EFT Bank record).
Tip: If you need to reexport a file, set the file sequence number back by 1 to generate the file
with the same number.
PAYROLL TAB
Output Destination:
SFTP: You need to fill in the FTP Host Name and credentials you want to use. Refer
to Output Destination: on page 132
File : Enter the file path below.
File Naming:
You can select the file name from the following:
File Sequence Number: this uses the File Sequence Number on the EFT Banks
Payroll Tab, and adds 1 to it.
Pay Period End Date YYYYMMDD
Fixed Name: you can type in the file name at the end of the EFT File Path, and can
include the variables highlighted on the right hand side of the screen. Variables include
the current date and time, the batch number, the file sequence number and fixed text.
Global Sequence 1..10: this gives you 10 File Sequence Numbers that can be used
across multiple banks. Global File Sequence Example on page 126
Tip: Use UNC Path so that all users and workstations can access the folder. If using mapped
drive, there is a risk that some users have a different drive mapping.
REFERENCE
Enter a payment reference code.
Note: The field name may be re-labelled based on the EFT format for the selected file type.
Important! Users who Generate the EFT File need to have security rights to update EFT Bank
(as the FSN is stored on the EFT Bank record).
Tip: If you need to reexport a file, set the file sequence number back by 1 to generate the file
with the same number.
Tip:
You can use the Drill-down Icon to open the related A/P Vendor screen. This is useful
to check the Vendor's delivery method for example.
Remit To
Note:
With this setup for your EFT Vendors, if you create an AP Payment entry to a specific Ven-
dor/Remit-to code combination, EFT Processing will apply the following rules to work out
which EFT Vendor record (and therefore bank details) to use when creating the EFT File:
Search for an EFT Vendor record with the same AP Vendor code and AP Remit-to
code - use this record as a first choice
Search for an EFT Vendor record with the same AP Vendor code and a blank Remit-to
code - use this record as a second choic
Report an error that there is no EFT Vendor record for the AP Payment entry
File Type
This field is optional. Select a file type to record different bank account details for the vendor
according to the file type.
If you leave this field blank, then EFT will use the file type that has been assigned in EFT
Options > Bank Setup
Note: This is only available if you select "Allow multiple vendor bank account details one per
EFT file type in EFT Setup > Options > A/P Tab
Delivery Method
If you select AP Vendor Delivery Method, EFT will use the setup in Accounts Payable
when emailing remittance advices.
Tip: Choose Email (vendor) or Email (contact) to send an email. At the moment,
EFT Processing doesn't support Sage 300 Multiple Contacts.
If you select EFT Vendor E-mail To, you can enter the email address to use below in the
Email To Field.
When sending remittance advices, if EFT Vendor Email To is selected and the Email To field is
populated, the remittance will be emailed to the E-Mail address entered in EFT. If no email
address is entered, users will receive an error message when printing remittance advices.
Remittance Password
If you select to password protect PDF remittance advice in EFT Options Screen Guide on
page 97 >AP Tab , optionally enter the Vendor-specific password the Vendor will use to open
their Remittance Advice PDF. If no password is entered, then the Auto-generated Remittance
Password described below will be used.
AUTOGEN REMITTANCE PASSWORD
The auto-generated password, based on the Password Formula on EFT Options \AP Tab, will be
displayed. (This is for visual verification only and is only available if you have security rights to edit
Vendor remittance advices.)
Email To
Tip: To send to multiple addresses, use a semi-colon (;) to separate the email addresses. For
example ronald@samplecompany.com; ronald.black@samplecompany.com;
Bank Name
BSB Number
Type the banking industry code that identifies this Vendor's bank.
If EFT Processing Options / A/P / Encrypt Bank BSB/Acct. No. is ticked, you will only see the last
4 digits of the details entered.
Account Number
Type the number of the bank account (assigned to the Vendor's account by their bank). The
number can be up to 22 characters.
If EFT Processing Options / A/P / Encrypt Bank BSB/Acct. No. is ticked, you will only see the last
4 digits of the details entered.
Account Name
Type the name of the Vendor's bank account. Defaults to the Vendor's name.
Payment Reference
Status
Entered
Active
Inactive
Note: Status must be Active before you can perform EFT Transactions
Note: You can setup security to control who can approve EFT Vendors - Refer to Approving
changes of EFT Vendor/Customer/Employee details: on page 37
Tip:
Field names might be different depending on the Primary Bank set up in EFT Options.
Use the Primary File Type Tab for EFT Processing (A/P and A/R)
Field names also depend on the File Type entered on the EFT Vendor and EFT Customer screens, if
using the multiple account details, one per EFT file type option.
Main Tab
Customer Number
Tip:
You can use the Drill-down Icon to open the related A/R Customer screen. This is use-
ful to check the Customer's delivery method for example.
File Type
This field is optional. It is only available if you select the "Allow multiple customer bank
account details, one per EFT File Type" in EFT Options > A/R Tab.
If this option is enabled, you have a Finder to select the EFT Customer, a field to select the
A/R Customer and another to select the File Type.
Select a file type to record different bank account details for the customer according to the file
type.
If you leave this field blank, then EFT will use the file type that has been assigned in EFT
Options > Primary Bank
Delivery Method
If you select AR Customer Delivery Method, EFT will use the setup in Accounts Receiv-
able when emailing advices.
If you select EFT Customer E-mail To, you can enter the email address to use below in
the Email To Field.
When sending remittance advices, if EFT Customer Email To is selected and the Email To field
is populated, the advice will be emailed to the E-Mail address entered in EFT. If no email
address is entered, users will receive an error message when printing remittance advices.
Remittance Password
If you select to password protect PDF remittance advice in EFT Options Screen Guide on page 97
>AR Tab , optionally enter the Customer-specific password the Customer will use to open their Remit-
tance Advice PDF. If no password is entered, then the Auto-generated Remittance Password described
below will be used.
AUTOGEN REMITTANCE PASSWORD
The auto-generated password, based on the Password Formula on EFT Options \AR Tab, will be
displayed. (This is for visual verification only and is only available if you have security rights to edit
Customer remittance advices.)
Email To
If this field is populated with an email address, it will be used if you choose delivery method as
“Vendor/Customer” in EFT Reports > Print Advices.
The field length is 250 characters
Bank Name
The name of the Customers bank account, up to 60 characters.
BSB Number
Type the banking industry code that identifies this Customer's bank.
If EFT Processing Options /A/R / Encrypt Bank BSB/Acct. No. is ticked, you will only see the last
4 digits of the details entered.
Account Number
Type the number of the bank account (assigned to the Customer's account by their bank). The
number can be up to 22 characters.
If EFT Processing Options /A/R / Encrypt Bank BSB/Acct. No. is ticked, you will only see the last
4 digits of the details entered.
Account Name : Type the name of the Customer's bank account.
Payment Reference : Enter the bank's payment reference number.
Status
Tip:
The status needs to be active if to create EFT files.
Refer to tutorial for details on using this feature: Approving changes of EFT Ven-
dor/Customer/Employee details on page 17
Defaults to No. Set to Yes if you want EFT to consolidate receipts by National Account.
Debit file. The fields are encrypted in the database, but please note that EFT Processing
module is not PCI compliant and that Orchid takes no responsibility for the use of asso-
Tip:
Field names might be different depending on the Primary Bank set up in EFT Options.
Use the Primary File Type Tab for EFT Processing (A/P and A/R)
Field names also depend on the File Type entered on the EFT Vendor and EFT Customer screens, if
using the multiple account details, one per EFT file type option.
Tip:
Field names might be different depending on the Primary Bank set up in EFT Options.
Tip: use F9 / Detail to see the additional fields for employees and enter the financial institutions that
the pay is paid into.
FILE TYPE
This field is optional. If you leave this field blank, then EFT will use the file type that has been
assigned in EFT Options > Payroll Tab > Primary Bank.
Select a different file type if the employee's bank requires different details than the Payroll Primary
Bank.
If you leave this field blank, then EFT will use the file type that has been assigned in EFT Options >
Payroll Tab > Primary Bank.
Example: If some employees are paid with in International bank transfer format, you only need to
enter the IAT file type for such employees. You can leave the file type blank for all other employees
paid the default file format.
DELIVERY METHOD
Select Payroll Email Delivery Method if you want to use the Payroll Employee Setup
Select EFT Email and Populate the Email To field if you want separate email details for Payroll and EFT
documents.
Select Mail if you don't want to email.
EMAIL TO
This field is optional.
If using "EFT Email Delivery Method, Enter the Email value you want to use.
If you leave this field blank, then EFT will use the Payroll Email based on the Payroll setup.
REMITTANCE PASSWORD
If you select to password protect PDF remittance advice in EFT Options Screen Guide on page 97
>Payroll Tab , optionally enter the Employee-specific password the Employee will use to open their
Remittance Advice PDF. If no password is entered, then the Auto-generated Remittance Password
described below will be used.
The auto-generated password, based on the Password Formula on EFT Options \Payroll Tab, will be
displayed. (This is for visual verification only and is only available if you have security rights to edit
Employee remittance advices.)
STATUS
Select the Status to be
Entered
Active
Inactive
Note: Status must be Active before you can perform EFT Transactions
Note: You can setup security to control who can approve EFT Employees
Tip: In most cases, the last rule should be set to Calculation Type "% Net Pay " and Per-
cent = 100. This means that any amount remaining after the previous rules have been
applied will be transferred to the account set in that line. If the pay is to be paid to a
single account, you only need to enter one line with "% Net Pay" as the Calculation
Example:
In the screenshot below, EFT Payroll will create a line in the file for $300 to CIBC and the remainder
of the pay will be transferred to RBC.
If the pay is $250 for the week, only one line will be created. If the pay for the period is $400, it will
create 2 lines, one for $300 and one for $100.
END DATE
Enter the end date if this pay components is only to be paid until the end date.
BANK NAME
The name of the Employee's bank name, up to 60 characters.
ACCOUNT NUMBER
Type the number of the bank account (assigned to the Vendor's account by their bank). The number
can be up to 22 characters.
If EFT Processing Options / A/P / Encrypt Bank BSB/Acct. No. is ticked, you will only see the last 4
digits of the details entered.
ACCOUNT NAME
Type the name of the Employee's bank account. Defaults to the Employee's name.
PAYMENT REFERENCE
Enter the bank's payment reference number.
DETAIL...
Click on the Detail. button to view additional fields that can optionally be configured for different
bank file types.
PASSWORD FORMULAS
Formulae are constructed in segments.
Segments are separated by the plus (+) symbol.
Segments comprise of functions that can be applied to Sage 300 view fields as follows:
{fieldname}
RIGHT() function
LEFT() function
YYYY() or YY() year function
MMM() or MM() month function
DD() day function
Example:
The following example sets the password to the Customer number, followed by the last 3 characters of
the customer name and the first 5 characters of the customer's postcode.
{IDCUST}+RIGHT({NAMECUST},3)+LEFT({CODEPSTL},5)
Customer: ORC001
Customer Name: Orchid Systems
Zipcode: NSW2060
Password Segments
Segment 1:
{IDCUST} - refers to the IDCUST field in AR0024 – AR Customers
- fields are enclosed in curly braces {}
- field names must be written in UPPERCASE.
Tip: See below for Sage 300 Views and Fields that can be included in the password formulae.
Segment 2:
RIGHT({NAMECUST},3)
Right 3 characters of the {NAMECUST} field.
RIGHT() is the function.
Segment 3:
LEFT({CODEPSTL},5)
Left 5 characters of the postcode field in ARCUS.
Tip: You can find the field names to use for each view in the Sage 300 Object Model.
Example:
AP Remittance Advice and Tax Number field
If you use {TAXNBR} in the password for AP Advices, the user emailing the remittance advices needs to
be in a Sage 300 Security Profile where the Tax Number Maintenance security group is selected.
Example:
Payslip and SIN Number
You can use {SSN} in the password for payslips (in EFT Options > Payroll Tab).
For example RIGHT({SSN},4) to get the last 4 digits of the SIN Number.
The user running the payroll and generating the PDF needs to be in a Sage 300 Security Profile where
the SIN Number Maintenance security group is selected. If they don't have rights to view the field, the
password will not be what is expected.
RIGHT({LASTNAME},2)+LEFT({EMPLOYEE},3)+LEFT({FIRSTNAME},4)+YYYY
({BIRTHDATE})+mmm({BIRTHDATE})+DD({BIRTHDATE})
Employee code: 23456754
Emplyee Name: Sean Smith
Date of Birth: 1/12/1970
The above formula would result in the following password applied to the PDF:
th234Sean1970DEC01
th: the last 2 characters of the last name
234: the first 3 characters of the employee code
Sean: the first 4 characters of the first name
1970: the year of the DOB
DEC: the month of DB
01: day of birth.
1. YYYY({datefield}) - returns the year in YYYY format. Can be written as YYYY or yyyy
2. YY({datefield}) - returns the year in YY format. Can be written as YY or yy.
3. Month only:
1. MMM({datefield}) - returns the month in abbreviated format: JAN, FEB, MAR, APR, MAY,
JUN, JUL, AUG, SEP, OCT, NOV, DEC. Month is returned in UPPERCASE. Can be written
as MMM or mmm
2. MM({datefield}) - returns the month in numeric format with padded left: 01,02,03,...,12.
Can be written as MM or mm
4. Day only:
1. DD({datefield}) - returns the day portion of the date: 01,02,03,...,31. Can be written as
DD or dd
PASSWORD EXAMPLES
Which remittance advice password will work if you have more than one?
In EFT Processing, you have the option to password-protect PDF sent with Remittance Advices when
emailing to a Vendor, Customer, or Employee.
Scenario 1
If you have a password formula for AP, AR & Payroll remittances in EFT Options
And in EFT Vendors, Customer or Employee, you have manually entered a password for “Remittance Pass-
word” the “Remittance Password” will over-ride the “Autogen Remittance Password”
Scenario 2
In EFT Options, if you have a PDF Master Password for AP, AR & Payroll remittances And an Autogen
Remittance Password, both passwords will work Both passwords will work
Scenario 3
If you have a PDF Master Password in EFT Options for AP, AR & Payroll remittances And no Password For-
mula/Autogen Remittance Password, And a Remittance Password in EFT Vendors, Customers, Employees
Scenario 4
If you have a PDF Master Password in EFT Options for AP, AR & Payroll remittances, but no other pass-
words (no formula, no manually entered passwords), the remittance advice will not be encrypted.
Tip: When you use {field} or $field , EFT will replace the code by the value of the field when sending
the email. When using HTML Emails, use {field} as it knows where the field ends and is more reliable.
$field is available for backward compatibility purposes.
Tip: Email templates are sent as HTML if they contain "<html>" and "</html> Tags. Only available in
the latest product updates of Sage 300 version 2016 and above.
Tip: To add a line in HTML templates, you must use <BR> or include <p>my text </p> around each
line.
Tip: If copying your existing text email templates and converting them to HTML template, make sure
you add <BR> wherever a new line is required.
Refer to Sample EFT Email Messages on page 160 that you can copy and paste in the EFT Email Messages
screen.
AP Payment Variables:
{DOCLIST} - Prints a list of AP Invoices that were paid.
{DOCAMTLIST} - Prints a list of A/P documents applied to the payment. Includes Document Number,
Date and Amount.
When you use HTML templates, the list is displayed in a table and alignment is controlled better.
Example:
If the transaction date is 10th October 2019, {PAYMENT_DATE} will display as 20191031 in the
email.
{PAYMENT_DATE_MM}-{PAYMENT_DATE_DD}- {PAYMENT_DATE_YYYY} will show as 10-31-2019
{PAYMENT_DATE_DD}-{PAYMENT_DATE_MM}- {PAYMENT_DATE_YYYY} will show as 31-10-2019
Example:
If the transaction date is 10th October 2019, {PAYMENT_DATE} will display as 20191031 in the
email.
{PAYMENT_DATE_MM}-{PAYMENT_DATE_DD}- {PAYMENT_DATE_YYYY} will show as 10-31-2019
{PAYMENT_DATE_DD}-{PAYMENT_DATE_MM}- {PAYMENT_DATE_YYYY} will show as 31-10-2019
Payroll Variables:
Any field from the EFT Payroll Audit log (ELPLOGD), surrounded by {fieldname} or with $ in front
{CREATENO} - Creation Number
{LINE}- Line Number
{DATERUN} - Date Run (e.g. 20180103)
{IDEMP} - Employee
{PEREND} - Pay Period End Date (e.g. 20190130)
{EAMOUNT} - Amount -
{BANK} - Bank Code
{FILETYPE} - File Type
{BANKNAME} - Bank
{BSBNO} - Branch Number
{ACCNO} - Account Number 123456789
{ACCNAME} - Account Name 100050acc
{PAYREF} - Payment Reference
{NAME} - Payee Name
{TEXTSTRE1} - Address 1
{TEXTSTRE2} - Address 2
{TEXTSTRE3} - Address 3
{TEXTSTRE4} - Address 4
{NAMECITY} - City
{CODESTTE}- State/Prov. BC
{CODEPSTL}- Zip/Postal Code
{CODECTRY} - Country
{NAMECTAC} - Contact
{PHONE} - Telephone
{FAX} - Fax
{EMAIL} - E-mail
{WEBSITE} - Web Site
{EXTRA1} to {EXTRA50}
You can include fields from the Payroll Cheque/Check History Summary table (CPCHKS or UPCHKS)
as follows:
{PAYCHECK_fieldname}
Example:
If the transaction date is 10th October 2019, {PAYCHECK_TRANSDATE} will display as 20191031 in
the email.
{PAYCHECK_TRANSDATE_MM}-{PAYCHECK_TRANSDATE_DD}- {PAYCHECK_TRANSDATE_YYYY} will
show as 10-31-2019
{PAYCHECK_TRANSDATE_DD}-{PAYCHECK_TRANSDATE_MM}- {PAYCHECK_TRANSDATE_YYYY} will
show as 31-10-2019
Hi {VENDOR_CONTACT}
Please be advised that a payment has been made to your nominated bank account on
{PAYMENT_DATE_YYYY}/{PAYMENT_DATE_MM}/{PAYMENT_DATE_DD}
Regards
{COMPANY_NAME}
<html>
<p>Hi {VENDOR_CONTACT}</p>
<p>Please be advised that a payment has been made to your nominated bank account on
{PAYMENT_DATE_YYYY}-{PAYMENT_DATE_MM}-{PAYMENT_DATE_DD}</p>
<p>The applied documents are as follows :</p>
<p>{DOCLIST}</p>
<p> </p>
<p>Regards</p>
<div><strong>{COMPANY_NAME}</strong></div>
<p> </p>
</html>
Hi {CUSTOMER_NAME}
Please be advised, according to our agreement, we have direct debited your nominated
bank account on {PAYMENT_DATE_YYYY}/{PAYMENT_DATE_MM}/{PAYMENT_DATE_DD}
The applied documents are as follows :
{DOCLIST}
Regards
{COMPANY_NAME}
<html>
<p>Hi {CUSTOMER_NAME}</p>
<p>Please be advised, according to our agreement, we have direct debited your nominated
bank account on {PAYMENT_DATE_YYYY}-{PAYMENT_DATE_MM}-{PAYMENT_DATE_DD}</p>
<p>The applied documents are as follows :</p>
<p>{DOCLIST}</p>
<p> </p>
<p>Regards</p>
<div><strong>{COMPANY_NAME}</strong></div>
<p> </p>
</html>
{EMPLOYEE_EMPLOYEE}
{EMPLOYEE_FULLNAME}
Hi {EMPLOYEE_FIRSTNAME}
Please find attached the remittance advice for your pay for Pay Period End {PEREND_
YYYY}/{PEREND_MM}/{PEREND_DD}
<html>
<div>
<p>{EMPLOYEE_EMPLOYEE}</p>
<p>{EMPLOYEE_FULLNAME}</p>
</div>
<div>
<p> </p>
<p>Hi {EMPLOYEE_FIRSTNAME}</p>
</div>
<p>Please find attached the remittance advice for your pay for Pay Period End {PEREND_
MM}-{PEREND_DD}- {PEREND_YYYY}</p>
<p>{BANK}</p>
<p>{BANKNAME}</p>
<p>{EAMOUNT}</p>
<p> </p>
<p>Regards</p>
<div><strong>{COMPANY_NAME}</strong></div>
<p> </p>
</html>
Tip:
Accounts Payable Setup is used to determine the A/R Refund payment type.
You can amend the payment types before posting the A/R Refund batch if you
Note: This option does not apply when creating A/R Refund in line with Sage's rules for
A/R Refund.
CRITERIA TAB
Use this Tab to select the Documents to include in the Receipt Batches.
The values setup on the specified receipt selection code appear as the default in the Create
Receipt Batch form, but you can change the values before creating the batch.
CUSTOMER:
Select the customer range
BATCH:
Select the batch range
INVOICE DATE:
Enter the Invoice date range
DUE FROM:
Enter the Due From date range
CUSTOMER BALANCE:
Enter a range for the Customer's Balance (this is the total amount outstanding)
Tip: When creating A/R Refund, if you only want to refund customers with a net credit
balance, set the From Customer Balance to the lowest negative number you want to
select. Set the To Customer Balance to 0.
INVOICE BALANCE:
Enter a range for the Invoice Balance (optional)
Account Set
Specify the range of account sets that you want included in the A/R Receipt/Refund
Batch, or leave the To field blank and specify ZZZZZZ in the To field to select from cus-
tomers with any account sets.
BILLING CYCLE
Specify the Customer billing cycle range that you want included in the A/R Receipt/Re-
fund Batch.
INTEREST PROFILE
Specify the Customer interest profile range that you want included in the A/R Receipt/Re-
fund Batch.
PAYMENT CODE
Specify the range of payment codes that you want included in the A/R Receipt/Refund
Batch.
GROUP CODE
Specify the Customer Group Code range that you want included in the A/R Receipt/Re-
fund Batch.
Tip: Select All to select All optional field values and Double click on the Yes
field in the Selected column to remove the values to exclude from the batch.
DOCUMENTS TAB
Include Credit Notes
Select “Yes” if you want to include any open Credit Notes in the calculation of the document
value.
Include Prepayments
Select “Yes” if you want to include any open Prepayments in the calculation of the document
value.
Include Unapplied Cash / Receipts
Select “Yes” if you want to include any open Unapplied Cash or Receipt Transactions in the cal-
culation of the document value.
Include Debit Notes
Select "Yes" if you want to include any open Debit Notes in the calculation of the document
value.
Include Interest Invoices
Select "Yes" if you want to include any open Interest Invoices in the calculation of the doc-
ument value.
EXCLUSIONS TAB
Use this tab to list the customer(s) which are to be excluded from the document selection pro-
cess and/or the Customer(s) and Document(s) combinations to be excluded from the doc-
ument selection process.
Note: If you enter a National Account Customer Number, then all child accounts
Select Tab
Use this tab to to specify details about the receipt batches to be created:
Criteria Tab
Use this tab to:
Document Tab
Use this tab to configure the document types to include in the calculation of the receipt amount, and
applied to the receipt created (AR Credit Notes, Prepayments, Unapplied Cash / Receipts, Debit Notes)
If you have already created a file for the Bank/Pay Period End Date, you will receive a warning to confirm
that you really want to re-create the file. If the files include the same employees, the remittance advice
will include details from both files. It is suggested to send the remittance advices from the "View'Clear
Payroll log" in EFT Periodic Processing and select an individual EFT file creation number.
License screen
You use the Orchid Module license screen to enter serial number and activation code.
When to use:
After a new installation or an upgrade to a newer version of Sage 300.
After a subscription renewal, enter the activation code with the new expiry date.
View the components of the Orchid module you are licensed for.
How to use:
Enter the license details, click the Add button to create the license file.
Restart the Sage desktop to enable the new license.
If you don't have an activation code for Orchid Module, you can create a 30-day trial license.
In the License screen, enter a serial number for the module, Sage 300 version and edition you are run-
ning.
Click the Add button. This create a 30-day trial license.
Tip: If you install a 30-day trial, enter a valid activation code before the trial expiry date to continue
using the application.
Note: In the four weeks before the expiry date, users receive a warning message when logging into
Sage 300 (weekly for the first three weeks and daily in the last week). If you don't renew before the
expiry date, the software will become read-only.
Important! If the Sage 300 Version or Edition change, a new Serial Number and activation
If the company name registered with Sage changes, a new Activation Code must be requested from
Orchid Systems.
When upgrading
If upgrading from a prior version with customisations done in the formats.ini file, you need to copy the
changes to the formats.ini to the userformats.ini. Refer to details in Upgrading EFT Processing Key Steps
on page 40
File Format
File format includes several sections:
1. Extra field declaration, including validations, label and help tips
2. Row Declaration
Each row type can have multiple lines with a number at the end to indicate the sequence. DetailAP1 and
DetailAP2
The definition of the header row(s) - general header for all transactions or an A/P specific header
or an A/R specific header
The definition of the detail row(s) - general detail for all transactions or an A/P specific detail or an
A/R specific detail
The definition of the footer row(s) - general footer for all transactions or an A/P specific detail or
an A/R specific footer
Example:
HeaderAP="A000000001[OriginatorIdNumber:%10C][FileCreationNumber:%04D]..”
DetailAP = "C[RecordCount:%09D][OriginatorIdNumber:%-10C]460..”
FooterAP = "Z[RecordCount:%09D][[TransactionTotalInCents:%014D] ..”
[USA_WF]
Name="USA Wells Fargo ACH"
BSBSize=9
AccountSize=9:17
BSBNumber="R/T Number"
AccountNumber="Account Number"
AccountName="Account Name"
SourceExtra1="Application ID"
SourceExtra2="Remote ID (RID)"
SourceExtra3="File ID"
SourceExtra4="Company ID"
Header=
BatchHeader=
DetailAR=
DetailAP=
BatchFooter=
Footer=
Validation examples:
Example: Bank Setup Validation and renaming.
AccountNumber="Account
Account Number will be Account Number
Number"
AccountName="Account
Account Name will be labeled Account Name
Name"
BSBSize is the size of the BSB field. This can either be one number, which means the BSB is a fixed size,
or two numbers in the format min:max.
AccountSize is the size of the Account Number field. This can either be one number, which means the
Account Number is a fixed size, or two numbers in the format min:max.
Example: [!DestAccountNumber] means that the Vendor Bank Account field cannot be
blank when creating the EFT File.
RENDER=API
Since the latest product update for Sage 300 version 2019, EFT Processing includes two dll engines to
generate the EFT Files:
The original dll ELEFT.dll works only with Sage 300. It includes support for optional fields on
AP Payments and AR Receipts headers. However, it doesn't support LUA functions for conditional
formulas in the file. While this dll is supported, enhancements are not added to it.
EFT.dll works with various ERP Applications. It includes standard predefined fields and includes sup-
port for LUA statements to write conditional statements in the file format. Any enhancements to
EFT Processing are done in the EFT.dll only. To use the newer dll, the file format must include the
line RENDER=API.
Note: If the RENDER=API is deleted or omitted, EFT Processing will use the ELEFT.dll.
To change an existing bank format (or create a new one), copy the original bank format from the format-
s.ini file to the userformats.ini file and make the required changes.
Note:
The userformats.ini can be copied to the customization directory to use standard Sage 300 func-
tionality of database and user control.
When processing a file layout, EFT Create File first checks the customization directory for
userformats.ini. If not found, it checks the ELXXA (e.g. EL68A for version 2021) folder of the Sage 300
install for userformats.ini and if not found it uses formats.ini in the ELXXA folder.
For a list of row types, field names and validations, refer to Bank Formats - Overview on page 173
Note: If you change the formats.ini file, you will get a "File Hash" Error when using the file in Create
EFT File function.
ROW TYPES
Within each section, there are 5 types of rows:
The row types are not case sensitive. DETAIL or Detail or detail is interpreted in the
same way.
Each row type is optional.
Some banks have the same format for AR and AP, some banks have different formats.
Example: For Example, CAN_CPA has the same header and footer format for AR and AP,
[CAN_CPA]
Name="Canadian CPA"
BSBSize=8
AccountSize=3:12
Header="A[RecordCount:%09D][SourceReference:%10C][BatchNumber:%04D]0[BatchDateJulian]
[SourceBankName:%-5C] [Blank:%-1409C][CR][LF]"
DetailAP = "C[RecordCount:%09D][SourceReference:%-10C][BatchNumber:%04D]460[Amoun-
tInCents:%010D]0[EntryDateJulian][DestBSB:%-9D][DestAccount:%-
12C]0000000000000000000000000[SourceAccountName:%-15C][DestAccountName:%-30C]
[SourceAccountName:%-30C][SourceReference:%-10C][DestId:%-19C]000000000 [Reference:%-15C]
[Blank:%-22C][Blank:%-2C][Blank:%-11C][CRLF]"
DetailAR = "D[RecordCount:%09D][SourceReference:%-10C][BatchNumber:%04D]460[Amoun-
tInCents:%010D]0[EntryDateJulian][DestBSB:%-9D][DestAccount:%-
12C]0000000000000000000000000[SourceAccountName:%-15C][DestAccountName:%-30C]
[SourceAccountName:%-30C][SourceReference:%-10C][DestId:%-19C]000000000 [Reference:%-15C]
[Blank:%-22C][Blank:%-2C][Blank:%-11C][CRLF]"
Footer = "Z[RecordCount:%09D][SourceReference:%-10c][BatchNum-
ber:%04D]0000000000000000000000[TransactionTotalInCents:%014D][NumberOfEntries:%08D]
[Blank:%-01396C][CRLF]"
Example: DetailAR is specific for AR Receipt transaction type, DetailRF is for refund trans-
action and DetailAP is for AP Payment transaction. Detail applies to all transaction types.
Row Sequence
Each row type also can have multiple lines with a number at the end to indicate the sequence.
For example: Header1, Header2 or DetailAR1, DetailAR2, DetailAR3.
[AUS_OCH]
Name="Australia Orchid Sample Bank"
BSBSize=0:12
AccountSize=0:20
BSBNumber="Bank Swift Code"
AccountNumber="Bank Account Number"
AccountName="Account Name"
BankAPPaymentReference="Payment Reference"
BankARPaymentReference="Receipt Reference "
CustomerPaymentReference="Customer Receipt Reference "
VendorPaymentReference="Vendor Payment Reference"
APINVOICE=”I,[InvoiceNumber:%-12C],[InvoiceDate:DDMMYY],[InvoiceDescription:%-75C],
[InvoiceNetAmount:%15D],[CRLF]"
HeaderAP="H,P[CRLF]"
DetailAP1="P,ACH,[BatchNumber:%08D][EntryNumber:%08D],[BankAccountNumber:%-34C],
[EntryDate:DD/MM/YYYY], [DestRemitName:%-35C],[DestBSB:%-11C],[DestAccountNumber:%-34C],
[Amount:%15D][CRLF]"
DetailAP2="[APINVOICES]"
FooterAP="T,[NumberOfEntries:%05D],[TransactionTotal:%14D]"
Important! A field can start with ! indicating it cannot be blank. During the Create EFT file,
Field Formatting
The Value of a field can be formatted to be displayed in specific structure.
A format mask is made up of multiple sections.
You can have any number of sections.
There are two types of sections:
1. Format
able
Plain text
This is just plain text. For example A - then the letter A would be written to the file
NUMERIC FORMATTING
D - numeric (same as D0)
D0 - numeric (sign, pad, value) only writes sign if it is negative
D1 - numeric (pad, value, sign) always writes sign
D2 - numeric (pad, sign, value) only writes sign if it is negative
- for Dx you can add another number (eg D0.2) which is number of decimal places
- if you omit the period (eg D02 vs D0.2) then no decimal point will be printed
- after D you can have a comma (eg D,0) if you want a comma instead of a period
Note: When using ^, the next character can either be a character to replace illegal characters with, 'r'
to remove illegals, 'S' to replace illegal swift characters with a space.
Examples:
Here are some more examples:
"%-10N" + "12345._890" --> NULL
"^ -10N" + "12345._890" --> "12345 890" - replace illegal with space
"^.-10N" + "12345._890" --> "12345..890" - replace illegal with .
"^r-10N" + "12345._890" --> "12345890 " - remove illegals
"^.3D-^.3D" + "123456" --> "123-456" - replace illegal with .
"^.3D-^.3D" + "12A456" --> "12.-456" - replace illegal with .
"^.3D-^.3D" + "12AZZZ" --> "12.-..." - replace illegal with .
"^.3D-^.3D" + "12A4C6" --> "12.-4.6" - replace illegal with .
"^Sc" + "INV[10]" --> "INV 10" - replace illegal swift characters with space
"^Sc" + "INV120111" --> "INV120111" - replace illegal swift characters with space
FIELD NAMES
The following fields are available for inclusion in the formats.
Fax
DestContactEmail The A/R Customer E-Mail or A/P Vendor Contact E-
mail
Miscellaneous:
10052)
TransactionTotal The total amount (eg $100.52 is 100.52)
NumberOfEntries Number of detail lines so far. This is coun-
ted from 1.
RecordCount Number of lines so far. This is counted
from 1.
CR The A/P Vendor Remit-To Fax
LF A line feed character
CRLF A carriage return / line feed
Blank A blank field. Useful for when there are
large runs of spaces or 0. Set the pad
length field to the size of the run.
Today The run date
+xD or -xD To add or minus number of days to the
date field. Eg. [Today+3D] [BatchDate-1D]
Reference The reference field from Create EFT File
screen
Description The description field from Create EFT File
screen
TransactionTotalInCents The total amount in cents (eg $100.52 is
10052)
TransactionTotal The total amount (eg $100.52 is 100.52)
NumberOfEntries Number of detail lines so far. This is coun-
ted from 1.
RecordCount Number of lines so far. This is counted
from 1.
CR A carriage return
LF A line feed character
CRLF A carriage return / line feed
Blank A blank field. Useful for when there are
large runs of spaces or 0. Set the pad
length field to the size of the run.
BCRLF A carriage return / line feed will only be
inserted if there is already a record /value
in the file. The use of this BCRLF specific
for formats without footer row and with
requirement that the last record should not
have carriage return. Instead of placing
CRLF at the end of detail row format, use
BCRLF at the starts of detail row.
FieldIDModifier Alphabet from A to Z. To indicate a par-
ticular batch has been run for Create EFT
file process for the number of time. The
first run will have ‘A’ as indicator, sub-
sequent run ‘B’, ‘C’ and so on.
Example: To use the company name from the Common Services file CSCOM you would use
[CSCOM.CONAME]
CPEMPL or UPEMPL,
CHK (for CPCHKH or UPCHKH)
ELEMPH
ELEMPD
Optional Field
(from Sage 300 version 6.0 onwards) and if the format doesn't include render=api
The layout is [tablename.optionalfield].
Example: [ARCUSO.PRIORITYCODE:%-5C].
VendorPaymentReference="Payment Reference"
CustomerPaymentReference="Receipt Reference"
Tip: Tips can be added to provide information about the field on the Sage 300 EFT Setup
For user defined fields, there are up to 9 extra fields available in the Bank Setup and up to 50 extra fields
available in the EFT Customers Setup or EFT Vendors Setup.
To activate the display on setup screen, declare the field and give it a name.
The syntax for extra field is: UserDefinedFieldName = "[fieldname:format]"
Eg.
BankExtra1="UserName"
BankExtra2="Password"
VendorExtra1="AccountType (1=Checking, 2=Savings, 3=Transmission)"
CustomerExtra1="AccountType (1=Checking, 2=Savings, 3=Transmission)"
To give a field extra information, we can use a tip.
When a tip is declared on the formats, on screen it will show as hyperlink.
Example: VendorExtra1="Payment"
\r\n To insert a new row for the remaining text after this key.
\t To insert a tab for the remaining text after this key.
Example: For example, in a situation where a beneficiary name is allowed for up to 35 char-
acters (on entry screen is up to 60 characters) and no trailing spaces allowed if it is less
than 35 characters, a user defined field can be created to retrieve the 35 characters of
beneficiary name and then used in the row with left aligned and exact length format.
AccName="[DestAccountName:%-35C]"
Header1=""[BankExtra1:%-C]","[BankExtra2:%-C]","[BankExtra3:%-C]","D","1","1"[CRLF]"
Header2=""Batch[BatchNumber:%06D]","[BatchDate:YYYY/MM/DD]"[CRLF]"
Detail1=""[DestID:%-C]","[AccName:%-C]","[DestExtra1:%-C]","[DestBSB:%06D]", "[DestAc-
count:%011D]","[AmountInCents:%-C]"[CRLF]"
CPA005MultiBankDisplay account number of the source bank from the selected range of batch. Same
bank use in multiple batch will appear only once in this function. The information to show on the Header
file of CPA005 format as the settlement account.
CPA005MultiBankIndexDisplay the Index of the bank of the source bank from the selected range of
batch. This information to show on detail line and to indicate which settlement account to be used for
the payment.
OneFilePerEntry=1This switch to indicate for each entry to go to an individual file.
IsEFT=0: This switch to indicate to skip checking whether the vendors/customers are setup in the EFT.
This is mainly used for formats that deal with Miscellaneous Receipt/Payment entry that don’t have Ven-
dor/Customer code.
UTF8=1 : This to indicate characters to be printed in UTF8.
AllowMiscellaneousPayments=1 : Use this switch to indicate that a vendor with no record in EFT
vendor is allowed in the EFT file (mainly for positive pay)
AllowMiscellaneousRefunds=1 : This switch indicates that a customer that has no record in EFT cus-
tomer is allowed in the EFT file (mainly for positive pay)
AllowMiscellaneousReceipts=1 : This switch indicates that a customer that has no record in EFT
customer is allowed in the EFT file.
{entry}Entry Number, this to be use with the option that each entry to go to individual file
Eval field
There are two new fields - Eval and EvalAtEnd. EvalAtEnd is done after all the detail records are written.
Within Eval* there are several functions available:
Note - it would all be one line - separated into multiple lines for readability.
That basically adds the sum into Amount1. The final "" makes it output nothing.
Detail2="[EvalAtEnd(SetAmount(2,0);AddAmount(2,GetAmount(1));AddAmount(2,GetField("Num-
berOfEntries"));GetAmount(2, 0))]"
That adds Amount1 and NumberOfEntries together, then prints it with no decimal places.
There's also UOBSetHashCode(), which sets amount 9 (eg 'Eval(GetAmount(9))'), and does the same as
the second if.
Nachanines
This is used as the last field in the footer section of the file when a file format needs to be in block of 10
lines.
[NachaNines] is adding lines filled with the character "9" at the end of the file to keep the file in the block
of 10 lines.
For example, If the total number of lines in the file is 8 lines, [NachaNines] will insert 2 lines of 94 bytes of
‘9’ characters.
Example:
This file has 5 lines, the bank requires 10 lines.
NachaNines field adds 5 lines of '9'
FooterAP3="9000001[ACHBlockCount10Div10:%06D][GetRecordCount:%08D][HashTotal:%R010D]
[TransactionTotalInCents:%012D][TransactionTotalInCents:%012D] [CRLF][NachaNines]"
LUA Functions
In the latest product updates in version 2019 and above, you can use LUA functions if the format uses
RENDER=API.
To create a LUA function, you need the following:
Example:
The example below checks if Ref is blank then the function returns first applied Invoice Num-
ber.
>>> lua
function GetRef(Ref)
if Ref == "" then return GetField("FirstInvoiceNumber")
else return(Ref)
end
end
<<< lua
Example:
DRef is the variable where you call the function and passing the parameter, in this case
DestReference.
DRef="[Eval(GetRef(Trim(GetField("DestReference"))))] "
Lastly, use the variable on the line where you want it to be displayed.
[USA_JPMC]
Name="JP Morgan Chase"
BSBSize=9
AccountSize=9:17
BSBNumber="R/T Number"
BSBNumberTip="Enter the 9 Digit R/T Number"
AccountNumber="Account Number"
AccountName="Account Name"
BankExtra1="Application ID"
BankExtra2="Remote ID (RID)"
BankExtra3="File ID"
BankExtra4="Company ID"
BankAPPaymentReference="A/P Payment Reference"
BankARPaymentReference="A/R Receipt Reference"
CustomerPaymentReference="Payment Reference"
CustomerPaymentReferenceTip="Enter the Payment Reference to be sent to the customer"
VendorPaymentReference="Payment Reference"
VendorPaymentReferenceTip="Enter the Payment Reference to be sent to the vendor"
HeaderAR1="LOGDX2010270388TB1TX00317*CH04000000000CTXC3173C0000000000000000[CRLF]"
HeaderAR2="101 [SourceBSB:%9D][SourceExtra3:%010D][Today:YYMMDD]
[Today:HHMM]1094101JPMORGAN CHASE [SourceAccountName:%-23C] [CRLF]"
HeaderAR3="5225[SourceAccountName:%-16C] [SourceExtra4:%-10C]PPD[Description:%-10C]
[BatchDate:YYMMDD] 1[SourceBSB:%8D]0000001[CRLF]"
HeaderAP1="LOGDX2010270388TB1TX00317*CH04000000000CTXC3173C0000000000000000[CRLF]"
HeaderAP2="101 [SourceBSB:%9D][SourceExtra3:%010D][Today:YYMMDD]
[Today:HHMM]1094101JPMORGAN CHASE [SourceAccountName:%-23C] [CRLF]"
HeaderAP3="5200[SourceAccountName:%-16C] [SourceExtra4:%-10C]PPD[Description:%-10C]
[BatchDate:YYMMDD] 1[SourceBSB:%8D]0000001[CRLF]"
Detail="6[DestReference:%2D][DestBSB:%9D][DestAccount:%-17C][AmountInCents:%010D][DestId:%-
15C][DestAccountName:%-22C] 0[SourceBSB:%8D][BatchNumber:%07D][CRLF]"
FooterAR1="8225[NumberOfEntries:%06D][WellsFargoHashTotal:%010D]000000000000[Trans-
actionTotalInCents:%012D][SourceExtra4:%-10C] [SourceBSB:%8D]0000001[CRLF]"
FooterAR2="9000001000001[NumberOfEntries:%08D][WellsFargoHashTotal:%010D]000000000000
[TransactionTotalInCents:%012D] [CRLF]"
FooterAP1="8200[NumberOfEntries:%06D][WellsFargoHashTotal:%010D]000000000000[Trans-
actionTotalInCents:%012D][SourceExtra4:%-10C] [SourceBSB:%8D]0000001[CRLF]"
FooterAP2="9000001000001[NumberOfEntries:%08D][WellsFargoHashTotal:%010D]000000000000
[TransactionTotalInCents:%012D] [CRLF]"
Example:
XPEMPL.LASTNAME to add theEmployee surname
ELEMPH.IDEMP for the employee ID
ELEMPD.PAYREF for payment reference