-
-
Notifications
You must be signed in to change notification settings - Fork 414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[12.0] [RFC] Account Payment Return Import SEPA PAIN: reason codes #226
Comments
Well, I don't remember well the source of this, but 225 can be too much, isn't it? Should we put all of them or only the most use ones? |
Question is: how to know which are the most used ones? I propose to add them all. If at some point people combine manual entry of return with PAIN import, one possibility could be adding active flag on return codes so they don't appear in the drop down list, while the import code could still use them. |
Would a XML file the best way to embed the 225 return reasons in the module (in terms of maintainability) ? I don't know if it can be done with a CSV file (no |
As this is standard, it can be tolerable to be put as CSV noupdate=0, as you shouldn't touch here. If you want, then create others. What do you think? |
Done in 12.0, I close this issue. |
The ISO20022 documentation lists 225 return codes while the OCA addon lists 20 codes. Shouldn't all these missing codes be added in the OCA addon?
The text was updated successfully, but these errors were encountered: