A journal didn't post, what can I do?
If you’ve noticed that your automated monthly depreciation journals other journals (sale, disposal, etc.) hasn’t posted, these journals can might be stuck in error or queued status.
To resolve this for journals in error status, follow these steps:
- Run the Journal Report for the date range in question. If it's the automated depreciation journals, then include that month, if it's an individual journal, include the month month the journal was processed.
- This will show the status of the journals and if there are any that journals that are in error status.
-
When there are errored journals, a red 'Retry posting errored journals' button will display.
Select this button for Asset.Guru to attempt again to post the journals.
- Refresh the Journal Report to see whether the journal has been successful.
If there are still errors or assets are in queued status, reach out to our support team to log a ticket and we can help figure it out.
The common reasons and solutions for journals not posting are the following:
Asset.Guru was connected to your accounting package with a user that no longer has permissions to create manual journals in your selected accounting software. Likely as a result of the user having left your organisation or the user's permissions have changed.
- Refresh Connection with a user that can create manual journals.
Your accounting package has been disconnected from Asset.Guru.
- Reconnect your accounting software.
The Asset Type of the errored journal is mapped to an account that has been edited (renamed/numbered) in your accounting software or no longer exists.
- Review the Asset Types to confirm they are mapped to the correct accounts.
API limits in your connected accounting package were reached during the minute that Asset.Guru was attempting to post the Journals.
- Press the "Retry posting failed journals".
The journal is attempting to post to a locked accounting period.
- Unlock the accounting period and press the "Retry posting failed journals"