Account Construction Process

Before a transaction updates to the general ledger, Greentree Desktop must determine which general ledger accounts are of the transaction. To do this, it works through the hierarchies that are outlined in this section, using the transaction type. In some cases, full accounts has been assigned to general ledger account fields, and in some cases, wildcards may have been used.

To construct a general ledger account when a transaction is being updated to the general ledger, Greentree Desktop starts the search by going to the first GL field defined the hierarchy. If it finds a valid account, it uses that account. If it does not find a valid account, it will continue to work through the hierarchy until it can find, or construct (if wildcards are used) a valid account.

If you use wildcards (*), Greentree Desktop fills in GL segments with the first value found for a segment. If Greentree Desktop searches through the entire hierarchy and no valid account is found or can be constructed, the value updates to the GL suspense account. If an account is constructed, but it is not valid values combined do not form a valid general ledger account using set-up in GL Account Maintenance), then the value also updates to the GL suspense account.