Share
Report
6We have a posted Transfer Order in Dynamics 365 Business Central where the Posting Date was entered incorrectly.
The transfer should have been posted on 03-Feb-2026, but it was accidentally posted on 11-Dec-2026.
The transfer itself is otherwise correct:
- Items and quantities are correct.
- Transfer-from and Transfer-to locations are correct.
- The Transfer Shipment and Transfer Receipt are fully posted.
- The inventory movement is correct.
- There is no requirement to change the quantities or locations.
- The issue is only the Posting Date.
The transaction has already generated the related Transfer Shipment/Receipt records, Item Ledger Entries, Value Entries and G/L Entries.
We have also traced the related Item Ledger Entries and confirmed that Business Central created the expected shipment → in-transit → receipt entries, all carrying the incorrect posting date.
What would be the Microsoft-supported and safest method to correct this situation?
In particular:
- Is there any standard Business Central functionality to correct the Posting Date of an already posted Transfer Shipment/Receipt?
- Would the recommended approach be to create corrective/reversing transfer transactions and then repost the transfer using the correct historical date?
- If a transactional correction is used, how should we ensure that inventory valuation, costing, Item Ledger Entries, Value Entries and G/L Entries remain correct?
- If there is no standard correction mechanism, is a controlled AL extension/data correction ever considered appropriate for changing the Posting Date across the related posted records?
- If direct data correction is not recommended, what is the best-practice approach for correcting the historical inventory and G/L position while maintaining a proper audit trail?
We would prefer to use a supported Business Central correction method rather than directly modifying posted ledger tables, so any guidance or experience with a similar scenario would be appreciated.
All responses (
Answers (
