Description

This TI covers the steps to follow to correct the issues and post any batch that have caused the auto creation of an IT ticket titled “Auto GL notification – Unposted Batches”. These batches fail to auto post and generate a notification to the IT Service Desk as per COINS system parameters for a variety of reasons but mostly due to a transaction GL account mapping corruption. It is the GL account mapping corruption fix that is covered within this TI.

All tickets look like the below with the company number and batch number specific each time.

A screenshot of a computerDescription automatically generated

 

Process

Switch to the KCO quoted on the IT ticket.

Navigate to General Ledger > Journals > Journal Batch.

Filter on ‘Batch Number’ and enter the batch number from the IT ticket.

Click on the batch number hyperlink.

A screenshot of a computerDescription automatically generated

Click on the ‘Transactions’ tab

Find the first line that is not ticked as ‘Posted’, you may need to use the page controls to change page until you find an unposted transaction.

Click on the ‘Details’ button for the first unposed line.

A screenshot of a computerDescription automatically generated

Review the ‘Account’ field, if it appears as below then the GL account mapping for the transaction is corrupted and needs to be reset.

Click the ‘Undo’ button.

A screenshot of a computerDescription automatically generated

Click the ‘Open’ button for the same transaction line.

A screenshot of a computerDescription automatically generated

Immediately click the ‘Save’ button, this will be enough reset the account mapping.

A screenshot of a computerDescription automatically generated

Click on the ‘Details’ button for the line once again.

A screenshot of a computerDescription automatically generated

This should now appear uncorrupted as below.

A screenshot of a computerDescription automatically generated

Apply the ‘Post’ action at the bottom of the page.

A screenshot of a computerDescription automatically generated

The report processes should all Complete and refresh the page to see the batch status change to “Posted”.

If the batch status is “Complete (with errors)” and the batch remains as “Posting” after refreshing your page, then repeat the steps from point 5.

A screenshot of a computerDescription automatically generated

 

Notes

Please note, these GL batches should have auto posted to the General Ledger in COINS, once they get stuck and require manual intervention as above, they fundamentally become manual postings as so they may require certain GL Element codes to be enabled for manual posting. Enabling GLs for manual posting is covered in the following TI - https://servicedesk.vistry.co.uk/a/solutions/articles/50000147639