In tenth of November 2021, I delivered a presentation on DynUG conference at Microsoft Norway. The main purpose of this session is related to how to take advantage of standard functions in D365FO for customers and partners. This routine will help us to get a better overview of the standard solution processes, strengths, and weaknesses to avoid implementing unnecessary customization and find the best standard solution to streamline our business processes.
In this regard, pros & cons for using standard function have been addressed:
Easy access / Quick startup / Ready to use: D365FO user-friendly interface made this easy for user to work with the solution. Almost every form can be exported to Excel for further analyze or are integrated to Excel add-inn for export and import purposes via Excel. In addition, the search bar in the in D365FO make this easy for user to filter and find forms or report, this will compensate time for users working with D365FO.
Cost saving: Standard has cost saving in both the short and long term. In the short term, you save a lot on avoiding the development of adaptations (all of internal time and consulting time), but in the longer term, customizations result in higher maintenance costs. Each version update, development time, test time both from the supplier and internally in the organization.
Process-oriented: Standard solutions have been created to solve a process for customers, whereas Microsoft has continuous improvements. It can be integrated with several modules and the module organization allows an easy integration between processes.
A great toolbox for process improvements: Many functions that can add value to the solution and improve / complete processes.
Compatible with the latest version: Continuous updates of Microsoft almost are compatible with the previous version. This will develop the existing processes.
Microsoft support: You can use Microsoft docs article to get better understanding of standard functions in D365FO. In a case that you need assistance, you can get a support from Microsoft community by registering an issue on Finance forum to get help from partners or Microsoft Community or you can register a support case on LCS to get an assistance directly from Microsoft.
The process can be time consuming: The use of standard solutions can be time consuming for resources and therefore can charge a company costs if the process is not improved or not adapted according to business needs (i.e. Time is money).
Can create trouble with customizations: Standard features can create trouble with customizations with new versions that charge customers to test a lot before they deploy any version update. The truth about customization is that it can be time consuming, expensive, and its maintenance with each version update will add further actions for testing.
Can lead to a change in current processes: when customers come from a system that they used to apply a routine from their legacy system, implementing the standard in the new system will due to change the process. It can be perceived as negative; both considering that change is demanding and that it can lead to a cost.
EHF3.0 / PEPPOL BIS Billing 3.0
There are several standard functions in D365FO that have been designed to resolve processes based on each country local rules. When it applies to Norway, Ref. Stortingsmelding 22 (2018–2019) kap 16.7 Regjeringens tiltak; all public enterprises must use digital tools in the procurement process. The regulations shall promote efficient and environmentally friendly invoice handling in public procurement. The EHF (Norwegian: Elektronisk handelsformat) is based on the European standard PEPPOL BIS for electronic exchange of information between sender and receiver, throughout the procurement process. This format have the following advantages:
Standard format: EHF makes invoicing easier and faster since the involved actors send and receive documents in the same way, so that the document flow is smoother and the post-processing on the control side becomes easier.
Environmentally friendly invoice handling: Since EHF process is electronic; the regulations shall promote efficient and environmentally friendly invoice handling in public procurement by saving the environment for all paper invoices.
Easy processing of the invoice: Electronic invoices move directly to the accounting system of recipient, it will also pave the way to be paid. In comparison to pdf invoices that sent to the customer mail box and create a potential risk that some invoices do not get paid since they transferred to spam or junk email box of recipient. Then, you have a better overview of invoices.
Cost and time efficiency: EHF will save time and resources on non-manual handling of documents and hence reduce cost of invoicing.
It is possible to start sending invoice electronically in D365FO with EHF3.0 for Norwegian companies. You can check the following six posts on DynFOTech to get a better overview and enable configuration to send e-invoice files to your access point.
Concisely, following task need to be performed to generate invoice files and send to your access point:
Overall, understanding of standard functions in D365FO helps us to avoid implementing unnecessary customization and reduce buying extra solutions from 3pv. I personally recommend to adopt a customization or a 3pv solution when standard does not have solution process for your process or it is time consuming to reach the solution in standard (i.e. potential workaround is time consuming).