Validation rules will continue to be added in subsequent releases. The Validate store transactions batch process checks the consistency of the commerce transaction tables, based on the following validation rules. The following illustration shows the recurring daytime processes for uploading transactions, validating transactions, and calculating and posting transaction statements and the end of day processes for financial statement calculation and posting. The Validate store transactions process prevents these issues by ensuring that only transactions that pass the transaction validation rules are passed to the transaction statement calculation process.

If inconsistent transactions are picked up by the statement posting process, sales invoices and payment journals that are created can cause statement posting to fail.

Taxes in the header table don't match the tax amount on the lines.

The number of items that is specified in the header table doesn't match the number of items in the transaction table.

The transaction total in the header table doesn't match the transaction total on the lines.

Here are some examples of factors that can cause these inconsistencies: When you try to post a statement, the validation process can fail because of inconsistent data in the commerce transaction tables. The validation process identifies and marks transactions that will cause posting errors, before they are picked up by the statement posting process. This article describes the functionality for validating store transactions in Microsoft Dynamics 365 Commerce.

How to delete roundedtb