Backdated Packing Slips

(3) Share

Report

Posted on by Arnaud Tournier

Dear F&O admin, Good Morning,

I'm confronted to a peculiar problem regarding Packing Slip dates.

We receive orders from customers via :
Online Store > Commerce > a batch autoconfirm the retail order into a sales order
Sales responsible create the SO manually.
In case of multiple SO, they are merged, then the goods are separeted between different LOADs and delivered.

Users post a Packing list DAY1, but the PS appears in the system with an anterior date :
Packing list posted the 04/08/2025, date registered in F&O = 01/08/2025
Packing list posted the 09/01/2025, date registered in F&O = 30/12/2024

This cause several problems with invoicing and BI reports. And as I understood from other posts from the community, backdating Packing Slips is not legit (or legal at worse).
There is no consistency with this issue, we found 4 occurences so far and I wasn't able to replicate it.

Do you know what could cause this behaviour ?

Thank you
Best Regards

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

André Arnaud de Cal... 297,529 Super User 2025 Season 2 on at

Like (1)

Report

Backdated Packing Slips

Hi Arnaud,

In Dynamics 365 Supply Chain Management, it is possible to use a date other than today. This is provided at the time of packing slip posting or other posting actions. The user can change the default provided date. In some processes, an integration takes care of posting packing slips that can indeed use dates throughout the last month and send a summary invoice at the beginning of the new month.

In your scenario, there can be two options. Either the user did change the date on the update form manually to another date, or the user did change the session date of Dynamics 365. The session date is used to default the date when starting posting actions. See also my blog: Session date in Microsoft Dynamics AX - Dynamicspedia

You can ask the users if they are changing the session date. If the session date is the culprit, you can limit access to this feature. I wrote a blog about this as well: Security how-to: Disable change of session date for users - Dynamicspedia

1 people found this reply helpful.

Was this reply helpful? Yes No