e3fee2cf46
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
71 lines
2.2 KiB
ReStructuredText
71 lines
2.2 KiB
ReStructuredText
========================
|
|
How to create new taxes
|
|
========================
|
|
|
|
Odoo's tax engine is very flexible and support many different type of
|
|
taxes: value added taxes (VAT), eco-taxes, federal/states/city taxes, retention,
|
|
withholding taxes, etc. For most countries, your system is pre-configured with the
|
|
right taxes.
|
|
|
|
This section details how you can define new taxes for specific use cases.
|
|
|
|
* Go to :menuselection:`Accounting --> Configuration --> Taxes`. From this menu, you
|
|
get all the taxes you can use: sales taxes and purchase taxes.
|
|
|
|
.. image:: media/create01.png
|
|
:align: center
|
|
|
|
* Choose a scope: Sales, Purchase or None (e.g. deprecated tax).
|
|
|
|
* Select a computation method:
|
|
|
|
* **Fixed**: eco-taxes, etc.
|
|
|
|
* **Percentage of Price**: most common (e.g. 15% sales tax)
|
|
|
|
* **Percentage of Price Tax Included**: used in Brazil, etc.
|
|
|
|
* **Group of taxes**: allows to have a compound tax
|
|
|
|
.. image:: media/create02.png
|
|
:align: center
|
|
|
|
|
|
* If you use Odoo Accounting, set a tax account (i.e. where the tax journal item will be
|
|
posted). This field is optional, if you keep it empty, Odoo posts
|
|
the tax journal item in the income account.
|
|
|
|
.. tip::
|
|
If you want to avoid using a tax, you can not delete it because the tax
|
|
is probably used in several invoices. So, in order to avoid users to
|
|
continue using this tax, you should set the field *Tax Scope* to *None*.
|
|
|
|
.. note::
|
|
If you need more advanced tax mechanism, you can install the
|
|
module **account_tax_python** and you will be able to define new taxes
|
|
with Python code.
|
|
|
|
Advanced configuration
|
|
======================
|
|
|
|
* **Label on Invoices**: a short text on how you want this tax to be
|
|
printed on invoice line. For example, a tax named "15% on
|
|
Services" can have the following label on invoice "15%".
|
|
|
|
* **Tax Group**: defines where this tax is summed in the invoice footer.
|
|
All the tax belonging to the same tax group will be grouped on
|
|
the invoice footer. Examples of tax group: VAT, Retention.
|
|
|
|
* **Include in Analytic Cost**: the tax is counted as a cost and, thus,
|
|
generate an analytic entry if your invoice uses analytic
|
|
accounts.
|
|
|
|
* **Tags**: are used for custom reports. Usually, you can keep this field
|
|
empty.
|
|
|
|
|
|
.. seealso::
|
|
|
|
* :doc:`application`
|
|
* :doc:`tax_included`
|