Inventory Value Determination & Cost Flow Behavior
1. Overview
This guide explains how inventory valuation, item costing, and asset value calculations behave within XoroERP. It covers cost hierarchy logic, purchase and manufacturing cost impact, inventory adjustments, valuation reporting, and transaction sequencing rules that determine inventory accuracy.
2. Functional Workflow
2.1 Item Cost Determination Workflow
Step 1: Item Creation
When an item is created, the system assigns a manually defined standard cost.
Step 2: Inventory Transactions Occur
As transactions are recorded, the system evaluates available cost sources:
Standard cost (fallback when no history exists)
Average cost (moving average recalculated over time)
Last landed cost (latest receipt cost including reconciliation charges)
Step 3: Transaction Cost Selection
The system applies the appropriate cost depending on transaction type and inventory history.
2.2 Purchase Order and Item Receipt Cost Flow
Step 1: Purchase Order Creation
Purchase orders default to the item’s standard cost unless manually overridden.
Step 2: Item Receipt Creation
When an Item Receipt (IR) is recorded:
Inventory quantity increases.
Asset value increases.
Landed cost may include reconciliation charges.
Average cost is recalculated.
Step 3: Cost Update
The moving average updates using total inventory value and quantity.
2.3 Average Cost Calculation Workflow
Average cost is calculated using:
Total Asset Value ÷ Total On-Hand Quantity
When new inventory is received:
Existing inventory value is combined with new receipt value.
Quantity-weighted recalculation occurs.
Historical inventory continues to influence valuation.
2.4 Invoice Consumption Workflow
When an invoice is created:
Inventory quantity decreases.
Cost of Goods Sold (COGS) is calculated using the current average cost.
Remaining inventory value is reduced.
Average cost does not change.
2.5 Manufacturing Order Cost Flow
Production Transactions
Finished goods increase inventory quantity.
Average cost is recalculated.
Consumption Transactions
Raw materials decrease inventory quantity.
Behaves similarly to invoice consumption.
Average cost is not recalculated.
2.6 Inventory Adjustment Workflow
Three adjustment types are supported:
Quantity-only adjustment
Value-only adjustment
Quantity and value adjustment
System Behavior
First-ever quantity adjustment uses standard cost.
Later quantity adjustments use average cost.
Value-based adjustments change inventory valuation.
2.7 Inventory Valuation Monitoring Workflow
Users review inventory valuation through the Inventory Valuation Summary report, which displays:
On-hand quantity
Total asset value
Average cost
Any negative values indicate data integrity issues.
2.8 Transaction Validation Workflow (Error Handling)
When a transaction is saved:
System validates inventory and asset value impact.
If negative values would result, the system blocks the transaction.
Error Code 102 identifies the conflicting transaction.
2.9 Item Receipt Merge Workflow
When multiple Item Receipts are merged:
Transaction history is rewritten.
Inventory availability dates may shift.
Incorrect sequencing may invalidate prior sales.
3. Core Configuration Logic
3.1 Cost Hierarchy Rules
The system prioritizes cost sources based on availability:
Standard cost — used when no inventory history exists.
Average cost — used after inventory transactions occur.
Last landed cost — derived from the most recent item receipt.
3.2 Purchase and Landed Cost Dependencies
Purchase order price does not define final inventory cost.
Reconciliation charges increase landed cost.
Item receipts determine actual inventory valuation.
3.3 Inventory Valuation Controls
Inventory quantity and asset value must remain positive.
Transaction sequence determines valuation accuracy.
Inventory history cannot be safely modified retroactively.
3.4 Manufacturing Cost Dependencies
Production increases valuation.
Consumption reduces quantity without repricing inventory.
3.5 Transaction Sequencing Constraints
Inventory must exist before invoicing.
Backdated transactions may invalidate valuation.
Merge operations must preserve original transaction order.
4. Transaction-Level Behavior
4.1 When an Item Receipt Is Created
System Behavior
Inventory quantity increases.
Asset value increases.
Landed cost may include reconciliation charges.
Average cost recalculates.
4.2 When an Invoice Is Created
System Behavior
Inventory quantity decreases.
COGS calculated using current average cost.
Asset value reduced.
Average cost unchanged.
4.3 When Manufacturing Production Occurs
System Behavior
Finished goods added to inventory.
Average cost recalculated.
4.4 When Manufacturing Consumption Occurs
System Behavior
Raw materials reduced.
Average cost unchanged.
4.5 When Inventory Adjustment Occurs
System Behavior
Quantity or value changes based on adjustment type.
First adjustment may use standard cost.
Value-based adjustments impact average cost.
4.6 When Backdated Transactions Are Saved
System Behavior
System checks for negative inventory impact.
Transaction blocked if valuation becomes invalid.
Error Code 102 displayed.
5. Structured Examples
Example 1: Receiving Inventory at Higher Cost
Action: Record an Item Receipt with higher cost than existing inventory.
System Impact:
Inventory quantity increases.
Asset value increases.
Moving average cost rises.
Example 2: Creating Invoice After Inventory Receipt
Action: Invoice created after inventory exists.
System Impact:
Inventory reduced.
COGS recorded using average cost.
Average cost unchanged.
Example 3: Backdated Invoice Before Inventory Receipt
Action: Invoice dated earlier than inventory receipt.
System Impact:
Negative on-hand quantity.
Negative asset value.
Transaction may trigger Error Code 102.
Example 4: Merging Item Receipts Using Incorrect Date
Action: Merge multiple item receipts using the most recent date.
System Impact:
Inventory availability shifted forward.
Prior sales invalidated.
Negative inventory risk introduced.
6. Important Rules & Constraints
Average cost is quantity-weighted and continuously recalculated.
Invoices never change average cost.
Item receipts determine inventory valuation.
Inventory must exist before invoicing.
Negative asset value indicates transactional sequencing issues.
First quantity adjustment uses standard cost.
Inventory adjustments only affect cost when value is included.
Merging item receipts must retain earliest transaction date.
Backdated transactions can invalidate inventory history.
7. Best Practices
Always verify transaction sequence before investigating valuation issues.
Review full transaction history when analyzing cost discrepancies.
Use value-based adjustments only when inventory repricing is required.
Maintain correct transaction dates for inventory and sales.
Educate users on proper item receipt merging procedures.
Monitor inventory valuation reports regularly.
8. Common Mistakes & Pitfalls
Creating invoices before inventory is received
Negative on-hand quantity and negative asset value
Backdating transactions without verifying inventory availability
Transaction sequencing errors and valuation inconsistencies
Assuming purchase order price equals final inventory cost
Incorrect expectation of inventory value due to reconciliation charges
Misinterpreting manufacturing consumption as cost-changing activity
Incorrect analysis of average cost changes
Performing the first inventory adjustment without understanding standard cost behavior
Unexpected inventory valuation results
Merging item receipts using the most recent date instead of earliest date
Invalidated historical sales and negative inventory scenarios
Ignoring negative asset value in valuation reports
Data integrity issues remain unresolved
Reviewing only current inventory value without checking transaction history
Root cause of cost discrepancies not identified
9. Frequently Asked Questions (FAQs)
Q1. Why does the system sometimes use standard cost instead of average cost?
A: The system uses standard cost when no prior inventory history exists.
Q2. Do invoices change average cost?
A: No. Invoices only reduce quantity and asset value using the existing average cost.
Q3. What transactions impact average cost?
A: Item receipts, manufacturing production, and inventory adjustments that include value.
Q4. Why does negative inventory occur?
A: Typically due to backdated invoices or selling inventory before it was received.
Q5. What is Error Code 102?
A: A validation error indicating the transaction would create negative inventory or asset value.
Q6. Can inventory adjustments change average cost?
A: Only adjustments that include value affect average cost.
Q7. Why can merging item receipts cause valuation issues?
A: Merging may overwrite transaction dates and invalidate earlier sales.
Q8. What is last landed cost?
A: The cost from the most recent item receipt, including reconciliation charges.
Q9. Does manufacturing consumption affect average cost?
A: No. Only production impacts average cost.
Q10. What should be checked first when inventory valuation appears incorrect?
A: Transaction sequence and transaction dates.
10. Conclusion
Accurate inventory valuation in XoroERP depends on correct cost hierarchy usage, proper transaction sequencing, and consistent inventory history management. Understanding how item receipts, manufacturing activity, and inventory adjustments influence average cost ensures reliable asset valuation and financial reporting.
Following the defined workflows and constraints prevents negative inventory scenarios, valuation inconsistencies, and transactional errors, enabling stable inventory control and accurate cost tracking across operations.
Last updated
Was this helpful?