Skip to main content
Community site session details

Community site session details

Session Id :
Business Central forum

EFT (Canada) - Generating EFT Files action gives "the specified transit number xxxxx for vendor is not valid"

(0) ShareShare
ReportReport
Posted on by 52

Hello,

I am trying to test out and generate an EFT file using the CA EFT DEFAULT bank format.  The following has been configured as per the documentation and blog:

  1. Bank Account Card set up
  2. Vendor Bank Account Card set up
  3. Payment Journal Batch set up

I have a simple payment journal line set for EFT.  I can export the line successfully.  When I then go to generate the EFT file via the Generate EFT Files function, I receive an error about the vendor's transit number (as shown in the subject).  I have tried several different account details, including my own account, and none seem to validate.  Is anyone aware of some configuration that might be triggering it to validate a different format than expected?

On the vendor bank account card, the bank branch number is 3 digits, the account number is 7 and the transit number is 5.  All other fields are blank (except Code and Name).  Use for Electronic Payments is checked.

On the bank account card, the country export format is CA and the Payment Export Format is CA EFT DEFAULT.

Any assistance or insight would be greatly appreciated,

Terry

  • Verified answer
    Terry Schmidt Profile Picture
    52 on at
    RE: EFT (Canada) - Generating EFT Files action gives "the specified transit number xxxxx for vendor is not valid"

    It turned out that the Fall 2018 update broke the EFT logic, using the incorrect validation code (ACH rules).  Microsoft confirmed awareness of the issue and had a patch to release.  All Canadian tenants apparently should now have this patch (Build 25251).  I've confirmed that this build resolves the validation issue around transit numbers.

  • Terry Schmidt Profile Picture
    52 on at
    RE: EFT (Canada) - Generating EFT Files action gives "the specified transit number xxxxx for vendor is not valid"

    In further investigation, I was able to pull up some codeunits from NAV 2018 to compare against to see if I can determine what the problem might be.  The configuration for CA EFT DEFAULT data exchange definition is to use codeunit 10321-Exp. Validation EFT.  In NAV 2018, this codeunit is just a shell with nothing it in, so assuming that is the same in Business Central, it is not executing the validation from there.  I pulled up the codeunit 10094-Export EFT (ACH) to see what transit number validation is being done in there.  Within that codeunit, it expects a minimum 9 digit transfer number and then does a checksum on the number.  I determined what a valid transit number would be using that logic as a baseline and applied it to my vendor's bank account in Business Central.  Lo and behold, the validation passed and the EFT was generated.  In one sense, great - figured out how it is validating the transit # - but in the other sense, what is going on here?  The CA EFT DEFAULT definition expects a 5 digit transfer number.  My CDN bank account is a 5 digit transfer number.  So why is it validating a 9+ digit transfer number?  Is Business Central not respecting the configuration seen under Data Exchange Definitions?

    Data-Exchange-Def.png

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard > Business Central

Featured topics

Product updates

Dynamics 365 release plans