This release is a pre-release and may not be stable for production use.
Account Cut-off Prepaid
This module allows you to easily compute the prepaid revenue and prepaid expenses and to generate the related cutoff journal items. It uses the Start Date and End Date fields of journal entries (copied from the same fields of invoice lines).
For example, if you have an insurance contrat for your company that run from April 1st 2013 to March 31st 2014, you will enter these dates as start and end dates on the supplier invoice line. If your fiscal year ends on December 31st 2013, 3 months of expenses are part of the 2014 fiscal year and should not be part of the 2013 fiscal year. So, thanks to this module, you will create a Prepaid Expense on December 31st 2013 and OpenERP 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.
Table of contents
Configuration
On the form view of the company, in the Configuration tab, 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 Prepaid Revenue,
the Default Account for Prepaid Expense.
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 items 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
Contributors
Alexis de Lattre <alexis.delattre@akretion.com>
Stéphane Bidoul <stephane.bidoul@acsone.eu>
Jim Hoefnagels <jim.hoefnagels@dynapps.be>
Maintainers
This module is maintained by the OCA.
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.
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.
1 maintainer
Metadata
1 maintainer
Release files for odoo12-addon-account-cutoff-prepaid 12.0.1.0.0.99.dev32
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo12_addon_account_cutoff_prepaid-12.0.1.0.0.99.dev32-py3-none-any.whl | Python 3 | none | any | Details for odoo12_addon_account_cutoff_prepaid-12.0.1.0.0.99.dev32-py3-none-any.whl |
Release files / odoo12_addon_account_cutoff_prepaid-12.0.1.0.0.99.dev32-py3-none-any.whl
| Download URL | odoo12_addon_account_cutoff_prepaid-12.0.1.0.0.99.dev32-py3-none-any.whl |
|---|---|
| Size | 241.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
439a9559df8268e895fcefb58d9406c1314717e16eb359838843301e1436fdf8
|
|
BLAKE2b-256 checksum How to use checksums |
09c8275b9e8230c02f0d757da89067cfcb1948b92fc0903bf67c7dae62bdf6ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for odoo12-addon-account-cutoff-prepaid 12.0.1.0.0.99.dev32
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.
