| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 210 |
| Technical Name |
nspl_journal_entry_approval |
| License | OPL-1 |
| Website | https://namahsoftech.com/ |
| Versions | 17.0 18.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 210 |
| Technical Name |
nspl_journal_entry_approval |
| License | OPL-1 |
| Website | https://namahsoftech.com/ |
| Versions | 17.0 18.0 |
Journal Entry Verification
This module adds a two-step verification for journal entries. When the "Verification Required" option is enabled at the journal level, entries must be approved by an authorized user before posting.
Community
Enterprise
Odoo.sh
Industry-Specific Modules Designed to Fit Your Needs
Take control with smart customizable Odoo dashboards built to deliver insights
and grow with
your business.
Two-step verification for Journal Entries
Only authorized users can approve entries
Two-step verification for Payments
Only authorized users can approve payments
Navigate to: Invoicing → Configuration → Accounting → Journals.
select a journal with "Verification Required" enabled, a Submit for Approval button will appear on the entry.
To assign this access, go to: Settings → Users & Companies → Users, and update the user’s access rights accordingly.
Once submitted for approval, the entry status will change to "Waiting for Approval".
Authorized users will see an Approve button on the journal entry. Once approved, the entry status will change to Posted.
You can view who approved the entry and when it was approved.
In Payments, if the selected journal has "Verification Required" enabled, a Submit for Approval button will be displayed.
After submitting for approval, the payment status will change to Waiting for Approval. Once approved, the payment will be marked as Posted.
When the Approve button is clicked, the payment/journal entry is marked as approved by the logged-in user, and the approval date is set to today’s date.
What’s
New in Journal Entry Verification
-
Journal entries require approval before they can be posted.
-
Payments also need to be approved before posting.
-
Only users with the proper approval rights can approve journal entries and payments.
-
The module records who approved the entry or payment and the date of approval, which can be viewed later.
Your one-stop solution
We are available 24/7 for your service. Contact us today!
+91-9427526501
support@namahsoftech.com
We will provide FREE 30 days support for any doubt, queries, and bug fixing (excluding data recovery) or any type of issues related to this module. This is applicable from the date of purchase.
Namah Softech
Namah Softech Odoo Services
Empower your business with Odoo Best Dashboard tools—customized, insightful, and ready to scale.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module