Comments
Dear product group, we just had another partner emphasizing the need for a change in this current design.
Following their insight: "This is a bug need to be fixed.
The function auto create journal, (the match rule) can’t be used when the posting date doesn’t match the bank statement booking date. Specially the bank fees normally happen at the end of the month. The file will be imported earliest the first date of next month. It will be caused different balance between the bank statement and bank transaction at the end of the month. "
Kindly review the matter again and reconsider the possible design change.
This is IMHO a dangerous idea! As a developer I would like that we can decided which fields the users should be able to see and hereby prevent them from "messing up their pages" with fields that either do nothing in their setup or have been "replaced" by other extension fields.
So if you plan to implement this idea, then at least make it possible to turn this feature off for all or some users.