Account Cut-off Accrual Picking
This module generates expense and revenue accruals based on the status of orders, pickings and invoices.
To understand the behavior of this module, let's take the example of an expense accrual. When you click on the button Re-Generate Lines of an Expense Accrual:
- Odoo will look for all incoming picking in Done state with a Transfer Date <= Cut-off Date (for performance reasons, by default, the incoming picking dated before Cut-off Date minus 90 days will not be taken into account (this limit is configurable via the field Picking Analysis). It will go to the stock moves of this picking and see if they are linked to a purchase order line.
- Once this analysis is completed, Odoo has a list of purchase order lines to analyse for potential expense accrual.
- For each of these purchase order lines, Odoo will:
- scan the related stock moves in done state and check their transfer date,
- scan the related invoices lines and check their invoice date.
- If, for a particular purchase order line, the quantity of products shipped before the cutoff-date (or on the same day) minus the quantity of products invoiced before the cut-off date (or on the same day) is positive, Odoo will generate a cut-off line.
This module should work well with multiple units of measure (including products purchased and invoiced in different units of measure) and in multi-currency.
auto_awesome What this module does
AI-generated from the code · Odoo 15.0Generates accrued expense and accrued revenue entries from done stock transfers linked to purchase and sale orders, so you can book cut-off accruals for goods received but not invoiced (or delivered but not invoiced).
This module extends the cut-off feature of Odoo so that accrual entries can be built from stock movements instead of only from invoices.
When you open an Account Cut-off of type Accrued Expense or Accrued Revenue and click Re-Generate Lines, Odoo looks at done incoming transfers (for expenses) or done outgoing transfers (for revenue) whose transfer date falls between the cut-off date and a number of days before it. That look-back window is the Picking Analysis Interval, shown on the cut-off form and defaulting to 90 days; it can be changed per cut-off and set company-wide in the accounting settings. The value must be strictly positive.
For each transfer, Odoo follows the stock moves back to their purchase or sale order line, then compares the quantity already delivered before the cut-off date with the quantity already invoiced before that date. The difference is valued using the invoice price when an invoice exists, otherwise the order price, and an accrual line is created with the partner, product description, quantity, unit price, currency, analytic account and the expense or income account (mapped through the fiscal position). Taxes are added when accrual taxes are enabled on the company. If the product or its category has no expense or income account, Odoo raises an error.
It touches account.cutoff, res.company and res.config.settings, and adds fields to the existing cut-off and settings screens.
Depends on
Models and fields (3)
- res.company · extends an existing modeldefault_cutoff_accrual_picking_interval_days (Picking Analysis Interval)
- account.cutoff · extends an existing modelpicking_interval_days (Picking Analysis Interval)
- res.config.settings · extends an existing modeldft_cutoff_accrual_picking_interval_days
Text generated by AI (DeepSeek) from reading the Odoo 15.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 4 confirmed, 5 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/account-closing.
terminal Installation and usage
OCA documentation · Odoo 15.0Configuration
Source · Odoo 15.0For configuration instructions, refer to the README of the module account_cutoff_base.
No verified information in OCA: Installation, Usage.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.