$ 8.00
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Sales (sale_management) • Discuss (mail) |
| Lines of code | 155 |
| Technical Name |
se_all_in_one_hide_view_taxes |
| License | LGPL-3 |
| Website | https://sprinterp.com |
| Versions | 17.0 18.0 19.0 |
All in One Enterprise Tax Visibility & Layout Compliance Framework
Dynamically hide or show tax columns, totals matrices, and subtotal layouts across Sales, Purchase, Invoices, Bills, and Inventory Operations.
Key Module Highlights
All in One Hide Taxes (Sale/Purchase/Invoice/Bill/Inventory)
Standard Document View with Active Tax Elements
When opening an operational document, such as a **Sales Order (S00007)**, with the localized restriction parameters disabled, Odoo renders all tax computations as standard. The **"Taxes"** breakdown column remains visible inside the **Order Lines** spreadsheet grid, and the complete calculation matrix displaying individual tax group distributions is displayed at the bottom right.
Key Logic: By default, the custom hide_taxes state toggle field is
un-ticked, allowing standard QWeb template render nodes and backend XML collection arrays to
process and output compute values normally.
Standard QWeb PDF Report Layout with Taxes Printed
When executing a native print operation without restriction flags active, the generated outward document layout, such as the **Sales Order PDF (S00007)**, fully mirrors your standard database values. The document outputs individual row tax distribution percentages (`15%`) inside the main items spreadsheet grid, followed by an explicit tax group distribution row directly inside the summary tables block.
Key Logic: The system evaluates the report compilation template routines, finding the
active doc.hide_taxes state flag set to False, which permits the
XML architecture's core `th_taxes` and subtotal groups to render seamlessly on the generated
page.
Dynamic Tax Suppression inside Backend Sales Order Form View
When an authorized user toggles the custom integrated "Hide Taxes" boolean widget to active on a document like **Sales Order (S00007)**, Odoo instantly triggers a runtime visibility adjustment. The **"Taxes"** selection column is completely stripped from the **Order Lines** list layout, and the tax distribution rows vanish from the bottom-right breakdown engine, displaying a polished, clean subtotal balance grid.
Key Logic: The view engine evaluates the custom XPath rules, driving column_invisible="parent.hide_taxes"
to hide list attributes and passing custom dictionary parameters ({'hide_taxes':
hide_taxes}) into the backend _compute_tax_totals() routine to securely
mask calculation rows.
Compliant PDF Report Execution with Hided Tax Rows
When printing the **Sales Order PDF (S00007)** with the concealment flag enabled, the custom QWeb extension architecture triggers. The outward customer-facing document strips the **"Taxes"** header cell and related row parameters seamlessly from the product details block, outputting only clean calculations containing the Untaxed Amount and the absolute Total balance symmetrically.
Key Logic: The custom print template engine catches the doc.hide_taxes
state flag condition via advanced template directives, dynamically enforcing conditional
exclusions (t-if="not doc.hide_taxes") on report compilation nodes during
binary PDF generation layouts.
Customer Invoice Dashboard Form Layout with Active Taxes
When navigating to the **Invoicing** application workspace and editing a customer invoice record like **INV/2026/00005**, the default operational layout preserves full visibility parameters. With the local **"Hide Tax"** toggle deactivated, the **"Taxes"** distribution column outputs inline mappings within the **Invoice Lines** matrix grid, and the bottom-right accounting distribution rows render detailed financial calculation entries.
Key Logic: The layout logic evaluates the custom inherited account.move
architecture. Since the boolean state field resolves to False, the core system
allows the native subtotal breakdown fields and multi-tax allocation cells to draw normally
on your dashboard.
Standard Invoice PDF Printout with Tax Breakdown Columns
When compiling the document into an outward PDF report, such as the **PROFORMA Invoice (INV/2026/00005)** with restriction overrides disabled, the standard QWeb template pipeline executes natively. The final generated invoice printout explicitly presents individual item tax values (`15%`) inside the products table matrix, keeping data rows fully synchronized with Odoo's baseline architectural configuration sheets.
Key Logic: The reporting infrastructure checks the active o.hide_tax
flag values. Since the condition returns False, the template layer safely
prints out the native th_taxes cells and fiscal distribution table structures
onto the document canvas.
Dynamic Invoice Grid Modification via Hide Tax Activation
Activating the localized **"Hide Tax"** boolean toggle on a customer invoice or vendor bill immediately alters the active record workspace views. The interface seamlessly eliminates the dedicated **"Taxes"** column from the active **Invoice Lines** spreadsheet tab, clean-formatting your financial documentation layout while keeping operational calculations structurally accurate.
Key Logic: The view structure leverages native XPath modifiers driving the column_invisible="parent.hide_tax"
property wrapper. This suppresses row cells on demand without disturbing ledger posting
routines or financial journal entry validation schemas.
Clean Proforma Invoice PDF Generation with Suppressed Tax Groups
When compiling the **PROFORMA Invoice (INV/2026/00005)** with the restriction switch active, the overridden reporting layer strips the document layout clean. The final printed PDF perfectly omits the **"Taxes"** line items column and suppresses any intermediate tax group calculations at the footer, outputting a highly professional breakdown showing only the Subtotal and Total layers.
Key Logic: The reporting framework utilizes standard QWeb inheritance on account.report_invoice_document.
It forces conditional assertions (t-if="not o.hide_tax") straight onto row
nodes, bypassing traditional accounting distributions dynamically on render execution.
Vendor Bill Operational Workspace with Unrestricted Tax Mapping
The suppression framework applies symmetrically to the purchase ledger ecosystem. When editing a standard vendor bill like **BILL/2025/04/0001** with the localized **"Hide Tax"** parameter turned off, Odoo loads full visibility parameters. The **"Taxes"** distribution column prints out baseline values inside the invoice lines item sub-grid, and the explicit tax distribution rows display full fiscal calculations at the footer.
Key Logic: Since Odoo maps customer invoices and supplier vendor bills under the same
unified account.move structural data model, the toggle status evaluates
identically across both workflows, ensuring flawless out-of-the-box data integrity.
Standard Vendor Bill PDF Printout Layout with Fiscal Tax Fields
When compiling purchase-side accounting documents into physical prints with the restriction overrides disabled, the native QWeb engine runs standard rules. The printed **PROFORMA Vendor Bill (BILL/2025/04/0001)** explicitly retains the individual item tax rows (`15%`) inside the products data matrix and prints full financial group distributions at the summary footer.
Key Logic: The document compiler relies directly on the underlying account.report_invoice_document
template structures. Since the suppression boolean evaluates to False, the XML
layout prints out baseline data lines uninterrupted.
Dynamic Vendor Bill Grid Modification via Hide Tax Activation
Activating the integrated **"Hide Tax"** boolean toggle on a vendor bill workspace immediately alters the active document layout. The interface seamlessly eliminates the dedicated **"Taxes"** column from the active **Invoice Lines** spreadsheet grid on the fly, clean-formatting your supplier purchase logs while keeping baseline total calculations structurally accurate.
Key Logic: The view structure leverages the inherited account.move view
layout rules, driving the column_invisible="parent.hide_tax" property wrapper
to hide supplier-side row elements on demand without disturbing the underlying journal
entries.
Clean Vendor Bill PDF Generation with Suppressed Tax Groups
When compiling the **PROFORMA Vendor Bill (BILL/2025/04/0001)** with the restriction switch active, the overridden reporting layer strips the document layout clean. The final printed PDF perfectly omits the **"Taxes"** line items column and suppresses any intermediate tax group calculations at the footer, outputting a highly professional breakdown showing only the Subtotal and Total layers.
Key Logic: The reporting framework utilizes standard QWeb inheritance on account.report_invoice_document.
It forces conditional assertions (t-if="not o.hide_tax") straight onto row
nodes, bypassing traditional accounting distributions dynamically on render execution.
Key Features & Capabilities
Empower your document layout compliance workflows with dynamic tax line concealment and native tax totals suppression matrix engines in Odoo.
Sales Column Suppression
Dynamically hides the tax column from sale order lines grid view and alters the main total breakdown calculations layout on a simple switch toggle.
Procurement Grid Polish
Alters standard purchase order forms by masking incoming line items tax fields while modifying compute total records without breaking base ledgers.
Invoice Subtotal Cleanup
Safely controls customer invoices or vendor bills layout visibilities by omitting tax breakdowns from lists and wiping out subtotal calculation groups.
Inventory Flow Masking
Injects conditional concealment hooks inside delivery picking slips, ensuring logistics workers or transporters view only item details.
QWeb Document Stripper
Overrides core corporate PDF templates (Invoices, Quotations, POs, and Delivery Slips) to hide tax headers and row data fields automatically.
Parametric System Storage
Utilizes custom system configurations via ir.config_parameter settings,
enabling default rules to map across multi-model layouts at runtime.
Need Any Help?
Installation, Configuration & Bug Fixing support from our experts.
© 2017 SprintERP Technologies. All Rights Reserved.
Please log in to comment on this module