Common reasons include:
Correcting Errors
A transaction may have been:
Re-updating the transaction pushes the corrected information through the system.
Reposting to the General Ledger
If:
you may need to update transactions again so the accounting entries repost properly.
Configuration Changes
If settings changed after the original update, such as:
the transactions may need to be reprocessed to apply the new configuration.
Recalculating Depreciation
If useful life, salvage value, acquisition date, or depreciation method changes, prior depreciation transactions may need to be recalculated and updated again.
Synchronizing Data
Sometimes transactions exist in Asset Management but:
Re-updating helps bring systems back into balance.
Audit or Reconciliation Cleanup
During:
staff may identify discrepancies requiring transactions to be regenerated or reposted.
Recovering From Interrupted Processing
If:
some transactions may appear updated but not have completed successfully.
In practical terms:
“Updating transactions again” usually means reprocessing accounting activity so the Asset Management records and General Ledger stay accurate and synchronized.
This is especially common in governmental accounting systems where:
Delete the transactions that will be re-updated
from the General Ledger.
1. Open Connect Asset Management > Organization > Update General Ledger.
2. Set up the GL Period, Date Range, and options to select the transactions to include in the export file.
For help filling in the fields on the form, see the help topic titled How do I post transactions to the General Ledger?
3. Click too select the checkbox titled Create GL Update Export File.