Difference between revisions of "ITrack/Enterprise/Work Order Accounting"

From ISoft Wiki
Jump to navigationJump to search
Line 42: Line 42:
<br>
<br>
See also: [[Accounting (Enterprise)]]
See also: [[Accounting (Enterprise)]]
[[Category:Enterprise Concepts]]
[[Category:ITrack/Enterprise]]
[[Category:ITrack/Enterprise/Concepts]]
[[Category:ITrack/Enterprise/Concepts]]

Revision as of 12:00, 10 July 2009

Work orders have a powerful but complicated accounting system. These accounting processes are described in detail here so that account managers can configure their GL Categories and GL Contexts appropriately.

Work orders essentially have two stages in their accounting lifetime: work in progress, and finalization. The timing of these stages can vary depending on the WO parameters, such as whether it is a customer WO, or a WO for inventory.

In the work in progress stage, inventory and labor value is moved into appropriate work in progress GL accounts. Then, once a WO has been finalized, value is moved from the work in progress accounts into either inventory value (for work on inventory WOs) or into sales and accounts receivable (for work on customer units).

Pertinent GL Contexts

Work orders have several GL Contexts used in different situations, depending on the item being accounted and the item being accounted.

  • Work Order Production - used by the master part record on a work order for inventory (not on customer WOs).
  • Work In Progress contexts - these contexts are designed to facilitate moving value into work in progress accounts. If a company doesn't use work in progress accounts, this context can be left empty. There are several specific contexts that are used depending on the item in question.
    • Work In Progress - used by inventory items (and miscellaneous part items), labor, EPA charges, and shop fees when an open WO is saved. This context is designed to facilitate moving assets into a work in progress account.
    • Work In Progress Inherent Core - same as above, but used for inherent core charges on inventory items.
    • Work In Progress Dirty Core - same as above, but used for dirty core items.
  • WO Sold contexts - these contexts come into play when a 'work on customer unit' WO gets finalized. One of the following contexts gets used depending on the type of item in question.
    • Work Order Sold - used by inventory items, labor, EPA charges, and shop fees when a 'work on customer unit' WO reaches the final accounting stage.
    • Work Order Sold Inherent Core - same as above, but for inherent cores.
    • Work Order Sold Dirty Core - same as above, but for dirty cores.
  • WO Consumed contexts - these contexts come into play when a 'work on inventory' WO gets finalized. One of the following contexts gets used for WO components' accounting, depending on the type of item in question.
    • Work Order Consumed - used by inventory items, labor, EPA charges, and shop fees when a 'work on inventory' WO reaches the final accounting stage.
    • Work Order Consumed Inherent Core - same as above, but for inherent cores.
    • Work Order Consumed Dirty Core - same as above, but for dirty cores.

GL Accounting Timeline

The following tables show detailed accounting information. The Item column describes the object that is being accounted. Timing describes the phase the accounting happens in (work in progress or finalization). Table is the database table that those objects are stored in. GL Category describes the gl category used to retrieve the accounts for accounting (if its in italics, that means the appropriate accounts are stored in the table, probably in the final...glaccountid or wip...glaccountid accounts). Context used quickly describes the gl context(s) used for accounting. WIP means Work In Progress, WOSold is Work Order Sold, and WOConsumed is Work Order Consumed (WIP..., WOSold..., or WOConsumed... mean either the context WIP, WIP Inherent Core, or WIP Dirty Core and so forth depending on the item type). Amount describes the value that will be accounted, which is normally the cost of the item for inventory account pairs and price of the item for transaction account pairs. Columns I and T simply describe which account pairs are hit in the accounting: inventory pair, transaction pair, or both.

ItemTimingTableGL CategoryContext UsedAmountITOther Notes
Job PartWIPjobpartjobpart.glcategoryWIP...jobpart.averagecost * jobpart.quantityX
LaborWIPworkclockjob.glcategoryWIPworkclock.costX
Job PartFinaljobpartjobpart.glcategoryWOSold... or WOConsumed...jobpart.averagecost * jobpart.quantityX
LaborFinalworkclockjob.glcategoryWOSold or WOConsumedworkclock.costX
JobFinaljobjob.glcategoryWOSold or WOConsumedjob.costXOnly if the job has a fixed price
Job PartFinaljobpartjobpart.glcategoryWOSold... or WOConsumed...jobpart.price* jobpart.quantityXOnly if the job doesn't have a fixed price
LaborFinalworkclockjob.glcategoryWOSold or WOConsumedjob.laborchargeXOnly if the job doesn't have a fixed price
EPA ChargesFinaljobEPA GL Category*WOSold or WOConsumedjob.epachargeXOnly if the job doesn't have a fixed price
Shop FeesFinaljobShop Fees GL Category**WOSold or WOConsumedjob.shopfeesXOnly if the job doesn't have a fixed price
Master PartFinalworkorderinventory.glcategoryWork Order ProductionSum of all job.costXOnly if the work order is 'work on inventory'
Master PartFinalworkorderinventory.glcategoryWork Order Productionworkorder.priceXOnly if the work order is 'work on inventory'


See also: Accounting (Enterprise)