Sage 300 – Common Services – Option to Allow Non-Existent G/L Account.

It is might possible that while making transaction entry user may come to know that the ledger or G/L account to be hit as effect of transaction is not exist in Sage 300 G/L Account’s master.  In many organizations certain process will be followed to create a G/L account which involves proper authorization levels and approvals from the accounts heads. In such case if the system does not allow the non-existent G/L account to be referred in the transaction then it will cause the delays in further processing, reporting or invoicing and can create unnecessary delays in bank transactions documentations , document filings etc.

Sage 300 provides the option to set the action to be taken if any non-existing G/L account is referred on finance transactions as well bank services entries.

New Stuff: Pros and Cons of Single vs Multiple Databases in Sage 300

In order to access the screen, navigates to “Common Services” -> Company Profile -> Options Tab.Kindly refer the below screenshot for the same:

As per the above screenshot user can set one of the three below mentioned values provided for this option.  Please find the detailed description for each of them.

1. None: If user specifies this option then Sage 300 will not display any message when user enters any Non-Existent G/L Account in transaction entry and allow user to save the record.
2. Warning: If user specifies this option then Sage 300 will display the warning message when user enters any Non-Existent G/L Account in transaction entry and allow user to save the record.
3. Error: If user specifies this option then Sage 300 will display the Error message when user enters any Non-Existent G/L Account in transaction entry and system will not allow user to save the record.

Below screenshot will illustrate the different behavior on selecting each of this value for “Non-Existent G/L Account”.

1. With None: If we input “TEMPACCTID” as Revenue Account and user tabbed over the field then it will not display any error and also allows saving the entry.

2. With Warning: If we input “TEMPACCTID” as Revenue Account and if user tabbed over the field then it will display Warning alert and allows saving the entry.

3. With Error: If we input “NONEXISTENT” as Revenue Account and if user tabbed over the field then it will display error message and does not allows saving the entry as well invalid revenue account value in that field.

Note: The value for this option can be changed any time. If value is change from “None” or “Warning” to “Error” then it will affect only new records which user will create after change in the value for this option. It will not display any error for the entries which are already exist.

Also read:

1. Restrict Posting to Inactive G/L Account through Sub-Ledger
2. Accounts Receivable Batch Status Report
3. Dates and Entered By field’s on G/L Journal Entry in Sage 300 ERP 2016
4. G/L Integration in A/P module with options for creating G/L transaction by (Creating and Posting a New Batch)
5. Account Receivable – Creating Summary Invoice in Sage 300