Place a General ledger transaction on hold
Important
This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
To help make data entry flexible, you can enter a transaction on one date, and then put it on hold to prevent users from posting it until a specified date. This is useful if you have an agreement with someone, such as a customer or your manager, about when a transaction can be posted.
To prevent a transaction from being posted until a specified date, enter a release date until which the transaction is on hold. You can edit and save transactions that are on hold, but you cannot post them unless you first remove the hold.
To place a General ledger transaction on hold
Click General ledger > Journals > General journal. Select a journal and then click Lines.
–or–
Click Fixed assets > Journals > Fixed assets. Select a journal and then click Lines.
–or–
Click Fixed assets > Journals > Fixed asset budget. Select a journal and then click Lines.
–or–
Click Fixed assets > Setup > Depreciation > Depreciation books. Select a journal and then click Lines.
–or–
Click Fixed assets > Journals > Inventory to fixed assets. Select a journal and then click Lines.
–or–
Click General ledger > Journals > Elimination. Select a journal and then click Lines. Select a journal voucher and then click Proposals > Elimination proposal.
–or–
Click General ledger > Periodic > Process allocation request.
–or–
Click General ledger > Periodic > Consolidate > Consolidate [Online].
In the Release date field, enter the date when the transaction is no longer on hold and becomes available for posting.
To remove a hold on a transaction, you can clear the entry in this field.
Press CTRL+S to save the transaction.
About the release date in different time zones
If your organization includes users who work across multiple time zones, the date and time when a transaction is released from a hold is based on the time zone of the user who most recently modified the Release date value. Because the transactions are released at midnight on the specified date in that user's time zone, the actual date and time of the release will be adjusted accordingly for users in other time zones.
Example
On December 31 in New York, a user puts a transaction on hold at noon Eastern Time, and enters a release date of January 1 (the next day). The transaction is set up to be on hold until midnight Eastern Time. Therefore, the user must wait 12 hours for the transaction to be released.
Users in London, which is five hours ahead of New York, must also wait 12 hours. However, because the transaction was put on hold at 17:00 Greenwich Mean Time on December 31, the transaction will not be released until 05:00 Greenwich Mean Time on January 1.
For users in Seattle, which is three hours behind New York, the transaction was put on hold at 09:00 Pacific Time on December 31. When the transaction is released 12 hours later (at 21:00 Pacific Time), it will still be December 31 for these users.