Common errors when posting stock transactions and general ledger (GL) batches include batches stuck in Posting status, posting failures due to account restrictions and stock goods receipt notes (GRNs) not generating GL entries. This article explains each issue and the steps to resolve it.
GL batch stuck in Posting status
A GL batch moves through three statuses during posting: Unposted, Posting and Posted. If a batch remains in Posting status for an extended period, the posting process may have failed mid-run.
Go to General Ledger, select Journals, then select Journal Batch.
Locate the batch in the listing and check its current status.
If the batch has been in Posting status for more than a few minutes, refresh the screen to confirm the status has not changed.
If the status remains in Posting, raise a support ticket — do not attempt to repost the batch without guidance, as this may cause duplicate GL entries.
⚠️Important: Do not delete or attempt to manually repost a batch stuck in Posting status without first contacting support. Doing so may result in duplicate GL entries.
GL batch posting fails due to account restrictions
A posting failure can occur when a GL batch contains lines for accounts that do not allow manual postings. This is common when a batch is sourced from another module, such as during a period end process.
Identify restricted accounts
Open the failed GL batch and review the batch lines.
Identify any lines referencing accounts that may be set to disallow manual postings.
Contact your system administrator to confirm the account configuration and whether manual posting should be permitted for those accounts.
Allow specific users to override posting errors
The GL/MANACCUSR parameter lets you specify users who can suppress manual posting errors on batches sourced from other modules.
Go to Parameter Maintenance.
Search for GL/MANACCUSR.
Add the relevant usernames to the parameter value.
Save your changes.
⚠️Important: Only grant posting override rights to users authorised to do so by your finance team. Incorrect use may allow postings to restricted accounts.
Stock GRN not generating a GL batch
When a stock GRN is processed, it should automatically generate a corresponding GL batch for the relevant project site store entries. If no GL batch appears, the following steps help identify the cause.
Confirm the stock GRN has been fully committed and is not in a draft or uncommitted state.
Check the GL Journal Batch listing to confirm whether a batch has been created but not yet posted.
Verify that the cost type and account codes on the GRN lines are correctly configured — missing or incorrect account codes can prevent GL batch generation.
If no GL batch has been created after confirming the above, raise a support ticket with the GRN reference and the relevant project and site store details.
📌Note: GL batch generation for stock GRNs depends on correct account code configuration. If account codes have recently changed, this may affect new GRN postings.
Raise a support ticket
Raise a support ticket if:
A GL batch remains in Posting status after several minutes.
A posting failure cannot be resolved by reviewing account restrictions.
A stock GRN has not generated a GL batch after checking configuration.
Include the batch number or GRN reference, the module name, the exact error message and a screenshot where possible.