odoo-forge-bundle 0.1.0

package/payload/skills/odoo18-docs/references/docs/contributing/documentation.md

@@ -0,0 +1,300 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/contributing/documentation.html"
+---
+
+:show-content:
+# 
+# Documentation
+
+.. toctree::
+   :titlesonly:
+
+   documentation/content_guidelines
+   documentation/rst_guidelines
+
+This introductory guide will help you acquire the tools and knowledge needed to contribute to the
+documentation.
+
+Read the :ref:`introduction to the reStructuredText language <contributing/documentation/rst-intro>`
+if you are not familiar with it. Then, there are two courses of action to start contributing to the
+documentation:
+
+- **For minor changes**, such as adding a paragraph or fixing a typo, we recommend **using the
+  GitHub interface**. This is the easiest and fastest way to submit changes, and it is suitable for
+  non-technical people. Jump directly to the :ref:`contributing/documentation/first-contribution`
+  section to get started.
+- **For more complex changes**, such as adding a new page, it is necessary to **use Git** and work
+  from a local copy of the documentation. Follow the instructions in the
+  :ref:`contributing/documentation/setup` section first to prepare your environment.
+
+.. seealso::
+   :doc:`Discover other ways to contribute to Odoo <../contributing>`
+
+.. _contributing/documentation/rst-intro:
+
+# reStructuredText (RST)
+
+The documentation is written in **reStructuredText** (RST), a [lightweight markup language
+](https://en.wikipedia.org/wiki/Lightweight_markup_language) consisting of regular text augmented
+with markup, which allows including headings, images, notes, and so on. :abbr:`RST
+(reStructuredText)` is easy to use, even if you are not familiar with it.
+
+> **important**:
+>    Be mindful of our :doc:`content <documentation/content_guidelines>` and
+   :doc:`RST <documentation/rst_guidelines>` guidelines as you write documentation. This ensures
+   that the documentation stays consistent and facilitates the approval of changes by the Odoo team.
+
+.. _contributing/documentation/setup:
+
+# Environment setup
+
+The instructions below help you prepare your environment for making local changes to the
+documentation and then push them to GitHub. Skip this section and go to
+:ref:`contributing/documentation/first-contribution` if you have already completed this step or want
+to make changes from the GitHub interface.
+
+#. First, [create a GitHub account ](https://github.com/join). Odoo uses GitHub to manage the
+   source code of its products, and this is where you will submit your changes.
+#. [Generate a new SSH key and register it on your GitHub account
+   ](https://docs.github.com/en/authentication/connecting-to-github-with-ssh).
+#. Go to [github.com/odoo/documentation ](https://github.com/odoo/documentation) and click on the
+   :guilabel:`Fork` button in the top right corner to create a fork (:dfn:`your own copy`) of the
+   repository on your account. This creates a copy of the codebase to which you can make changes
+   without affecting the main codebase. Skip this step if you work at Odoo.
+#. .. include:: install_git.rst
+#. Configure Git to identify yourself as the author of your future contributions. Enter the same
+   email address you used to register on GitHub.
+
+   ```console
+
+      $ git config --global user.name "Your Name"
+      $ git config --global user.email "youremail@example.com"
+
+#. Clone the sources with Git and navigate into the local repository.
+
+   ```console
+
+      $ git clone git@github.com:odoo/documentation.git
+      $ cd documentation
+
+#. Configure Git to push changes to your fork rather than to the main codebase. In the commands
+   below, replace `<your_github_account>` with the name of the GitHub account on which you created
+   the fork. Skip this step if you work at Odoo.
+
+   ```console
+
+      $ git remote add dev git@github.com:<your_github_account>/documentation.git
+
+#. Configure Git to ease the collaboration between writers coming from different systems.
+
+   .. tabs::
+
+      .. group-tab:: Linux and macOS
+
+         ```console
+
+            $ git config --global core.autocrlf input
+            $ git config commit.template `pwd`/commit_template.txt
+
+      .. group-tab:: Windows
+
+         ```console
+
+            $ git config --global core.autocrlf true
+            $ git config commit.template %CD%\commit_template.txt
+
+#. Install the latest release of [Python ](https://wiki.python.org/moin/BeginnersGuide/Download)
+   and [pip ](https://pip.pypa.io/en/stable/installation/).
+#. Install the Python dependencies of the documentation with pip.
+
+   ```console
+
+      $ pip install -r requirements.txt
+
+   Verify that the installation directory of the Python dependencies is included in your system's
+   `PATH` variable.
+
+   .. tabs::
+
+      .. group-tab:: Linux and macOS
+
+         Follow the [guide to update the PATH variable on Linux and macOS
+         ](https://unix.stackexchange.com/a/26059) with the installation path of the Python
+         dependencies (by default :file:`~/.local/bin`).
+
+      .. group-tab:: Windows
+
+         Follow the [guide to update the PATH variable on Windows
+         ](https://www.howtogeek.com/118594/how-to-edit-your-system-path-for-easy-command-line-access/)
+         with the installation path of the Python dependencies.
+
+#. Install Make.
+
+   .. tabs::
+
+      .. group-tab:: Linux
+
+         ```console
+
+            $ sudo apt install make -y
+
+      .. group-tab:: macOS
+
+         Follow the [guide to install Make on macOS ](https://formulae.brew.sh/formula/make)
+
+      .. group-tab:: Windows
+
+         Follow the [guide to install Make on Windows
+         ](https://www.technewstoday.com/install-and-use-make-in-windows).
+
+#. [Install pngquant ](https://pngquant.org/).
+#. You are now ready to :ref:`make your first contribution
+   <contributing/documentation/first-contribution>` with Git.
+
+.. _contributing/documentation/first-contribution:
+
+# Contributing to the documentation
+
+.. tabs::
+
+   .. tab:: Contribute from the GitHub interface
+
+      #. First, [create a GitHub account ](https://github.com/join). Odoo uses GitHub to manage the
+         source code of its products, and this is where you will submit your changes.
+      #. Verify that you are browsing the documentation in the version that you intend to change.
+         The version can be selected from the dropdown in the top menu.
+      #. Head to the page that you want to change and click on the :guilabel:`Edit on GitHub` button
+         in the top right corner of the page.
+      #. Click on the :guilabel:`Fork this repository` button to create a fork (:dfn:`your own
+         copy`) of the repository on your account. This creates a copy of the codebase to which you
+         can make changes without affecting the main codebase. Skip this step if you work at Odoo.
+
+         .. image:: documentation/fork-repository.png
+            :scale: 60%
+
+      #. Make the desired changes while taking care of following the :doc:`content
+         <documentation/content_guidelines>` and :doc:`RST <documentation/rst_guidelines>`
+         guidelines.
+
+         > **tip**:
+>             Click on the :guilabel:`Preview changes` button to review your contribution in a more
+            human-readable format. Be aware that the preview is not able to handle all markups
+            correctly. Notes and tips, for instance, are shown as plain text.
+
+      #. Scroll to the bottom of the page and fill out the small form to propose your changes. In
+         the first text box, write a very short summary of your changes. For instance, "Fix a typo"
+         or "Add documentation for invoicing of sales orders." In the second text box, explain *why*
+         you are proposing these changes. Then, click on the :guilabel:`Propose changes` button.
+
+         .. image:: documentation/propose-changes.png
+            :scale: 60%
+
+      #. Review your changes and click on the :guilabel:`Create pull request` button.
+      #. Tick the :guilabel:`Allow edits from maintainer` checkbox. Skip this step if you work at
+         Odoo.
+      #. Review the summary that you wrote about your changes and click on the :guilabel:`Create
+         pull request` button again.
+      #. At the bottom of the page, check the mergeability status and address any issues.
+      #. As soon as your :abbr:`PR (Pull Request)` is ready for merging, a member of the Odoo team
+         is automatically assigned for review. If the reviewer has questions or remarks, they will
+         post them as comments and you will be notified by email. Those comments must be resolved
+         for the contribution to go forward.
+
+      #. Once your changes are approved, the reviewer merges them and they appear online the next
+         day.
+
+   .. tab:: Contribute with Git
+
+      > **important**:
+>          Some steps of this guide require to be comfortable with Git. Here are some [tutorials
+         ](https://www.atlassian.com/git/tutorials) and an [interactive training
+         ](https://learngitbranching.js.org/) if you are stuck at some point.
+
+      Now that your environment is set up, you can start contributing to the documentation. In a
+      terminal, navigate to the directory where you cloned the sources and follow the guide below.
+
+      #. Choose the version of the documentation to which you want to make changes. Keep in mind
+         that contributions targeting an :doc:`unsupported version of Odoo
+         </administration/supported_versions>` are not accepted. This guide assumes that the changes
+         target the documentation of Odoo {CURRENT_VERSION}, which corresponds to branch
+         `{CURRENT_BRANCH}`.
+      #. Create a new branch starting from branch {CURRENT_BRANCH}. Prefix the branch name with the
+         base branch: `{CURRENT_BRANCH}-...`. If you work at Odoo, suffix the branch name with your
+         Odoo handle: `{CURRENT_BRANCH}-...-xyz`.
+
+         .. example::
+
+            ```console
+
+               $ git switch -c {CURRENT_BRANCH}-explain-pricelists
+
+            ```console
+
+               $ git switch -c {CURRENT_BRANCH}-explain-pricelists-xyz
+
+      #. Make the desired changes while taking care of following the :doc:`content
+         <documentation/content_guidelines>` and :doc:`RST <documentation/rst_guidelines>`
+         guidelines.
+      #. Compress all PNG images that were added or modified.
+
+         ```console
+
+            $ pngquant path/to/image.png
+            $ mv path/to/image-fs8.png path/to/image.png
+
+      #. Write a [redirect rule
+         ](https://github.com/odoo/documentation/tree/{BRANCH}/redirects/MANUAL.md) for every RST
+         file that were renamed.
+      #. Build the documentation with :command:`make`. Then, open :file:`_build/index.html` in a web
+         browser to browse the documentation with your changes.
+
+         > **tip**:
+>             Use :command:`make help` to learn about other useful commands.
+
+      #. Commit your changes. Write a clear commit message as instructed in the :doc:`Git guidelines
+         <development/git_guidelines>`.
+
+         ```console
+
+            $ git add .
+            $ git commit
+
+      #. Push your changes to your fork, for which we added the remote alias `dev`.
+
+         .. example::
+
+            ```console
+
+               $ git push -u dev {CURRENT_BRANCH}-explain-pricelists
+
+         If you work at Odoo, push your changes directly to the main codebase whose remote alias is
+         `origin`.
+
+         .. example::
+
+            ```console
+
+               $ git push -u origin {CURRENT_BRANCH}-explain-pricelists-xyz
+
+      #. Open a :abbr:`PR (Pull Request)` on GitHub to submit your changes for review.
+
+         #. Go to the [compare page of the odoo/documentation codebase
+            ](https://github.com/odoo/documentation/compare).
+         #. Select **{CURRENT_BRANCH}** for the base.
+         #. Click on :guilabel:`compare across forks`.
+         #. Select **<your_github_account>/odoo** for the head repository. Replace
+            `<your_github_account>` with the name of the GitHub account on which you created the
+            fork. Skip this step if you work at Odoo.
+         #. Review your changes and click on the :guilabel:`Create pull request` button.
+         #. Tick the :guilabel:`Allow edits from maintainer` checkbox. Skip this step if you work at
+            Odoo.
+         #. Complete the description and click on the :guilabel:`Create pull request` button again.
+
+      #. At the bottom of the page, check the mergeability status and address any issues.
+      #. As soon as your :abbr:`PR (Pull Request)` is ready for merging, a member of the Odoo team
+         is automatically assigned for review. If the reviewer has questions or remarks, they will
+         post them as comments and you will be notified by email. Those comments must be resolved
+         for the contribution to go forward.
+      #. Once your changes are approved, the reviewer merges them and they appear online the next
+         day.

package/payload/skills/odoo18-docs/references/docs/contributing/install_git.md

@@ -0,0 +1,25 @@
+---
+title: "`Install Git <https://git-scm.com/book/en/v2/Getting-Started-Installing-Git>`_. It is a command-line"
+source_url: "https://docs.odoo.sbggai.top/contributing/install_git.html"
+---
+
+[Install Git ](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git). It is a command-line
+(:dfn:`a text interface`) tool that allows tracking the history of changes made to a file and, more
+importantly, working on different versions of that file simultaneously. It means you do not need to
+worry about overwriting someone else’s pending work when making changes.
+
+Verify that the installation directory of Git is included in your system's `PATH` variable.
+
+.. tabs::
+
+   .. group-tab:: Linux and macOS
+
+      Follow the [guide to update the PATH variable on Linux and macOS
+      ](https://unix.stackexchange.com/a/26059) with the installation path of Git (by default
+      :file:`/usr/bin/git`).
+
+   .. group-tab:: Windows
+
+      Follow the [guide to update the PATH variable on Windows
+      ](https://www.howtogeek.com/118594/how-to-edit-your-system-path-for-easy-command-line-access/)
+      with the installation path of Git (by default :file:`C:\\Program Files\\Git`).

package/payload/skills/odoo18-docs/references/docs/developer/glossary.md

@@ -0,0 +1,46 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/developer/glossary.html"
+---
+
+:orphan: true
+# 
+# Glossary
+
+.. glossary::
+
+    external id
+    external identifier
+    external identifiers
+        string identifier stored in `ir.model.data`, can be used to refer
+        to a record regardless of its database identifier during data imports
+        or export/import roundtrips.
+
+        External identifiers are in the form :samp:`{module}.{id}` (e.g.
+        `account.invoice_graph`). From within a module, the
+        :samp:`{module}.` prefix can be left out.
+
+        Sometimes referred to as "xml id" or `xml_id` as XML-based
+        :ref:`reference/data` make extensive use of them.
+
+    format string
+        inspired by `jinja variables`_, format strings allow more easily
+        mixing literal content and computed content (expressions): content
+        between `{{` and `}}` is interpreted as an expression and
+        evaluated, other content is interpreted as literal strings and
+        displayed as-is
+
+    GIS
+    Geographic Information System
+        any computer system or subsystem to capture, store, manipulate,
+        analyze, manage or present spatial and geographical data.
+
+    minified
+    minification
+        process of removing extraneous/non-necessary sections of files
+        (comments, whitespace) and possibly recompiling them using equivalent
+        but shorter structures (`ternary operator`_ instead of `if/else`) in
+        order to reduce network traffic
+
+.. _jinja variables: http://jinja.pocoo.org/docs/dev/templates/#variables
+.. _ternary operator: http://en.wikipedia.org/wiki/%3F:

package/payload/skills/odoo18-docs/references/docs/developer/howtos/accounting_localization.md

@@ -0,0 +1,305 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/developer/howtos/accounting_localization.html"
+---
+
+# 
+# Accounting localization
+
+> **warning**:
+>     This tutorial requires knowledge about how to build a module in Odoo (see
+    :doc:`../tutorials/server_framework_101`).
+
+
+# Installation procedure
+
+On installing the [account ]({GITHUB_PATH}/addons/account) module, the localization module corresponding to the country code of the company is installed automatically.
+In case of no country code set or no localization module found, the [l10n_generic_coa ]({GITHUB_PATH}/addons/l10n_generic_coa) (US) localization module is installed by default.
+Check [post init hook ]({GITHUB_PATH}/addons/account/__init__.py) for details.
+
+For example, [l10n_ch ]({GITHUB_PATH}/addons/l10n_ch) will be installed if the company has `Switzerland` as country.
+
+# Building a localization module
+
+The structure of a basic `l10n_XX` module may be described with the following :file:`__manifest__.py` file:
+
+```python
+
+    {
+        "name": "COUNTRY - Accounting",
+        "version": "1.0.0",
+        "category": "Accounting/Localizations/Account Charts",
+        "license": "LGPL-3",
+        "depends": [
+            "account",
+        ],
+        "data": [
+            "data/other_data.xml",
+            "views/xxxmodel_views.xml",
+        ],
+        "demo": [
+            "demo/demo_company.xml",
+        ]
+    }
+
+Your worktree should look like this
+
+```bash
+
+  l10n_xx
+  ├── data
+  │   ├── template
+  │   │   ├── account.account-xx.csv
+  │   │   ├── account.group-xx.csv
+  │   │   └── account.tax.group-xx.csv
+  │   └── other_data.xml
+  ├── views
+  │   └── xxxmodel_views.xml
+  ├── demo
+  │   └── demo_company.xml
+  ├── models
+  │   ├── template_xx.py
+  │   └── __init__.py
+  ├── __init__.py
+  └── __manifest__.py
+
+
+In the first file :file:`models/template_xx.py`, we set the name for the chart of accounts along with some basic fields.
+
+.. seealso::
+   :doc:`Chart Template References </developer/reference/standard_modules/account>`
+
+.. example::
+  [addons/l10n_be/models/template_be.py ]({GITHUB_PATH}/addons/l10n_be/models/template_be.py)
+
+  .. literalinclude:: {ODOO_RELPATH}/addons/l10n_be/models/template_be.py
+    :condition: odoo_dir_in_path
+    :language: python
+    :start-at: _get_be_template_data
+    :end-before: _get_be_reconcile_model
+
+
+# Chart of Accounts
+
+## Account tags
+
+.. seealso::
+   :ref:`Account Tag References <reference/account_account_tag>`
+
+Tags are a way to sort accounts.
+For example, imagine you want to create a financial report having multiple lines but you have no way to find a rule to dispatch the accounts according to their `code`.
+The solution is the usage of tags, one for each report line, to filter accounts like you want.
+
+Put the tags in the :file:`data/account_account_tag_data.xml` file.
+
+.. example::
+  [addons/l10n_lt/data/template/account.account-lt.csv ]({GITHUB_PATH}/addons/l10n_lt/data/template/account.account-lt.csv)
+
+  .. literalinclude:: {ODOO_RELPATH}/addons/l10n_lt/data/template/account.account-lt.csv
+    :condition: odoo_dir_in_path
+    :language: csv
+    :end-at: account_account_template_1201
+
+## Accounts
+
+.. seealso::
+   - :ref:`Account References <reference/account_account>`
+   - :doc:`/applications/finance/accounting/get_started/chart_of_accounts`
+
+Obviously, :guilabel:`Chart of Accounts` cannot exist without :guilabel:`Accounts`. You need to specify them in :file:`data/account.account.template.csv`.
+
+.. example::
+  [addons/l10n_ch/data/template/account.account-ch.csv ]({GITHUB_PATH}/addons/l10n_ch/data/template/account.account-ch.csv)
+
+  .. literalinclude:: {ODOO_RELPATH}/addons/l10n_ch/data/template/account.account-ch.csv
+    :condition: odoo_dir_in_path
+    :language: csv
+    :end-at: ch_coa_1171
+
+> **warning**:
+>     - Avoid the usage of `asset_cash` `account_type`!
+      Indeed, the bank & cash accounts are created directly at the installation of the localization module and then, are linked to an `account.journal`.
+    - Only one account of type payable/receivable is enough for the generic case.  We need to define a PoS receivable account as well however. (linked in the CoA)
+    - Don't create too many accounts: 200-300 is enough. But mostly, we try to find a good balance where the CoA needs minimal adapting for most companies afterwards.
+
+
+## Account groups
+
+.. seealso::
+   :ref:`Account Group References <reference/account_group>`
+
+Account groups allow describing the hierarchical structure of the chart of accounts. The filter needs to be activated in the report and then when you decollapse into journal entries it will show the parents of the account.
+
+It works with the prefix *start*/*end*, so every account where the code starts with something between *start* and *end* will have this `account.group` as the parent group.  Furthermore, the account groups can have a parent account group as well to form the hierarchy.
+
+
+.. example::
+  [addons/l10n_il/data/template/account.group-il.csv ]({GITHUB_PATH}/addons/l10n_il/data/template/account.group-il.csv)
+
+  .. csv-table::
+     :condition: odoo_dir_in_path
+     :file: {ODOO_RELPATH}/addons/l10n_il/data/template/account.group-il.csv
+     :widths: 20,20,20,20,20
+     :header-rows: 1
+
+## Taxes
+
+.. seealso::
+   - :ref:`Tax References <reference/account_tax>`
+   - :doc:`/applications/finance/accounting/taxes/`
+
+To add taxes you first need to specify tax groups. You normally need just one tax group for every tax rate, except for the 0% as you need to often distinguish between exempt, 0%, not subject, ... taxes.
+This model only has two required fields: `name` and `country`. Create the file :file:`data/template/account.tax.group-xx.csv` and list the groups.
+
+.. example::
+  [addons/l10n_uk/data/template/account.tax.group-uk.csv ]({GITHUB_PATH}/addons/l10n_uk/data/template/account.tax.group-uk.csv)
+
+  .. literalinclude:: {ODOO_RELPATH}/addons/l10n_uk/data/template/account.tax.group-uk.csv
+    :condition: odoo_dir_in_path
+    :language: csv
+
+
+Now you can add the taxes via :file:`data/template/account.tax-xx.csv` file.  The first tax you define that is purchase/sale also becomes the default purchase/sale tax for your products.
+
+
+.. example::
+  [addons/l10n_ae/data/template/account.tax-ae.csv ]({GITHUB_PATH}/addons/l10n_ae/data/template/account.tax-ae.csv)
+
+  .. literalinclude:: {ODOO_RELPATH}/addons/l10n_ae/data/template/account.tax-ae.csv
+    :condition: odoo_dir_in_path
+    :language: xml
+    :end-at: uae_sale_tax_5_ras_al_khaima
+
+
+## Tax Report
+
+.. raw:: html
+
+   <div><span class="badge" style="background-color:#AD5E99">Enterprise feature</span><div>
+
+The tax report is declared in the :guilabel:`Invoicing` (`account`) app, but the report is only accessible when :guilabel:`Accounting` (`account_accountant`) is installed.
+
+.. seealso::
+   - :doc:`/developer/reference/standard_modules/account/account_report_line`
+   - :doc:`/applications/finance/accounting/reporting/tax_returns`
+
+In the previous section, you noticed the fields `invoice_repartition_line_ids` or `refund_repartition_line_ids` and probably understood nothing about them. Good news: you are not alone on this incomprehension. Bad news: you have to figure it out a bit. The topic is complicated. Indeed:
+
+.. graphviz:: accounting_localization/tax_report.dot
+    :class: overflow-auto
+
+The simple version is that, in the tax template, you indicate in the invoice/refund repartition lines whether the base or a percentage of the tax needs to be reported in which report line (through the *minus/plus_report_line_ids* fields).
+It becomes clear also when you check the tax configuration in the Odoo interface (or check the docs :ref:`Tax References <reference/account_tax>`, :ref:`Tax Repartition References <reference/account_tax_repartition>`).
+
+So, once you have properly configured taxes, you just need to add the :file:`data/account_tax_report_data.xml` file with a record for your `account.report`. For it to be considered as a tax report, you need to provide it with the right `root_report_id`.
+
+```xml
+
+    <odoo>
+        <record id="tax_report" model="account.report">
+            <field name="name">Tax Report</field>
+            <field name="root_report_id" ref="account.generic_tax_report"/>
+            <field name="country_id" ref="base.XX"/>
+        </record>
+
+        ...
+    </odoo>
+
+... followed by the declaration of its lines, as `account.report.line` records.
+
+.. example::
+  [addons/l10n_au/data/account_tax_report_data.xml ]({GITHUB_PATH}/addons/l10n_au/data/account_tax_report_data.xml)
+
+  .. literalinclude:: {ODOO_RELPATH}/addons/l10n_au/data/account_tax_report_data.xml
+    :condition: odoo_dir_in_path
+    :language: xml
+    :start-at: tax_report
+    :end-before: account_tax_report_gstrpt_g3
+
+
+
+## Fiscal positions
+
+.. seealso::
+   - :ref:`Fiscal Position References <reference/account_fiscal_position>`
+   - :doc:`/applications/finance/accounting/taxes/fiscal_positions`
+
+Specify fiscal positions in the :file:`data/template/account.fiscal.position-xx.csv` file.
+
+.. example::
+  [addons/l10n_es/data/template/account.fiscal.position-es_common_mainland.csv ]({GITHUB_PATH}/addons/l10n_es/data/template/account.fiscal.position-es_common_mainland.csv)
+
+  .. literalinclude:: {ODOO_RELPATH}/addons/l10n_es/data/template/account.fiscal.position-es_common_mainland.csv
+    :condition: odoo_dir_in_path
+    :language: csv
+    :end-at: account_tax_template_p_iva10_sp_ex
+
+# Final steps
+
+Finally, you may add a demo company, so the localization can easily be tested in demo mode.
+
+.. example::
+  [addons/l10n_ch/demo/demo_company.xml ]({GITHUB_PATH}/addons/l10n_ch/demo/demo_company.xml)
+
+  .. literalinclude:: {ODOO_RELPATH}/addons/l10n_ch/demo/demo_company.xml
+    :condition: odoo_dir_in_path
+    :language: xml
+    :start-after: <odoo>
+    :end-before: </odoo>
+
+# Accounting reports
+
+.. raw:: html
+
+   <div><span class="badge" style="background-color:#AD5E99">Enterprise feature</span><div>
+
+.. seealso::
+  :doc:`/applications/finance/accounting/reporting`
+
+Accounting reports should be added via a separate module `l10n_XX_reports` that should go to the [enterprise repository ]({GITHUB_ENT_PATH}).
+
+Basic :file:`__manifest__.py` file for such a module looks as following:
+
+
+```python
+
+    {
+        "name": "COUNTRY - Accounting Reports",
+        "category": "Accounting/Localizations/Reporting",
+        "version": "1.0.0",
+        "license": "OEEL-1",
+        "depends": [
+            "l10n_XX", "account_reports"
+        ],
+        "data": [
+            "data/balance_sheet.xml",
+            "data/profit_and_loss.xml",
+        ],
+        "auto_install": True,
+    }
+
+
+Functional overview of financial reports is here: :doc:`/applications/finance/accounting/reporting`.
+
+Some good examples:
+
+* [l10n_ch_reports/data/account_financial_html_report_data.xml ]({GITHUB_ENT_PATH}/l10n_ch_reports/data/account_financial_html_report_data.xml)
+* [l10n_be_reports/data/account_financial_html_report_data.xml ]({GITHUB_ENT_PATH}/l10n_be_reports/data/account_financial_html_report_data.xml)
+
+You can check the meaning of the fields here:
+
+* :doc:`/developer/reference/standard_modules/account/account_report`
+* :doc:`/developer/reference/standard_modules/account/account_report_line`
+
+If you gave a `root_report_id` to your report, it is now available in its variant selector. If not,
+you still need to add a menu item for it. A default menu item can be created from the form view of
+the report by clicking on :menuselection:`Actions --> Create Menu Item`. You will then need to
+refresh the page to see it. Alternatively, to create a dedicated section for a totally new report in
+the :guilabel:`Reporting` menu, you need to create a new `ir.ui.menu` record (usually in the main
+`l10n_XX` module) and a new `ir.actions.client` (usually in the new report XML file) that calls the
+`account.report` with  the new **report id**. Then, set the new menu as `parent_id` field in the
+action model.
+
+.. example::
+   * [ir.ui.menu creation ]({GITHUB_PATH}/addons/l10n_be/data/menuitem_data.xml)
+   * [ir.actions.client and menu item creation ]({GITHUB_ENT_PATH}/l10n_be_reports/data/partner_vat_listing.xml)