General Ledger Categories

 


 

   
 
Stock General Ledger Categories
 

Stock movement values can be posted to the General Ledger. The Stock GL Category field in Inventory Control Full Stock Details (st_stock_entry) can be used to enter a three-character code to identify the General Ledger accounts to which details of stock movements should be posted. (Note that if your system is set up to use Landed Costs then this field can be used with the Supplier Category to identify which Landed Costs Matrix is to be used.)

GL Cross References (st_nl_xref) allows you to define General Ledger accounts for a Stock GL Category to analyse the value of stock movements. Only detail GL accounts can be assigned for cross-reference purposes.

In order for a movement type to generate these General Ledger transactions the movement type must be entered in the STNLMOVTYP system key see below for a list of the movement types.

The wild card system keys (STNLWCDEP, STNLWCWH and STNLWCANx) record how they are to be used in the GL account codes. When creating a GL Cross Reference posting code, the appropriate value is used to replace the wild cards in the given element. For example,
WO assembly warehouse = WH
GL Cross reference code = 01-02-0003-??
Value of STNLWCWH = 4
Posting code = 01-02-003-WH

If your system is set up to use Works Order Variances and Analysis you will be able to create GL cross references to analyse Works Order movements and cost variances in detail. Works Order issues (wo_issue_works_order), completions (wo_complete_orders), dekits and rework can all have account codes to analyse material, labour, overhead and subcontracted outwork costs. Planned variance (between Planned costs, for the BOM and the loaded Route, and the Standard Cost) and Actual variance (between the Actual costs and the Planned costs) can also be analysed by material, labour, overhead and subcontracted outwork. If your system is also set up to use Alternative BOM Assemblies you can also analyse planned and actual variances for alternative and supersession Bills of Material and Routes.

 
     
 
Analysis Codes and System Keys
 

If a product does not have a Stock GL Category or a movement type does not have an account code the following system keys contain the default account code:

Movement
Type

Account Group

System Key
A SOP issues STNLOPIACC
B Works Order Rework and Dekits STNLDEKACC
C Inventory Control adjustments STNLADJACC
D Inventory Control issues STNLSTIACC
E Inventory Control despatches STNLDSPACC
F Works Order issues STNLWOIACC
G Works Order finished goods STNLFINACC
H SOP customer returns STNLOPRACC
I Inventory Control customer returns STNLCRTACC
J Inventory Control production receipts STNLPRACC
K Inventory Control transfers STNLTRNACC
L POP supplier returns / bad goods STNLBADACC
M Inventory Control write-off goods STNLOFFACC
N Purchase Order receipts STNLPORACC
O Inventory Control goods received STNLGRNACC

If your system is set up to use Works Order Variances and Analysis there are new and amended movement types, that are reflected in the STNLMOVTYP system key which has the following changes to its possible settings:

Movement type Account group System key holding
default posting code
Old New
B R Works Order Rework STNLREWACC
B S Works Order Dekit STNLDEKACC
F Q Works Order Issues STNLWOIACC
G P Works Order Finished Goods STNLFINACC
  T Planned variance due to Alternative BOM / Route STNLAPVACC
  U Actual variance due to Alternative BOM / Route STNLAAVACC
  V Planned variance due to Supersession BOM / Route STNLSPVACC
  W Actual variance due to Supersession BOM / Route STNLSAVACC
  X Planned variance due to Master BOM / Route STNLNPVACC
  Y Actual variance due to Master BOM / Route STNLNAVACC
  Z Works Operations STNLWOPACC
  a Stock revaluation due to Works Order Rework or Dekit STNLSRVACC

NOTE: Although the Works Order stock movements above can be broken down into material, labour, overhead and outwork if they use a GL Cross Reference, each movement type only has one default system key, so the distributions will not be split.

     
 
Works Operations Cost Recovery Accounts
  If your system is set up to use Works Order Variances and Analysis a General Ledger distribution is generated when a routes' operation resource i.e. labour, overhead or outwork, is booked to a Works Order using one of the following Work in Progress options:
  • Work in Progress Tracking (ww_wip_tracking)
  • Timesheet Entry (ww_timesheet_entry)
  • Operation Tracking (ww_operation_track)

A contra distribution is made to the relevant Works Operation cost recovery account.

The Stock GL distribution for the Works Operation movement has movement type of 'Z'.

The Stock General Ledger Category used is taken from the Works Order Finished Goods.

The basis for the cost recovery account is a GL detail account code template defined by a system key, one for each resource type i.e. labour, overhead and outwork

The templates can contain up to two (i.e. 0, 1 or 2) sets of wild card characters (?), each representing all, or part, of an element of the GL detail account code structure.

Example templates:

  • 3-01-10-01-005 - No wild cards
  • 3-??-10-01-005 - One wild card set in element 2
  • 3-??-10-01-??? - Two wild card sets in elements 2 and 5
  • 3-01-10-01-??5 - A partial wild card set in element 5
 
 
Labour Cost Recovery
 

The labour cost recovery template system key WSNLOPLBR should have one wild card set if the Setters and Operators in your Operations are all booked by Skill Group, the element the wild card set appears in is set by WSNLOPSG. The values used to replace the wild card characters are held in the Skill Group's GL Map Code field.

WSNLOPLBR should have two wild card sets if any of the Setters and Operators are booked by Operator, one for the Skill Group, as above, and one for the Operator appearing in the element set by WSNLOPOP and taking its values from the Operator's GL Map Code field. In this instance if a Setter or Operator is booked by Skill Group, then the code to fill the Operator wild card set is taken from the same elements of the posting code of system key STNLWOPACC, if that produces an invalid posting code, the whole of the STNLWOPACC posting code is used.

 
     
 
Overhead Cost Recovery
 

The overhead cost recovery template system key WSNLOPOVH should have one wild card set if the Machines in your non-Outwork Operations are all booked by Work Centre, the element the wild card set appears in is set by WSNLOPWC. The values used to replace the wild card characters are held in the Work Centre's GL Map Code field.

WSNLOPOVH should have two wild card sets if any of the Machines are booked by Machine Code, one for the Work Centre, as above, and one for the Machine appearing in the element set by WSNLOPMC and taking its values from the Machine's GL Map Code field. In this instance if a Machine is booked by Work Centre, then the code to fill the Machine wild card set is taken from the same elements of the posting code of system key STNLWOPACC, if that produces an invalid posting code, the whole of the STNLWOPACC posting code is used.

 
     
 
Outwork (subcontracting) Cost Recovery
 

The outwork cost recovery template system key WSNLOPSUB should have one wild card set if the Machines in your Outwork Operations are all booked by Work Centre, the element the wild card set appears in is set by WSNLOPWC. The values used to replace the wild card characters are held in the Work Centre's GL Map Code field.

WSNLOPSUB should have two wild card sets if any of the Machines are booked by Machine Code, one for the Work Centre, as above, and one for the Machine appearing in the element set by WSNLOPMC and taking its values from the Machine's GL Map Code field. In this instance if a Machine is booked by Work Centre, then the code to fill the Machine wild card set is taken from the same elements of the posting code of system key STNLWOPACC, if that produces an invalid posting code, the whole of the STNLWOPACC posting code is used.

 
     
 
Works Order Movements and Variance Distributions
  The Stock General Ledger Category used is taken from the Works Order Finished Goods for all Works Order movement types except for the Stock Balance Sheet Account of stock components, when the Stock General Ledger Category of the component is used instead, this applies to both issues and dekits.  
     
 
Sales General Ledger Categories
  Sales from within the Sales Order Entry module can be posted to the General Ledger via the Accounts Receivable module. The Sales G/L Category field in Full Stock Details (st_stock_entry) can be used to enter a three-character code to identify those General Ledger accounts to which details should be posted. This code is used by the Cost of Sale Codes option in Sales Order Entry & Invoicing to define the General Ledger account codes to be used.  
     
 
Purchase General Ledger Categories
  Purchases from within the Purchase Order Processing module may be posted to the General Ledger via the Accounts Payable module. The Purchase G/L Category field in Full Stock Details (st_stock_entry) can be used to enter a three-character code to identify those General Ledger accounts to which details should be posted. This code is used by the system keys PONLACCxxx (where xxx = category code) to link the Purchase G/L Category to a General Ledger Posting Code. If no account code is specified in the system keys for the Purchase G/L Category the default purchases account code held in the PONLACC system key will be used.