How to set up NAV 2017 for EFT payments in Australia

EFT payments are enabled in NAV 2017 without customisation. It just requires proper setup.

First, setup the Bank Account details for the account you will be using.

 

Relevant fields are:

EFT Bank Code: the approved financial instituion abbreviation. Westpac’s abbreviation is WBC. Ask your financial institution for this.
EFT BSB No.: the Bank Branch No., same as in the General tab. This seems to be an unnecessary duplication of fields but is required.
EFT Security No.: User Identification Number, sometimes called APCA number, allocated by financial institution to organisation. Required.
EFT Security Name: Name of organisation supplying EFT file.
EFT Balancing Record Required: tick only if your bank requires this.

 

Next, setup the Vendor Bank Account cards and edit the Vendor records. Every vendor who will be paid by EFT must have a Vendor Bank Account record. The EFT Managment codeunit looks for the record whose code is the EFT Bank Account No., so if you do not use the EFT Bank Account No. and the Code, you will need to edit the EFT Management codeunit where it looks for the Vendor Bank Account record.

You must enter the Bank Branch No. in the EFT BSB No. field. It is a duplication of the Bank Branch No. field on the General tab, but it is required.

Then edit the Vendor Card.

Relevant fields:

EFT Payment: must be ticked.
EFT Vendor Bank Account Code: required. Use the Vendor Bank Account code you added or edited in the previous step.

 

Once you have all the Vendors setup, you are ready for the payments. Go to the Payment Journal. You probably will want to create a General Journal Batch for EFT payments. The balancing account will be the Bank Account which you edited in the first step.

If you use Suggest Vendor Payments, tick the EFT Payments field so only vendors setup for EFT Payments are included.

 

Payment records to pay the payables meeting the conditions will be added to the Payment Journal.

Notice that the field EFT Bank Account No. is populated. The next field, Recipient Bank Account, is the EFT Bank Account No.. Leave it blank. The EFT Management codeunit uses the Bank Account No. field from the Vendor record, not from the Gen. Journal Line. Message to Recipient is not used.

Below is a payment journal line that I entered manually.

 

Notice that theĀ  EFT Bank Account No. field is not populated. You will need to enter it manually, or edit the Gen. Journal Line table function GetVendorAccount to populate that with the EFT Vendor Bank Account Code in the Vendor record.

After you have the lines in the Payment Journal ready to pay, go to the Navigate tab in the Action ribbon, click on EFT Payments, then Create File.

 

You are then prompted for the File Name and Description.

Usually the file has the filename extension of aba.

Click OK, and the EFT Management codeunit will create a file, or display error messages.

When I looked at the file created, I noticed the BSB No. looked like 999–9 instead of 999-999. The EFT Management codeunit inserts a hyphen in the 4th position without checking if a hypen is already there. To fix this, edit the FormatBranchNumber function to return the BranchNo field with change if it contains a hyphen.

Another issue that I ran into is needing to editing the payment lines and re-create the EFT file but getting an error. When the EFT file is created, it populates the EFT Register No. field in the Vendor Ledger Entry table for the Apply-to records. When running it a second time, there is an error because the Vendor Ledger Entry record had a value in the EFT Register No. field. To resolve this, I added a function to clear the EFT Register No. for the Register No. of the current journal, and added a Page Action for it under EFT Payments.

So there are some issues that must be worked through. But once that is done, the process works well.