D365FO

  On the pending invoice posting form, there are different dates that may need to be filled. But there are two fields that may be mixed up. Invoice Date and Posting Date.  -Invoice Date is the date of the real invoice and most of the calculations(cash discount, exchange rates etc.) are using this date. It is optional not to fill this information unless on the parameters it is set to be filled mandatory. (Account payable > Setup > Account payable parameters -> Require document date on vendor invoice) - Posting Date is the date the transaction is posted to GL. This may differ from the invoice date in many circumstances. For example the invoice may arrive to posting user after the invoice date, period is closed etc. This field is used for calculations if invoice date is not filled. To fill the invoice date is mandatory and it is set to today as default when invoice is created but can be changed before posting. In some circumstances, users may need to change or bulk ...

 Updates to Dynamics 365 Finance 2022 release wave 2 include general availability of vendor invoice OCR (optical character recognition). This will automate the reading and recognition of vendor invoices by providing OCR capabilities to complete the full end-to-end automation of accounts payable. I was expecting this functionality for a while. I've not set it up or tried before but we were using some third parties to manage this functionality.  According to the documentation, we will be able to Upload vendor invoices to pending invoices as header and lines and related attachments.  Will be managed through data entities. Vendor pending invoice header entity will be change for to add attachment and new entity to be added for attachments. Also for to manage the process UI forms will be added. According to my previous experiences, there is still need to cover the processes below: Use vendor invoice journal for the processes that do not use a PO or a pending invoice. Use vendor...

 When we say allocations of expenses through accounts and dimension, there are various ways that can be used in D365 FO. In this blog you can find these ways and their differences from one to another. Cost Accounting Module:  If you do not need/require to post any transaction or you think that there will be too many transactions appear on voucher transactions, then you can use cost accounting module to report on your balances. This module works separate from the GL module. Data is transferred from GL module and you prepare your allocation rules in this module and do your reporting. also you can use this module for to report different versions. Allocation Rules : You can define allocation rules and within the period you want to use, system will allocate the balance to the relevant account and dimensions. The pros of this type is that, you can trigger and change the rules whenever you want to . The cons of this type is, you need to trigger each rule one by one, wait for the repo...

  When you are in the design phase, you need to decide how many journal names to define. I would advise to use as minimum as you can but it depends on the parameters below with my experience. Which Journal Types are going to be used? Like payment journals, invoice journals etc. How many journals do we need for migration. Are we going to create one of one for each purpose of migration. Do we need separate journals or user groups for reporting purposes? Do we need separate journals for different work flow operations? Are we going to use same journal type but create new ones for managing operations/purposes from the modules like accruals, TMS related journals etc. Do we need to differentiate voucher series for easy reporting? Do we need to auto setup offset account for users not to select? Like bank accounts to be automated directly and not to be selected by the user one by one on each transaction. These questions will help you how many journal names to setup in the system for ea...

  In D365 F&O there are ways to manage the descriptions. You may find the list below: Manual:  You may fill the description in the journals per line before you post the transactions. you may fill both for account and offset account. If you define a description before, you may select one from the list. Automatic:  Some transactions are auto created to the journals or on transactions default from the hard coded codes, like asset lease management and some functionalities in TMS management. Default Descriptions:  You can setup default descriptions by transaction type (sales order invoice, Po invoice, revaluation etc). On the transaction types you can use static (constant) text and/or variables. Specific Cases:  There are specific cases like revaluation. If you define the text during to run in revaluation process, system uses that information instead of to use the definition on the default description. Or if there is no setup on default descriptions, cancel opera...

  Dynamics 365 -Project Management- Project Operations: Helps plan, estimate, schedule and track projects. -Sales : Helps to track contacts, leads , marketing lists, campaigns, service cases and opportunities. https://docs.microsoft.com/en-us/dynamics365/sales/overview -Marketing: With using Sales, Customer Insights, Teams and other products helps decision making. https://docs.microsoft.com/en-us/dynamics365/marketing/overview -Customer Service: Customer Service for customers. https://docs.microsoft.com/en-us/dynamics365/customer-service/overview -Field Service: Helps deliver on-site services for customers. https://docs.microsoft.com/en-us/dynamics365/field-service/overview -Finance: Decision making of financial insights. https://dynamics.microsoft.com/en-gb/finance/overview/ -Supply Chain Management: Manage Supply Chain processes for all inventory related transactions. https://dynamics.microsoft.com/en-us/supply-chain-management/overview/ -Intelligent Order Management:C oordinate,...

   I were in a meeting yesterday of Tech Talk 2 days ago and I found that very useful if you have too many transaction to proceed.    This is a pretty new feature.  Was available in 10.0.25 but with 10.0.29 enabled with all instances. Can be enabled in feature management.    As a setup, first you have to set the  batch reserved capacity level parameter under batch global settings. There are 4 capacity type to be selected. 1.No reserved capacity – Default 2.Low reserved capacity –  %10 3.Medium reserved capacity – %15 4.High reserved capacity –  %25    You can not reserve full capacity.    Then on the batch groups, you define priority. Can see the weigh of the priorities. 1. Low: 5% 2. Normal: 10% 3. High: 15% 4. Critical: 30% 5. Reserved Capacity: 40%  Links: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/priority-based-batch-scheduling#set-the-batch-reserved-capa...

  Before to start the balance migration, be sure that all the master data is in the system like bank accounts, GL accounts, vendors , customers and their posting profiles. Also need at least one journal to be able to post the transactions. You may use a separate journal to be used once or can use one of which are already defined and to be used while balance upload journal will stay forever in the system and can not be deleted. But you may restrict by to add a user group , so that users will not see in the future as a solution. Also may require a separate journal o use a separate voucher series for balance upload but that also can be managed by to change the original journals number sequence as well. One daily journal will be enough but it depends on the implementation type while if assets are going to be uploaded or vendor invoices for balance upload need to be reported as invoices in transactional level.     While modules are used in D365FO, module related accounts ...

     What we should understand is Cost Management Module is just a module for calculation. So before this module is used, data in the system must be ready and correct. And for data to be correct, we have to setup the system correctly and train users.     In this blog I would like to explain the key points that needs to be controlled before to run the the inventory closing. I assume that the closure is done monthly basis. Before the postings 1. Train users how to process the transactions 2. Train users on which reports to use on daily, weekly and month end basis. It is very important to control the system while there is time for the month end. Not wait till the month end for controls. 3. Prepare a document/process flow of month end closure. 4. Setup item related setups correctly. (Which cost method to be used, price lists, inventory dimensions) Before to run closure: 1. Control the production orders  at the month end, all the status must be in "Ended" s...

  We have the new release of D365FO. 10.0.27 has only couple features to be released but some of them were really needed one like the customer aging report performance and bank reconciliation cancelling. Can find the list of details in the link.  https://docs.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-changed-10-0-27

  This question is usually asked and I see this question again couple of days ago in the community forum. So rather than to give an answer that has been explained technically, I would like to give that my answer for this question.  1. Newness:  While it is a Microsoft product, innovation is everywhere. The team is open for new technologies and improvements. 2. Documentation:  Has a huge documentation , in which is updated and is easy to understand. 3. User Support:  Supports users with the ticketing system. 4.  Project Support:  It is not only the programme that you but but also guides on how to process your project. Microsoft also cares on the project to success. This is why you can use Success by design documentations and LCS tools to decide your project models and processes. 5. Reporting Tools:  There are various reporting tools that you can use within or outside of the programme. For internal use, I can give example of standard queries, SSRS r...

  There are various reconciliation reports between module and GL in the system , so no need to define the dimensions to full fill this need. 5. Will the dimension to be automated? User may have some issues to fill all the dimensions in the system during the entry of the transactions. So less is better but if the dimension is really needed than need to be checked if these can be automated by to select on the main data like on products, sites, vendor, customer, account, employee etc. Or may be used in derived dimensions. 6. Can two information be grouped in to one dimension and then solve the grouping in the reporting tools? User can select one dimension rather than to fill multi fields and then solve the grouping with the reporting tools. This will need smart coding during creation of the dimensions.

Telemetry data is the base of the information for environment monitoring and used in three use cases  Monitoring Diagnostics Analytics Let me go through for each subject one by one quickly and explain which has been used for which purpose. Monitoring Monitoring in basic just for monitoring your environment if is in active state, up and running. This monitoring can be done in two states  Availability monitoring  Health monitoring Diagnostics High detail of telemetry data is used for user created issues to identify the real cause of the issues. In addition the SQL data can be added to identify the performance issues too. Analytics Another usage of telemetry data. This part is can be done only by Microsoft now. Microsoft tracks the feature usage and performance through Power BI. Access LCS Monitoring and Diagnostics portal Navigate to LCS and select your project. Select necessary environment from the Environments section. On the opened page find the Environment Mon...

      Derived Dimension functionality is used to automate the related dimension and prevent users to do mistakes during entries. Even the dimensions are derived, user can be able to change/override the derived dimension if prevent setup is not set.     For example, you have 2 dimensions. Department and Cost Center. You need the department dimension to filled in auto once user selects the cost center. You use Department dimension for reporting purposes.  Department: Project Operations Cost Center: ERP                           CRM Once this both cost centers (ERP and CRM)  are attached to the Project Operations department, user only needs to select one the cost center and department dimension information is auto filled.   You can link more than one segment to dimension segment.      For example: You have 3 dimensions; Product, Department and Cost Cen...

       Cost Accounting is a module for reporting purposes. It looks like a separate module /ISV  that is embedded to D365 FO. But it is one of the standard modules.      It is often mixed up with Cost Management. Cost management is used for inventory transactions inquiries, revaluation/closing operations and item costing operations.       In cost accounting module you are able to manage cost allocations within D365 or Ax 2012 or upload data from Excel.      System operates the transactions to copy data from the GL module if it is an operational data from D365 and allocated the transactions due to the rules setup in the module.      You can do versioning due to the allocation rule setups user do.      There is a detailed documentation for this module in Microsoft docs. Which has wonderful examples in the documentation.     The only think that is a bit   confusing i...

      There are two ways to manage the bank reconciliation.  1. Manual Reconciliation: Bank reconciliation is made from the bank account from account reconciliation page but all the transactions are manually marked and reconciled. For to cancel a bank reconciliation cancel feature needed to be enabled. 2. Advance Reconciliation: For to use advance reconciliation, bank needed to be selected. Once selected, can not be removed. Then users needs to upload the file (MT940 etc) for the reconciliation. Users can setup rules for auto reconciliation for to match the file with the transactions and for the rest, user can manually match the transactions. Once reconciled, user can always cancel the reconciliation with to enable feature. If there are minor differences, these difference can be posted in differences accounts with the setup applied by the user. For older versions, if there were posted differences, it was not allowed to reverse the transactions and there was a need fo...

      Today, I would like to share the reporting possibilities of D365 FO. There are various ways to report; 1. SSRS: Most of the SSRS reports are in the system ready to be used. But if there is a need to add a new report or a field/grouping etc to the current report, there is a need for a developer. This kind of reports are mostly used for internal needs and maybe sent to 3 rd parties in a proper shape. 2. Embedded Power BI: There are Power BI reports that are already created in the system and embedded in the modules. These reports are easy to use and is more focused on the visual.  3. Power BI: Power BI reports can be created with the Power BI desktop application and easy to manage. 4. Management Reporter: Management Reporter tool is a user efficient tool that users can create reports  from COA, transactions, budget and dimensions. Users can create their own reports or use/change the ones that are already offered in the system like audit trail, balance sheet, ...

       Payment Proposals can be used both for customer and vendor transactions. You can always pay to vendor or collect from customer manually and match invoice and payment. But  think using payment proposal is even better.      By to use payment proposals you can achieve the process below:     -  Able to see the open invoices     - Able to see the open balances of an invoice for partial payments     - Able to filter the due date if not paid transactions are not required to be seen     - Able to filter payment per currency, posting profile     - Able to see prepayments       To use the proposals, these processes below needs to be applied.     - Settle the payments and invoices properly     - Track advance payments     - Setup posting profiles properly  

      Management reporter is  a tool that help users to create their own financial reports without customization/development or help from the IT team/consultants . Is used to prepare financial statements such as income statements, balance sheet etc which has the GL transactional/budget data and dimensions in D365 F&O. It was outside Ax but now you can reach within the D365 F&O.      You may use the functionalities below:          -    Transactional and Budgets Data          -     COA and Dimensions          -     Total Accounts          -     Report Variances          -     Pre Set Reports          -     Report Details of Transactions like voucher number, vendor and customer etc for audit reporting         -...

      Tax Calculation service helps system to calculate complex taxes between country and locations and EU and multiple tax registration ids. For this purpose you have to setup RCS, enable feature and setup all the scenarios in the tax calculation engine. Not only it helps calculate these but more complex scenarios like calculation of taxes based on margin.     You may find the documentation of Microsoft below and also a video that briefly explains how system works. https://docs.microsoft.com/en-us/dynamics365/finance/localizations/global-tax-calcuation-service-overview https://www.youtube.com/watch?v=B2fN9AHoYnQ