Network

Innovate

Learn

Experiment

Guðmundur Helgi AxelssonProgram Manager

End of Day and Statement Posting

Disclaimer

© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other

product names are or may be registered trademarks and/or trademarks in the U.S. and/or other

countries. Other names and brands may be claimed as the property of others.

The information herein is for informational purposes only and represents the current view of

Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to

changing market conditions, it should not be interpreted to be a commitment on the part of

Microsoft. Microsoft cannot guarantee the accuracy of any information provided after the date of

this presentation. All product release dates and features specified are preliminary based on

current expectations, and are subject to change without notice. Microsoft may make changes to

specifications and product descriptions at any time, without notice.

Sample code included in this presentation is made available AS IS. THE ENTIRE RISK OF THE USE

OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER.

MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE

INFORMATION IN THIS PRESENTATION. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR

OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS PRESENTATION.

Microsoft products are not intended for use in medical, life saving, or life sustaining applications.

Session focus

Centralized Omni-Channel Management

E-Commerce POS

IT Pro Experience

UX Improvements

Flexible, Scalable & Extensible Infrastructure

Search driven Shopping

Experience

OOB “Starter” Storefront

Hardware

Time Clock Customer OrdersPayment

Processing

Commerce Data Exchange (CDX)

Commerce Run Time (CRT)

Storefront Extensibility POS Extensibility

Merchandising

Payment ProcessingBI/ReportingOrder Management &

Fulfillment

Customer ManagementChannel Management

& Publishing

Catalog Management, Enrichment &

Publishing

Scale/Performance Upgrade & SupportMonitoring & Diagnostics

Rapid StartSetup/Deployment

Administration Experience

Payments Extensibility

Customer Management

CRT Services Omni-Channel

Workflows

Pricing, Shipping & Taxes

Search, Scan

Inventory & Replenishment

EOD & Financials

Pain points and challenges

Staff accountability and flexibility

Reliable and current information

Efficiancy and scalability

Key investments

Shift management

Statements and batch posting

Inventory reservations

Financial dimensions

End of day processing

End of day processingDrawer operationsDeclare starting amountFloat entryTender removalIncome/Expense accountsSafe drop/Bank dropTender declaration

End of day

ShiftsGroup transactions that belong together such as sales and tender declarationsSummarize transaction totals

Shift operationsSuspend shiftResume shiftClose shiftBlind closePrint X/Z reports

End of dayStore setupPayment methodsCash declarationIncome/Expense accountsCurrencies

Demo

End of day processes

Statement posting

Statement posting

Statements• Retail documents that contain a collection of

inventory and financial transactions from the POS for a given store over a specified period of time

• Transactions can be posted in detail or aggregated• Posting of a statement will create and invoice Sales

orders, create payment journals and settle against the Sales invoice

• Provides consistent tracking and referencing of sales across channels

Statement postingPosting processes

POS Retail Sales

AX for Retail Transactions

• Sales header• Sales lines • Payment lines• Banked Tender Trans• Tender Declaration Trans

Customer transactions

Finance Inventory transactions

• Variant Trans• Order Invoice Trans• Loyalty Point Trans• Invent Trans• Infocode Trans

Statement post

Sales transactions are pulled from the

POSs

Inventory update can be run at any time

Statements are posted

Statement calculate

Inventory update

Statement is created and calculated per store

Statement postingPOS transactionsRetail transactions are pulled into AX using the CDX SchedulerUploaded transactional data is stored within the AX database in Retail transaction tablesUsers can view details of the uploaded data using the Transactions inquiry

Statement postingRetail parametersConfigure and set company wide defaults for posting• Discount specific posting• Gift card• Email receipt• Settlement• Aggregation

Statement posting

Store setupStore specific posting options and defaults• Statement method• Closing method• Rounding• Counting differences• Batch configuration

Statement posting

Warehouse settingsNegative inventoryStorage dimensions• Location• Pallet ID

Statement postingPosting processesStatements can be done manually or periodically by batch jobs• Inventory update (batch only)• Calculate• Post

Statement posting

Posted statementsPosted statements can be viewed including all related documents• Retail transactions• Shifts• Invoices• Payment journals• Vouchers

Demo

Statement posting

Financial dimensions

Financial dimensions

Retail dimensionsRetail channelTerminal

Financial dimensionsDimension valuesDimensions values are captured on Retail transactions from• Customer• Store• Terminal• Worker

Stamped on• Statements• Sales orders• Payment journals

Demo

Financial dimensions

Key takeawaysEnd of day processesFlexible shift management and staff accountability

Financial postingEasily and effectively consolidate all POS transactions for tracking and posting in AX Inventory postingUp to date inventory providing accurate view of store sales and replenishment needs

Financial dimensionsRetail specific dimensions and dimension values captured with Retail transactions

Q & A

© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.