BeyondERP.Newsletter
Menu

Page · Retail and Commerce

Statements

A processing page where you manually create, calculate and post store statements, which turn POS transactions pulled into headquarters into sales orders, invoices, payment journals and inventory updates; it also shows statements that failed during batch posting.

Used by
Retail operations manager, Retail service, Retail store manager
Business process
Post store end-of-day financial statements in Dynamics 365 Commerce
Menu item
RetailEodTrickleFeedStatementListPage
Main table
RetailStatementTable
Data entity
RetailTransactionEntity
Show what matters for
PAGE GUIDEWhat the page does and how to use it8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA processing page where you manually create, calculate and post store statements, which turn POS transactions pulled into headquarters into sales orders, invoices, payment journals and inventory updates; it also shows statements that failed during batch posting.
What you do hereUse this page to create a statement for a store, calculate it (marking transactions and building lines per payment method), review the difference between tendered and counted amounts, and post it. Use the Execution details buttons to check status, event logs, aggregated transactions and vouchers when a statement fails.
ExampleFor example, after a store closes its shifts for the day, a finance clerk creates and calculates the statement here and posts it so that the day's sales become invoiced sales orders.
Statements 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

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.

Steps from Microsoft

  1. Go to Retail and Commerce > Channels > Stores > Statements.
  2. Select New and identify the store the statement is for.
  3. Calculate the statement to mark the transactions and build the statement lines.
  4. Check the counted amount against the transaction amount (tender declarations are used, or enter the counted amount manually).
  5. Post the statement.
  6. If posting fails, use Status details, Event logs and Aggregated transactions under Execution details to find and fix the error, then post again.

Source: Microsoft Learn

Fields on the page

FieldWhat it means
Statement methodHow statement lines are grouped: Total, Staff, POS terminal or Shift.Microsoft Learn
Counted amountThe amount actually counted, taken from register tender declarations or entered by hand.Microsoft Learn
Status detailsShows the current state of the statement and any error code and message.Microsoft Learn
Event logsAn audit trail of the Create, Calculate, Clear and Post operations run on the statement.Microsoft Learn
Aggregated transactionsThe cash-and-carry transactions grouped by customer and product that become sales orders.Microsoft Learn
Journal vouchersThe voucher transactions created for discounts, income/expense and gift cards (posted statements only).Microsoft Learn
Payment journalsThe payment journals created for the statement (posted statements only).Microsoft Learn

Test checklist

  1. Pull POS transactions into headquarters with the P-job.
  2. Create a statement for the store and select Calculate statement.
  3. Check lines are created per payment method and the counted amounts come from tender declarations.
  4. Post the statement and check it moves to Posted statements.
  5. Enter a counted amount that exceeds the store's maximum posting difference and check posting is blocked.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Feature management and licence

Licence or add-inStatements configuration key (Retail and Commerce node in License configuration); Statements (legacy) must be off

Microsoft Learn

Solution architect

5Design impact

Can it be undoneHard to reverse: Only one of the Statements and Statements (legacy) configuration keys can be on, and a statement must be created, calculated and posted under the same key. Posting creates sales orders, invoices and payment journals and updates store inventory. Microsoft Learn
If you change it laterPosting is blocked when the gap between counted and transaction amounts exceeds the store's maximum posting difference; posting creates sales orders, invoices and payment journals and updates store inventory, so a wrongly calculated statement affects the ledger and stock. Microsoft Learn
Technical architect

6Technical

Menu itemRetailEodTrickleFeedStatementListPage Checked in Dynamics 365
FormRetailEodTrickleFeedStatementTable Checked in Dynamics 365
TableRetailStatementTableShown as “STATEMENTS” in Record infoKey field: statementIdChecked in Dynamics 365
Data entitiesRetailTransactionEntityTransactions Microsoft data model
Who can open itPrivilegesMaintain retail statements RetailEodStatementsMaintainDutiesMaintain retail statements RetailStatementsMaintainRetail Store Manager Statements Posting RetailStoreManagerStatementsPosting
3 security rolesRetail operations manager RetailOperationsManagerRetail service RetailServiceRetail store manager RetailStoreManager
Checked in Dynamics 365
Roles to set it up and use itTo set it up or change itRetail service RetailServiceRetail operations manager RetailOperationsManagerRetail store manager RetailStoreManagerGive people one of these roles. On this system, 3 roles can open this page.Checked in Dynamics 365
Actions on the pageStatement(Action Pane without tabs): New, Post statementChecked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=RetailEodTrickleFeedStatementListPage
Integrate withRetailTransactionEntity data entity Microsoft data model
Table definitionRetailStatementTable columns and relations Microsoft data model
Everyone

8Sources