25 Sep’19

D365 Finance and Operations, D365 RetailData fidelity checker in Microsoft Dynamics 365 Retail

In this blog, I am going to shed some light on a new feature which is already available in the public preview of Microsoft Dynamics 365 Retail. General availability will be sometime in Oct 2019

Statement posting process is used to account for the transactions that occur in Cloud point of sale (POS) or Modern POS (MPOS). This process uses the distribution schedule to pull a set of POS transactions into the headquarters (HQ)

The parameters that are defined on the Retail parameters and Stores pages are used to select the transactions that are pulled into individual statements.

A retail transaction consistency checker(Validation checker) identifies and isolates inconsistent transactions before they are picked up by the statement posting process.

We faced a lot of issues with statement posting. The process often asks you to run a validate store transaction job but still the statement won’t post. Raising an MS support ticket is the only way to fix this.

I believe data fidelity should make the statement posting process more efficient. Fidelity checker does the following:

  • Data fidelity checker will check the data for omissions and anomalies and only those transactions that pass the validation will be included in the statement process.
  • Validate records, gift cards, tax table
  • Fix the transactions by users who are not in line with the auditing purpose.
  •  Also, currently the statement posting process first reserves the inventory throughout the day as the transactions are carried out. Which is temporary. Then at the end of the day during the statement posting system removes these reservations for inventory created and then creates sales orders, payment journals, and ledger journals in the system.
  • This process is not very efficient because when all the transactions are processed together at the end of the day, it could result in overloading and failure. To address this in future this process will be removed all together. Which means no temporary inventory job will be created. A new job which will run as per predefined schedule will create sales orders, invoice them, and create, post, and apply for payments.
  • The statement document that gets created at the end of the day will only be used to calculate and post any counting variances.
Written by

Rutvik Mehta

Functional consultant

Leave a Reply

Your email address will not be published. Required fields are marked *

Want to streamline your business processes?

  • This field is for validation purposes and should be left unchanged.

Recent Articles

  • Introduction to Microsoft Dynamics Commerce Tools

    19 October’ 2019

    As we know, Dynamics 365 Commerce is released in the preview version, So in this blog, we will have a quick explanation ...

    Read more
  • Error Handling Approaches for Integration

    16 October’ 2019

    Introduction: Handling Errors is a best practice in Integration when integrating to keep a track of the Errors that occu...

    Read more
  • Change in URLs for Business Central Tenants

    16 October’ 2019

    Change in base URLs for Business Central SaaS Tenants. I have noticed the Business Central links for Tenants have chan...

    Read more
  • Record Deletion Tool in Business Central

    16 October’ 2019

    Introduction: After a successful Go-Live in Business Central, we somehow need to delete a record from Backend. There is...

    Read more
  • Error “A reference to ‘xyz ‘ is required to compile this module” solution

    10 October’ 2019

    Many of the time while building project/solution we came across the “reference is required to compile this module ...

    Read more
  • We respect your privacy.
  • This field is for validation purposes and should be left unchanged.