Abnormal Posting Date

Alex_Chow
Member Posts: 5,063
This was a post I made on my BLOG. I asked Luc to put the report object in the download sections so people with regular license and import the object into their database.
Abnormal posting date entries happens when the Posting Date of the receipt/shipments of inventory is after the Posting Date of the invoice. Why does this happen? You'll need to ask your CFO or Controller. Typically, I found this more in return orders where the receipt of the product is a certain date, and the accounting department decides to post the credit memo in prior dates.
Either by mistake or intentional, if this happens, your Inventory Valuation will not tie to your G/L.
Here's a step by step on how to replicate this problem, and how to solve this problem:
1. Create a sales order with posting date of 11/01/08
2. Post the Shipment with a posting date of 11/01/08
3. Change the posting date to 09/01/08
4. Post the invoice
5. Run your inventory valuation report as of 9/30/08
6. Notice that the item is not taken out? But if you look at your G/L, the inventory value is taken out.
This will work for purchase side as well. It doesn't matter how to do it either using warehouse shipment/receive, the underlying process will net you the same problem.
Usually, problems like this won't come up until the user is trying to do month end and gets really frustrated on why their inventory doesn't tie to G/L. Unfortunately, there's no easy way to reverse this transaction after it's posted, the only way is to run a report at the end of the period to see what transactions have this "Abnormal Posting Dates".
Here's a report that will give you all the transactions that have abnormal posting dates. If you take this amount, add/subtract it to your inventory valuation report, it will be equal to the G/L inventory.
Abnormal posting date entries happens when the Posting Date of the receipt/shipments of inventory is after the Posting Date of the invoice. Why does this happen? You'll need to ask your CFO or Controller. Typically, I found this more in return orders where the receipt of the product is a certain date, and the accounting department decides to post the credit memo in prior dates.
Either by mistake or intentional, if this happens, your Inventory Valuation will not tie to your G/L.
Here's a step by step on how to replicate this problem, and how to solve this problem:
1. Create a sales order with posting date of 11/01/08
2. Post the Shipment with a posting date of 11/01/08
3. Change the posting date to 09/01/08
4. Post the invoice
5. Run your inventory valuation report as of 9/30/08
6. Notice that the item is not taken out? But if you look at your G/L, the inventory value is taken out.
This will work for purchase side as well. It doesn't matter how to do it either using warehouse shipment/receive, the underlying process will net you the same problem.
Usually, problems like this won't come up until the user is trying to do month end and gets really frustrated on why their inventory doesn't tie to G/L. Unfortunately, there's no easy way to reverse this transaction after it's posted, the only way is to run a report at the end of the period to see what transactions have this "Abnormal Posting Dates".
Here's a report that will give you all the transactions that have abnormal posting dates. If you take this amount, add/subtract it to your inventory valuation report, it will be equal to the G/L inventory.
Confessions of a Dynamics NAV Consultant = my blog
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
0
Comments
-
-
Yes, the report is useful, but how to prevent this?
Changing CU90?
any suggestion?
thank you0 -
Yes, the report is useful, but how to prevent this?
Changing CU90?
any suggestion?
thank you0 -
There's nothing to prevent. The dates reflect on the G/L and ILE are required and necessary.
Take a look at my blog to see why there's nothing to prevent. The key is to understand what the user needs and what the system is doing to address this.Confessions of a Dynamics NAV Consultant = my blog
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book0 -
Thank you Alex.
The customer actually asked for some kind of a message or error to appear whenever there is a case like this, but we will to convince them and try not to change any code, but use this report.
thanks again,0 -
I just noticed this and downloaded the report but I cant figure out how to open it. can anyone help? If it can work I will find it very useful!0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions