BeyondERP.Newsletter
Menu

Job page · Retail and Commerce

Post transactional statements in batch

A batch job that posts calculated transactional statements and creates the resulting sales orders, invoices and journals.

Business process
Post store end-of-day financial statements in Dynamics 365 Commerce
Menu item
RetailEodTransactionalStatementPost_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 posts calculated transactional statements and creates the resulting sales orders, invoices and journals.
What you do hereUse this page to schedule frequent posting of transactional statements so that inventory, revenue and payments are recognized in near-real time.
Post 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 › Post transactional statements in batch
Set up firstCalculate transactional statements in batch Microsoft Learn
Related pagesStatements 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, after each run of Calculate transactional statements in batch.
How oftenHigh frequency throughout the day, at the same pace as the transactional statement calculation.
Batch settingsA recurring batch job with a short interval that follows the calculation job, so inventory, revenue and payments are recognized close to real time.
What the output showsPosted transactional statements with sales orders, sales invoices, payment journals, discount journals and income-expense transactions. Statements that still show on the Statements page have errors and weren't posted.

Source: Microsoft Learn

Steps from Microsoft

  1. Go to Retail and Commerce > Retail and Commerce IT > POS posting > Post transactional statements in batch.
  2. On the General tab, take the Organization hierarchy and select the stores whose calculated transactional statements should be posted.
  3. Schedule it at a high frequency, right after Calculate transactional statements in batch.
  4. Open the Statements page to find statements that weren't posted because of errors; the job skips them and keeps posting the others. Fix them so the next run posts them.
  5. Check the sales orders and invoices created for the posted statements, and that store inventory is updated.

Source: Microsoft Learn

Test checklist

  1. Calculated transactional statements are posted.
  2. Sales invoices exist for the store sales on the statements.
  3. Statements with errors are listed on the Statements page.

Source: Microsoft Learn

Solution architect

4Design impact

Can it be undoneNo: Posted sales orders, invoices and journals stay posted. Correct mistakes with returns or new transactions. Microsoft Learn
If you change it laterCreates and posts sales orders, invoices, payment and discount journals and income-expense transactions for the calculated statements. Microsoft Learn
Technical architect

5Technical

Menu itemRetailEodTransactionalStatementPost_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=RetailEodTransactionalStatementPost_Batch
Everyone

7Sources