Finance and inventory teams live with a recurring reconciliation headache: stock physically moves, but the corresponding accounting entries lag, land in the wrong period, or get posted by hand after the fact. Odoo's native Anglo-Saxon (perpetual) valuation does generate stock-interim and stock-valuation entries when accounts are configured on the product category — but the moment your reality gets more nuanced, the standard behavior runs out of road. Landed costs that must hit COGS on a specific date, inter-warehouse transfers that should be accounting-neutral yet auditable, consignment or third-party moves that must never touch valuation, scrap and inventory adjustments needing dedicated expense accounts, manual and backdated pickings that slip past the automation — each of these leaves a gap. Month-end then gets spent chasing the difference between the stock.valuation.layer figures and the general ledger.

Stock Picking Auto Journal Entry is a module we build for your specific database that hooks into stock-move confirmation and posts a complete, correct account.move for every validated stock.picking according to rules you define. Technically we extend stock.picking and stock.move — typically an override of _action_done() supported by an @api.depends compute, plus (where you need backdated or manual pickings covered) an automated action on the done state so nothing slips through. The logic resolves the debit and credit accounts through a configurable resolution chain — product, then product category (property_stock_account_input/output/valuation), then a per-operation-type or per-location override we add via new fields on stock.picking.type and stock.location. Amounts are read from the authoritative stock.valuation.layer value rather than recomputed, so the ledger always ties back to Odoo's own valuation numbers.

On top of the core posting engine we add the governance you need to trust it: configurable journal selection per operation type, a dedicated analytic-distribution hook, an idempotency guard so re-validated or backordered pickings never double-post, and a clear link (account.move.stock_picking_id) from each entry back to its source transfer for one-click drill-down. Everything ships with ir.model.access.csv rules plus record rules for multi-company isolation, a settings panel under Inventory/Accounting configuration, and QWeb-ready fields so your existing valuation and journal reports pick the data up. Because it is built against your chart of accounts and product-category setup, the accounts are correct on day one rather than after weeks of correcting mispostings.

Delivery is build-to-order. We start with a scoping call to confirm your valuation method, edition (Community or Enterprise), the operation types and locations in play, and any localization requirements, then we build against a staging copy of your database, run UAT with your finance team, and deploy with a documented rollback plan. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company consolidation, additional operation-type/location rules, deep localization of the account resolution, and migration of historical stock moves into the new posting model increase the quoted scope.