Account Cutoff Accrual Dates
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).
Configuration
On the Accounting configuration page available via the menu Accounting > 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
To compute the accrued revenue, go to the menu Accounting > 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.
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 smashing it by providing a detailed and welcomed feedback.
Credits
Contributors
Alexis de Lattre <alexis.delattre@akretion.com>
Maintainer
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.
To contribute to this module, please visit https://odoo-community.org.
1 maintainer
Metadata
1 maintainer
Release files for odoo10-addon-account-cutoff-accrual-dates 10.0.1.1.0
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 |
|---|---|---|---|---|
| odoo10_addon_account_cutoff_accrual_dates-10.0.1.1.0-py2-none-any.whl | Python 2 | none | any | Details for odoo10_addon_account_cutoff_accrual_dates-10.0.1.1.0-py2-none-any.whl |
Release files / odoo10_addon_account_cutoff_accrual_dates-10.0.1.1.0-py2-none-any.whl
| Download URL | odoo10_addon_account_cutoff_accrual_dates-10.0.1.1.0-py2-none-any.whl |
|---|---|
| Size | 10.9 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
31ce649828bd9024f0d00c10bf5180eb4d11bbdf43b1686a21bac1fc9f1710d3
|
|
BLAKE2b-256 checksum How to use checksums |
8e12fc00707dae9fd1ee213f5653d7d073cfa6a8c72de2d92e0d11a09f090e11
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for odoo10-addon-account-cutoff-accrual-dates 10.0.1.1.0
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.
