[IMP] orm: api.constraint deferred

The Odoo 17 and 18 RPM builds target Fedora 38 instead of 36:

16: https://github.com/odoo/odoo/blob/16.0/setup/package.dffedora#L3
17: https://github.com/odoo/odoo/blob/17.0/setup/package.dffedora#L3
18: https://github.com/odoo/odoo/blob/18.0/setup/package.dffedora#L3

Note that both Fedora 36 and 38 are EOL:
https://docs.fedoraproject.org/en-US/releases/eol/

closes odoo/documentation#11953

X-original-commit: 24966a91c8
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>

.tx/config

@@ -1,7 +1,7 @@
 [main]
 host = https://www.transifex.com
 
-[o:odoo:p:odoo-17-doc:r:administration]
+[o:odoo:p:odoo-18-doc:r:administration]
 file_filter            = locale/<lang>/LC_MESSAGES/administration.po
 source_file            = locale/sources/administration.pot
 type                   = POT
@@ -11,7 +11,7 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en
 
-[o:odoo:p:odoo-17-doc:r:applications]
+[o:odoo:p:odoo-18-doc:r:applications]
 file_filter            = locale/<lang>/LC_MESSAGES/applications.po
 source_file            = locale/sources/applications.pot
 type                   = POT
@@ -21,7 +21,7 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en
 
-[o:odoo:p:odoo-17-doc:r:essentials]
+[o:odoo:p:odoo-18-doc:r:essentials]
 file_filter            = locale/<lang>/LC_MESSAGES/essentials.po
 source_file            = locale/sources/essentials.pot
 type                   = POT
@@ -31,7 +31,7 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en
 
-[o:odoo:p:odoo-17-doc:r:finance]
+[o:odoo:p:odoo-18-doc:r:finance]
 file_filter            = locale/<lang>/LC_MESSAGES/finance.po
 source_file            = locale/sources/finance.pot
 type                   = POT
@@ -41,7 +41,7 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en
 
-[o:odoo:p:odoo-17-doc:r:general]
+[o:odoo:p:odoo-18-doc:r:general]
 file_filter            = locale/<lang>/LC_MESSAGES/general.po
 source_file            = locale/sources/general.pot
 type                   = POT
@@ -51,7 +51,7 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en
 
-[o:odoo:p:odoo-17-doc:r:hr]
+[o:odoo:p:odoo-18-doc:r:hr]
 file_filter            = locale/<lang>/LC_MESSAGES/hr.po
 source_file            = locale/sources/hr.pot
 type                   = POT
@@ -61,7 +61,7 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en
 
-[o:odoo:p:odoo-17-doc:r:index]
+[o:odoo:p:odoo-18-doc:r:index]
 file_filter            = locale/<lang>/LC_MESSAGES/index.po
 source_file            = locale/sources/index.pot
 type                   = POT
@@ -71,7 +71,7 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en
 
-[o:odoo:p:odoo-17-doc:r:inventory_and_mrp]
+[o:odoo:p:odoo-18-doc:r:inventory_and_mrp]
 file_filter            = locale/<lang>/LC_MESSAGES/inventory_and_mrp.po
 source_file            = locale/sources/inventory_and_mrp.pot
 type                   = POT
@@ -81,7 +81,7 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en
 
-[o:odoo:p:odoo-17-doc:r:marketing]
+[o:odoo:p:odoo-18-doc:r:marketing]
 file_filter            = locale/<lang>/LC_MESSAGES/marketing.po
 source_file            = locale/sources/marketing.pot
 type                   = POT
@@ -91,7 +91,7 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en
 
-[o:odoo:p:odoo-17-doc:r:productivity]
+[o:odoo:p:odoo-18-doc:r:productivity]
 file_filter            = locale/<lang>/LC_MESSAGES/productivity.po
 source_file            = locale/sources/productivity.pot
 type                   = POT
@@ -101,7 +101,7 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en
 
-[o:odoo:p:odoo-17-doc:r:sales]
+[o:odoo:p:odoo-18-doc:r:sales]
 file_filter            = locale/<lang>/LC_MESSAGES/sales.po
 source_file            = locale/sources/sales.pot
 type                   = POT
@@ -111,7 +111,7 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en
 
-[o:odoo:p:odoo-17-doc:r:services]
+[o:odoo:p:odoo-18-doc:r:services]
 file_filter            = locale/<lang>/LC_MESSAGES/services.po
 source_file            = locale/sources/services.pot
 type                   = POT
@@ -121,7 +121,7 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en
 
-[o:odoo:p:odoo-17-doc:r:user_settings]
+[o:odoo:p:odoo-18-doc:r:user_settings]
 file_filter            = locale/<lang>/LC_MESSAGES/settings.po
 source_file            = locale/sources/settings.pot
 type                   = POT
@@ -131,7 +131,7 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en
 
-[o:odoo:p:odoo-17-doc:r:studio]
+[o:odoo:p:odoo-18-doc:r:studio]
 file_filter            = locale/<lang>/LC_MESSAGES/studio.po
 source_file            = locale/sources/studio.pot
 type                   = POT
@@ -141,7 +141,7 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en
 
-[o:odoo:p:odoo-17-doc:r:websites]
+[o:odoo:p:odoo-18-doc:r:websites]
 file_filter            = locale/<lang>/LC_MESSAGES/websites.po
 source_file            = locale/sources/websites.pot
 type                   = POT

Makefile

@@ -27,7 +27,7 @@ SOURCE_DIR     = content
 
 HTML_BUILD_DIR = $(BUILD_DIR)/html
 ifdef VERSIONS
-  HTML_BUILD_DIR := $(HTML_BUILD_DIR)/saas-17.4
+  HTML_BUILD_DIR := $(HTML_BUILD_DIR)/master
 endif
 ifneq ($(CURRENT_LANG),en)
   HTML_BUILD_DIR := $(HTML_BUILD_DIR)/$(CURRENT_LANG)

conf.py

@@ -21,8 +21,8 @@ copyright = 'Odoo S.A.'
 
 # `version` is the version info for the project being documented, acts as replacement for |version|,
 # also used in various other places throughout the built documents.
-# `release` is the full version, including alpha/beta/rc tags. Acts as replacement for |release|.
-version = release = 'saas-17.4'
+# `release` is the full version, including a/b/rc tags. Acts as replacement for |release|.
+version = release = 'master'
 
 # `current_branch` is the technical name of the current branch.
 # E.g., saas-15.4 -> saas-15.4; 12.0 -> 12.0, master -> master (*).
@@ -116,7 +116,7 @@ else:
     odoo.addons.__path__.append(str(odoo_dir) + '/addons')
     from odoo import release as odoo_release  # Don't collide with Sphinx's 'release' config option
     odoo_version = '.'.join(str(s) for s in odoo_release.version_info[:2]).replace('~', '-')  # Change saas~XX.Y to saas-XX.Y
-    odoo_version = 'master' if 'alpha' in odoo_release.version else odoo_version
+    odoo_version = 'master' if odoo_release.ALPHA in odoo_release.version_info else odoo_version
     if release != odoo_version:
         _logger.warning(
             "Found Odoo sources in %(directory)s but with version '%(odoo_version)s' incompatible "
@@ -246,7 +246,9 @@ languages_names = {
     'de': 'DE',
     'en': 'EN',
     'es': 'ES',
+    'es_419': 'ES (LATAM)',
     'fr': 'FR',
+    'id': 'ID',
     'it': 'IT',
     'ja': 'JA',
     'ko': 'KR',
@@ -256,6 +258,7 @@ languages_names = {
     'sv': 'SV',
     'th': 'TH',
     'uk': 'UA',
+    'vi': 'VI',
     'zh_CN': 'ZH (CN)',
     'zh_TW': 'ZH (TW)'
 }

content/administration/mobile.rst

@@ -64,4 +64,4 @@ The Odoo mobile apps are available for download on the `Google Play Store
 .. important::
    The iOS app cannot be updated and will be deprecated at some point in the future.
 
-While the store apps support multi-accounts, they are not compatible with SS0 authentication.
+While the store apps support multi-accounts, they are not compatible with SSO authentication.

content/administration/odoo_accounts.rst

@@ -23,7 +23,7 @@ Edit Security Settings --> Delete Account`. It can also be accessed by going to
 Upon clicking the :guilabel:`Delete Account` button, a pop-up window appears, requesting
 confirmation for the account deletion.
 
-.. image:: odoo_accounts/delete-account.png
+.. image:: odoo_account/delete-account.png
    :align: center
    :alt: Clicking on the Delete Account button will populate a window verifying the change.
 

content/applications/essentials/contacts.rst

@@ -4,9 +4,9 @@
 Contacts
 ========
 
-The *Contacts* application comes installed on all Odoo databases. Contacts are created for customers
-the company does business with through Odoo. A contact is a repository of vital business
-information, facilitating communication and business transactions.
+Contacts are created in the **Contacts** application for customers the company does business with
+through Odoo. A contact is a repository of vital business information, facilitating communication
+and business transactions.
 
 Contact form
 ============

content/applications/essentials/export_import_data.rst

@@ -28,15 +28,13 @@ select a record, tick the checkbox next to the corresponding record. Finally, cl
 then :guilabel:`Export`.
 
 .. image:: export_import_data/list-view-export.png
-   :align: center
    :alt: View of the different things to enable/click to export data.
 
 When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over window appears, with
 several options for the data to export:
 
 .. image:: export_import_data/export-data-overview.png
-   :align: center
-   :alt: Overview of options to consider when exporting data in Odoo..
+   :alt: Overview of options to consider when exporting data in Odoo.
 
 #. With the :guilabel:`I want to update data (import-compatable export)` option ticked, the system
    only shows the fields that can be imported. This is helpful in the case where the :ref:`existing
@@ -87,7 +85,6 @@ data into an Odoo database.
    options: :guilabel:`Track history during import` and :guilabel:`Allow matching with subfields`.
 
    .. image:: export_import_data/advanced-import.png
-      :align: center
       :alt: Advanced import options when developer mode is activated.
 
    If the model uses openchatter, the :guilabel:`Track history during import` option sets up
@@ -96,6 +93,8 @@ data into an Odoo database.
    Should the :guilabel:`Allow matching with subfields` option be selected, then all subfields
    within a field are used to match under the :guilabel:`Odoo Field` while importing.
 
+.. _essentials/export_import_data/get-started:
+
 Get started
 -----------
 
@@ -103,30 +102,32 @@ Data can be imported on any Odoo business object using either Excel (`.xlsx`) or
 (Comma-separated Values)` (`.csv`) formats. This includes: contacts, products, bank statements,
 journal entries, and orders.
 
-Open the view of the object to which the data should be imported/populated, and click on
-:menuselection:`⚙️ (Action) --> Import records`.
+Open the view of the object to which the data should be imported/populated, click the :icon:`fa-cog`
+(:guilabel:`gear`) icon and select :guilabel:`Import records`.
 
 .. image:: export_import_data/import-button.png
-   :align: center
    :alt:  Action menu revealed with the import records option highlighted.
 
-After clicking :guilabel:`Import records`, Odoo reveals a separate page with templates that can be
-downloaded and populated with the company's own data. Such templates can be imported in one click,
-since the data mapping is already done. To download a template click :guilabel:`Import Template for
-Customers` at the center of the page.
+Click :icon:`fa-download`:guilabel:`Import Template for Customers` at the center of the page to
+download a :ref:`template <essentials/export_import_data/adapt-a-template>` and populate it with
+the company's own data. Such templates can be imported in one click since the data mapping is
+already preconfigured.
 
-.. important::
-   When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides :guilabel:`Formatting`
-   options. These options do **not** appear when importing the proprietary Excel file type (`.xls`,
-   `.xlsx`).
+To upload the downloaded template or your own file, follow the next steps:
 
-   .. image:: export_import_data/formatting.png
-      :align: center
-      :alt: Formatting options presented when a CVS file is imported in Odoo.
+#. Click :guilabel:`Upload Data File` and select the desired file.
+#. Adjust the :guilabel:`Formatting` options as needed (for CSV files only).
+#. Ensure all data in the :guilabel:`File Column` is correctly mapped to the appropriate
+   :guilabel:`Odoo Field` and free of errors.
+#. (Optional) Click :guilabel:`Load Data File` to reload the same file or upload a different one.
+#. Click :guilabel:`Test` to verify that the data is valid.
+#. Click :guilabel:`Import`.
 
-Make necessary adjustments to the *Formatting* options, and ensure all columns in the
-:guilabel:`Odoo field` and :guilabel:`File Column` are free of errors. Finally, click
-:guilabel:`Import` to import the data.
+.. note::
+   The :guilabel:`Formatting` options do **not** appear when importing the proprietary Excel file
+   type (i.e., `.xls` or `.xlsx`).
+
+.. _essentials/export_import_data/adapt-a-template:
 
 Adapt a template
 ----------------
@@ -144,7 +145,6 @@ Once the template is downloaded, proceed to follow these steps:
   (ID) column.
 
 .. image:: export_import_data/dragdown.gif
-   :align: center
    :alt: An animation of the mouse dragging down the ID column, so each record has a unique ID.
 
 .. note::
@@ -153,7 +153,6 @@ Once the template is downloaded, proceed to follow these steps:
    Search the drop-down menu for the corresponding field.
 
    .. image:: export_import_data/field_list.png
-      :align: center
       :alt: Drop-down menu expanded in the initial import screen on Odoo.
 
    Then, use this field's label in the import file to ensure future imports are successful.
@@ -203,7 +202,6 @@ If this happens, check the :guilabel:`Show fields of relation fields (advanced)
 complete list of fields becomes available for each column.
 
 .. image:: export_import_data/field_list.png
-   :align: center
    :alt: Searching for the field to match the tax column.
 
 Change data import format
@@ -401,6 +399,33 @@ respective contacts:
 - :download:`Customers and their respective contacts
   <export_import_data/o2m_customers_contacts.csv>`
 
+Import image files
+------------------
+
+To import image files along with the :ref:`uploaded <essentials/export_import_data/get-started>`
+CSV or Excel file, follow the next steps:
+
+#. Add the image file names to the relevant :guilabel:`Image` column in the data file.
+#. :ref:`Upload the data file <essentials/export_import_data/get-started>` or reload it by
+   clicking :guilabel:`Load Data File`.
+#. Click :guilabel:`Upload your files` under the :guilabel:`Files to import` section.
+#. Select the relevant image files. The number of files selected appears next to the button.
+#. Click :guilabel:`Test` to verify that all data is valid.
+#. Click :guilabel:`Import`. During the import process, Odoo performs a file check to automatically
+   link the uploaded images to the imported data file. If there is no match, the data file is
+   imported without any image.
+
+.. note::
+   - The :guilabel:`Files to import` section is enabled if your product template has an
+     :guilabel:`Image` column with all fields populated.
+   - The image file names in the data file must correspond to the uploaded image files.
+   - When importing a large number of images, you can specify the maximum batch size in megabytes
+     and set a delay to prevent the system from becoming overloaded. To do so, :doc:`enable the
+     developer mode <../general/developer_mode>` and fill in the :guilabel:`Max size per
+     batch` and the :guilabel:`Delay after each batch` fields in the :guilabel:`Files to import`
+     section. By default, the delay meets the RPC/API call limit defined in the `Odoo Cloud -
+     Acceptable Use Policy <https://www.odoo.com/acceptable-use>`_.
+
 Import records several times
 ----------------------------
 

content/applications/finance/accounting/bank.rst

@@ -4,7 +4,7 @@
 Bank and cash accounts
 ======================
 
-You can manage as many bank or cash accounts as needed on your database. Configuring them well
+You can manage as many bank or cash accounts as needed on your database. Configuring them correctly
 allows you to have all your banking data up-to-date and ready for :doc:`reconciliation
 <bank/reconciliation>` with your journal entries.
 
@@ -21,22 +21,22 @@ which include action buttons.
 .. image:: bank/card.png
    :alt: Bank journals are displayed on the Accounting Dashboard and contain action buttons
 
-.. _bank_accounts/manage:
+.. _accounting/bank/manage:
 
-Manage your bank and cash accounts
-==================================
+Manage bank and cash accounts
+=============================
 
-Connect your bank for automatic synchronization
------------------------------------------------
+Connect a bank for automatic synchronization
+--------------------------------------------
 
 To connect your bank account to your database, go to :menuselection:`Accounting --> Configuration
---> Banks: Add a Bank Account`, select your bank in the list, click on :guilabel:`Connect`, and
-follow the instructions.
+--> Add a Bank Account`, select your bank in the list, click on :guilabel:`Connect`, and follow the
+instructions.
 
 .. seealso::
    :doc:`bank/bank_synchronization`
 
-.. _bank_accounts/create:
+.. _accounting/bank/create:
 
 Create a bank account
 ---------------------
@@ -44,8 +44,9 @@ Create a bank account
 If your banking institution is not available in Odoo, or if you don't want to connect your bank
 account to your database, you can configure your bank account manually.
 
-To manually add a bank account, go to :menuselection:`Accounting --> Configuration --> Banks:
-Add a Bank Account`, click on :guilabel:`Create it` (at the bottom right), and fill out the form.
+To manually add a bank account, go to :menuselection:`Accounting --> Configuration --> Add a Bank
+Account`, click on :guilabel:`Record transactions manually` (at the bottom right), fill out the bank
+information, and click :guilabel:`Create`.
 
 .. note::
    - Odoo automatically detects the bank account type (e.g., IBAN) and enables some features
@@ -61,7 +62,7 @@ To create a new cash journal, go to :menuselection:`Accounting --> Configuration
 Journals`, click on :guilabel:`Create` and select :guilabel:`Cash` in the :guilabel:`Type` field.
 
 For more information on the accounting information fields, read the
-:ref:`bank_accounts/configuration` section of this page.
+:ref:`accounting/bank/configuration` section of this page.
 
 .. note::
    A default cash journal is available and can be used straight away. You can review it by going to
@@ -73,7 +74,7 @@ Edit an existing bank or cash journal
 To edit an existing bank journal, go to :menuselection:`Accounting --> Configuration --> Accounting:
 Journals` and select the journal you want to modify.
 
-.. _bank_accounts/configuration:
+.. _accounting/bank/configuration:
 
 Configuration
 =============
@@ -86,14 +87,23 @@ You can edit the accounting information and bank account number according to you
 .. seealso::
    - :doc:`get_started/multi_currency`
    - :doc:`bank/transactions`
+   - `Bank configuration <https://www.youtube.com/watch?v=tVhhXw-VnGE>`_
 
-.. _bank_accounts/suspense:
+.. _accounting/bank/suspense:
 
 Suspense account
 ----------------
 
-Bank statement transactions are posted on the :guilabel:`Suspense Account` until the final
-reconciliation allows finding the right account.
+Bank statement transactions are posted on the suspense account until they are reconciled. At any
+moment, the suspense account's balance in the general ledger shows the balance of transactions that
+have not yet been reconciled.
+
+.. note::
+   When a bank transaction is reconciled, the journal entry is modified to replace the bank suspense
+   account with the account of the journal item it is reconciled with. This account is usually the
+   :ref:`outstanding receipts or payments account <accounting/bank/outstanding-accounts>` if
+   reconciling with a registered payment or the account receivable or payable if reconciling with
+   an invoice or bill directly.
 
 Profit and loss accounts
 ------------------------
@@ -105,18 +115,16 @@ register a loss when the ending balance of a cash register differs from what the
 Currency
 --------
 
-You can edit the currency used to enter the statements.
+You can edit the currency used to enter the transactions.
 
 .. seealso::
    :doc:`get_started/multi_currency`
 
-.. _accounting/bank/account-number:
-
 Account number
 --------------
 
 If you need to **edit your bank account details**, click on the external link arrow next to your
-:guilabel:`Account Number`. On the new page, click on the external link arrow next to your
+:guilabel:`Account Number`. On the account page, click on the external link arrow next to your
 :guilabel:`Bank` and update your bank information accordingly. These details are used when
 registering payments.
 
@@ -126,12 +134,13 @@ registering payments.
 Bank feeds
 ----------
 
-:guilabel:`Bank Feeds` defines how the bank statements are registered. Three options are available:
+:guilabel:`Bank Feeds` defines how the bank transactions are registered. Three options are
+available:
 
 - :guilabel:`Undefined yet`, which should be selected when you don’t know yet if you will
   synchronize your bank account with your database or not.
 - :guilabel:`Import (CAMT, CODA, CSV, OFX, QIF)`, which should be selected if you want to import
-  your bank statement using a different format.
+  your bank statements and transactions using a different format.
 - :guilabel:`Automated Bank Synchronization`, which should be selected if your bank is synchronized
   with your database.
 
@@ -139,53 +148,47 @@ Bank feeds
    - :doc:`bank/bank_synchronization`
    - :doc:`bank/transactions`
 
-.. _bank/outstanding-accounts:
+.. _accounting/bank/outstanding-accounts:
 
 Outstanding accounts
 ====================
 
-By default, payments are registered through transitory accounts named **outstanding accounts**,
-before being recorded in your bank account.
+By default, payments in Odoo do not create journal entries, but they can easily be configured to
+create journal entries using **outstanding accounts**.
 
-- An **outstanding payments account** is where outgoing payments are posted until they are linked
-  with a withdrawal from your bank statement.
 - An **outstanding receipts account** is where incoming payments are posted until they are linked
-  with a deposit from your bank statement.
+  with incoming bank transactions.
+- An **outstanding payments account** is where outgoing payments are posted until they are linked
+  with outgoing bank transactions.
 
-These accounts should be of :ref:`type <chart-of-account/type>` :guilabel:`Current Assets`.
+These accounts are usually of :ref:`type <chart-of-account/type>` :guilabel:`Current Assets` and
+:guilabel:`Current Liabilities`.
+
+Payments that are registered in Odoo are posted to the outstanding receipts and outstanding accounts
+until they are reconciled. At any moment, the outstanding receipts account's balance in the general
+ledger shows the balance of registered incoming payments that have not yet been reconciled, and the
+outstanding payments account's balance in the general ledger shows the balance of registered
+outgoing payments that have not yet been reconciled.
+
+Bank and cash journal configuration
+-----------------------------------
+
+To configure payments to create journal entries, set outstanding accounts for the journal's payment
+methods. This can be done for any journal with the :ref:`type <chart-of-account/type>`
+:guilabel:`Bank` or :guilabel:`Cash`.
+
+To configure the outstanding accounts for a journal's payment methods, first go to
+:menuselection:`Accounting --> Configuration --> Journals` and select a bank or cash journal. In the
+:guilabel:`Incoming Payments` and :guilabel:`Outgoing Payments` tabs, set :guilabel:`Outstanding
+Receipts accounts` and :guilabel:`Outstanding Payments accounts` for each payment method that you
+want to create journal entries.
 
 .. note::
-   The movement from an outstanding account to a bank account is done automatically when you
-   reconcile the bank account with a bank statement.
-
-Default accounts configuration
-------------------------------
-
-The outstanding accounts are defined by default. If necessary, you can update them by going to
-:menuselection:`Accounting --> Configuration --> Settings --> Default Accounts` and update your
-:guilabel:`Outstanding Receipts Account` and :guilabel:`Outstanding Payments Account`.
-
-Bank and cash journals configuration
-------------------------------------
-
-You can also set specific outstanding accounts for any journal with the :ref:`type
-<chart-of-account/type>` :guilabel:`Bank` or :guilabel:`Cash`.
-
-From your :guilabel:`Accounting Dashboard`, click on the menu selection ⋮ of the journal you want to
-configure, and click on :guilabel:`Configuration`, then open the :guilabel:`Incoming/Outgoing
-Payments` tab. To display the outstanding accounts column, click on the toggle button and check the
-:guilabel:`Outstanding Receipts/Payments accounts`, then update the account.
-
-.. image:: bank/toggle-button.png
-   :align: center
-   :alt: Select the toggle button and click on outstanding Accounts
-
-.. note::
-   - If you do not specify an outstanding payments account or an outstanding receipts account for a
-     specific journal, Odoo uses the default outstanding accounts.
-   - If your main bank account is added as an outstanding receipts account or outstanding payments
-     account, when a payment is registered, the invoice or bill's status is directly set to
-     :guilabel:`Paid`.
+   - If the main bank account of the journal is added as an outstanding receipts account or
+     outstanding payments account, when a payment is registered, the invoice or bill's status is
+     directly set to :guilabel:`Paid`.
+   - If the outstanding receipts or outstanding payments account for a payment method is left blank,
+     registering a payment with that payment method will not create any journal entry.
 
 .. toctree::
    :titlesonly:
@@ -194,4 +197,6 @@ Payments` tab. To display the outstanding accounts column, click on the toggle b
    bank/transactions
    bank/reconciliation
    bank/reconciliation_models
+   bank/internal_transfers
    bank/foreign_currency
+   bank/loans

content/applications/finance/accounting/bank/bank_synchronization.rst

@@ -11,7 +11,7 @@ To check if your bank is compatible with Odoo, go to `Odoo Accounting Features
 <https://www.odoo.com/page/accounting-features>`_, and click on
 :guilabel:`See list of supported institutions`.
 
-Odoo supports more than 25,000 institutions around the world.
+Odoo supports more than 26,000 institutions around the world.
 
 To connect to the banks, Odoo uses multiple web-services:
 

content/applications/finance/accounting/bank/internal_transfers.rst

@@ -0,0 +1,71 @@
+==================
+Internal transfers
+==================
+
+Internal money transfers can be handled in Odoo. At least two bank or cash accounts are needed to
+make internal transfers.
+
+.. seealso::
+   :ref:`How to add an additional bank account <accounting/bank/create>`
+
+Configuration
+=============
+
+An internal transfer account is automatically created on your database based on your company's
+:doc:`localization <../../fiscal_localizations>` and depending on your country’s legislation. To
+modify the default :guilabel:`Internal Transfer` account, go to :menuselection:`Accounting -->
+Configuration --> Settings` and scroll down to the :guilabel:`Default Accounts` section.
+
+Register an internal transfer from one bank to another
+======================================================
+
+When money is transferred from one bank or cash account to another, that amount appears as two
+transactions on the corresponding journals, whether the transactions are created manually, via
+import, or via :doc:`bank synchronization <bank_synchronization>`. When reconciling the transaction,
+select the :guilabel:`Internal Transfers` :doc:`reconciliation model <reconciliation_models>`
+button. This reconciliation model button writes the transaction off to the :guilabel:`Internal
+Transfer` account.
+
+.. tip::
+   Remember to reconcile the transaction for both the outgoing transaction on the journal that sends
+   the payment and the incoming transaction on the journal that receives the payment.
+
+.. example::
+   Take, for example, a transfer of $1000 from Bank A to Bank B:
+
+   - Bank journal (Bank A)
+
+     .. list-table::
+        :header-rows: 1
+        :stub-columns: 1
+
+        * - **Account**
+          - **Debit**
+          - **Credit**
+        * - Bank A account
+          -
+          - $1,000
+        * - **Internal transfer account**
+          - **$1,000**
+          -
+
+   - Bank journal (Bank B)
+
+
+     .. list-table::
+        :header-rows: 1
+        :stub-columns: 1
+
+        * - **Account**
+          - **Debit**
+          - **Credit**
+        * - Bank B account
+          - $1,000
+          -
+        * - **Internal transfer account**
+          -
+          - **$1,000**
+
+.. seealso::
+   :doc:`reconciliation`
+   :doc:`reconciliation_models`

content/applications/finance/accounting/bank/loans.rst

@@ -0,0 +1,70 @@
+================
+Loans management
+================
+
+Odoo's loan management gives a comprehensive list of all loans undertaken by your company in order
+to maintain a holistic and forecasted view of upcoming due dates (e.g., cash forecast). Set up
+amortization schedules—or import them—and let Odoo automatically handle monthly interest and
+principal adjustments so that your financial reports are always accurate with minimal effort.
+
+Create a new loan
+-----------------
+
+Create a new loan by going to :menuselection:`Accounting --> Accounting --> Loans`. When creating a
+new loan, there are three options for how to create amortization schedules:
+
+- importing it from a supported file;
+- calculating it from multiple input values (e.g., the :guilabel:`Amount Borrowed`, the
+  :guilabel:`Duration`, etc.) using the :guilabel:`Compute` button;
+- manually filling in the lines of the schedule.
+
+In each case, three different fields are required for each line of the amortization schedule: the
+:guilabel:`Date`, the :guilabel:`Principal`, and the :guilabel:`Interest`.
+
+The :guilabel:`Amount Borrowed`, :guilabel:`Interest`, and :guilabel:`Duration` fields will be red
+if the sum of the lines does not match the total of the amortization schedule lines.
+
+Loan entries mechanism
+----------------------
+
+When the amount borrowed is credited to a bank account, it should be transferred to a long-term
+account (defined in the :guilabel:`Loan Settings` tab). Then, upon the validation of the loan, Odoo
+creates the necessary journal entries so that there is always a holistic and forecasted view of
+upcoming due dates. The entire process is completely automated with a long-term and short-term
+principal reclassification mechanism.
+
+For each line of the amortization schedule, Odoo creates the following entries:
+
+A payment entry on the same date that
+  - debits the principal amount to the long-term account;
+  - debits the interest amount to the expense account;
+  - credits the payment amount to the short-term account: this is the amount that will be
+    withdrawn by the bank.
+
+A reclassification entry on the same date that
+  - debits the sum of the principal amounts of the next 12 months to the long-term account;
+  - credits the sum of the principal amounts of the next 12 months to the short-term account.
+
+A reversed entry of the reclassification entry on *the next day* that simply reverses the previous
+one.
+
+With this mechanism, month after month, the short-term account is always up to date with the
+current short-term due amounts.
+
+Closing a loan
+--------------
+
+By default, a loan will be closed whenever its last payment entry is posted. However, it can also
+be manually closed (e.g., because it is being paid off early) by clicking on the :guilabel:`Close`
+button. A wizard will appear asking from which date the loan should be closed. All draft entries
+after this date will be deleted too.
+
+A loan can also be cancelled. In that case, all entries will be deleted even if they were already
+posted.
+
+Loans Analysis Report
+---------------------
+
+By going to :menuselection:`Accounting --> Reporting --> Loans Analysis`, you can access a
+report with a pivot view of your ongoing loans. By default, the report shows the principal,
+interest, and total payment for each year for the loan duration.

content/applications/finance/accounting/bank/transactions.rst

@@ -21,23 +21,25 @@ Import transactions
 
 Odoo supports multiple file formats to import transactions:
 
-- SEPA recommended Cash Management format (CAMT.053)
-- Comma-separated values (CSV)
-- Open Financial Exchange (OFX)
-- Quicken Interchange Format (QIF)
-- Belgium: Coded Statement of Account (CODA)
+- SEPA recommended Cash Management format (CAMT.053);
+- Comma-separated values (.CSV);
+- Open Financial Exchange (.OFX);
+- Quicken Interchange Format (.QIF);
+- Belgium: Coded Statement of Account (.CODA).
 
-To import a file, go to the :guilabel:`Accounting Dashboard`, and in the :guilabel:`Bank` journal,
+To import a file, go to the **Accounting Dashboard**, and in the :guilabel:`Bank` journal,
 click on :guilabel:`Import File`.
 
 .. tip::
    Alternatively, you can also:
 
-   - click the :icon:`fa-ellipsis-v` :guilabel:`(ellipsis)` icon on the :guilabel:`Bank`
-     journal and select :guilabel:`Import file`;
-   - or access the transaction list by clicking the :icon:`fa-ellipsis-v` :guilabel:`(ellipsis)`
-     icon on the :guilabel:`Bank` journal and selecting :guilabel:`Transactions`, then click
-     the :icon:`fa-cog` :guilabel:`(gear)` icon and select :guilabel:`Import records`.
+   - click :guilabel:`⋮` on the :guilabel:`Bank` journal and select :guilabel:`Import file`;
+   - or access the transaction list by clicking :guilabel:`⋮` on the :guilabel:`Bank` journal and
+     selecting :guilabel:`Transactions`, then click the gear icon :guilabel:`(⚙)` and select
+     :guilabel:`Import records`.
+
+     .. image:: transactions/import-transactions.png
+        :alt: Import bank transactions from the bank journal
 
 Next, select the file and upload it.
 
@@ -73,28 +75,22 @@ on your business flow, you may want to record them for control purposes.
    account balance as of the date you begin synchronizing or importing transactions. This is
    necessary to ensure the accuracy of your accounting.
 
-To access a list of existing statements, go to the :guilabel:`Accounting Dashboard`, click the
-:icon:`fa-ellipsis-v` :guilabel:`(ellipsis)` icon next to the bank or cash journal you want to
-check, then click :guilabel:`Statements`.
-
-.. _transactions/statement-kanban:
+To access a list of statements, go to your :guilabel:`Accounting Dashboard`, click on the vertical
+ellipsis (:guilabel:`⋮`) button next to the bank or cash journal you want to check, then on
+:guilabel:`Statements`
 
 Statement creation from the kanban view
 ---------------------------------------
 
-Open the bank reconciliation (kanban) view from the :guilabel:`Accounting Dashboard` by clicking on
-the name of the bank journal and identify the transaction corresponding to the last (most recent)
-transaction of your bank statement. Click on the :guilabel:`Statement` button when hovering on the
-upper separator line to create a statement from that transaction down to the oldest transaction that
-is not yet part of a statement.
+Open the bank reconciliation view by clicking on the name of the bank journal, and identify the
+transaction corresponding to the last transaction of your bank statement. Click on the
+:guilabel:`STATEMENT` button when hovering on the upper separator line.
 
 .. image:: transactions/statements-kanban.png
-   :alt: A "Statement" button is visible when hovering on the line separating two transactions.
+   :alt: A "STATEMENT" button is visible when hovering on the line separating two transactions.
 
-In the :guilabel:`Create Statement` window, fill out the statement's :guilabel:`Reference`, verify
-its :guilabel:`Starting Balance` and :guilabel:`Ending Balance`, and click :guilabel:`Save`.
-
-.. _transactions/statement-list:
+Fill out the statement's details and save. The newly created statement includes the previous
+transactions following the last statement.
 
 Statement creation from the list view
 -------------------------------------
@@ -104,35 +100,3 @@ view. Select all the transactions corresponding to the bank statement, and, in t
 :guilabel:`Statement` column, select an existing statement or create a new one by typing its
 reference, clicking on :guilabel:`Create and edit...`, filling out the statement's details, and
 saving.
-
-.. _transactions/view-edit-print:
-
-Statement viewing, editing, and printing
-----------------------------------------
-
-To view an existing statement, click on the statement amount in the reconciliation (kanban) view or
-click on the statement name in the bank transaction list view. From here, you can edit the
-:guilabel:`Reference`, :guilabel:`Starting Balance`, or :guilabel:`Ending Balance`.
-
-.. note::
-   Manually updating the :guilabel:`Starting Balance` automatically updates the :guilabel:`Ending
-   Balance` based on the new value of the :guilabel:`Starting Balance` and the value of the
-   statement's transactions.
-
-.. warning::
-   If the :guilabel:`Starting Balance` doesn't equal the previous statement's :guilabel:`Ending
-   Balance`, or if the :guilabel:`Ending Balance` doesn't equal the running balance
-   (:guilabel:`Starting Balance` plus the statement's transactions), a warning appears explaining
-   the issue. To maintain flexibility, it is still possible to save without first resolving the
-   issue.
-
-To attach a digital copy (i.e., JPEG, PNG, or PDF) of the bank statement for enhanced recordkeeping,
-click the :icon:`fa-paperclip` :guilabel:`Attachments` button and select the file to attach.
-
-To generate and print a PDF of the bank statement, click the :guilabel:`Print` button (if accessed
-via the reconciliation view) or click on the :icon:`fa-cog`:guilabel:`(gear)` icon and click
-:icon:`fa-print`:guilabel:`Statement` (if accessed via the list view).
-
-.. note::
-   When a bank statement is generated to be printed, it is automatically added to the
-   :guilabel:`Attachments`.

content/applications/finance/accounting/customer_invoices.rst

@@ -82,7 +82,7 @@ confirmation, Odoo assigns each document a unique number from a defined
    - 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:`Lock posted entries with hash <data-inalterability/lock>` feature.
+     using the :ref:`Secure posted entries with hash <data-inalterability/restricted>` feature.
 
 .. _accounting/invoice/sending:
 

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

@@ -13,49 +13,33 @@ 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, among others, the following formats.
+Odoo supports e-invoicing in many countries. Refer to the country's page for more details:
 
-.. 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.
+- :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>`
 
 .. seealso::
-   :doc:`../../fiscal_localizations`
+   :doc:`Fiscal localizations documentation <../../fiscal_localizations>`
 
 .. _e-invoicing/configuration:
 

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

@@ -0,0 +1,52 @@
+: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

@@ -0,0 +1,50 @@
+: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

@@ -0,0 +1,53 @@
+: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

@@ -0,0 +1,50 @@
+: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

@@ -0,0 +1,47 @@
+: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

@@ -0,0 +1,47 @@
+: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

@@ -0,0 +1,47 @@
+: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

@@ -0,0 +1,50 @@
+: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

@@ -0,0 +1,47 @@
+: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

@@ -0,0 +1,46 @@
+: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

@@ -0,0 +1,46 @@
+: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

@@ -0,0 +1,50 @@
+: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

@@ -0,0 +1,45 @@
+: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

@@ -0,0 +1,46 @@
+: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

@@ -0,0 +1,47 @@
+: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

@@ -0,0 +1,46 @@
+: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

@@ -0,0 +1,44 @@
+: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

@@ -0,0 +1,45 @@
+: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

@@ -0,0 +1,48 @@
+: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

@@ -0,0 +1,54 @@
+: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

@@ -0,0 +1,45 @@
+: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

@@ -0,0 +1,50 @@
+: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/payments.rst

@@ -15,7 +15,7 @@ for use at a later date:
   reduce/settle unpaid invoices/bills.
 
 .. seealso::
-   - :doc:`Internal transfers <payments/internal_transfers>`
+   - :doc:`Internal transfers <bank/internal_transfers>`
    - :doc:`bank/reconciliation`
    - `Odoo Tutorials: Bank Configuration
      <https://www.odoo.com/slides/slide/bank-configuration-6832>`_
@@ -25,17 +25,16 @@ for use at a later date:
 Registering payment from an invoice or bill
 ===========================================
 
-Clicking :guilabel:`Register payment` in a customer invoice or vendor bill generates a new journal
-entry and sets the amount due according to the payment amount. The counterpart is reflected in an
-:ref:`outstanding <bank/outstanding-accounts>` **receipts** or **payments** account. At this point,
-the customer invoice or vendor bill is marked as :guilabel:`In payment` or :ref:`Partially paid
-<accounting/payments/partial-payment>`. Then, when the outstanding account is reconciled with a bank
-transaction, the invoice or vendor bill changes to the :guilabel:`Paid` status.
+When clicking :guilabel:`Register payment` in a customer invoice or vendor bill, it generates a new
+journal entry and changes the amount due according to the payment amount. The counterpart is
+reflected in an :ref:`outstanding <accounting/bank/outstanding-accounts>` **receipts** or
+**payments** account. At this point, the customer invoice or vendor bill is marked as :guilabel:`In
+payment`. Then, when the outstanding account is reconciled with a bank transaction line, the invoice
+or vendor bill changes to the :guilabel:`Paid` status.
 
-To open the :guilabel:`Journal Entry Info` window and display more information about the payment,
-click the :icon:`fa-info-circle` :guilabel:`(information)` icon in the footer of the
-:guilabel:`Invoice Lines` tab. To access additional information, such as the related journal entry,
-click :guilabel:`View`.
+The :icon:`fa-info-circle` information icon next to the payment line displays more
+information about the payment. To access additional information, such as the related journal, click
+:guilabel:`View`.
 
 .. image:: payments/information-icon.png
    :alt: See detailed information of a payment.
@@ -47,13 +46,13 @@ click :guilabel:`View`.
      invoice.
    - If a payment is (un)reconciled in a different currency, a journal entry is automatically
      created to post the currency exchange gains/losses (reversal) amount.
-   - If a payment is (un)reconciled on an invoice with cash-basis taxes, a journal entry is
+   - If a payment is (un)reconciled and an invoice with cash-basis taxes, a journal entry is
      automatically created to post the cash-basis tax (reversal) amount.
 
 .. tip::
-   If the main bank account is set as the :ref:`outstanding account <bank/outstanding-accounts>` on
-   the bank journal's payment method, registering the full payment on an invoice or bill moves the
-   invoice/bill directly to the :guilabel:`Paid` status without requiring bank reconciliation.
+   If the main bank account is set as an :ref:`outstanding account
+   <accounting/bank/outstanding-accounts>`, and the payment is registered in Odoo (not through a
+   related bank transaction), invoices and bills are directly registered as :guilabel:`Paid`.
 
 .. _accounting/payments/not-tied:
 
@@ -63,107 +62,92 @@ Registering payments not tied to an invoice or bill
 When a new payment is registered via :menuselection:`Customers / Vendors --> Payments`, it is not
 directly linked to an invoice or bill. Instead, the account receivable or the account payable is
 matched with the **outstanding account** until it is manually matched with its related invoice or
-bill. Then, :doc:`reconciling <bank/reconciliation>` the payment with the bank transaction completes
-the payment workflow.
-
-.. _accounting/payments/payments-matching:
-
-Payments matching
------------------
-
-.. note::
-   During the :doc:`bank reconciliation <bank/reconciliation>` process, a remaining balance is
-   identified if the total debits and credits do not match when records are compared with bank
-   transactions. This balance must either be reconciled later or written off immediately.
+bill.
 
 .. _accounting/payments/matching-invoices-bills:
 
-For a single invoice or bill
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Matching invoices and bills with payments
+-----------------------------------------
 
 A blue banner appears when validating a new invoice/bill and an **outstanding payment** exists for
-this specific customer or vendor. To match it with the invoice or bill, click :guilabel:`Add`
+this specific customer or vendor. To match it with the invoice or bill, click :guilabel:`ADD`
 under :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`.
 
 .. image:: payments/add-option.png
-   :alt: Shows the Add option to reconcile an invoice or a bill with a payment.
+   :alt: Shows the ADD option to reconcile an invoice or a bill with a payment.
 
-The invoice or bill is then marked as :guilabel:`In payment` until the payment is :doc:`reconciled
-<bank/reconciliation>` with its corresponding :doc:`bank transaction(s) <bank/transactions>`.
-
-.. _accounting/payments/auto-reconcile-tool:
-
-Matching payments
-~~~~~~~~~~~~~~~~~
-
-The :guilabel:`Payments matching` or :guilabel:`Auto-reconcile` tool allows reconciling journal
-items with each other (i.e., payments with customer invoices or vendor bills) either individually or
-in batches. Access the :guilabel:`Accounting Dashboard`, click the :icon:`fa-ellipsis-v`
-(:guilabel:`dropdown menu`) button from the :guilabel:`Customer Invoices` or :guilabel:`Vendor
-Bills` journals, and select :guilabel:`Payments Matching`. Alternatively, go to
-:menuselection:`Accounting --> Accounting --> Reconcile`.
-
-To manually :guilabel:`Reconcile` journal items, select the individual items from the list view and
-click :guilabel:`Reconcile`.
-
-Auto-Reconcile Feature
-**********************
-
-To use the :guilabel:`Auto-Reconcile` feature, follow these steps:
-
-#. In the :guilabel:`Journal Items to reconcile` list view, click :guilabel:`Auto-Reconcile` next to
-   the receivable or payable account (or a specific contact's journal item in that account).
-#. In the :guilabel:`Find Entries to Reconcile Automatically` window, set the :guilabel:`Reconcile`
-   field depending on how you want to match journal items:
-
-   - :guilabel:`Opposite balances one by one`: Each debit journal item will be matched with the
-     corresponding credit journal item of the same value.
-   - :guilabel:`Accounts with zero balances`: All reconciled journal items will have the same
-     matching number.
-
-#. Click :guilabel:`Launch`.
-
-Invoices and bills are automatically matched to their corresponding payments and marked as
-:guilabel:`In payment` until they are :doc:`reconciled <bank/reconciliation>` with their
-corresponding :doc:`bank transactions <bank/transactions>`.
+The invoice or bill is now marked as :guilabel:`In payment` until it is reconciled with its
+corresponding bank transaction.
 
 .. _accounting/payments/group-payments:
 
-Registering payments on multiple invoices or bills (group payments)
-===================================================================
+Group payments
+--------------
 
-To register payments on multiple invoices/bills, follow these steps:
+Group payments allow combining outgoing and incoming payments from the same contact into a single
+payment to simplify the process and improve payment usability. To register a group payment:
 
 #. Go to :menuselection:`Accounting --> Customers --> Invoices/Credit Notes` or
    :menuselection:`Accounting --> Vendors --> Bills/Refunds`.
-#. In the list view, select the relevant invoices/credit notes or bills/refunds.
-#. Click :icon:`fa-cog` :guilabel:`Actions` and select :guilabel:`Register Payment`.
+#. Select the relevant invoices/credit notes or bills/refunds linked to a specific contact.
+#. Click the :icon:`fa-cog` (:guilabel:`Action menu`) icon and select :guilabel:`Register Payment`.
 #. In the :guilabel:`Register Payment` window, select the :guilabel:`Journal`, the
    :guilabel:`Payment Method`, and the :guilabel:`Payment Date`.
-#. To combine all payments from the same contact into a single payment, enable the :guilabel:`Group
-   Payments` option, or leave it unchecked to create separate payments.
-#. Click :guilabel:`Create payment`.
+#. Enable the :guilabel:`Group Payments` option and click :guilabel:`Create payment`.
 
-The invoices or bills are then marked as :guilabel:`In payment` until the bank transactions are
-:doc:`reconciled <bank/reconciliation>` with the payments.
+The invoices or bills are now marked as :guilabel:`In payment` until they are reconciled with the
+corresponding bank transactions. The credit notes or refunds are marked as :guilabel:`Paid`.
 
 .. _accounting/payments/batch-payments:
 
-Registering a single payment for multiple customers or vendors (batch payments)
-===============================================================================
+Batch payments
+--------------
 
 Batch payments allow grouping payments from multiple contacts to ease
 :doc:`reconciliation <bank/reconciliation>`. They are also useful when depositing :doc:`checks
-<payments/checks>` to the bank or for generating bank payment files such as :doc:`SEPA
-<payments/pay_sepa>` or :ref:`NACHA <l10n_us/nacha>`. To do so, go to :menuselection:`Accounting -->
-Customers --> Payments` or :menuselection:`Accounting --> Vendors --> Payments`. In the payments
-list view, select the payments to be grouped in a batch, click :icon:`fa-cog` :guilabel:`Actions`,
-and select :guilabel:`Create Batch Payment`.
+<payments/checks>` to the bank or for :doc:`SEPA payments <payments/pay_sepa>`. To do so, go to
+:menuselection:`Accounting --> Customers --> Batch Payments` or :menuselection:`Accounting -->
+Vendors --> Batch Payments`. In the list view of payments, to group several payments in a
+batch, select them and click :menuselection:`Action --> Create Batch Payment`.
 
 .. seealso::
   - :doc:`payments/batch`
   - :doc:`payments/batch_sdd`
 
+.. _accounting/payments/matching:
+
+Payments matching
+-----------------
+
+The :guilabel:`Payments matching` tool opens all unreconciled customer invoices or vendor bills and
+allows them to be processed individually, matching all payments and invoices in one place. Go to the
+:guilabel:`Accounting Dashboard`, click the :icon:`fa-ellipsis-v` (:guilabel:`dropdown menu`)
+button from the :guilabel:`Customer Invoices` or :guilabel:`Vendor Bills` journals, and select
+:guilabel:`Payments Matching`, or go to :menuselection:`Accounting --> Accounting -->
+Reconciliation`.
+
+.. image:: payments/payments-journal.png
+   :alt: Payments matching menu in the drop-down menu.
+
+.. note::
+   During the :doc:`reconciliation <bank/reconciliation>`, if the sum of the debits and credits does
+   not match, there is a remaining balance. This either needs to be reconciled at a later date or
+   written off directly.
+
+.. _accounting/payments/batch-payments-matching:
+
+Batch payments matching
+-----------------------
+
+Use the batch reconciliation feature to reconcile several outstanding payments or invoices
+simultaneously for a specific customer or vendor. Go to :menuselection:`Accounting --> Reporting -->
+Aged Receivable / Aged Payable`. All transactions that have not yet been reconciled for that
+contact are visible, and when a customer or vendor is selected, the :guilabel:`Reconcile` option is
+displayed.
+
+.. image:: payments/reconcile-option.png
+   :alt: The batch payment reconcile option.
+
 .. _accounting/payments/partial-payment:
 
 Registering a partial payment
@@ -189,9 +173,8 @@ Reconciling payments with bank transactions
 ===========================================
 
 Once a payment has been registered, the status of the invoice or bill is :guilabel:`In payment`. The
-next step is :doc:`reconciling <bank/reconciliation>` the payment with the related :doc:`bank
-transaction <bank/transactions>` line to finalize the payment workflow and mark the invoice or bill
-as :guilabel:`Paid`.
+next step is :doc:`reconciling <bank/reconciliation>` it with the related bank transaction line to
+finalize the payment workflow and mark the invoice or bill as :guilabel:`Paid`.
 
 .. toctree::
    :titlesonly:
@@ -201,7 +184,6 @@ as :guilabel:`Paid`.
    payments/batch
    payments/batch_sdd
    payments/follow_up
-   payments/internal_transfers
    payments/pay_sepa
    payments/pay_checks
    payments/forecast

content/applications/finance/accounting/payments/checks.rst

@@ -17,7 +17,7 @@ into account checks yet to be cashed.
    statement.
 
 .. seealso::
-   * :ref:`Outstanding accounts <bank/outstanding-accounts>`
+   * :ref:`Outstanding accounts <accounting/bank/outstanding-accounts>`
    * :ref:`Bank reconciliation <accounting/reconciliation>`
 
 .. _checks/outstanding-account:

content/applications/finance/accounting/payments/internal_transfers.rst

@@ -1,73 +0,0 @@
-==================
-Internal transfers
-==================
-
-Internal money transfers can be handled in Odoo. At least two bank accounts are needed to make
-internal transfers.
-
-.. seealso::
-   :doc:`How to add an additional bank account <../bank>`
-
-Configuration
-=============
-
-An internal transfer account is automatically created on your database based on your company's
-localization and depending on your country’s legislation. To modify the default :guilabel:`Internal
-transfer account`, go to :menuselection:`Accounting --> Configuration --> Settings` and scroll down
-to the :guilabel:`Default Accounts` section.
-
-Register an internal transfer from one bank to another
-======================================================
-
-If you want to transfer money from one bank to another, access the Accounting Dashboard, click the
-drop-down selection button (:guilabel:`⋮`) on the bank from which you want to make the transfer,
-then click :guilabel:`Payments`. Select or create a payment, tick the :guilabel:`Internal Transfer`
-checkbox, and select a :guilabel:`Destination Journal` before you :guilabel:`Confirm` the internal
-transfer.
-
-The money is now booked in the transfer account and another payment is automatically created in the
-destination journal.
-
-.. example::
-
-   - Bank journal (Bank A)
-
-     .. list-table::
-        :header-rows: 1
-        :stub-columns: 1
-
-        * - **Account**
-          - **Debit**
-          - **Credit**
-        * - Outstanding Payments account
-          -
-          - $1,000
-        * - **Internal transfer account**
-          - **$1,000**
-          -
-
-   - Bank journal (Bank B)
-
-
-     .. list-table::
-        :header-rows: 1
-        :stub-columns: 1
-
-        * - **Account**
-          - **Debit**
-          - **Credit**
-        * - Outstanding Receipts account
-          - $1,000
-          -
-        * - **Internal transfer account**
-          -
-          - **$1,000**
-
-   There is **one outstanding payment** and **one outstanding receipt** pending in your two bank
-   account journals because the bank statement confirming the sending and receiving of the money
-   has not been booked yet.
-
-Once this is done, you can book and reconcile your bank statement lines as usual.
-
-.. seealso::
-   :doc:`../bank/reconciliation`

content/applications/finance/accounting/reporting/analytic_accounting.rst

@@ -6,12 +6,16 @@ Analytic accounting helps you track costs and revenues, as well as analyze the p
 project or service. When creating your journal entries, the analytic widget allows the distribution
 of costs in one or more analytic accounts.
 
+.. _accounting/analytic_accounting/configuration:
+
 Configuration
 =============
 
 Enable the :guilabel:`Analytic Accounting` feature by going to :menuselection:`Accounting -->
 Configuration --> Settings --> Analytics`.
 
+.. _accounting/analytic_accounting/analytic_accounts:
+
 Analytic accounts
 =================
 
@@ -25,14 +29,14 @@ and fill in the required information:
 - :guilabel:`Customer`: select the customer related to your project;
 - :guilabel:`Reference`: add a reference to make it easier to find the account when you are on your
   bill;
-- :guilabel:`Plan`: add an :ref:`analytic plan <analytic_accounting/analytic_plans>`;
+- :guilabel:`Plan`: add an :ref:`analytic plan <accounting/analytic_accounting/analytic_plans>`;
 - :guilabel:`Company`: if you are managing multiple companies, select the company for which the
   analytic account will be used;
 - :guilabel:`Currency`: select the currency of the analytic account;
 
 Then, fill in your :doc:`budget <budget>` information.
 
-.. _analytic_accounting/analytic_plans:
+.. _accounting/analytic_accounting/analytic_plans:
 
 Analytic plans
 ==============
@@ -83,6 +87,8 @@ Two smart buttons are available in the top-right corner:
      :ref:`Analytic Distribution Models <analytic_distribution_models>`;
    - Each analytic plan must have at least one analytic account.
 
+.. _accounting/analytic_accounting/analytic-distribution:
+
 Analytic distribution
 =====================
 
@@ -98,6 +104,8 @@ accounts by modifying the percentage.
 
 .. _analytic_distribution_models:
 
+.. _accounting/analytic_accounting/analytic-distribution-models:
+
 Analytic distribution models
 ----------------------------
 

content/applications/finance/accounting/reporting/budget.rst

@@ -1,102 +1,170 @@
-================
+=======
+Budgets
+=======
+
+:ref:`Analytic budgets <accounting/budgets/analytic-budgets>` track specific activities and projects
+using analytic accounts, helping businesses make informed decisions about specific departments,
+projects, or other groups of transactions. In contrast, :ref:`financial budgets
+<accounting/budgets/financial>` are tied to the general ledger accounts that appear on the profit
+and loss and focus on the company's overall economic position.
+
+.. _accounting/budgets/analytic-budgets:
+
 Analytic budgets
 ================
 
-Managing budgets is an essential part of running a business. Budgets help people become more
-intentional with how money is spent and direct people to organize and prioritize their work to meet
-financial goals. They allow the planning of a desired financial outcome and then measure the actual
-performance against the plan. Odoo manages budgets using both **general** and **analytic accounts**.
+Analytic budgets allow for allocating and tracking income and expenses in detail, breaking down
+costs and revenues by specific projects, departments, or groups of transactions. Analytic budgets
+can be applied across various departments or projects to measure profitability and performance. Odoo
+manages analytic budgets using :doc:`analytic accounting <analytic_accounting>`.
 
-Configuration
-=============
+To activate the option for creating analytic budgets, go to :menuselection:`Accounting -->
+Configuration --> Settings`, and enable :guilabel:`Budget Management` in the :guilabel:`Analytics`
+section.
 
-Go to :menuselection:`Accounting --> Configuration --> Settings --> Analytics section`, and enable
-:guilabel:`Budget Management`.
+.. important::
+   Odoo structures budgets using :ref:`plans <accounting/analytic_accounting/analytic_plans>` and
+   :ref:`accounts <accounting/analytic_accounting/analytic_accounts>`, which must be configured
+   *before* creating a budget.
 
-Budgetary positions
--------------------
+.. _accounting/budgets/analytic-budget-set:
 
-Budgetary positions are lists of accounts for which you want to keep budgets (typically expense or
-income accounts).
+Set an analytic budget
+----------------------
 
-To define budgetary positions, go to :menuselection:`Accounting --> Configuration --> Management:
-Budgetary Positions` and :guilabel:`New`. Add a :guilabel:`Name` to your budgetary position and
-select the :guilabel:`Company` it applies to. Click :guilabel:`Add a line` to add one or more
-accounts.
+To create a new budget, go to :menuselection:`Accounting --> Accounting --> Analytic Budgets` and
+click :guilabel:`New`. Make sure the following fields are appropriately completed: :guilabel:`Budget
+Name`, :guilabel:`Period`, and :guilabel:`Budget Type`.
+
+Click :guilabel:`Add a line` in the :guilabel:`Budget Lines` tab to structure the budget with the
+:ref:`analytic plans <accounting/analytic_accounting/analytic_plans>` and :ref:`accounts
+<accounting/analytic_accounting/analytic_accounts>` previously created. While the :ref:`analytic
+plans <accounting/analytic_accounting/analytic_plans>` correspond to the column names, select the
+:ref:`analytic accounts <accounting/analytic_accounting/analytic_accounts>` to define the budget
+lines and set the amounts for each in the :guilabel:`Budgeted` column. Once all the budget lines are
+settled, click :guilabel:`Open`. If changes need to be made once the budget's status is
+:guilabel:`Open`, there are two options:
+
+- :guilabel:`Reset to Draft`: To overwrite the data, then reopen the budget.
+- :guilabel:`Revise`: A new budget will be created. Once it is :guilabel:`Open`, a :guilabel:`Rev`
+  reference is added to the :guilabel:`Budget Name`. The original budget is then
+  :guilabel:`Revised`.
+
+.. _accounting/budgets/analytic-budget-check:
+
+Check an analytic budget
+------------------------
+
+Once the budget is :guilabel:`Open`, two additional columns are available: :guilabel:`Committed` and
+:guilabel:`Achieved`. These columns' amounts are automatically calculated based on the related
+:ref:`analytic distribution <accounting/analytic_accounting/analytic-distribution>` of journal
+items. When the :ref:`analytic distribution <accounting/analytic_accounting/analytic-distribution>`
+of a journal item within the budget's period is updated, the budget's columns for the analytic
+account(s) selected in the distribution are automatically updated. The :guilabel:`Achieved` amount
+reflects the current result according to the items of confirmed journal entries for the associated
+:ref:`analytic account <accounting/analytic_accounting/analytic_accounts>`. In contrast, the
+:guilabel:`Committed` amount displays the full value of the :guilabel:`Achieved` amount, plus any
+confirmed sales or purchase orders that have not yet been invoiced or billed.
 
 .. note::
-   Each budgetary position can have any number of accounts from the chart of accounts, though it
-   must have at least one.
+   - When a line in a request for quotation or purchase order includes an analytic distribution, a
+     :guilabel:`Budget` smart button appears, providing a link to the :ref:`budget report
+     <accounting/budgets/analytic-budget-reporting>` for more details.
+   - For :guilabel:`Open` budgets, if a request for quotation or a purchase order is created using
+     the associated analytic distribution and exceeds the allocated budget amount, the corresponding
+     purchase order line is highlighted in red.
 
-Use case
-========
+To reveal the :guilabel:`Theoretical` amount or percentage, use the :icon:`oi-settings-adjust`
+(:guilabel:`adjust settings`) icon in the :guilabel:`Budget Lines`' header. The
+:guilabel:`Theoretical` amount represents the amount of money that could theoretically have been
+spent or should have been received based on the current date relative to the start/end dates. Click
+:guilabel:`Details` to open a filtered view of the :ref:`budget report
+<accounting/budgets/analytic-budget-reporting>` related to that specific budget line.
 
-Let’s illustrate this with an example.
+.. image:: budget/budget.png
+   :alt: open budget with committed, achieved, and theoretical amounts
 
-We just started a project with *Smith & Co*, and we would like to budget the income and expenses of
-that project. We plan on having a revenue of 1000, and we don’t want to spend more than 700.
+.. note::
+   Deleting a budget is only allowed in the :guilabel:`Draft` and :guilabel:`Cancelled` stages.
 
-First, we need to define what accounts relate to our project’s expenses. Go to
-:menuselection:`Accounting --> Configuration --> Management: Budgetary positions`, and click
-:guilabel:`New` to add a position. Add the accounts wherein expenses will be booked.
+To view the budget lines of one or multiple budgets directly from the :guilabel:`Budgets` list view,
+select the budget(s) and click :guilabel:`Budget Lines`.
 
-.. image::  budget/smith-and-co-expenses.png
-   :align: center
-   :alt: display the Smith and Co expenses
+.. _accounting/budgets/analytic-budget-generate:
 
-Let's repeat the steps to create a budgetary position that reflects the revenue.
+Generate periodic budgets
+-------------------------
 
-.. image::  budget/smith-and-co-revenue.png
-   :align: center
-   :alt: display the Smith and Co revenue
+To create periodic budgets (monthly, quarterly, and yearly) for the selected :guilabel:`Analytic
+Plans`, click :guilabel:`Generate`. A new budget is created for each :guilabel:`Period` between the
+start and end dates:
 
-Analytical accounts
--------------------
+- If a single analytic plan is selected, each budget includes a line for each account in that
+  analytic plan.
+- If multiple analytic plans are selected, each budget includes a line for each account/analytic
+  plan combination.
 
-Odoo needs to know which costs or expenses are relevant to a specified budget, as the above general
-accounts may be used for different projects. Go to :menuselection:`Accounting --> Configuration -->
-Analytic Accounting: Analytic Accounts` and click :guilabel:`New` to add a new **Analytic Account**
-called *Smith & Co*.
+To generate periodic budgets, follow these steps:
 
-The :guilabel:`Plan` field has to be completed. Plans group multiple analytic accounts; they
-distribute costs and benefits to analyze business performance. **Analytic Plans** can be created or
-configured by going to :menuselection:`Accounting --> Configuration --> Analytic Accounting:
-Analytic Plans`.
+#. In the :guilabel:`Budgets` list view, click :guilabel:`Generate`.
+#. In the :guilabel:`Generate Budget` window, set the dates and select the :guilabel:`Period` and
+   the :guilabel:`Analytic Plans`.
 
-When creating a new customer invoice and/or vendor bill, you have to refer to this analytic account.
+   .. image:: budget/generate-budgets.png
+      :alt: all the options to generate periodical budgets
 
-.. image:: budget/analytic-accounts.png
-   :align: center
-   :alt: add analytic accounts in a new invoice or bill.
+#. Click :guilabel:`Split` to create the periodic budgets.
+#. Click :guilabel:`Budgets` in the top-left corner to return to the :guilabel:`Budgets` list view.
+#. One by one, click on the different periodic budgets with the :guilabel:`Draft` status to open
+   them and set the amounts in the :guilabel:`Budgeted` column for each analytic account linked to
+   the chosen analytic plans.
+#. Click :guilabel:`Open` for each periodic budget.
 
-Define the budget
------------------
+.. _accounting/budgets/analytic-budget-reporting:
 
-Let’s set our targets. We specified that we expect to gain 1000 with this project, and we would like
-not to spend more than 700. Go to :menuselection:`Accounting --> Management: Budgets` and click
-:guilabel:`New` to create a new budget for *Smith & Co* project.
+Reporting
+---------
 
-First, fill in your :guilabel:`Budget Name`. Then, select the :guilabel:`Period` wherein the budget
-is applicable. Next, add the :guilabel:`Budgetary Position` you want to track, define the related
-:guilabel:`Analytic Account`, and add the :guilabel:`Planned Amount`.
+To perform various reporting actions, go to :menuselection:`Accounting --> Reporting -->
+Budget Report`, then:
 
-.. image:: budget/define-the-budget.png
-   :align: center
-   :alt: budget lines display
+- Track, analyze, and compare budget data.
+- Filter and group data using the :icon:`fa-plus-square` (:guilabel:`plus-square`) or
+  :icon:`fa-minus-square` :guilabel:`(minus-square)` icon.
+- Drill down into the report to see more details on the actual amounts and transactions.
+- Export the data for further analysis or reporting needs.
 
-.. Note::
-   When recording a planned amount related to expenses, the amount must be negative.
+.. _accounting/budgets/financial:
 
-Check your budget
------------------
+Financial budgets
+=================
 
-Go to :menuselection:`Accounting --> Management: Budgets` and find the *Smith & Co* Project to see
-how it evolves according to the expenses or income for the related analytic account.
+Financial budgets are structured around specific income and expense accounts and transactions for
+official financial reporting and compliance purposes.
 
-The :guilabel:`Practical Amount` evolves when a new journal entry related to your analytic account
-and an account from your budgetary position is created.
+.. note::
+   Financial budgets are available on the :ref:`Profit and Loss
+   <accounting/reporting/profit-and-loss>` report.
 
-The :guilabel:`Theoretical Amount` represents the amount of money you theoretically could have spent
-or should have received based on the date. For example, suppose your budget is 1200 for 12 months
-(January to December), and today is 31 of January. In that case, the theoretical amount will be 100
-since this is the actual amount that could have been made.
+.. _accounting/budgets/financial-budget-set:
+
+Set a financial budget
+----------------------
+
+To create a new financial budget, follow these steps:
+
+#. Go to :menuselection:`Accounting --> Reporting --> Profit and Loss` to open the
+   :ref:`Profit and Loss <accounting/reporting/profit-and-loss>` report.
+#. Click the :icon:`fa-calendar` :guilabel:`(calendar)` button to use the date selector and choose a
+   period.
+#. Click the :icon:`fa-bar-chart` :guilabel:`Budget` button and name the budget. A new column
+   labeled with the budget name will appear next to the :guilabel:`Balance` column.
+#. Assign amounts to each account requiring analysis.
+#. A new :guilabel:`%` column will appear to the right of the new budget column, indicating the
+   current status.
+
+Different financial budgets can be created using these steps for comparison purposes.
+
+.. note::
+   The date selector enables the division of periods and navigation between periods, automatically
+   updating the amounts accordingly.

content/applications/finance/accounting/reporting/data_inalterability.rst

@@ -3,10 +3,10 @@ Data inalterability check report
 ================================
 
 Tax authorities in some countries require companies to **prove their posted accounting entries are
-inalterable**, meaning that once an entry has been posted, it can no longer be changed.
+unaltered**, meaning that once an entry has been secured, it can no longer be changed.
 
-To do so, Odoo can use the **SHA-256 algorithm** to create a unique fingerprint for each posted
-entry. This fingerprint is called a hash. The hash is generated by taking an entry's essential data
+To do so, Odoo creates a unique fingerprint for each secured entry thanks to the **SHA-256 algorithm**.
+This fingerprint is called a hash. The hash is generated by taking an entry's essential data
 (the values of the `name`, `date`, `journal_id`, `company_id`, `debit`, `credit`, `account_id`, and
 `partner_id` fields), concatenating it, and inputting it to the SHA-256 hash function, which then
 outputs a fixed size (256-bit) string of characters. The hash function is deterministic (:dfn:`the
@@ -15,7 +15,7 @@ completely change the resulting hash. Consequently, the SHA-256 algorithm is oft
 others, for data integrity verification purposes.
 
 In addition, the previous entry's hash is always added to the next entry to form a **hash chain**.
-This is used to ensure a new entry is not added afterward between two posted entries, as doing so
+This is used to ensure a new entry is not added afterward between two secured entries, as doing so
 would break the hash chain.
 
 .. note::
@@ -24,27 +24,70 @@ would break the hash chain.
    bigger than the number of atoms in the known universe. This is why hashes are considered unique
    in practice.
 
-.. _data-inalterability/lock:
+.. _data-inalterability/inalterability_features:
 
-Lock entries with hash
-======================
+Inalterability features
+=======================
 
-To start using the hashing function, go to :menuselection:`Accounting --> Configuration > Journals`.
-Open the journal for which you want to activate the feature, go to the :guilabel:`Advanced Settings`
-tab, and enable :guilabel:`Lock Sent Invoices with Hash` for sale journals, or
-:guilabel:`Lock Entries Manually` for purchase and general journals.
+Inalterability features can be enabled by activating the :ref:`secure posted entries with hash
+<data-inalterability/restricted>` option on any journal or using the :ref:`secure entries wizard
+<data-inalterability/wizard>`.
 
-For sale journals, the entry is automatically locked once it is sent. You can also click on the
-button :guilabel:`Lock` on the invoice to lock it without sending it. For sale, purchase, and
-general journals, the locking is always done manually using the same button.
+- Two indicators are added to the journal entry's form view.
+  They show whether the entry is secured or not.
+
+  - A :icon:`fa-lock` or :icon:`fa-unlock` (:guilabel:`lock icon`) next to the :guilabel:`Posted` state.
+  - A :guilabel:`Secured` checkbox in the :guilabel:`Other info` tab.
+
+- A :guilabel:`Not Secured` filter is available on journal entries and journal items' list views.
+  It can be used to find posted journal entries that are not secured yet.
+- The option to open the :ref:`secure entries wizard <data-inalterability/wizard>` is displayed in the
+  :guilabel:`Accounting` menu.
+
+.. _data-inalterability/restricted:
+
+Secure posted entries with hash
+===============================
+
+To activate the hashing function on a specific journal, go to :menuselection:`Accounting -->
+Configuration --> Journals`. Open a sales, purchase, or miscellaneous journal, go to the
+:guilabel:`Advanced Settings` tab, and enable :guilabel:`Secure Posted Entries with Hash`.
+Journals for which the feature is activated are called "restricted".
 
 To compute the hash of an entry, Odoo retrieves the predecessor entries of the chain (i.e., the
 entries with the same sequence prefix) and hashes them in a continuous way from the last hashed
 entry to the new entry to hash.
 
 .. warning::
-   Once you lock an entry in a locked journal, you cannot disable the feature anymore, nor edit any
-   locked entry.
+   Once you post an entry in a restricted journal, you cannot disable the feature anymore, nor edit
+   any secured entry.
+
+.. _data-inalterability/wizard:
+
+Secure entries wizard
+=====================
+
+You can also use the :guilabel:`Secure Entries` Wizard to secure all journal entries,
+in **all** journals, up to a specific date.
+
+.. note::
+   The wizard operates independently of the journal settings and journal types.
+
+To open it, activate the :ref:`developer mode <developer-mode>`, go to :menuselection:`Accounting
+--> Accounting`, and click on :guilabel:`Secure Entries`. If the :ref:`inalterability features
+<data-inalterability/inalterability_features>` are activated, it is also visible outside the debug
+mode.
+
+To secure entries, select a date up to which all entries should be secured and press
+:guilabel:`Secure Entries`.
+
+.. warning::
+   After securing the entries, you can no longer edit them.
+
+.. note::
+   It can happen that entries that are past the selected date are secured.
+   This is possible since the hash chain corresponds to the sequence prefix,
+   ordered by sequence number.
 
 .. _data-inalterability/report:
 
@@ -54,17 +97,18 @@ Report download
 To download the data inalterability check report, go to :menuselection:`Accounting --> Configuration
 --> Settings --> Reporting` and click on :guilabel:`Download the Data Inalterability Check Report`.
 
-The report's first section is an overview of all your journals and their configuration. Under the
-inalterability check column, you can see whether or not a journal's entries are locked with a hash
-(V) or not (X). The coverage column tells you when a journal's entries started being locked.
+The report's first section is an overview of all journal sequence prefixes containing hashed entries.
+In the :guilabel:`Restricted` column, you can see whether or not a journal has the :ref:`secure
+posted entries with hash <data-inalterability/restricted>` option (V) activated or not (X). The
+:guilabel:`Check` column tells you whether all entries are correctly hashed.
 
 .. image:: data_inalterability/journal-overview.png
    :align: center
    :alt: Configuration report for two journals
 
-The second section gives you the result of the data consistency check for each hashed journal. You
-can view the first hashed entry and its corresponding hash and the last hashed entry and its
-corresponding hash.
+The second section gives a more detailed result of the data consistency check for each hashed
+journal sequence prefix. You can view the first hashed entry and its corresponding hash,
+as well as the last hashed entry and its corresponding hash.
 
 .. image:: data_inalterability/data-consistency-check.png
    :align: center

content/applications/finance/accounting/reporting/tax_returns.rst

@@ -35,9 +35,6 @@ To do so, go to :menuselection:`Accounting --> Configuration --> Settings`. Unde
 - :guilabel:`Reminder`: define when Odoo should remind you to submit your tax return;
 - :guilabel:`Journal`: select the journal in which to record the tax return.
 
-.. image:: tax_returns/tax_return_periodicity.png
-   :align: center
-   :alt: Configure how often tax returns have to be made in Odoo Accounting
 
 .. note::
    This is usually configured during the :doc:`app's initial set up <../get_started>`.
@@ -53,16 +50,11 @@ You can see the :guilabel:`Tax Grids` by opening the :guilabel:`Journal Items` t
 invoice and bill.
 
 .. image:: tax_returns/tax_return_grids.png
-   :align: center
    :alt: see which tax grids are used to record transactions in Odoo Accounting
 
 To configure your tax grids, go to :menuselection:`Accounting --> Configuration --> Taxes`,
 and open the tax you want to modify. There, you can edit your tax settings, along with the tax
-grids that are used to record invoices or credit notes.
-
-.. image:: tax_returns/tax_return_taxes.png
-   :align: center
-   :alt: Configure taxes and their tax grids in Odoo Accounting
+grids that are used to record invoices or refunds.
 
 .. note::
    Taxes and reports are usually already pre-configured in Odoo: a :ref:`fiscal localization package
@@ -76,44 +68,42 @@ Close a tax period
 
 .. _tax-returns/lock-date:
 
-Tax Lock Date
+Tax lock date
 -------------
 
-Any new transaction whose accounting date prior to the :guilabel:`Tax Lock Date` has its tax values
-moved to the next open tax period. This is useful to make sure that no change can be made to a
-report once its period is closed.
+Any new transaction whose accounting date prior to the :guilabel:`Lock Tax Return` date has its tax
+values moved to the next open tax period. This is useful to make sure that no change can be made to
+a report once its period is closed.
 
 Therefore, we recommend locking your tax date before working on your
 :guilabel:`Closing Journal Entry`.
 This way, other users cannot modify or add transactions that would have an impact on the
 :guilabel:`Closing Journal Entry`, which can help you avoid some tax declaration errors.
 
-To check the current :guilabel:`Tax Lock Date`, or to edit it, go to
-:menuselection:`Accounting --> Accounting --> Actions: Lock Dates`.
-
-.. image:: tax_returns/tax_return_lock.png
-   :align: center
-   :alt: Lock your tax for a specific period in Odoo Accounting
+To check the current :guilabel:`Lock Tax Return` date, or to edit it, go to
+:menuselection:`Accounting --> Accounting --> Lock Dates`.
 
 .. _tax-returns/report:
 
-Tax Report
+Tax return
 ----------
 
 Once all the transactions involving taxes have been posted for the period you want to report, open
-the :guilabel:`Tax Report` by going to :menuselection:`Accounting --> Reporting --> Tax Report`.
-Select the period you want to declare using the date filter to have an overview of the tax report.
-From the report, click :guilabel:`PDF` or :guilabel:`XLSX` to download the desired format of the tax
-report. To save the report to the Documents app, click the :icon:`fa-caret-down` (:guilabel:`down
-arrow`) icon, then click :guilabel:`Save`. Select the format to :guilabel:`Export to`, the
+the :guilabel:`Tax Return` report by going to :menuselection:`Accounting --> Reporting --> Tax
+Return`. Select the period you want to declare using the date filter to have an overview of the tax
+return. Then, click :guilabel:`Closing Entry` to create a tax closing journal entry. Odoo
+automatically proposes the details of the journal entry. Make any necessary changes and click
+:guilabel:`Post`.
+
+From the report, click :guilabel:`PDF` to download a PDF of the tax return. Alternatively, click the
+:icon:`fa-cog` (:guilabel:`gear`) icon, then click :guilabel:`Download Excel` to download an XLSX of
+the tax return. To save the report to the Documents app, click the :icon:`fa-cog` (:guilabel:`gear`)
+icon, then click :guilabel:`Copy to Documents`. Select the format to :guilabel:`Export to`, the
 :guilabel:`Documents Name`, the :guilabel:`Folder` to store it in, and add any :guilabel:`Tags`.
 
 The report includes all the values to report to the tax authorities, along with the amount to be
 paid or refunded.
 
-.. image:: tax_returns/tax_return_report.png
-   :alt: download the PDF with your Tax Report in Odoo Accounting
-
 .. note::
    If you forgot to lock your tax date before clicking on :guilabel:`Closing Journal Entry`, then
    Odoo automatically locks your fiscal period on the same date as the accounting date of your

content/applications/finance/accounting/reporting/year_end.rst

@@ -43,7 +43,7 @@ Before closing a fiscal year, ensure first everything is accurate and up-to-date
 - Validate all :doc:`expenses <../../expenses>`, ensuring their accuracy.
 - Corroborate that all :doc:`received payments <../payments>` have been encoded and recorded
   accurately.
-- Close all :ref:`suspense accounts <bank_accounts/suspense>`.
+- Close all :ref:`suspense accounts <accounting/bank/suspense>`.
 - Book all :doc:`depreciation <../vendor_bills/assets>` and :doc:`deferred revenue
   <../customer_invoices/deferred_revenues>` entries.
 
@@ -62,7 +62,7 @@ Then, to close the fiscal year:
     <accounting/reporting/aged-payable>` reports.
   - Audit all accounts, being sure to fully understand all transactions and their nature, making
     sure to include loans and fixed assets.
-  - Optionally, :ref:`match payments <accounting/payments/auto-reconcile-tool>` to validate any open
+  - Optionally, run :ref:`payments matching <accounting/payments/matching>` to validate any open
     vendor bills and customer invoices with their payments. While this step is optional, it could
     assist the year-end closing process if all outstanding payments and invoices are reconciled,
     potentially finding errors or mistakes in the system.

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

@@ -24,10 +24,8 @@ programming interface)` integration.
 .. important::
    Some limitations exist in Odoo while using AvaTax for tax calculation:
 
-   - 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.
+   - 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.
    - Excise tax is **not** supported. This includes tobacco/vape taxes, fuel taxes, and other
      specific industries.
 

content/applications/finance/accounting/vendor_bills.rst

@@ -37,7 +37,7 @@ appropriately completed:
 - :guilabel:`Vendor`: Odoo automatically fills some information based on the vendor's registered
   information, previous purchase orders, or bills.
 - :guilabel:`Bill Reference`: add the sales order reference provided by the vendor and is used to do
-  the :ref:`matching <accounting/payments/payments-matching>` when you receive the products.
+  the :ref:`matching <accounting/payments/matching>` when you receive the products.
 - :guilabel:`Auto-Complete`: select a past bill/purchase order to automatically complete the
   document. The :guilabel:`Vendor` field should be completed prior to completing this field.
 - :guilabel:`Bill Date`: is the issuance date of the document.

content/applications/finance/fiscal_localizations.rst

@@ -4,128 +4,163 @@
 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:
 
-Fiscal localization packages
-============================
+Configuration
+=============
 
-**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.
+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.
 
 .. note::
-   Odoo continuously adds new localizations and improves the existing packages.
+   Each company in a multi-company environment can use different fiscal localization modules.
 
-Configuration
--------------
+.. _fiscal_localizations/accounting:
 
-Odoo automatically installs the appropriate package for your company, according to the country
-selected at the creation of the database.
+Accounting
+----------
 
-.. important::
-   As long as you haven't posted any entry, you can still select another package.
+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.
 
-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.
+.. warning::
+   Selecting another package is only possible if no entry has been posted.
 
-.. image:: fiscal_localizations/package-selection.png
-   :alt: Select your country's fiscal localization package in Odoo Accounting.
+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.
 
-Use
----
+.. _fiscal_localizations/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.
+Payroll
+-------
 
-.. seealso::
-   - :doc:`accounting/get_started/chart_of_accounts`
-   - :doc:`accounting/taxes`
+Localization settings can be accessed by going to :menuselection:`Payroll --> Configuration -->
+Settings` and searching for the country's **Localization** section.
 
 .. _fiscal_localizations/countries-list:
 
-List of supported countries
-===========================
+List of countries
+=================
 
-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.
+Fiscal localization modules are available for the countries listed below.
 
-- 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
+.. 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
 - :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
 
-  - 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>`
+.. seealso::
+   :doc:`Employment Hero Payroll documentation <fiscal_localizations/employment_hero>`
 
 .. toctree::
    :titlesonly:
@@ -152,17 +187,17 @@ available on Odoo.
    fiscal_localizations/mexico
    fiscal_localizations/netherlands
    fiscal_localizations/new_zealand
-   fiscal_localizations/romania
    fiscal_localizations/peru
    fiscal_localizations/philippines
+   fiscal_localizations/romania
    fiscal_localizations/saudi_arabia
    fiscal_localizations/singapore
    fiscal_localizations/spain
    fiscal_localizations/switzerland
    fiscal_localizations/thailand
-   fiscal_localizations/vietnam
    fiscal_localizations/united_arab_emirates
    fiscal_localizations/united_kingdom
    fiscal_localizations/united_states
    fiscal_localizations/uruguay
+   fiscal_localizations/vietnam
    fiscal_localizations/employment_hero