Skip to main content

Cutoffs based on start/end dates

Project description

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.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

File details

Details for the file odoo_addon_account_cutoff_start_end_dates-17.0.1.1.0.2-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo_addon_account_cutoff_start_end_dates-17.0.1.1.0.2-py3-none-any.whl
Algorithm Hash digest
SHA256 21982b12b7a72d3316420c261066cdd202ead02dd6cdaf8b410e79700755dda8
MD5 91e108dcf7c143b7b5e4bca38dd23a17
BLAKE2b-256 d029f68cf6a251916c8549fa5a381fe511b13bff243d380f85377d426d7e33db

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page