| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) • Inventory (stock) |
| Community Apps Dependencies | Show |
| Lines of code | 1960 |
| Technical Name |
l10n_ro_stock_custody |
| License | OPL-1 |
| Website | https://www.nexterp.ro |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) • Inventory (stock) |
| Community Apps Dependencies | Show |
| Lines of code | 1960 |
| Technical Name |
l10n_ro_stock_custody |
| License | OPL-1 |
| Website | https://www.nexterp.ro |
Romania - Stock Custody
Romania - Custody and Call-off Stock locations and tracking
Overview
This module adds support for Romanian custody (custodie) and call-off stock locations on top of Odoo's standard inventory.
A location can be flagged as a custody location and given a direction:
- Inbound custody — goods physically held on our premises but owned by a foreign supplier. Romanian accounting requires they be tracked off-balance-sheet (class 80xx, typically 8033 paired with 8039) rather than on the standard stock valuation accounts.
- Outbound custody / call-off stock — our goods physically held at a customer's site abroad. They remain on the balance sheet through the standard valuation account on the location, and a 12-month deadline is monitored automatically — the EU call-off stock simplification expires at that point and the arrangement converts into a mandatory intra-community acquisition in the destination Member State.
Inbound moves post a custody / counterpart pair on the off-balance sheet, dispatches reverse it, and internal transfers between two inbound custody locations post nothing. A daily cron scans outbound transfers approaching the 12-month limit and schedules a warning activity on the related picking.
Built & supported by NextERP Romania
Romanian Odoo specialists, here for the long run — from implementation to localization and day-to-day production support.
What we do
Odoo Solutions
From quick-start rollouts to multi-company deployments and custom modules built for your processes.
Romanian Localization
SAF-T (D406), e-Factura, e-Transport, D300 / D390 / D394, ANAF integration, full chart of accounts and fiscal positions.
Our Services
Implementation, customization, migration, integration, support and consultancy — Romanian-speaking, SLA-backed.
Features
- Custody flag on stock locations — two new fields,
Custody LocationandCustody Type(Inbound / Outbound), are added to the standard location form under the Additional Information group. - Off-balance-sheet posting for inbound custody — moves into an
inbound custody location post
Dr custody / Cr counterpart(e.g. 8033 / 8039), dispatches post the reverse, and internal transfers between two inbound custody locations post nothing. - Company-level account configuration — the pair of accounts is
set once on the company through
l10n_ro_property_stock_picking_custody_account_idandl10n_ro_property_stock_picking_custody_counterpart_account_id. - Outbound (call-off) stock keeps the standard balance-sheet valuation flow — Romanian practice uses account 357 (Goods at third parties).
- 12-month call-off deadline tracking — a daily cron
(
Romania - Call-off Custody Expiry Check) scans outbound transfers between 11 and 12 months old and schedules a Call-off Custody Expiry mail activity on the picking with the 12-month deadline. - Storable, real-time products only — the off-balance-sheet entry is generated only when the product is storable with real-time valuation; consumable / standard-costed products fall back to Odoo's default behavior.
- Safe fallback — if either custody account is missing on the company, the module steps back to standard Odoo behavior, which requires a valuation account on the location.
Configuration
Two steps are required: configure the off-balance-sheet account pair on the company, then flag the locations used for custody.
1. Set the custody accounts on the company
- Go to Settings → Users & Companies → Companies and open the Romanian company.
- On the company form, fill in:
- Romania - Picking Account Custody
(
l10n_ro_property_stock_picking_custody_account_id) — typically8033 - Stocks held in custody. - Romania - Picking Account Custody Counterpart
(
l10n_ro_property_stock_picking_custody_counterpart_account_id) — typically8039 - Counterpart for class-80 accounts.
- Romania - Picking Account Custody
(
- Save. If either field is left empty, the module silently falls
back to standard Odoo behavior (which requires a
valuation_account_idon the location).
The demo data shipped with the module configures 8033 / 8039 from
the Romanian chart template automatically.
2. Create the custody locations
- Go to Inventory → Configuration → Warehouse Management → Storage Locations.
- Click New (or open an existing internal location).
- In the Additional Information section, expand the Romania -
Custody group:
- Tick Custody Location.
- Pick a Custody Type:
- Inbound (supplier's goods at our site) — for goods we hold on behalf of a foreign supplier.
- Outbound (our goods at customer's site) — for our goods physically at a customer's site (call-off stock).
- Save. The location now behaves as a custody location for all transfers that touch it.
3. Outbound (call-off) deadline cron
The daily cron Romania - Call-off Custody Expiry Check
(l10n_ro_stock_custody.cron_custody_expiry_check) is enabled by
default and runs once a day. It can be paused or rescheduled from
Settings → Technical → Scheduled Actions. The activity it
schedules is Call-off Custody Expiry, defined in the Activity
Types registry.
4. Access rights
No dedicated security groups are added. Standard inventory and accounting permissions apply: setting the custody accounts on the company requires Settings: Administrator, and tagging locations requires Inventory: Manager.
How it works
Once the custody accounts and locations are configured, stock operations work exactly like standard Odoo transfers. The accounting side adapts automatically based on where the move starts and ends.
Inbound custody (8033 / 8039)
- Receipt to an inbound custody location — posts
Dr custody (8033) / Cr counterpart (8039)for the move's computed value. When the standardstock_accountflow leaves the value at zero (no upstream invoice / sale order), the module falls back tostandard_price × quantityso the off-balance-sheet entry still reflects an amount. - Delivery from an inbound custody location — posts the reverse:
Dr counterpart (8039) / Cr custody (8033). - Transfer between two inbound custody locations — no account entry is created; the net off-balance-sheet position is unchanged.
Only storable products with real-time valuation produce these
entries; consumable or manual-cost products are ignored, matching
standard Odoo behavior.
The accounting entries are visible on the related stock move's Account Move link, the same way standard inventory valuation entries are.
Outbound (call-off) stock
Outbound custody locations keep Odoo's normal balance-sheet flow through the location's valuation account (in Romania account 357). What the module adds is a deadline reminder:
- The daily cron looks for outbound custody transfers whose
date_doneis between 11 and 12 months ago. - For each such picking it schedules a Call-off Custody Expiry
activity on the picking, dated 12 months after
date_doneand assigned to the picking's responsible user. - The activity carries a note explaining that the sale to the customer must be triggered or the goods returned to Romania before the deadline, otherwise the call-off simplification falls and an intra-community acquisition has to be declared in the destination Member State.
The cron is idempotent — pickings that already carry the activity are skipped on subsequent runs.
Versions
19.0.0.1.0 (2026-05-24)
- Changelog tracking starts at this release.
Discover the NextERP suite
Other modules from the same publisher, built to work together.
NextERP Romania
Odoo implementation, customization, Romanian localization and long-term support since 2018.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module