-
Set up customer and vendor compensation to be world wide not Hungary and Poland only
There's a great function "customer and vendor compensation" which is already there in application but limited to Hungary or Poland, it about offsetting customers and vendor balance (if they are the same).
This function is already required for some other companies I have worked with in different countries (Egypt - KSA - UAE).
So, this function is needed to be for all countries and only be limited by a parameter or anything, other than this function is in a high demand.
-
Print bank information on sales invoices
Business Central already supports the printing of the bank information on sales invoice, not only that but the users also get to choose which bank to print, not just the default bank (This was an idea and it was completed)
In D365FO, a default bank account is already identified on the legal entity level, why this can't be printed by default on the sales invoice report? Nevertheless, we should also get to choose which bank account to be printed as it might differ from a customer to other or at least a default bank account should be the default for each currency (I believe this can be maintained on the bank accounts form)
-
Set up mandatory payment references
After some digging to make the payment reference as mandatory for journals without using "Method of payment", I didn't face any solution to cover this requirement.
So whenever a user remove the method of payment, or making a normal bank transfer, there won't be any control on that, and he isn't obligated to enter the transaction payment reference.
However, I then encountered a localized functionality for Iceland called "Set up mandatory payment references", it requires the payment reference to be mandatory per main account, which is an okay solution, so this functionality should not be localized, Or at least a new functionality should be introduced to cover this part either by making it mandatory on the Journal Name level, or making the method of payment mandatory on the journal name, and this would make more control somehow, to always obligate the user to choose the appropriate method of payment, but I also believe that the both would be there for more control.
- Mandatory payment reference on the journal name
- Mandatory method of payment on the journal name.
-
Summarize amounts in bank account with ledger accounts
Currently "Summarize amounts in bank account" function only supports customer or vendor account types and doesn't support ledger account type.
A ledger type is needed, to be added to work with other payment types such as bridging, as you already know that bridging account can only be a ledger account, so if user wanted to enter a bank payment using a bridging account, this payment won't be summarized in anyway.
-
Removing the localization of the Additional Months field, in the terms of payment forum
In the terms of payment form, when using payment method as cutoff days, in some localization, there's a field called additional months, so that the due date can be calculated no only in the current month, but based on the cutoff days and adding months.
examples:
without using additional months functionality:
if we have a terms of payment ( Net 60 days from the end of the calendar Month), so if today us April 23 and cutoff day is 15 the due date will be May15th.
with using additional months functionality:
if we have a terms of payment ( Net 60 days from the end of the calendar Month), so if today us April 23,cutoff day is 15 and additional months of 1 the due date will be June 15th.
-
Legal entity overides - Suspended option to follow the same concept
The legal entity override functionality concept is to have different attribute other than the default attribute of the (Main account or the Financial dimension).
This concept should also apply to the "Suspended" option, for instance if I wish to "Suspend" a specific FD value for all legal entities (80+ Legal entities) except for only 1 legal entity , I should be able to do so.
Currently, it's not allowing me to do so, whenever a FD is suspended, this attribute cannot be overriden for a specific legal entity becuase it's dimmed.
I have noticed that the same behavior is happening with the Active from/to date, once it's defined on the main level it cannot be overriden,