[FIX] support: noindex what_can_i_expect.rst

The content of this page moved to the support
page at https://www.odoo.com/help. The page hosted
in the documentation repository is planned for
deletion. In the meanwhile the page should be
excluded from web search results.

Makefile

@@ -84,5 +84,14 @@ static: $(HTML_BUILD_DIR)/_static/style.css
 	cp -r extensions/odoo_theme/static/* $(HTML_BUILD_DIR)/_static/
 	cp -r static/* $(HTML_BUILD_DIR)/_static/
 
+# Called by runbot for the ci/documentation_guideline check.
 test:
 	@python tests/main.py $(SOURCE_DIR)/administration $(SOURCE_DIR)/applications $(SOURCE_DIR)/contributing $(SOURCE_DIR)/developer $(SOURCE_DIR)/services redirects
+
+# Similar as `test`, but called only manually by content reviewers to trigger extra checks.
+review:
+	@read -p "Enter content path: " path; read -p "Enter max line length (default: 100): " line_length; \
+	if [ -z "$$path" ]; then echo "Error: Path cannot be empty"; exit 1; fi; \
+	if [ -z "$$line_length" ]; then line_length=100; fi; \
+	export REVIEW=1; \
+	python tests/main.py --max-line-length=$$line_length $(SOURCE_DIR)/$$path

conf.py

@@ -188,6 +188,7 @@ sphinx.transforms.i18n.docname_to_domain = (
 # is populated. If a version is passed to `versions` but is not listed here, it will not be shown.
 versions_names = {
     'master': "Master",
+    'saas-16.4': "Odoo Online",
     'saas-16.3': "Odoo Online",
     'saas-16.2': "Odoo Online",
     'saas-16.1': "Odoo Online",

content/administration/maintain/domain_names.rst

@@ -115,7 +115,7 @@ name with your website <domain-name/website-map>`.
 .. note::
    - Free domain names are also available for free Odoo Online databases (if you installed one app
      only, for example). In this case, Odoo reviews your request and your website to avoid abuse.
-     This process may take up to three days.
+     This process can take several days due to the success of the offer.
    - This is not available for Odoo.sh databases yet.
 
 .. _domain-name/odoo-manage:

content/administration/maintain/supported_versions.rst

@@ -33,24 +33,30 @@ This matrix shows the support status of every version.
      - On-Premise
      - Release date
      - End of support
-   * - Odoo saas~16.3
+   * - Odoo saas~16.4
      - |green|
      - N/A
      - N/A
+     - August 2023
+     -
+   * - Odoo saas~16.3
+     - |red|
+     - N/A
+     - N/A
      - June 2023
-     - September 2023 (planned)
+     -
    * - Odoo saas~16.2
-     - |green|
+     - |red|
      - N/A
      - N/A
      - March 2023
-     - July 2023 (planned)
+     -
    * - Odoo saas~16.1
      - |red|
      - N/A
      - N/A
      - February 2023
-     - April 2023
+     -
    * - **Odoo 16.0**
      - |green|
      - |green|
@@ -80,79 +86,13 @@ This matrix shows the support status of every version.
      - |green|
      - |green|
      - October 2020
-     - October 2023 (planned)
+     - November 2023 (planned)
    * - **Odoo 13.0**
      - |red|
      - |red|
      - |red|
      - October 2019
      - October 2022
-   * - Odoo saas~12.3
-     - |red|
-     - N/A
-     - N/A
-     - August 2019
-     -
-   * - **Odoo 12.0**
-     - |red|
-     - |red|
-     - |red|
-     - October 2018
-     - October 2021
-   * - Odoo saas~11.3
-     - |red|
-     - N/A
-     - N/A
-     - April 2018
-     -
-   * - **Odoo 11.0**
-     - |red|
-     - |red|
-     - |red|
-     - October 2017
-     - October 2020
-   * - Odoo 10.saas~15
-     - |red|
-     - N/A
-     - N/A
-     - March 2017
-     -
-   * - Odoo 10.saas~14
-     - |red|
-     - N/A
-     - N/A
-     - January 2017
-     -
-   * - **Odoo 10.0**
-     - |red|
-     - |red|
-     - |red|
-     - October 2016
-     - October 2019
-   * - Odoo 9.saas~11
-     - |red|
-     - N/A
-     - N/A
-     - May 2016
-     -
-   * - **Odoo 9.0**
-     - |red|
-     - N/A
-     - |red|
-     - October 2015
-     - October 2018
-   * - Odoo 8.saas~6
-     - |red|
-     - N/A
-     - N/A
-     - February 2015
-     -
-   * - **Odoo 8.0**
-     - |red|
-     - N/A
-     - |red|
-     - September 2014
-     - October 2017
 
 .. note::
 
@@ -175,8 +115,10 @@ This matrix shows the support status of every version.
 I run an older version of Odoo/OpenERP/TinyERP
 ==============================================
 
-OpenERP 7.0, 6.1, 6.0 and 5.0 is not supported anymore, on any platform.
+Odoo 12.0, 11.0, 10.0, 9.0, and 8.0 are not supported anymore, on any platform.
 
-TinyERP 4.0, 3.0, 2.0 and 1.0 is not supported anymore, on any platform.
+OpenERP 7.0, 6.1, 6.0 and 5.0 are not supported anymore, on any platform.
+
+TinyERP 4.0, 3.0, 2.0 and 1.0 are not supported anymore, on any platform.
 
 Even though we don't support older versions, you can always `upgrade from any version <https://upgrade.odoo.com/>`_.

content/applications/finance/fiscal_localizations.rst

@@ -68,8 +68,7 @@ available on Odoo.
 - Canada - Accounting
 - :doc:`Chile - Accounting <fiscal_localizations/chile>`
 - China - Accounting
-- :doc:`Colombia - Accounting <fiscal_localizations/colombia>` (:doc:`doc in Spanish
-  <fiscal_localizations/colombia_ES>`)
+- :doc:`Colombia - Accounting <fiscal_localizations/colombia>`
 - Costa Rica - Accounting
 - Croatia - Accounting (RRIF 2012)
 - Denmark - Accounting
@@ -135,7 +134,6 @@ available on Odoo.
    fiscal_localizations/belgium
    fiscal_localizations/chile
    fiscal_localizations/colombia
-   fiscal_localizations/colombia_ES
    fiscal_localizations/france
    fiscal_localizations/germany
    fiscal_localizations/indonesia

content/applications/finance/fiscal_localizations/colombia.rst

@@ -2,85 +2,86 @@
 Colombia
 ========
 
-Webinars
-========
+The following documentation covers the Colombian localization modules and their basic concepts to
+understand, implement, and use Colombian localization in Odoo.
 
-Below you can find videos with a general description of the localization, and how to configure it.
+- Configure Master Data for Colombia
+- Use and configure Electronic Invoicing in Odoo for Colombia.
+- :ref:`Invoice creation <colombia/invoice-creation>` and :ref:`validation
+  <colombia/invoice-validation>`
+- :ref:`Reception of legal XML and PDF <colombia/invoice-xml>`
+- :ref:`Avoid common mistakes <colombia/common-errors>`
+- :ref:`Financial reports <colombia/reports>`
 
-- `VIDEO WEBINAR OF A COMPLETE DEMO <https://youtu.be/BOzucXRUZDE>`_.
+.. seealso::
+   `Smart Tutorial - Localización de Colombia
+   <https://www.odoo.com/slides/smart-tutorial-localizacion-de-colombia-132>`_
 
-Introduction
-============
-
-Electronic invoicing for Colombia is available from Odoo 12 and
-requires the next modules:
-
-#. **l10n_co**: All the basic data to manage the accounting module,
-   contains the default setup for: chart of accounts, taxes,
-   retentions, identification document types
-#. **l10n_co_edi**: This module includes all the extra fields that are
-   required for the Integration with Carvajal and generate the
-   electronic invoice, based on the DIAN legal requirements.
-
-Workflow
-========
-
-.. image:: colombia/colombia01.png
-   :align: center
+.. _colombia/configuration:
 
 Configuration
 =============
 
-Install the Colombian localization modules
-------------------------------------------
+Modules installation
+--------------------
 
-To :ref:`install <general/install>` the modules, go to :menuselection:`Apps`, remove the *Apps*
-filter and search for "Colombia". Then click on *Install* for the first two modules.
+:ref:`Install <general/install>` the following modules to get all the features of the Colombian
+localization:
 
-.. image:: colombia/colombia02.png
-   :align: center
+.. list-table::
+   :header-rows: 1
+   :widths: 25 25 50
+
+   * - Name
+     - Technical name
+     - Description
+   * - :guilabel:`Colombia - Accounting`
+     - `l10n_co`
+     - Default :ref:`fiscal localization package <fiscal_localizations/packages>`
+   * - :guilabel:`Electronic invoicing for Colombia with Carvajal`
+     - `l10n_co_edi`
+     - Carvajal e-invoicing integration
+   * - :guilabel:`Colombian - Point of Sale`
+     - `l10n_co_pos`
+     - Point of Sale
+   * - :guilabel:`Colombian - Accounting Reports`
+     - `l10n_co_reports`
+     - Colombian reports
 
 Configure credentials for Carvajal web service
 ----------------------------------------------
 
-Once that the modules are installed, in order to be able to connect
-with Carvajal Web Service, it's necessary to configure the user
-and credentials, this information will be provided by Carvajal.
+Once the modules are installed, the user credentials need to be configured in order to connect with
+Carvajal Web Service. First, navigate to :menuselection:`Accounting --> Configuration --> Settings`
+and look for the :guilabel:`Colombian Electronic Invoice` section. Then, fill in the required
+configuration information provided by Carvajal.
 
-Go to :menuselection:`Accounting --> Configuration --> Settings` and
-look for the *Colombian Electronic Invoice* section.
+.. image:: colombia/carvajal-credential-config.png
+   :alt: Configure credentials for Carvajal web service in Odoo.
 
-.. image:: colombia/colombia03.png
-   :align: center
+Check the :guilabel:`Test mode` checkbox to connect with the Carvajal testing environment. This
+allows users to test the complete workflow and integration with the :abbr:`CEN (Centro Electrónico
+de Negocios)` Financiero portal, which is accessible here:
 
-Using the Testing mode it is possible to connect with a Carvajal
-testing environment. This allows users to test the complete workflow
-and integration with the CEN Financiero portal, which is accessible
-here:
+- `CTS (Carvajal T&S) <https://cenflab.cen.biz/site/>`_.
+- `CSC (Carvajal Servicios de Comunicación) <https://web-stage.facturacarvajal.com/>`_.
 
-CTS (Carvajal T&S)
-  https://cenflab.cen.biz/site/
+:abbr:`CSC (Carvajal Servicios de Comunicación)` is the default for new databases.
 
-CSC (Carvajal Servicios de Comunicación)
-  https://web-stage.facturacarvajal.com/
+Once Odoo and Carvajal are fully configured and ready for production, the testing environment can be
+disabled by unchecking the :guilabel:`Test mode` checkbox.
 
-CSC is the default for new databases.
+Configure report data
+---------------------
 
-Once that Odoo and Carvajal are fully configured and ready for
-production the testing environment can be disabled.
+Report data can be defined for the fiscal section and the bank information in the PDF as part of the
+configurable information that is sent in the XML.
 
-Configure your report data
---------------------------
+Navigate to :menuselection:`Accounting --> Configuration --> Settings` and look for the
+:guilabel:`Colombian Electronic Invoice` section.
 
-As part of the configurable information that is sent in the XML, you
-can define the data for the fiscal section and the bank information in
-the PDF.
-
-Go to :menuselection:`Accounting --> Configuration --> Settings` and
-look for the *Colombian Electronic Invoice* section.
-
-.. image:: colombia/colombia04.png
-   :align: center
+.. image:: colombia/report-config.png
+   :alt: Configure the report data in Odoo.
 
 Configure data required in the XML
 ----------------------------------
@@ -88,174 +89,181 @@ Configure data required in the XML
 Partner
 ~~~~~~~
 
+Configure the identification number and fiscal structure.
+
 Identification
 **************
 
-As part of the Colombian Localization, the document types defined by
-the DIAN are now available on the Partner form. Colombian partners
-have to have their identification number and document type set:
+As part of the Colombian Localization, the document types defined by the :abbr:`DIAN (Dirección de
+Impuestos y Aduanas Nacionales)` are now available on the Partner form. Colombian partners have to
+have their identification number (:guilabel:`VAT`) and :guilabel:`Document Type` set:
 
-.. image:: colombia/colombia05.png
-   :align: center
+.. image:: colombia/partner-rut-doc-type.png
+   :alt: The document type of RUT set in Odoo.
 
-.. tip:: When the document type is RUT the identification number needs
-   to be configured in Odoo including the verification digit, Odoo
-   will split this number when the data to the third party vendor is
-   sent.
+.. tip::
+   When the :guilabel:`Document Type` is `RUT`, the identification number needs to be configured in
+   Odoo, including the verification digit, Odoo will split this number when the data to the
+   third-party vendor is sent.
 
 Fiscal structure (RUT)
 **********************
 
-The partner's responsibility codes (section 53 in the RUT document)
-are included as part of the electronic invoice module given that is
-part of the information required by the DIAN .
+The partner's responsibility codes (section 53 in the RUT document) are included as part of the
+electronic invoice module, given it is part of the information required by the :abbr:`DIAN
+(Dirección de Impuestos y Aduanas Nacionales)`.
 
-These fields can be found in :menuselection:`Partner --> Sales &
-Purchase Tab --> Fiscal Information`
+The required fields can be found in :menuselection:`Partner --> Sales & Purchase Tab --> Fiscal
+Information`.
 
-.. image:: colombia/colombia06.png
-   :align: center
+.. image:: colombia/partner-fiscal-information.png
+   :alt: The fiscal information included in the electronic invoice module in Odoo.
 
-Additionally two booleans fields were added in order to specify the
-fiscal regimen of the partner.
+Additionally, two boolean fields were added in order to specify the fiscal regimen of the partner.
 
 Taxes
 ~~~~~
 
-If your sales transactions include products with taxes, it's important
-to consider that an extra field *Value Type* needs to be configured
-per tax. This option is located in the Advanced Options tab.
+If sales transactions include products with taxes, the :guilabel:`Value Type` field in the
+:guilabel:`Advanced Options tab` needs to be configured per tax.
 
-.. image:: colombia/colombia07.png
-   :align: center
+Retention tax types (ICA, IVA, Fuente) are also included in the options to configure taxes. This
+configuration is used in order to display taxes in the invoice PDF correctly.
 
-Retention tax types (ICA, IVA, Fuente) are also included in the
-options to configure your taxes. This configuration is used in order
-to correctly display taxes in the invoice PDF.
-
-.. image:: colombia/colombia08.png
-   :align: center
-
-Journals
-~~~~~~~~
-
-Once the DIAN has assigned the official sequence and prefix for the
-electronic invoice resolution, the Sales journals related to your
-invoice documents need to be updated in Odoo.  The sequence can be
-accessed using the :ref:`developer mode <developer-mode>`: :menuselection:`Accounting -->
-Settings --> Configuration Setting --> Journals`.
-
-.. image:: colombia/colombia09.png
-   :align: center
-
-Once that the sequence is opened, the Prefix and Next Number fields
-should be configured and synchronized with the CEN Financiero.
-
-.. image:: colombia/colombia10.png
-   :align: center
+.. image:: colombia/retention-tax-types.png
+   :alt: The ICA, IVA and Fuente fields in the Advanced Options tab in Odoo.
 
 Users
 ~~~~~
 
-The default template that is used by Odoo on the invoice PDF includes
-the job position of the salesperson, so these fields should be
-configured:
+The default template that is used by Odoo on the invoice PDF includes the job position of the
+salesperson, so the :guilabel:`Job Position` field should be configured.
 
-.. image:: colombia/colombia11.png
-   :align: center
+.. _colombia/workflows:
 
-Usage and testing
-=================
+Main workflows
+==============
 
-Invoice
--------
+.. image:: colombia/electronic-invoice-workflow.png
+   :alt: Electronic invoice workflow in Odoo.
 
-When all your master data and credentials has been configured, it's
-possible to start testing the electronic invoice workflow.
+.. _colombia/invoice-creation:
 
 Invoice creation
-~~~~~~~~~~~~~~~~
+----------------
 
-The functional workflow that takes place before an invoice validation
-doesn't change. The main changes that are introduced with the
-electronic invoice are the next fields:
-
-.. image:: colombia/colombia12.png
-   :align: center
+The functional workflow that takes place before an invoice validation doesn't change. The main
+changes that are introduced with the electronic invoice are the next fields.
 
 There are three types of documents:
 
-- **Factura Electronica**: This is the regular type of document and
-  its applicable for Invoices, Credit Notes and Debit Notes.
-- **Factura de Importación**: This should be selected for importation
-  transactions.
-- **Factura de contingencia**: This is an exceptional type that is
-  used as a manual backup in case that the company is not able to use
-  the ERP and it's necessary to generate the invoice manually, when
-  this invoice is added to the ERP, this invoice type should be
-  selected.
+- **Factura Electronica**: This is the regular document type applicable for Invoices, Credit Notes
+  and Debit Notes.
+- **Factura de Importación**: This should be selected for importation transactions.
+- **Factura de contingencia**: This is an exceptional type that is used as a manual backup if the
+  company is not able to use the ERP and if it is necessary to generate the invoice manually when
+  this invoice is added to the ERP.
+
+.. _colombia/invoice-validation:
 
 Invoice validation
-~~~~~~~~~~~~~~~~~~
+------------------
 
-After the invoice is validated an XML file is created and sent
-automatically to Carvajal, this file is displayed in the chatter.
+After the invoice is validated, an XML file is created and sent automatically to Carvajal. This file
+is also displayed in the chatter.
 
-.. image:: colombia/colombia13.png
-   :align: center
+.. image:: colombia/carvajal-invoice-xml-chatter.png
+   :alt: Carvajal XML invoice file in Odoo chatter.
 
-An extra field is now displayed in "Other Info" tab with the name of
-the XML file. Additionally there is a second extra field that is
-displayed with the Electronic Invoice status, with the initial value
-"In progress":
+The :guilabel:`Electronic Invoice Name` field is now displayed in the :guilabel:`Other Info` tab
+with the name of the XML file. Additionally, the :guilabel:`Electronic Invoice Status` field is
+displayed with the initial value :guilabel:`In progress`.
 
-.. image:: colombia/colombia14.png
-   :align: center
+.. _colombia/invoice-xml:
 
 Reception of legal XML and PDF
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+------------------------------
 
-The electronic invoice vendor receives the XML file and proceeds to
-validate the structure and the information in it, if everything is
-correct the invoice status changes to "Validated" after using the
-"Check Carvajal Status" button in the Action dropdown. They then
-proceed to generate a Legal XML which includes a digital signature and
-a unique code (CUFE), a PDF invoice that includes a QR code and the
-CUFE is also generated.
+The electronic invoice vendor receives the XML file and proceeds to validate the structure and the
+information in it. In the :guilabel:`Action` drop-down menu, select the :guilabel:`Check Carvajal
+Status` button. If everything is correct, the :guilabel:`Electronic Invoice Status` field value
+changes to :guilabel:`Validated`. Then, proceed to generate a legal XML, which includes a digital
+signature and a unique code (CUFE), a PDF invoice that includes a QR code, and the CUFE is also
+generated.
 
 After this:
 
-- A ZIP containing the legal XML and the PDF is downloaded and
-  displayed in the invoice chatter:
+- A ZIP containing the legal XML and the PDF is downloaded and displayed in the invoice chatter:
 
-  .. image:: colombia/colombia15.png
+  .. image:: colombia/zip-invoice-chatter.png
+     :alt: ZIP file displayed in the invoice chatter in Odoo.
 
-  .. image:: colombia/colombia16.png
+  .. image:: colombia/zip-file-contents.png
+     :alt: XML and PDF contained in invoice ZIP file.
 
-- The Electronic Invoice status changes to "Accepted"
+- The electronic invoice status changes to :guilabel:`Accepted`.
+
+.. _colombia/common-errors:
 
 Common errors
-~~~~~~~~~~~~~
+-------------
 
-During the XML validation the most common errors are usually related
-to missing master data. In such cases, error messages are shown in the
-chatter after updating the electronic invoice status.
+During the XML validation, the most common errors are usually related to missing master data. In
+such cases, error messages are shown in the chatter after updating the electronic invoice status.
 
-.. image:: colombia/colombia17.png
-   :align: center
+.. image:: colombia/xml-validation-errors.png
+   :alt: XML validation errors shown in the invoice chatter in Odoo.
 
-After the master data is corrected, it's possible to reprocess the XML
-with the new data and send the updated version, using the following
-button:
+After the master data is corrected, it's possible to reprocess the XML with the new data and send
+the updated version, using the following button in the :guilabel:`Action` drop-down menu.
 
-.. image:: colombia/colombia18.png
-   :align: center
-
-.. image:: colombia/colombia19.png
-   :align: center
+.. image:: colombia/updated-invoice-status.png
+   :alt: The updated invoice status in Odoo.
 
 Additional use cases
 --------------------
 
-The process for credit and debit notes is exactly the same as the
-invoice, the functional workflow remains the same as well.
+The process for credit and debit notes is exactly the same as the invoice. The functional workflow
+remains the same as well.
+
+.. _colombia/reports:
+
+Financial reports
+=================
+
+This information is a quick reference to the accounting reports included in the *Colombian
+Localization Accounting Reports* module.
+
+Certificado de Retención en ICA
+-------------------------------
+
+This report is a certification to vendors for withholdings made for the Colombian Industry and
+Commerce tax (ICA).
+
+Go to :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de Retención
+en ICA`.
+
+.. image:: colombia/ica-report.png
+   :alt: Certificado de Retención en ICA report in Odoo Accounting.
+
+Certificado de Retención en IVA
+-------------------------------
+
+This report issues a certificate on the amount withheld from vendors for VAT withholding.
+
+Go to :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de Retención
+en IVA`.
+
+.. image:: colombia/iva-report.png
+   :alt: Certificado de Retención en IVA report in Odoo Accounting.
+
+Certificado de Retención en la Fuente
+-------------------------------------
+
+This certificate is issued to partners for the withholding tax that they have made.
+
+Go to :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de Retención
+en Fuente`.
+
+.. image:: colombia/fuente-report.png
+   :alt: Certificado de Retención en Fuente report in Odoo Accounting.

content/applications/finance/fiscal_localizations/colombia_ES.rst

@@ -1,602 +0,0 @@
-=============
-Colombia (ES)
-=============
-
-Introducción
-============
-
-La Facturación Electrónica para Colombia está disponible en Odoo 12 y
-requiere los siguientes Módulos:
-
-#. **l10n_co**: Contiene los datos básicos para manejar el módulo de
-   contabilidad, incluyendo la configuración por defecto de los siguientes
-   puntos:
-
-   - Plan Contable
-   - Impuestos
-   - Retenciones
-   - Tipos de Documentos de Identificación
-
-#. **l10n_co_edi**: Este módulo incluye todos los campos adicionales que son
-   requeridos para la Integración entre Carvajal y la generación de la
-   Factura Electrónica, basado en los requisitos legales de la DIAN.
-
-
-Flujo General
-=============
-
-.. image:: colombia/colombia01.png
-   :align: center
-
-
-Configuración
-=============
-
-Instalación de los módulos de Localización Colombiana
------------------------------------------------------
-
-Para esto ve a las aplicaciones y busca “Colombia”, luego da click en
-Instalar a los primeros dos módulos:
-
-.. image:: colombia/colombia02.png
-   :align: center
-
-
-Configuración de las credenciales del Servicio Web de Carvajal
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-| Una vez que los módulos están instalados, para poderte conectar con el
-  Servicio Web de Carvajal, es necesario configurar el Usuario y las
-  Credenciales. Esta información será provista por Carvajal.
-| Ve a :menuselection:`Facturación --> Configuración --> Configuración` y busca la sección
-  **Facturación Electrónica Colombiana**
-
-.. image:: colombia_ES/colombia_ES02.png
-  :align: center
-
-La funcionalidad de pruebas le permite conectarse e interactuar con el
-ambiente piloto de Carvajal, esto permite a los usuarios probar el
-flujo completo y la integración con el Portal Financiero CEN, al cual
-se accede a través de la siguiente liga:
-
-CTS (Carvajal T&S)
-   https://cenflab.cen.biz/site/
-
-CSC (Carvajal Servicios de Comunicación)
-   https://web-stage.facturacarvajal.com/
-
-CSC es el predeterminado para nuevas bases de datos.
-
-Una vez que el ambiente de producción está listo en Odoo y en Carvajal
-el ambiente de pruebas debe ser deshabilitado para poder enviar la
-información al ambiente de producción de Carvajal.
-
-
-Configuración de Información para PDF
--------------------------------------
-
-| Como parte de la información configurable que es enviada en el XML,
-  puedes definir los datos de la sección fiscal del PDF, así como de la
-  información Bancaria.
-| Ve a :menuselection:`Contabilidad --> Configuración --> Ajustes` y busca la sección
-  **Facturación Electrónica Colombiana**.
-
-.. image:: colombia_ES/colombia_ES03.png
-  :align: center
-
-
-Configuración de los Datos Principales Requeridos en el XML
------------------------------------------------------------
-
-Contacto (Tercero)
-~~~~~~~~~~~~~~~~~~
-
-Identificación
-**************
-
-Como parte de la Localización Colombiana, los tipos de documentos
-definidos por la DIAN ahora están disponibles en el formulario de
-Contactos, por lo cual ya es posible asignarles su número de
-identificación asociado al tipo de documento correspondiente.
-
-.. image:: colombia_ES/colombia_ES04.png
-  :align: center
-
-Nota: Cuando el tipo de documento es RUT la identificación necesita ser
-ingresada en Odoo incluyendo el Dígito de Verificación. Odoo separará
-este número cuando la información sea enviada a los proveedores
-terceros.
-
-
-Estructura Fiscal (RUT)
-***********************
-
-Los Códigos de tipo de Obligación aplicables a los terceros (sección 53
-en el documento de RUT), son incluidos como parte del módulo de
-Facturación Electrónica, dado que es información requerida por la DIAN.
-
-Estos campos se encuentran en :menuselection:`Contactos --> Pestaña de Ventas y Compras
---> Información Fiscal`
-
-.. image:: colombia_ES/colombia_ES05.png
-  :align: center
-
-Adicionalmente dos últimos campos fueron agregados para especificar el
-régimen fiscal del contacto. Cabe aclarar que para envío de Factura
-electrónica de Carvajal, únicamente se hace distinción de entre Grandes
-Contribuyentes y Régimen simplificado, por lo se muestran solo estas dos
-opciones.
-
-Impuestos
-~~~~~~~~~
-
-Si tus transacciones de ventas incluyen productos con impuestos, es
-importante considerar que un campo adicional llamado *Tipo de Valor*
-necesita ser configurado en la siguiente ruta: :menuselection:`Contabilidad
---> Configuración --> Impuestos: --> Opciones Avanzadas --> Tipo de Valor`
-
-.. image:: colombia_ES/colombia_ES06.png
-  :align: center
-
-Los impuestos para Retenciones (ICA, IVA y Fuente) también están
-incluidos en las opciones para configurar tus impuestos, esta
-configuración es considerada para desplegar correctamente los impuestos
-en la representación gráfica de la Factura. (PDF)
-
-.. image:: colombia_ES/colombia_ES07.png
-  :align: center
-
-
-Diarios
-~~~~~~~
-
-Una vez que la DIAN ha asignado la secuencia y prefijo oficiales para la
-resolución de la Facturación Electrónica, los Diarios de Ventas
-relacionados con tus documentos de facturación necesitan ser
-actualizados en Odoo.
-
-La secuencia es configurada usando el modo de desarrollador en la
-siguiente ruta: :menuselection:`Contabilidad --> Configuración --> Diarios
---> Liga de Secuencia`
-
-.. image:: colombia_ES/colombia_ES08.png
-  :align: center
-
-Una vez que la secuencia es abierta, los campos de Prefijo y Siguiente
-Número deben ser configurados y sincronizados con el CEN Financiero.
-
-.. image:: colombia_ES/colombia_ES09.png
-  :align: center
-
-
-Usuarios
-~~~~~~~~
-
-La plantilla por defecto que es usada por Odoo en la representación
-gráfica incluye el nombre del Vendedor, así que estos campos deben ser
-considerados:
-
-.. image:: colombia_ES/colombia_ES10.png
-  :align: center
-
-
-Uso y Pruebas
-=============
-
-Facturas
---------
-
-Una vez que toda la información principal y las credenciales han sido
-configuradas, es posible empezar a probar el flujo de la Facturación
-Electrónica siguiendo las instrucciones que se detallan a continuación:
-
-
-Invoice Creation
-~~~~~~~~~~~~~~~~
-
-El flujo de trabajo funcional que lleva lugar antes de la validación de
-una factura continua siendo igual con Facturación Electrónica,
-independientemente de si es creada desde una Orden de Venta o si es
-creado manualmente.
-
-Los cambios principales que son introducidos con la Facturación
-Electrónica son los siguientes:
-
-Hay tres tipos de documentos
-
-- **Factura electrónica**. Este es el documento normal y aplica
-  para Facturas, Notas de Crédito y Notas de Débito.
-
-- **Factura de Importación**. Debe ser seleccionada para
-  transacciones de importación.
-
-- **Factura de Contingencia**. Esta es un caso excepcional y es
-  utilizada como un respaldo manual en caso que la compañía no
-  pueda usar el ERP y hay necesidad de crear la factura
-  manualmente. Al ingresar esta factura en el ERP, se debe
-  seleccionar este tipo.
-
-  .. image:: colombia_ES/colombia_ES11.png
-
-
-Invoice Validation
-~~~~~~~~~~~~~~~~~~
-
-Después que la factura fue validada, un archivo XML es creado y enviado
-automáticamente al proveedor de la factura electrónica. Este archivo es
-desplegado en el historial.
-
-.. image:: colombia_ES/colombia_ES12.png
-  :align: center
-
-Un campo adicional es ahora desplegado en la pestaña de “Otra
-Información” con el nombre del archivo XML. Adicionalmente hay un
-segundo campo adicional que es desplegado con el estatus de la Factura
-Electrónica, con el valor inicial **En Proceso**.
-
-.. image:: colombia_ES/colombia_ES13.png
-  :align: center
-
-
-Recepción del XML y PDF Legal
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-| El proveedor de la Factura Electrónica recibe el archivo XML y procede
-  a validar la información y la estructura contenida. Si todo es
-  correcto, el estatus de la Factura cambia a “Validado”. Como parte de
-  este proceso se generar el XML Legal, el cual incluye una firma
-  digital y un código único (CUFE) y generan el PDF de la Factura (el
-  cual incluye un código QR) y el CUFE.
-
-| Odoo envía una petición de actualización automáticamente para
-  verificar que el XML fue creado. Si este es el caso, las siguientes
-  acciones son hechas automáticamente:
-
-- El XML Legal y el PDF son incluidos en un archivo ZIP y desplegados
-  en el historial de la Factura.
-
-  .. image:: colombia_ES/colombia_ES14.png
-
-- El estatus de la Factura Electrónica es cambiado a “Aceptado”.
-
-  .. image:: colombia_ES/colombia_ES15.png
-
-.. tip::
-   En caso que el PDF y el XML sean requeridos inmediatamente, es
-   posible mandar manualmente la petición del estatus usando el siguiente
-   botón:
-
-   .. image:: colombia_ES/colombia_ES16.png
-      :align: center
-
-
-Errores Frecuentes
-~~~~~~~~~~~~~~~~~~
-
-Durante la validación del XML los errores más comunes usualmente están
-relacionados con información principal faltante. En estos casos, los
-detalles del error son recuperados en la petición de actualización y
-desplegados en el historial.
-
-.. image:: colombia_ES/colombia_ES17.png
-  :align: center
-
-Si la información principal es corregida, es posible re procesar el XML
-con la nueva información y mandar la versión actualizada usando el
-siguiente botón:
-
-.. image:: colombia_ES/colombia_ES18.png
-  :align: center
-
-.. image:: colombia_ES/colombia_ES19.png
-  :align: center
-
-
-Casos de Uso adicionales
-------------------------
-
-El proceso para las Notas de Crédito y Débito (Proveedores) es
-exactamente el mismo que en las Facturas. Su flujo de trabajo funcional
-se mantiene igual.
-
-Consideraciones del Anexo 1.7
-=============================
-
-Contexto
---------
-
-Contexto Normativo
-~~~~~~~~~~~~~~~~~~
-
-| Soporte Normativo:
-| Resolución DIAN Número 000042  ( 5 de Mayo de 2020)  Por la cual se desarrollan:
-
-- Los sistemas de facturación,
-- Los proveedores tecnológicos,
-- El registro de la factura electrónica de venta como título valor,
-- Se expide el anexo técnico de factura electrónica de venta y
-- Se dictan otras disposiciones en materia de sistemas de facturación.
-
-Anexo 1.7: Principales Cambios
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-- Cambios en la definición de Consumidor Final.
-- Informar bienes cubiertos para los 3 dias sin IVA.
-- Actualización de descripción de Impuestos.
-- Se agrega concepto para IVA Excluido.
-- Informar la fecha efectiva de entrega de los bienes.
-- Adecuaciones en la representación Gráfica (PDF).
-
-Calendario
-~~~~~~~~~~
-
-Se tiene varias fechas límites para la salida a producción bajo las condiciones del Anexo 1.7 las
-cuales dependen de los siguientes factores:
-
-#. Calendario de implementación de acuerdo con la actividad económica principal en el RUT:
-
-   .. image:: colombia_ES/colombia-es-calendario-rut.png
-      :align: center
-
-#. Calendario de implementación, para otros sujetos obligados:
-
-   .. image:: colombia_ES/colombia-es-calendario-otros-obligados.png
-      :align: center
-
-#. Calendario de implementación permanente:
-
-   .. image:: colombia_ES/colombia-es-calendario-permanente.png
-      :align: center
-
-Requerimientos en Odoo
-----------------------
-
-Con la finalidad de facilitar el proceso de preparación de las bases de Odoo estándar V12 y v13,
-únicamente será necesario que los administradores actualicen algunos módulos y creen los datos
-maestros relacionados a los nuevos procesos.
-
-Actualización de listado de Apps
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Utilizando el modo desarrollador, acceder al módulo de Aplicaciones y seleccionar el menú
-*Actualizar Lista*.
-
-.. image:: colombia_ES/colombia-es-actualizar-lista.png
-   :align: center
-
-Actualización de Módulos
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-Una vez actualizado Buscar *Colombia*, los siguientes módulos serán desplegados, se requieren
-actualizar dos módulos.
-
-#. Colombia - Contabilidad - l10n_co
-#. Electronic invoicing for Colombia with Carvajal UBL 2.1 - l10n_co_edi_ubl_2_1
-
-.. image:: colombia_ES/colombia-es-modulos.png
-   :align: center
-
-En cada módulo o ícono hay que desplegar el menú opciones utilizando los 3 puntos de la esquina
-superior derecha y seleccionamos *Actualizar*.
-
-Primero lo hacemos con en el módulo l10n_co:
-
-.. image:: colombia_ES/colombia-es-actualizar-contabilidad.png
-   :align: center
-
-Posteriormente lo hacemos con el módulo l10n_co_edi_ubl_2_1:
-
-.. image:: colombia_ES/colombia-es-actualizar-electronic-invoicing.png
-   :align: center
-
-Creación de Datos Maestros
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Las bases de datos existentes a Junio 2020 tanto en V12 como V13, deberán crear algunos datos
-maestros necesarios para operar correctamente con los cambios del Anexo 1.7.
-
-Consumidor Final
-****************
-
-La figura del consumidor final será utilizada para aquellas ventas sobre las cuales no es posible
-identificar toda la información fiscal y demográfica del cliente por lo que la factura se genera a
-nombre de este registro genérico.
-
-Es importante coordinar y definir los casos de uso en los que dependiendo de su empresa se tendrá
-permitido utilizar este registro genérico.
-
-Dentro de Odoo se tendrá que crear un contacto con las siguientes características, es importante que
-se defina de esta manera debido a que son los parámetros definidos por la DIAN.
-
-- **Tipo de contacto:** Individuo
-- **Nombre:** Consumidor Final
-- **Tipo de documento:** Cedula de Ciudadania
-- **Numero de Identificacion:** 222222222222
-
-.. image:: colombia_ES/colombia-es-consumidor-final-nuevo-contacto.png
-   :align: center
-
-Dentro de la pestaña Ventas y Compras, en la sección Información Fiscal, del campo Obligaciones y
-Responsabilidades colocaremos el valor: **R-99-PN**.
-
-.. image:: colombia_ES/colombia-es-consumidor-final-r-99-pn.png
-   :align: center
-
-IVA Excluido - Bienes Cubiertos
-*******************************
-
-Para reportar las transacciones realizadas mediante Bienes Cubiertos para los tres días sin IVA,
-será necesario crear un nuevo Impuesto al cual se le debe de asociar un grupo de impuestos
-específico que será utilizado por Odoo para agregar la sección requerida en el XML de factura
-electrónica.
-
-Para el crear el impuesto accederemos a Contabilidad dentro del menú :menuselection:`Configuración
---> Impuestos`:
-
-.. image:: colombia_ES/colombia-es-menu-impuestos.png
-   :align: center
-
-Procedemos a crear un nuevo Impuesto con importe 0% considerando los siguientes parámetros:
-
-.. image:: colombia_ES/colombia-es-nuevo-impuesto.png
-   :align: center
-
-El nombre del Impuesto puede ser definido a preferencia del usuario, sin embargo el campo clave es
-**Grupo de Impuestos** dentro de Opciones avanzadas, el cual debe ser: *bienes cubiertos* y el campo
-**Tipo de Valor**: *IVA*.
-
-.. image:: colombia_ES/colombia-es-nuevo-impuesto-opciones-avanzadas.png
-   :align: center
-
-Actualización de descripción de Departamentos
-*********************************************
-
-Es necesario actualizar la descripción de algunos departamentos, para lo cual accederemos a módulo
-de Contactos y dentro del menú de :menuselection:`Configuración --> Provincias`.
-
-.. image:: colombia_ES/colombia-es-menu-provincias.png
-   :align: center
-
-Posteriormente, podemos agregar por País para identificar claramente las provincias (Departamentos)
-de Colombia:
-
-.. image:: colombia_ES/colombia-es-provincias-agrupar.png
-   :align: center
-
-Una vez agrupados buscar los siguientes departamentos para actualizarlos con el valor indicado en la
-columna **Nombre actualizado**:
-
-+------------------------------+---------------------+--------------------------+
-| Nombre de provincia          | Código de Provincia | Nombre actualizado       |
-+==============================+=====================+==========================+
-| D.C.                         | DC                  | Bogotá                   |
-+------------------------------+---------------------+--------------------------+
-| Quindio                      | QUI                 | Quindío                  |
-+------------------------------+---------------------+--------------------------+
-| Archipiélago de San Andrés,  | SAP                 | San Andrés y Providencia |
-| Providencia y Santa Catalina |                     |                          |
-+------------------------------+---------------------+--------------------------+
-
-Ejemplo:
-
-.. image:: colombia_ES/colombia-es-provincias-ejemplo.png
-   :align: center
-
-Verificación de Código postal
-*****************************
-
-Dentro del Anexo 1.7 se comienza a validar que el código postal de las direcciones para contactos
-colombianos corresponda a las tablas oficiales definidas por la DIAN, por lo que se debe verificar
-que este campo está debidamente diligenciado de acuerdo a los definidos en la sigueinte fuente:
-`Codigos_Postales_Nacionales.csv
-<http://visor.codigopostal.gov.co/472/visor/Codigos_Postales_Nacionales.csv>`_
-
-Consideraciones Operativas
---------------------------
-
-Consumidor Final
-~~~~~~~~~~~~~~~~
-
-Una vez que resgistro de Consumidor final ha sido creado este deberá ser utilizado a demanda,
-generalmente será utilizado en las transacciones de facturación del punto de punto de venta.
-
-- El proceso de validación de la Factura será realizado de forma convencional en Odoo y la factura
-  será generada de la misma manera. Al detectar que el número de identificación corresponde a
-  consumidor Final, el XML que se envía a Carvajal será generado con las consideraciones y secciones
-  correspondientes.
-- Contablemente todos los registros de Consumidor final quedarán asociados al identificador generico:
-
-.. image:: colombia_ES/colombia-es-consumidor-final-asociado.png
-   :align: center
-
-IVA Excluido - Bienes Cubiertos
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-El 21 mayo del 2020 fue publicado el El Decreto 682 el cual establece Excepción especial en el
-Impuesto sobre las ventas. El principal objetivo de este decreto es reactivar la economía en
-Colombia por las bajas ventas generadas a causa del COVID.
-
-Fechas
-******
-
-Días de excención del impuesto sobre las ventas – IVA para bienes cubiertos (3 días SIN IVA).
-
-- **Primer día**: 19 de junio de 2020
-- **Segundo día**: 3 de Julio de 2020
-- **Tercer día**: 19 de Julio de 2020
-
-Condiciones
-***********
-
-Debido a que estas transacciones serán generadas de forma excepcional y que se tiene una combinación
-de varios factores y condiciones, los productores debera ser actualizados de forma manual en Odoo
-asignados temporalmente el impuesto de venta *IVA exento - Bienes cubierto* en cada empresa según
-corresponda.
-
-A continuación se mencionan algunas de las principales condiciones, sin embargo, cabe mencionar que
-las empresas deben de verificar todos los detalles en el `Decreto 682
-<https://dapre.presidencia.gov.co/normativa/normativa/DECRETO%20682%20DEL%2021%20DE%20MAYO%20DE%202020.pdf>`_.
-
-- Tipo de productos y precio Máximo:
-
-  +-----------------------------+---------------------------------------+
-  | Tipo de Productos           | Precio Máximo                         |
-  +=============================+=======================================+
-  | Electrodomesticos           | 40 UVT: $1,4 millones.                |
-  +-----------------------------+---------------------------------------+
-  | Vestuario y complementos    | | 3 UVT: $106.000                     |
-  |                             | | En el caso de los complementos es:  |
-  |                             | | 10 UVT- $356.000                    |
-  +-----------------------------+---------------------------------------+
-  | Elementos deportivos        | 10 UVT- $356.000                      |
-  +-----------------------------+---------------------------------------+
-  | Juguetes y Utiles Escolares | 5 UVT - $178.035                      |
-  +-----------------------------+---------------------------------------+
-  | Utiles Escolares            | 5 UVT - $178.035                      |
-  +-----------------------------+---------------------------------------+
-  | Bienes o servicios para     | 80 UVT - $2.848.560                   |
-  | el sector agropecuario      |                                       |
-  +-----------------------------+---------------------------------------+
-
-- Métodos de Pago:
-
-  - El pago debe realizarse por medios electrónico por ejemplo tarjetas de crédito/débito o bien mecanismos de pago online.
-
-- Limite de unidades:
-
-  - Cada cliente puede adquirir únicamente 3 unidades como máximo de cada producto.
-
-Medidas en Odoo
-***************
-
-- **Preparación de datos**
-
-  - Crear el Impuesto para Bienes cubiertos de acuerdo a lo indicado en este punto: Datos maestros.
-  - Identificar los productos y transacciones a los cuales les aplicará la Exclusión de IVA de
-    acuerdo a las condiciones establecidas en el decreto 682. En caso de ser un porcentaje
-    significativo de productos, se recomienda actualizar el impuesto de forma temporal en Odoo.
-  - Exportar un listado con los productos que serán afectados incluyendo el campo IVA Venta el cual
-    será sustituido temporalmente por el IVA de Bienes Cubiertos.
-  - Al finalizar las operaciones del día anterior a las fechas establecidas de día sin IVA, se debe
-    hacer la actualización temporal a IVA de Bienes Cubiertos.
-
-    .. image:: colombia_ES/columbia-es-producto-iva-bienes-cubiertos.png
-       :align: center
-
-- **Durante el día SIN IVA**
-
-  - Por defecto los productos previamente considerados con IVA de Bienes cubiertos serán generados
-    con este parámetro tanto en Órdenes de venta como facturas creadas durante ese mismo día.
-
-    .. image:: colombia_ES/columbia-es-factura-iva-bienes-cubiertos.png
-       :align: center
-
-  - Las órdenes de venta generadas con este impuesto deberán ser facturas el mismo día.
-  - En caso de que alguna de las condiciones no sea cumplida (ejemplo el pago es realizado en
-    efectivo) el impuesto deberá ser actualizado manualmente al momento de facturar.
-
-- **Posterior al día SIN IVA**
-
-  - Los productos que fueron actualizados deberá ser reconfigurados a su IVA original.
-  - En caso de que se detecte alguna Orden de venta facturar en la cual se incluya IVA de Bienes
-    Cubiertos, se deberá realizar actualización manual correspondiente al IVA convencional.

content/applications/general/auth/azure.rst

@@ -59,6 +59,16 @@ registration` from the drop-down menu. On the :guilabel:`Register an application
 :guilabel:`Supported account types` section select the option for :guilabel:`Accounts in this
 organizational directory only (Default Directory only - Single tenant)`.
 
+.. warning::
+   The :guilabel:`Supported account types` can vary by Microsoft account type and end use of the
+   OAuth. For example: Is the login meant for internal users within one organization or is it meant
+   for customer portal access? The above configuration is used for internal users in an
+   organization.
+
+   Choose :guilabel:`Personal Microsoft accounts only` if the target audience is meant for portal
+   users. Choose :guilabel:`Accounts in this organizational directory only (Default Directory only -
+   Single tenant)` if the target audience is company users.
+
 Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the platform, and then input
 `https://<odoo base url>/auth_oauth/signin` in the :guilabel:`URL` field. The Odoo base :abbr:`URL
 (Uniform Resource Locator)` is the canonical domain at which your Odoo instance can be reached (e.g.
@@ -97,17 +107,6 @@ After finishing this step, click on :guilabel:`Endpoints` on the top menu and cl
 next to :guilabel:`OAuth 2.0 authorization endpoint (v2)` field. Paste this value in the clipboard /
 notepad.
 
-The value should equal `https://login.microsoftonline.com/<directory_id>/oauth2/v2.0/authorize`.
-Replace the `<directory_id>` with the :guilabel:`Directory (tenant) ID` under the
-:guilabel:`Essentials` section of the *Overview* page if it is not already present in the :abbr:`URL
-(uniform resource locator)`.
-
-.. example::
-   Should the :guilabel:`Directory (tenant) ID` be equal to `6729e9df-afbb-4522-a876-f1408d416396`
-   then the new value of the :guilabel:`OAuth 2.0 authorization endpoint (v2)` :abbr:`URL (Uniform
-   Resource Locator)` should be:
-   `https://login.microsoftonline.com/6729e9df-afbb-4522-a876-f1408d416396/oauth2/v2.0/authorize`.
-
 .. image:: azure/overview-azure-app.png
    :align: center
    :alt: Application ID and OAuth 2.0 authorization endpoint (v2) credentials.

content/applications/general/email_communication/faq.rst

@@ -41,9 +41,8 @@ our e-mail servers from being blacklisted.
 Here are the default limits for new databases:
 
 - 200 emails/day for Odoo Online and Odoo.sh databases with an active subscription,
-
-- 50 emails/day for one-app free and trial databases,
-
+- 20 emails/day for one-app free databases,
+- 50 emails/day for trial databases,
 - in case of migration, your daily limit might be reset to 50 emails a day.
 
 In case you hit the limit, you can:

content/applications/hr/payroll.rst

@@ -1,18 +1,359 @@
-:nosearch:
-:show-content:
-:hide-page-toc:
-:show-toc:
-
 =======
 Payroll
 =======
 
-**Odoo Payroll** generates payslips for all employees based on timeseets and various salary rules.
+Odoo *Payroll* is used to process work entries and create payslips for employees, including both
+regular pay and commission. Payroll works in conjunction with other Odoo apps, such as *Employees*,
+*Timesheets*, *Time Off*, and *Attendances*.
 
-.. seealso::
-   `Odoo Tutorials: Payroll <https://www.odoo.com/slides/slide/manage-payroll-1002>`_
+The *Payroll* app helps ensure there are no issues or conflicts when validating work entries,
+handles country-specific localizations to ensure that payslips follow local rules and taxes, and
+allows for salary assignments. Payroll configuration is critical to ensure accurate and timely
+processing of payslips.
 
-.. toctree::
-   :titlesonly:
+Settings
+========
 
-   payroll/configuration
+To access the *Settings*, go to :menuselection:`Payroll --> Configuration --> Settings`. Whether or
+not payslips are posted in accounting, and whether SEPA payments are created, is selected here.
+
+The :guilabel:`Settings` screen is where localization settings are configured. *Localizations* are
+country-specific settings pre-configured in Odoo at the creation of the database, and account for
+all taxes, fees, and allowances for that particular country. The :guilabel:`Localization` section of
+the :guilabel:`Settings` includes a detailed view of all benefits provided to employees.
+
+.. image:: payroll/payroll-settings.png
+   :align: center
+   :alt: Settings available for Payroll.
+
+Any country-specific localizations are set up in the :guilabel:`Localization` section of the
+:guilabel:`Settings` screen. All localization items are pre-populated when the country is specified
+during the creation of the database. It is not recommended to alter the localization settings unless
+specifically required.
+
+Work entries
+============
+
+A *work entry* is an individual record on an employee's timesheet. Work entries can be configured to
+account for all types of work and time off, such as :guilabel:`Attendance`, :guilabel:`Sick Time
+Off`, :guilabel:`Training`, or :guilabel:`Public Holiday`.
+
+Work entry types
+----------------
+
+When creating a work entry in the *Payroll* application, or when an employee enters information in
+the *Timesheets* application, a :guilabel:`Work Entry Type` needs to be selected. The list of
+:guilabel:`Work Entry Types` is automatically created based on localization settings set in the
+database.
+
+To view the current work entry types available, go to :menuselection:`Payroll --> Configuration -->
+Work Entry Types`.
+
+Each work entry type has a code to aid in the creation of payslips, and ensure all taxes and fees
+are correctly entered.
+
+.. image:: payroll/work-entry-types.png
+   :align: center
+   :alt: List of all work entry types currently available.
+
+New work entry type
+~~~~~~~~~~~~~~~~~~~
+
+To create a new work entry type, click the :guilabel:`Create` button. Enter the information on the
+form:
+
+- :guilabel:`Work Entry Type Name`: The name should be short and descriptive, such as `Sick Time` or
+  `Public Holiday`.
+- :guilabel:`Code`: This code appears with the work entry type on timesheets and payslips. Since the
+  code is used in conjunction with the *Accounting* application, it is advised to check with the
+  accounting department for a code to use.
+- :guilabel:`Sequence`: The sequence determines the order that the work entry is computed in the
+  payslip list.
+- Check boxes: If any of the items in the list applies to the work entry, check off the box by
+  clicking it. If :guilabel:`Time Off` is checked off, a :guilabel:`Time Off Type` field appears.
+  This field has a drop-down menu to select the specific type of time off, or a new type of time off
+  can be entered.
+
+.. image:: payroll/new-work-entry.png
+   :align: center
+   :alt: New work entry type form.
+
+- :guilabel:`Rounding`: The rounding method determines how timesheet entries are displayed on the
+  payslip.
+
+  - :guilabel:`No Rounding`: A timesheet entry is not modified.
+  - :guilabel:`Half Day`: A timesheet entry is rounded to the closest half day amount.
+  - :guilabel:`Day`: A timesheet entry is rounded to the closest full day amount.
+
+.. example::
+   If the working time is set to an 8-hour work day (40-hour work week), and an employee enters a
+   time of 5.5 hours on a timesheet, and :guilabel:`Rounding` is set to :guilabel:`No Rounding`, the
+   entry remains 5.5 hours. If :guilabel:`Rounding` is set to :guilabel:`Half Day`, the entry is
+   changed to 4 hours. If it is set to :guilabel:`Day`, it is changed to 8 hours.
+
+Working times
+-------------
+
+To view the currently configured working times, go to :menuselection:`Payroll --> Configuration -->
+Working Times`. The working times that are available for an employee's contracts and work entries
+are found in this list.
+
+Working times are company-specific. Each company must identify each type of working time they use.
+For example, an Odoo database containing multiple companies that use a standard 40-hour work week
+needs to have a separate working time entry for each company that uses the 40-hour standard work
+week.
+
+.. image:: payroll/working-times.png
+   :align: center
+   :alt: All working times currently set up in the database.
+
+New working time
+~~~~~~~~~~~~~~~~
+
+To create a new working time, click the :guilabel:`Create` button. Enter the information on the
+form.
+
+.. image:: payroll/new-working-times.png
+   :align: center
+   :alt: New working type form.
+
+The fields are auto-populated for a regular 40-hour work week but can be modified. First, change the
+name of the working time by modifying the text in the :guilabel:`Name` field. Next, make any
+adjustments to the days and times that apply to the new working time.
+
+In the :guilabel:`Working Hours` tab, modify the :guilabel:`Day of Week`, :guilabel:`Day Period`,
+and :guilabel:`Work Entry Type` selections by clicking on the drop-down menus in each column and
+making the desired selection. The :guilabel:`Work From` and :guilabel:`Work To` columns are modified
+by typing in the time.
+
+.. note::
+   The :guilabel:`Work From` and :guilabel:`Work To` times must be in a 24-hour format. For example,
+   `2:00 PM` would be entered as `14:00`.
+
+If the working time should be in a two-week configuration, click the :guilabel:`Switch To 2 Week
+Calendar` button. This creates entries for an :guilabel:`Even week` and an :guilabel:`Odd week`.
+
+Salary
+======
+
+.. _payroll/structure-types:
+
+Structure types
+---------------
+
+In Odoo, an employee's payslip is based on *structures* and *structure types*, which both affect how
+an employee enters timesheets. Each structure type is an individual set of rules for processing a
+timesheet entry, which consists of different structures nested within it. Structure types define how
+often an employee gets paid, the working hours, and if wages are based on a salary (fixed) or how
+many hours the employee worked (varied).
+
+For example, a structure type could be `Employee`, and that structure type could have two different
+structures in it: a `Regular Pay` structure which includes all the separate rules for processing
+regular pay, as well as a structure for an `End of Year Bonus` which includes the rules only for the
+end of year bonus. Both the `Regular Pay` structure and `End of Year Bonus` structure are structures
+within the `Employee` structure type.
+
+The different structure types can be seen by going to :menuselection:`Payroll --> Configuration -->
+Structure Types`.
+
+There are two default structure types configured in Odoo: *Employee* and *Worker*. Typically,
+*Employee* is used for salaried employees, which is why the wage type is *Monthly Fixed Wage*, and
+*Worker* is typically used for employees paid by the hour, so the wage type is *Hourly Wage*.
+
+.. image:: payroll/structure-type.png
+   :align: center
+   :alt: List of all structure types.
+
+Click the :guilabel:`Create` button to make a new structure type. Most fields are pre-populated, but
+all fields can be edited. Once the fields are edited, click the :guilabel:`Save` button to save the
+changes, or click :guilabel:`Discard` to delete the entry.
+
+.. image:: payroll/new-structure.png
+   :align: center
+   :alt: New structure type box.
+
+Structures
+----------
+
+*Salary structures* are the different ways an employee gets paid within a specific *structure*, and
+are specifically defined by various rules.
+
+The amount of structures a company needs for each structure type depends on how many different ways
+employees are paid, and how their pay is calculated. For example, a common structure that could be
+useful to add may be a `Bonus`.
+
+To view all the various structures for each structure type, go to :menuselection:`Payroll -->
+Configuration --> Structures`.
+
+.. image:: payroll/salary-structure.png
+   :align: center
+   :alt: All available salary structures.
+
+Each :ref:`structure type <payroll/structure-types>` lists the various structures associated with
+it. Each structure contains a set of rules that define it.
+
+Click on a structure to view its :guilabel:`Salary Rules`. These rules are what calculate the
+payslip for the employee.
+
+.. image:: payroll/structure-regular-pay-rules.png
+   :align: center
+   :alt: Salary structure details for Regular Pay.
+
+Rules
+-----
+
+Each structure has a set of *salary rules* to follow for accounting purposes. These rules are
+configured by the localization, and affect the *Accounting* application, so modifications to the
+default rules, or the creation of new rules, should only be done when necessary.
+
+To view all the rules, go to :menuselection:`Payroll app --> Configuration --> Rules`. Click on a
+structure (such as :guilabel:`Regular Pay`) to view all the rules.
+
+.. image:: payroll/rules.png
+   :align: center
+   :alt: Rules for each salary structure type.
+
+To make a new rule, click :guilabel:`Create`. A new rule form appears. Enter the information in the
+fields, then click :guilabel:`Save`.
+
+.. image:: payroll/new-rule.png
+   :align: center
+   :alt: Enter the information for the new rule.
+
+The required fields for a rule are:
+
+- :guilabel:`Name`: Enter a name for the rule.
+- :guilabel:`Category`: Select a category the rule applies to from the drop-down menu, or enter a
+  new one.
+- :guilabel:`Code`: Enter a code to be used for this new rule. It is recommended to coordinate with
+  the accounting department for a code as this will affect them.
+- :guilabel:`Salary Structure`: Select a salary structure the rule applies to from the drop-down
+  menu, or enter a new one.
+- :guilabel:`Condition Based on`: In the :guilabel:`General` tab, select from the drop-down menu
+  whether the rule is :guilabel:`Always True` (always applies), a :guilabel:`Range` (applies to a
+  specific range, which is entered beneath the selection), or a :guilabel:`Python Expression` (the
+  code is entered beneath the selection).
+- :guilabel:`Amount Type`: In the :guilabel:`General` tab, select from the drop-down menu whether
+  the amount is a :guilabel:`Fixed Amount`, a :guilabel:`Percentage (%)`, or a :guilabel:`Python
+  Code`. Depending on what is selected, the fixed amount, percentage, or Python code needs to be
+  entered next.
+
+Rule parameters
+---------------
+
+.. note::
+   Currently, the :guilabel:`Rule Parameters` feature found inside the :menuselection:`Payroll app
+   --> Configuration` menu is still in development and only serves a specific use case for Belgian
+   markets. The documentation will be updated when this section has matured to more markets.
+
+Other input types
+-----------------
+
+When creating payslips, it is sometimes necessary to add other entries for specific circumstances,
+like expenses, reimbursements, or deductions. These other inputs can be configured by going to
+:menuselection:`Payroll --> Configuration --> Other Input Types`.
+
+.. image:: payroll/other-input.png
+   :align: center
+   :alt: Other input types for payroll.
+
+To create a new input type, click the :guilabel:`Create` button. Enter the :guilabel:`Description`,
+the :guilabel:`Code`, and which structure it applies to in the :guilabel:`Availability in Structure`
+field. Click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete
+the entry.
+
+.. image:: payroll/input-type-new.png
+   :align: center
+   :alt: Create a new Input Type.
+
+Salary package configurator
+===========================
+
+The various options under the :guilabel:`Salary Package Configurator` section of the
+:menuselection:`Payroll --> Configuration` menu all affect an employee's potential salary. These
+sections (:guilabel:`Advantages`, :guilabel:`Personal Info`, and :guilabel:`Resume`) specify what
+benefits can be offered to an employee in their salary package.
+
+Depending on what information an employee enters (such as deductions, dependents, etc.), their
+salary is adjusted accordingly. When an applicant applies for a job on the company website, the
+sections under :guilabel:`Salary Package Configurator` directly affect what the applicant sees, and
+what is populated as the applicant enters information.
+
+Advantages
+----------
+
+When offering potential employees a position, there can be certain *advantages* set in Odoo in
+addition to the salary to make the offer more appealing (such as extra time off, access to a company
+car, reimbursement for a phone or internet, etc.).
+
+To see the advantages, go to :menuselection:`Payroll --> Configuration --> Advantages`. Advantages
+are grouped by :guilabel:`Structure type`.
+
+.. image:: payroll/advantages.png
+   :align: center
+   :alt: Settings available for payroll.
+
+To make a new advantage, click the :guilabel:`Create` button. Enter the information in the fields,
+then click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete
+the entry.
+
+.. image:: payroll/new-advantage.png
+   :align: center
+   :alt: List of advantages employee's can have.
+
+The required fields for an advantage are:
+
+- :guilabel:`Name`: Enter the name for the advantage.
+- :guilabel:`Advantage Field`: Select from the drop-down menu what field in the payslip this
+  advantage appears under.
+- :guilabel:`Advantage Type`: Select from the drop-down menu what type of advantage the benefit is.
+  Select from :guilabel:`Monthly Benefit in Kind`, :guilabel:`Monthly Advantages in Net`,
+  :guilabel:`Monthly Advantages in Cash`, or :guilabel:`Yearly Advantages in Cash`.
+- :guilabel:`Salary Structure Type`: Select from the drop-down menu which salary structure type this
+  advantage applies to.
+
+Personal info
+-------------
+
+Every employee in Odoo has an *employee card* that includes all of their personal information,
+resume, work information, and documents. To view an employee's card, go to the main
+:menuselection:`Payroll` app dashboard, and click on the employee's card, or go to
+:menuselection:`Payroll --> Employees --> Employees` and click on the employee's card. Employee
+cards can also be viewed by going to the :menuselection:`Employees` app.
+
+.. note::
+   An employee card can be thought of as an employee personnel file.
+
+The *Personal Information* section lists all of the fields that are available to enter on the
+employee's card. To access this section, go to :menuselection:`Payroll --> Configuration -->
+Personal Info`.
+
+.. image:: payroll/personal-info.png
+   :align: center
+   :alt: Personal information that appear on employee cards to enter.
+
+To edit an entry, select it from the list. Then, click the :guilabel:`Edit` button, and modify the
+entry. When done, click :guilabel:`Save` or :guilabel:`Discard` to save the information or cancel
+the edits.
+
+.. image:: payroll/personal-new.png
+   :align: center
+   :alt: New personal information entry.
+
+The two most important fields on the personal info form are :guilabel:`Is Required` and
+:guilabel:`Display Type`. Checking the :guilabel:`Is Required` box makes the field mandatory on the
+employee's card.
+
+The :guilabel:`Display Type` drop-down menu allows for the information to be entered in a variety of
+ways, from a :guilabel:`Text` box, to a customizable :guilabel:`Radio` button, a
+:guilabel:`Checkbox`, a :guilabel:`Document`, and more.
+
+Once the information is entered, click the :guilabel:`Save` button to save the entry.
+
+Resume
+------
+
+.. note::
+   Currently, the :guilabel:`Resume` feature found inside the :menuselection:`Payroll app -->
+   Configuration` menu is still in development and only serves a specific use case for Belgian
+   markets. The documentation will be updated when this section has matured to more markets.

content/applications/hr/payroll/configuration.rst

@@ -1,359 +0,0 @@
-=====================
-Payroll configuration
-=====================
-
-Odoo *Payroll* is used to process work entries and create payslips for employees, including both
-regular pay and commission. Payroll works in conjunction with other Odoo apps, such as *Employees*,
-*Timesheets*, *Time Off*, and *Attendances*.
-
-The *Payroll* app helps ensure there are no issues or conflicts when validating work entries,
-handles country-specific localizations to ensure that payslips follow local rules and taxes, and
-allows for salary assignments. Payroll configuration is critical to ensure accurate and timely
-processing of payslips.
-
-Settings
-========
-
-To access the *Settings*, go to :menuselection:`Payroll --> Configuration --> Settings`. Whether or
-not payslips are posted in accounting, and whether SEPA payments are created, is selected here.
-
-The :guilabel:`Settings` screen is where localization settings are configured. *Localizations* are
-country-specific settings pre-configured in Odoo at the creation of the database, and account for
-all taxes, fees, and allowances for that particular country. The :guilabel:`Localization` section of
-the :guilabel:`Settings` includes a detailed view of all benefits provided to employees.
-
-.. image:: configuration/payroll-settings.png
-   :align: center
-   :alt: Settings available for Payroll.
-
-Any country-specific localizations are set up in the :guilabel:`Localization` section of the
-:guilabel:`Settings` screen. All localization items are pre-populated when the country is specified
-during the creation of the database. It is not recommended to alter the localization settings unless
-specifically required.
-
-Work entries
-============
-
-A *work entry* is an individual record on an employee's timesheet. Work entries can be configured to
-account for all types of work and time off, such as :guilabel:`Attendance`, :guilabel:`Sick Time
-Off`, :guilabel:`Training`, or :guilabel:`Public Holiday`.
-
-Work entry types
-----------------
-
-When creating a work entry in the *Payroll* application, or when an employee enters information in
-the *Timesheets* application, a :guilabel:`Work Entry Type` needs to be selected. The list of
-:guilabel:`Work Entry Types` is automatically created based on localization settings set in the
-database.
-
-To view the current work entry types available, go to :menuselection:`Payroll --> Configuration -->
-Work Entry Types`.
-
-Each work entry type has a code to aid in the creation of payslips, and ensure all taxes and fees
-are correctly entered.
-
-.. image:: configuration/work-entry-types.png
-   :align: center
-   :alt: List of all work entry types currently available.
-
-New work entry type
-~~~~~~~~~~~~~~~~~~~
-
-To create a new work entry type, click the :guilabel:`Create` button. Enter the information on the
-form:
-
-- :guilabel:`Work Entry Type Name`: The name should be short and descriptive, such as `Sick Time` or
-  `Public Holiday`.
-- :guilabel:`Code`: This code appears with the work entry type on timesheets and payslips. Since the
-  code is used in conjunction with the *Accounting* application, it is advised to check with the
-  accounting department for a code to use.
-- :guilabel:`Sequence`: The sequence determines the order that the work entry is computed in the
-  payslip list.
-- Check boxes: If any of the items in the list applies to the work entry, check off the box by
-  clicking it. If :guilabel:`Time Off` is checked off, a :guilabel:`Time Off Type` field appears.
-  This field has a drop-down menu to select the specific type of time off, or a new type of time off
-  can be entered.
-
-.. image:: configuration/new-work-entry.png
-   :align: center
-   :alt: New work entry type form.
-
-- :guilabel:`Rounding`: The rounding method determines how timesheet entries are displayed on the
-  payslip.
-
-  - :guilabel:`No Rounding`: A timesheet entry is not modified.
-  - :guilabel:`Half Day`: A timesheet entry is rounded to the closest half day amount.
-  - :guilabel:`Day`: A timesheet entry is rounded to the closest full day amount.
-
-.. example::
-   If the working time is set to an 8-hour work day (40-hour work week), and an employee enters a
-   time of 5.5 hours on a timesheet, and :guilabel:`Rounding` is set to :guilabel:`No Rounding`, the
-   entry remains 5.5 hours. If :guilabel:`Rounding` is set to :guilabel:`Half Day`, the entry is
-   changed to 4 hours. If it is set to :guilabel:`Day`, it is changed to 8 hours.
-
-Working times
--------------
-
-To view the currently configured working times, go to :menuselection:`Payroll --> Configuration -->
-Working Times`. The working times that are available for an employee's contracts and work entries
-are found in this list.
-
-Working times are company-specific. Each company must identify each type of working time they use.
-For example, an Odoo database containing multiple companies that use a standard 40-hour work week
-needs to have a separate working time entry for each company that uses the 40-hour standard work
-week.
-
-.. image:: configuration/working-times.png
-   :align: center
-   :alt: All working times currently set up in the database.
-
-New working time
-~~~~~~~~~~~~~~~~
-
-To create a new working time, click the :guilabel:`Create` button. Enter the information on the
-form.
-
-.. image:: configuration/new-working-times.png
-   :align: center
-   :alt: New working type form.
-
-The fields are auto-populated for a regular 40-hour work week but can be modified. First, change the
-name of the working time by modifying the text in the :guilabel:`Name` field. Next, make any
-adjustments to the days and times that apply to the new working time.
-
-In the :guilabel:`Working Hours` tab, modify the :guilabel:`Day of Week`, :guilabel:`Day Period`,
-and :guilabel:`Work Entry Type` selections by clicking on the drop-down menus in each column and
-making the desired selection. The :guilabel:`Work From` and :guilabel:`Work To` columns are modified
-by typing in the time.
-
-.. note::
-   The :guilabel:`Work From` and :guilabel:`Work To` times must be in a 24-hour format. For example,
-   `2:00 PM` would be entered as `14:00`.
-
-If the working time should be in a two-week configuration, click the :guilabel:`Switch To 2 Week
-Calendar` button. This creates entries for an :guilabel:`Even week` and an :guilabel:`Odd week`.
-
-Salary
-======
-
-.. _payroll/structure-types:
-
-Structure types
----------------
-
-In Odoo, an employee's payslip is based on *structures* and *structure types*, which both affect how
-an employee enters timesheets. Each structure type is an individual set of rules for processing a
-timesheet entry, which consists of different structures nested within it. Structure types define how
-often an employee gets paid, the working hours, and if wages are based on a salary (fixed) or how
-many hours the employee worked (varied).
-
-For example, a structure type could be `Employee`, and that structure type could have two different
-structures in it: a `Regular Pay` structure which includes all the separate rules for processing
-regular pay, as well as a structure for an `End of Year Bonus` which includes the rules only for the
-end of year bonus. Both the `Regular Pay` structure and `End of Year Bonus` structure are structures
-within the `Employee` structure type.
-
-The different structure types can be seen by going to :menuselection:`Payroll --> Configuration -->
-Structure Types`.
-
-There are two default structure types configured in Odoo: *Employee* and *Worker*. Typically,
-*Employee* is used for salaried employees, which is why the wage type is *Monthly Fixed Wage*, and
-*Worker* is typically used for employees paid by the hour, so the wage type is *Hourly Wage*.
-
-.. image:: configuration/structure-type.png
-   :align: center
-   :alt: List of all structure types.
-
-Click the :guilabel:`Create` button to make a new structure type. Most fields are pre-populated, but
-all fields can be edited. Once the fields are edited, click the :guilabel:`Save` button to save the
-changes, or click :guilabel:`Discard` to delete the entry.
-
-.. image:: configuration/new-structure.png
-   :align: center
-   :alt: New structure type box.
-
-Structures
-----------
-
-*Salary structures* are the different ways an employee gets paid within a specific *structure*, and
-are specifically defined by various rules.
-
-The amount of structures a company needs for each structure type depends on how many different ways
-employees are paid, and how their pay is calculated. For example, a common structure that could be
-useful to add may be a `Bonus`.
-
-To view all the various structures for each structure type, go to :menuselection:`Payroll -->
-Configuration --> Structures`.
-
-.. image:: configuration/salary-structure.png
-   :align: center
-   :alt: All available salary structures.
-
-Each :ref:`structure type <payroll/structure-types>` lists the various structures associated with
-it. Each structure contains a set of rules that define it.
-
-Click on a structure to view its :guilabel:`Salary Rules`. These rules are what calculate the
-payslip for the employee.
-
-.. image:: configuration/structure-regular-pay-rules.png
-   :align: center
-   :alt: Salary structure details for Regular Pay.
-
-Rules
------
-
-Each structure has a set of *salary rules* to follow for accounting purposes. These rules are
-configured by the localization, and affect the *Accounting* application, so modifications to the
-default rules, or the creation of new rules, should only be done when necessary.
-
-To view all the rules, go to :menuselection:`Payroll app --> Configuration --> Rules`. Click on a
-structure (such as :guilabel:`Regular Pay`) to view all the rules.
-
-.. image:: configuration/rules.png
-   :align: center
-   :alt: Rules for each salary structure type.
-
-To make a new rule, click :guilabel:`Create`. A new rule form appears. Enter the information in the
-fields, then click :guilabel:`Save`.
-
-.. image:: configuration/new-rule.png
-   :align: center
-   :alt: Enter the information for the new rule.
-
-The required fields for a rule are:
-
-- :guilabel:`Name`: Enter a name for the rule.
-- :guilabel:`Category`: Select a category the rule applies to from the drop-down menu, or enter a
-  new one.
-- :guilabel:`Code`: Enter a code to be used for this new rule. It is recommended to coordinate with
-  the accounting department for a code as this will affect them.
-- :guilabel:`Salary Structure`: Select a salary structure the rule applies to from the drop-down
-  menu, or enter a new one.
-- :guilabel:`Condition Based on`: In the :guilabel:`General` tab, select from the drop-down menu
-  whether the rule is :guilabel:`Always True` (always applies), a :guilabel:`Range` (applies to a
-  specific range, which is entered beneath the selection), or a :guilabel:`Python Expression` (the
-  code is entered beneath the selection).
-- :guilabel:`Amount Type`: In the :guilabel:`General` tab, select from the drop-down menu whether
-  the amount is a :guilabel:`Fixed Amount`, a :guilabel:`Percentage (%)`, or a :guilabel:`Python
-  Code`. Depending on what is selected, the fixed amount, percentage, or Python code needs to be
-  entered next.
-
-Rule parameters
----------------
-
-.. note::
-   Currently, the :guilabel:`Rule Parameters` feature found inside the :menuselection:`Payroll app
-   --> Configuration` menu is still in development and only serves a specific use case for Belgian
-   markets. The documentation will be updated when this section has matured to more markets.
-
-Other input types
------------------
-
-When creating payslips, it is sometimes necessary to add other entries for specific circumstances,
-like expenses, reimbursements, or deductions. These other inputs can be configured by going to
-:menuselection:`Payroll --> Configuration --> Other Input Types`.
-
-.. image:: configuration/other-input.png
-   :align: center
-   :alt: Other input types for payroll.
-
-To create a new input type, click the :guilabel:`Create` button. Enter the :guilabel:`Description`,
-the :guilabel:`Code`, and which structure it applies to in the :guilabel:`Availability in Structure`
-field. Click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete
-the entry.
-
-.. image:: configuration/input-type-new.png
-   :align: center
-   :alt: Create a new Input Type.
-
-Salary package configurator
-===========================
-
-The various options under the :guilabel:`Salary Package Configurator` section of the
-:menuselection:`Payroll --> Configuration` menu all affect an employee's potential salary. These
-sections (:guilabel:`Advantages`, :guilabel:`Personal Info`, and :guilabel:`Resume`) specify what
-benefits can be offered to an employee in their salary package.
-
-Depending on what information an employee enters (such as deductions, dependents, etc.), their
-salary is adjusted accordingly. When an applicant applies for a job on the company website, the
-sections under :guilabel:`Salary Package Configurator` directly affect what the applicant sees, and
-what is populated as the applicant enters information.
-
-Advantages
-----------
-
-When offering potential employees a position, there can be certain *advantages* set in Odoo in
-addition to the salary to make the offer more appealing (such as extra time off, access to a company
-car, reimbursement for a phone or internet, etc.).
-
-To see the advantages, go to :menuselection:`Payroll --> Configuration --> Advantages`. Advantages
-are grouped by :guilabel:`Structure type`.
-
-.. image:: configuration/advantages.png
-   :align: center
-   :alt: Settings available for payroll.
-
-To make a new advantage, click the :guilabel:`Create` button. Enter the information in the fields,
-then click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete
-the entry.
-
-.. image:: configuration/new-advantage.png
-   :align: center
-   :alt: List of advantages employee's can have.
-
-The required fields for an advantage are:
-
-- :guilabel:`Name`: Enter the name for the advantage.
-- :guilabel:`Advantage Field`: Select from the drop-down menu what field in the payslip this
-  advantage appears under.
-- :guilabel:`Advantage Type`: Select from the drop-down menu what type of advantage the benefit is.
-  Select from :guilabel:`Monthly Benefit in Kind`, :guilabel:`Monthly Advantages in Net`,
-  :guilabel:`Monthly Advantages in Cash`, or :guilabel:`Yearly Advantages in Cash`.
-- :guilabel:`Salary Structure Type`: Select from the drop-down menu which salary structure type this
-  advantage applies to.
-
-Personal info
--------------
-
-Every employee in Odoo has an *employee card* that includes all of their personal information,
-resume, work information, and documents. To view an employee's card, go to the main
-:menuselection:`Payroll` app dashboard, and click on the employee's card, or go to
-:menuselection:`Payroll --> Employees --> Employees` and click on the employee's card. Employee
-cards can also be viewed by going to the :menuselection:`Employees` app.
-
-.. note::
-   An employee card can be thought of as an employee personnel file.
-
-The *Personal Information* section lists all of the fields that are available to enter on the
-employee's card. To access this section, go to :menuselection:`Payroll --> Configuration -->
-Personal Info`.
-
-.. image:: configuration/personal-info.png
-   :align: center
-   :alt: Personal information that appear on employee cards to enter.
-
-To edit an entry, select it from the list. Then, click the :guilabel:`Edit` button, and modify the
-entry. When done, click :guilabel:`Save` or :guilabel:`Discard` to save the information or cancel
-the edits.
-
-.. image:: configuration/personal-new.png
-   :align: center
-   :alt: New personal information entry.
-
-The two most important fields on the personal info form are :guilabel:`Is Required` and
-:guilabel:`Display Type`. Checking the :guilabel:`Is Required` box makes the field mandatory on the
-employee's card.
-
-The :guilabel:`Display Type` drop-down menu allows for the information to be entered in a variety of
-ways, from a :guilabel:`Text` box, to a customizable :guilabel:`Radio` button, a
-:guilabel:`Checkbox`, a :guilabel:`Document`, and more.
-
-Once the information is entered, click the :guilabel:`Save` button to save the entry.
-
-Resume
-------
-
-.. note::
-   Currently, the :guilabel:`Resume` feature found inside the :menuselection:`Payroll app -->
-   Configuration` menu is still in development and only serves a specific use case for Belgian
-   markets. The documentation will be updated when this section has matured to more markets.

content/applications/inventory_and_mrp/inventory/barcode/operations/internal.rst

@@ -2,6 +2,8 @@
 Process to Transfers
 ====================
 
+.. _barcode/operations/intro:
+
 Simple Transfers
 ================
 

content/applications/inventory_and_mrp/inventory/barcode/setup/software.rst

@@ -2,6 +2,8 @@
 Activate the Barcodes in Odoo
 =============================
 
+.. _inventory/barcode/software:
+
 The barcode scanning features can save you a lot of time usually lost
 switching between the keyboard, the mouse and the scanner. Properly
 attributing barcodes to products, pickings locations, etc. allows you to

content/applications/inventory_and_mrp/inventory/management/products/uom.rst

@@ -2,6 +2,8 @@
 Use Different Units of Measure
 ==============================
 
+.. _inventory/management/products/units_of_measure:
+
 In some cases, handling products in different units of measure is
 necessary. For example, if you buy products in a country where the
 metric system is of application and sell in a country where the imperial