web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

EFT File Generation Issue - Business Central OnCloud AU Localization

(0) ShareShare
ReportReport
Posted on by 85

Before 2021 Wave 1 Update and also till 18.0 for Business Central, from Payment Journal, EFT File was generated with Document No. displayed in the Exported File (.aba Format) in every Line but from 18.1 (the latest version) Microsoft has used the Payment Reference field of Payment Journal instead of Document No. because of which now the file that gets Exported has blank value at that place as Payment Reference field was never used for generating File. That means whatever value was taken in Document No. field, now it needs to defined in Payment Reference Field.

Any specific reason for this kind of change from Microsoft? Is there any default way (configuration) to accommodate this change or will have to solve this issue with customization only?

I have the same question (0)
  • Suggested answer
    Community Member Profile Picture
    on at

    Chanky,

    I checked the v18.1 release, for AU, and cannot find such a referenced update (link below):

    support.microsoft.com/.../update-18-1-for-microsoft-dynamics-365-business-central-2021-release-wave-1-application-build-18-1-25158-platform-build-18-0-25290-c2b1b1d3-e875-4079-817e-aa51454feddb

    I hope those in the Forum from Microsoft can chime in. I would recommend you contact your Partner who can also assist if there are other issues causing this.

    Hope this helps.

    Thanks,

    Steve

  • Chanky Profile Picture
    85 on at

    Hi Steve,

    Thanks for the response. I am myself a Developer & from the team of a Partner. Some of our customers reported this issue on the next day of the latest update. And as this issue is related to the Payment so I had less time to find a solution for it. So as soon as I found that Microsoft has made this change like by removing use of Document No. and using Payment Reference instead, I quickly created Extension and solved this issue by flowing the value of Document No. in Payment Reference Field.

    But, just wanted to know the reason for this change from Microsoft as its not documented anywhere. Or maybe I am missing something? Don't know :/

    As this is a process change for Customers no Customer would like to do an extra step that previously never existed.

  • Suggested answer
    Marco Mels Profile Picture
    on at

    Hello,

    This indeed was a change done based on partner request.

    EFT Banking export uses internal document for payment reference.

    Partners feedback was that it is weird that we cannot use the External Document No., Payment Reference or Message to Recipient for this purpose.

    The Vendor would like to see their number in there, and not the BC internal document number linked to their information. It would be much easier to identify if we could use the vendor number than the internal information.

    The ideal would be maybe a setup where the user could select to use:

    - Document No. --> we currently use this one with no other option

    - External Document No.

    - Payment Reference

    - Message to Recipient

    At least, 1 of them, so the user could select the External information to be exported in the EFT file, and not our internal Document No. which means nothing for the vendors.

    Based on this we swapped to Payment reference which makes has more relevance.

    The change can be first found in v17.6 and as a result also in v18.

    support.microsoft.com/.../update-17-6-for-microsoft-dynamics-365-business-central-2020-release-wave-2-application-build-17-6-23727-platform-build-17-0-23708-5204bd69-9c14-44ca-b1bc-aaee9aaef94b

    391963 The EFT Banking export uses an internal document for the payment reference in the APAC version.

    Thanks.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 3,143

#2
Jainam M. Kothari Profile Picture

Jainam M. Kothari 1,694 Super User 2025 Season 2

#3
YUN ZHU Profile Picture

YUN ZHU 1,067 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans