BeyondERP.Newsletter
Menu

Job page · Retail and Commerce

Calculate transactional statements in batch

A batch job that adds all unposted, validated store sales transactions to new transactional statements.

Business process
Post store end-of-day financial statements in Dynamics 365 Commerce
Menu item
RetailEodTransactionalStatementCalculate_Batch
Show what matters for
PAGE GUIDEWhat the page does and how to use it7 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA batch job that adds all unposted, validated store sales transactions to new transactional statements.
What you do hereUse this page to schedule high-frequency calculation of transactional statements during the day so documents are created soon after transactions are uploaded.
Calculate transactional statements in batch page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

Business processManage sales orders › Manage store operations › Post store end-of-day financial statements in Dynamics 365 Commerce
Menu pathRetail and Commerce › Retail and Commerce IT › POS posting › Calculate transactional statements in batch
Set up firstValidate store transactions Microsoft Learn
Used next byPost transactional statements in batch Microsoft Learn
End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

When to run it

When to run itDuring the business day, each time the P-job and Validate store transactions have brought in new store sales.
How oftenHigh frequency throughout the day, at the same pace as the P-job and validation.
Batch settingsA recurring batch job with a short interval, scheduled after the P-job and Validate store transactions.
What the output showsNew transactional statements with all unposted, validated store sales transactions. If a sale is missing, it usually failed validation or wasn't uploaded by the P-job yet.

Source: Microsoft Learn

Steps from Microsoft

  1. Go to Retail and Commerce > Retail and Commerce IT > POS posting > Calculate transactional statements in batch.
  2. On the General tab, select the Organization hierarchy and move the stores whose sales should be put on statements into Selected organization nodes.
  3. Schedule Validate store transactions before it: this job only picks up unposted transactions that passed validation.
  4. Schedule it at a high frequency during the day, right after the P-job uploads transactions, so documents are created soon after the sales.
  5. Open Statements in Store financials and check the new transactional statements; transactions with validation errors are missing until they are fixed.

Source: Microsoft Learn

Test checklist

  1. Validated transactions of the selected stores are on a transactional statement.
  2. Transactions with Validation status Error aren't on it.

Source: Microsoft Learn

Solution architect

4Design impact

Can it be undoneYes, before posting: Nothing is posted yet. Clear statement frees the marked transactions so they go on a new statement. Microsoft Learn
If you change it laterCreates transactional statements and marks the validated store sales transactions with the statement. Microsoft Learn
Technical architect

5Technical

Menu itemRetailEodTransactionalStatementCalculate_Batch Checked in Dynamics 365
FormRetailOperatingUnitPicker Checked in Dynamics 365
Roles to set it up and use itTo use itRetail service RetailServiceRetail operations manager RetailOperationsManagerRetail store manager RetailStoreManagerGive people one of these roles. On this system, 3 roles can run this page.Checked in Dynamics 365
Developer

6Developer

Open it by URLhttps://<your-environment>/?mi=RetailEodTransactionalStatementCalculate_Batch
Everyone

7Sources