@helpdesk37 yes, best practice is to post all transactions otherwise it won’t make a GL impact

@helpdesk37 is there a reason why some transactions are left unreleased/unposted?

Hi @helpdesk37 unposted or unreleased transactions shouldn't be causing variances although as Iqra mentioned it’s good idea to post these transactions. Sometimes variances might be caused by setting changes, run the Recalculate Customer Balances and Recalculate Account History:

Hello @helpdesk37 ,

Unreleased transactions do not cause any difference between the GL and the subsidiary modules.  A document or batch with Unreleased status has not updated AR or GL and is not causing any difference between the AR Period Sensitive Aging and GL Trial Balance reports.

Unposted batches are released in the subsidiary module and therefore HAVE updated AR Period Sensitive Aging and HAVE updated the customer balances, yet have not updated the GL. Unposted batches do cause differences between AR Period Sensitive Aging and GL Trial Balance reports.

Hi @helpdesk37,

Unposted or unreleased transactions can cause a variance in the AR and GL control accounts, as these accounts represent the amounts that have been invoiced and recognized in the financial statements. If there are unposted or unreleased transactions, the amounts in the AR and GL control accounts may not match the actual amounts of invoices issued and revenue recognized, leading to a variance. It is important to regularly reconcile the AR and GL control accounts to identify and correct any variances.

If you “pretend” to close out the period in the manage financial periods screen you can run a report called unreleased documents that will show you a list of all documents and GL batches that have yet to be posted. 

I find this helpful as it breaks them out by modules but gives you a full list.