[IMP] documentation: update many2many_binary widget

The widget now also display an image preview for the files of MIME type "image".
A new option 'reverse_order' has been added to visually reverse the files order.

content/administration/on_premise.rst

@@ -61,8 +61,8 @@ To resolve the issue:
   your **network and firewall settings** allow the Odoo server to open outgoing connections
   towards:
 
-  - Odoo 18.0 and above: `services.odoo.com` on port `80`
-  - Odoo 17.0 and below: `services.openerp.com` on port `80`
+  - Odoo 18.0 and above: `services.odoo.com` on port `443` (or `80`)
+  - Odoo 17.0 and below: `services.openerp.com` on port `443` (or `80`)
 
   These ports must be kept open even after registering a database, as the update notification runs
   once a week.
@@ -85,6 +85,12 @@ To resolve the issue, either:
   displayed in the message to validate the upsell quotation and pay for the extra users.
 - :ref:`Deactivate users <users/deactivate>` and **reject** the upsell quotation.
 
+.. important::
+   If you are on a monthly subscription plan, the database will automatically update to reflect the
+   added user(s). If you are on a yearly or multi-year plan, an expiration banner will appear in the
+   database. You can create the upsell quotation by clicking the banner to update the subscription
+   or `send a support ticket <https://www.odoo.com/help>`_ to resolve the issue.
+
 Once your database has the correct number of users, the expiration message disappears automatically
 after a few days, when the next verification occurs.
 

content/administration/upgrade.rst

@@ -3,7 +3,7 @@ Upgrade
 =======
 
 An upgrade involves moving a database from an older version to a newer supported version (e.g., from
-Odoo 16.0 to Odoo 18.0). Regular upgrades are crucial as each version offers new features, bug
+Odoo 15.0 to Odoo 17.0). Regular upgrades are crucial as each version offers new features, bug
 fixes, and security patches. Using a :doc:`supported version <supported_versions>` is strongly
 recommended. Each major version is supported for three years.
 
@@ -13,11 +13,11 @@ Depending on the hosting type and Odoo version used, a database upgrade can be *
 
    .. group-tab:: Odoo Online
 
-      - If a database is on a **major version** (e.g., 16.0, 17.0, 18.0), an upgrade is mandatory
+      - If a database is on a **major version** (e.g., 15.0, 16.0, 17.0), an upgrade is mandatory
         every two years.
       - If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade is mandatory
         a few weeks after the next version is released. Minor versions are usually released every
-        two months.
+        three months.
 
    .. group-tab:: Odoo.sh
 
@@ -390,8 +390,8 @@ few exceptions.
          filestore before deploying the new version.
 
 In case of an issue with your production database, you can request the assistance of Odoo by going
-to the `Support page and selecting "An issue related to my upgrade (production)"
-<https://www.odoo.com/help?stage=post_upgrade>`_.
+to the `Support page and selecting "An issue related to my future upgrade (I am testing an upgrade)"
+<https://www.odoo.com/help?stage=migration>`_.
 
 .. _upgrade-sla:
 

content/applications/finance/accounting/customer_invoices.rst

@@ -4,251 +4,225 @@
 Customer invoices
 =================
 
-A customer invoice is a document issued by a company for products and/or services sold to a
-customer. It records receivables as they are sent to customers. Customer invoices can include
-amounts due for the goods and/or services provided, applicable sales taxes, shipping and handling
-fees, and other charges.
-Odoo supports multiple invoicing and payment workflows.
+From Customer Invoice to Payments Collection
+============================================
 
-.. seealso::
-   :doc:`/applications/finance/accounting/customer_invoices/overview`
+Odoo supports multiple invoicing and payment workflows, so you can
+choose and use the ones that match your business needs. Whether you want
+to accept a single payment for a single invoice, or process a payment
+spanning multiple invoices and taking discounts for early payments, you
+can do so efficiently and accurately.
 
-From draft invoice to profit and loss report, the process involves several steps once the goods (or
-services) have been ordered/shipped (or rendered) to a customer, depending on the invoicing policy:
+From Draft Invoice to Profit and Loss
+-------------------------------------
 
-- :ref:`accounting/invoice/creation`
-- :ref:`accounting/invoice/confirmation`
-- :ref:`accounting/invoice/sending`
-- :ref:`accounting/invoice/paymentandreconciliation`
-- :ref:`accounting/invoice/followup`
-- :ref:`accounting/invoice/reporting`
+If we pick up at the end of a typical 'order to cash' scenario, after
+the goods have been shipped, you will: issue an invoice; receive
+payment; deposit that payment at the bank; make sure the Customer
+Invoice is closed; follow up if Customers are late; and finally present
+your Income on the Profit and Loss report and show the decrease in
+Assets on the Balance Sheet report.
 
-.. _accounting/invoice/creation:
+Invoicing in most countries occurs when a contractual obligation is met.
+If you ship a box to a customer, you have met the terms of the contract
+and can bill them. If your supplier sends you a shipment, they have met
+the terms of that contract and can bill you. Therefore, the terms of the
+contract is fulfilled when the box moves to or from the truck. At this
+point, Odoo supports the creation of what is called a Draft Invoice by
+Warehouse staff.
 
 Invoice creation
-================
+----------------
 
-Draft invoices can be created directly from documents like sales orders or purchase orders or
-manually from the :guilabel:`Customer Invoices` journal in the :guilabel:`Accounting Dashboard`.
+Draft invoices can be manually generated from other documents such as
+Sales Orders, Purchase Orders,etc. Although you can create a draft
+invoice directly if you would like.
 
-An invoice must include the required information to enable the customer to pay promptly for their
-goods and services. Make sure the following fields are appropriately completed:
+An invoice must be provided to the customer with the necessary
+information in order for them to pay for the goods and services ordered
+and delivered. It must also include other information needed to pay the
+invoice in a timely and precise manner.
 
-- :guilabel:`Customer`: When a customer is selected, Odoo automatically pulls information from the
-  customer record like the invoice address,
-  :doc:`preferred payment terms <customer_invoices/payment_terms>`,
-  :doc:`fiscal positions <taxes/fiscal_positions>`, receivable account, and more onto the invoice.
-  To change these values for this specific invoice, edit them directly on the invoice. To change
-  them for future invoices, change the values on the contact record.
-- :guilabel:`Invoice Date`: If not set manually, this field is automatically set as the current date
-  upon confirmation.
-- :guilabel:`Due Date` or :doc:`payment terms <customer_invoices/payment_terms>`: To specify when
-  the customer has to pay the invoice.
-- :guilabel:`Journal`: Is automatically set and can be changed if needed.
-- :doc:`Currency <get_started/multi_currency>`
-- :guilabel:`Product`: Click :guilabel:`Add a line` to add a product.
-- :guilabel:`Quantity`
-- :guilabel:`Price`
-- :doc:`Taxes <taxes>` (if applicable)
+Draft invoices
+--------------
 
-.. tip::
-   To display the total amount of the invoice in words, go to :menuselection:`Accounting -->
-   Configuration --> Settings` and activate the :guilabel:`Total amount of invoice in letters`
-   option.
+The system generates invoice which are initially set to the Draft state.
+While these invoices remain unvalidated, they have no accounting impact within the system.
+There is nothing to stop users from creating their own draft invoices.
 
-The :guilabel:`Journal Items` tab displays the accounting entries created.
-Additional invoice information such as the :guilabel:`Customer Reference`, :doc:`Fiscal Positions
-<taxes/fiscal_positions>`, :doc:`Incoterms <customer_invoices/incoterms>`, and more can be added or
-modified in the :guilabel:`Other Info` tab.
+Let's create a customer invoice with following information:
 
-.. note::
-   Odoo initially creates invoices in :guilabel:`Draft` status. Draft invoices have no accounting
-   impact until they are :ref:`confirmed <accounting/invoice/confirmation>`.
+- Customer: Agrolait
+- Product: iMac
+- Quantity: 1
+- Unit Price: 100
+- Taxes: Tax 15%
 
-.. seealso::
-   :doc:`/applications/sales/sales/invoicing/proforma`
+.. image:: customer_invoices/invoice01.png
 
-.. _accounting/invoice/confirmation:
+.. image:: customer_invoices/invoice02.png
 
-Invoice confirmation
-====================
+The document is composed of three parts:
 
-Click :guilabel:`Confirm` when the document is completed. The document's status changes to
-:guilabel:`Posted`, and a journal entry is generated based on the invoice configuration. On
-confirmation, Odoo assigns each document a unique number from a defined
-:ref:`sequence <accounting/invoice/sequence>`.
+-  the top of the invoice, with customer information,
+-  the main body of the invoice, with detailed invoice lines,
+-  the bottom of the page, with detail about the taxes, and the totals.
 
-.. note::
-   - Once confirmed, an invoice can no longer be updated. Click :guilabel:`Reset to draft` if
-     changes are needed.
-   - If required, invoices and other journal entries can be locked once posted
-     using the :ref:`Secure posted entries with hash <data-inalterability/restricted>` feature.
+Open or Pro-forma invoices
+--------------------------
 
-.. _accounting/invoice/sending:
+An invoice will usually include the quantity and the price of goods
+and/or services, the date, any parties involved, the unique invoice
+number, and any tax information.
 
-Invoice sending
-===============
+"Validate" the invoice when you are ready to approve it. The invoice
+then moves from the Draft state to the Open state.
 
-To send the invoice to the customer, click :guilabel:`Send & Print`. A :guilabel:`Configure your
-document layout` pop-up window will appear if a :ref:`default invoice layout
-<studio/pdf-reports/default-layout>` hasn't been customized. Then, select how to send this invoice
-to the customer in the :guilabel:`Send` window.
+When you have validated an invoice, Odoo gives it a unique number from a
+defined, and modifiable, sequence.
 
-To send and print multiple invoices, go to :menuselection:`Accounting --> Customers --> Invoices`
-and select them. Then click the :icon:`fa-cog` :guilabel:`Actions` menu and select
-:guilabel:`Send & Print`. A banner will appear on the selected invoices to indicate they are part of
-an ongoing send and print batch. This helps prevent the process from being triggered manually again,
-as it may take some time to complete for exceptionally large batches.
+.. image:: customer_invoices/invoice03.png
 
-.. _accounting/invoice/paymentandreconciliation:
+Accounting entries corresponding to this invoice are automatically
+generated when you validate the invoice. You can see the details by
+clicking on the entry in the Journal Entry field in the "Other Info"
+tab.
 
-Payment and reconciliation
-==========================
+.. image:: customer_invoices/invoice04.png
 
-In Odoo, an invoice is considered :guilabel:`Paid` when the associated accounting entry has been
-reconciled with a corresponding bank transaction.
+Send the invoice to customer
+----------------------------
 
-.. seealso::
-   - :doc:`payments`
-   - :doc:`bank/reconciliation`
+After validating the customer invoice, you can directly send it to the
+customer via the 'Send by email' functionality.
 
-.. _accounting/invoice/followup:
+.. image:: customer_invoices/invoice05.png
 
-Payment follow-up
-=================
+A typical journal entry generated from a validated invoice will look
+like as follows:
 
-Odoo's :doc:`follow-up actions <payments/follow_up>` help companies follow up on customer invoices.
-Different actions can be set up to remind customers to pay their outstanding invoices, depending on
-how much the customer is overdue. These actions are bundled into follow-up levels that trigger when
-an invoice is overdue by a certain number of days. If there are multiple overdue invoices for the
-same customer, the actions are performed on the most overdue invoice.
++-----------------------+---------------+----------------+-------------+--------------+
+| **Account**           | **Partner**   | **Due date**   | **Debit**   | **Credit**   |
++=======================+===============+================+=============+==============+
+| Accounts Receivable   | Agrolait      | 01/07/2015     | 115         |              |
++-----------------------+---------------+----------------+-------------+--------------+
+| Taxes                 | Agrolait      |                |             | 15           |
++-----------------------+---------------+----------------+-------------+--------------+
+| Sales                 |               |                |             | 100          |
++-----------------------+---------------+----------------+-------------+--------------+
 
-.. _accounting/invoice/sequence:
+Payment
+-------
 
-Sequence
-========
+In Odoo, an invoice is considered to be paid when the associated
+accounting entry has been reconciled with the payment entries. If there
+has not been a reconciliation, the invoice will remain in the Open state
+until you have entered the payment.
 
-The sequence that Odoo assigns to each document is a unique number made up of a prefix and a number.
-The prefix combines the journal code and the entry date and is used to group entries by period. The
-number is unique for each period and is used to identify the entry. The default sequence on customer
-invoices is INV/YYYY/number. In some specific cases,
-:ref:`resequencing <accounting/invoice/resequencing>` invoices might be necessary.
+A typical journal entry generated from a payment will look like as
+follows:
 
-.. _accounting/invoice/resequencing:
++-----------------------+---------------+----------------+-------------+--------------+
+| **Account**           | **Partner**   | **Due date**   | **Debit**   | **Credit**   |
++=======================+===============+================+=============+==============+
+| Bank                  | Agrolait      |                | 115         |              |
++-----------------------+---------------+----------------+-------------+--------------+
+| Accounts Receivable   | Agrolait      |                |             | 115          |
++-----------------------+---------------+----------------+-------------+--------------+
 
-Resequencing
-------------
+Receive a partial payment through the bank statement
+----------------------------------------------------
 
-Resequencing is not possible:
+You can manually enter your bank statements in Odoo, or you can import
+them in from a csv file or from several other predefined formats
+according to your accounting localisation.
 
-- When entries are before a lock date.
-- When the sequence leads to a duplicate.
-- When the :guilabel:`Invoice Date` doesn't match the date contained in the new sequence number,
-  e.g., if the sequence is changed to INV/2023/XXXXX for a document with an :guilabel:`Invoice Date`
-  of 2024.
+Create a bank statement from the accounting dashboard with the related
+journal and enter an amount of $100 .
 
-To change the invoice sequence with the structure INV/YYYY/MM/number, add `/MM` with the number of
-the month of the :guilabel:`Invoice date`. Odoo will recognize the "/" term as a month and update
-the future invoice sequence appropriately with the month of the :guilabel:`Invoice date`. For
-example, if the invoice date is January, change the sequence to `INV/2024/01/XXXXX`.
+.. image:: customer_invoices/invoice06.png
 
-In this case, if the :guilabel:`Invoice date` isn't aligned with the sequence number, a
-:guilabel:`Validation Error` message appears.
+Reconcile
+---------
 
-.. note::
+Now let's reconcile!
 
-   - All sequence changes are logged in the chatter to keep the information.
-   - Sequence changes also affect the format of future invoices' sequences.
+.. image:: customer_invoices/invoice07.png
 
-.. _accounting/invoice/resequencing-one-invoice:
+You can now go through every transaction and reconcile them or you can mass reconcile with instructions at the bottom.
 
-Resequencing a single invoice
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+After reconciling the items in the sheet, the related invoice will now
+display "You have outstanding payments for this customer. You can
+reconcile them to pay this invoice. "
 
-To resequence the last confirmed invoice, click :guilabel:`Reset to Draft`, then change the
-sequence. The invoice now appears in red on the :guilabel:`Customer Invoices` list.
+.. image:: customer_invoices/invoice08.png
 
-.. _accounting/invoice/mass-resequencing:
+.. image:: customer_invoices/invoice09.png
 
-Mass-resequencing invoices
-~~~~~~~~~~~~~~~~~~~~~~~~~~
+Apply the payment. Below, you can see that the payment has been added to
+the invoice.
 
-It can be helpful to resequence multiple invoice numbers. For example, when importing invoices from
-another invoicing or accounting system and the reference originates from the previous software,
-continuity for the current year must be maintained without restarting from the beginning.
+.. image:: customer_invoices/invoice10.png
 
-.. note::
-   This feature is only available to users with administrator or advisor access.
+Payment Followup
+----------------
 
-Follow these steps to resequence invoice numbers:
+There's a growing trend of customers paying bills later and later.
+Therefore, collectors must make every effort to collect money and
+collect it faster.
 
-#. Activate the :ref:`developer mode <developer-mode>`.
-#. From the :guilabel:`Accounting Dashboard`, open the :guilabel:`Customer Invoices` journal.
-#. Select the invoices that need a new sequence.
-#. Click the :icon:`fa-cog` :guilabel:`Actions` menu and select :guilabel:`Resequence`.
-#. In the :guilabel:`Ordering` field, choose to
+Odoo will help you define your follow-up strategy. To remind customers
+to pay their outstanding invoices, you can define different actions
+depending on how severely overdue the customer is. These actions are
+bundled into follow-up levels that are triggered when the due date of an
+invoice has passed a certain number of days. If there are other overdue
+invoices for the same customer, the actions of the most overdue invoice
+will be executed.
 
-   - :guilabel:`Keep current order`: The order of the numbers remains the same.
-   - :guilabel:`Reorder by accounting date`: The number is reordered by accounting date.
-#. Set the :guilabel:`First New Sequence`.
-#. :guilabel:`Preview Modifications` and click :guilabel:`Confirm`.
+By going to the customer record and diving into the "Overdue Payments"
+you will see the follow-up message and all overdue invoices.
 
-The first invoice using the new sequence appears in red in the :guilabel:`Customer Invoices` list.
+.. image:: customer_invoices/invoice11.png
 
-.. image:: customer_invoices/invoice-sequencing.png
-   :alt: Resequence options window
+.. image:: customer_invoices/invoice12.png
 
-.. _accounting/invoice/reporting:
+.. _customer-invoices/aging-report:
 
-Reporting
-=========
+Customer aging report:
+~~~~~~~~~~~~~~~~~~~~~~
 
-.. _accounting/invoice/partner-reports:
+The customer aging report will be an additional key tool for the
+collector to understand the customer credit issues, and to prioritize
+their work.
 
-Partner reports
+Use the aging report to determine which customers are overdue and begin
+your collection efforts.
+
+.. image:: customer_invoices/invoice13.png
+
+Profit and loss
 ---------------
 
-.. _accounting/invoices/partner-ledger:
+The Profit and Loss statement displays your revenue and expense details.
+Ultimately, this gives you a clear image of your Net Profit and Loss. It
+is sometimes referred to as the "Income Statement" or "Statement of
+Revenues and Expenses."
 
-Partner Ledger
-~~~~~~~~~~~~~~
-
-The :guilabel:`Partner Ledger` report shows the balance of customers and suppliers. To access it,
-go to :menuselection:`Accounting --> Reporting --> Partner Ledger`.
-
-.. _accounting/invoices/aging-report:
-
-Aged Receivable
-~~~~~~~~~~~~~~~
-
-To review outstanding customer invoices and their related due dates, use the
-:ref:`Aged Receivable <accounting/reporting/aged-receivable>` report. To access it, go to
-:menuselection:`Accounting --> Reporting --> Aged Receivable`.
-
-.. _accounting/invoices/aged-payable:
-
-Aged Payable
-~~~~~~~~~~~~
-
-To review outstanding vendor bills and their related due dates, use the
-:ref:`Aged Payable <accounting/reporting/aged-payable>` report. To access it, go to
-:menuselection:`Accounting --> Reporting --> Aged Payable`.
-
-.. _accounting/invoices/profit-and-loss:
-
-Profit and Loss
----------------
-
-The :ref:`Profit and Loss <accounting/reporting/profit-and-loss>` statement shows details of income
-and expenses.
-
-.. _accounting/invoices/balance-sheet:
+.. image:: customer_invoices/invoice14.png
 
 Balance sheet
 -------------
 
-The :ref:`Balance Sheet <accounting/reporting/balance-sheet>` summarizes the company's assets,
-liabilities, and equity at a specific time.
+The balance sheet summarizes your company's liabilities,
+assets and equity at a specific moment in time.
+
+.. image:: customer_invoices/invoice15.png
+
+.. image:: customer_invoices/invoice16.png
+
+For example, if you manage your inventory using the perpetual accounting
+method, you should expect a decrease in account "Current Assets" once
+the material has been shipped to the customer.
 
 .. toctree::
    :titlesonly:

content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst

@@ -13,33 +13,49 @@ some governments for fiscal control or to facilitate the administration.
 Electronic invoicing of your documents such as customer invoices, credit notes or vendor bills is
 one of the application of EDI.
 
-Odoo supports e-invoicing in many countries. Refer to the country's page for more details:
+Odoo supports, among others, the following formats.
 
-- :doc:`Austria <electronic_invoicing/austria>`
-- :doc:`Belgium <electronic_invoicing/belgium>`
-- :doc:`Croatia <electronic_invoicing/croatia>`
-- :doc:`Denmark <electronic_invoicing/denmark>`
-- :doc:`Estonia <electronic_invoicing/estonia>`
-- :doc:`Finland <electronic_invoicing/finland>`
-- :doc:`France <electronic_invoicing/france>`
-- :doc:`Germany <electronic_invoicing/germany>`
-- :doc:`Hungary <electronic_invoicing/hungary>`
-- :doc:`Ireland <electronic_invoicing/ireland>`
-- :doc:`Italy <electronic_invoicing/italy>`
-- :doc:`Latvia <electronic_invoicing/latvia>`
-- :doc:`Lithuania <electronic_invoicing/lithuania>`
-- :doc:`Luxembourg <electronic_invoicing/luxembourg>`
-- :doc:`Netherlands <electronic_invoicing/netherlands>`
-- :doc:`Norway <electronic_invoicing/norway>`
-- :doc:`Poland <electronic_invoicing/poland>`
-- :doc:`Portugal <electronic_invoicing/portugal>`
-- :doc:`Romania <electronic_invoicing/romania>`
-- :doc:`Slovenia <electronic_invoicing/slovenia>`
-- :doc:`Spain <electronic_invoicing/spain>`
-- :doc:`Spain - Basque Country <electronic_invoicing/basque_country>`
+.. list-table::
+   :header-rows: 1
+
+   * - Format Name
+     - Applicability
+   * - Factur-X (CII)
+     - All customers
+   * - Peppol BIS Billing 3.0
+     - All customers
+   * - XRechnung (UBL)
+     - All customers
+   * - Fattura PA (IT)
+     - Italian companies
+   * - CFDI (4.0)
+     - Mexican companies
+   * - Peru UBL 2.1
+     - Peruvian companies
+   * - SII IVA Llevanza de libros registro (ES)
+     - Spanish companies
+   * - UBL 2.1 (Columbia)
+     - Colombian companies
+   * - Egyptian Tax Authority
+     - Egyptian companies
+   * - E-Invoice (IN)
+     - Indian companies
+   * - NLCIUS (Netherlands)
+     - Dutch companies
+   * - EHF 3.0
+     - Norwegian companies
+   * - SG BIS Billing 3.0
+     - Singaporean companies
+   * - A-NZ BIS Billing 3.0
+     - All customers
+
+.. note::
+   - The **Factur-X (CII)** format enables validation checks on the invoice and generates PDF/A-3
+     compliant files.
+   - Every PDF generated by Odoo includes an integrated **Factur-X** XML file.
 
 .. seealso::
-   :doc:`Fiscal localizations documentation <../../fiscal_localizations>`
+   :doc:`../../fiscal_localizations`
 
 .. _e-invoicing/configuration:
 

content/applications/finance/accounting/customer_invoices/electronic_invoicing/austria.rst

@@ -1,52 +0,0 @@
-:orphan:
-
-====================================
-Odoo electronic invoicing in Austria
-====================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Austria's regulatory standards, and compatible with the European `Peppol
-<https://peppol.org/about/>`_ framework.
-
-Legal framework for e-invoicing in Austria
-==========================================
-
-In Austria, businesses must adhere to e-invoicing laws that ensure secure, authentic, and storable
-transactions. The main regulation governing e-invoicing requirements in Austria is the `Austrian VAT
-Act (UStG) <https://www.ris.bka.gv.at/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10004873>`_
-and its related e-invoicing standards for public procurement (`BGBI. I Nr. 32/2019 <https://360.lexisnexis.at/d/rechtsnorm-ris/32_bundesgesetz_mit_dem_das_beamten_dienstrechtsge/b_bgbl_2019_2019_I_32_46c550bf37>`_),
-which aligns with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_.
-These laws mandate that all businesses engaged in :abbr:`B2G (business-to-government)` transactions
-must use e-invoicing, and increasingly, e-invoicing is encouraged for B2B transactions to improve
-tax compliance and transparency.
-
-Compliance with Austrian e-invoicing regulations
-================================================
-
-Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
-invoices. Here is how Odoo ensures compliance:
-
-- **Supported format**: Odoo supports standard e-invoice formats such as PDF with digital signatures
-  and XML in :abbr:`UBL (Universal Business Language)` format, which are fully compatible with
-  e-rechnung.gv.at, Austria's central electronic invoicing platform for public procurement
-  transactions. Any platform can be used if connected to the authentication services of the Federal
-  Service Portal (:abbr:`USP (Unternehmensserviceportal)`) e-rechnung.gv.at for e-invoicing
-  transmission.
-- **Secure storage and retrieval**: In accordance with the Austrian requirement to store invoices
-  for a minimum of seven years, Odoo securely archives all invoices in a tamper-proof system,
-  ensuring that they can be easily retrieved during audits.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing helps businesses stay in line with
-  Austrian VAT requirements by automatically calculating and including VAT in invoices and ensuring
-  that each invoice follows the legal format for B2B and :abbr:`B2G (business-to-government)`
-  transactions.
-
-.. seealso::
-   :doc:`Austria fiscal localization documentation <../../../fiscal_localizations/austria>`
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Austrian e-invoicing laws and how Odoo Invoicing supports
-   compliance with the Austrian VAT Act (UStG) and related regulations. It does does not constitute
-   legal advice. We recommend consulting with a tax advisor or legal professional familiar with
-   Austrian e-invoicing regulations to ensure full compliance tailored to your specific business
-   requirements.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/basque_country.rst

@@ -1,50 +0,0 @@
-:orphan:
-
-===============================================
-Odoo electronic invoicing in the Basque Country
-===============================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to meet Basque Country's regulatory standards.
-
-Legal framework for e-invoicing in the Basque Country
-=====================================================
-
-In the Basque Country, electronic invoicing is governed by Spanish national legislation and regional
-implementations, including the `Ley de Facturación Electrónica <https://www.facturae.gob.es/face/Paginas/FACE.aspx>`_
-and compliance with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_.
-For :abbr:`B2G (business-to-government)` transactions, e-invoicing is mandatory, and suppliers must
-submit e-invoices through the FACe platform or the regional system, e-Factura Euskadi, specifically
-designed for the Basque Country. These platforms ensure the secure submission of invoices to public
-administrations. While B2B e-invoicing is not yet mandatory, its use is growing, supported by the
-implementation of the TicketBAI system, which is specific to the Basque Country and promotes tax
-transparency.
-
-Compliance with Basque e-invoicing regulations
-==============================================
-
-Odoo Invoicing is fully prepared to help businesses meet the Basque Country's e-invoicing
-requirements while complying with broader Spanish and EU standards. Here is how Odoo ensures
-compliance:
-
-- **Supported formats**: Odoo supports formats such as Facturae XML, required for compliance with
-  the FACe and e-Factura Euskadi platforms. Additionally, Odoo integrates with the TicketBAI system,
-  ensuring all invoices meet the technical and legal standards for secure submission to tax
-  authorities. Odoo enables businesses to submit e-invoices seamlessly to the FACe platform for
-  national compliance and the e-Factura Euskadi system for regional public administration
-  transactions. Furthermore, Odoo supports compliance with the TicketBAI initiative, specific to the
-  Basque Country.
-- **Secure storage and retrieval**: In accordance with regulations requiring invoices to be stored
-  for a minimum of 6 years, Odoo provides a secure, tamper-proof archive for all invoices, allowing
-  easy access for audits and tax reviews.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations, ensuring
-  invoices adhere to Basque Country VAT requirements for B2G and B2B transactions while facilitating
-  compliance with the SII (Immediate Supply of Information) system for real-time VAT reporting.
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of e-invoicing laws in the Basque Country and how Odoo Invoicing
-   supports compliance with the Ley de Facturación Electrónica, e-Factura Euskadi, TicketBAI system,
-   and FACe platform. It is not intended as legal advice. We recommend consulting with a tax advisor
-   or legal professional familiar with e-invoicing regulations in the Basque Country to ensure
-   compliance tailored to your specific business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/belgium.rst

@@ -1,53 +0,0 @@
-:orphan:
-
-====================================
-Odoo electronic invoicing in Belgium
-====================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Belgium's regulatory standards, and compatible with the European `Peppol
-<https://peppol.org/about/>`_ framework.
-
-Legal framework for e-invoicing in Belgium
-==========================================
-
-In Belgium, businesses must adhere to e-invoicing laws that ensure secure, authentic, and storable
-transactions. The primary regulation governing e-invoicing requirements in Belgium is the `Belgian
-VAT Code <https://finances.belgium.be/fr/sur_le_spf/r%C3%A9glementation/r%C3%A9glementation-2023/tva>`_
-and its related `e-invoicing standards for public procurement <https://www.ejustice.just.fgov.be/cgi_loi/article.pl?language=fr&sum_date=&pd_search=2023-09-21&numac_search=2023045155&page=1&lg_txt=F&caller=list&2023045155=0&trier=promulgation&fr=f&nm_ecran=2023045155&choix1=et&choix2=et>`_,
-which align with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_.
-These laws mandate that all businesses engaged in :abbr:`B2G (business-to-government)` transactions
-must use e-invoicing via Mercurius, Belgium's official electronic invoicing platform for public
-procurement transactions. Additionally, Belgium is part of the Peppol network, which provides a
-standardized framework for cross-border e-invoicing across Europe. Increasingly, e-invoicing is also
-encouraged for B2B transactions to enhance tax compliance and transparency.
-
-Compliance with Belgian e-invoicing regulations
-===============================================
-
-Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
-invoices. Here is how Odoo ensures compliance:
-
-- **Peppol-compliant formats**: Odoo supports the standardized XML (:abbr:`UBL (Universal Business
-  Language)`) format for Peppol, ensuring compliance with both Belgian and European e-invoicing
-  standards. This ensures your invoices meet the legal requirements for public procurement in
-  Belgium and other EU countries. Odoo enables businesses to send e-invoices directly to government
-  entities in compliance with Belgian regulations through Belgium’s Mercurius platform for public
-  procurement.
-- **Secure storage and retrieval**: In accordance with Belgian requirements to store invoices for a
-  minimum of seven years, Odoo securely archives all invoices in a tamper-proof system, ensuring
-  that they can be easily retrieved during audits.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing helps businesses comply with Belgian
-  VAT requirements by automatically calculating and including VAT in invoices and ensuring that each
-  invoice follows the legal format for B2B and :abbr:`B2G (business-to-government)` transactions.
-
-.. seealso::
-   :doc:`Belgium fiscal localization documentation <../../../fiscal_localizations/belgium>`
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Belgian e-invoicing laws and how Odoo Invoicing supports
-   compliance with the Belgian VAT Code, Peppol standards, and related regulations. It does not
-   constitute legal advice. We recommend consulting with a tax advisor or legal professional
-   familiar with Belgian e-invoicing regulations to ensure full compliance tailored to your specific
-   business requirements.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/croatia.rst

@@ -1,50 +0,0 @@
-:orphan:
-
-====================================
-Odoo electronic invoicing in Croatia
-====================================
-
-Odoo Invoicing is our trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Croatia's regulatory standards.
-
-Legal framework for e-invoicing in Croatia
-==========================================
-
-In Croatia, businesses must comply with e-invoicing regulations to ensure secure, authentic, and
-storable transactions. The main legal framework governing e-invoicing in Croatia is the
-Fiscalization Act and its related requirements for public procurement, which are aligned with `EU
-Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_ on
-e-invoicing in public procurement. Under these regulations, all businesses involved in :abbr:`B2G
-(business-to-government)` transactions are required to use electronic invoicing via the :abbr:`CIS
-(Central Invoice System)`, Croatia’s official platform for public sector e-invoicing. Croatia is
-also part of the Peppol network, facilitating standardized cross-border e-invoicing within the
-European Union. Furthermore, e-invoicing is increasingly encouraged for B2B transactions, promoting
-greater transparency and tax compliance.
-
-Compliance with Croatian e-invoicing regulations
-================================================
-
-Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
-invoices. Here is how Odoo ensures compliance:
-
-- **Supported formats**: Odoo supports standard e-invoice formats, such as PDF with digital
-  signatures and XML in :abbr:`UBL (Universal Business Language)` format, which are fully compatible
-  with Croatia's :abbr:`CIS (Central Invoice System)` for public procurement transactions.
-  Additionally, Odoo enables transmission of e-invoices through any platform connected to the Peppol
-  network, as the *Servis eRačun za državu* reached via Peppol, ensuring compliance with both
-  Croatian and EU standards.
-- **Secure storage and retrieval**: In accordance with Croatian regulations to store invoices for a
-  minimum of eleven years, Odoo securely archives all invoices in a tamper-proof system, ensuring
-  they can be easily retrieved during audits.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing helps businesses stay in line with
-  Croatian VAT requirements by automatically calculating and including VAT in invoices and ensuring
-  that each invoice follows the legal format for both B2B and :abbr:`B2G (business-to-government)`
-  transactions.
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Croatian e-invoicing laws and how Odoo Invoicing supports
-   compliance with the Fiscalization Act, Peppol standards, and other relevant regulations. It does
-   not constitute legal adviceWe recommend consulting with a tax advisor or legal professional
-   familiar with Croatian e-invoicing regulations to ensure compliance tailored to your specific
-   business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/denmark.rst

@@ -1,47 +0,0 @@
-:orphan:
-
-====================================
-Odoo electronic invoicing in Denmark
-====================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Denmark's regulatory standards.
-
-Legal framework for e-invoicing in Denmark
-==========================================
-
-In Denmark, e-invoicing is governed by `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
-mandating the use of e-invoicing for :abbr:`B2G (business-to-government)` transactions. Danish
-public sector entities require invoices to be submitted through NemHandel, the national e-invoicing
-platform, using the OIOUBL format (a local version of :abbr:`UBL (Universal Business Language)` and
-XML). Denmark is also a key member of the Peppol network, enabling streamlined, standardized, and
-secure cross-border e-invoicing for transactions within the European Union. While e-invoicing is not
-mandatory for B2B transactions, its adoption is growing as businesses seek greater efficiency and
-compliance.
-
-Compliance with Danish e-invoicing regulations
-==============================================
-
-Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
-invoices. Here is how Odoo ensures compliance:
-
-- **Supported formats**: Odoo supports OIOUBL, which is required for public sector invoicing via
-  NemHandel. It also supports UBL XML for transactions through the Peppol network, ensuring
-  compatibility with Denmark’s and Europe’s e-invoicing standards. Odoo enables businesses to send
-  e-invoices through NemHandel, directly to Danish public entities in the required format. For
-  international transactions, Odoo ensures compatibility with Peppol Access Points,
-  facilitating cross-border invoicing.
-- **Secure storage and retrieval**: In line with Danish regulations, which require businesses to
-  store invoices for at least five years, Odoo securely archives all invoices in a tamper-proof
-  system, ensuring easy access for audits and compliance checks.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and
-  ensures invoices are formatted to meet Denmark’s legal requirements for B2G and B2B transactions,
-  helping businesses comply with local tax laws.
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Danish e-invoicing laws and how Odoo Invoicing supports
-   compliance with NemHandel, OIOUBL standards, Peppol standards, and other relevant regulations. It
-   does not constitute legal advice. We recommend consulting with a tax advisor or legal
-   professional familiar with Danish e-invoicing regulations to ensure compliance tailored to your
-   specific business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/estonia.rst

@@ -1,47 +0,0 @@
-:orphan:
-
-====================================
-Odoo electronic invoicing in Estonia
-====================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Estonia's regulatory standards.
-
-Legal framework for e-invoicing in Estonia
-==========================================
-
-In Estonia, businesses must comply with e-invoicing regulations to ensure secure, authentic, and
-storable transactions. The main legal framework governing e-invoicing in Estonia is the `Accounting
-Act <https://www.riigiteataja.ee/en/eli/ee/514052021001/consolide/current>`_ and its provisions
-related to e-invoicing, which align with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_
-on e-invoicing in public procurement. Since 2019, :abbr:`B2G (business-to-government)` transactions
-must use electronic invoices via Estonia's Rik's e-Invoicing System, the government's platform for
-public sector e-invoicing. Estonia is also part of the Peppol network, which ensures standardized
-cross-border e-invoicing across Europe. Additionally, the use of e-invoicing is encouraged for B2B
-transactions, promoting better transparency, efficiency, and compliance with VAT requirements.
-
-Compliance with Estonian e-invoicing regulations
-================================================
-
-Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
-invoices. Here is how Odoo ensures compliance:
-
-- **Supported formats**: Odoo supports standard e-invoice formats, such as XML in :abbr:`UBL
-  (Universal Business Language)` format, which is fully compatible with Estonia's Rik’s e-Invoicing
-  System for public procurement transactions. Additionally, Odoo enables seamless transmission of
-  e-invoices through platforms connected to the Peppol network, ensuring compliance with Estonian
-  and EU e-invoicing standards.
-- **Secure storage and retrival**: In accordance with Estonian regulations to store invoices for a
-  minimum of seven years, Odoo securely archives all invoices in a tamper-proof system, making them
-  easily retrievable during audits.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
-  invoices are formatted to meet Denmark’s legal requirements for :abbr:`B2G
-  (business-to-government)` and B2B transactions, helping businesses compliant with local tax laws.
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Estonian e-invoicing laws and how Odoo Invoicing supports
-   compliance with the Accounting Act, Peppol standards, and other relevant regulations. It does not
-   constitute legal advice. We recommend consulting with a tax advisor or legal professional
-   familiar with Estonian e-invoicing regulations to ensure compliance tailored to your specific
-   business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/finland.rst

@@ -1,47 +0,0 @@
-:orphan:
-
-====================================
-Odoo electronic invoicing in Finland
-====================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Finland's regulatory standards.
-
-Legal framework for e-invoicing in Finland
-==========================================
-
-In Finland, businesses must comply with e-invoicing regulations to ensure secure, authentic, and
-storable transactions. The primary legal framework governing e-invoicing is the `Act on Electronic
-Invoicing (241/2019) <https://www.finlex.fi/fi/laki/alkup/2019/20190241#Pidp446241968>`_, which
-aligns with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_
-on electronic invoicing in public procurement. Under Finnish law, all :abbr:`B2G
-(business-to-government)` transactions require the use of electronic invoices via Apix Messaging or
-other Peppol-connected platforms, Finland’s standard for public sector e-invoicing. Finland is also
-part of the Peppol network, ensuring interoperability and standardization for cross-border
-e-invoicing within the EU. Additionally, e-invoicing is widely adopted for B2B transactions,
-promoting efficient processes and improved tax compliance.
-
-Compliance with Finnish e-invoicing regulations
-===============================================
-
-Odoo invoicing module makes it easy for businesses to adhere to Finland's e-invoicing regulations.
-Here is how Odoo ensures compliance:
-
-- **Supported formats**: Odoo supports the e-invoicing formats widely used in Finland, including
-  TEAPPSXML, Finvoice, and the standardized XML in :abbr:`UBL (Universal Business Language)` format
-  required for Peppol compliance. This ensures compatibility with Finnish platforms such as Handi
-  for public sector invoicing and eKuitti for enhanced receipt management and e-invoicing.
-- **Secure storage and retrieval**: In accordance with Finnish regulations requiring businesses to
-  store invoices for a minimum of seven years, Odoo securely archives all invoices in a tamper-proof
-  system, allowing for easy retrieval during audits.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing ensures compliance with Finnish VAT
-  requirements by automatically calculating and including VAT in invoices and formatting them to
-  meet the legal standards for both B2B and :abbr:`B2G (business-to-government)` transactions.
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Finnish e-invoicing laws and how Odoo Invoicing supports
-   compliance with the Act on Electronic Invoicing, Peppol standards, and other relevant
-   regulations. It is not intended as legal advice. We recommend consulting with a tax advisor or
-   legal professional familiar with Finnish e-invoicing regulations to ensure compliance tailored to
-   your specific business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/france.rst

@@ -1,50 +0,0 @@
-:orphan:
-
-===================================
-Odoo electronic invoicing in France
-===================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to France's regulatory standards.
-
-Legal framework for e-invoicing in France
-=========================================
-
-In France, electronic invoicing is regulated by the `Ordonnance n° 2019-359
-<https://www.legifrance.gouv.fr/jorf/id/JORFTEXT000038410002>`_, which is aligned with `EU Directive
-2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_, and requires
-mandatory :abbr:`B2G (business-to-government)` e-invoicing through the Chorus Pro platform. Starting
-in 2024, B2B e-invoicing will be progressively implemented, becoming mandatory for all businesses by
-2026. This reform aims to combat tax fraud, improve VAT collection, and enhance business
-transparency. The Factur-X hybrid format (a combination of PDF and XML data) is widely used in
-France, ensuring compliance with both local and European e-invoicing standards.
-
-Compliance with French e-invoicing regulations
-==============================================
-
-Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
-invoices. Here is how Odoo ensures compliance:
-
-- **Supported formats**: Odoo supports the Factur-X hybrid format (PDF with embedded XML) required
-  for compliance with French e-invoicing standards. It is also compatible with :abbr:`UBL (Universal
-  Business Language)` XML for transactions via the Peppol network, facilitating both local and
-  international invoicing. Odoo enables businesses, through Chorus Pro France’s official e-invoicing
-  platform, to submit compliant e-invoices directly to public authorities and soon to private sector
-  recipients as B2B e-invoicing becomes mandatory.
-- **Secure storage and retrieval**: In compliance with French regulations, which require invoices to
-  be stored for a minimum of 10 years, Odoo securely archives all invoices in a tamper-proof system,
-  ensuring easy access for audits and inspections.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations, ensuring
-  invoices meet French VAT requirements and are formatted correctly for both B2G and B2B
-  transactions, supporting seamless compliance with evolving standards.
-
-.. seealso::
-   :doc:`France fiscal localization documentation <../../../fiscal_localizations/france>`
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of French e-invoicing laws and how Odoo Invoicing supports
-   compliance with the Chorus Pro platform, Factur-X standard, Peppol network, and other relevant
-   regulations. It does not constitute legal advice. We recommend consulting with a tax advisor or
-   legal professional familiar with French e-invoicing regulations to ensure compliance tailored to
-   your specific business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/germany.rst

@@ -1,47 +0,0 @@
-:orphan:
-
-====================================
-Odoo electronic invoicing in Germany
-====================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Germany's regulatory standards.
-
-Legal framework for e-invoicing in Germany
-==========================================
-
-In Germany, e-invoicing is governed by the `E-Rechnungsgesetz <https://www.bgbl.de/xaver/bgbl/start.xav?start=%2F%2F*%5B%40attr_id%3D%27bgbl117s0770.pdf%27%5D#__bgbl__%2F%2F*%5B%40attr_id%3D%27bgbl117s0770.pdf%27%5D__1733401471138>`_,
-which is aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
-requiring e-invoicing for all :abbr:`B2G (business-to-government)` transactions. Invoices to public
-sector entities must comply with the XRechnung format or the Peppol BIS Billing 3.0 standard.
-Submission is typically handled through platforms like :abbr:`ZRE (Zentraler Rechnungseingang)` or
-:abbr:`OZG-RE (Onlinezugangsgesetz-Rechnungseingang)`. While B2B e-invoicing is not yet mandatory,
-its adoption is increasing as businesses seek to enhance compliance, efficiency, and transparency.
-
-Compliance with German e-invoicing regulations
-==============================================
-
-Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
-invoices. Here is how Odoo ensures compliance:
-
-- **Supported formats**: Odoo supports both XRechnung (XML), the mandatory format for public sector
-  e-invoicing, and Peppol BIS Billing 3.0, enabling seamless compliance with Germany’s national and
-  European standards.
-- **Secure storage and retrieval**: In line with German regulations, which require invoices to be
-  stored for at least ten years, Odoo securely archives all invoices in a tamper-proof system,
-  ensuring they are easily accessible for audits and compliance checks.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations, ensuring
-  compliance with German VAT requirements and proper formatting for both :abbr:`B2G
-  (business-to-government)` and B2B transactions, supporting efficient reporting and legal
-  adherence.
-
-.. seealso::
-   :doc:`Germany fiscal localization documentation <../../../fiscal_localizations/germany>`
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of German e-invoicing laws and how Odoo Invoicing supports
-   compliance with E-Rechnungsgesetz, XRechnung, Peppol standards, and other relevant regulations.
-   It does not constitute legal advice. We recommend consulting with a tax advisor or legal
-   professional familiar with German e-invoicing regulations to ensure compliance tailored to your
-   specific business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/hungary.rst

@@ -1,46 +0,0 @@
-:orphan:
-
-====================================
-Odoo electronic invoicing in Hungary
-====================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Hungary's regulatory standards.
-
-Legal framework for e-invoicing in Hungary
-==========================================
-
-In Hungary, businesses must adhere to e-invoicing regulations to ensure secure, authentic, and
-storable transactions. The primary legal framework is the Hungarian VAT Act (Act CXXVII of 2007),
-which mandates real-time reporting of invoices to the NAV Online invoice system, Hungary's
-government e-invoicing platform. As of 2021, all B2B and B2C invoices must be reported in real-time,
-regardless of value. Hungary's regulations do not currently require :abbr:`B2G
-(business-to-government)` e-invoicing, but public sector invoicing is encouraged via the Peppol
-network. Common formats for e-invoicing include XML for NAV submissions and other structured formats
-to streamline compliance.
-
-Compliance with Hungarian e-invoicing regulations
-=================================================
-
-Odoo invoicing module is designed to help businesses meet Hungary's e-invoicing and VAT reporting
-requirements. Here is how Odoo ensures compliance:
-
-- **Supported Formats**: Odoo supports the standardized XML format required for integration with the
-  NAV (Nemzeti Adó és Vámhivatal) Online Invoice System, ensuring seamless real-time invoice
-  reporting. The module also supports formats compatible with Peppol for cross-border transactions,
-  promoting compliance with EU e-invoicing standards. Odoo enables businesses to automatically
-  report invoices to the Hungarian tax authorities in real-time, as required by law.
-- **Secure storage and retrieval**: In accordance with Hungarian regulations, which mandate storing
-  invoices for a minimum of eight years, Odoo securely archives all invoices in a tamper-proof
-  system, allowing for easy retrieval during audits.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
-  invoices meet the strict requirements of the Hungarian VAT Act, simplifying compliance for B2B and
-  B2C transactions.
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Hungarian e-invoicing laws and how Odoo Invoicing supports
-   compliance with the Hungarian VAT Act, NAV Online Invoice System, Peppol standards, and other
-   relevant regulations. It does not constitute legal advice. We recommend consulting with a tax
-   advisor or legal professional familiar with Hungarian e-invoicing regulations to ensure
-   compliance tailored to your specific business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/ireland.rst

@@ -1,46 +0,0 @@
-:orphan:
-
-====================================
-Odoo electronic invoicing in Ireland
-====================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Ireland's regulatory standards.
-
-Legal framework for e-invoicing in Ireland
-==========================================
-
-In Ireland, businesses must comply with e-invoicing regulations to ensure secure, authentic, and
-storable transactions. The legal framework for e-invoicing is primarily shaped by `EU Directive
-2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_, which
-mandates the use of electronic invoicing in :abbr:`B2G (business-to-government)` transactions. Irish
-public sector bodies must accept electronic invoices that comply with the European Standard EN
-16931. E-invoicing in the public sector is facilitated through the Peppol network, providing a
-streamlined and standardized platform for invoicing. While not mandatory for B2B transactions,
-e-invoicing is increasingly encouraged to enhance efficiency, transparency, and compliance.
-
-Compliance with Irish e-invoicing regulations
-=============================================
-
-Odoo Invoicing is equipped to meet Ireland's e-invoicing requirements, ensuring businesses
-can operate with confidence. Here is how Odoo ensures compliance:
-
-- **Supported formats**: Odoo supports the XML and :abbr:`UBL (Universal Business Language)` formats
-  required for Peppol compliance and ensures compatibility with the European Standard EN 16931,
-  which is the basis for public sector e-invoicing in Ireland. Odoo seamlessly integrates with the
-  Peppol network, enabling businesses to send compliant e-invoices directly to Irish public sector
-  bodies and facilitating cross-border invoicing in line with EU standards.
-- **Secure storage and retrieval**: In accordance with Irish regulations that require businesses to
-  retain invoices for a minimum of six years, Odoo securely archives all invoices in a tamper-proof
-  system, ensuring they can be easily accessed during audits or inspections.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing ensures full compliance with Irish VAT
-  regulations by automatically calculating and including VAT in invoices, while formatting them to
-  meet the legal requirements for both B2B and :abbr:`B2G (business-to-government)` transactions.
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Irish e-invoicing laws and how Odoo Invoicing supports
-   compliance with EU Directive 2014/55/EU, Peppol standards, and other relevant regulations. It
-   does not constitute legal advice. We recommend consulting with a tax advisor or legal
-   professional familiar with Irish e-invoicing regulations to ensure compliance tailored to your
-   specific business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/italy.rst

@@ -1,50 +0,0 @@
-:orphan:
-
-==================================
-Odoo electronic invoicing in Italy
-==================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Italy's regulatory standards.
-
-Legal framework for e-invoicing in Italy
-========================================
-
-Italy has one of the most advanced e-invoicing frameworks in Europe, governed by the `Italian budget
-law <https://www.gazzettaufficiale.it/eli/id/2022/12/29/22G00211/sg>`_ and regulations issued by the
-Agenzia delle Entrate. Since 2019, e-invoicing is mandatory for B2B, B2C, and :abbr:`B2G
-(business-to-government)` transactions. All e-invoices must be submitted through the :abbr:`Sdi
-(Sistema di Interscambio)`, the Italian government's centralized exchange system. The format for
-e-invoices is FatturaPA, a structured XML format specifically designed for compliance with Italian
-regulations. As part of its compliance with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
-Italy also supports Peppol standards for cross-border e-invoicing.
-
-Compliance with Italian e-invoicing regulations
-===============================================
-
-Odoo Invoicing is fully equipped to meet Italy's e-invoicing requirements. Here is how Odoo ensures
-compliance:
-
-- **Supported formats**: Odoo supports the FatturaPA XML format required by the :abbr:`Sdi (Sistema
-  di Interscambio)` for all domestic e-invoices, as well as :abbr:`UBL (Universal Business
-  Language)` XML for cross-border invoicing via the Peppol network, ensuring compliance with both
-  Italian and EU standards. Odoo has an easy access to the :abbr:`Sdi (Sistema di Interscambio)`
-  platform, allowing businesses to send, validate, and track invoices in real-time, ensuring
-  seamless compliance with Italian regulations.
-- **Secure storage and retrieval**: In accordance with Italian law, which requires invoices to be
-  stored for a minimum of ten years, Odoo securely archives all invoices in a tamper-proof system,
-  ensuring they can be easily retrieved for audits or inspections.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
-  invoices adhere to the strict formatting and reporting requirements of Italian law for B2B, B2C,
-  and :abbr:`B2G (business-to-government)` transactions.
-
-.. seealso::
-   :doc:`Italy fiscal localization documentation <../../../fiscal_localizations/italy>`
-
- .. admonition:: Disclaimer
-
-    This page provides an overview of Italian e-invoicing laws and how Odoo Invoicing supports
-    compliance with the Italian Budget Law, :abbr:`Sdi (Sistema di Interscambio)`, FatturaPA format,
-    Peppol standards, and other relevant regulations. It does not constitute legal advice. We
-    recommend consulting with a tax advisor or legal professional familiar with Italian e-invoicing
-    regulations to ensure compliance tailored to your specific business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/latvia.rst

@@ -1,45 +0,0 @@
-:orphan:
-
-===================================
-Odoo electronic invoicing in Latvia
-===================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Latvia's regulatory standards.
-
-Legal framework for e-invoicing in Latvia
-=========================================
-
-In Latvia, electronic invoicing is governed by the `Law on Accounting <https://eur-lex.europa.eu/legal-content/LV/TXT/PDF/?uri=CELEX:72014L0055LVA_270633>`_
-and regulations aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
-mandating the use of e-invoicing in :abbr:`B2G (business-to-government)` transactions. All public
-sector invoices must be sent in the European Standard EN 16931 format through platforms such as
-eInvoicing.lv, Latvia’s official e-invoicing infrastructure. Latvia is also connected to the Peppol
-network, facilitating standardized cross-border e-invoicing across the European Union.
-
-Compliance with Latvian e-invoicing regulations
-===============================================
-
-Odoo Invoicing is designed to help businesses comply with Latvia's specific e-invoicing
-requirements. Here is how Odoo ensures compliance:
-
-- **Supported formats**: Odoo supports the XML :abbr:`UBL (Universal Business Language)` format,
-  compliant with European Standard EN 16931, which is required for public sector e-invoicing in
-  Latvia. Odoo also facilitates e-invoicing through the Peppol network, ensuring seamless
-  cross-border compatibility. Odoo integrates with Latvian e-invoicing platforms, such as
-  eInvoicing.lv, allowing businesses to send compliant e-invoices directly to government entities
-  while adhering to legal standards.
-- **Secure storage and retrieval**: In accordance with Latvian regulations requiring invoices to be
-  stored for a minimum of five years, Odoo securely archives all invoices in a tamper-proof system,
-  ensuring they can be easily accessed during audits or inspections.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
-  invoices adhere to the legal requirements for :abbr:`B2G (business-to-government)` and B2B
-  transactions, helping businesses comply with Latvian VAT laws.
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Latvian e-invoicing laws and how Odoo Invoicing supports
-   compliance with the Law on Accounting, European Standard EN 16931, eInvoicing.lv, Peppol
-   standards, and other relevant regulations. It does not constitute legal advice. We recommend
-   consulting with a tax advisor or legal professional familiar with Latvian e-invoicing regulations
-   to ensure compliance tailored to your specific business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/lithuania.rst

@@ -1,46 +0,0 @@
-:orphan:
-
-======================================
-Odoo electronic invoicing in Lithuania
-======================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Lithuania's regulatory standards.
-
-Legal framework for e-invoicing in Lithuania
-============================================
-
-In Lithuania, e-invoicing is regulated under the `Law on Accounting <https://www.e-tar.lt/portal/lt/legalAct/207ad17030a011e78397ae072f58c508>`_
-and aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_
-for mandatory :abbr:`B2G (business-to-government)` e-invoicing. Businesses working with public
-sector entities must use e-invoicing, and invoices must be submitted through the E.sąskaita
-platform, Lithuania’s centralized invoicing system for public procurement. Lithuania also
-participates in the Peppol network, enabling seamless cross-border e-invoicing. While B2B
-e-invoicing is currently optional, its use is encouraged to enhance tax compliance and operational
-efficiency.
-
-Compliance with Lithuanian e-invoicing regulations
-==================================================
-
-Odoo invoicing module is fully equipped to meet Lithuania's e-invoicing requirements and ensure
-compliance with local and EU standards. Here is how Odoo ensures compliance:
-
-- **Supported formats**: Odoo supports Peppol BIS Billing 3.0 and XML formats required for
-  compliance with E.sąskaita, ensuring e-invoices meet the mandatory standards for public
-  procurement and cross-border transactions. Odoo enables businesses to send e-invoices directly to
-  public entities with Lithuania’s E.sąskaita platform. For international invoicing, Odoo supports
-  the Peppol network.
-- **Secure storage and retrieval**: In compliance with Lithuanian regulations, which require
-  invoices to be stored for a minimum of ten years, Odoo securely archives all invoices in a
-  tamper-proof system, ensuring they are accessible for audits and tax inspections.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
-  invoices meet Lithuania’s VAT requirements for both B2G and B2B transactions, reducing the risk of
-  non-compliance.
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Lithuanian e-invoicing laws and how Odoo Invoicing supports
-   compliance with the Law on Accounting, E.sąskaita platform, Peppol standards, and other relevant
-   regulations. It does not constitute legal advice. We recommend consulting with a tax advisor or
-   legal professional familiar with Lithuanian e-invoicing regulations to ensure compliance tailored
-   to your specific business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/luxembourg.rst

@@ -1,47 +0,0 @@
-:orphan:
-
-=======================================
-Odoo electronic invoicing in Luxembourg
-=======================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Luxembourg's regulatory standards.
-
-Legal framework for e-invoicing in Luxembourg
-=============================================
-
-In Luxembourg, e-invoicing is regulated in accordance with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
-requiring the use of electronic invoicing in :abbr:`B2G (business-to-government)` transactions.
-Public sector entities in Luxembourg must accept e-invoices in the European Standard EN 16931
-format. The government supports e-invoicing through the Peppol network, ensuring streamlined
-communication and compliance for cross-border transactions. While e-invoicing is not yet mandatory
-for B2B transactions, its adoption is encouraged to promote operational efficiency and tax
-compliance across industries.
-
-Compliance with Luxembourgish e-invoicing regulations
-=====================================================
-
-Odoo invoicing is equipped to support businesses in adhering to Luxembourg's e-invoicing standards.
-Here is how Odoo ensures compliance:
-
-- **Supported formats**: Odoo supports the XML :abbr:`UBL (Universal Business Language)` format,
-  compliant with European Standard EN 16931, meeting the requirements for public sector e-invoicing
-  in Luxembourg. It also facilitates e-invoicing through the Peppol network, ensuring
-  interoperability for cross-border invoicing.
-- **Secure storage and retrieval**: In line with Luxembourg’s requirement to retain invoices for a
-  minimum of ten years, Odoo securely archives all invoices in a tamper-proof system, ensuring easy
-  access during audits or inspections.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing ensures full compliance with
-  Luxembourg's VAT regulations by automating VAT calculations and formatting invoices to meet the
-  legal standards for :abbr:`B2G (business-to-government)` and B2B transactions.
-
-.. seealso::
-   :doc:`Luxembourg fiscal localization documentation <../../../fiscal_localizations/luxembourg>`
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Luxembourg's e-invoicing laws and how Odoo Invoicing supports
-   compliance with EU Directive 2014/55/EU, European Standard EN 16931, Peppol standards, and other
-   relevant regulations. It does not constitute legal advice. We recommend consulting with a tax
-   advisor or legal professional familiar with Luxembourg’s e-invoicing regulations to ensure
-   compliance tailored to your specific business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/netherlands.rst

@@ -1,46 +0,0 @@
-:orphan:
-
-============================================
-Odoo electronic invoicing in the Netherlands
-============================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to the Netherlands' regulatory standards.
-
-Legal framework for e-invoicing in the Netherlands
-==================================================
-
-In the Netherlands, e-invoicing is regulated under `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
-requiring :abbr:`B2G (business-to-government)` transactions to adhere to the European Standard EN
-16931. Public sector entities must accept e-invoices through platforms such as Digipoort, the Dutch
-government's official gateway for electronic data exchange. The Netherlands is also a prominent
-member of the Peppol network, which enables secure and standardized e-invoicing for cross-border
-transactions across Europe. While e-invoicing is not yet mandatory for B2B transactions, it is
-strongly encouraged to enhance transparency and efficiency in business processes.
-
-Compliance with Dutch e-invoicing regulations
-=============================================
-
-Odoo invoicing is equipped to support businesses with the Netherlands' e-invoicing requirements.
-Here is how Odoo ensures compliance:
-
-- **Supported formats**: Odoo supports :abbr:`UBL (Universal Business Language)` XML, which is the
-  standard format for e-invoicing in the Netherlands. It ensures compatibility with both Digipoort
-  for domestic B2G transactions and the Peppol network for international e-invoicing.
-- **Secure storage and retrieval**: In accordance with Dutch regulations, which require businesses
-  to store invoices for a minimum of seven years, Odoo securely archives all invoices in a
-  tamper-proof system, ensuring they are accessible during audits or inspections.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and formats
-  invoices to meet Dutch VAT requirements, ensuring compliance with legal standards for both
-  :abbr:`B2G (business-to-government)` and B2B transactions.
-
-.. seealso::
-   :doc:`Netherlands fiscal localization documentation <../../../fiscal_localizations/netherlands>`
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Dutch e-invoicing laws and how Odoo Invoicing supports
-   compliance with EU Directive 2014/55/EU, Digipoort, Peppol standards, and other relevant
-   regulations. It does not constitute legal advice. We recommend consulting with a tax advisor or
-   legal professional familiar with Dutch e-invoicing regulations to ensure compliance tailored to
-   your specific business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/norway.rst

@@ -1,44 +0,0 @@
-:orphan:
-
-===================================
-Odoo electronic invoicing in Norway
-===================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Norway's regulatory standards.
-
-Legal framework for e-invoicing in Norway
-=========================================
-
-In Norway, e-invoicing is governed by regulations aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
-requiring :abbr:`B2G (business-to-government)` transactions to comply with mandatory e-invoicing
-standards. Norwegian public sector entities mandate the use of the EHF (Elektronisk Handelsformat)
-standard for e-invoices, ensuring uniformity and security. Norway is a member of the Peppol network,
-which supports standardized and interoperable cross-border e-invoicing throughout Europe. Although
-not mandatory for B2B transactions, e-invoicing is widely encouraged and adopted across the private
-sector to boost efficiency, transparency, and compliance.
-
-Compliance with Norwegian e-invoicing regulations
-=================================================
-
-Odoo invoicing is designed to fully support businesses in meeting Norway's e-invoicing standards.
-Here is how Odoo ensures compliance:
-
-- **Supported formats**: Odoo supports the EHF (Elektronisk Handelsformat) standard, which is
-  required for public sector e-invoicing in Norway. Odoo is also compatible with :abbr:`UBL
-  (Universal Business Language)` XML for transactions through the Peppol network, ensuring adherence
-  to both Norwegian and EU e-invoicing requirements.
-- **Secure storage and retrieval**: In compliance with Norwegian regulations that mandate the
-  retention of invoices for a minimum of five years, Odoo securely archives all invoices in a
-  tamper-proof system, ensuring accessibility and security during audits or inspections.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations, ensuring
-  that invoices meet Norwegian VAT requirements while adhering to the correct format for both
-  :abbr:`B2G (business-to-government)` and B2B transactions.
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Norwegian e-invoicing laws and how Odoo Invoicing supports
-   compliance with the EHF standard, Peppol network, and other relevant regulations. It does not
-   constitute legal advice. We recommend consulting with a tax advisor or legal professional
-   familiar with Norwegian e-invoicing regulations to ensure compliance tailored to your specific
-   business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/poland.rst

@@ -1,45 +0,0 @@
-:orphan:
-
-===================================
-Odoo electronic invoicing in Poland
-===================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Poland's regulatory standards.
-
-Legal framework for e-invoicing in Poland
-=========================================
-
-In Poland, e-invoicing is governed by the `Polish VAT Act <https://isap.sejm.gov.pl/isap.nsf/DocDetails.xsp?id=WDU20230001598>`_
-and the National e-Invoicing System (KSeF – Krajowy System e-Faktur), which became operational in
-2022. While :abbr:`B2G (business-to-government)` e-invoicing is mandatory under `EU Directive
-2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_, B2B
-e-invoicing is mandatory for all businesses starting July 2024, following Poland's adoption of the
-e-invoicing scheme. E-invoices must be issued in the FA_VAT (structured XML) format and transmitted
-through the KSeF platform, ensuring compliance with tax reporting and transparency goals.
-
-Compliance with Polish e-invoicing regulations
-==============================================
-
-Odoo Invoicing is fully equipped to help businesses comply with Poland's evolving e-invoicing
-requirements. Here is how Odoo ensures compliance:
-
-- **Supported formats**: Odoo supports the FA_VAT (structured XML) format required for submission to
-  the KSeF platform. It also supports Peppol BIS Billing 3.0 for cross-border transactions, ensuring
-  compliance with Polish and European standards. Odoo enables businesses to issue and transmit
-  structured e-invoices to public authorities and other businesses through the KSeF platform.
-  Additionally, Odoo facilitates cross-border invoicing through the Peppol network.
-- **Secure storage and retrieval**: In accordance with Polish regulations, which require invoices to
-  be stored for at least five years, Odoo securely archives all invoices in a tamper-proof system,
-  ensuring easy access for audits and compliance checks.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
-  invoices meet Polish VAT requirements for both B2G and B2B transactions, streamlining compliance
-  and tax reporting processes.
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Polish e-invoicing laws and how Odoo Invoicing supports
-   compliance with the VAT Act, KSeF platform, Peppol standards, and other relevant regulations. It
-   does not constitute legal advice. We recommend consulting with a tax advisor or legal
-   professional familiar with Polish e-invoicing regulations to ensure compliance tailored to your
-   specific business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/portugal.rst

@@ -1,48 +0,0 @@
-:orphan:
-
-=====================================
-Odoo electronic invoicing in Portugal
-=====================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Portugal's regulatory standards.
-
-Legal framework for e-invoicing in Portugal
-===========================================
-
-In Portugal, e-invoicing is regulated under the Portuguese VAT Code and in compliance with `EU
-Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_ for
-:abbr:`B2G (business-to-government)` transactions. E-invoicing has been mandatory for public sector
-suppliers since 2021. Businesses must use structured e-invoices in the :abbr:`CIUS-PT (Customizable
-Invoice User Specification for Portugal)` format, which aligns with European standards. While B2B
-e-invoicing is not yet mandatory, its adoption is encouraged to improve tax compliance and
-efficiency. Additionally, e-invoices must be validated and certified under Portugal's SAF-T (PT)
-system, which integrates with the tax authority for reporting.
-
-Compliance with Portuguese e-invoicing regulations
-==================================================
-
-Odoo Invoicing is fully equipped to meet Portugal's e-invoicing and tax reporting requirements. Here
-is how Odoo ensures compliance:
-
-- **Supported formats**: Odoo supports the :abbr:`CIUS-PT (Customizable Invoice User Specification
-  for Portugal)` format, ensuring compatibility with Portugal's public procurement e-invoicing
-  requirements. For cross-border transactions, Odoo also supports the Peppol BIS Billing 3.0 format,
-  facilitating seamless compliance with EU standards. Integration with SAF-T (PT) and Tax Authority
-  Systems enables businesses to generate, validate, and report certified e-invoices to the tax
-  authority in compliance with local regulations.
-- **Secure storage and retrieval**: In accordance with Portuguese regulations, which require
-  invoices to be stored for at least ten years, Odoo securely archives all invoices in a
-  tamper-proof system, ensuring they are accessible for audits and inspections.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
-  that invoices meet Portuguese VAT requirements for both :abbr:`B2G (business-to-government)` and
-  B2B transactions, supporting efficient and accurate tax reporting.
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Portuguese e-invoicing laws and how Odoo Invoicing supports
-   compliance with the VAT Code, :abbr:`CIUS-PT (Customizable Invoice User Specification for
-   Portugal)` format, SAF-T (PT) system, Peppol standards, and other relevant regulations. It does
-   not constitute legal advice. We recommend consulting with a tax advisor or legal professional
-   familiar with Portuguese e-invoicing regulations to ensure compliance tailored to your specific
-   business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/romania.rst

@@ -1,54 +0,0 @@
-:orphan:
-
-====================================
-Odoo electronic invoicing in Romania
-====================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Romania's regulatory standards.
-
-Legal framework for e-invoicing in Romania
-==========================================
-
-In Romania, e-invoicing is regulated under the `Fiscal Code <http://www.dreptonline.ro/carti/start_carte.php?id_carte=324>`_
-and aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
-which mandates e-invoicing for :abbr:`B2G (business-to-government)` transactions. Romania has
-implemented the RO e-Factura system, the national platform for issuing and receiving electronic
-invoices in a standardized format. The use of RO e-Factura is mandatory for :abbr:`B2G
-(business-to-government)` transactions and for specific high-risk B2B sectors, with further
-expansion anticipated. Romania is also integrated with the Peppol network, facilitating cross-border
-e-invoicing and compliance within the European Union.
-
-Compliance with Romanian e-invoicing regulations
-================================================
-
-Odoo invoicing module is fully equipped to help businesses comply with Romania’s specific
-e-invoicing requirements. Here’s how Odoo supports compliance:
-
-- **Supported formats**: Odoo supports XML in :abbr:`UBL (Universal Business Language)` and the
-  structured formats required by RO e-Factura, ensuring compliance with Romania's e-invoicing
-  standards for B2G and high-risk B2B transactions. Additionally, Odoo supports formats compatible
-  with the Peppol network, enabling seamless cross-border invoicing. Odoo integrates with the RO
-  e-Factura system, allowing businesses to generate, validate, and submit e-invoices directly to
-  Romanian public authorities or private entities as required by law. Odoo helps businesses comply
-  with eTransport requirements by generating and managing the data necessary for reporting the
-  movement of high-fiscal risk goods. This includes shipment details such as the nature of the
-  goods, vehicle information, and delivery destinations, ensuring timely submission to the
-  :abbr:`ANAF (Romanian National Agency for Fiscal Administration)`.
-- **Secure storage and retrieval**: In compliance with Romanian regulations, which require invoices
-  to be stored for a minimum of ten years, Odoo securely archives all invoices in a tamper-proof
-  system, ensuring accessibility during audits or inspections.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and formats
-  invoices to comply with Romanian VAT requirements, ensuring accuracy and adherence to legal
-  standards for both :abbr:`B2G (business-to-government)` and B2B transactions.
-
-.. seealso::
-   :doc:`Romania fiscal localization documentation <../../../fiscal_localizations/romania>`
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Romanian e-invoicing laws and how Odoo Invoicing supports
-   compliance with the Fiscal Code, RO e-Factura, Peppol standards, and other relevant regulations.
-   It does not constitute legal advice. We recommend consulting with a tax advisor or legal
-   professional familiar with Romanian e-invoicing regulations to ensure compliance tailored to your
-   specific business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/slovenia.rst

@@ -1,45 +0,0 @@
-:orphan:
-
-=====================================
-Odoo electronic invoicing in Slovenia
-=====================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Slovenia's regulatory standards.
-
-Legal framework for e-invoicing in Slovenia
-===========================================
-
-In Slovenia, e-invoicing is regulated under the `Slovenian VAT Act <https://www.uradni-list.si/glasilo-uradni-list-rs/vsebina/2019-01-2291?sop=2019-01-2291>`_
-and complies with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
-mandating the use of e-invoices for :abbr:`B2G (business-to-government)` transactions. Suppliers to
-public sector entities must submit e-invoices in the e-SLOG XML format, which is the national
-standard for e-invoicing. These invoices are transmitted via the UJP (Uradni list Republike
-Slovenije - Agency for Public Payments) e-invoicing platform. While B2B e-invoicing remains
-optional, its adoption is encouraged to promote transparency and tax compliance.
-
-Compliance with Slovenian e-invoicing regulations
-=================================================
-
-Odoo Invoicing is fully equipped to support businesses in meeting Slovenia’s e-invoicing
-requirements. Here is how Odoo ensures compliance:
-
-- **Supported formats**: Odoo supports the e-SLOG XML format, enabling businesses to comply with
-  public procurement requirements in Slovenia. For cross-border transactions, Odoo also supports the
-  Peppol BIS Billing 3.0 format, ensuring compliance with EU standards. Odoo allows businesses to
-  send e-invoices directly to public entities in compliance with national e-invoicing regulations
-  through Slovenia’s UJP platform.
-- **Secure storage and retrieval**: In line with Slovenian regulations, which require invoices to be
-  stored for a minimum of ten years, Odoo securely archives all invoices in a tamper-proof system,
-  ensuring they are easily accessible for audits and inspections.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
-  invoices meet Slovenian VAT requirements for both B2G and B2B transactions, simplifying tax
-  reporting and ensuring accuracy.
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Slovenian e-invoicing laws and how Odoo Invoicing supports
-   compliance with the VAT Act, e-SLOG XML format, UJP platform, Peppol standards, and other
-   relevant regulations. It does not constitute legal advice. We recommend consulting with a tax
-   advisor or legal professional familiar with Slovenian e-invoicing regulations to ensure
-   compliance tailored to your specific business needs.

content/applications/finance/accounting/customer_invoices/electronic_invoicing/spain.rst

@@ -1,50 +0,0 @@
-:orphan:
-
-==================================
-Odoo electronic invoicing in Spain
-==================================
-
-Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
-solutions tailored to Spain's regulatory standards.
-
-Legal framework for e-invoicing in Spain
-========================================
-
-In Spain, e-invoicing is governed by the `Ley de Facturación Electrónica <https://www.facturae.gob.es/face/Paginas/FACE.aspx>`_
-and aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
-mandating e-invoicing for :abbr:`B2G (business-to-government)` transactions. All invoices to public
-sector entities must be submitted through the FACe platform, Spain’s official electronic invoicing
-hub, using the required Facturae format. Additionally, the :abbr:`SII (Immediate Supply of
-Information)` system mandates near real-time reporting of VAT-related invoice data for certain
-companies, reinforcing transparency and compliance. While e-invoicing is not yet mandatory for B2B
-transactions, its adoption is expected to expand in the near future.
-
-Compliance with Spanish e-invoicing regulations
-===============================================
-
-Odoo Invoicing is fully equipped to help businesses meet Spain's e-invoicing and VAT reporting
-requirements. Here is how Odoo ensures compliance:
-
-- **Supported formats**: Odoo supports the Facturae (XML) format required by the FACe platform for
-  public sector e-invoicing in Spain. It is also compatible with XML in :abbr:`UBL (Universal
-  Business Language)` formats used within the Peppol network for cross-border transactions. Odoo
-  integrates with FACe, allowing businesses to submit e-invoices directly to Spanish public
-  authorities. Odoo also facilitates compliance with the SII system, enabling automated and near
-  real-time reporting of VAT-related data to the Spanish Tax Agency.
-- **Secure storage and retrieval**: In compliance with Spanish regulations requiring invoices to be
-  stored for a minimum of four years, Odoo securely archives all invoices in a tamper-proof system,
-  ensuring easy access during audits or inspections.
-- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
-  invoices are formatted to meet Spanish requirements for both :abbr:`B2G (business-to-government)`
-  and B2B transactions, helping businesses comply with national and EU standards.
-
-.. seealso::
-   :doc:`Spain fiscal localization documentation <../../../fiscal_localizations/spain>`
-
-.. admonition:: Disclaimer
-
-   This page provides an overview of Spanish e-invoicing laws and how Odoo Invoicing supports
-   compliance with the Ley de Facturación Electrónica, FACe platform, SII system, Peppol standards,
-   and other relevant regulations. It does not constitute legal advice. We recommend consulting with
-   a tax advisor or legal professional familiar with Spanish e-invoicing regulations to ensure
-   compliance tailored to your specific business needs.

content/applications/finance/accounting/customer_invoices/payment_terms.rst

@@ -116,7 +116,7 @@ for every computed *due date*.
 This makes for easier :doc:`follow-ups </applications/finance/accounting/payments/follow_up>` and
 :doc:`reconciliation </applications/finance/accounting/bank/reconciliation>` since Odoo takes each
 due date into account, rather than just the balance due date. It also helps to get an accurate
-:ref:`aged receivable report <accounting/invoices/aging-report>`.
+:ref:`aged receivable report <customer-invoices/aging-report>`.
 
 .. example::
    .. image:: payment_terms/journal-entry.png

content/applications/finance/accounting/taxes/avatax.rst

@@ -24,8 +24,10 @@ programming interface)` integration.
 .. important::
    Some limitations exist in Odoo while using AvaTax for tax calculation:
 
-   - AvaTax uses the company address by default. To use the warehouse address, enable :doc:`Allow
-     Ship Later <../../../sales/point_of_sale/shop/ship_later>` in the **POS** app settings.
+   - AvaTax is **not** supported in Odoo's **Point of Sale** app, because a dynamic tax
+     calculation model is excessive for transactions within a single delivery address, such as
+     stores or restaurants.
+   - AvaTax and Odoo use the company address, **not** the warehouse address.
    - Excise tax is **not** supported. This includes tobacco/vape taxes, fuel taxes, and other
      specific industries.
 

content/applications/finance/fiscal_localizations.rst

@@ -4,163 +4,128 @@
 Fiscal localizations
 ====================
 
-Fiscal localizations are country-specific modules that allow you to be compliant with a country's
-fiscal requirements. Most of these modules are related to the :ref:`Accounting
-<fiscal_localizations/accounting>` or :ref:`Payroll <fiscal_localizations/payroll>` app, but they
-can also be necessary for other apps such as Point of Sale, eCommerce, etc., depending on a
-country's fiscal requirements.
-
 .. _fiscal_localizations/packages:
 
-Configuration
-=============
+Fiscal localization packages
+============================
 
-Odoo should automatically install the required fiscal localization modules based on the company's
-country when the related app is installed. Refer to the :ref:`list of countries
-<fiscal_localizations/countries-list>` to view the currently supported countries and access their
-specific documentation.
+**Fiscal Localization Packages** are country-specific modules that install pre-configured taxes,
+fiscal positions, chart of accounts, and legal statements on your database. Some additional
+features, such as the configuration of specific certificates, are also added to your Accounting app,
+following your fiscal administration requirements.
 
 .. note::
-   Each company in a multi-company environment can use different fiscal localization modules.
+   Odoo continuously adds new localizations and improves the existing packages.
 
-.. _fiscal_localizations/accounting:
+Configuration
+-------------
 
-Accounting
-----------
+Odoo automatically installs the appropriate package for your company, according to the country
+selected at the creation of the database.
 
-Verify the right package of modules is installed by going to :menuselection:`Accounting -->
-Configuration --> Settings` and checking the :guilabel:`Package` field under the :guilabel:`Fiscal
-Localization` section. Select another one if necessary.
+.. important::
+   As long as you haven't posted any entry, you can still select another package.
 
-.. warning::
-   Selecting another package is only possible if no entry has been posted.
+To select a fiscal localization package for your company, go to :menuselection:`Accounting -->
+Configuration --> Settings --> Fiscal Localization`, select the appropriate package from the list
+and save.
 
-These packages require fine-tuning the chart of accounts, activating the taxes to be used,
-configuring the country-specific statements and certifications, and sometimes more.
+.. image:: fiscal_localizations/package-selection.png
+   :alt: Select your country's fiscal localization package in Odoo Accounting.
 
-.. _fiscal_localizations/payroll:
+Use
+---
 
-Payroll
--------
+These packages require you to fine-tune your chart of accounts according to your needs, activate the
+taxes you use, and configure your country-specific statements and certifications.
 
-Localization settings can be accessed by going to :menuselection:`Payroll --> Configuration -->
-Settings` and searching for the country's **Localization** section.
+.. seealso::
+   - :doc:`accounting/get_started/chart_of_accounts`
+   - :doc:`accounting/taxes`
 
 .. _fiscal_localizations/countries-list:
 
-List of countries
-=================
+List of supported countries
+===========================
 
-Fiscal localization modules are available for the countries listed below.
+Odoo Accounting can be used in many countries out of the box by installing the appropriate module.
+Here is a list of all :ref:`fiscal localization package <fiscal_localizations/packages>` that are
+available on Odoo.
 
-.. note::
-   New countries are frequently added to this list and Odoo keeps expanding and improving existing
-   localizations and the related documentation.
-
-- Algeria
-- :doc:`Argentina <fiscal_localizations/argentina>`
-- :doc:`Australia <fiscal_localizations/australia>`
-- :doc:`Austria <fiscal_localizations/austria>`
-- Bangladesh
-- :doc:`Belgium <fiscal_localizations/belgium>`
-- Benin
-- Bolivia
-- :doc:`Brazil <fiscal_localizations/brazil>`
-- Burkina Faso
-- Bulgaria
-- Cameroon
-- :doc:`Canada <fiscal_localizations/canada>`
-- Central African Republic
-- Chad
-- :doc:`Chile <fiscal_localizations/chile>`
-- China
-- :doc:`Colombia <fiscal_localizations/colombia>`
-- Comoros
-- Congo
-- Costa Rica
-- Croatia
-- Cyprus
-- Czech Republic
-- Democratic Republic of the Congo
-- Denmark
-- Dominican Republic
-- :doc:`Ecuador <fiscal_localizations/ecuador>`
-- :doc:`Egypt <fiscal_localizations/egypt>`
-- Equatorial Guinea
-- Estonia
-- Ethiopia
-- Finland
-- :doc:`France <fiscal_localizations/france>`
-- Gabon
+- Algeria - Accounting
+- :doc:`Argentina - Accounting <fiscal_localizations/argentina>`
+- :doc:`Australian - Accounting <fiscal_localizations/australia>`
+- :doc:`Austria - Accounting <fiscal_localizations/austria>`
+- :doc:`Belgium - Accounting <fiscal_localizations/belgium>`
+- Bolivia - Accounting
+- :doc:`Brazilian - Accounting <fiscal_localizations/brazil>`
+- :doc:`Canada - Accounting <fiscal_localizations/canada>`
+- :doc:`Chile - Accounting <fiscal_localizations/chile>`
+- China - Accounting
+- :doc:`Colombia - Accounting <fiscal_localizations/colombia>`
+- Costa Rica - Accounting
+- Croatia - Accounting (RRIF 2012)
+- Czech - Accounting
+- Denmark - Accounting
+- Dominican Republic - Accounting
+- :doc:`Ecuadorian - Accounting <fiscal_localizations/ecuador>`
+- :doc:`Egypt - Accounting <fiscal_localizations/egypt>`
+- Ethiopia - Accounting
+- Finnish Localization
+- :doc:`France - Accounting <fiscal_localizations/france>`
+- Generic - Accounting
 - :doc:`Germany <fiscal_localizations/germany>`
-- Guinea
-- Greece
-- Guatemala
-- Guinea-Bissau
-- Honduras
-- :doc:`Hong Kong <fiscal_localizations/hong_kong>`
-- Hungary
-- :doc:`India <fiscal_localizations/india>`
-- :doc:`Indonesia <fiscal_localizations/indonesia>`
-- :doc:`Italy <fiscal_localizations/italy>`
-- Ivory Coast
-- Japan
-- Jordan
-- Kazakhstan
-- :doc:`Kenya <fiscal_localizations/kenya>`
-- Kuwait
-- Latvia
-- Lithuania
-- :doc:`Luxembourg <fiscal_localizations/luxembourg>`
-- Mali
-- Malta
-- Mauritius
-- :doc:`Malaysia <fiscal_localizations/malaysia>`
-- :doc:`Mexico <fiscal_localizations/mexico>`
-- Mongolia
-- Morocco
-- Mozambique
-- :doc:`Netherlands <fiscal_localizations/netherlands>`
-- :doc:`New Zealand <fiscal_localizations/new_zealand>`
-- Niger
-- Nigeria
-- Norway
-- Pakistan
-- Panama
-- :doc:`Peru <fiscal_localizations/peru>`
-- :doc:`Philippines <fiscal_localizations/philippines>`
-- Poland
-- Portugal
-- Qatar
-- :doc:`Romania <fiscal_localizations/romania>`
-- Rwanda
-- :doc:`Saudi Arabia <fiscal_localizations/saudi_arabia>`
-- Senegal
-- Serbia
-- :doc:`Singapore <fiscal_localizations/singapore>`
-- Slovakia
-- Slovenia
-- South Africa
-- :doc:`Spain <fiscal_localizations/spain>`
-- Sweden
-- :doc:`Switzerland <fiscal_localizations/switzerland>`
-- Taiwan
-- Tanzania
-- :doc:`Thailand <fiscal_localizations/thailand>`
-- Tunisia
-- Türkiye
-- Uganda
-- Ukraine
-- :doc:`United Arab Emirates <fiscal_localizations/united_arab_emirates>`
-- :doc:`United Kingdom <fiscal_localizations/united_kingdom>`
-- :doc:`United States of America <fiscal_localizations/united_states>`
-- :doc:`Uruguay <fiscal_localizations/uruguay>`
-- Venezuela
-- :doc:`Vietnam <fiscal_localizations/vietnam>`
-- Zambia
 
-.. seealso::
-   :doc:`Employment Hero Payroll documentation <fiscal_localizations/employment_hero>`
+  - Germany SKR03 - Accounting
+  - Germany SKR04 - Accounting
+
+- Greece - Accounting
+- Guatemala - Accounting
+- Honduras - Accounting
+- :doc:`Hong Kong - Accounting <fiscal_localizations/hong_kong>`
+- Hungarian - Accounting
+- :doc:`Indian - Accounting <fiscal_localizations/india>`
+- :doc:`Indonesian - Accounting <fiscal_localizations/indonesia>`
+- Ireland - Accounting
+- Israel - Accounting
+- :doc:`Italy - Accounting <fiscal_localizations/italy>`
+- Japan - Accounting
+- :doc:`Kenya - Accounting <fiscal_localizations/kenya>`
+- Lithuania - Accounting
+- :doc:`Luxembourg - Accounting <fiscal_localizations/luxembourg>`
+- :doc:`Malaysia - Accounting <fiscal_localizations/malaysia>`
+- Maroc - Accounting
+- :doc:`Mexico - Accounting <fiscal_localizations/mexico>`
+- Mongolia - Accounting
+- :doc:`Netherlands - Accounting <fiscal_localizations/netherlands>`
+- :doc:`New Zealand - Accounting <fiscal_localizations/new_zealand>`
+- Norway - Accounting
+- OHADA - Accounting
+- Pakistan - Accounting
+- Panama - Accounting
+- :doc:`Peru - Accounting <fiscal_localizations/peru>`
+- :doc:`Philippines - Accounting <fiscal_localizations/philippines>`
+- Poland - Accounting
+- Portugal - Accounting
+- :doc:`Romania - Accounting <fiscal_localizations/romania>`
+- :doc:`Saudi Arabia - Accounting <fiscal_localizations/saudi_arabia>`
+- :doc:`Singapore - Accounting <fiscal_localizations/singapore>`
+- Slovak - Accounting
+- Slovenian - Accounting
+- South Africa - Accounting
+- :doc:`Spain - Accounting (PGCE 2008) <fiscal_localizations/spain>`
+- Sweden - Accounting
+- :doc:`Switzerland - Accounting <fiscal_localizations/switzerland>`
+- Taiwan - Accounting
+- :doc:`Thailand - Accounting <fiscal_localizations/thailand>`
+- Turkey - Accounting
+- :doc:`United Arab Emirates - Accounting <fiscal_localizations/united_arab_emirates>`
+- :doc:`UK - Accounting <fiscal_localizations/united_kingdom>`
+- Ukraine - Accounting
+- :doc:`United States - Accounting <fiscal_localizations/united_states>`
+- :doc:`Uruguay - Accounting <fiscal_localizations/uruguay>`
+- Venezuela - Accounting
+- :doc:`Vietnam - Accounting <fiscal_localizations/vietnam>`
 
 .. toctree::
    :titlesonly:

content/applications/finance/fiscal_localizations/belgium.rst

@@ -449,9 +449,8 @@ This government-certified system entails the use of a :ref:`certified POS system
 Certified POS system
 --------------------
 
-The Odoo POS system is certified for the major versions of databases hosted on **Odoo Online**,
-**Odoo.sh**, and **On-Premise**. Please refer to the following table to ensure that your POS system
-is certified.
+The Odoo POS system is certified for the major versions of databases hosted on **Odoo Online** and
+**Odoo.sh**. Please refer to the following table to ensure that your POS system is certified.
 
 .. list-table::
    :header-rows: 1
@@ -461,26 +460,22 @@ is certified.
      - Odoo Online
      - Odoo.sh
      - On-Premise
-   * - Odoo 18.0
-     - Certified
-     - Certified
-     - Certified
    * - Odoo 17.0
      - Certified
      - Certified
-     - Certified
+     - Not certified
    * - Odoo 16.0
      - Certified
      - Certified
-     - Certified
+     - Not certified
    * - Odoo 15.0
      - Certified
      - Certified
-     - Certified
+     - Not certified
    * - Odoo 14.0
      - Certified
      - Certified
-     - Certified
+     - Not certified
 
 .. seealso::
    :doc:`/administration/supported_versions`

content/applications/finance/fiscal_localizations/brazil.rst

@@ -24,17 +24,6 @@ with AvaTax.
 The localization also includes taxes and a chart of accounts template that can be modified if
 needed.
 
-.. seealso::
-   Links to helpful resources for the Brazilian localization, including onboarding materials and
-   videos:
-
-   - `Onboarding checklist for new users
-     <https://docs.google.com/document/d/e/2PACX-1vSNYTYVnR_BzvQKL3kn5YdVzPjjHc-WHw_U3udk5tz_dJXo69woj9QrTMinH_siyOX2rLGjvspvc8AF/pub>`_.
-   - `YouTube playlist - Brazil (Localization)
-     <https://youtube.com/playlist?list=PL1-aSABtP6ADqexw4YNCbKPmpFggajxlX&si=RgmZR3Jco3223Np4>`_.
-   - `YouTube playlist - Tutoriais Odoo em Português
-     <https://youtube.com/playlist?list=PL1-aSABtP6ACGOW2UREePGjHQ2Bgdy-UZ&si=j6tiI36eB7BoKVQB>`_.
-
 Configuration
 =============
 

content/applications/finance/fiscal_localizations/colombia.rst

@@ -3,38 +3,23 @@ Colombia
 ========
 
 .. |DIAN| replace:: :abbr:`DIAN (Dirección de Impuestos y Aduanas Nacionales)`
-.. |NIT| replace:: :abbr:`NIT (El Número de Identificación Tributaria)`
 
 Odoo's Colombian localization package provides accounting, fiscal, and legal features for databases
-in Colombia - such as chart of accounts, taxes, and electronic invoicing. The localization has the
-following `prerequisites
-<https://micrositios.dian.gov.co/sistema-de-facturacion-electronica/que-requieres-para-factura-electronicamente/>`_
-when using the `DIAN Own Software
-<https://micrositios.dian.gov.co/sistema-de-facturacion-electronica/como-puedes-facturar-electronicamente/>`_
-solution with Odoo:
+in Colombia – such as chart of accounts, taxes, and electronic invoicing.
 
-- Be registered in the `RUT
-  <https://www.dian.gov.co/tramitesservicios/tramites-y-servicios/tributarios/Paginas/RUT.aspx>`_
-  (Registro Único Tributario) with a valid |NIT|.
-- Have a valid digital signature certificate `approved by the ONAC
-  <https://onac.org.co/directorio-de-acreditados/>`_.
-- `Register and get enabled
-  <https://micrositios.dian.gov.co/sistema-de-facturacion-electronica/proceso-de-registro-y-habilitacion-como-facturador-electronico/>`_
-  by completing the certification process required by the |DIAN|.
+In addition, a series of videos on the subject is also available. These videos cover how to start
+from scratch, set up configurations, complete common workflows, and provide in-depth looks at some
+specific use cases as well.
 
 .. seealso::
-   - For more information on how to complete the certification process for the |DIAN| module, review
-     the following `webinar <https://www.youtube.com/watch?v=l0G6iDc7NQA>`_.
-   - `Smart Tutorial - Colombian Localization
-     <https://www.odoo.com/slides/smart-tutorial-localizacion-de-colombia-132>`_.
+   `Smart Tutorial - Colombian Localization
+   <https://www.odoo.com/slides/smart-tutorial-localizacion-de-colombia-132>`_.
 
-.. _localization/colombia/configuration:
+.. _colombia/configuration:
 
 Configuration
 =============
 
-.. _localization/colombia/modules:
-
 Modules installation
 --------------------
 
@@ -53,148 +38,155 @@ localization:
      - Default :ref:`fiscal localization package <fiscal_localizations/packages>`. This module adds
        the base accounting features for the Colombian localization: chart of accounts, taxes,
        withholdings, and identification document type.
-   * - :guilabel:`Electronic invoicing for Colombia with DIAN`
-     - `l10n_co_dian`
-     - This module includes the features required for integration with the |DIAN| as its own
-       software, and adds the ability to generate electronic invoices and support documents based on
-       |DIAN| regulations.
    * - :guilabel:`Colombian - Accounting Reports`
      - `l10n_co_reports`
-     - This module includes accounting reports for sending certifications to suppliers for
-       withholdings applied.
+     - Includes accounting reports for sending certifications to suppliers for withholdings applied.
    * - :guilabel:`Electronic invoicing for Colombia with Carvajal`
      - `l10n_co_edi`
-     - This module includes the features required for integration with Carvajal. Adds the ability to
-       generate the electronic invoices and support documents, based on |DIAN| regulations.
+     - This module includes the features required for integration with Carvajal, and
+       generates the electronic invoices and support documents related to the vendor bills, based on
+       |DIAN| regulations.
    * - :guilabel:`Colombian - Point of Sale`
      - `l10n_co_pos`
-     - This module includes **Point of Sale** receipts for Colombian localization.
-
-.. _localization/colombia/configuration/company:
-
-Company information
--------------------
-
-To configure your company information:
-
-#. Access your company's contact form:
-
-   - Go to the :guilabel:`Contacts` app and search for your company or;
-   - Go to the :guilabel:`Settings` app, activate the :ref:`developer mode <developer-mode>`, and in
-     the :guilabel:`Companies` section, click :guilabel:`Update Info`. Then, in the
-     :guilabel:`Contact` field, click on the company name.
-
-#. Configure the following information:
-
-   - :guilabel:`Company Name`.
-   - :guilabel:`Address`: Including :guilabel:`City`, :guilabel:`Department`, and :guilabel:`ZIP`
-     code.
-   - :guilabel:`Identification Number`: Select the :guilabel:`Identification Type` (:guilabel:`NIT`,
-     :guilabel:`Cédula de Ciudadanía`, :guilabel:`Registro Civil`, etc.). When the
-     :guilabel:`Identification Type` is :guilabel:`NIT`, the
-     :guilabel:`Identification Number` **must** have the *verification digit* at the end of the ID
-     prefixed by a hyphen (`-`).
-
-#. Go to the :guilabel:`Sales & Purchase` tab and configure the :guilabel:`Fiscal Information`:
-
-   - :guilabel:`Obligaciones y Responsabilidades`: Select the fiscal responsibility for the company.
-     (:guilabel:`O-13` Gran Contribuyente, :guilabel:`O-15` Autorretenedor,
-     :guilabel:`O-23` Agente de retención IVA, :guilabel:`O-47` Regimen de tributación simple,
-     :guilabel:`R-99-PN` No Aplica).
-   - :guilabel:`Gran Contribuyente`: If the company is *Gran Contribuyente*, enable this option.
-   - :guilabel:`Fiscal Regimen`: Select the Tribute Name for the company (:guilabel:`IVA`,
-     :guilabel:`INC`, :guilabel:`IVA e INC`, or :guilabel:`No Aplica`)
-   - :guilabel:`Commercial Name`: If the company uses a specific commercial name and it needs to be
-     displayed in the invoice.
-
-.. tip::
-   The data configured in the :guilabel:`Fiscal Information` section is printed in the valid fiscal
-   PDF reports.
-
-.. _localization/colombia/einvoice-configuration:
-
-Electronic invoicing credentials and |DIAN| environment
--------------------------------------------------------
-
-To configure the user credentials to be used to connect with the |DIAN|'s web service and the
-|DIAN| environment, navigate to :menuselection:`Accounting --> Configuration --> Settings` and
-scroll to the :guilabel:`Colombian Electronic Invoicing` section. Then, follow these steps:
-
-#. Select :guilabel:`DIAN: Free Service` as the :guilabel:`Electronic Invoicing Provider`.
-#. Configure the :guilabel:`Operation Modes` for the respective types of documents
-   (*electronic invoices* or *support documents*) to be generated from Odoo. Click
-   :guilabel:`Add a line`, then fill in the fields:
-
-   - :guilabel:`Software Mode`: the type of document to be generated with the operation mode.
-   - :guilabel:`Software ID`: the ID generated by |DIAN| for the specific operation mode.
-   - :guilabel:`Software PIN`: the PIN selected in the operation mode configuration in the |DIAN|
-     portal.
-   - :guilabel:`Testing ID`: the testing ID generated by |DIAN| and obtained after testing the
-     operation mode.
-
-#. Configure the available :guilabel:`Certificates` to sign the electronic documents. Click
-   :guilabel:`Add a line`, then fill in the fields:
-
-   - :guilabel:`Name`: the name of the certificate.
-   - :guilabel:`Certificate`: upload the certificate file in PEM format. In the :guilabel:`Private
-     Key` field that appears on the screen, select an existing private key or create a new one. To
-     do so, enter a key name and select :guilabel:`Create and edit`. Then, in the :guilabel:`Create
-     Private Key` wizard, upload a valid :guilabel:`Key file` and click :guilabel:`Save & Close`.
-
-     .. image:: colombia/dian-credentials-configuration.png
-        :alt: Colombian electronic invoicing credentials configured.
-
-#. Configure the |DIAN| environment; the |DIAN| electronic invoicing module offers three different
-   |DIAN| environments to connect with:
-
-   - **Certification environment**: This environment is useful to pass the |DIAN| certification
-     process and obtain the *Enabled* status to invoice from Odoo. To activate it, enable both the
-     :guilabel:`Test environment` and the :guilabel:`Activate the certification process` checkboxes.
-
-   - **Testing environment**: This environment allows reproducing electronic invoicing flows
-     and validations in the |DIAN| testing portal. To activate it, enable only the :guilabel:`Test
-     Environment` checkbox.
-
-   - **Production environment**: Activate production databases to generate valid electronic documents.
-     To activate it, disable both the :guilabel:`Test environment` and the :guilabel:`Activate the
-     certification process` checkboxes.
+     - Includes Point of Sale receipts for Colombian localization.
 
 .. note::
-   In a multi-company database, each company can have its own certificate.
+   When `Colombia` is selected for a company's :guilabel:`Fiscal Localization`, Odoo automatically
+   installs certain modules.
 
-.. seealso::
-   For electronic invoicing configurations using the Carvajal solution, review the following video:
-   `Configuración de Facturación Electrónica - Localización de Colombia
-   <https://www.youtube.com/watch?v=bzweMwTEbfY&list=PL1-aSABtP6ABxZshems3snMjx7bj_7ZsZ&index=3>`_.
+Company configuration
+---------------------
 
-.. _localization/colombia/master-data:
+To configure your company information, go to the :menuselection:`Contacts` app, and search for your
+company.
 
-Master data
------------
+Alternatively, activate :ref:`developer mode <developer-mode>` and navigate to
+:menuselection:`General Setting --> Company --> Update Info --> Contact`. Then, edit the contact
+form and configure the following information:
 
-.. _localization/colombia/contacts:
+- :guilabel:`Company Name`.
+- :guilabel:`Address`: Including :guilabel:`City`, :guilabel:`Department` and :guilabel:`ZIP` code.
+- :guilabel:`Identification Number`: Select the :guilabel:`Identification Type` (`NIT`, `Cédula de
+  Ciudadanía`, `Registro Civil`, etc.). When the :guilabel:`Identification Type` is `NIT`, the
+  :guilabel:`Identification Number` **must** have the *verification digit* at the end of the ID
+  prefixed by a hyphen (`-`).
 
-Contacts
-~~~~~~~~
+Next, configure the :guilabel:`Fiscal Information` in the :guilabel:`Sales & Purchase` tab:
 
-Configure the following fields on the :doc:`contact form <../../essentials/contacts>`:
+- :guilabel:`Obligaciones y Responsabilidades`: Select the fiscal responsibility for the company
+  (`O-13` Gran Contribuyente, `O-15` Autorretenedor, `O-23` Agente de retención IVA, `O-47` Regimen
+  de tributación simple, `R-99-PN` No Aplica).
+- :guilabel:`Gran Contribuyente`: If the company is *Gran Contribuyente* this option should be
+  selected.
+- :guilabel:`Fiscal Regimen`: Select the Tribute Name for the company (`IVA`, `INC`, `IVA e INC`,
+  or `No Aplica`)
+- :guilabel:`Commercial Name`: If the company uses a specific commercial name, and it needs to be
+  displayed in the invoice.
 
-- :guilabel:`Identification Number` (VAT): Select the identification number type and enter the
-  identification number. If the identification number type is :guilabel:`NIT`, the identification
-  number must include the verification digit at the end, prefixed by a hyphen (`-`).
-- :ref:`Fiscal Information fields <localization/colombia/configuration/company>` in the
-  :guilabel:`Sales & Purchase` tab.
+Carjaval credentials configuration
+----------------------------------
 
-.. _localization/colombia/products:
+Once the modules are installed, the user credentials **must** be configured, in order to connect
+with Carvajal Web Service. To do so, navigate to :menuselection:`Accounting --> Configuration -->
+Settings` and scroll to the :guilabel:`Colombian Electronic Invoicing` section. Then, fill in the
+required configuration information provided by Carvajal:
+
+- :guilabel:`Username` and :guilabel:`Password`: Username and password (provided by Carvajal) to the
+  company.
+- :guilabel:`Company Registry`: Company's NIT number *without* the verification code.
+- :guilabel:`Account ID`: Company's NIT number followed by `_01`.
+- :guilabel:`Colombia Template Code`: Select one of the two available templates (`CGEN03` or
+  `CGNE04`) to be used in the PDF format of the electronic invoice.
+
+Enable the :guilabel:`Test mode` checkbox to connect with the Carvajal testing environment.
+
+Once Odoo and Carvajal are fully configured and ready for production, deactivate the :guilabel:`Test
+mode` checkbox to use the production database.
+
+.. image:: colombia/carvajal-configuration.png
+   :align: center
+   :alt: Configure credentials for Carvajal web service in Odoo.
+
+.. important::
+   :guilabel:`Test mode` must **only** be used on duplicated databases, **not** the production
+   environment.
+
+Report data configuration
+-------------------------
+
+Report data can be defined for the fiscal section and bank information of the PDF as part of the
+configurable information sent in the XML.
+
+Navigate to :menuselection:`Accounting --> Configuration --> Settings`, and scroll to the
+:guilabel:`Colombian Electronic Invoicing` section, in order to find the :guilabel:`Report
+Configuration` fields. Here the header information for each report type can be configured.
+
+- :guilabel:`Gran Contribuyente`
+- :guilabel:`Tipo de Régimen`
+- :guilabel:`Retenedores de IVA`
+- :guilabel:`Autorretenedores`
+- :guilabel:`Resolución Aplicable`
+- :guilabel:`Actividad Económica`
+- :guilabel:`Bank Information`
+
+.. _colombia/master-data:
+
+Master data configuration
+-------------------------
+
+Partner
+~~~~~~~
+
+Partner contacts can be created in the *Contacts* app. To do so, navigate to
+:menuselection:`Contacts`, and click the :guilabel:`Create` button.
+
+Then, name the contact, and using the radio buttons, select the contact type, either
+:guilabel:`Individual` or :guilabel:`Company`.
+
+Complete the full :guilabel:`Address`, including the :guilabel:`City`, :guilabel:`State`, and
+:guilabel:`ZIP` code. Then, complete the identification and fiscal information.
+
+Identification information
+**************************
+
+Identification types, defined by the |DIAN|, are available on the partner form, as part of the
+Colombian localization. Colombian partners **must** have their :guilabel:`Identification Number`
+(VAT) and :guilabel:`Document Type` set.
+
+.. tip::
+   When the :guilabel:`Document Type` is `NIT`, the :guilabel:`Identification Number` needs to be
+   configured in Odoo, including the *verification digit at the end of the ID, prefixed by a hyphen
+   (`-`)*.
+
+Fiscal information
+******************
+
+The partner's responsibility codes (section 53 in the :abbr:`RUT (Registro único tributario)`
+document) are included as part of the electronic invoicing module, as it is required by the |DIAN|.
+
+The required fields can be found under :menuselection:`Partner --> Sales & Purchase Tab --> Fiscal
+Information section`:
+
+- :guilabel:`Obligaciones y Responsabilidades`: Select the fiscal responsibility for the company
+  (`O-13` Gran Contribuyente, `O-15` Autorretenedor, `O-23` Agente de retención IVA, `O-47` Regimen
+  de tributación simple, or `R-99-PN` No Aplica).
+- :guilabel:`Gran Contribuyente`: If the company is *Gran Contribuyente* this option should be
+  selected.
+- :guilabel:`Fiscal Regimen`: Select the tribute name for the company (`IVA`, `INC`, `IVA e INC`, or
+  `No Aplica`)
+- :guilabel:`Commercial Name`: If the company uses a specific commercial name, and it needs to be
+  displayed in the invoice.
 
 Products
 ~~~~~~~~
 
-Access the product's form via :menuselection:`Accounting --> Customers --> Products` and ensure
-that either the :guilabel:`UNSPSC Category` field (found in the :guilabel:`Accounting tab`) or the
-:guilabel:`Internal Reference` field (in the :guilabel:`General Information` tab) is configured.
+To manage products, navigate to :menuselection:`Accounting --> Customers --> Products`, then click
+on a product.
 
-.. _localization/colombia/taxes:
+When adding general information on the product form, it is required that either the
+:guilabel:`UNSPSC Category` (:guilabel:`Accounting` tab), or :guilabel:`Internal Reference`
+(:guilabel:`General Information` tab) field is configured. Be sure to :guilabel:`Save` the product
+once configured.
 
 Taxes
 ~~~~~
@@ -202,103 +194,91 @@ Taxes
 To create or modify taxes, go to :menuselection:`Accounting --> Configuration --> Taxes`, and select
 the related tax.
 
-If sales transactions include products with taxes, configure the :guilabel:`Value Type` field in the
-:guilabel:`Advanced Options` tab. Retention tax types (:guilabel:`ICA`, :guilabel:`IVA`,
-:guilabel:`Fuente`) are also included. This configuration is used to display taxes correctly on the
-invoice.
+If sales transactions include products with taxes, the :guilabel:`Value Type` field in the
+:guilabel:`Advanced Options` tab needs to be configured per tax. Retention tax types
+(:guilabel:`ICA`, :guilabel:`IVA`, :guilabel:`Fuente`) are also included. This configuration is used
+to display taxes correctly in the invoice PDF.
 
-.. image:: colombia/dian-taxes-configuration.png
-   :alt: Specific tax configurations per DIAN regulations.
+.. image:: colombia/retention-tax-types.png
+   :align: center
+   :alt: The ICA, IVA and Fuente fields in the Advanced Options tab in Odoo.
 
-.. _localization/colombia/co-journals:
+.. _co-journals:
 
 Sales journals
 ~~~~~~~~~~~~~~
 
 Once the |DIAN| has assigned the official sequence and prefix for the electronic invoice resolution,
-the sales journals related to the invoices **must** be updated in Odoo. To do so, navigate
-to :menuselection:`Accounting --> Configuration --> Journals` and select an existing sales journal
+the sales journals related to the invoice documents **must** be updated in Odoo. To do so, navigate
+to :menuselection:`Accounting --> Configuration --> Journals`, and select an existing sales journal,
 or create a new one with the :guilabel:`Create` button.
 
-On the sales journal form, enter the :guilabel:`Journal Name` and :guilabel:`Type`, then set a
-unique :guilabel:`Short Code` in the :guilabel:`Journals Entries` tab. Then, configure the following
-data in the :guilabel:`Advanced Settings` tab:
+On the sales journal form, input the :guilabel:`Journal Name`, :guilabel:`Type`, and set a unique
+:guilabel:`Short Code` in the :guilabel:`Journals Entries` tab. Then, configure the following data
+in the :guilabel:`Advanced Settings` tab:
 
-- :guilabel:`Electronic invoicing`: enable UBL 2.1 (Colombia).
-- :guilabel:`Invoicing Resolution`: resolution number issued by |DIAN| to the company via their test
-  set.
-- :guilabel:`Resolution Date`: initial effective date of the resolution.
-- :guilabel:`Resolution End Date`: end date of the resolution's validity.
-- :guilabel:`Range of Numbering (minimum)`: first authorized invoice number.
-- :guilabel:`Range of Numbering (maximum)`: last authorized invoice number.
-- :guilabel:`Technical Key`: control key received from the |DIAN| portal test set or from their web
-  service in case of the production environment.
+- :guilabel:`Electronic invoicing`: Enable :guilabel:`UBL 2.1 (Colombia)`.
+- :guilabel:`Invoicing Resolution`: Resolution number issued by |DIAN| to the company.
+- :guilabel:`Resolution Date`: Initial effective date of the resolution.
+- :guilabel:`Resolution end date`: End date of the resolution's validity.
+- :guilabel:`Range of Numbering (minimum)`: First authorized invoice number.
+- :guilabel:`Range of Numbering (maximum)`: Last authorized invoice number.
 
-When the database is configured for the :ref:`production environment
-<localization/colombia/einvoice-configuration>`, instead of configuring these fields manually,
-click the :guilabel:`Reload DIAN configuration` button to obtain the |DIAN| resolution information
-from the |DIAN| web service.
+.. note::
+   The sequence and resolution of the journal **must** match the one configured in Carvajal and the
+   |DIAN|.
 
-.. image:: colombia/reload-dian-configuration-button.png
-   :alt: Reload DIAN configuration button in sale journals.
+Invoice sequence
+****************
 
-.. important::
-   - The short code and resolution of the journal **must** match the ones received in the |DIAN|
-     portal test set or from the MUISCA portal.
-   - The :ref:`invoice sequence and prefix <localization/colombia/invoice-creation>` **must** be
-     correctly configured when the first invoice is created. Odoo automatically assigns a prefix
-     and sequence to the following invoices.
+The invoice sequence and prefix **must** be correctly configured when the first document is created.
 
-.. _localization/colombia/purchase-journals:
+.. note::
+   Odoo automatically assigns a prefix and sequence to the following invoices.
 
 Purchase journals
-~~~~~~~~~~~~~~~~~
+*****************
 
 Once the |DIAN| has assigned the official sequence and prefix for the *support document* related to
 vendor bills, the purchase journals related to their supporting documents need to be updated in
-Odoo. The process is similar to the configuration of the :ref:`sales journals
-<localization/colombia/co-journals>`.
-
-.. seealso::
-   For more information on support document journals using the Carvajal solution, review the
-   `Documento Soporte - Localización de Colombia video
-   <https://www.youtube.com/watch?v=UmYsFcD7xzE&list=PL1-aSABtP6ABxZshems3snMjx7bj_7ZsZ&index=8>`_.
-
-.. _localization/colombia/chart-of-accounts:
+Odoo. The process is similar to the configuration of the :ref:`sales journals <co-journals>`.
 
 Chart of accounts
-~~~~~~~~~~~~~~~~~
+*****************
 
 The :doc:`chart of accounts </applications/finance/accounting/get_started/chart_of_accounts>` is
-installed by default as part of the localization module. The accounts are mapped automatically in
+installed by default as part of the localization module, the accounts are mapped automatically in
 taxes, default account payable, and default account receivable. The chart of accounts for Colombia
 is based on the PUC (Plan Unico de Cuentas).
 
-.. _localization/colombia/workflows:
+.. _colombia/workflows:
 
 Main workflows
 ==============
 
-.. _localization/colombia/electronic-invoices:
-
 Electronic invoices
 -------------------
 
 The following is a breakdown of the main workflow for electronic invoices with the Colombian
 localization:
 
-#. The user creates an invoice.
-#. Odoo generates the legal XML file.
-#. Odoo generates the CUFE (Invoice Electronic Code) with the electronic signature.
-#. Odoo sends a notification to DIAN.
+#. Sender creates an invoice.
+#. Electronic invoice provider generates the legal XML file.
+#. Electronic invoice provider creates the CUFE (Invoice Electronic Code) with the electronic
+   signature.
+#. Electronic invoice provider sends a notification to |DIAN|.
 #. |DIAN| validates the invoice.
 #. |DIAN| accepts or rejects the invoice.
-#. Odoo generates the PDF invoice with a QR code.
-#. Odoo compresses the attached document (containing the sent XML file and the DIAN validation
-   response) and the fiscal valid PDF into a :file:`.zip` file.
-#. The user sends the invoice (:file:`.zip` file) via Odoo to the acquirer.
+#. Electronic invoice provider generates the PDF invoice with a QR code.
+#. Electronic invoice provider sends invoice to the acquirer.
+#. Acquirer sends a receipt of acknowledgement, and accepts or rejects the invoice.
+#. Sender downloads a :file:`.zip` file with the PDF and XML.
 
-.. _localization/colombia/invoice-creation:
+.. image:: colombia/workflow-electronic-invoice.png
+   :align: center
+   :alt: Electronic invoice workflow for Colombian localization.
+
+.. _colombia/invoice-creation:
 
 Invoice creation
 ~~~~~~~~~~~~~~~~
@@ -307,62 +287,58 @@ Invoice creation
    The functional workflow taking place before an invoice validation does **not** alter the main
    changes introduced with the electronic invoice.
 
-Electronic invoices are generated and sent to both the |DIAN| and the customer. These documents can
-be created from the sales order or manually generated. To create a new invoice, go to
-:menuselection:`Accounting --> Costumers --> Invoices`, and select :guilabel:`Create`. On the
-invoice form, configure the following fields:
+Electronic invoices are generated and sent to both the |DIAN| and customer through Carvajal's web
+service integration. These documents can be created from your sales order or manually generated. To
+create a new invoice, go to :menuselection:`Accounting --> Customers --> Invoices`, and select
+:guilabel:`Create`. On the invoice form configure the following fields:
 
-- :guilabel:`Customer`: customer's information.
-- :guilabel:`Journal`: journal used for electronic invoices.
+- :guilabel:`Customer`: Customer's information.
+- :guilabel:`Journal`: Journal used for electronic invoices.
 - :guilabel:`Electronic Invoice Type`: Select the type of document. By default, :guilabel:`Factura
   de Venta` is selected.
 - :guilabel:`Invoice Lines`: Specify the products with the correct taxes.
 
-.. important::
-   When creating the first invoice related to an electronic invoicing journal, it is required to
-   manually change the *sequence* of the invoice to the |DIAN| format: `Prefix + Sequence`.
-
-   For example, format the sequence from `SETP/2024/00001` to `SETP1`.
-
 When done, click :guilabel:`Confirm`.
 
-.. _localization/colombia/send-electronic-invoice:
+.. _colombia/invoice-validation:
 
-Electronic invoice sending
-~~~~~~~~~~~~~~~~~~~~~~~~~~
+Invoice validation
+~~~~~~~~~~~~~~~~~~
 
-After the :ref:`invoice confirmation <localization/colombia/invoice-creation>`, click
-:guilabel:`Print & Send`. In the wizard that appears, make sure to enable the :guilabel:`DIAN` and
-:guilabel:`Email` checkboxes to send an XML to the |DIAN| web service and the validated invoice to
-the client fiscal email and click :guilabel:`Print & Send`. Then:
+After the invoice confirmation, an XML file is created and sent automatically to Carvajal. The
+invoice is then processed asynchronously by the E-invoicing service UBL 2.1 (Colombia). The file is
+also displayed in the chatter.
 
-- The XML document is created.
-- The CUFE is generated.
-- The XML is processed synchronously by the |DIAN|.
-- If accepted, the file is displayed in the chatter and the email to the client with the
-  corresponding :file:`.zip` file.
+.. image:: colombia/invoice-sent.png
+   :align: center
+   :alt: Carvajal XML invoice file in Odoo chatter.
 
-.. image:: colombia/zip-xml-chatter-colombia.png
-   :alt: EDI documents available in the chatter.
+The :guilabel:`Electronic Invoice Name` field is now displayed in the :guilabel:`EDI Documents` tab,
+with the name of the XML file. Additionally, the :guilabel:`Electronic Invoice Status` field is
+displayed with the initial value :guilabel:`To Send`. To process the invoice manually, click on the
+:guilabel:`Process Now` button.
 
-The :guilabel:`DIAN` tab then displays the following:
+.. _colombia/invoice-xml:
 
-- :guilabel:`Signed Date`: timestamp recorded of the XML creation.
-- :guilabel:`Status`: Status result obtained in the |DIAN| response. If the invoice was
-  rejected, the error messages can be seen here.
-- :guilabel:`Testing Environment`: To know if the document sent was delivered to the |DIAN| testing
-  environment.
-- :guilabel:`Certification Process`: To know if the document was sent as part of the certification
-  process with the |DIAN|.
-- :guilabel:`Download`: To download the sent XML file, even if the |DIAN| result was
-  rejected.
-- :guilabel:`Fetch Attached Document`: To download the generated attached document file included in
-  the delivered :file:`.zip` file to the client.
+Reception of legal XML and PDF
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. image:: colombia/dian-tab-electronic-document.png
-   :alt: EDI document record available in DIAN tab.
+The electronic invoice vendor (Carvajal) receives the XML file, and proceeds to validate its
+structure and information.
 
-.. _localization/colombia/credit-notes:
+After validating the electronic invoice, 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. If everything is correct the :guilabel:`Electronic Invoicing` field value changes to
+:guilabel:`Sent`.
+
+A :file:`.zip` containing the legal electronic invoice (in XML format) and the invoice in (PDF
+format) is downloaded and displayed in the invoice chatter:
+
+.. image:: colombia/invoice-zip.png
+   :align: center
+   :alt: ZIP file displayed in the invoice chatter in Odoo.
+
+The electronic invoice status changes to :guilabel:`Accepted`.
 
 Credit notes
 ------------
@@ -388,8 +364,6 @@ an invoice, go to :menuselection:`Accounting --> Customers --> Invoices`. On the
 
 Once reviewed, click the :guilabel:`Reverse` button.
 
-.. _localization/colombia/debit-notes:
-
 Debit notes
 -----------
 
@@ -406,8 +380,6 @@ invoice, go to :menuselection:`Accounting --> Customers --> Invoices`. On the in
 
 When done, click :guilabel:`Create Debit Note`.
 
-.. _localization/colombia/support-document:
-
 Support document for vendor bills
 ---------------------------------
 
@@ -425,34 +397,26 @@ Support documents for vendor bills can be created from your purchase order or ma
 Once reviewed, click the :guilabel:`Confirm` button. Upon confirmation, an XML file is created and
 automatically sent to Carvajal.
 
-.. _localization/colombia/common-errors:
+.. _colombia/common-errors:
 
 Common errors
 -------------
 
-During the XML validation, the most common errors are related to missing :ref:`master data
-<localization/colombia/master-data>`. In such cases, a validation error message is displayed and
-sending is blocked.
+During the XML validation, the most common errors are related to missing master data (*Contact Tax
+ID*, *Address*, *Products*, *Taxes*). In such cases, error messages are shown in the chatter after
+updating the electronic invoice status.
 
-If the invoice was sent and set as *Rejected* by the |DIAN|, the error messages are visible by
-clicking the :icon:`fa-info-circle` :guilabel:`(info circle)` icon next to the :guilabel:`Status`
-field in the :guilabel:`DIAN` tab. Using the reported error codes, it is possible to review
-solutions to apply before re-sending.
+After the master data is corrected, it's possible to reprocess the XML with the new data and send
+the updated version, using the :guilabel:`Retry` button.
 
-.. image:: colombia/rejected-invoice-error-message.png
-   :alt: Example of error messages on rejected invoices.
+.. image:: colombia/xml-validation-error.png
+   :alt: XML validation errors shown in the invoice chatter in Odoo.
 
-After the master data or other issues are corrected, it is possible to reprocess the XML again. Do
-so by following the :ref:`electronic invoice sending <localization/colombia/send-electronic-invoice>`
-flow.
-
-.. _localization/colombia/reports:
+.. _colombia/reports:
 
 Financial reports
 =================
 
-.. _localization/colombia/certificado-ica:
-
 Certificado de Retención en ICA
 -------------------------------
 
@@ -460,14 +424,10 @@ This report is a certification to vendors for withholdings made for the Colombia
 Commerce (ICA) tax. The report can be found under :menuselection:`Accounting --> Reporting -->
 Colombian Statements --> Certificado de Retención en ICA`.
 
-Click the :icon:`fa-cog` :guilabel:`(gear)` icon to display options to :guilabel:`Download Excel`
-and :guilabel:`Copy to Documents`.
-
-.. image:: colombia/retencion-ica-dian.png
+.. image:: colombia/ica-report.png
+   :align: center
    :alt: Certificado de Retención en ICA report in Odoo Accounting.
 
-.. _localization/colombia/certificado-iva:
-
 Certificado de Retención en IVA
 -------------------------------
 
@@ -475,14 +435,10 @@ This report issues a certificate on the amount withheld from vendors for VAT wit
 can be found under :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado
 de Retención en IVA`.
 
-Click the :icon:`fa-cog` :guilabel:`(gear)` icon to display options to :guilabel:`Download Excel`
-and :guilabel:`Copy to Documents`.
-
-.. image:: colombia/retencion-iva-dian.png
+.. image:: colombia/iva-report.png
+   :align: center
    :alt: Certificado de Retención en IVA report in Odoo Accounting.
 
-.. _localization/colombia/certificado-fuente:
-
 Certificado de Retención en la Fuente
 -------------------------------------
 
@@ -490,8 +446,6 @@ This certificate is issued to partners for the withholding tax that they have ma
 be found under :menuselection:`Accounting --> Reporting --> Colombian Statements --> Certificado de
 Retención en Fuente`.
 
-Click the :icon:`fa-cog` :guilabel:`(gear)` icon to display options to :guilabel:`Download Excel`
-and :guilabel:`Copy to Documents`.
-
-.. image:: colombia/retencion-fuente-dian.png
+.. image:: colombia/fuente-report.png
+   :align: center
    :alt: Certificado de Retención en Fuente report in Odoo Accounting.

content/applications/finance/fiscal_localizations/employment_hero.rst

@@ -38,7 +38,7 @@ Configuration
         :ref:`Malaysia <malaysia/employment-hero>`,
         :ref:`New Zealand <new-zealand/employment-hero>`,
         :ref:`Singapore <singapore/employment-hero>`,
-        and the :ref:`United Kingdom <localization/united-kingdom/employment-hero>`.
+        and the :ref:`United Kingdom <united-kingdom/employment-hero>`.
 
    - You can find the **Business ID** in the Employment Hero URL. (i.e., `189241`)
 

content/applications/finance/fiscal_localizations/france.rst

@@ -2,7 +2,7 @@
 France
 ======
 
-.. _localization/france/fec:
+.. _france/fec:
 
 FEC - Fichier des Écritures Comptables
 ======================================
@@ -14,9 +14,7 @@ arranged in chronological order.
 Since January 1st, 2014, every French company is required to produce and transmit this file upon
 request by the tax authorities for audit purposes.
 
-.. _localization/france/fec-import:
-
-FEC import
+FEC Import
 ----------
 
 To make the onboarding of new users easier, Odoo Enterprise's French :ref:`fiscal localization
@@ -36,8 +34,6 @@ click on *Import*.
       year, you might need to cancel those entries in the User Interface. Odoo makes those entries
       (RAN) useless.
 
-.. _localization/france/fec-file:
-
 File formats
 ~~~~~~~~~~~~
 
@@ -56,8 +52,6 @@ Our module expects the files to meet the following technical specifications:
 - **Line terminators**: both CR+LF (`\\r\\n`) and LF (`\\n`) character groups are supported.
 - **Date format**: `%Y%m%d`
 
-.. _localization/france/fec-fields:
-
 Fields description and use
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -121,8 +115,6 @@ These two fields can be found in place of the others in the sence above.
 |    |               | or "D" for Debit                     | or `move_line.credit`             |                 |
 +----+---------------+--------------------------------------+-----------------------------------+-----------------+
 
-.. _localization/france/fec-implementation:
-
 Implementation details
 ~~~~~~~~~~~~~~~~~~~~~~
 
@@ -138,16 +130,12 @@ header.
 If the check passes, then the file is read in full, kept in memory, and scanned. Accounting entities
 are imported one type at a time, in the following order.
 
-.. _localization/france/fec-accounts:
-
 Accounts
 ********
 
 Every accounting entry is related to an account, which should be determined by the field
 `CompteNum`.
 
-.. _localization/france/fec-code-matching:
-
 Code matching
 *************
 
@@ -165,8 +153,6 @@ the first six digits of the codes.
    The account code `65800000` in the file is matched against an existing `658000` account in Odoo,
    and that account is used instead of creating a new one.
 
-.. _localization/france/fec-reconcilable-flag:
-
 Reconcilable flag
 *****************
 
@@ -180,9 +166,7 @@ reconciled with another one.
     with a payment that hasn't yet been recorded, this isn't a problem anyway; the account is
     flagged as reconcilable as soon as the import of the move lines requires it.
 
-.. _localization/france/fec-account-type-template-matching:
-
-Account type and templates matching
+Account type and Templates matching
 ***********************************
 
 As the **type** of the account is not specified in the FEC format, **new** accounts are created
@@ -206,8 +190,6 @@ The match is done with the left-most digits, starting by using all digits, then
 
 The type of the account is then flagged as *payable* and *reconcilable* as per the account template.
 
-.. _localization/france/fec-journals:
-
 Journals
 ********
 
@@ -224,8 +206,6 @@ New journals have their name prefixed by the string ``FEC-``.
 
 The journals are *not* archived, the user is entitled to handle them as he wishes.
 
-.. _localization/france/fec-journal-type:
-
 Journal type determination
 **************************
 
@@ -269,8 +249,6 @@ moves and accounts:
    The journal `type` would be `bank`, because the bank moves percentage (75%) exceeds the threshold
    (70%).
 
-.. _localization/france/fec-partners:
-
 Partners
 ********
 
@@ -287,8 +265,6 @@ Each partner keeps its `Reference` from the field `CompAuxNum`.
     partner entries may be merged by the user, with assistance from the system that groups them by
     similar entries.
 
-.. _localization/france/fec-moves:
-
 Moves
 *****
 
@@ -298,8 +274,6 @@ do the matching between the entries themselves.
 The `EcritureNum` field represents the name of the moves. We noticed that sometimes it may not be
 filled out. In this case, the field `PieceRef` is used.
 
-.. _localization/france/fec-rounding:
-
 Rounding issues
 ***************
 
@@ -310,8 +284,6 @@ targeting the accounts:
 - `658000` Charges diverses de gestion courante, for added debits
 - `758000` Produits divers de gestion courante, for added credits
 
-.. _localization/france/fec-missing-move-name:
-
 Missing move name
 *****************
 
@@ -330,16 +302,12 @@ each different combination of journal and date creates a new move.
 Should this attempt fail, the user is prompted an error message with all the move lines that are
 supposedly unbalanced.
 
-.. _localization/france/fec-partner-info:
-
 Partner information
 *******************
 
 If a line has the partner information specified, the information is copied to the accounting move
 itself if the targeted Journal is of type *payable* or *receivable*.
 
-.. _localization/france/fec-partner-info-export:
-
 Export
 ------
 
@@ -359,9 +327,7 @@ France --> FEC`.
     - `Test-Compta-Demat (Official FEC Testing tool)
       <https://github.com/DGFiP/Test-Compta-Demat>`_
 
-.. _localization/france/accounting-reports:
-
-French accounting reports
+French Accounting Reports
 =========================
 
 If you have installed the French Accounting, you will have access to some accounting reports
@@ -371,103 +337,6 @@ specific to France:
 - Compte de résultats
 - Plan de Taxes France
 
-.. _localization/france/liasse-fiscale:
-
-Liasse fiscale
-==============
-
-The *liasse fiscale* (tax returns) is a collection of standardized financial documents that
-businesses must submit annually to the tax authorities. It comprehensively summarizes the company’s
-financial activities and determines corporate taxes.
-
-`Teledec <https://www.teledec.fr>`_ is a platform used to prepare and submit tax returns using data
-from accounting records. To synchronize your accounting data stored in Odoo with Teledec and
-electronically send your company's *liasse fiscale* to the DGFiP (Direction Générale des Finances
-Publiques), follow these steps:
-
-#. :ref:`localization/france/teledec-account`
-#. :ref:`localization/france/teledec-registration`
-#. :ref:`localization/france/teledec-synchronization`
-
-.. _localization/france/teledec-account:
-
-Teledec account creation
-------------------------
-
-To create a Teledec account, access the `Teledec account creation page <https://www.teledec.fr/s-enregistrer>`_
-and fill in the :guilabel:`Adresse e-mail` field with an email address. Choose a secure password,
-accept the general terms and conditions by checking the box, and click :guilabel:`S'enregistrer` to
-save. Then, enter the :abbr:`SIREN (Système d'identification du répertoire des entreprises,
-Business Directory Identification System)` number of the company.
-
-.. note::
-   If the account has already been created, click :guilabel:`Déjà enregistré?` (Already registered).
-
-.. _localization/france/teledec-registration:
-
-Company registration and fiscal year information
-------------------------------------------------
-
-To register the company on Teledec, go to :guilabel:`Vos entreprises` (Your companies) and click
-:guilabel:`Enregistrer votre entreprise` (Register your company). Make sure to fill in the following
-company information in the :guilabel:`Coordonnées de l'entreprise` (Company's details) and
-:guilabel:`Représentant légal` (Legal representative) sections:
-
-- :guilabel:`Nom de l'entreprise`: Company's name.
-- :guilabel:`Forme juridique`: Select the company's legal form.
-- :guilabel:`Les comptes sont clôturés le`: Closing date.
-- :guilabel:`Régime d'imposition, choix de la liasse`: Select the Tax scheme and tax return option.
-- :guilabel:`Adresse du siège social`: Head office address.
-- :guilabel:`Nom du représentant légal`: Legal representative's name.
-- :guilabel:`Agissant en qualité de`: Legal representative's function.
-- :guilabel:`Numéro de téléphone`: Phone number.
-
-Click :guilabel:`Sauvegarder` (Save) to display the next step
-:guilabel:`Informations générales sur l'exercice déclaré` (General information about the declared
-fiscal year). Then, fill in information on the financial year, such as the fiscal year start and end
-dates or the closing date and duration of the previous fiscal period. After saving, the list of
-documents included in the *liasse fiscale* is displayed, including both standard tax forms and
-those customized for the company’s tax return.
-
-.. tip::
-   - The :guilabel:`Etat` (Status) column shows the progress of the document filing.
-   - Click :guilabel:`Compléter` to fill out a document, then :guilabel:`Sauvegarder` to save.
-   - To print a blank version of the declaration, click :guilabel:`Imprimer la déclaration` and
-     select the :guilabel:`Imprimer la déclaration avec les notices` option.
-
-.. _localization/france/teledec-synchronization:
-
-Odoo synchronization
---------------------
-
-To enable Odoo to automatically fill in the data for the :guilabel:`Liasse fiscale`, click
-:guilabel:`Autres actions` (Other actions) in the top-right corner and select
-:guilabel:`Synchroniser avec un logiciel tiers` (Synchronize with third-party software), then
-:guilabel:`Synchroniser cette liasse avec Odoo` (Synchronize this *liasse* with Odoo).
-
-In the :guilabel:`Synchroniser cette liasse avec Odoo` window, fill in the following
-information to complete the synchronization:
-
-- :guilabel:`Nom / URL complète de la base de données ODOO`: Odoo database name or URL. To provide
-  the full URL of the database, enable :guilabel:`Je voudrais donner une url complète hors .odoo.com`
-  option.
-- :guilabel:`Nom de l'utilisateur`: User name associated with the Odoo account.
-- :guilabel:`Clé API`: :ref:`API key <api/external_api/keys>` generated by the Odoo instance.
-
-Next, click :guilabel:`Importer` to synch data from Odoo. In the
-:guilabel:`Confirmation de la synchronisation de liasse avec Odoo` window, review the amounts and
-make any necessary changes. Then click :guilabel:`Importer la balance` to confirm the
-synchronization of the *liasse fiscale* with Odoo and import the balance.
-
-.. important::
-   Clicking :guilabel:`Importer la balance` may overwrite or alter any manual updates made
-   previously.
-
-To make payment and send the declaration to the tax authorities, click :guilabel:`Paiement & envoi
-de la déclaration`.
-
-.. _localization/france/anti-fraud:
-
 Get the VAT anti-fraud certification with Odoo
 ==============================================
 
@@ -477,8 +346,6 @@ concerning the inalterability, security, storage and archiving of sales data.
 These legal requirements are implemented in Odoo, version 9 onward,
 through a module and a certificate of conformity to download.
 
-.. _localization/france/anti-fraud-software:
-
 Is my company required to use anti-fraud software?
 --------------------------------------------------
 
@@ -491,8 +358,6 @@ Odoo (CGI art. 286, I. 3° bis) if:
 This rule applies to any company size. Auto-entrepreneurs are exempted from
 VAT and therefore are not affected.
 
-.. _localization/france/anti-fraud-odoo-certification:
-
 Get certified with Odoo
 -----------------------
 
@@ -535,8 +400,6 @@ To get the certification, just follow the following steps:
       Finally, make sure the following module *l10n_fr_sale_closing*
       is installed.
 
-.. _localization/france/anti-fraud-features:
-
 Anti-fraud features
 -------------------
 
@@ -548,8 +411,6 @@ The anti-fraud module introduces the following features:
 - **Storage**: automatic sales closings with computation of both period
   and cumulative totals (daily, monthly, annually).
 
-.. _localization/france/anti-fraud-inalterability:
-
 Inalterability
 ~~~~~~~~~~~~~~
 
@@ -561,8 +422,6 @@ if the company is located in France or in any DOM-TOM.
 
     If you run a multi-companies environment, only the documents of such companies are impacted.
 
-.. _localization/france/anti-fraud-security:
-
 Security
 ~~~~~~~~
 
@@ -583,8 +442,6 @@ For POS orders, go to
 For invoices or journal entries,
 go to :menuselection:`Invoicing/Accounting --> Reporting --> French Statements`.
 
-.. _localization/france/anti-fraud-storage:
-
 Storage
 ~~~~~~~
 
@@ -620,8 +477,6 @@ Invoicing and Accounting apps.
       :ref:`developer mode <developer-mode>`.
     - Then go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`.
 
-.. _localization/france/anti-fraud-responsibilities:
-
 Responsibilities
 ----------------
 
@@ -635,9 +490,7 @@ the inalterability of data.
 Odoo absolves itself of all and any responsibility in case of changes
 in the module’s functions caused by 3rd party applications not certified by Odoo.
 
-.. _localization/france/anti-fraud-more-info:
-
-More information
+More Information
 ----------------
 
 You can find more information about this legislation in the following official documents.

content/applications/finance/fiscal_localizations/india.rst

@@ -25,9 +25,6 @@ localization:
    * - :guilabel:`Indian E-waybill`
      - `l10n_in_edi_ewaybill`
      - :ref:`Indian E-way bill integration <india/e-waybill>`
-   * - :guilabel:`Indian - Check GST Number Status`
-     - `l10n_in_gstin_status`
-     - :ref:`Indian Check GST Number Status <india/gstin_status>`
    * - :guilabel:`Indian - GSTR India eFiling`
      - `l10n_in_reports_gstr`
      - :ref:`Indian GST Return filing <india/gstr>`
@@ -296,8 +293,9 @@ Workflow
 Send an E-Way bill
 ~~~~~~~~~~~~~~~~~~
 
-To send an E-Way bill, confirm the customer invoice/vendor bill and click :guilabel:`Send E-Way
-bill`.
+You can manually send an E-Way bill by clicking :guilabel:`Send E-Way bill`. To send the E-Way bill
+automatically when an invoice or a bill is confirmed, enable :guilabel:`E-Way bill (IN)` in your
+:ref:`Sales or Purchase journal <india/e-invoicing-journals>`.
 
 .. image:: india/e-waybill-send-button.png
    :alt: Send E-waybill button on invoices
@@ -307,8 +305,8 @@ bill`.
 Invoice validation
 ~~~~~~~~~~~~~~~~~~
 
-Once an invoice/bill has been issued and sent via :guilabel:`Send E-Way bill`, a confirmation
-message is displayed.
+Once an invoice has been issued and sent via :guilabel:`Send E-Way bill`, a confirmation message is
+displayed.
 
 .. image:: india/e-waybill-process.png
    :alt: Indian e-Way bill confirmation message
@@ -316,7 +314,7 @@ message is displayed.
 .. note::
    - You can find the JSON-signed file in the attached files in the chatter.
    - Odoo automatically uploads the JSON-signed file to the government portal after some time. Click
-     :guilabel:`Process now` if you want to process the invoice/bill immediately.
+     :guilabel:`Process now` if you want to process the invoice immediately.
 
 Invoice PDF report
 ~~~~~~~~~~~~~~~~~~
@@ -332,9 +330,9 @@ You can print the invoice PDF report once you have submitted the E-Way bill. The
 E-Way bill cancellation
 ~~~~~~~~~~~~~~~~~~~~~~~
 
-If you want to cancel an E-Way bill, go to the :guilabel:`E-Way bill` tab of the related
-invoice/bill and fill out the :guilabel:`Cancel reason` and :guilabel:`Cancel remarks` fields. Then,
-click :guilabel:`Request EDI Cancellation`.
+If you want to cancel an E-Way bill, go to the :guilabel:`E-Way bill` tab of the related invoice and
+fill out the :guilabel:`Cancel reason` and :guilabel:`Cancel remarks` fields. Then, click
+:guilabel:`Request EDI Cancellation`.
 
 .. important::
    Doing so cancels both the :ref:`e-Invoice <india/e-invoicing>` (if applicable) and the
@@ -350,26 +348,6 @@ click :guilabel:`Request EDI Cancellation`.
      the government portal. You can click :guilabel:`Process Now` if you want to process the invoice
      immediately.
 
-.. _india/gstin_status:
-
-Indian Check GSTIN Status
-=========================
-
-The :guilabel:`Indian - Check GST Number Status` module allows you to verify the status of a
-:abbr:`GSTIN (Goods and Services Tax Identification Number)` directly from Odoo.
-
-To verify the status of a contact's GST number, access the customer's/vendor's form and click
-:guilabel:`Check GSTIN Status` next to the :guilabel:`GSTIN` field.
-
-To verify the status of a GST number entered on an invoice/bill, access the invoice/bill and click
-the :icon:`fa-refresh` (:guilabel:`refresh`) button next to the :guilabel:`GST Status` field.
-
-.. image:: india/gstin-status-invoice.png
-   :alt: Check GSTIN status of an invoice
-
-A notification is displayed to confirm the status update and the GSTIN status and verification date
-are logged in the contact's chatter.
-
 .. _india/gstr:
 
 Indian GST Return filing

content/applications/finance/fiscal_localizations/malaysia.rst

@@ -2,220 +2,6 @@
 Malaysia
 ========
 
-.. _MyTax: https://mytax.hasil.gov.my
-
-.. _malaysia/configuration:
-
-Configuration
-=============
-
-.. _malaysia/configuration/modules:
-
-Modules installation
---------------------
-
-:ref:`Install <general/install>` the following modules to get all the features of the Malaysian
-localization:
-
-.. list-table::
-   :header-rows: 1
-
-   * - Name
-     - Technical name
-     - Description
-   * - :guilabel:`Malaysia - Accounting`
-     - `l10n_my`
-     - This module includes the default
-       :ref:`fiscal localization package <fiscal_localizations/packages>`.
-   * - :guilabel:`Malaysia - Accounting Reports`
-     - `l10n_my_reports`
-     - This module includes the accounting reports for Malaysia.
-   * - :guilabel:`Malaysia - UBL PINT`
-     - `l10n_my_ubl_pint`
-     - This module includes the features required to export invoices in PINT format.
-   * - :guilabel:`Malaysia - E-invoicing`
-     - `l10n_my_edi`
-     - This module includes the features required for integration with MyInvois under IRBM.
-
-.. _malaysia/configuration/company:
-
-Company information
--------------------
-
-To configure your company information, go to the :guilabel:`Contacts` app, search for your company,
-and select it. Then configure the following fields:
-
-- :guilabel:`Name`
-- :guilabel:`Address`, including the :guilabel:`City`, :guilabel:`State`, :guilabel:`Zip Code`,
-  and :guilabel:`Country`.
-
-   - In the :guilabel:`Street` field, enter the street name, number, and any additional address
-     information.
-   - In the :guilabel:`Street 2` field, enter the neighborhood.
-
-- :guilabel:`Tax ID`: Tax identification number
-- :guilabel:`SST`: Malaysian Sales and Service Tax Number, if applicable
-- :guilabel:`TTx`: Malaysian Tourism Tax Number, if applicable
-- :guilabel:`Phone`
-
-.. _malaysia/myinvois:
-
-E-invoicing integration with MyInvois
-=====================================
-
-The MyInvois Portal is a platform provided by the :abbr:`IRBM (Inland Revenue Board of Malaysia)`
-that facilitates the implementation of e-invoices for Malaysian taxpayers.
-Odoo supports integration with MyInvois to submit the invoices generated in Odoo.
-
-.. note::
-   The :guilabel:`Malaysia - E-invoicing module` must be installed to submit invoices to MyInvois.
-
-.. _malaysia/myinvois/setup:
-
-Set-up
-------
-
-.. _malaysia/myinvois/setup/registration:
-
-MyInvois registration
-~~~~~~~~~~~~~~~~~~~~~
-
-To send electronic invoices to MyInvois, you first need to register and log in to the MyInvois
-portal to grant Odoo the **right to invoice** as an intermediary for your company.
-
-.. note::
-   If this is the first time you log into the MyInvois portal, click :guilabel:`User Manual` on
-   MyTax_ to learn more about the registration process. Both the **pre-production** (:dfn:`testing
-   environment to try the functions before using the actual (production) environment`) and
-   **production** (:dfn:`actual environment to submit e-invoices with accurate information`)
-   environments are supported.
-
-#. Log into MyTax_. Choose the :guilabel:`ID Type` and the corresponding
-   :guilabel:`identification number` used to register for the digital certificate.
-#. From the dashboard, click the :icon:`fa-angle-down` :guilabel:`(angle-down)` icon in the
-   top-right corner and select :guilabel:`View Taxpayer Profile`.
-#. In the :guilabel:`Representatives` section, click :guilabel:`Add Intermediary` in the top-right
-   corner.
-
-   .. image:: malaysia/myinvois-add-intermediary.png
-      :alt: MyInvois add intermediary
-
-#. Add `ODOO S.A.` as an intermediary using the following information:
-
-   - :guilabel:`TIN`: `C57800417080`
-   - :guilabel:`BRN`: `BE0477472701`
-   - :guilabel:`Name`: `ODOO S.A.`
-
-#. Grant the following permissions by clicking the :icon:`fa-toggle-on` :guilabel:`(toggle-on)`
-   icon:
-
-   - :guilabel:`Representation From`
-   - :guilabel:`Document - Submit`
-   - :guilabel:`Document - Cancel`
-   - :guilabel:`Document - Request Rejection`
-
-   .. note::
-      - Access can be revoked in the future if needed.
-      - Odoo, as an intermediary, does not store invoices sent on behalf of the client on the proxy
-        server.
-
-#. Click :guilabel:`Save`. The status for `ODOO S.A.` is then :guilabel:`Active`.
-
-   .. image:: malaysia/myinvois-intermediary-active.png
-      :alt: MyInvois status active
-
-.. _malaysia/myinvois/setup/odoo:
-
-Configuration in Odoo
-~~~~~~~~~~~~~~~~~~~~~
-
-.. _malaysia/myinvois/setup/odoo/einvoicing:
-
-Electronic invoicing
-********************
-
-Go to :menuselection:`Accounting --> Configuration --> Settings`. In the
-:guilabel:`Malaysian Electronic Invoicing` section, choose the relevant :guilabel:`MyInvois mode`
-based on the environment you used to register on MyInvois.
-
-Make sure to allow Odoo to process e-invoices by checking the box, then click :guilabel:`Register`.
-
-.. note::
-   To change the TIN reference, click :guilabel:`Unregister`, change the company's information and
-   make sure the number registered on MyInvois matches, then :guilabel:`Register` again.
-
-.. _malaysia/myinvois/setup/odoo/company:
-
-Company
-*******
-
-Open the Settings app, and in the :guilabel:`Companies` section, click :guilabel:`Update Info`. Then,
-in the :guilabel:`E-invoicing` section, fill in the following fields:
-
-   - :guilabel:`Identification`: The :guilabel:`ID Type` and associated :guilabel:`Identification
-     number` used to register for the digital certificate.
-   - :guilabel:`Ind. Classification`: The 5-digit numeric code that represents the nature and
-     activity of the business.
-
-Contacts
-********
-
-Access the contact's form and fill in the following fields:
-
-   - :guilabel:`Country`
-   - :guilabel:`State`
-   - :guilabel:`Phone`
-   - :guilabel:`Tax ID`
-   - :guilabel:`Identification`: the :guilabel:`ID Type` and the corresponding
-     :guilabel:`Identification number` of the contact registered on MyTax.
-
-.. _malaysia/myinvois/setup/odoo/product:
-
-Products
-********
-
-All products to be included in e-invoices require a Malaysian classification code. To add it,
-access the :guilabel:`Product` form and in the :guilabel:`General Information` tab, fill in the
-:guilabel:`Malaysian classification code` field.
-
-.. _malaysia/myinvois/workflow:
-
-Workflow
---------
-
-.. _malaysia/myinvois/workflow/sending:
-
-Send invoices to MyInvois
-~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Invoices can be sent to MyInvois once they have been confirmed. To do so, follow the
-:ref:`invoice sending <accounting/invoice/sending>` steps, and in the :guilabel:`Send` window,
-enable the :guilabel:`Send to MyInvois` option and click :guilabel:`Print & Send`.
-
-.. _malaysia/myinvois/workflow/sending/status:
-
-MyInvois status
-***************
-
-In the :guilabel:`MyInvois` tab of the invoice, the :guilabel:`MyInvois State` is updated to
-:guilabel:`Valid` when the submission to MyInvois is successful. The :guilabel:`Submission UID`,
-:guilabel:`MyInvois` and :guilabel:`Validation Time` are also updated.
-The same information is available on MyInvois.
-
-.. note::
-   If no information is received from the MyInvois portal, the :guilabel:`MyInvois State` is
-   :guilabel:`In Progress`. In this case, Odoo automatically checks and updates the status.
-
-.. _malaysia/myinvois/workflow/cancellation:
-
-Invoice cancellation
-~~~~~~~~~~~~~~~~~~~~
-
-Sent invoices can be canceled within 72 hours from :guilabel:`Validation time`. In this case, open
-the invoice and click :guilabel:`Request Cancel`. In the :guilabel:`Cancel document` window, include
-the cancellation :guilabel:`Reason`, then click :guilabel:`Update Invoice`. The
-:guilabel:`MyInvois State` is updated to :guilabel:`cancelled`.
-
 .. _malaysia/employment-hero:
 
 Employment Hero payroll

content/applications/finance/fiscal_localizations/united_kingdom.rst

@@ -2,7 +2,7 @@
 United Kingdom
 ==============
 
-.. _localization/united-kingdom/modules:
+.. _united-kingdom/modules:
 
 Configuration
 =============
@@ -27,28 +27,17 @@ Reports` modules to get all the features of the UK localization.
         - Allows sending the tax report via the MTD-VAT API to HMRC.
    * - :guilabel:`UK BACS Payment Files`
      - `l10n_uk_bacs`
-     - Allows generating :ref:`localization/united-kingdom/BACS-files` for bill and invoice payments
-   * - :guilabel:`UK - Construction Industry Scheme`
-     - `l10n_uk_reports_cis`
-     -  - Allows sending the Monthly return to |HMRC|
-        - CIS Deduction (GB) report for UK construction industry
-   * - :guilabel:`UK - HMRC API`
-     - `l10n_uk_hmrc`
-     - Includes the |HMRC| basics.
+     - Allows generating :ref:`united-kingdom/BACS-files` for bill and invoice payments
 
 .. note::
    - Only UK-based companies can submit reports to HMRC.
    - Installing the module :guilabel:`UK - Accounting Reports` installs all two modules at once.
-   - The :guilabel:`UK - Construction Industry Scheme` module automatically includes the
-     :guilabel:`UK - HMRC API` module during installation.
 
 .. seealso::
    - `HM Revenue & Customs <https://www.gov.uk/government/organisations/hm-revenue-customs/>`_
    - `Overview of Making Tax Digital
      <https://www.gov.uk/government/publications/making-tax-digital/overview-of-making-tax-digital/>`_
 
-.. _localization/united-kingdom/chart-of-account:
-
 Chart of accounts
 =================
 
@@ -59,8 +48,6 @@ Setup your :abbr:`CoA (chart of accounts)` by going to :menuselection:`Accountin
 --> Settings --> Accounting Import section` and choose to :guilabel:`Review Manually` or
 :guilabel:`Import (recommended)` your initial balances.
 
-.. _localization/united-kingdom/taxes:
-
 Taxes
 =====
 
@@ -79,8 +66,6 @@ Configuration --> Accounting: Taxes`.
    - Tutorial: `Tax report and return
      <https://www.odoo.com/slides/slide/tax-report-and-return-1719?fullscreen=1>`_.
 
-.. _localization/united-kingdom/digital-tax:
-
 Making Tax Digital (MTD)
 ------------------------
 
@@ -97,7 +82,7 @@ The **UK - Accounting Reports** module enables you to comply with the `HM Revenu
    it through Odoo, as Odoo only retrieves open bonds from the last three months. Your submission
    has to be done manually by contacting HMRC.
 
-.. _localization/united-kingdom/hmrc-registration:
+.. _uk_localization/hmrc-registration:
 
 Register your company to HMRC before the first submission
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -106,8 +91,6 @@ Go to :menuselection:`Accounting --> Reporting --> Tax report` and click on
 :guilabel:`Connect to HMRC`. Enter your company information on the HMRC platform. You only need to
 do it once.
 
-.. _localization/united-kingdom/periodic-hmrc-submission:
-
 Periodic submission to HMRC
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -121,8 +104,6 @@ clicking :guilabel:`Send to HMRC`.
    the value line to `demo`. You can get such credentials from the `HMRC Developer Hub
    <https://developer.service.hmrc.gov.uk/api-test-user>`_.
 
-.. _localization/united-kingdom/periodic-hmrc-submission-multi:
-
 Periodic submission to HMRC for multi-company
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -135,15 +116,15 @@ each submission:
    :guilabel:`Manage Users`. Select the user who is connected to HMRC.
 #. Go to the :guilabel:`UK HMRC Integration` tab and click :guilabel:`Reset Authentication
    Credentials` or :guilabel:`Remove Authentication Credentials` button.
-#. :ref:`Register your company to HMRC <localization/united-kingdom/hmrc-registration>` and submit
-   the company's tax report.
+#. You can now :ref:`register your company to HMRC <uk_localization/hmrc-registration>` and submit
+   the tax report for this company.
 #. Repeat the steps for other companies' HMRC submissions.
 
 .. note::
    During this process, the :guilabel:`Connect to HMRC` button no longer appears for other UK-based
    companies.
 
-.. _localization/united-kingdom/BACS-files:
+.. _united-kingdom/BACS-files:
 
 Bacs files
 ==========
@@ -151,8 +132,8 @@ Bacs files
 :abbr:`Bacs (Bankers' Automated Clearing Services)` files are electronic files used in the UK to
 process payments and transfers between bank accounts.
 
-To enable the use of Bacs files, make sure the
-:ref:`UK BACS Payment Files <localization/united-kingdom/modules>` module is installed, then:
+To enable the use of Bacs files, make sure the :ref:`UK BACS Payment Files <united-kingdom/modules>`
+module is installed, then:
 
 #. Configure your Bacs Service User Number:
 
@@ -173,8 +154,6 @@ To enable the use of Bacs files, make sure the
    the :guilabel:`Accounting` tab, click :guilabel:`Add a line` and fill in the
    :guilabel:`Account Number` and :guilabel:`Bank` fields.
 
-.. _localization/united-kingdom/bill-payments:
-
 Bill payments
 -------------
 
@@ -200,8 +179,6 @@ Export File` if you need a new Bacs file for that batch payment.
 .. image:: united_kingdom/bacs-files.png
    :alt: Vendor Batch Payment view with generated BACS file.
 
-.. _localization/united-kingdom/invoice-payments:
-
 Invoice payments
 ----------------
 
@@ -239,7 +216,7 @@ Then, create a customer batch payment:
 Once validated, the Bacs file is available in the chatter. You can also :guilabel:`Re-generate
 Export File` if you need a new Bacs file for that batch payment.
 
-.. _localization/united-kingdom/employment-hero:
+.. _united-kingdom/employment-hero:
 
 Employment Hero payroll
 =======================
@@ -250,153 +227,3 @@ use our connector as an alternative payroll solution.
 .. important::
    To :ref:`configure the Employment Hero API <employment_hero/configuration>` for **United
    Kingdom**, use the following value as :guilabel:`Payroll URL`: `https://api.yourpayroll.co.uk/`.
-
-.. _localization/united-kingdom/cis-deduction:
-
-.. |HMRC| replace:: :abbr:`HMRC (HM Revenue and Customs)`
-.. |CIS| replace:: :abbr:`CIS (Construction Industry Scheme)`
-
-CIS deduction
-=============
-
-The Construction Industry Scheme deduction (CIS deduction) is a tax deduction system used in the UK
-designed specifically for the construction industry. It requires contractors to deduct a percentage
-of payments made to subcontractors and forward these deductions to HM Revenue and Customs (HMRC).
-These deductions apply only to the labor portion of the payments and serve as advance payments
-towards the subcontractor's tax and National Insurance contributions. Contractors are required to
-register for the scheme, but subcontractors are not. However, subcontractors who are not registered
-face higher payment deductions. Under the |CIS|, contractors must deduct 20% from payments to
-registered subcontractors, while the deduction increases to 30% for unregistered ones.
-
-.. seealso::
-
-   - `Construction Industry Scheme (CIS) <https://www.gov.uk/what-is-the-construction-industry-scheme>`_
-   - `Guidelines for CIS contractors
-     <https://www.gov.uk/what-you-must-do-as-a-cis-contractor>`_
-   - `Guidelines for CIS subcontractors
-     <https://www.gov.uk/what-you-must-do-as-a-cis-subcontractor>`_
-
-As a contractor, you are required to register with the |CIS| before hiring subcontractors and to
-check whether each subcontractor is registered with the |CIS|. You must also maintain records of all
-payments and deductions and submit monthly returns to HMRC, including the following details:
-
-- information about the subcontractors
-- records of payments made and any deductions applied
-- a declaration confirming that the employment status of all subcontractors has been reviewed
-- a declaration confirming that all subcontractors requiring verification have been verified
-
-.. note::
-   If no payments were made to subcontractors in the previous tax month, contractors must notify
-   |HMRC| by the 19th of the month to avoid a penalty.
-
-To submit Monthly Returns to |HMRC|, :ref:`install <general/install>` the
-:ref:`UK - Construction Industry Scheme <localization/united-kingdom/modules>` module.
-
-.. tip::
-   To enable the :guilabel:`Test` mode and use test credentials, open the Settings app, activate the
-   :ref:`developer mode <developer-mode>` and go to :menuselection:`Settings --> Technical -->
-   System Parameters`. Search for `l10n_uk_hmrc.api_mode`, select it, and change the
-   :guilabel:`Value` from `production` to `test`.
-
-.. _localization/united-kingdom/cis-monthly-returns:
-
-Monthly returns
----------------
-
-Monthly returns only work for vendor bills and vendor refunds. To submit a complete return to
-|HMRC|, several steps must be followed to report all payments made to subcontractors under the
-scheme during the previous tax month:
-
-- :ref:`localization/united-kingdom/cis-contractor-setup`
-- :ref:`localization/united-kingdom/cis-subcontractor-setup`
-- :ref:`localization/united-kingdom/cis-vendorbills`
-- :ref:`localization/united-kingdom/cis-monthly-return-sending`
-
-.. _localization/united-kingdom/cis-contractor-setup:
-
-Contractor (company) setup
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To configure your company's |HMRC| information, go to the Settings app and, in the
-:guilabel:`Companies` section, click :guilabel:`Update Info`. Open the :guilabel:`HMRC` tab and
-configure the information in the :guilabel:`HMRC Credentials` and the :guilabel:`Contractor details`
-sections. All fields are mandatory.
-
-.. _localization/united-kingdom/cis-subcontractor-setup:
-
-Subcontractor setup
-~~~~~~~~~~~~~~~~~~~
-
-Access the subcontractor's contact form and select the :guilabel:`Accounting` tab. In the
-:guilabel:`HMRC Details` section, enable the :guilabel:`Construction Industry Scheme` option; the
-|CIS|-related fields are displayed.
-
-By default, the :guilabel:`Deduction rate` is set to 30%. To modify it, first enter the
-:guilabel:`Verification Number` provided by |HMRC| when verifying the subcontractor's status, then
-update the :guilabel:`Deduction Rate` accordingly.
-
-.. note::
-   The :guilabel:`Forename` and :guilabel:`Surname` fields are mandatory if the contact type is set
-   to :guilabel:`Individual`.
-
-.. _localization/united-kingdom/cis-vendorbills:
-
-Vendor bills
-~~~~~~~~~~~~
-
-The appropriate |CIS| tax must be applied to **labor items** on vendor bills based on the
-subcontractor's :guilabel:`Deduction Rate`: :guilabel:`0% CIS`, :guilabel:`20% CIS` or
-:guilabel:`30% CIS`. To apply the rate, go to the :guilabel:`Invoice Lines` section of the vendor
-bill and select the appropriate |CIS| tax rate in the :guilabel:`Taxes` column of the **labor**
-items.
-
-.. note::
-   - The |CIS| tax rate is not necessary for material items on vendor bills.
-   - A yellow banner appears at the top of the page if:
-
-     - The :guilabel:`Construction Industry Scheme` option hasn't been enabled in the
-       :ref:`subcontractor <localization/united-kingdom/cis-subcontractor-setup>`'s
-       :guilabel:`Contact` form when creating a vendor bill.
-     - The |CIS| tax used in the vendor bill does not match the expected |CIS| deduction rate for a
-       :ref:`subcontractor <localization/united-kingdom/cis-subcontractor-setup>`.
-
-.. _localization/united-kingdom/cis-monthly-return-sending:
-
-Monthly returns sending
-~~~~~~~~~~~~~~~~~~~~~~~
-
-On the 6th of each month, Odoo sends a reminder email to submit a monthly return to |HMRC|. The
-recipient email address is the one entered in the company :guilabel:`Email` field. To send monthly
-returns to |HMRC|, go to :menuselection:`Accounting --> Reporting --> Tax Return` and follow these
-steps:
-
-#. Click :icon:`fa-book` :guilabel:`Report:` and select :guilabel:`CIS Deduction (GB)`.
-#. In the :icon:`fa-calendar` :guilabel:`(calendar)` date selector, the :guilabel:`Tax Period` is
-   automatically adjusted to match the |CIS| deduction period.
-#. Click on :guilabel:`Send to HMRC` in the top-left corner.
-#. In the :guilabel:`CIS monthly return` window, select the required options in the
-   :guilabel:`Declaration` section:
-
-   - :guilabel:`Employment Status`: To declare that the employment status of all subcontractors has
-     been reviewed.
-   - :guilabel:`Subcontractor Verification`: To declare that all submitted subcontractors requiring
-     verification have been verified.
-   - :guilabel:`Inactivity Indicator`: To declare temporary inactivity.
-
-#. In the :guilabel:`Information correct declaration` section, confirm the information is true and
-   complete by checking the box. Then, enter the :guilabel:`Password` used in the
-   :guilabel:`HMRC Credentials` section during
-   :ref:`contractor setup <localization/united-kingdom/cis-contractor-setup>`.
-#. Click :guilabel:`Send` to prompt Odoo to request |HMRC| to initiate the transaction.
-
-When |HMRC| replies to a transaction, Odoo automatically notifies the user who submitted it by
-email. The email informs them that the response is available in the company's chatter with an
-attached XML document for download. Both the electronic and paper versions of the |HMRC| receipt
-should be retained. If an error is detected, a new submission is required to comply with |HMRC|
-requirements.
-
-.. note::
-   - Transactions are updated daily. To manually update the |HMRC| request, click the :icon:`fa-cog`
-     :guilabel:`(gear)` icon and select :guilabel:`Refresh HMRC request`.
-   - |CIS| invoices are included in the :guilabel:`CIS Deduction (GB)` report but are not sent to
-     |HMRC|.

content/applications/general/email_communication/mailjet_api.rst

@@ -18,6 +18,7 @@ page. Next, navigate to the :guilabel:`Senders & Domains` section and click on :
 SEND API Settings`.
 
 .. image:: mailjet_api/api-settings.png
+   :align: center
    :alt: SMTP and Send API Settings link in the Senders & Domains section of Mailjet.
 
 Then, copy the :abbr:`SMTP (Simple Mail Transfer Protocol)` configuration settings onto a notepad.
@@ -36,6 +37,7 @@ port number. The settings are needed to configure Mailjet in Odoo, which is cove
    databases.
 
 .. image:: mailjet_api/smtp-config.png
+   :align: center
    :alt: SMTP configuration from Mailjet.
 
 Next, click on the button labeled :guilabel:`Retrieve your API credentials` to retrieve the Mailjet
@@ -55,6 +57,7 @@ email address or domain is approved to send emails using Mailjet's servers. Firs
 :guilabel:`Add a Sender Domain or Address` link under the :guilabel:`Senders & Domains` section.
 
 .. image:: mailjet_api/add-domain-email.png
+   :align: center
    :alt: Add a sender domain or address in the Mailjet interface.
 
 Determine if a sender's email address or the entire domain needs to be added to the Mailjet
@@ -122,6 +125,7 @@ Copy the TXT record information to a notepad and then navigate to the domain's :
 Name System)` provider to complete validation.
 
 .. image:: mailjet_api/host-value-dns.png
+   :align: center
    :alt: The TXT record information to input on the domain's DNS.
 
 Setup in the domain's DNS
@@ -147,6 +151,7 @@ Next, click :guilabel:`Check Now` to validate the TXT record that was added on t
 success screen will appear if the domain is configured correctly.
 
 .. image:: mailjet_api/check-dns.png
+   :align: center
    :alt: Check DNS record in Mailjet.
 
 After successfully setting up the domain, there is an option to :guilabel:`Authenticate this domain
@@ -158,6 +163,7 @@ Identified Mail) records to input into the :abbr:`DNS (Domain Name System)` prov
    360042412734-Authenticating-Domains-with-SPF-DKIM>`_
 
 .. image:: mailjet_api/authenticate.png
+   :align: center
    :alt: Authenticate the domain with SPF/DKIM records in Mailjet.
 
 .. _maintain/mailjet-api/odoo-setup:
@@ -181,8 +187,30 @@ settings can be found on :menuselection:`Mailjet -->  Account Settings --> SMTP
 Settings`.
 
 Then, if the Mailjet server is used for mass emailing, set the :guilabel:`Priority` value higher
-than that of any transactional email server(s). Finally, save the settings and :guilabel:`Test the
-Connection`.
+than that of any transactional email server(s). Finally, save the settings and :guilabel:`Test the Connection`.
 
 .. image:: mailjet_api/server-settings.png
+   :align: center
    :alt: Odoo outgoing email server settings.
+
+.. important::
+   In order for the notifications feature to work using Mailjet, there are three settings that need
+   to be set in Odoo.
+
+   #. The :guilabel:`From Filter` needs to be set on the server configuration. It is recommended
+      to set it as a domain and not a full email address. It should match the domain in the two
+      proceeding steps. For more information, check out the :ref:`FROM filtering documentation
+      <email-outbound-different-servers-personalized-from-filtering>`.
+   #. The :guilabel:`mail.default.from` system parameter must have the value
+      `notifications\@yourdomain.com`.
+   #. The :guilabel:`mail.default.from_filter` system parameter must have the value
+      `yourdomain.com`. Replace `yourdomain` with the custom domain for the Odoo database. If there
+      isn't one, then use the :guilabel:`mail.catchall.domain` system parameter.
+
+   For more information, check out the :ref:`"Using a unique email address" documentation
+   <email-outbound-unique-address>`.
+
+   The :guilabel:`System Parameters` can be accessed by activating the :ref:`developer-mode`.
+
+Once the setup is complete, the Odoo database is ready to use the Mailjet email server for mass
+mailing or transactional emails.

content/applications/general/users/ldap.rst

@@ -1,44 +1,55 @@
-===================
-LDAP authentication
-===================
+=================
+Sign in with LDAP
+=================
 
-To configure :abbr:`LDAP (Lightweight Directory Access Protocol)` authentication in Odoo:
+- Install the Lightweight Directory Access Protocol (LDAP) module in General Settings.
 
-#. Open the Settings app, scroll down to the :guilabel:`Integrations` section, and enable
-   :guilabel:`LDAP Authentication`.
-#. Click :guilabel:`Save`, then go back to the :guilabel:`Integrations` section and click
-   :guilabel:`LDAP Server`.
-#. In the :guilabel:`Set up your LDAP Server` list, click :guilabel:`New`, then select the required
-   company in the dropdown list.
-#. In the :guilabel:`Server information` section, enter the server's IP address and port in the
-   :guilabel:`LDAP server address` and :guilabel:`LDAP Server port` fields, respectively.
-#. Enable :guilabel:`Use TLS` to request secure TLS/SSL encryption when connecting to the LDAP
-   server, providing the server has StartTLS enabled.
-#. In the :guilabel:`Login information` section, enter the ID and password of the account used to
-   query the server in the :guilabel:`LDAP binddn` and :guilabel:`LDAP password` fields,
-   respectively. If the fields are left empty, the server will perform the query anonymously.
-#. In the :guilabel:`Process parameter` section, enter:
+- Click on **Create** in Setup the :abbr:`LDAP (Lightweight Directory Access Protocol)` Server.
 
-   - the LDAP server's name in the :guilabel:`LDAP base` field using LDAP format
-     (e.g., ``dc=example,dc=com``);
-   - ``uid=%s`` in the :guilabel:`LDAP filter` field.
+.. image:: ldap/ldap01.png
+    :align: center
+    :alt: LDAP Authentication checkbox highlighted in the integrations settings on Odoo.
 
-#. In the :guilabel:`User information` section:
+.. image:: ldap/ldap02.png
+    :align: center
+    :alt: Create highlighted in the LDAP server settings.
 
-   - Enable :guilabel:`Create user` to create a user profile in Odoo the first time someone logs in
-     using LDAP;
-   - Select the :guilabel:`User template` to be used to create the new user profiles. If no template
-     is selected, the administrator's profile is used.
+- Choose the company using the LDAP.
 
-.. note::
-   When using Microsoft Active Directory (AD) for LDAP authentication, if users experience login
-   issues despite using valid credentials, create a new system parameter to disable referral chasing
-   in the LDAP client:
+.. image:: ldap/ldap03.png
+    :align: center
+    :alt: Select the company drop-down menu highlighted in LDAP setup.
 
-    #. :ref:`Activate the developer mode. <developer-mode>`
-    #. Go to :menuselection:`Settings --> Technical --> System Parameters` and click
-       :guilabel:`New`.
-    #. Fill in the fields:
+- In **Server Information**, enter the IP address of the server and the port it listens to.
 
-       - :guilabel:`Key`: ``auth_ldap.disable_chase_ref``
-       - :guilabel:`Value`: ``True``
+- Tick **Use TLS** if the server is compatible.
+
+.. image:: ldap/ldap04.png
+    :align: center
+    :alt: LDAP server settings highlighted in LDAP server setup on Odoo.
+
+- In **Login Information**, enter ID and password of the account used to query the server. If left
+  empty, the server queries anonymously.
+
+.. image:: ldap/ldap05.png
+    :align: center
+    :alt: Login information highlighted in LDAP server setup on Odoo.
+
+- In **Process Parameter**, enter the domain name of the LDAP server in :abbr:`LDAP (Lightweight
+  Directory Access Protocol)` nomenclature (e.g. ``dc=example,dc=com``).
+
+- In **LDAP filter**, enter ``uid=%s``
+
+.. image:: ldap/ldap06.png
+    :align: center
+    :alt: Process parameter highlighted in LDAP server setup on Odoo.
+
+- In **User Information**, tick *Create User* if Odoo should create a User profile the first time
+  someone logs in with :abbr:`LDAP (Lightweight Directory Access Protocol)`.
+
+- In **Template User**, indicate a template for the new profiles created. If left blanked, the admin
+  profile will be used as template.
+
+.. image:: ldap/ldap07.png
+    :align: center
+    :alt: User information highlighted on LDAP server setup on Odoo.

content/applications/hr/payroll.rst

@@ -29,8 +29,6 @@ The accounting section of the configuration menu relates to three options:
   created from all the accounting entries from the same period. This disables the generation of
   single payments.
 
-.. _payroll-localizations:
-
 Localizations
 -------------
 

content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst

@@ -17,13 +17,6 @@ To set up the UPS shipping connector in Odoo, complete these steps:
    <inventory/shipping_receiving/ups-client-id>`
 #. Set up shipping method in Odoo
 
-.. warning::
-   When configuring a shipping method to use UPS, make sure the :guilabel:`Provider` is set to
-   :guilabel:`UPS`, **NOT** :guilabel:`UPS Legacy`.
-
-   If shipping methods currently exist with the :guilabel:`Provider` set to :guilabel:`UPS Legacy`,
-   archive them, and create new shipping methods using :guilabel:`UPS`, instead.
-
 UPS account setup
 =================
 

content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst

@@ -9,12 +9,13 @@ Manufacturing order costs
 .. |BoMs| replace:: :abbr:`BoMs (Bills of Materials)`
 
 The ability to accurately calculate the cost of manufacturing a product is critical when determining
-product profitability. Odoo's **Manufacturing** app simplifies this calculation by automatically
+product profitability. Odoo's *Manufacturing* app simplifies this calculation by automatically
 calculating the cost to complete each manufacturing order (MO), as well as the average production
 cost of a product, based on all completed |MOs|.
 
 .. important::
-   Odoo's Manufacturing app distinguishes between the *MO cost* and the *real cost* of an |MO|.
+   Odoo's Manufacturing app distinguishes between the *manufacturing order cost* and the *real cost*
+   of an |MO|.
 
    The |MO| cost represents how much it *should* cost to complete an |MO|, based on the
    configuration of the product's bill of materials (BoM). This takes into account the cost and
@@ -29,9 +30,8 @@ Cost configuration
 ==================
 
 Odoo computes |MO| costs based on the configuration of the |BoM| used to manufacture a product. This
-calculation includes the cost and quantity of components and operations listed on the |BoM|, in
-addition to the operating costs of the work centers where those operations are carried out, and the
-amount paid to each employee who works on an operation.
+includes the cost and quantity of components and operations listed on the |BoM|, in addition to the
+operating costs of the work centers where those operations are carried out.
 
 Component cost
 --------------
@@ -42,61 +42,44 @@ Products --> Products`, and select a component product. The cost is displayed in
 :guilabel:`Cost` field of the :guilabel:`General Information` tab, on the component's product form.
 
 It is possible to set the cost of a component manually, by clicking the :guilabel:`Cost` field on
-the component's product form and entering a value. However, any future |POs| for the component
-override a manually entered value, resetting the :guilabel:`Cost` field back to an automatically
+the component's product form, and entering a value. However, any future |POs| for the component
+override a value entered manually, resetting the :guilabel:`Cost` field back to an automatically
 computed value.
 
-.. _manufacturing/mo-costs/work-center-cost:
-
 Work center cost
 ----------------
 
 To set the operating cost for a specific work center, navigate to :menuselection:`Manufacturing app
 --> Configuration --> Work Centers`, and select a work center.
 
-To set the cost of operating the work center for one hour, enter a value in the :guilabel:`per
+To set the operating cost for the work center, as a whole, enter a value in the :guilabel:`per
 workcenter` field, located beside the :guilabel:`Cost per hour` section on the work center's
-:guilabel:`General Information` tab.
+:guilabel:`General Information` tab. This operating cost is used regardless of how many employees
+are working at the work center at any given time.
 
-To set the hourly cost of each employee that operates the work center, enter a value in the
-:guilabel:`per employee` field, located beside the :guilabel:`Cost per hour` section on the work
-center's :guilabel:`General Information` tab. For example, if `25.00` is entered in the
-:guilabel:`per employee` field, it costs $25.00 per hour for *each* employee working at the work
-center.
+To set the operating cost for the work center based on the number of employees working there at a
+given time, enter a value in the :guilabel:`per employee` field, located beside the :guilabel:`Cost
+per hour` section on the work center's :guilabel:`General Information` tab. For example, if `25.00`
+is entered in the :guilabel:`per employee` field, it costs $25.00 per hour for *each* employee
+working at the work center.
+
+Note that, if values are entered in both the :guilabel:`per workcenter` *and* :guilabel:`per
+employee` fields, the value in the :guilabel:`per workcenter` field takes precedence, and the value
+in the :guilabel:`per employee` field is ignored.
 
 .. important::
-   The value entered in the :guilabel:`per employee` field is only used to calculate the |MO| cost,
-   which is the estimated cost of completing the |MO|.
+   It is also possible to set a per hour cost for specific employees, by navigating to the
+   :menuselection:`Employees` app, selecting an employee, clicking the :guilabel:`HR Settings` tab
+   on their employee form, and entering a value in the :guilabel:`Hourly Cost` field.
 
-   The actual cost of completing the |MO| is represented by the real cost. Instead of using the
-   value entered in the :guilabel:`per employee` field, the real cost is calculated using the hourly
-   cost specific to each employee.
+   Just like the *per workcenter* field on a work center form, the :guilabel:`Hourly Cost` field on
+   an employee's form overrides the *per employee* field on a work center form.
 
-   For example, if the :guilabel:`per employee` cost of a work center is '$50.00', and an employee
-   with an hourly cost of '$60.00' completes a work order there, the |MO| cost (estimated) is
-   calculated using the $50/hr cost, while the real cost is calculated using the $60/hr cost.
+   However, the *per workcenter* field takes precedence over both the *per employee* field on the
+   workcenter form *and* the :guilabel:`Hourly Cost` field on the employee form.
 
-   See the :ref:`employee cost section <manufacturing/mo-costs/employee-cost>` below for information
-   on how to set the cost for specific employees.
-
-.. _manufacturing/mo-costs/employee-cost:
-
-Employee cost
--------------
-
-To set the hourly cost for a specific employee, navigate to the :menuselection:`Employees` app, and
-select an employee. On the employee's form, select the :guilabel:`Settings` tab, and enter the
-employee's rate in the :guilabel:`Hourly Cost` field of the :guilabel:`Application Settings`
-section.
-
-.. important::
-   As detailed in the :ref:`work center cost section <manufacturing/mo-costs/work-center-cost>`
-   above, the value entered in the :guilabel:`Hourly Cost` field on the employee's form is used to
-   calculate the real cost of an |MO|. The estimated cost of an |MO|, referred to as the |MO| cost,
-   uses the per employee cost set on each work center's form.
-
-|BoM| configuration
--------------------
+|BoM| cost
+----------
 
 Configuring a |BoM| so Odoo can accurately calculate the cost of |MOs| that use it requires two
 steps. First, components **must** be added, and the required quantity specified. Second, operations
@@ -120,10 +103,10 @@ By default, the :guilabel:`Duration Computation` field is set to :guilabel:`Set
 which means that the number entered in :guilabel:`Default Duration` field is always used as the
 expected duration of the operation.
 
-Selecting :guilabel:`Compute based on tracked time` causes Odoo to automatically compute the
-:guilabel:`Default Duration` based on a certain number of work orders, which is set in the
-:guilabel:`Based on` field. Before there are work orders to compute this duration, the value in the
-:guilabel:`Default Duration` field is used instead.
+Selecting :guilabel:`Compute based on tracked time` causes Odoo to automatically compute the default
+duration based on a certain number of work orders, which is set in the :guilabel:`Based on` field.
+Before there are work orders to compute this duration, the value in the :guilabel:`Default Duration`
+field is used instead.
 
 The hourly cost of operating the work center, and the duration of the operation, are used to
 calculate the operation's cost.
@@ -154,9 +137,7 @@ same costs. This is the *estimated* cost of completing the |MO|.
 
 However, once work commences, the values in the :guilabel:`Real Cost` column may begin to diverge
 from the values in the :guilabel:`MO Cost` column. This happens if a different component quantity is
-used than was listed on the |MO|, the duration of a work order is different than expected, or the
-hourly cost of the employee performing a work order differs from the employee cost set on the work
-center.
+used than was listed on the |MO|, or if the duration of a work order is different than expected.
 
 Once the |MO| has been completed by clicking :guilabel:`Produce All`, the values in the
 :guilabel:`MO Cost` column update to match those displayed in the :guilabel:`Real Cost` column.

content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst

@@ -41,22 +41,21 @@ quality check to be created for new manufacturing orders (MOs).
 
 If the :guilabel:`Manufacturing` operation is selected in the :guilabel:`Operations` field, a new
 field appears below it, titled :guilabel:`Work Order Operation`. From this field, select a specific
-work order to generate quality checks for that operation, rather than the manufacturing operation,
-in general.
+work order to generate quality checks for that operation, rather than the manufacturing operation in
+general.
 
-.. example::
-   A |QCP| could be configured to create quality checks for the `Assembly` work order of the `Coffee
-   Table` product. Then, if a new |MO| is confirmed for a `Coffee Table`, the |QCP| creates a
-   quality check specifically for the `Assembly` operation.
+For example, a |QCP| could be configured to create quality checks for the `Assembly` work order of
+the `Coffee Table` product. Then, if a new |MO| is confirmed for a `Coffee Table`, the |QCP| creates
+a quality check specifically for the `Assembly` operation.
 
 The :guilabel:`Control Per` field is set to one of three options that determine *when* a new quality
 check is created:
 
-- :guilabel:`Operation`: One check is requested for the specified operation, as a whole.
-- :guilabel:`Product`: One check is requested for each *unique* product included in the specified
+- :guilabel:`Operation`: one check is requested for the specified operation, as a whole.
+- :guilabel:`Product`: one check is requested for each *unique* product included in the specified
   operation. For example, a delivery operation for one table and four chairs would generate two
   checks, since two *unique* products are included in the operation.
-- :guilabel:`Quantity`: A check is requested for a certain percentage of items within the specified
+- :guilabel:`Quantity`: a check is requested for a certain percentage of items within the specified
   operation. This percentage is set by enabling the :guilabel:`Partial Transfer Test` checkbox, and
   then entering a numerical value in the :guilabel:`Percentage` field that appears below. If the
   checkbox is not enabled, one quality check is created for the full quantity.
@@ -64,11 +63,11 @@ check is created:
 The :guilabel:`Control Frequency` field is set to one of three options that determine *how often* a
 new quality check is created:
 
-- :guilabel:`All`: A quality check is requested every time the conditions of the |QCP| are met.
-- :guilabel:`Randomly`: A quality check is randomly requested for a certain percentage of
-  operations, which can be specified in the :guilabel:`Every #% of Operations` field that appears
+- :guilabel:`All`: a quality check is requested every time the conditions of the |QCP| are met.
+- :guilabel:`Randomly`: a quality check is randomly requested for a certain percentage of
+  operations, which can be specified in the :guilabel:`Every #% of Transfers` field that appears
   below.
-- :guilabel:`Periodically`: A quality check is requested once every set period of time, which is
+- :guilabel:`Periodically`: a quality check is requested once every set period of time, which is
   specified by entering a numerical value in the field below, and choosing either :guilabel:`Days`,
   :guilabel:`Weeks`, or :guilabel:`Months` as the desired time interval.
 
@@ -85,10 +84,8 @@ selected:
 - :guilabel:`Pass - Fail` checks specify a criterion that products must meet for the check to pass.
 - :guilabel:`Measure` checks prompt employees to record a measurement of the product that must be
   within a tolerance of a norm value for the check to pass.
-- :guilabel:`Worksheet` checks require the employee processing the check to fill out an interactive
-  worksheet.
-- :guilabel:`Spreadsheet` checks require the employee processing the check to fill out an
-  interactive spreadsheet.
+- :guilabel:`Worksheet` checks provide an interactive worksheet that must be filled out by the
+  employee processing the check.
 
 .. important::
    An *Instructions* check is the same as a step on a work order for an MO.
@@ -100,17 +97,6 @@ selected:
    However, when creating a control point specifically for quality control purposes, using a
    different check type is probably more effective.
 
-.. note::
-   When creating a |QCP| with the :guilabel:`Worksheet` or :guilabel:`Spreadsheet` check types, it
-   is necessary to specify a *Quality Worksheet Template* or *Quality Spreadsheet Template* in the
-   :guilabel:`Template` field that appears below the :guilabel:`Type` field.
-
-   The selected template is duplicated for each quality check created by the |QCP|, and **must** be
-   filled out to complete the quality check.
-
-   To create a new template, navigate to :menuselection:`Quality app --> Configuration --> Quality
-   Worksheet/Spreadsheet Templates`, and click :guilabel:`New`.
-
 In the :guilabel:`Team` field, specify the quality team that is responsible for managing the |QCP|,
 and the quality checks it creates. If a specific quality team member is responsible for the |QCP|,
 select them in the :guilabel:`Responsible` field.

content/applications/marketing/email_marketing/analyze_metrics.rst

@@ -6,11 +6,8 @@ Analyze metrics
 
 In order to properly understand the success or failure of an email marketing campaign, it is
 necessary to monitor several key metrics. The insights gained from these metrics can then be used to
-optimize future campaigns. Odoo's **Email Marketing** application tracks several :ref:`key metrics
-<email-marketing/view-metrics>`, that can be interpreted through :ref:`reports
-<email_marketing/create_reports>` to improve future campaigns.
-
-.. _email-marketing/view-metrics:
+optimize future campaigns. Odoo's *Email Marketing* application tracks several :ref:`key metrics
+<email-marketing/key-metrics>`, that can be interpreted to improve future campaigns.
 
 View metrics
 ============
@@ -20,182 +17,84 @@ locations.
 
 To access the metrics for an individual mailing, navigate to :menuselection:`Email Marketing app
 --> Mailings`. Locate the specific mailing in the list view, and use the column headings to view the
-results for that mailing. Click on one of the mailings in the list to open the record.
-
-At the top of the record, detailed metrics are displayed as smart buttons.
+results for that mailing. Click on one of the mailings in the list to open the record. At the top of
+the record, detailed metrics are displayed as smart buttons.
 
 .. image:: analyze_metrics/metric-smart-buttons.png
    :align: center
    :alt: The smart buttons on a mass mailing, displaying the results of the message.
 
+.. tip::
+   Click on the smart buttons to see the recipient records for each metric.
+
+.. _email-marketing/key-metrics:
+
 Opened rate
 -----------
 
-The percentage of emails opened by recipients, against the total number of sent emails.
+The *Opened* rate measures the percentage of emails opened by recipients against the total number of
+sent emails.
 
-In cases where a reply is expected, such as cold outreach emails, high open rate may indicate the
-subject line was timely, compelling, and successfully prompted the recipients to view the message.
+A high open rate may indicate that the subject line was timely, compelling, and successfully
+prompted the recipients to view the message.
 
-In cases where a reply is not expected, such as promotional emails, it may indicate an issue with
-the email, such as incorrect product links or coupon codes.
-
-In cases where a reply is expected, a low open rate may indicate the subject
-line failed to capture the recipients' interest or the message ended up in a spam or junk folder. It
-could also indicate the email ended up in a spam or junk folder.
-
-.. note::
-   Emails that consistently land in recipient spam folders could be due to having a poor sender
-   reputation (i.e. high unsubscribe rate, high percentage of past emails marked as spam, etc.),
-   or failing to :doc:`configure the proper DNS records
-   <../../general/email_communication/email_domain>`.
+A low open rate may indicate the subject line failed to capture the recipients' interest. It could
+also indicate the email ended up in a spam or junk folder due to having a poor sender reputation or
+failing to :doc:`configure the proper DNS records <../../general/email_communication/email_domain>`.
 
 Replied rate
 ------------
 
-The percentage of recipients who responded to the email, against the total number of sent emails.
+The *Replied* rate measures the percentage of recipients who responded to the email directly against
+the total number of sent emails.
 
-A high replied rate may indicate the email resonated with recipients, prompting them to take
-action or provide feedback.
+A high replied rate may indicate the email resonated with recipients, prompting them to take action
+or provide feedback.
 
-A low replied rate may suggest the message lacked relevance or did not contain a clear
-call-to-action.
+A low replied rate may suggest that the message lacked relevance or did not contain a clear call to
+action.
 
 Clicked rate
 ------------
 
-This represents the *Clicked through rate (CTR)*, which measures the
-percentage of recipients who clicked on a link within the email, against the total number of sent
-emails.
+The *Clicked* through rate (CTR), measures the percentage of recipients who clicked on a link within
+the email against the total number of sent emails.
 
-A high |CTR| may indicate the email content was relevant and appropriately targeted. Recipients
-were motivated to click the links provided, and likely found the content engaging.
+A high |CTR| may indicate the email content was relevant and appropriately targeted. Recipients were
+motivated to click the links provided, and likely found the content engaging.
 
 A low |CTR| may indicate issues with either the targeting, or the content itself. Recipients may
-have been unmotivated by the calls-to-action, if there were any, or the message itself may have
-been directed toward the wrong audience.
+have been unmotivated by the calls to action, if there were any, or the message itself may have been
+directed toward the wrong audience.
 
 Received rate
 -------------
 
-This rate measures the percentage of emails that were **successfully** delivered, against the total
-number of sent emails.
+The *Received* rate measures the percentage of emails that were successfully delivered against the
+total number of sent emails.
 
-A high received rate can indicate the mailing list used is up-to-date, and the sender authentication
-is trusted by email providers.
+A high received rate can indicate that the mailing list used is up to date and the sender
+authentication is trusted by email providers.
 
-A low received rate may indicate issues, either with the mailing list used for the mailing, or with
+A low received rate may indicate issues either with the mailing list used for the mailing or with
 the sender authentication. View the :ref:`email-marketing/deliverability-issues` section for more
 information.
 
 Bounced rate
 ------------
 
-This rate measures the percentage of emails that were **unsuccessfully** delivered, and did not
-enter a recipient's inbox, against the total number of sent emails.
+The *Bounced* rate measures the percentage of emails that were unsuccessfully delivered, against the
+total number of sent emails.
 
-A high bounce rate could indicate issues, either with the mailing list used for the mailing, or with
+A high bounce rate could indicate issues either with the mailing list used for the mailing or with
 the sender authentication.
 
-A low bounce rate may indicate that the mailing list used is up-to-date, and the sender
+A low bounce rate may indicate that the mailing list used is up to date and the sender
 authentication is trusted by email providers. View the :ref:`email-marketing/deliverability-issues`
 section for more information.
 
-.. tip::
-   Click on the respective smart buttons to see all the corresponding recipient records that are
-   attributed to each metric. When these filtered records are in view, multiple types of reports can
-   be run for further analysis.
-
-.. _email_marketing/create_reports:
-
-Create metrics reports
-======================
-
-Individual metrics can be analyzed by creating a report. To begin, click on the smart button of the
-desired metric.
-
-Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` to the right of the search bar to see
-a drop-down menu of filtering and grouping parameters.
-
-:guilabel:`Filters`, located in the left column of the search options, can be used to keep only the
-results that fit the filter. For example, selecting the *Bounced* filter only shows emails
-that could not be delivered.
-
-:guilabel:`Group By`, found in the middle column, is used to organize the results into groups, and
-can be used with or without filters.
-
-.. note::
-   Setting multiple :guilabel:`Group By` options creates nested groups, according to which option
-   is selected first. For example, selecting :guilabel:`Sent Period`, followed by
-   :guilabel:`Add Custom Group --> Responsible`, in the :guilabel:`Group By` column, sorts all
-   results *first* by the sent period, *then* by the team member responsible. This is a useful
-   metric for analyzing who on the team is sending in volume or quantity over a set time period.
-
-   This can be verified by looking at the direction, and order, of the selections in the group tile
-   that appears in the search bar after the selections are made.
-
-.. example::
-   A monthly newsletter has been sent out, and 6.9% of the sent emails were bounced.
-
-   .. image:: analyze_metrics/newsletter-metrics.png
-      :align: center
-      :alt: The metrics smart buttons of the newsletter.
-
-   To see what these bounced recipients have in common, the records are grouped using a custom group
-   targeting :guilabel:`Mailing Lists`, which groups all records by the mailing lists they are on.
-   The records are then filtered using a custom filter with the rule `Created on >= 07/01/2024
-   00:00:00`, to filter by when the mailing list was last checked. This filter only includes
-   recipients that have been created on, or after, July 1st, 2024, in the report.
-
-   .. image:: analyze_metrics/metrics-filter.png
-      :align: center
-      :alt: The custom filter creation form.
-
-   Using these configurations, it is evident that all the recipients with bounced emails were added
-   after the list was last checked. Looking closer at the domains, it is evident that each
-   recipient has a malformed email domain (i.e: @yaoo.com instead of @yahoo.com), likely due to a
-   manual entry error while updating the database.
-
-   .. image:: analyze_metrics/malformed-addresses.png
-      :align: center
-      :alt: A list of bounced email addresses with malformed email domains.
-
-.. seealso::
-   View :doc:`../../essentials/search` for more information about making custom groups and
-   filters.
-
 .. _email-marketing/deliverability-issues:
 
-Mass mailing analysis
-=====================
-
-It is also possible to analyze the success between mailing campaigns by creating a *Mass Mailing
-Analysis* report. To begin, navigate to :menuselection:`Email Marketing app --> Reporting --> Mass
-Mailing Analysis`.
-
-A dashboard appears displaying a bar chart containing each mailing campaign. By default,
-:guilabel:`Sent` is selected, displaying the number of sent records on the y-axis. To change the
-measure, click the :guilabel:`Measures` button, and select the desired measure from the drop-down
-menu.
-
-.. example::
-   The following chart displays the number of opened emails from two different mass mailings.
-
-   In this view, it can be seen that the first mass mailing led to a higher opened rate than the
-   second. Because a lower opened rate can sometimes be attributed to a subject line that failed to
-   capture readers' attention, the subject line of each mass mailing can be a good place to begin
-   looking.
-
-   .. image:: analyze_metrics/mma-opened.png
-      :align: center
-      :alt: A bar chart displaying the different opened rate between two mass mailing campaigns.
-
-   Comparing the two subject lines, it is clear the newsletter's subject line was less engaging,
-   which may have led to the lower opened rate, when compared to the other mass mailing.
-
-   .. image:: analyze_metrics/mailing-comparison.png
-      :align: center
-      :alt: alt text
-
 Deliverability issues
 =====================
 

content/applications/productivity/discuss.rst

@@ -1,169 +1,105 @@
 :show-content:
-:hide-page-toc:
+:show-toc:
 
 =======
 Discuss
 =======
 
-Odoo **Discuss** is an internal communication app that allows users to connect through messages,
-notes, file sharing, and video calls. **Discuss** enables communication through a persistent chat
-window that works across applications, or through the dedicated *Discuss* dashboard.
+Odoo *Discuss* is an internal communication app that allows users to connect through messages,
+notes, and file sharing, either through a persistent chat window that works across applications, or
+through the dedicated *Discuss* dashboard.
 
-Upon opening the :menuselection:`Discuss app`, the :guilabel:`Discuss` dashboard appears.
+.. _discuss_app/notification_preferences:
 
-Inbox, starred, and history
-===========================
+Choose notifications preference
+===============================
 
-Upon opening the :menuselection:`Discuss app`, the *Discuss* dashboard appears.
+Access user-specific preferences for the *Discuss* app by navigating to :menuselection:`Settings app
+--> Users --> User --> Preferences tab`.
 
-On the :guilabel:`Discuss` dashboard, unread messages are visible in the :icon:`fa-inbox`
-:guilabel:`Inbox`. :icon:`fa-star-o` :guilabel:`Starred` is where starred messages are stored.
-:icon:`fa-history` :guilabel:`History` shows chatter updates for records in the Odoo database the
-user has been assigned to, or tagged on.
+.. image:: discuss/preferences-user.png
+   :alt: View of the Preferences tab for Odoo Discuss.
 
-Direct messages
-===============
+By default, the :guilabel:`Notification` field is set as :guilabel:`Handle by Emails`. With this
+setting enabled, a notification email will be sent by Odoo every time a message is sent from the
+chatter, a note is sent with an `@` mention (from chatter), or a notification is sent for a record
+that the user follows. Something that triggers a notification is changing of the stage (if an email\
+is configured to be sent, for example if the task is set to :guilabel:`Done`).
 
-*Direct messages* allow the user to communicate privately with one or multiple team members. To
-start a new direct message, click the :icon:`fa-plus` icon, next to :guilabel:`Direct Messages` on
-the :guilabel:`Discuss` dashboard, and enter the name of the desired person in the :guilabel:`Start
-a conversation` search bar that appears.
+By choosing :guilabel:`Handle in Odoo`, the above notifications are shown in the *Discuss* app's
+*inbox*. Messages can have the following actions taken on them: respond with an emoji by clicking
+:guilabel:`Add a Reaction`, or reply to the message by clicking on :guilabel:`Reply`. Additional
+actions may include starring the message by clicking :guilabel:`Marked as Todo`, or pinning the
+message by selecting :guilabel:`Pin` or even mark the message as unread by selecting
+:guilabel:`Marked as unread`.
+
+.. image:: discuss/reactions-discuss.png
+   :alt: View of an inbox message and its action options in Odoo Discuss.
+
+Clicking :guilabel:`Mark as Todo` on a message causes it to appear on the :guilabel:`Starred` page,
+while clicking :guilabel:`Mark as Read` moves the message to :guilabel:`History`.
+
+.. image:: discuss/starred-messages.png
+   :alt: View of messages marked as todo in Odoo Discuss.
+
+Start chatting
+==============
+
+The first time a user logs in to their account, OdooBot sends a message asking for permission to
+send desktop notifications for chats. If accepted, the user will receive push notifications on their
+desktop for the messages they receive, regardless of where the user is in Odoo.
+
+.. image:: discuss/odoobot-push.png
+   :alt: View of the messages under the messaging menu emphasizing the request for push
+         notifications for Odoo Discuss.
 
 .. tip::
-   Multiple names can be selected in the :guilabel:`Start a conversation` search bar. Once all of
-   the names have been entered, press :kbd:`Enter`.
+   To stop receiving desktop notifications, reset the notifications settings of the browser.
 
-Direct message actions
-----------------------
+To start a chat, go to the :menuselection:`Discuss` app and click on the :guilabel:`+ (plus)` icon
+next to :guilabel:`Direct Messages` or :guilabel:`Channels` in the left menu of the dashboard.
 
-Hover over a direct message in the chat window to see a menu of actions to take on the message.
+.. image:: discuss/channels-direct-messages.png
+   :height: 400
+   :alt: View of Discuss's panel emphasizing the titles channels and direct messages in Odoo
+         Discuss.
 
-- :icon:`oi-smile-add` :guilabel:`(Add a Reaction)`: open a drop-down menu of emojis that can be
-  used to react to the direct message.
-- :icon:`fa-reply` :guilabel:`(Reply)`: reply to the direct message in a thread.
-- :icon:`fa-star-o` :guilabel:`(Mark as Todo)`: add the message to the :guilabel:`Starred` tab.
-- :icon:`fa-ellipsis-h` :guilabel:`(Expand)`: reveals more message actions, including:
+A company can also easily create :doc:`public and private channels <discuss/team_communication>`.
 
-  - :icon:`fa-thumb-tack` :guilabel:`Pin`
-  - :icon:`fa-eye-slash` :guilabel:`Mark as Unread`
-  - :icon:`fa-pencil` :guilabel:`Edit`
-  - :icon:`fa-trash` :guilabel:`Delete`
+Mentions in the chat and on the chatter
+---------------------------------------
 
-Conversation actions
---------------------
+To mention a user within a chat or the chatter, type `@user-name`; to refer to a channel, type
+`#channel-name`. The user mentioned will be notified in their *inbox* or through an email, depending
+on their communication settings.
 
-The icons in the top-right corner of a direct message conversation represent different actions the
-user can take on that conversation.
+.. image:: discuss/chat-windows.png
+   :alt: View of a couple of chat window messages for Odoo Discuss.
 
-Click :icon:`fa-bell` :guilabel:`Notification Settings` to set up notification preferences for the
-conversation, or click :icon:`fa-phone` :guilabel:`Start a Call` to begin a meeting. See the
-:ref:`Meetings <discuss/meetings>` section for more information about meetings.
-
-At the top of the direct message window, click the name of the direct message to change the group
-name, and choose to add a description in the adjacent :guilabel:`Add a description` field.
-
-.. image:: discuss/conversation-actions.png
-   :alt: View of the conversation actions.
-
-
-.. note::
-   The :guilabel:`Add a description` field is **only** available for group messages with more than
-   two participants.
+.. tip::
+   When a user is mentioned, the search list (list of names) suggests values first based on the
+   task's followers, and secondly on employees. If the record being searched does not match with
+   either a follower or employee, the scope of the search becomes all partners.
 
 User status
 -----------
 
-It is helpful to see what colleagues are up to, and how quickly they can respond to messages, by
-checking their status. The status is displayed as a circle in the bottom-right corner of a contact's
-photo in the :icon:`fa-users` :guilabel:`(Members List)`.
-
-The color of the circle represents the user's status:
+It is helpful to see what colleagues are up to and how quickly they can respond to messages by
+checking their *status*. The status is shown on the left side of a contact's name on the
+:guilabel:`Discuss` sidebar, on the *messaging menu* and when listed in the *chatter*.
 
 - Green = online
 - Orange = away
 - White = offline
 - Airplane = out of the office
 
-Leave a direct message conversation
------------------------------------
-
-To leave a direct message conversations, click the :icon:`fa-times` :guilabel:`(Leave this channel)`
-icon next to the conversation name in the :guilabel:`Direct Messages` section of the sidebar.
-
-.. note::
-   Leaving a conversation does **not** delete the direct messages in the conversation. The direct
-   message conversation's history is visible when another direct message with the same person, or
-   group, is created.
-
-.. _discuss/meetings:
-
-Meetings
-========
-
-In **Discuss**, *Meetings* are video calls. To start a meeting from the :guilabel:`Discuss`
-dashboard, click :guilabel:`Start a meeting` in the top-left corner, and select who to invite to the
-meeting, via the :guilabel:`Invite People` drop-down window that appears. To start a meeting from a
-direct message, click the :icon:`fa-phone` :guilabel:`Start a Call` icon in the top-right corner.
-
-.. image:: discuss/meeting.png
-   :alt: View of a Meeting in Odoo Discuss.
-
-Once a meeting has been started, the following buttons can be used:
-
-+-----------------------------+--------------------------------+
-| Icon                        | Use                            |
-+=============================+================================+
-| :icon:`fa-microphone`       | :guilabel:`Mute`               |
-+-----------------------------+--------------------------------+
-| :icon:`fa-microphone-slash` | :guilabel:`Unmute`             |
-+-----------------------------+--------------------------------+
-| :icon:`fa-headphones`       | :guilabel:`Deafen`             |
-+-----------------------------+--------------------------------+
-| :icon:`fa-deaf`             | :guilabel:`Undeafen`           |
-+-----------------------------+--------------------------------+
-| :icon:`fa-video-camera`     | :guilabel:`Turn camera on/off` |
-+-----------------------------+--------------------------------+
-| :icon:`fa-hand-paper-o`     | :guilabel:`Raise Hand`         |
-+-----------------------------+--------------------------------+
-| :icon:`fa-desktop`          | :guilabel:`Share Screen`       |
-+-----------------------------+--------------------------------+
-| :icon:`fa-arrows-alt`       | :guilabel:`Enter Full Screen`  |
-+-----------------------------+--------------------------------+
-
-.. _discuss_app/notification_preferences:
-
-User-specific notification preferences
-======================================
-
-Access user-specific preferences for the **Discuss** app by navigating to :menuselection:`Settings
-app --> Manage Users`, select a user, then click the :guilabel:`Preferences` tab.
-
-.. image:: discuss/preferences-user.png
-   :alt: View of the Preferences tab for Odoo Discuss.
-
-By default, the :guilabel:`Notification` field is set as :guilabel:`Handle by Emails`. With this
-setting enabled, a notification email is sent by Odoo every time a message is sent from the chatter
-of a record, a note is sent with an `@` mention (from the chatter of a record), or a notification is
-sent for a record the user follows.
-
-By choosing :guilabel:`Handle in Odoo`, the above notifications are shown in the **Discuss** app's
-*Inbox*.
-
-Chat from different applications
-================================
-
-The **Discuss** application enables communication across all of Odoo's applications. To view chats
-and channels, or start a new message, select the speech bubbles that are consistently present in the
-upper-right corner of the database header.
-
-.. image:: discuss/discuss-in-other-apps.png
-   :alt: Use Discuss across other applications by clicking the speech bubbles.
+.. image:: discuss/status.png
+   :height: 300
+   :alt: View of the contacts' status for Odoo Discuss.
 
 .. seealso::
    - :doc:`discuss/team_communication`
    - :doc:`/applications/essentials/activities`
-   - :doc:`discuss/ice_servers`
-   - :doc:`discuss/chatter`
 
 .. toctree::
    :titlesonly: