Invoice Zero Amount Blocker
Enforce Strict Financial Controls & Eliminate Empty Journal Entries in Odoo 19
Prevent accountants from accidentally confirming zero-value documents.
A bulletproof operational guardrail for Customer Invoices, Vendor Bills, and Credit Notes.
The Risk: Dirty Ledgers & Audit Inconsistencies
By default, Odoo allows users to confirm financial documents with a total amount of zero. Whether caused by a missing price list, an unpopulated order line, or a simple human typo, posting these transactions creates empty, valueless journal entries. This litters your General Ledger, skews transaction counts, and complicates end-of-month financial audits. Finding and reversing these posted moves manually wastes critical administrative hours.
Comprehensive Invoice Guardrails
Simple configuration, airtight protection, and smart exception management built natively into Odoo Accounting.
Airtight Posting Block
Intercepts the invoice confirmation pipeline. If the total amount resolves to 0.00, it throws a clear validation pop-up error, halting the creation of erroneous accounting entries on the spot.
Controlled Manager Override
Need to pass a zero-amount voucher intentionally? Users within the authorized Zero Amount Invoice Manager security group can bypass the block by checking an override toggle.
Mandatory Reason Logging
Security requires accountability. Managers cannot override blindlyâthey must input a justified reason, which the module instantly commits directly into the invoice chatter audit log.
Global Settings Activation
Multi-company friendly architecture. Toggle the zero-amount operational rule sets on or off instantly via a checkbox under core Accounting/Invoicing â Configuration â Settings.
Full Document Model Coverage
Protects all directional accounting variations out of the box (`account.move` types):
How to Configure & Use
| 1. | Navigate to Accounting > Configuration > Settings. |
| 2. | Locate the Zero Amount Invoice Control group and check the box to enable company-wide restriction. |
| 3. | Go to Settings > Users > Groups to grant trusted supervisors the "Zero Amount Invoice Manager" clearance level. |
| 4. | Standard operators trying to post an empty invoice will now see validation exceptions, keeping your journals clean. |
User Interface & Functional Flow
Seamless integration that looks completely native to the standard Odoo enterprise layout.
Developed with by SyncSoft LLC
Need further customization on mail flows, priority scheduling, or customized email templates?
We are here to support your team!
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 126 |
| Technical Name |
invoice_prevent_zero_payment |
| License | OPL-1 |
| Website | https://pxfox.com |
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