Retail transaction consistency checker
This topic applies to Dynamics 365 for Retail and Dynamics 365 for Finance and Operations.
Functionality noted in this topic is available to targeted users as part of a preview release. The content and the functionality are subject to change. For more information about preview releases, see One version service updates FAQ.
This topic describes the retail transaction consistency checker functionality introduced in Microsoft Dynamics 365 for Finance and Operations version 8.1.3. The consistency checker identifies and isolates inconsistent transactions before they are picked up by the statement posting process.
When a statement is posted in Retail, posting can fail due to inconsistent data in the retail transaction tables. The data issue may be caused by by unforeseen issues in the point of sale (POS) application, or if transactions were incorrectly imported from third-party POS systems. Examples of how these inconsistencies may appear include:
- The transaction total on the header table does not match the transaction total on the lines.
- The line count on the header table does not match with the number of lines in the transaction table.
- Taxes on the header table do not match the tax amount on the lines.
When inconsistent transactions are picked up by the statement posting process, inconsistent sales invoices and payment journals are created, and the entire statement posting process fails as a result. Recovering the statements from such a state involves complex data fixes across multiple transaction tables. The retail transaction consistency checker prevents such issues.
The following chart illustrates the posting process with the transaction consistency checker.
The Validate store transactions batch process checks the consistency of the retail transaction tables for the following scenarios.
- Customer account - Validates that the customer account in the retail transaction tables exists in the HQ customer master.
- Line count - Validates that the number of lines, as captured on the transaction header table, matches the number of lines in the sales transaction tables.
Set up the consistency checker
Configure the "Validate store transactions" batch process, at Retail > Retail IT > POS posting, for periodic runs. The batch job can be scheduled based on store organization hierarchy, similar to how the "Calculate statement in batch" and "Post statement in batch" processes are set up. We recommend that you configure this batch process to run multiple times in a day and schedule it so that it runs at the end of every P-job execution.
Results of validation process
The results of the validation check by the batch process are tagged on the appropriate retail transaction. The Validation status field on the retail transaction record is either set to Successful or Error, and the date of the last validation run appears on the Last validation time field.
To view more descriptive error text relating to a validation failure, select the relevant retail store transaction record and click the Validation errors button.
Transactions that fail the validation check and transactions that have not yet been validated will not be pulled into statements. During the "Calculate statement" process, users will be notified if there are transactions that could have been included in the statement but weren't.
If a validation error is found, the only way to fix the error is to contact Microsoft Support. In a future release, capability will be added so that users can fix the records that failed through the user interface. Logging and auditing capabilities will also be made available to trace the history of the modifications.
Additional validation rules to support more scenarios will be added in a future release.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.