ItemCostFifo
Updated
Cost layers of an Item. A receipt opens a layer with quantity and amount. An issue takes quantity off open layers and writes the matching amount off. The engine is FIFO lots even when the company values issues at weighted average.
| Kind | Accumulation register |
| Module | Costing |
| Menu | Costing → Registers → Item cost (FIFO) |
Dimensions and resources#
| Name | |
|---|---|
| Dimension | Item → Item |
| Resource | Quantity |
| Resource | Amount |
The Item cut is a schema dimension, not an analytic. The register is not double-entry. It allows a negative balance. Quantity drives the lots. Amount is the cost those lots still hold.
CostingSettings Costing method chooses which open layers the next issue takes, and at what unit. FIFO takes the oldest layers first. Weighted average takes quantity from each open layer in proportion to what that layer still holds, at the average unit of all open layers. Empty method is FIFO. InventoryValue is then written down by the quantity and the amount the layers gave up.
There is no LIFO. There is no layer per cell or per store. A quantity-only opening without a receipt does not create a layer. An issue can then take only as much cost as the layers still hold. An already-issued lot is not retargeted from a script.
Written by#
PurchaseOrder on Received opens a layer per receipt line. A surplus on StockAdjustment or StockCount opens a layer at the current average, or at the planned unit when there are no layers.
A net stock issue consumes layers: SalesRealization, GoodsIssue, PurchaseReturn, a shortage on StockAdjustment or StockCount, and component consumption on ProductionOrder. StockTransfer nets to zero and leaves the layers.
When ProductionOrder is Finished, a layer is opened for the product at the cost taken off the component layers, plus confirmed labour.
How the issue amount is chosen is Costing method.