Hello,

The hotfix KB 3034468 released for this feature ‘Advance invoices for prepayments in retail ‘. The link to LCS:

https://fix.lcs.dynamics.com/issue/results/?q=3034468

This feature is based on the regular Polish functionality of advance invoices in AX and extends the functionality to process advance invoices when a Customer order Deposit is registered in POS or a final Payment for a Customer order is processed. The following is a high-level overview of the process:

There are only two setup steps required to enable and use this functionality in POS (in addition to the regular setup of advance invoices in AX):

1. Set Retail parameters \ Customer orders \ Create advance invoice for deposit to enable the functionality;
2. Configure a windows printer in the Hardware profile of POS to be able to print advance invoices from POS.

The feature does not change user scenarios in POS.

Best regards,

Ramune Peckyte

Microsoft EMEA Customer Services and Support

The post PL – Retail – Advance invoices for prepayments in retail appeared first on Microsoft Dynamics 365 Blog.

Hello,

If you have any issues regarding sales tax (net amount) rounding between Retail store transactions and posted sales invoice voucher transactions, you should check at first Sales tax setup.

The recommended setup for sales tax which should be used when ‘Price include sales tax’ is enabled on a Store.

1. ‘Marginal base’ to set up as ‘Net amount per line’ for Sales tax code:

Tab Calculation:

• Origin= Percentage of net amount
• Marginal base= Net amount per line
• Calculation method= Whole amount

2. ‘Rounding by’ recommended to have ‘Sales tax codes’ for Sales tax group:

It is very important to know that once you did some changes on sales tax setup in HQ, you should run Job 1080 (Tax) and then be sure that Retail server is restarted, because changed tax setup might be cached (for immediate affect, otherwise Retail Server pool is refreshed in 30 min).

With that setup you should always get the same calculation of all amounts (Net amount and Sales tax amount) in POS/Retail and in HQ transactions.

Also a suggestion to change sales tax setup only after working hours when nobody is working to be sure that the changes are done correctly, distributed to POS and there are no differences between HQ and POS or their transactions.

The same is valid for AX2012 and D365.

Best regards,

Ramune Peckyte

Microsoft EMEA Customer Services and Support

The post Setup for sales tax which should be used when ‘Price include sales tax’ is enabled on a Store appeared first on Microsoft Dynamics 365 Blog.

Sales Tax on Gift card sales in Retail

With the hotfix KB 3183056 installed there is possible to get a sales tax calculated on gift card transactions.

Setup and repro steps how this feature is supposed to be working can be in the attached file.

Sales-Tax-on-Gift-card-sales

The post Sales Tax on Gift card sales in Retail appeared first on Microsoft Dynamics 365 Blog.

Credit memo functionality on Dynamics 365 MPOS

Steps (please find the document with screenshots attached credit-memo-functionality-on-dynamics-365-mpos).

1.Set up Payment method with the Operation name ‘Pay credit memo’ and associate appropriate Posting accounts in it

Retail and commerce/Channels/Retail stores/All retail stores/select the store HOUSTON/Tab Set up/Payment methods/in our case it is called Voucher:

2.Issue Credit Memo

Go to MPOS/Show journal/select sale transaction/ Select Return transaction/Return/select Products/Return/select Reason for return/OK.

Go to Actions/Transaction options/Issue credit memo:

Credit memo will be issued and transaction will be posted.

3.Now we can check if credit memo has been issued

Retail and commerce/Channels/Retail stores/Credit memos:

Credit memo is issued with the number 1.

4.Apply Credit memo

Enter Sales Transaction in MPOS and then pay it using the Payment method ‘Voucher’ (which has an Operation name ‘Pay credit memo’):

Enter Credit memo number 1 (the number we see in step 3):

Click Check amount, we see Available amount:

Click the button on bottom ‘Tender Payment’:

5.Now we can check if Credit memo has been applied

Retail and commerce/Channels/Retail stores/Credit memos:

You will notice that Applied check box is now marked, Applied amount and Applied date are filled in.

The post Credit memo functionality on Dynamics 365 MPOS appeared first on Microsoft Dynamics 365 Blog.

In AX2012 R3 CU10 two different Total prices (Gross amounts) are calculated in EPOS for the same product with different product dimensions.

E.g. Item price with no tax is 33,61+19% Sales tax = price tax included is 39,9959 if we calculate manually, which is 40,00.

When the product is selected in EPOS the first time- Gross amount calculated 40,00 (tax percentage is 19,01).

The second time, the same product, but with different product dimensions, selected, and now Gross amount calculated 39,99 (tax percentage is 18,98).

On the receipt these two different gross amounts are printed for the same product.

The expected result– it should be the same Gross amount calculated for the same product each time.

To get the expected result Sales tax code setup should be the following:

We recommend the Sales tax code to set up with ‘Marginal base’= “Net amount per line”.

With the above setup, you will get an expected result in EPOS- both lines with the same product has the same Gross amount 40,00 and Balance amount for payment 80,00.

The post Sales tax rounding in EPOS appeared first on Microsoft Dynamics 365 Blog.

How AX is intended to work using destination based tax for retail

How to set up Destination based tax for sales orders created in EPOS or MPOS?

Repro steps and setup (please refer to the document attached):

1. A Store should have a parameter ‘Use destination-based tax’ enabled.

2. Default Sales tax group is TX on a store.

3. Delivery address should be added and tax setup on a customer account:

On a customer account 2001, Tab Addresses you should add Delivery address (Cust-Ship) and then add Sales tax on Tab General (Sales tax TN):

4. Sales tax setup:

TX has 6,25 % tax

TN has 7% tax

5. In POS sell an item and select Shipping address:

In POS select an item 0113 with 99,99 price tax included, then enter customer 2001. Sales tax is taken by default from the store as TX and tax amount calculated 5,88.

Then click a button ‘Add shipping address’ and select created delivery address Cust-Ship.

Now Sales tax is taken TN from Shipping address and calculated 7% with amount 6,54.

———————————————-

In EPOS and MPOS Destination based tax works as described above, only if we have Sales tax group set on Customer Delivery address (it is explained on white paper).

Destination based tax set up on a Sales tax group is used only for ONLINE STORES.

Such information can be found on technet https://technet.microsoft.com/en-us/library/aa498345.aspx

When the user enters sales in web (online) store, selects a Shipping address, then the system is checking Destination based tax from Sales tax group.

The post Destination based tax in Retail EPOS/MPOS or Online stores appeared first on Microsoft Dynamics 365 Blog.

There might be a situation when you are not able to settle customer transaction with payment due to error message “The transactions on voucher XXX do not balance as per [date]. (accounting currency: 50,00 – reporting currency: 50,00)” (when the amount in error message is full invoice amount).

Cases when this issue can occur:

1. You have enabled the “Mark lines on free text invoices and interest notes” in AR/Setup/Tab Settlement/AR parameters.

2. Post Free text invoice for a customer.

3. Delete posted FTI in step 2 (it was possible to delete posted FTI before R2 CU7, but the hotfix KB 2878451 solves this issue in 6.2.1000.2487).

4. Create payment journal and try to settle it with invoice transaction posted in step 2. (or you can have payment posted and settle open transactions later).

Actual result: the error appears “The transactions on voucher XXX do not balance as per [date]. (accounting currency: 50,00 – reporting currency: 50,00)” (when the amount in error message is full invoice amount).

Solution: disable the parameter “Mark lines on free text invoices and interest notes” and then settle open transactions again. Settlement should be posted successfully. Go back and enable the “Mark lines on free text invoices and interest notes” parameter again.

If you have the hotfix KB 2878451 installed, you should not be faced with this issue.

The post The error message “The transactions on voucher XXX do not balance as per [date]. (accounting currency: 50,00 – reporting currency: 50,00)” in open customer transactions settlement appeared first on Microsoft Dynamics 365 Blog.

There could be a situation in AX2012 when you have created Purchase order and saved it (Project ID is unknown in this stage). After that if you want to enter Project ID to a header level or line level- it is not possible, Project ID field is greyed out.

The conclusion of this behavior is that this is how project Purchase order is currently designed:

– The Project ID on the PO header shouldn’t be editable when a PO header is created without a project.

– The Project ID on the PO header will only be editable when a PO header is created with a project.  The project ID on the PO header also cannot be cleared when a PO header is created with a project.

This design is done due to some consequences changing project ID in Purchase order.

The post Project ID in a Purchase order header level or line level- it is not possible, Project ID field is greyed out appeared first on Microsoft Dynamics 365 Blog.

The issue is in AX2012 R2+CU6- the error message received ‘The value in field offset account is not valid’ when in General journal we use a function ‘Select bridged transactions’.

To avoid an error, you can:

1.      Check Journal Name setup in General ledger. If you have set fixed offset account, just remove it (the error appears if we have different fixed Offset account in Journal Name and in Method of payment of bridged transaction).

 2.      Or in GL Journal Name setup form, you can set fixed Offset account the same as in Method of payment (which was used posting bridged transaction- vendor payment).

The post Error ‘The value in field offset account is not valid’ creating bridged transactions- AX2012 R2 CU6 appeared first on Microsoft Dynamics 365 Blog.