12
STATUS DETAILS
Inactive
Ideas Administrator

Thank you for sharing your idea. 
We haven't heard this from other customers, yet, and this hasn't got enough votes for further consideration. For the foreseeable future, we are not considering the suggestion but if you find more customers that ask for the same scenario, please keep sharing the insights.
We do appreciate your feedback and hope you'll continue to submit ideas for improvement in the future.

Sincerely,

PM, Leonid Nesterov,

Microsoft.

Comments

M

Our customer also generates SEPA DD files for customer collections using ER and subsequently receives a response file in the pain.002 format from the bank. This is the same approach as what we have for vendor payment status updates in D365FO currently.
It offers the user reassurance that the file has been received by the bank and that some basic checking of data has been performed. Any issues can then be addressed proactively rather than reacting to a failed collection.

Personally, it feels like this should be achievable with a small number of changes - allow the ER return format to be mapped to the Customer method of payment. Then either add the Customer payment journal line entity to the existing vendor payment status ER data model and map this OR create a separate one.
The Payment Transfers form already exists, as does the Return file import menu item.

Category: Globalization - Regulatory features