This module allows you to easily compute the accrued revenue and accrued expenses based on the Start Date and End Date of journal items (copied from the same fields of invoice lines) and to generate the related cutoff journal items.
For example, imagine that you have an activity where you invoice at the begining of each quarter the period corresponding to the previous quarter. So, on January 10th 2018, you generate customer invoices for the period running from October 1st 2017 to December 31st 2017. If your fiscal year ends on December 31st, you will need to provision in 2017 the revenue that is invoiced in 2018 that cover 2017. With this module, you will create an Accrued Revenue on December 31st 2017 and Odoo will identify the customer invoices that are dated after December 31st 2017 and that cover a period before December 31st 2017 (totally or in part).
auto_awesome What this module does
AI-generated from the code · Odoo 13.0Adds accrued expense and accrued revenue cutoffs based on the start and end dates of invoice lines, so you can provision revenue or costs that belong to a period before the cutoff date even if the invoice is dated later.
This module extends the cutoff feature in Accounting. When you create an Accrued Expense or Accrued Revenue cutoff, Odoo now looks at journal items that have a start date and an end date (copied from invoice lines) and that are dated after the cutoff date but cover a period starting on or before it.
- For each such item, the module computes how many days of the period fall before the cutoff date and calculates the proportional amount to accrue.
- It creates cutoff lines with the original account, the mapped cutoff account, the partner, the analytic account, and the computed amount.
- If the original item has taxes, the module also computes the tax portion and creates tax lines, using the 'Accrued Expense Tax Account' or 'Accrued Revenue Tax Account' configured on the tax. If those accounts are missing, or if a tax is price-included, an error message is shown.
- The source journals are automatically pre-filled: purchase journals for accrued expenses and sale journals for accrued revenues, based on the company.
The feature appears in the Accounting app under the cutoff menus (Accrued Expenses and Accrued Revenues). It touches the account.cutoff, account.cutoff.line, account.cutoff.mapping, account.move.line, and account.tax models.
Models and fields (1)
- account.cutoff · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 13.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: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 13.0
Confirmed on 2026-11-03 in branch 13.0 of OCA/account-closing.
terminal Installation and usage
OCA documentation · Odoo 13.0Configuration
Source · Odoo 13.0On the Accounting configuration page available via the menu Invoicing > Configuration > Settings, there is a Cut-offs section where you can configure:
- the Default Cut-off Journal, which is the journal in which the cut-off journal items will be generated by default,
- the Default Account for Accrued Revenue,
- the Default Account for Accrued Expense.
Usage
Source · Odoo 13.0To compute the accrued revenue, go to the menu Invoicing > Cut-offs > Accrued Revenue and click on the Create button. Enter the cut-off date, check that the source journals contains all your sale journals and click on the button Re-Generate lines: Odoo will scan all the journal entries of the source journals and will get all the lines that have a start date before or equal to the cut-off date and, for each line, it will compute the revenue to provision. If you agree with the result, click on the button Create Journal Entry: Odoo will generate an account move at the cut-off date to provision these revenue. Hint: you can then use the reversal feature to generate the reverse journal items on the next day.
No verified information in OCA: Installation.
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.