Hello Odoo Forum, I am using *Odoo 17 Community Edition* In our company, the separation of received inventory value is *critical for accurate balance sheet reporting*, based on the item's billing status: *Goods Received, Not Billed (Accrue WH)*: This represents a *Current Liability*. The goods are physically in our warehouse, but the legal vendor invoice (Bill) has not yet been processed or validated. This account reflects an immediate, unbilled obligation. *Goods Billed/Paid, Not Received (Item

Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:

CRM
e-Commerce
Contabilitate
Inventar
PoS
Proiect
MRP

All apps

All Posts Oameni Insigne

Etichete (View all)

odoo accounting v14 pos v15

Despre acest forum

Suport

How to use TWO DIFFERENT Accrual Accounts (Accrue WH & Item in Transit) for Inventory Valuation?

accounting inventory valuation odoo17CE

2 Răspunsuri

422 Vizualizări

Muhammad Naufal

Hello Odoo Forum,

I am using Odoo 17 Community Edition

In our company, the separation of received inventory value is critical for accurate balance sheet reporting, based on the item's billing status:

Goods Received, Not Billed (Accrue WH): This represents a Current Liability. The goods are physically in our warehouse, but the legal vendor invoice (Bill) has not yet been processed or validated. This account reflects an immediate, unbilled obligation.
Goods Billed/Paid, Not Received (Item in Transit / GIT): This represents a Current Asset. Our company has either legally acknowledged the invoice or paid for the goods, but the physical items are still in transit. This account reflects the value of the asset we legally own but have not yet taken physical possession of.

Conclusion: We cannot use a single, shared Odoo account for both scenarios, as mixing Assets (GIT) and Liabilities (Accrue WH) in one account violates our financial reporting standards and distorts the Balance Sheet.

Current Successfull Configuration :

I have set the Stock Input Account on my Product Category to a liability account called Accrue WH (Current Liability).
Result: This successfully handles Scenario 1 (Goods Received Before Bill), where the journal is: DR Stock Valuation / CR Accrue WH. (This works!)

My Challenge (The Need for Item in Transit):

The problem is that Odoo uses this same Stock Input Account (Accrue WH) for ALL automated purchase receipts. I need to implement Scenario 2 where the Vendor Bill is processed first (as Goods In Transit).

Goal for Scenario 2: When the Vendor Bill is validated, the value must go to an Asset Account named Item in Transit (Current Asset), instead of relying on the standard Accrue WH setup.
- Expected Bill Validation Jurnal: DR Item in Transit / CR Accounts Payable
- Expected Receipt Jurnal: DR Stock Valuation / CR Item in Transit

My Configuration Challenge Summary:

Odoo defaults to the single Stock Input Account on the Product Category, making separation impossible here.

My Questions :

If this requires using a second Product Category, how should the second Product Category be configured to only interact with the Bill (and not the Receipt) for the Item in Transit journal?

Thank you for your time and expertise!

Cybrosys Techno Solutions Pvt.Ltd

Cel mai bun răspuns

Hi,

Odoo 17 Community does not support separating Goods Received Not Billed (GRNI) and Goods in Transit (GIT) using different accounts for the same product, because Odoo only allows one Stock Input Account per product category. This means the system cannot automatically decide whether to post to a liability account (Accrue WH) or an asset account (Item in Transit) based on whether the bill or the receipt comes first. That behavior is only achievable through customization.

To achieve clean accounting separation without custom code, the only practical configuration-based solution is to use two different product categories. One category uses the Accrue WH liability account for the scenario where goods are received before the bill. The other category uses the Item in Transit asset account for the scenario where the bill is validated before the goods are received. This correctly produces liability postings for GRNI and asset postings for GIT.

However, you cannot configure a category to apply only at the bill step or only at the receipt step—the category’s Stock Input Account is used for both the bill and the receipt. If a product must support both workflows, users need to assign the appropriate category based on the purchase process, or a small custom module must be created to switch categories automatically.

Hope it helps

Muhammad Naufal

Autor

Tentu. Here is the concise English version of the reply for the Odoo forum:

Hello Cybrosys Techno Solutions Pvt.Ltd,

Thank you very much for your valuable confirmation and the solutions provided.

I have decided to move forward with developing a custom module. This decision was made to avoid manual workarounds and ensure precise account separation for financial reporting.

This custom module will specifically utilize the status of the Bill and the Receipt to automatically route the purchase journal entries to the correct account, whether it is Accrue WH (Liability) or Item in Transit (Asset).

Thank you for your guidance!

Masoud

Odoo doesn’t support separate input accounts per transaction type (bill vs receipt) out of the box and for a single product category. To achieve your GIT vs Accrue WH split, you’ll need either a 1-custom module or a 2-workaround using separate product categories and manual journal adjustments. Odoo uses the Stock Input Account from the product category for all incoming stock valuation entries—regardless of whether the bill or receipt comes first. It doesn’t distinguish between “Goods Received Not Billed” and “Goods Billed Not Received” in its default flow.

Option 1: Use two product categories

Category A (Accrue WH): For standard flow—goods received before bill.

Category B (GIT): For pre-billed items—used only when the vendor bill is validated before receipt.

Option 2: Custom module

Key limitations : Odoo CE doesn’t support landed costs or advanced valuation flows natively and your developer has a lot of work :)

Muhammad Naufal

Autor

Thank you for confirming the limitations and suggesting the custom module route.

Regarding the "Key limitations" you mentioned: Odoo 17 CE does support Landed Costs (I see that configuration under Inventory Menu / Configuration / Valuation / Landed Costs). But you are absolutely right about the Advanced Valuation Flows—that is indeed the core logic my developer will need to customize to achieve the GIT vs. Accrue WH split.

Thanks for your input!

Enjoying the discussion? Don't just read, join in!

Create an account today to enjoy exclusive features and engage with our awesome community!

Înscrie-te

Related Posts	Răspunsuri	Vizualizări
Valuation of inventory in a multi-branch enviroment accounting inventory valuation	1 oct. 24	2886
What are Stock Interim Accounts and how should they be used? Rezolvat accounting inventory valuation	2 dec. 24	41704
Costing method was not selected but now selected how to process existing transactions? accounting inventory valuation	0 oct. 17	4144
How to Correct Finished Goods Valuation After Raw Material Cost Mistake (FIFO + Automated Valuation) Rezolvat accounting manufacturing inventory valuation	2 aug. 25	1213
Negative Stock and Valuation Issue Due to Inventory Adjustment in Odoo 17 accounting inventory valuation v17	1 mar. 25	3719

Această întrebare a fost marcată

Enjoying the discussion? Don't just read, join in!