Home | Logon | Contact | Newsletters | Search:- 

EFTPAC Version 6.3

Modulo Software | Eftpac Sage 300 EFT BPay Payments Receipts
Sage 300 Add In Product Download Demo
EFT Products Comparison Chart
EFTPAC Supported Banks
WebEx Online Demo

IMPORTANT: EFTPAC V6.3 Product Update 2017 is required for use with Sage 300 2017 (6.4)

Why Use Electronic Payments
  • Electronic Funds Transfer and BPay are the most efficient means of being paid by customers and paying creditors.
  • EFTPAC supports BPAY to allow you to quickly and easily pay your bills, using a BPAY Biller ID and Reference Number
  • No need to purchase cheque stationery
  • No need to sign or bank cheques.
  • No rekeying of data - creates EFT files directly from vendor payment and customer receipt batches
  • Easy to use and saves you time

EFTPAC creates BPay payments and EFT payment, receipt and refund files from Accounts Payable payment batches and Accounts Receivable receipt and refund batches - both posted and unposted (subject to user security privileges). Many North American, Australian, New Zealand and other international bank file formats are supported.  Modulo will add other formats as requested. 

For a list of currently supported formats and for information on adding new formats to EFTPAC please click here.

  • EFTPAC 6.3 (2016) provides compatibility with Sage 300 System Manager and General Ledger versions 6.3 (2016)
  • EFTPAC 6.3 (2016) is developed with the Sage 300 Software Development Kit (SDK) and supports operation in both the Sage 300 Windows, Internet Explorer browser and Portal desktops.
  • *NEW*The Westpac PPS BPAY format was updated to comply with changes to the format.              
  • EFTPAC now allows AP EFT and BPay payments and AR EFT receipts to be created for batches containing entries of type Check or Other. Prior versions of EFTPAC required batches containing checks only - which meant you had to print Accounts Payable checks and advices for EFT or BPay entries, even if they weren’t needed. In EFTPAC 6.3 if you don’t want to print Accounts Payable checks and advices, for your EFT or BPay entries, you don’t have to. You can use payments of type “Other” which don’t require a remittance advice to be printed in Accounts Payable.

    Additionally if you use MAILPAC you can now create and email your remittance or receipt advices for any type of Payment or Receipt entry and for both posted or unposted batches. This means you don’t have to wait until batches have been posted to send your remittance or receipt advices if you don’t want to. 

    The use of payments of type “Other” is optional, so if you are upgrading from a previous version of EFTPAC and are happy with the traditional EFTPAC processes and setups, you don’t have to change a thing.
  • If you use the Accounts Payable Create Payment Batch function to system generate payment batches, you can now generate batches of type “Check or “Other” and make EFT or BPay payments from EFTPAC.  To facilitate this, you can setup AP Payment Codes for EFT and BPAY payments and assign them type “Other” if you don’t want to print AP Checks and Advices or assign them type “Check” if you do. If you assign your Vendors or Vendor Groups to use your EFT or BPAY Payment codes, the AP Create Payment Batch function will allow you to generate batches for those Vendors using the Payment Code range on the Create Payment Batch screen. 
    The use of Payment Codes to generate batches or to generate payments of type “Other” is optional. So if you are upgrading from a previous version of EFTPAC and are happy with the traditional EFTPAC processes and setups, you don’t have to change a thing.
  • The new feature allowing EFT or BPay Payments of type “Other” means that some or all EFT and BPay payments may not have a valid Check Number. For cases where the Check Number is chosen as the lodgement reference for a payment, but the Check Number is blank or 0000000000, EFTPAC will use the Document Number instead. All Vendor payments are assigned a unique Document Number regardless of the document type.
  • Process EFT or BPay payments for Customer Receipts, Customer Refunds, Vendor Payments or Miscellaneous Payments.
  • EFT details can be maintained separately or via EFTPAC enhanced versions of the Sage 300 AP Payment Entry, Customer or Vendor screens. Multiple bank account details may be maintained for Vendors using vendor remit to locations.
  • Flexible Lodgement References. The Lodgement Reference that shows on the customer or vendors bank statement can be set to any one of the following:
    (i) Same for all payments
    (ii) Unique value for each Customer, Vendor or Vendor Remit to Location
    (iii) Sage 300 payment/check number
    (iv) Last applied invoice for the payment. Lodgement References can also be changed within EFTPAC following creation of the EFT file.
  • Maintains a full audit history of all EFT files created by EFTPAC. Historical files can be viewed, cleared or recreated at any time (subject to user security privileges).
  • Maintains an audit log and reports on all changes made to EFT bank account records for Customers, Vendors, Vendor Remit to Locations and Miscellaneous bank records.
  • Automated Customer Receipt batch creation based on the AR Aged Trial Balance report. This streamlines EFT processing for accounts receivable customers.  
  • Each EFTPAC 6.3 bank record links to a specific bank account defined in Sage 300 Bank Services.
  • EFTPAC 6.3 can be used with multiple Sage 300 companies.
  • EFTPAC allows the electronic file created to be viewed prior to transfer to the bank and indicates to the operator possible problems or omissions in the file. This allows the operator to correct issues prior to submission of the file to the bank.
  • Optionally forward date EFT or BPay payments as required.

Technical Specifications

  • Sage 300 2016 (6.4) System Manager and either Accounts Payable or Accounts Receivable modules, or
  • Sage 300 2017 (6.4) (with latest Product Update - IMPORTANT) SM 6.4 with EFTPAC 6.3 Product Update 2017 and either Accounts Payable or Accounts Receivable modules, using one of the following databases:

    Microsoft SQL Server

  • Microsoft Windows 7 or above
  • Prior versions of EFTPAC are available for Sage 300 6.2 (2014) and prior
  • EFTPAC does not provide modem communications software or bank specific file submission software
Modulo Software