---
title: "Odoo 19.4 Tax-Included and Tax-Excluded Switch"
description: "Understand Odoo 19.4's document-level tax price switch, how it relates to tax configuration and what businesses should verify before use."
canonical_url: "https://websitefuze.com/blog/odoo-19-4-tax-included-tax-excluded-switch"
last_updated: "2026-07-25T09:01:16.976Z"
keywords: ["Odoo 19.4", "Odoo tax included", "Odoo tax excluded", "Odoo sales orders", "Odoo purchase orders", "Odoo invoices", "Odoo website tax display", "Odoo B2B B2C"]
---

# Odoo 19.4 Adds Document-Level Tax-Included and Tax-Excluded Pricing

Published: 2026-07-25

Category: Odoo Updates

Understand Odoo 19.4's document-level tax price switch, how it relates to tax configuration and what businesses should verify before use.

Odoo 19.4 adds a control for switching between tax-included and tax-excluded prices on sales orders, purchase orders and invoices. This places the selection on the transaction document instead of relying solely on website settings or the configuration of individual taxes.([Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes))

Individual taxes can be configured to override the document-level behaviour. The new switch therefore works alongside existing tax rules rather than replacing them. When checking a transaction, organisations need to consider both the document selection and any override configured for the applicable tax.([Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes))

## What the new switch covers

The confirmed scope covers sales orders, purchase orders and invoices, making the control relevant to customer sales, supplier purchasing and invoicing workflows. The release information does not confirm an equivalent switch for other Odoo interfaces, so its availability elsewhere should not be assumed.([Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes))

The feature determines whether prices on a supported document are tax included or tax excluded. It is separate from Odoo's underlying tax calculation process. Odoo applies taxes to individual sales, purchase, invoice, bill and point-of-sale lines, then calculates the tax amounts and corresponding accounting entries.([Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes);[Odoo 19.0 Docs: Accounting Taxes](https://www.odoo.com/documentation/19.0/applications/finance/accounting/taxes.html))

This distinction separates document-level price treatment from line-level tax calculation. Selecting a mode on an order or invoice does not remove the need to configure the taxes applied to its lines. The tax setup continues to determine the amounts Odoo calculates and the accounting entries it creates.([Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes);[Odoo 19.0 Docs: Accounting Taxes](https://www.odoo.com/documentation/19.0/applications/finance/accounting/taxes.html))

## Individual taxes can override the selection

Odoo 19.4 allows individual taxes to override the document-level behaviour. A user may select tax-included or tax-excluded pricing for a document while the configuration of a particular tax takes precedence. Testing only the visible document selection may therefore miss a different result caused by an override.([Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes))

Rollout testing should cover each tax used in the relevant sales and purchasing workflows. Review the tax on each line, the document totals and the resulting accounting treatment. These checks cover the interaction between the new document-level control and Odoo's existing calculation of line taxes, tax amounts and accounting entries.([Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes);[Odoo 19.0 Docs: Accounting Taxes](https://www.odoo.com/documentation/19.0/applications/finance/accounting/taxes.html))

The release notes confirm that overrides are available, but the supplied information does not specify their detailed settings, default values or order of precedence. Administrators should verify these points in the deployed Odoo 19.4 environment before documenting procedures or assigning responsibility for changing the selection.([Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes))

## Website tax display remains separate

Odoo's eCommerce tax display is configured per website. Separate websites can therefore show prices with tax included or tax excluded. This website setting is distinct from the Odoo 19.4 control available on sales orders, purchase orders and invoices.([Odoo 19.0 Docs: eCommerce Prices](https://www.odoo.com/documentation/19.0/applications/websites/ecommerce/configuration/prices.html);[Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes))

Changing a transaction document to tax-included or tax-excluded pricing should not be assumed to alter the website presentation. The sources describe separate controls: website configuration governs online display, while the Odoo 19.4 feature applies to supported transaction documents.([Odoo 19.0 Docs: eCommerce Prices](https://www.odoo.com/documentation/19.0/applications/websites/ecommerce/configuration/prices.html);[Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes))

This separation matters when an online transaction becomes a sales order or invoice. Testing should compare the price shown to the customer on the website with the presentation and tax calculation on the resulting document. Website display alone does not establish that the document-level selection and tax configuration are correct.([Odoo 19.0 Docs: eCommerce Prices](https://www.odoo.com/documentation/19.0/applications/websites/ecommerce/configuration/prices.html);[Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes);[Odoo 19.0 Docs: Accounting Taxes](https://www.odoo.com/documentation/19.0/applications/finance/accounting/taxes.html))

## B2B and B2C website structure

Odoo's B2B and B2C documentation recommends separate websites when a business requires materially different customer access and pricing behaviour. Because tax display is configured for each website, separate sites can provide different online tax presentations for distinct customer groups.([Odoo 19.0 Docs: eCommerce B2b B2c](https://www.odoo.com/documentation/19.0/applications/websites/ecommerce/configuration/b2b_b2c.html);[Odoo 19.0 Docs: eCommerce Prices](https://www.odoo.com/documentation/19.0/applications/websites/ecommerce/configuration/prices.html))

The document switch does not remove that website architecture consideration. It controls pricing on sales orders, purchase orders and invoices, while separate websites remain Odoo's documented approach when B2B and B2C operations require materially different online access and pricing behaviour.([Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes);[Odoo 19.0 Docs: eCommerce B2b B2c](https://www.odoo.com/documentation/19.0/applications/websites/ecommerce/configuration/b2b_b2c.html))

A business serving consumers and trade customers should decide separately how each website displays prices and how internal transaction documents handle tax inclusion. The decisions may align, but they operate at different levels. A document-level setting is not a substitute for assessing the required website structure and per-website tax display.([Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes);[Odoo 19.0 Docs: eCommerce Prices](https://www.odoo.com/documentation/19.0/applications/websites/ecommerce/configuration/prices.html);[Odoo 19.0 Docs: eCommerce B2b B2c](https://www.odoo.com/documentation/19.0/applications/websites/ecommerce/configuration/b2b_b2c.html))

## What to verify before rollout

First, confirm that the control appears in every required sales order, purchase order and invoice workflow in the deployed Odoo 19.4 environment. The release notes identify the supported document categories, but the supplied information does not specify access rights, interface placement or whether customised forms need adjustment.([Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes))

Second, identify every tax configured to override document-level behaviour. Test each one in the transaction types where it is used. Check the tax attached to each line, the computed amount and the accounting entries generated by Odoo instead of relying only on the displayed unit price or document total.([Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes);[Odoo 19.0 Docs: Accounting Taxes](https://www.odoo.com/documentation/19.0/applications/finance/accounting/taxes.html))

Third, review each website independently. Odoo configures tax display per website, so verifying one site does not confirm another site's settings. Where separate B2B and B2C websites are used, test the intended price presentation and customer access behaviour on each site.([Odoo 19.0 Docs: eCommerce Prices](https://www.odoo.com/documentation/19.0/applications/websites/ecommerce/configuration/prices.html);[Odoo 19.0 Docs: eCommerce B2b B2c](https://www.odoo.com/documentation/19.0/applications/websites/ecommerce/configuration/b2b_b2c.html))

Fourth, test the complete transaction path from website price display to the relevant sales order and invoice. For purchasing, test purchase orders and the resulting accounting treatment under the applicable tax setup. This checks the boundary between website presentation, the document-level selection and Odoo's line-level tax calculation.([Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes);[Odoo 19.0 Docs: eCommerce Prices](https://www.odoo.com/documentation/19.0/applications/websites/ecommerce/configuration/prices.html);[Odoo 19.0 Docs: Accounting Taxes](https://www.odoo.com/documentation/19.0/applications/finance/accounting/taxes.html))

## Limits of the available information

The supplied sources confirm the new switch, its three supported document categories and the ability of individual taxes to override it. They do not specify migration behaviour for existing documents, the default selection after an upgrade, user permission controls, localisation-specific results or the treatment of customised modules.([Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes))

These points require implementation testing rather than assumptions based on the feature announcement. Before using the control in operational workflows, organisations should validate their taxes, websites, transaction documents, templates and accounting results in the target Odoo 19.4 environment.([Odoo 19.4 Release Notes](https://www.odoo.com/odoo-19-4-release-notes);[Odoo 19.0 Docs: eCommerce Prices](https://www.odoo.com/documentation/19.0/applications/websites/ecommerce/configuration/prices.html);[Odoo 19.0 Docs: Accounting Taxes](https://www.odoo.com/documentation/19.0/applications/finance/accounting/taxes.html))