Account Move Post Block
This module allows you to block the post of a journal entry when a Post Block Reason has been provided. The moves will be waiting for post by a Manager.
Table of contents
Configuration
Go to ‘Invoicing / Configuration / Invoicing / Purchase Approval Block Reasons’ and create the blocking reasons as needed, providing a name and a description. A field ‘Active’ allows you to deactivate the reason if you do not plan to use it any more.
Assign the security group ‘Release Journal Entry with post block’ to users that should be able to release the block. Users in group ‘Invoicing / Billing Administrator’ are by default assigned to this group.
Usage
Set the Journal Entry Post Block
Go to ‘Invoicing’ and go to create an Invoice or a Bill.
Indicate the post block reason (found in the ‘Other Info’ tab).
Search existing Journal Entries
There is a filter ‘Blocked’ to search for moves that are blocked for post. It is also possible to search journal entries with a specific block reason.
Confirm the Journal Entry
Press the button ‘Post’. If there’s a post block, you will need to request a Billing Manager release the post block in order to approve it.
Release the entry post block
While the Journal Entry is in draft, members of security group ‘Release Journal Entry with post block’ can see a button ‘Release Post Block’ and click on it. From this point and on, anyone seeing that Journal Entry will be able to validate it.
Notifications to followers
Followers of the Journal entry receive notifications when a post block has been set or released.
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.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Miquel Raïch <miquel.raich@forgeflow.com>
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-invoicing 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 odoo13-addon-account-move-post-block 13.0.1.0.2
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 |
|---|---|---|---|---|
| odoo13_addon_account_move_post_block-13.0.1.0.2-py3-none-any.whl | Python 3 | none | any | Details for odoo13_addon_account_move_post_block-13.0.1.0.2-py3-none-any.whl |
Release files / odoo13_addon_account_move_post_block-13.0.1.0.2-py3-none-any.whl
| Download URL | odoo13_addon_account_move_post_block-13.0.1.0.2-py3-none-any.whl |
|---|---|
| Size | 32.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
faae4517fbf7a488cf0d224d210263d044912e454e8fd109cd0116485b77b318
|
|
BLAKE2b-256 checksum How to use checksums |
f28f65cffde02d0265172ecce089051c38010304c7a80521f1180db206ba1492
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.1 setuptools/51.0.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.7.3
|
Security for odoo13-addon-account-move-post-block 13.0.1.0.2
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.
