IN Transaction Hierarchy

This is the hierarchy that Greentree Desktop follows when posting the debit and credit transactions for an inventory transaction:

Debit

• StockItem.stockAccount
• StockItem.myINAnalysisCode.stockAccount
• Location.stockAccount
• Warehouse.stockAccount
• GLControl.stockAccount
• GLControl.suspense

Credit

• TransType.stockAccountNo

  (If this account is fully wildcarded, then Greentree Desktop posts to GLControl.suspense)

  If Inventory Module Control Use IN Analysis cost of sales in GL hierarchy is selected, then

  • StockItem.myINAnalysisCode.costAccount

    else

  • StockItem.myINAnalysisCode.salesAccount

    endif

  • myBatch.myBranch.glAccountStructure
  • Location.stockAccount
  • Warehouse.stockAccount
  • GLControl.suspense

Note: The above example represents a positive adjustment. For a negative adjustment, transactions are reversed.

Example

This example outlines how Greentree Desktop would construct the credit general ledger account to post the transaction value to if you use wildcards:

Greentree stops the search at this point, as it can construct a general ledger account. This is the account that the credit value is posted to, as long as it is a valid account set up on the GL Account Maintenance form. If Greentree Desktop works through the hierarchy and cannot find a valid account, the credit value posts to the general ledger suspense account.

Note: If the costing method is standard cost, and there is a variance between the actual transaction cost (if the user has edited the default standard cost in the transaction line) and the item's standard cost, the Cost of Purchase Variance Account specified in General Ledger Module Control is updated with the value of the variance.