IN Transaction Hierarchy

Here is the hierarchy followed by Greentree Desktop when posting the debit and credit transactions for an IN 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 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

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

Example

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

TransType.stockAccountNo

10. *. * (last two segments wildcarded)

StockItem.myINAnalysisCode.salesAccount

*. 10. 1010 (last two segments specified)

Greentree will stop the search at this point, as it can construct a general ledger account. This is the account that the credit value will be posted to, as long as it is a valid account set up in GL Account Maintenance. If Greentree works through the hierarchy and cannot find a valid account, the credit value posts to the GL Suspense Account.

Information

If Greentree costing method is standard cost (set in IN Module Control), 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 will be updated with the value of the variance.