[IMP] base: ir.cron documentation

New function and description of how to write CRON jobs and related best-practices. task-4472661
[MOV] accounting: invoice sequence section on a separate page
2025-02-24 10:17:01 +00:00 · 2025-02-22 06:15:03 +00:00 · 2025-02-22 06:14:58 +00:00 · 2025-02-21 18:05:14 +00:00 · 2025-02-21 16:38:11 +00:00 · 2025-02-21 16:38:04 +00:00
792 changed files with 30345 additions and 18432 deletions
@@ -21,7 +21,7 @@ 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|.
+# `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.
@@ -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 "
@@ -231,6 +231,7 @@ sphinx.transforms.i18n.docname_to_domain = (
 # is populated. If a version is passed to `versions` but is not listed here, it will not be shown.
 versions_names = {
    'master': "Master",
+    'saas-18.1': "Odoo Online",
    '18.0': "Odoo 18",
    'saas-17.4': "Odoo Online",
    'saas-17.2': "Odoo Online",
@@ -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.
@@ -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_account/delete-account.png
+.. image:: odoo_accounts/delete-account.png
   :align: center
   :alt: Clicking on the Delete Account button will populate a window verifying the change.

@@ -132,7 +132,7 @@ be downloaded from the `Odoo download page <https://www.odoo.com/page/download>`
   .. group-tab:: Fedora

      .. note::
-         Odoo {CURRENT_MAJOR_VERSION} 'rpm' package supports Fedora 36.
+         Odoo {CURRENT_MAJOR_VERSION} 'rpm' package supports Fedora 38.

      Once downloaded, the package can be installed using the 'dnf' package manager:

@@ -31,6 +31,12 @@ This matrix shows the support status of every version.
     - On-Premise
     - Release date
     - End of support
+   * - Odoo SaaS 18.1
+     - |green|
+     - N/A
+     - N/A
+     - January 2025
+     -
   * - **Odoo 18.0**
     - |green|
     - |green|
@@ -38,17 +44,17 @@ This matrix shows the support status of every version.
     - October 2024
     - October 2027 (planned)
   * - Odoo SaaS 17.4
-     - |green|
+     - |red|
     - N/A
     - N/A
     - July 2024
-     -
+     - October 2024
   * - Odoo SaaS 17.2
-     - |green|
+     - |red|
     - N/A
     - N/A
     - April 2024
-     -
+     - October 2024
   * - **Odoo 17.0**
     - |green|
     - |green|
@@ -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
 ----------------------------

@@ -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,16 +115,18 @@ 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.

@@ -124,12 +136,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.

@@ -137,53 +150,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:
@@ -192,5 +199,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
@@ -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:

@@ -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`
@@ -21,25 +21,23 @@ 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 **Accounting Dashboard**, and in the :guilabel:`Bank` journal,
+To import a file, go to the :guilabel:`Accounting Dashboard`, and in the :guilabel:`Bank` journal,
 click on :guilabel:`Import File`.

 .. tip::
   Alternatively, you can also:

-   - 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
+   - 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`.

 Next, select the file and upload it.

@@ -75,22 +73,28 @@ 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 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`
+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:

 Statement creation from the kanban view
 ---------------------------------------

-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.
+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.

 .. 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.

-Fill out the statement's details and save. The newly created statement includes the previous
-transactions following the last statement.
+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:

 Statement creation from the list view
 -------------------------------------
@@ -100,3 +104,35 @@ 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`.
@@ -7,8 +7,7 @@ Customer invoices
 A customer invoice is a document issued by a company for products and/or services sold to a
 customer. It records receivables as they are sent to customers. Customer invoices can include
 amounts due for the goods and/or services provided, applicable sales taxes, shipping and handling
-fees, and other charges.
-Odoo supports multiple invoicing and payment workflows.
+fees, and other charges. Odoo supports multiple invoicing and payment workflows.

 .. seealso::
   :doc:`/applications/finance/accounting/customer_invoices/overview`
@@ -44,22 +43,31 @@ goods and services. Make sure the following fields are appropriately completed:
  upon confirmation.
 - :guilabel:`Due Date` or :doc:`payment terms <customer_invoices/payment_terms>`: To specify when
  the customer has to pay the invoice.
- :guilabel:`Journal`: Is automatically set and can be changed if needed.
- :doc:`Currency <get_started/multi_currency>`
- :guilabel:`Product`: Click :guilabel:`Add a line` to add a product.
+- :guilabel:`Journal`: Automatically set and can be changed if needed.
+- :doc:`Currency <get_started/multi_currency>`. If the invoice's currency differs from the
+  company's currency, the currency exchange rate is automatically displayed.
+
+In the :guilabel:`Invoice Lines` tab:
+
+- :guilabel:`Product`: Click :guilabel:`Add a line`, then search for and select the product.
 - :guilabel:`Quantity`
 - :guilabel:`Price`
 - :doc:`Taxes <taxes>` (if applicable)

+To access the product catalog and view all items in an organized display, click :doc:`Catalog
+</applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/product_catalog>`.
+When the products and quantities are selected, click :guilabel:`Back to Invoice` to return to the
+invoice; the selected catalog items will appear in the invoice lines.
+
 .. tip::
   To display the total amount of the invoice in words, go to :menuselection:`Accounting -->
   Configuration --> Settings` and activate the :guilabel:`Total amount of invoice in letters`
   option.

-The :guilabel:`Journal Items` tab displays the accounting entries created.
-Additional invoice information such as the :guilabel:`Customer Reference`, :doc:`Fiscal Positions
-<taxes/fiscal_positions>`, :doc:`Incoterms <customer_invoices/incoterms>`, and more can be added or
-modified in the :guilabel:`Other Info` tab.
+The :guilabel:`Journal Items` tab displays the accounting entries created. Additional invoice
+information such as the :guilabel:`Customer Reference`, :guilabel:`Payment Reference`, :doc:`Fiscal
+Positions <taxes/fiscal_positions>`, :doc:`Incoterms <customer_invoices/incoterms>`, and more can be
+added or modified in the :guilabel:`Other Info` tab.

 .. note::
   Odoo initially creates invoices in :guilabel:`Draft` status. Draft invoices have no accounting
@@ -73,32 +81,72 @@ modified in the :guilabel:`Other Info` tab.
 Invoice confirmation
 ====================

-Click :guilabel:`Confirm` when the document is completed. The document's status changes to
+Click :guilabel:`Confirm` when the invoice is completed. The invoice's status changes to
 :guilabel:`Posted`, and a journal entry is generated based on the invoice configuration. On
-confirmation, Odoo assigns each document a unique number from a defined
-:ref:`sequence <accounting/invoice/sequence>`.
+confirmation, Odoo assigns each invoice a unique number from a defined :doc:`sequence
+<customer_invoices/sequence>`.

 .. note::
   - Once confirmed, an invoice can no longer be updated. Click :guilabel:`Reset to draft` if
     changes are needed.
-   - If required, invoices and other journal entries can be locked once posted
-     using the :ref:`Secure posted entries with hash <data-inalterability/restricted>` feature.
+   - If required, invoices and other journal entries can be locked once posted using the
+     :ref:`Secure posted entries with hash <data-inalterability/restricted>` feature.

 .. _accounting/invoice/sending:

 Invoice sending
 ===============

-To send the invoice to the customer, click :guilabel:`Send & Print`. A :guilabel:`Configure your
-document layout` pop-up window will appear if a :ref:`default invoice layout
-<studio/pdf-reports/default-layout>` hasn't been customized. Then, select how to send this invoice
-to the customer in the :guilabel:`Send` window.
+To set a preferred :guilabel:`Invoice sending` method for a customer, go to
+:menuselection:`Accounting --> Customers --> Customers` and select the customer. In the
+:guilabel:`Accounting` tab of the contact form, select the preferred :guilabel:`Invoice sending`
+method in the :guilabel:`Customer Invoices` section.

-To send and print multiple invoices, go to :menuselection:`Accounting --> Customers --> Invoices`
-and select them. Then click the :icon:`fa-cog` :guilabel:`Actions` menu and select
-:guilabel:`Send & Print`. A banner will appear on the selected invoices to indicate they are part of
-an ongoing send and print batch. This helps prevent the process from being triggered manually again,
-as it may take some time to complete for exceptionally large batches.
+.. note::
+   Sending letters in Odoo requires :doc:`In-App Purchase (IAP) <../../essentials/in_app_purchase>`
+   credit or tokens.
+
+To send the invoice to the customer, navigate back to the invoice record and follow these steps:
+
+#. Click :guilabel:`Print & Send`.
+#. If the :ref:`default invoice layout <studio/pdf-reports/default-layout>` has not been customized
+   yet, a :guilabel:`Configure your document layout` pop-up window appears. Configure the layout and
+   click :guilabel:`Continue`.
+
+   .. note::
+      - The document layout can be changed at any time in the general settings.
+      - To add a QR code for banking app payments to the invoice, enable the :guilabel:`QR Code`
+        option in the :guilabel:`Configure Your Document Layout` window. To modify this option, go
+        to :menuselection:`Accounting --> Configuration --> Settings`, scroll down to the
+        :guilabel:`Customer Payments` section, and enable/disable the :guilabel:`QR Codes` option.
+
+#. In the :guilabel:`Print & Send` window:
+
+   - If a preferred :guilabel:`Invoice sending` method was set in the contact form, it is selected
+     by default. Select another one if needed.
+   - If no preferred :guilabel:`Invoice sending` method was set in the contact form, select the
+     method to use for sending the invoice to the customer.
+
+#. Click :guilabel:`Print & Send` if the :guilabel:`by Email` option is selected, or click
+   :guilabel:`Print`.
+
+.. _accounting/invoice/sending-multiple-invoices:
+
+Sending multiple invoices
+-------------------------
+
+To send and print multiple invoices, go to :menuselection:`Accounting --> Customers --> Invoices`,
+select them in the :guilabel:`Invoices` list view and click :guilabel:`Print & Send`. The
+:guilabel:`Print & Send` window displays the selected invoice sending methods based on the preferred
+method set.
+
+A banner is added to the selected invoices to indicate they are part of an ongoing send and print
+batch. This helps prevent the process from being triggered manually again, as it may take some time
+to complete for exceptionally large batches.
+
+To check all invoices that have not yet been sent, go to :menuselection:`Accounting --> Customers
+--> Invoices`. In the :guilabel:`Invoices` list view, click into the search bar and filter on
+:guilabel:`Not Sent`.

 .. _accounting/invoice/paymentandreconciliation:

@@ -123,81 +171,6 @@ how much the customer is overdue. These actions are bundled into follow-up level
 an invoice is overdue by a certain number of days. If there are multiple overdue invoices for the
 same customer, the actions are performed on the most overdue invoice.

-.. _accounting/invoice/sequence:
-
-Sequence
-========
-
-The sequence that Odoo assigns to each document is a unique number made up of a prefix and a number.
-The prefix combines the journal code and the entry date and is used to group entries by period. The
-number is unique for each period and is used to identify the entry. The default sequence on customer
-invoices is INV/YYYY/number. In some specific cases,
-:ref:`resequencing <accounting/invoice/resequencing>` invoices might be necessary.
-
-.. _accounting/invoice/resequencing:
-
-Resequencing
------------
-
-Resequencing is not possible:
-
- When entries are before a lock date.
- When the sequence leads to a duplicate.
- When the :guilabel:`Invoice Date` doesn't match the date contained in the new sequence number,
-  e.g., if the sequence is changed to INV/2023/XXXXX for a document with an :guilabel:`Invoice Date`
-  of 2024.
-
-To change the invoice sequence with the structure INV/YYYY/MM/number, add `/MM` with the number of
-the month of the :guilabel:`Invoice date`. Odoo will recognize the "/" term as a month and update
-the future invoice sequence appropriately with the month of the :guilabel:`Invoice date`. For
-example, if the invoice date is January, change the sequence to `INV/2024/01/XXXXX`.
-
-In this case, if the :guilabel:`Invoice date` isn't aligned with the sequence number, a
-:guilabel:`Validation Error` message appears.
-
-.. note::
-
-   - All sequence changes are logged in the chatter to keep the information.
-   - Sequence changes also affect the format of future invoices' sequences.
-
-.. _accounting/invoice/resequencing-one-invoice:
-
-Resequencing a single invoice
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To resequence the last confirmed invoice, click :guilabel:`Reset to Draft`, then change the
-sequence. The invoice now appears in red on the :guilabel:`Customer Invoices` list.
-
-.. _accounting/invoice/mass-resequencing:
-
-Mass-resequencing invoices
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-It can be helpful to resequence multiple invoice numbers. For example, when importing invoices from
-another invoicing or accounting system and the reference originates from the previous software,
-continuity for the current year must be maintained without restarting from the beginning.
-
-.. note::
-   This feature is only available to users with administrator or advisor access.
-
-Follow these steps to resequence invoice numbers:
-
-#. Activate the :ref:`developer mode <developer-mode>`.
-#. From the :guilabel:`Accounting Dashboard`, open the :guilabel:`Customer Invoices` journal.
-#. Select the invoices that need a new sequence.
-#. Click the :icon:`fa-cog` :guilabel:`Actions` menu and select :guilabel:`Resequence`.
-#. In the :guilabel:`Ordering` field, choose to
-
-   - :guilabel:`Keep current order`: The order of the numbers remains the same.
-   - :guilabel:`Reorder by accounting date`: The number is reordered by accounting date.
-#. Set the :guilabel:`First New Sequence`.
-#. :guilabel:`Preview Modifications` and click :guilabel:`Confirm`.
-
-The first invoice using the new sequence appears in red in the :guilabel:`Customer Invoices` list.
-
-.. image:: customer_invoices/invoice-sequencing.png
-   :alt: Resequence options window
-
 .. _accounting/invoice/reporting:

 Reporting
@@ -221,18 +194,18 @@ go to :menuselection:`Accounting --> Reporting --> Partner Ledger`.
 Aged Receivable
 ~~~~~~~~~~~~~~~

-To review outstanding customer invoices and their related due dates, use the
-:ref:`Aged Receivable <accounting/reporting/aged-receivable>` report. To access it, go to
-:menuselection:`Accounting --> Reporting --> Aged Receivable`.
+To review outstanding customer invoices and their related due dates, use the :ref:`Aged Receivable
+<accounting/reporting/aged-receivable>` report. To access it, go to :menuselection:`Accounting -->
+Reporting --> Aged Receivable`.

 .. _accounting/invoices/aged-payable:

 Aged Payable
 ~~~~~~~~~~~~

-To review outstanding vendor bills and their related due dates, use the
-:ref:`Aged Payable <accounting/reporting/aged-payable>` report. To access it, go to
-:menuselection:`Accounting --> Reporting --> Aged Payable`.
+To review outstanding vendor bills and their related due dates, use the :ref:`Aged Payable
+<accounting/reporting/aged-payable>` report. To access it, go to :menuselection:`Accounting -->
+Reporting --> Aged Payable`.

 .. _accounting/invoices/profit-and-loss:

@@ -262,6 +235,7 @@ liabilities, and equity at a specific time.
   customer_invoices/cash_rounding
   customer_invoices/deferred_revenues
   customer_invoices/electronic_invoicing
+   customer_invoices/sequence
   customer_invoices/snailmail
   customer_invoices/epc_qr_code
   customer_invoices/incoterms
@@ -15,10 +15,15 @@ one of the application of EDI.

 Odoo supports e-invoicing in many countries. Refer to the country's page for more details:

+- :doc:`Argentina <electronic_invoicing/argentina>`
 - :doc:`Austria <electronic_invoicing/austria>`
 - :doc:`Belgium <electronic_invoicing/belgium>`
+- :doc:`Brazil <electronic_invoicing/brazil>`
+- :doc:`Chile <electronic_invoicing/chile>`
+- :doc:`Colombia <electronic_invoicing/colombia>`
 - :doc:`Croatia <electronic_invoicing/croatia>`
 - :doc:`Denmark <electronic_invoicing/denmark>`
+- :doc:`Ecuador <electronic_invoicing/ecuador>`
 - :doc:`Estonia <electronic_invoicing/estonia>`
 - :doc:`Finland <electronic_invoicing/finland>`
 - :doc:`France <electronic_invoicing/france>`
@@ -29,14 +34,17 @@ Odoo supports e-invoicing in many countries. Refer to the country's page for mor
 - :doc:`Latvia <electronic_invoicing/latvia>`
 - :doc:`Lithuania <electronic_invoicing/lithuania>`
 - :doc:`Luxembourg <electronic_invoicing/luxembourg>`
+- :doc:`Mexico <electronic_invoicing/mexico>`
 - :doc:`Netherlands <electronic_invoicing/netherlands>`
 - :doc:`Norway <electronic_invoicing/norway>`
+- :doc:`Peru <electronic_invoicing/peru>`
 - :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>`
+- :doc:`Uruguay <electronic_invoicing/uruguay>`

 .. seealso::
   :doc:`Fiscal localizations documentation <../../fiscal_localizations>`
@@ -0,0 +1,54 @@
+:orphan:
+
+======================================
+Odoo electronic invoicing in Argentina
+======================================
+
+Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
+solutions tailored to meet Argentina's regulatory standards and compatible with the requirements set
+forth by the `Administración Federal de Ingresos Públicos (AFIP) <https://www.afip.gob.ar/>`_.
+
+Legal framework for e-invoicing in Argentina
+============================================
+
+In Argentina, e-invoicing is regulated by the :abbr:`AFIP (Administración Federal de Ingresos
+Públicos)` and is mandatory for most businesses to ensure tax compliance and transparency. The
+primary regulations governing e-invoicing include:
+
+- `General Resolution No. 4290/2018 <https://biblioteca.afip.gob.ar/search/query/norma.aspx?p=t:RAG|n:4290|o:3|a:2018|f:02/08/2018>`_
+  which establishes the mandatory use of electronic invoices for specific economic activities and
+  turnover thresholds.
+- Fiscal code regulations: Requires electronic invoices for all VAT-registered businesses, including
+  B2B, :abbr:`B2G (business-to-government)`, and B2C transactions.
+- Implementation of :abbr:`CAE (Código de Autorización Electrónico)`: Every electronic invoice must
+  include a :abbr:`CAE (Código de Autorización Electrónico)` issued by the :abbr:`AFIP
+  (Administración Federal de Ingresos Públicos)`, ensuring its validity and authenticity.
+
+Compliance with Argentinian e-invoicing regulations
+===================================================
+
+Odoo Invoicing simplifies the process of adhering to Argentina's e-invoicing regulations, offering
+features designed to ensure compliance:
+
+- **Supported formats**: Odoo supports Argentina's authorized e-invoice formats, including :abbr:`FE
+  (Factura Electrónica)` with :abbr:`AFIP (Administración Federal de Ingresos Públicos)`-compliant
+  digital validation, XML with :abbr:`CAE (Código de Autorización Electrónico)` authorization for
+  real-time integration with :abbr:`AFIP (Administración Federal de Ingresos Públicos)`, and
+  digitally signed PDF invoices featuring :abbr:`CAE (Código de Autorización Electrónico)` and
+  QR codes for secure validation.
+- **Secure storage and retrieval**: Complying with Argentina’s ten-year storage requirement, Odoo
+  provides tamper-proof archiving and easy retrieval for audits or tax inspections.
+- **Automatic VAT calculation and reporting**: Odoo ensures compliance with Argentina's VAT
+  regulations by automatically calculating VAT, incorporating it into invoices, and adhering to
+  legal reporting requirements for accurate tax submissions.
+
+.. seealso::
+   :doc:`Argentinian fiscal localization documentation <../../../fiscal_localizations/argentina>`
+
+.. admonition:: Disclaimer
+
+   This page provides a general overview of Argentine e-invoicing laws and how Odoo’s invoicing
+   module supports compliance with AFIP regulations and the Fiscal Code. It is not intended as legal
+   advice. We recommend consulting with a tax advisor or legal professional familiar with
+   Argentinian e-invoicing regulations to ensure compliance tailored to your specific business
+   needs.
@@ -0,0 +1,53 @@
+:orphan:
+
+===================================
+Odoo electronic invoicing in Brazil
+===================================
+
+Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
+solutions tailored to meet Brazil's regulatory standards and compatible with the requirements set
+forth by the `Secretaria da Fazenda (SEFAZ) <https://www.gov.br/receitafederal/pt-br>`_.
+
+Legal framework for e-invoicing in Brazil
+=========================================
+
+In Brazil, e-invoicing is highly regulated and mandatory for most businesses to ensure tax
+compliance and transparency. The key regulations governing e-invoicing include:
+
+- :abbr:`NF-e (Nota Fiscal Eletrônica)`: A mandatory e-invoice for goods and services used in B2B
+  and :abbr:`B2G (business-to-government)` transactions.
+- :abbr:`CT-e (Conhecimento de Transporte Eletrônico)`: Specific to freight and logistics services.
+- :abbr:`NFS-e (Nota Fiscal de Serviços Eletrônica)`: Issued for service-based transactions, with
+  implementation varying by municipality.
+- Integration with :abbr:`SEFAZ (Secretaria da Fazenda)`: Every electronic invoice must be
+  authorized by :abbr:`SEFAZ (Secretaria da Fazenda)` and issued with a unique authorization code
+  (Autorização de Uso).
+
+Compliance with Brazilian e-invoicing regulations
+=================================================
+
+Odoo Invoicing simplifies the process of adhering to Brazil’s complex e-invoicing regulations,
+offering features designed to ensure compliance:
+
+- **Supported formats**: Odoo supports Brazil's authorized e-invoice formats, including :abbr:`NF-e
+  (Nota Fiscal Eletrônica)` for goods and services compliant with :abbr:`SEFAZ (Secretaria da
+  Fazenda)`, :abbr:`NFS-e (Nota Fiscal de Serviços Eletrônica)` customizable for municipal
+  requirements, :abbr:`CT-e (Conhecimento de Transporte Eletrônico)` for logistics and
+  transportation, and digital PDF invoices with :abbr:`SEFAZ (Secretaria da Fazenda)` authorization
+  codes and QR codes.
+- **Secure storage and retrieval**: Complying with Brazil's five-year storage requirement, Odoo
+  offers tamper-proof archiving for easy retrieval during audits or inspections.
+- **Automatic tax calculation and reporting**: Odoo automates tax calculations for ICMS, IPI, and
+  ISS, ensuring compliance with regional tax rules and generating reports compatible with
+  :abbr:`SEFAZ (Secretaria da Fazenda)` and municipal requirements.
+
+.. seealso::
+   :doc:`Brazilian fiscal localization documentation <../../../fiscal_localizations/brazil>`
+
+.. admonition:: Disclaimer
+
+   This page provides a general overview of Brazilian e-invoicing laws and how Odoo’s invoicing
+   module supports compliance with :abbr:`SEFAZ (Secretaria da Fazenda)` regulations. It is not
+   intended as legal advice. We recommend consulting with a tax advisor or legal professional
+   familiar with Brazilian e-invoicing regulations to ensure compliance tailored to your specific
+   business needs.
@@ -0,0 +1,51 @@
+:orphan:
+
+==================================
+Odoo electronic invoicing in Chile
+==================================
+
+Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
+solutions tailored to meet Chile's regulatory requirements and compatible with standards set by the
+`Servicio de Impuestos Internos (SII) <https://homer.sii.cl/>`_.
+
+Legal framework for e-invoicing in Chile
+========================================
+
+Chile is a pioneer in mandatory electronic invoicing, with comprehensive regulations to ensure tax
+compliance and enhance transparency. Key elements include:
+
+-  **Factura Electrónica**: Mandatory for most businesses to issue invoices digitally through the
+   :abbr:`SII (Servicio de Impuestos Internos)`'s system.
+-  **Boleta Electrónica**: Required for retail transactions to report sales and tax information.
+-  **Guía de Despacho Electrónica**: Necessary for tracking the transport of goods.
+-  **Integration with SII**: All electronic invoices must be validated by the :abbr:`SII (Servicio
+   de Impuestos Internos)`, assigned a unique Folio authorization code, and reported for tax
+   purposes.
+
+Compliance with Chilean e-invoicing regulations
+===============================================
+
+Odoo Invoicing simplifies adherence to Chile's e-invoicing requirements with features designed to
+ensure compliance:
+
+-  **Supported formats**: Odoo supports all major Chilean e-invoice formats, including Factura
+   Electrónica, Boleta Electrónica, and Guía de Despacho Electrónica, ensuring :abbr:`SII (Servicio
+   de Impuestos Internos)` compatibility with digital validation and Folio assignment.
+-  **Integration with SII**: Odoo seamlessly connects with :abbr:`SII (Servicio de Impuestos
+   Internos)`'s systems, automating invoice submission and ensuring real-time validation for
+   compliant issuance.
+-  **Secure storage and retrieval**: Complying with Chile's mandatory storage period of six years,
+   Odoo provides tamper-proof archiving for invoices, enabling easy access for audits or tax
+   inspections.
+-  **Automatic tax calculation and reporting**: Odoo automates calculations for VAT (IVA) and other
+   applicable taxes, ensuring accurate invoicing and adherence to Chile's tax reporting standards.
+
+.. seealso::
+   :doc:`Chilean fiscal localization documentation <../../../fiscal_localizations/chile>`
+
+.. admonition:: Disclaimer
+
+   This page provides a general overview of Chilean e-invoicing laws and how Odoo supports
+   compliance with :abbr:`SII (Servicio de Impuestos Internos)` regulations. It is not intended as
+   legal or tax advice. We recommend consulting a tax advisor or legal professional familiar with
+   Chilean e-invoicing regulations to ensure compliance tailored to your specific business needs.
@@ -0,0 +1,51 @@
+:orphan:
+
+=====================================
+Odoo electronic invoicing in Colombia
+=====================================
+
+Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
+solutions tailored to meet Colombia's regulatory requirements and fully compatible with the
+guidelines established by the `Dirección de Impuestos y Aduanas Nacionales (DIAN)
+<https://www.dian.gov.co/>`_.
+
+Legal framework for e-invoicing in Colombia
+===========================================
+
+Colombia has implemented mandatory e-invoicing for most businesses to enhance tax compliance and
+improve transparency. Key elements include:
+
+-  **Factura Electrónica**: Mandatory for B2B, B2C, and :abbr:`B2G (business-to-government)`
+   transactions, requiring compliance with :abbr:`DIAN (Dirección de Impuestos y Aduanas
+   Nacionales)`'s technical specifications.
+-  **Integration with DIAN**: All electronic invoices must be submitted to :abbr:`DIAN (Dirección de
+   Impuestos y Aduanas Nacionales)` for validation, where they are assigned a unique :abbr:`CUFE
+   (Código Único de Factura Electrónica)` authorization code.
+-  **Adoption of XML Standards**: Colombian e-invoicing uses XML as the standard format for
+   electronic invoices, ensuring interoperability and standardized reporting.
+
+Compliance with Colombian e-invoicing regulations
+=================================================
+
+Odoo Invoicing simplifies the complexities of e-invoicing compliance in Colombia, offering tailored
+features:
+
+- **Supported formats**: Odoo supports Factura Electrónica in :abbr:`DIAN (Dirección de Impuestos y
+  Aduanas Nacionales)`-compliant XML formats, including legally required :abbr:`CUFE (Código Único
+  de Factura Electrónica)` codes and additional fields for B2B, B2C, and :abbr:`B2G
+  (business-to-government)` transactions.
+- **Secure storage and retrieval**: In compliance with Colombia's six-year mandatory storage
+  requirement, Odoo provides tamper-proof invoice archiving, ensuring easy access for audits or
+  inspections.
+- **Automatic tax calculation and reporting**: Odoo automates tax calculations for VAT (IVA) and
+  other applicable taxes, ensuring accuracy and compliance with DIAN's tax reporting standards.
+
+.. seealso::
+   :doc:`Colombian fiscal localization documentation <../../../fiscal_localizations/colombia>`
+
+.. admonition:: Disclaimer
+
+   This page provides a general overview of Colombian e-invoicing regulations and how Odoo supports
+   compliance with DIAN requirements. It is not intended as legal or tax advice. We recommend
+   consulting with a tax advisor or legal professional familiar with Colombian e-invoicing
+   regulations to ensure compliance tailored to your specific business needs.
@@ -0,0 +1,50 @@
+:orphan:
+
+====================================
+Odoo electronic invoicing in Ecuador
+====================================
+
+Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
+solutions tailored to meet Ecuador's regulatory requirements and fully compatible with the
+guidelines established by the `Servicio de Rentas Internas (SRI)
+<https://www.sri.gob.ec/web/intersri/home>`_.
+
+Legal framework for e-invoicing in Ecuador
+==========================================
+
+Ecuador has implemented mandatory electronic invoicing for most businesses aimed to enhance tax
+compliance and transparency. Key elements include:
+
+- **Factura Electrónica**: All businesses must issue electronic invoices in XML format for B2B, B2C,
+  and :abbr:`B2G (business-to-government)` transactions, ensuring compliance with :abbr:`SRI
+  (Servicio de Rentas Internas)`'s technical specifications.
+- **Transmission Requirements**: E-invoices must be transmitted to the SRI within 24 hours of
+  issuance.
+- **Record Storage**: E-invoices, including the :abbr:`SRI (Servicio de Rentas Internas)`'s
+  acceptance messages, must be stored for a minimum of seven years.
+
+Compliance with Ecuadorian e-invoicing regulations
+==================================================
+
+Odoo Invoicing simplifies compliance with Ecuador's e-invoicing requirements by offering tailored
+features:
+
+- **Supported formats**: Odoo supports the Ecuadorian e-invoice format (XML) and ensures
+  compatibility with the :abbr:`SRI (Servicio de Rentas Internas)`'s system for validation and
+  authorization, including the necessary digital signature.
+- **Secure storage and retrieval**: In compliance with Ecuador's seven-year storage requirement,
+  Odoo offers tamper-proof archiving so that invoices can be easily accessed during audits or
+  inspections.
+- **Automatic tax calculation and reporting**: Odoo automates tax calculations for VAT (IVA) and
+  other applicable taxes, ensuring accurate invoicing and adherence to Ecuador's tax reporting
+  standards.
+
+.. seealso::
+   :doc:`Ecuadorian fiscal localization documentation <../../../fiscal_localizations/ecuador>`
+
+.. admonition:: Disclaimer
+
+  This page provides a general overview of Ecuadorian e-invoicing regulations and how Odoo supports
+  compliance with SRI requirements. It is not intended as legal or tax advice. We recommend
+  consulting with a tax advisor or legal professional familiar with Ecuador's e-invoicing
+  regulations to ensure compliance tailored to your specific business needs.
@@ -0,0 +1,57 @@
+:orphan:
+
+===================================
+Odoo electronic invoicing in Mexico
+===================================
+
+Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
+solutions tailored to meet Mexico's regulatory requirements and fully compatible with the guidelines
+established by the :abbr:`SAT (Servicio de Administración Tributaria)`.
+
+Legal framework for e-invoicing in Mexico
+=========================================
+
+Mexico has one of the most advanced e-invoicing systems globally, with electronic invoicing
+:abbr:`CFDI (Comprobante Fiscal Digital por Internet)` being mandatory for most taxpayers. Key
+elements include:
+
+-  **CFDI**: A mandatory electronic invoice format for B2B, B2C, and :abbr:`B2G
+   (business-to-government)` transactions, fully compliant with SAT requirements.
+-  **Digital tax receipt validation**: All :abbr:`CFDIs (Comprobante Fiscal Digital por Internet)`
+   must be digitally signed and validated by :abbr:`SAT (Servicio de Administración
+   Tributaria)`-authorized :abbr:`PACs (authorized certification providers)` before issuance.
+-  **Complementos**: Specific complements are required for certain transaction types, such as
+   payroll or foreign trade.
+-  **XML Format**: The XML format is mandatory, ensuring interoperability and compliance with
+   :abbr:`SAT (Servicio de Administración Tributaria)`'s technical standards.
+
+Compliance with Mexican e-invoicing regulations
+===============================================
+
+Odoo Invoicing simplifies compliance with Mexico’s e-invoicing requirements by offering tailored
+features:
+
+-  **Supported formats**: Odoo supports :abbr:`CFDI (Comprobante Fiscal Digital por Internet)` in
+   :abbr:`SAT (Servicio de Administración Tributaria)`-compliant XML formats, including all
+   mandatory fields, digital signatures, and complements for specialized transactions.
+-  **Integration with PACs**: Odoo integrates with :abbr:`SAT (Servicio de Administración
+   Tributaria)`-authorized :abbr:`PACs (authorized certification providers)` to automate the
+   validation, certification, and issuance of :abbr:`CFDIs (Comprobante Fiscal Digital por
+   Internet)`, ensuring real-time compliance.
+-  **Secure storage and retrieval**: In compliance with Mexico's five-year mandatory storage
+   requirement, Odoo provides tamper-proof archiving for easy access to invoices during audits
+   or inspections.
+-  **Automatic tax calculation and reporting**: Odoo automates tax calculations for VAT (IVA) and
+   other applicable taxes, ensuring accuracy and compliance with :abbr:`SAT (Servicio de
+   Administración Tributaria)`'s tax reporting standards.
+
+.. seealso::
+   :doc:`Mexican fiscal localization documentation <../../../fiscal_localizations/mexico>`
+
+.. admonition:: Disclaimer
+
+   This page provides a general overview of Mexican e-invoicing regulations and how Odoo supports
+   compliance with :abbr:`SAT (Servicio de Administración Tributaria)` requirements. It is not
+   intended as legal or tax advice. We recommend consulting with a tax advisor or legal professional
+   familiar with Mexico's e-invoicing regulations to ensure compliance tailored to your specific
+   business needs.
@@ -0,0 +1,55 @@
+:orphan:
+
+=================================
+Odoo electronic invoicing in Peru
+=================================
+
+Odoo Invoicing provides secure, efficient, and legally compliant e-invoicing solutions tailored to
+meet Peru’s regulatory requirements and fully compatible with the guidelines established by the
+`Superintendencia Nacional de Aduanas y de Administración Tributaria (SUNAT)
+<https://www.sunat.gob.pe/>`_.
+
+Legal framework for e-invoicing in Peru
+=======================================
+
+Peru has mandated electronic invoicing for most taxpayers to enhance tax compliance, reduce fraud,
+and improve transparency. Key elements include:
+
+- **Comprobante de Pago Electrónico (CPE)**: A mandatory electronic document required for B2B, B2C,
+  and :abbr:`B2G (business-to-government)` transactions, fully compliant with :abbr:`SUNAT
+  (Superintendencia Nacional de Aduanas y de Administración Tributaria)`'s technical specifications.
+- **Integration with SUNAT**: E-invoices must be submitted to :abbr:`SUNAT (Superintendencia
+  Nacional de Aduanas y de Administración Tributaria)` for validation and authorization. Upon
+  approval, :abbr:`SUNAT (Superintendencia Nacional de Aduanas y de Administración Tributaria)`
+  assigns a unique identification code to the invoice.
+- **XML Format**: All electronic invoices must be issued in XML format, ensuring standardization and
+  interoperability.
+- **Mandatory adoption timeline**: Electronic invoicing is mandatory for most businesses, with
+  specific deadlines for smaller entities.
+
+Compliance with Peruvian e-invoicing regulations
+================================================
+
+Odoo Invoicing simplifies compliance with Peru’s e-invoicing requirements by offering tailored
+features:
+
+- **Supported formats**: Odoo supports the Peruvian :abbr:`CPE (Comprobante de Pago Electrónico` in
+  :abbr:`SUNAT (Superintendencia Nacional de Aduanas y de Administración Tributaria)`-compliant XML
+  formats, including all required fields and authorization codes.
+- **Secure storage and retrieval**: In compliance with Peru's five-year mandatory storage
+  requirement, Odoo offers tamper-proof archiving, ensuring easy access for audits or inspections.
+- **Automatic tax calculation and reporting**: Odoo automates tax calculations for :abbr:`IGV
+  (Impuesto General a las Ventas) and other applicable taxes, ensuring accuracy and compliance
+  with :abbr:`SUNAT (Superintendencia Nacional de Aduanas y de Administración Tributaria)`'s
+  reporting standards.
+
+.. seealso::
+   :doc:`Peruvian fiscal localization documentation <../../../fiscal_localizations/peru>`
+
+.. admonition:: Disclaimer
+
+   This page provides a general overview of Peruvian e-invoicing regulations and how Odoo supports
+   compliance with :abbr:`SUNAT (Superintendencia Nacional de Aduanas y de Administración
+   Tributaria)` requirements. It is not intended as legal or tax advice. We recommend consulting
+   with a tax advisor or legal professional familiar with Peru's e-invoicing regulations to ensure
+   compliance tailored to your specific business needs.
@@ -0,0 +1,57 @@
+:orphan:
+
+====================================
+Odoo electronic invoicing in Uruguay
+====================================
+
+Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
+solutions tailored to meet Uruguay's regulatory requirements and fully compatible with the
+guidelines established by the `Dirección General Impositiva (DGI)
+<https://www.gub.uy/direccion-general-impositiva/>`_.
+
+Legal framework for e-invoicing in Uruguay
+==========================================
+
+Uruguay has mandated electronic invoicing under the :abbr:`CFE (Comprobante Fiscal Electrónico)`
+system, which applies to most businesses to promote tax transparency and streamline financial
+transactions. Key elements include:
+
+- **Comprobante Fiscal Electrónico**: A mandatory e-invoice format required for B2B, B2C, and
+  :abbr:`B2G (business-to-government)` transactions, fully compliant with :abbr:`DGI (Dirección
+  General Impositiva)`'s technical standards.
+- **Integration with DGI**: All :abbr:`CFE (Comprobante Fiscal Electrónico)` must be submitted to
+  the :abbr:`DGI (Dirección General Impositiva)` for validation. Upon approval, the :abbr:`CFE
+  (Comprobante Fiscal Electrónico)` receives a unique identification code and authorization for
+  issuance.
+- **XML Format**: Uruguay mandates the use of XML as the standard format for e-invoices, ensuring
+  compatibility and interoperability with various systems.
+- **Adoption Timeline**: E-invoicing is mandatory for most businesses, with specific deadlines for
+  smaller enterprises to transition into the system.
+
+Compliance with Uruguayan e-invoicing regulations
+=================================================
+
+Odoo Invoicing simplifies the complexities of compliance with Uruguay's e-invoicing requirements by
+offering tailored features:
+
+- **Supported formats**: Odoo supports the :abbr:`CFE (Comprobante Fiscal Electrónico)` format in
+  :abbr:`DGI (Dirección General Impositiva)`-compliant XML, including all legally required fields,
+  such as the unique identification code, authorization number, and digital signature. Odoo allows
+  the automated submission, validation, and issuance through the :abbr:`DGI (Dirección General
+  Impositiva)`'s e-invoicing platform to ensure compliance in real time.
+- **Secure storage and retrieval**: In line with Uruguay’s mandatory five-year storage requirement,
+  Odoo provides tamper-proof archiving solutions, ensuring easy access to invoices for audits or
+  inspections.
+- **Automatic tax calculation and reporting**: Odoo automates tax calculations for IVA (Value-Added
+  Tax) and other applicable taxes, ensuring accuracy and compliance with :abbr:`DGI (Dirección
+  General Impositiva)`'s reporting standards.
+
+.. seealso::
+   :doc:`Uruguayan fiscal localization documentation <../../../fiscal_localizations/uruguay>`
+
+.. admonition:: Disclaimer
+
+   This page provides a general overview of Uruguayan e-invoicing regulations and how Odoo supports
+   compliance with DGI requirements. It is not intended as legal or tax advice. We recommend
+   consulting with a tax advisor or legal professional familiar with Uruguay's e-invoicing
+   regulations to ensure full compliance tailored to your specific business requirements.
@@ -0,0 +1,66 @@
+================
+Invoice sequence
+================
+
+When confirming an invoice, Odoo generates a unique invoice reference number. By default, Odoo uses
+the following sequence format `INV/year/incrementing-number` (e.g., `INV/2025/00001`), which
+restarts from `00001` each year.
+
+However, it is possible to :ref:`change the sequence format <accounting/invoice/resequencing>` and
+its periodicity, and to :ref:`mass-resequence invoices <accounting/invoice/mass-resequencing>`.
+
+.. note::
+   Changes made to reference numbers are logged in the chatter.
+
+.. _accounting/invoice/resequencing:
+
+Changing the default sequence
+=============================
+
+To customize the default sequence, open the last confirmed invoice, click :guilabel:`Reset to
+Draft`, and edit the invoice's reference number.
+
+.. image:: sequence/reference-number.png
+   :alt: Editing the reference number of an invoice.
+
+Odoo then explains how the detected format will be applied to all future invoices. For example, if
+the current invoice's month is added, the sequence's periodicity will change to every month instead
+of every year.
+
+.. image:: sequence/sequence-dialog.png
+   :alt: Editing the reference number of an invoice.
+
+.. tip::
+   The sequence format can be edited directly when creating the first invoice of a given sequence
+   period.
+
+.. _accounting/invoice/mass-resequencing:
+
+Mass-resequencing invoices
+==========================
+
+It can be helpful to resequence multiple invoice numbers. For example, when importing invoices from
+another invoicing or accounting system and the reference originates from the previous software,
+continuity for the current year must be maintained without restarting from the beginning.
+
+.. note::
+   This feature is only available to users with administrator or advisor access.
+
+Follow these steps to resequence invoice numbers:
+
+#. Activate the :ref:`developer mode <developer-mode>`.
+#. From the :guilabel:`Accounting Dashboard`, open the :guilabel:`Customer Invoices` journal.
+#. Select the invoices that need a new sequence.
+#. Click the :icon:`fa-cog` :guilabel:`Actions` menu and select :guilabel:`Resequence`.
+#. In the :guilabel:`Ordering` field, choose to
+
+   - :guilabel:`Keep current order`: The order of the numbers remains the same.
+   - :guilabel:`Reorder by accounting date`: The number is reordered by accounting date.
+
+#. Set the :guilabel:`First New Sequence`.
+#. :guilabel:`Preview Modifications` and click :guilabel:`Confirm`.
+
+The first invoice using the new sequence appears in red in the :guilabel:`Customer Invoices` list.
+
+.. image:: sequence/invoice-sequencing.png
+   :alt: Resequence options window
@@ -15,44 +15,115 @@ 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>`_

+.. _accounting/payments/payment-methods:
+
+Payment methods
+===============
+
+Several payment methods are available in Odoo to allow different configurations for different types
+of payments. Examples of payment methods include manual payments (such as cash), :doc:`checks
+<payments/pay_checks>`, and batch payment files (such as :ref:`NACHA
+<l10n_us/ach-electronic-transfers>` and :doc:`SEPA <payments/pay_sepa>`). Payment methods can be
+configured in the :guilabel:`Incoming Payments` and :guilabel:`Outgoing Payments` tabs of a bank or
+cash journal.
+
+.. seealso::
+   :doc:`../../sales/point_of_sale/payment_methods` for Point of Sale
+
+.. _accounting/payments/preferred-payment-methods:
+
+Preferred payment method
+------------------------
+
+A contact's preferred payment method can be set so that when a payment is created for that contact,
+the payment method is automatically selected by default. Invoices and bills can be filtered by
+:guilabel:`Payment Method` to simplify :ref:`group <accounting/payments/group-payments>` payments.
+
+To set a preferred :guilabel:`Payment Method` for a customer or a vendor, go to
+:menuselection:`Accounting --> Customers --> Customers` or :menuselection:`Accounting --> Vendors
+--> Vendors` and select the customer or vendor. In the :guilabel:`Sales & Purchase` tab of the
+contact form, select the preferred :guilabel:`Payment Method` in the :guilabel:`Sales` section for
+invoice payments or for vendor bill payments in the :guilabel:`Purchase` section.
+
+.. tip::
+   Access a full list of all contacts from the :guilabel:`Customers` or :guilabel:`Vendors` list
+   view by removing the :guilabel:`Customers` or :guilabel:`Vendors` filter. Alternatively, access
+   the full contact list through the Contacts app.
+
 .. _accounting/payments/from-invoice-bill:

 Registering payment from an invoice or bill
 ===========================================

-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 <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 register a payment for an invoice or a bill, follow these steps:

-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`.
+#. Click :guilabel:`Pay` on a customer invoice or vendor bill. In the :guilabel:`Pay` window, select
+   the :guilabel:`Journal` and the :guilabel:`Payment Date`.
+#. If previously set, the contact's preferred :guilabel:`Payment Method` is automatically selected
+   by default but can be updated if necessary.
+#. If using :doc:`payment terms <customer_invoices/payment_terms>`, the :guilabel:`Amount` is
+   automatically set based on the installment amounts defined by the payment term. To pay the full
+   amount instead, click :guilabel:`full amount`.
+#. If necessary, edit the :guilabel:`Memo`.
+#. Click :guilabel:`Create Payment`.

-.. image:: payments/information-icon.png
-   :alt: See detailed information of a payment.
+After the payment is registered, the customer invoice or vendor bill is marked as
+:guilabel:`In payment`.

-.. note::
-   - The customer invoice or vendor bill must be in the :guilabel:`Posted` status to register the
-     payment.
-   - If a payment is unreconciled, it still appears in the books but is no longer linked to the
-     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 and an invoice with cash-basis taxes, a journal entry is
-     automatically created to post the cash-basis tax (reversal) amount.
+.. tabs::

-.. tip::
-   If the main bank account is set as an :ref:`outstanding account
-   <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`.
+   .. group-tab:: Without outstanding accounts
+
+      If no :ref:`outstanding accounts <accounting/bank/outstanding-accounts>` are configured, no
+      journal entry is created. To display more information about the payment, click the
+      :guilabel:`Payments` smart button.
+
+      When the invoice or vendor bill is :doc:`reconciled <bank/reconciliation>` with a bank
+      transaction, its status is updated to :guilabel:`Paid`.
+
+      .. note::
+         - If a bank transaction is reconciled in a different currency, a journal entry is
+           automatically created to post the currency exchange gains/loss amount.
+         - When a bank transaction is reconciled with an invoice with cash-basis, a journal entry is
+           automatically created to post the cash-basis tax amount.
+
+   .. group-tab:: Using outstanding accounts
+
+      By default, payments in Odoo do not create journal entries, but they can easily be configured
+      to create journal entries using :ref:`outstanding accounts
+      <accounting/bank/outstanding-accounts>`.
+
+      Registering a payment on a customer invoice or vendor bill generates a new journal entry and
+      reduces the :guilabel:`Amount Due` based on 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 payment is :doc:`reconciled <bank/reconciliation>` with
+      a bank transaction, the invoice or vendor bill status changes to :guilabel:`Paid`.
+
+      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.
+
+      .. note::
+         - Unreconciling a payment unlinks it from the invoice or bill but does not delete the
+           payment.
+         - 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
+           automatically created to post the cash-basis tax (reversal) amount.
+
+      .. tip::
+         If the main bank account is set as the outstanding account 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.

 .. _accounting/payments/not-tied:

@@ -60,71 +131,185 @@ 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.
+directly linked to an invoice or bill.
+
+.. tabs::
+
+   .. group-tab:: Without outstanding accounts
+
+      Payments that are not linked to an invoice or bill should not be registered without using
+      :ref:`outstanding accounts <accounting/bank/outstanding-accounts>`, as there is no way to
+      associate the payment with the invoice or bill since no journal entry is created for the
+      payment. The amount paid or received is not reflected in the accounting and the
+      :guilabel:`Amount Due` is not updated based on the payment amount.
+
+   .. group-tab:: Using outstanding accounts
+
+      Instead, the payment's journal entry matches the :guilabel:`outstanding account` with the
+      account receivable or the account payable until the payment 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.

 .. _accounting/payments/matching-invoices-bills:

-Matching invoices and bills with payments
-----------------------------------------
+For a single invoice or bill
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-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`
-under :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`.
+.. tabs::

-.. image:: payments/add-option.png
-   :alt: Shows the ADD option to reconcile an invoice or a bill with a payment.
+   .. group-tab:: Without outstanding accounts

-The invoice or bill is now marked as :guilabel:`In payment` until it is reconciled with its
-corresponding bank transaction.
+      By default, payments in Odoo do not create journal entries. As a result, there is no payment
+      to match.
+
+   .. group-tab:: Using outstanding accounts
+
+      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` 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.
+
+      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:
+
+For multiple invoices or bills
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. tabs::
+
+   .. group-tab:: Without outstanding accounts
+
+      By default, payments in Odoo do not create journal entries. As a result, there is no payment
+      to match, but this feature can still be used to match miscellaneous journal items.
+
+   .. group-tab:: Using outstanding accounts
+
+      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:`ellipsis`) 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`.
+
+.. _accounting/payments/auto-reconcile-feature:
+
+Auto-Reconcile Feature
+**********************
+
+.. tabs::
+
+   .. group-tab:: Without outstanding accounts
+
+      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 group of journal items
+         in that account).
+      #. In the :guilabel:`Reconcile automatically` window, click :guilabel:`Reconcile`.
+
+   .. group-tab:: Using outstanding accounts
+
+      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 group of journal items
+         in that account).
+      #. In the :guilabel:`Reconcile Automatically` window, set the
+         :guilabel:`Reconcile` field depending on how you want to match journal items:
+
+         - :guilabel:`Perfect Match`: Each debit journal item will be matched with
+           the corresponding credit journal item of the same value.
+         - :guilabel:`Clear Accounts`: All reconciled journal items will have the same
+           matching number, as they are selected from the same account.
+
+      #. Click :guilabel:`Reconcile`.
+
+      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>`.

 .. _accounting/payments/group-payments:

-Group payments
--------------
+Registering payments on multiple invoices/credit notes or bills/refunds (group payments)
+========================================================================================

-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:
+To register payments on multiple invoices/credit notes or bills/refunds, follow these steps:

 #. Go to :menuselection:`Accounting --> Customers --> Invoices/Credit Notes` or
   :menuselection:`Accounting --> Vendors --> Bills/Refunds`.
-#. 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`.
-#. Enable the :guilabel:`Group Payments` option and click :guilabel:`Create payment`.
+#. In the list view, click into the search bar, group by :guilabel:`Payment Method`, select the
+   relevant invoices/credit notes or bills/refunds and click :guilabel:`Pay`.
+#. In the :guilabel:`Pay` window, select the :guilabel:`Journal` and the :guilabel:`Payment Date`.
+#. If previously set, the contact's preferred :guilabel:`Payment Method` is automatically selected
+   by default but can be updated if necessary.
+#. If using :doc:`payment terms <customer_invoices/payment_terms>`, the :guilabel:`Amount` is
+   automatically set based on the installment amounts defined by the payment term. To pay the full
+   amount instead, click :guilabel:`full amount`.
+#. 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`.

-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`.
+.. tabs::
+
+   .. group-tab:: Without outstanding accounts
+
+      The invoices or bills are then marked as :guilabel:`In payment` until they are
+      :doc:`reconciled <bank/reconciliation>` with the bank transactions.
+
+   .. group-tab:: Using outstanding accounts
+
+      The invoices or bills are then marked as :guilabel:`In payment` until the bank transactions
+      are :doc:`reconciled <bank/reconciliation>` with the payments.

 .. _accounting/payments/batch-payments:

-Batch payments
--------------
+Registering a single payment for multiple customers or vendors (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 :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`.
+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`.
+
+.. note::
+   All payments in a batch must have the same :ref:`payment method
+   <accounting/payments/payment-methods>`.

 .. seealso::
-  - :doc:`payments/batch`
-  - :doc:`payments/batch_sdd`
+   - :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`.
+The :guilabel:`Payments matching` tool opens all unreconciled journal items and allows them to be
+processed individually, matching all payments and journal items. Go to the
+:guilabel:`Accounting Dashboard`, go to :menuselection:`Accounting --> Accounting --> Reconcile` or
+click the :icon:`fa-ellipsis-v` (:guilabel:`ellipsis`) button from the :guilabel:`Customer
+Invoices` or :guilabel:`Vendor Bills` journals, and select :guilabel:`Payments Matching`.

 .. image:: payments/payments-journal.png
   :alt: Payments matching menu in the drop-down menu.
@@ -134,47 +319,56 @@ Reconciliation`.
   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
 =============================

-To register a partial payment, click on :guilabel:`Register Payment` from the related invoice or
-bill. In the case of a partial payment (when the :guilabel:`Amount` paid is less than the total
-remaining amount on the invoice or the bill), the :guilabel:`Payment Difference` field displays the
-outstanding balance. There are two options:
+To register a partial payment, click on :guilabel:`Pay` from the related invoice or bill.

- :guilabel:`Keep open`: Keep the invoice or the bill open and mark it with a :guilabel:`Partial`
-  banner;
- :guilabel:`Mark as fully paid`: Select an account in the :guilabel:`Post Difference In` field and
-  change the :guilabel:`Label` if needed. A journal entry will be created to balance the accounts
-  payable or receivable with the selected account.
+.. tabs::

-.. image:: payments/partial-payment.png
-   :alt: register a partial payment
+   .. group-tab:: Without outstanding accounts
+
+      In the case of a partial payment (when the :guilabel:`Amount` paid is less than the total
+      remaining amount on the invoice or the bill), fill in the :guilabel:`Amount` in the
+      :guilabel:`Pay` window.
+
+   .. group-tab:: Using outstanding accounts
+
+      In the case of a partial payment (when the :guilabel:`Amount` paid is less than the total
+      remaining amount on the invoice or the bill), the :guilabel:`Payment Difference` field
+      displays the outstanding balance. There are two options:
+
+      - :guilabel:`Keep open`: Keep the invoice or the bill open and mark it with a
+        :guilabel:`Partial` banner;
+      - :guilabel:`Mark as fully paid`: Select an account in the :guilabel:`Post Difference In`
+        field and change the :guilabel:`Label` if needed. A journal entry will be created to balance
+        the accounts payable or receivable with the selected account.
+
+      .. image:: payments/partial-payment.png
+         :alt: register a partial payment

 .. _accounting/payments/reconciling-payments:

 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>` it with the related bank transaction line to
-finalize the payment workflow and mark the invoice or bill as :guilabel:`Paid`.
+.. tabs::
+
+   .. group-tab:: Without outstanding accounts
+
+      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 related :doc:`bank
+      transaction <bank/transactions>` line with the invoice or bill to finalize the payment
+      workflow and mark the invoice or bill as :guilabel:`Paid`.
+
+   .. group-tab:: Using outstanding accounts
+
+      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`.

 .. toctree::
   :titlesonly:
@@ -184,7 +378,6 @@ finalize the payment workflow and mark the invoice or bill as :guilabel:`Paid`.
   payments/batch
   payments/batch_sdd
   payments/follow_up
-   payments/internal_transfers
   payments/pay_sepa
   payments/pay_checks
   payments/forecast
@@ -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:
@@ -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`
@@ -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
 ----------------------------

@@ -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.
@@ -173,7 +173,8 @@ expression's **label** (ex. **code.label**).
 `CUR` is the currency code in capital letters, and `amount` is the amount of the bound expressed in
 that currency.

-You can also use the `cross_report` subformula to match an expression found in another report.
+`cross_report(xml_id | report_id)`
+   Used to match an expression from another report targeted by the xml_id or the report ID itself.

 'Prefix of Account Codes' engine
 --------------------------------
@@ -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,40 +68,41 @@ 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
-your :guilabel:`Tax Report` by going to :menuselection:`Accounting --> Reporting -->
-Audit Reports: Tax Report`. Make sure to select the right period you want to declare by using the
-date filter, this way you can have an overview of your tax report. From this view, you can easily
-access different formats of your tax report, such as `PDF` and XLSX. These include all the values to
-report to the tax authorities, along with the amount you have to pay or be refunded.
+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`.

-.. image:: tax_returns/tax_return_report.png
-   :align: center
-   :alt: download the PDF with your Tax Report in Odoo Accounting
+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.

 .. note::
   If you forgot to lock your tax date before clicking on :guilabel:`Closing Journal Entry`, then
@@ -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, run :ref:`payments matching <accounting/payments/matching>` to validate any open
+  - Optionally, :ref:`match payments <accounting/payments/auto-reconcile-tool>` 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.
@@ -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/matching>` when you receive the products.
+  the :ref:`matching <accounting/payments/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.
@@ -91,9 +91,10 @@ To buy credits, go to :menuselection:`Accounting --> Configuration --> Settings
 and click on :guilabel:`Buy credits`, or go to :menuselection:`Settings --> Odoo IAP` and click on
 :guilabel:`View My Services`.

-.. important::
-   If you are on Odoo Online and have the Enterprise version, you benefit from free trial credits to
-   test the feature.
+.. note::
+   Enterprise Odoo users with a valid subscription get free credits to test IAP features before
+   deciding to purchase more credits for the database. This includes demo/training databases,
+   educational databases, and one-app-free databases.

 .. seealso::
   - `Our Privacy Policy <https://iap.odoo.com/privacy#header_6>`_
@@ -187,17 +187,17 @@ Fiscal localization modules are available for the countries listed below.
   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
@@ -11,7 +11,10 @@ Below you can find videos with a general description of the localization, and ho
 - `eCommerce - Localización de Argentina <https://www.youtube.com/watch?v=5gUi2WWfRuI>`_.

 .. seealso::
-   `Smart Tutorial - Localización de Argentina <https://www.odoo.com/slides/smart-tutorial-localizacion-de-argentina-130>`_
+   - `Smart Tutorial - Localización de Argentina
+     <https://www.odoo.com/slides/smart-tutorial-localizacion-de-argentina-130>`_
+   - :doc:`Documentation on e-invoicing's legality and compliance in Argentina
+     <../accounting/customer_invoices/electronic_invoicing/argentina>`

 Configuration
 =============
@@ -45,6 +48,9 @@ localization:
     - `l10n_ar_website_sale`
     - (optional) Allows the user to see Identification Type and AFIP Responsibility in the
       eCommerce checkout form in order to create electronic invoices.
+   * - :ref:`Argentina - Payment Withholdings <l10n_ar/payment-withholdings>`
+     - `l10n_ar_withholding`
+     - Allows registering withholdings during the payment of an invoice.

 .. _argentina/configure-your-company:

@@ -678,6 +684,147 @@ the invoice can then be validated.
   :align: center
   :alt: Enter the perception amount.

+.. _l10n_ar/payment-withholdings:
+
+Withholding management
+----------------------
+
+The Argentinean fiscal localization module is already loaded with the necessary withholdings
+records, which can be seen by navigating to :menuselection:`Accounting app --> Configuration -->
+Taxes` and removing the default :guilabel:`Sale or Purchase` filter. To verify these records, the
+**Argentina Payment Withholdings** (`l10n_ar_withholding`) module must be :ref:`installed
+<general/install>`:
+
+Journal entries are *not* created when payments are posted unless :ref:`outstanding accounts
+<accounting/bank/outstanding-accounts>` are set up. Thus, for this feature to work properly, it is
+important to verify that *all* payment methods within the bank journals have an outstanding payment
+and receipt account set.
+
+.. image:: argentina/l10n-ar-outstanding-payments.png
+   :alt: An outstanding payment account must be set.
+
+This configuration is crucial for the proper accounting of withholding transactions with clients
+and vendors.
+
+.. note::
+   In Argentina, withholdings represent the cancellation of a specific portion of the total debt
+   owed to a supplier or a reduction in the total payment to be collected from a customer.
+   Therefore, one or multiple withholdings can be recorded for each payment applied to an invoice.
+
+Configuration
+~~~~~~~~~~~~~
+
+While Odoo already creates most of the required withholdings inside the :guilabel:`Taxes`
+menu, in several cases, it is necessary to apply or modify certain configurations to correctly
+calculate the withholding amount on vendor payments. The following withholding types are available:
+
+- :ref:`Earnings <l10n_ar/earnings-withholdings>`
+- :ref:`Earnings Scale <l10n_ar/earnings-scale-withholdings>`
+- :ref:`IIBB Total Amount <l10n_ar/iib-total-amount-withholdings>`
+- :ref:`IIBB Non-Taxable <l10n_ar/iib-nontax-withholdings>`
+
+.. _l10n_ar/earnings-withholdings:
+
+Earnings
+********
+
+For :guilabel:`Earnings` withholdings, Odoo already has a record for each regime group, which is
+stated under the name of the tax and the AFIP code.
+
+Each of these records are ready to be used. As a good practice, the configuration should be double
+checked to make sure the configuration is updated and well-applied. The fields to validate are:
+
+- :guilabel:`Amount`: This is the percentage of the total payment amount which is withheld.
+- :guilabel:`Non-Taxable Amount`: Up to this amount, the withholding does not apply.
+- :guilabel:`Minimum Withholding`: If the calculated withholding amount is smaller than this value,
+  the total withholding amount is set to `0.0`.
+- :guilabel:`Withholding Sequence`: This field helps to automate the capture of a withholding number
+  under the payment line. If this field is not set, a number is manually captured while adding a
+  withholding to a payment.
+
+.. image:: argentina/l10n-ar-earnings.png
+   :alt: Earnings withholding type.
+
+.. _l10n_ar/earnings-scale-withholdings:
+
+Earnings Scale
+**************
+
+In this particular case, a percentage does not need to be set. Instead, this withholding is
+calculated based on the value of the :guilabel:`Scale` field.
+
+To view, modify, or create new scales, navigate to :menuselection:`Accounting app --> Configuration
+--> Earnings Scale`. By default, the Argentinian localization is preconfigured with two main scales.
+However, scales should be created and updated as necessary to suit a business's needs.
+
+.. note::
+   Earnings scales are cumulative, which means that Odoo keeps track of the different records
+   created for a bill and automatically calculates the proper withholding amount.
+
+.. _l10n_ar/iib-total-amount-withholdings:
+
+IIBB Total Amount
+*****************
+
+In this case, the necessary records related to the applicable province need to be created. The
+withholding amount is calculated based on the percentage :guilabel:`Amount` set on the tax
+configuration. Since Odoo does not automatically synchronize the percentages applicable to each
+province, this information needs to be manually updated.
+
+The recommendation, in this case, is to always duplicate and apply the different configurations for
+each record to safeguard any technical configurations that allow the proper calculation and
+accounting of the withholding.
+
+.. _l10n_ar/iib-nontax-withholdings:
+
+IIBB Untaxed
+************
+
+The configuration of non-taxable gross income withholdings is very similar to that of a :ref:`total
+amount withholding <l10n_ar/iib-total-amount-withholdings>`, so the percentage :guilabel:`Amount` in
+each of the records needs to be maintained. However, Odoo comes preconfigured with several records
+that apply to different provinces. The difference, in this case, is that it is not necessary to
+establish a non-taxable amount or minimum withholding for this record type.
+
+Partner withholding assignation
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Once the proper configuration is set on each possible withholding for partners, the applicable
+withholdings need to be assigned to each contact. To do this, open the :guilabel:`Contacts` app and
+select the desired partner. In the :guilabel:`Accounting` tab, find the :guilabel:`Purchase
+Withholdings` table.
+
+By using the additional fields :guilabel:`From Date` and :guilabel:`To Date`, the applicability of
+multiple withholdings can be automated across different date ranges. The :guilabel:`ref` field
+allows you to apply an internal control number to each withholding line, which is just for internal
+reference, so it does not affect any transactions and is not visible on them. These fields are
+accessible from the :icon:`oi-settings-adjust` :guilabel:`(adjust settings)` menu.
+
+- :guilabel:`From Date`: the start of the withholding date range.
+- :guilabel:`To Date`: the end of the withholding date range.
+- :guilabel:`ref`: apply an internal control number to each withholding line that is only visible
+  for internal reference and does not affect any transactions.
+
+Automatic withholding calculation and application per payment
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+By applying new payments to vendor bills, Odoo automatically applies and calculates the proper
+withholding into the payment. Based on the record's configuration, it may be necessary to use a
+reference number for each withholding line.
+
+More withholdings can be added, or computed withholdings can be edited if necessary.
+
+.. image:: argentina/l10n-ar-payment.png
+   :alt: Payment with applied withholdings.
+
+.. important::
+   The total amount of the debt to be canceled is the total amount of the payment. However, Odoo
+   still captures the net amount (i.e. the amount to be reconciled with the bank), which will be
+   represented as the payment amount after the withholding application.
+
+   .. image:: argentina/l10n-ar-payment-registered.png
+      :alt: Payment registered form.
+
 Check management
 ----------------

--- a/Show More
+++ b/Show More