Skip to main content
Odoo Community Association

Account Cut-off Start End Dates

Beta License: AGPL-3 OCA/account-closing Translate me on Weblate Try me on Runboat

This module allows you to easily compute the prepaid revenue/expenses and also the revenue/expense accruals by using the Start Date and End Date fields of invoice lines/journal items.

For example, if you have an insurance contrat invoiced in April 2020 that run from April 1st 2020 to March 31st 2021, you will enter these dates as start and end dates on the supplier invoice line. If your fiscal year ends on December 31st 2020, 3 months of expenses are part of the 2021 fiscal year and should not be part of the 2020 fiscal year. So, thanks to this module, you will create a Prepaid Expense on December 31st 2020 and Odoo will identify this expense with the 3 months that are after the cut-off date and propose to generate the appropriate cut-off journal entry.

Another example: you have a UPS invoice dated January 5th 2021 that covers the shipments of December 2020. When you encode this vendor bill, set the start date as December 1st 2020 and the end date as December 31st 2020. Then, thanks to this module, you will create an Expense Accrual dated December 31st 2020 that will generate a cut-off journal entry that will “move” the UPS expense from 2021 to 2020.

Table of contents

Configuration

Please refer to the CONFIGURATION section of the README of the module account_cutoff_base.

Usage

To compute the prepaid revenue, go to the menu Accounting > Cut-offs > Prepaid 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 an end date after the cut-off date and, for each line, it will compute the prepaid revenue. 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 cut these prepaid revenue. Hint: you can then use the reversal feature to generate the reverse journal entry on the next day.

If you need to answer a question such as How much revenue did I already invoice for my next fiscal year ?, you will be interested by the forecast feature. For that, on the Prepaid Revenue form, click on the Forecast option and you will see 2 new fields: Start Date and End Date. Enter the start date and the end date of your next fiscal year and click on the button Re-Generate lines: you will see all the revenue that you already have in your source journals for that period.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Akretion

Contributors

Other credits

The migration of this module from 16.0 to 17.0 was financially supported by Camptocamp

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

Current maintainer:

alexis-via

This module is part of the OCA/account-closing project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Metadata

Release files for odoo-addon-account-cutoff-start-end-dates 18.0.1.1.0.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for odoo-addon-account-cutoff-start-end-dates 18.0.1.1.0.5
File Interpreter ABI Platform Actions
odoo_addon_account_cutoff_start_end_dates-18.0.1.1.0.5-py3-none-any.whl Python 3 none any Details for odoo_addon_account_cutoff_start_end_dates-18.0.1.1.0.5-py3-none-any.whl

Release files / odoo_addon_account_cutoff_start_end_dates-18.0.1.1.0.5-py3-none-any.whl

Download URL odoo_addon_account_cutoff_start_end_dates-18.0.1.1.0.5-py3-none-any.whl
Size 239.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2a36a638f8e26630271ecdf7a0fde3359588753d30574b86f8be3f536e1f3c07
BLAKE2b-256 checksum
How to use checksums
f9b6d8674464be6c2ef421a5388ef036bb5ca6b1fba0b3967e2aa60fb11d6bbb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.12.3

Security for odoo-addon-account-cutoff-start-end-dates 18.0.1.1.0.5

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

18.0.1.1.0.5 This release

1 release file No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page