odoo-forge-bundle 0.1.0

package/payload/skills/odoo18-docs/references/docs/applications/finance/accounting/reporting/customize.md

@@ -0,0 +1,308 @@
+---
+title: "Custom reports"
+source_url: "https://docs.odoo.sbggai.top/applications/finance/accounting/reporting/customize.html"
+---
+
+==============
+# Custom reports
+
+Odoo comes with a powerful and easy-to-use reporting framework. The engine allows you to create new
+reports, such as **tax reports**, or **balance sheets** and **income statements** with **specific
+groupings** and **layouts**.
+
+> **important**:
+>    Activate the :ref:`developer mode <developer-mode>` to access the accounting report creation
+   interface.
+
+To create a new report, go to :menuselection:`Accounting --> Configuration --> Management:
+Accounting Reports`. From here, you can either create a :ref:`root report <customize-reports/root>`
+or a :ref:`variant <customize-reports/variants>`.
+
+.. image:: customize/engine-accounting-reports.png
+   :align: center
+   :alt: Accounting reports engine.
+
+.. _customize-reports/root:
+
+# Root reports
+
+Root reports can be regarded as generic, neutral accounting reports. They serve as models on which
+local accounting versions are built. If a report has no root report, it is considered to be a root
+report itself.
+
+.. example::
+   A tax report for Belgium and the US would both use the same generic version as a base and adapt
+   it for their domestic regulations.
+
+When creating a new root report, you need to create a **menu item** for it. To do so, open the
+report and then, on that same report, click on :menuselection:`Action --> Create Menu Item`. Refresh
+the page; the report is now available under :menuselection:`Accounting --> Reporting`.
+
+> **note**:
+>    Cases that require creating a new root report are rare, such as when a country's tax authorities
+   require a new and specific type of report.
+
+.. image:: customize/engine-create-menu-item.png
+   :align: center
+   :alt: Create Menu Item button.
+
+.. _customize-reports/variants:
+
+# Variants
+
+Variants are country-specific versions of root reports and, therefore, always refer to a root
+report. To create a variant, select a generic (root) report in the :guilabel:`Root Report` field
+when creating a new report.
+
+When a root report is opened from one of the accounting app's main menus, all its variants are
+displayed in the variant selector in the top right corner of the view.
+
+.. example::
+   In the following image, :guilabel:`VAT Report (BE)` is the variant of the root :guilabel:`Generic
+   Tax report`.
+
+   .. image:: customize/engine-variant.png
+      :align: center
+      :alt: Report variant selection.
+
+# Lines
+
+After having created a report (either root or variant), you need to fill it with lines. You can
+either create a new one by clicking on :guilabel:`Add a line`, or modify an existing line by
+clicking on it. All lines *require* a :guilabel:`Name`, and can have an optional additional
+:guilabel:`Code` (of your choice) if you wish to use their value in formulas.
+
+.. image:: customize/engine-lines-options.png
+   :align: center
+   :alt: Engine lines options.
+
+# Expressions
+
+Each line can contain one or multiple **expressions**. Expressions can be seen as **sub-variables**
+needed by a report line. To create an expression, click on :guilabel:`Add a line` *within* a line
+report.
+
+When creating an expression, you must attribute a :guilabel:`label` used to refer to that
+expression. Therefore, it has to be **unique** among the expressions of each line. Both a
+:guilabel:`Computation Engine` and a :guilabel:`Formula` must also be indicated. The **engine**
+defines how your **formula(s)** and **subformula(s)** are interpreted. It is possible to mix
+expressions using different computation engines under the same line if you need to.
+
+> **note**:
+>    Depending on the engine, :guilabel:`subformulas` may also be required.
+
+## 'Odoo Domain' engine
+
+With this engine, a formula is interpreted as an :ref:`Odoo domain <reference/orm/domains>`
+targeting `account.move.line` objects.
+
+The subformula allows you to define how the move lines matching the domain are used to compute the
+value of the expression:
+
+`sum`
+   The result is the sum of all the balances of the matched move lines.
+
+`sum_if_pos`
+   The result is the sum of all the balances of the matched move lines if this amount is positive.
+   Otherwise, it is `0`.
+
+`sum_if_neg`
+   The result is the sum of all the balances of the matched move lines if this amount is negative.
+   Otherwise, it is `0`.
+
+`count_rows`
+   The result is the number of sub-lines of this expression. If the parent line has a group-by
+   value, this will correspond to the number of distinct grouping keys in the matched move lines.
+   Otherwise, it will be the number of matched move lines.
+
+You can also put a `-` sign at the beginning of the subformula to **reverse** the sign of the
+result.
+
+.. image:: customize/engine-expressions.png
+   :align: center
+   :alt: Expression line within a line report
+
+## 'Tax Tags' engine
+
+A formula made for this engine consists of a name used to match tax tags. If such tags do not exist
+when creating the expression, they will be created.
+
+When evaluating the expression, the expression computation can roughly be expressed as: **(amount of
+the move lines with** `+` **tag)** `-` **(amount of the move lines with** `-` **tag)**.
+
+.. example::
+   If the formula is `tag_name`, the engine matches tax tags `+tag_name` and `-tag_name`, creating
+   them if necessary. To exemplify further: two tags are matched by the formula. If the formula
+   is `A`, it will require (and create, if needed) tags `+A` and `-A`.
+
+## 'Aggregate Other Formulas' engine
+
+Use this engine when you need to perform arithmetic operations on the amounts obtained for other
+expressions. Formulas here are composed of references to expressions separated by one of the four
+basic arithmetic operators (addition `+`, subtraction `-`, division `/`, and multiplication `*`). To
+refer to an expression, type in its parent line's **code** followed by a period `.` and the
+expression's **label** (ex. **code.label**).
+
+**Subformulas** can be one of the following:
+
+`if_above(CUR(amount))`
+   The value of the arithmetic expression will be returned only if it is greater than the provided
+   bound. Otherwise, the result will be `0`.
+
+`if_below(CUR(amount))`
+   The value of the arithmetic expression will be returned only if it is lower than the provided
+   bound. Otherwise, the result will be `0`.
+
+`if_between(CUR1(amount1), CUR2(amount2))`
+   The value of the arithmetic expression will be returned only if it is strictly between the
+   provided bounds. Otherwise, it will be brought back to the closest bound.
+
+`if_other_expr_above(LINE_CODE.EXPRESSION_LABEL, CUR(amount))`
+   The value of the arithmetic expression will be returned only if the value of the expression
+   denoted by the provided line code and expression label is greater than the provided bound.
+   Otherwise, the result will be `0`.
+
+`if_other_expr_below(LINE_CODE.EXPRESSION_LABEL, CUR(amount))`
+   The value of the arithmetic expression will be returned only if the value of the expression
+   denoted by the provided line code and expression label is lower than the provided bound.
+   Otherwise, the result will be `0`.
+
+`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.
+
+## 'Prefix of Account Codes' engine
+
+This engine is used to match amounts made on accounts using the prefixes of these accounts' codes as
+variables in an arithmetic expression.
+
+.. example::
+   | `21`
+   | Arithmetic expressions can also be a single prefix, such as here.
+
+.. example::
+   | `21 + 10 - 5`
+   | This formula adds the balances of the move lines made on accounts whose codes start with `21`
+     and `10`, and subtracts the balance of the ones on accounts with the prefix `5`.
+
+It is also possible to ignore a selection of sub-prefixes.
+
+.. example::
+   | `21 + 10\\(101, 102) - 5\\(57)`
+   | This formula works the same way as the previous example but ignores the prefixes `101`, `102`,
+     and `57`.
+
+You can apply 'sub-filtering' on **credits and debits** using the `C` and `D` suffixes. In this
+case, an account will only be considered if its prefix matches, *and* if the total balance of the
+move lines made on this account is **credit/debit**.
+
+.. example::
+   Account `210001` has a balance of -42 and account `210002` has a balance of 25. The formula
+   `21D` only matches the account `210002`, and hence returns 25. `210001` is not matched, as its
+   balance is *credit*.
+
+Prefix exclusions can be mixed with the `C` and `D` suffixes.
+
+.. example::
+   | `21D + 10\\(101, 102)C - 5\\(57)`
+   | This formula adds the balances of the move lines made on accounts whose code starts with `21`
+     *if* it is debit (`D`) and `10` *if* it is credit (`C`), but ignores prefixes `101`, `102`, and
+     subtracts the balance of the ones on accounts with the prefix `5`, ignoring the prefix `57`.
+
+To match the letter `C` or `D` in a prefix and not use it as a suffix, use an empty exclusion `()`.
+
+.. example::
+   | `21D\\()`
+   | This formula matches accounts whose code starts with `21D`, regardless of their balance sign.
+
+In addition to using code prefixes to include accounts, you can also match them with **account
+tags**. This is especially useful, for example, if your country lacks a standardized chart of
+accounts, where the same prefix might be used for different purposes across companies.
+
+.. example::
+   | `tag(25)`
+   | This formula matches accounts whose associated tags contain the one with id *25*.
+
+If the tag you reference is defined in a data file, an xmlid can be used instead of the id.
+
+.. example::
+   | `tag(my_module.my_tag)`
+   | This formula matches accounts whose associated tags include the tag denoted by
+     *my_module.my_tag*.
+
+You can also use arithmetic expressions with tags, possibly combining them with prefix selections.
+
+.. example::
+   | `tag(my_module.my_tag) + tag(42) + 10`
+   | The balances of accounts tagged as *my_module.my_tag* will be summed with those of accounts
+     linked to the tag with ID *42* and accounts with the code prefix `10`
+
+`C` and `D` suffixes can be used in the same way with tags.
+
+.. example::
+   | `tag(my_module.my_tag)C`
+   | This formula matches accounts with the tag *my_module.my_tag* and a credit balance.
+
+Prefix exclusion also works with tags.
+
+.. example::
+   | `tag(my_module.my_tag)\\(10)`
+   | This formula matches accounts with the tag *my_module.my_tag* and a code not starting with
+     `10`.
+
+
+## 'External Value' engine
+
+The 'external value' engine is used to refer to **manual** and **carryover values**. Those values
+are not stored using `account.move.line`, but with `account.report.external.value`. Each of these
+objects directly points to the expression it impacts, so very little needs to be done about their
+selection here.
+
+**Formulas** can be one of the following:
+
+`sum`
+   If the result must be the sum of all the external values in the period.
+
+`most_recent`
+   If the result must be the value of the latest external value in the period.
+
+In addition, **subformulas** can be used in two ways:
+
+`rounding=X`
+   Replacing `X` with a number instructs to round the amount to X decimals.
+
+`editable`
+   Indicates this expression can be edited manually, triggering the display of an icon in the
+   report, allowing the user to perform this action.
+
+> **note**:
+>    Manual values are created at the `date_to` currently selected in the report.
+
+Both subformulas can be mixed by separating them with a `;`.
+
+.. example::
+   | `editable;rounding=2`
+   | is a correct subformula mixing both behaviors.
+
+## 'Custom Python Function' engine
+
+This engine is a means for developers to introduce custom computation of expressions on a
+case-by-case basis. The formula is the name of a **python function** to call, and the subformula is
+a **key** to fetch in the **dictionary** returned by this function. Use it only if you are making a
+custom module of your own.
+
+# Columns
+
+Reports can have an **indefinite number** of columns to display. Each column gets its values from
+the **expressions** declared on the **lines**. The field :guilabel:`expression_label` of the column
+gives the label of the expressions whose value is displayed. If a line has no **expression** in that
+field, then nothing is displayed for it in this column. If multiple columns are required, you must
+use different **expression** labels.
+
+.. image:: customize/engine-columns.png
+   :align: center
+   :alt: Columns of report.
+
+When using the **period comparison** feature found under the :guilabel:`Options` tab of an
+accounting report, all columns are repeated in and for each period.

package/payload/skills/odoo18-docs/references/docs/applications/finance/accounting/reporting/data_inalterability.md

@@ -0,0 +1,115 @@
+---
+title: "Data inalterability check report"
+source_url: "https://docs.odoo.sbggai.top/applications/finance/accounting/reporting/data_inalterability.html"
+---
+
+================================
+# Data inalterability check report
+
+Tax authorities in some countries require companies to **prove their posted accounting entries are
+unaltered**, meaning that once an entry has been secured, it can no longer be changed.
+
+To do so, Odoo creates a unique fingerprint for each secured entry thanks to the **SHA-256 algorithm**.
+This fingerprint is called a hash. The hash is generated by taking an entry's essential data
+(the values of the `name`, `date`, `journal_id`, `company_id`, `debit`, `credit`, `account_id`, and
+`partner_id` fields), concatenating it, and inputting it to the SHA-256 hash function, which then
+outputs a fixed size (256-bit) string of characters. The hash function is deterministic (:dfn:`the
+same input always creates the same output`): any minor modification to the original data would
+completely change the resulting hash. Consequently, the SHA-256 algorithm is often used, among
+others, for data integrity verification purposes.
+
+In addition, the previous entry's hash is always added to the next entry to form a **hash chain**.
+This is used to ensure a new entry is not added afterward between two secured entries, as doing so
+would break the hash chain.
+
+> **note**:
+>    Hashes generated by the SHA-256 algorithm are theoretically not unique, as there is a finite
+   number of possible values. However, this number is exceptionally high: 2²⁵⁶, which is a lot
+   bigger than the number of atoms in the known universe. This is why hashes are considered unique
+   in practice.
+
+.. _data-inalterability/inalterability_features:
+
+# Inalterability features
+
+Inalterability features can be enabled by activating the :ref:`secure posted entries with hash
+<data-inalterability/restricted>` option on any journal or using the :ref:`secure entries wizard
+<data-inalterability/wizard>`.
+
+- Two indicators are added to the journal entry's form view.
+  They show whether the entry is secured or not.
+
+  - A :icon:`fa-lock` or :icon:`fa-unlock` (:guilabel:`lock icon`) next to the :guilabel:`Posted` state.
+  - A :guilabel:`Secured` checkbox in the :guilabel:`Other info` tab.
+
+- A :guilabel:`Not Secured` filter is available on journal entries and journal items' list views.
+  It can be used to find posted journal entries that are not secured yet.
+- The option to open the :ref:`secure entries wizard <data-inalterability/wizard>` is displayed in the
+  :guilabel:`Accounting` menu.
+
+.. _data-inalterability/restricted:
+
+# Secure posted entries with hash
+
+To activate the hashing function on a specific journal, go to :menuselection:`Accounting -->
+Configuration --> Journals`. Open a sales, purchase, or miscellaneous journal, go to the
+:guilabel:`Advanced Settings` tab, and enable :guilabel:`Secure Posted Entries with Hash`.
+Journals for which the feature is activated are called "restricted".
+
+To compute the hash of an entry, Odoo retrieves the predecessor entries of the chain (i.e., the
+entries with the same sequence prefix) and hashes them in a continuous way from the last hashed
+entry to the new entry to hash.
+
+> **warning**:
+>    Once you post an entry in a restricted journal, you cannot disable the feature anymore, nor edit
+   any secured entry.
+
+.. _data-inalterability/wizard:
+
+# Secure entries wizard
+
+You can also use the :guilabel:`Secure Entries` Wizard to secure all journal entries,
+in **all** journals, up to a specific date.
+
+> **note**:
+>    The wizard operates independently of the journal settings and journal types.
+
+To open it, activate the :ref:`developer mode <developer-mode>`, go to :menuselection:`Accounting
+--> Accounting`, and click on :guilabel:`Secure Entries`. If the :ref:`inalterability features
+<data-inalterability/inalterability_features>` are activated, it is also visible outside the debug
+mode.
+
+To secure entries, select a date up to which all entries should be secured and press
+:guilabel:`Secure Entries`.
+
+> **warning**:
+>    After securing the entries, you can no longer edit them.
+
+> **note**:
+>    It can happen that entries that are past the selected date are secured.
+   This is possible since the hash chain corresponds to the sequence prefix,
+   ordered by sequence number.
+
+.. _data-inalterability/report:
+
+# Report download
+
+To download the data inalterability check report, go to :menuselection:`Accounting --> Configuration
+--> Settings --> Reporting` and click on :guilabel:`Download the Data Inalterability Check Report`.
+
+The report's first section is an overview of all journal sequence prefixes containing hashed entries.
+In the :guilabel:`Restricted` column, you can see whether or not a journal has the :ref:`secure
+posted entries with hash <data-inalterability/restricted>` option (V) activated or not (X). The
+:guilabel:`Check` column tells you whether all entries are correctly hashed.
+
+.. image:: data_inalterability/journal-overview.png
+   :align: center
+   :alt: Configuration report for two journals
+
+The second section gives a more detailed result of the data consistency check for each hashed
+journal sequence prefix. You can view the first hashed entry and its corresponding hash,
+as well as the last hashed entry and its corresponding hash.
+
+.. image:: data_inalterability/data-consistency-check.png
+   :align: center
+   :alt: Data consistency check report for a journal

package/payload/skills/odoo18-docs/references/docs/applications/finance/accounting/reporting/intrastat.md

@@ -0,0 +1,189 @@
+---
+title: "Intrastat"
+source_url: "https://docs.odoo.sbggai.top/applications/finance/accounting/reporting/intrastat.html"
+---
+
+=========
+# Intrastat
+
+Intrastat is the data collection and statistics production system for goods traded among EU member
+states. It collects data on:
+
+- Commercial transactions of goods for use, consumption, investment, or resale with ownership
+  transfer;
+- Goods movements without transfer of ownership (e.g., stock relocations or moves of goods
+  before or after outsourced production or processing, and after maintenance or repair);
+- Returns of goods.
+
+> **note**:
+>    Although the Intrastat system continues to be used, the term Intrastat is not used in the [latest
+   legislation ](http://data.europa.eu/eli/reg/2019/2152/2022-01-01), referring instead to
+   *intra-Union trade in goods statistics*.
+
+.. seealso::
+   [Eurostat Statistics Explained - Glossary: Intrastat
+   ](https://ec.europa.eu/eurostat/statistics-explained/index.php?title=Glossary:Intrastat)
+
+.. _intrastat/general-configuration:
+
+# General configuration
+
+Enable the Intrastat report by going to :menuselection:`Accounting --> Configuration --> Settings`.
+Under the :guilabel:`Customer Invoices` section, tick :guilabel:`Intrastat` and then
+:guilabel:`Save`.
+
+.. _intrastat/default-transaction-codes:
+
+## Default transaction codes: invoice and refund
+
+You can set a default :ref:`transaction code <intrastat/transaction-code>` for all newly created
+invoice and refund transactions. Under :menuselection:`Accounting --> Configuration --> Settings`,
+select a :guilabel:`Default invoice transaction code` and/or a :guilabel:`Default refund transaction
+code` and then :guilabel:`Save`. The code will be set automatically on all respective invoice lines.
+
+.. _intrastat/region-code:
+
+## Region code
+
+The region code is **only used by Belgian companies**. Under :menuselection:`Accounting -->
+Configuration --> Settings`, select the :guilabel:`Company Intrastat Region` where the company is
+located and then :guilabel:`Save`.
+
+> **tip**:
+>    If your warehouses are located in more than one region, you can define the region code at the
+   level of each warehouse instead. To do so, go to :menuselection:`Inventory --> Configuration -->
+   Warehouses`, select a warehouse, set its :guilabel:`Intrastat region`, and then :guilabel:`Save`.
+
+   .. image:: intrastat/warehouse-region.png
+      :align: center
+      :alt: Adding the Intrastat region to a warehouse
+
+.. _intrastat/product-configuration:
+
+# Product configuration
+
+All products must be properly configured to be included in the Intrastat report.
+
+.. _intrastat/commodity-code:
+
+## Commodity code
+
+Commodity codes are internationally recognized reference numbers used to classify goods depending on
+their **nature**. Intrastat uses the [Combined Nomenclature ](https://taxation-customs.ec.europa.eu/customs-4/calculation-customs-duties/customs-tariff/combined-nomenclature_en).
+
+To add a commodity code, go to :menuselection:`Accounting --> Customers --> Products` and select a
+product. Under the :guilabel:`Accounting` tab, set the product's :guilabel:`Commodity Code`.
+
+.. seealso::
+   [National Bank of Belgium - Intrastat commodity codes
+   ](https://www.nbb.be/en/statistics/foreign-trade/nomenclature-and-codes)
+
+.. _intrastat/quantity:
+
+## Quantity: weight and supplementary unit
+
+Depending on the nature of the goods, it is necessary to specify either the product's weight in
+kilos (without packaging) or the product's supplementary unit, such as square meter (`m2`), number
+of items (`p/st`), liter (`l`), or gram (`g`).
+
+To add a product's weight or supplementary unit, go to :menuselection:`Accounting --> Customers -->
+Products` and select a product. Under the :guilabel:`Accounting` tab, depending on the commodity
+code set, either fill in the product :guilabel:`Weight` or its :guilabel:`Supplementary Units`.
+
+.. _intrastat/origin-country:
+
+## Country of origin
+
+To add the product's country of origin, go to :menuselection:`Accounting --> Customers --> Products`
+and select a product. Under the :guilabel:`Accounting` tab, set the :guilabel:`Country of Origin`.
+
+.. _intrastat/invoice-bill-configuration:
+
+# Invoices and bills configuration
+
+Once products are properly configured, several settings must be configured on the invoices and bills
+you create.
+
+.. _intrastat/transaction-code:
+
+## Transaction code
+
+Transaction codes are used to identify a transaction's nature. :ref:`Default transaction codes
+<intrastat/default-transaction-codes>` can be set for invoice and refund transactions.
+
+To set a transaction code on an invoice line, create an invoice or a bill, click the columns
+selection button, tick :guilabel:`Intrastat`, and use the newly-added :guilabel:`Intrastat` column
+to select a transaction code.
+
+.. image:: intrastat/intrastat-column.png
+   :align: center
+   :alt: Adding the Intrastat column to an invoice or bill
+
+.. seealso::
+   [National Bank of Belgium - Intrastat: Nature of transactions from January 2022
+   ](https://www.nbb.be/doc/dd/onegate/data/new_natures_of_transaction_2022_en.pdf)
+
+.. _intrastat/partner-country:
+
+## Partner country
+
+The partner country represents the vendor's country for bills and the customer's country for
+invoices. It is automatically filled in using the country set in the contact's :guilabel:`Country`
+field.
+
+To edit the partner country manually, create an invoice or a bill, click the :guilabel:`Other Info`
+tab, and select the :guilabel:`Intrastat Country`.
+
+.. _intrastat/transport-code:
+
+## Transport code
+
+The transport code identifies the presumed **mode of transport** used to send the goods (arrival or
+dispatch).
+
+To add the transport code, create an invoice or a bill, go to the :guilabel:`Other info` tab,
+and select the :guilabel:`Intrastat Transport Mode`.
+
+.. _intrastat/value:
+
+## Value of the goods
+
+The value of a good is the untaxed :guilabel:`Subtotal` (:guilabel:`Price` multiplied by
+:guilabel:`Quantity`) of an invoice line.
+
+.. _intrastat/partner:
+
+# Partner configuration
+
+Two fields from the partner's contact form are used with Intrastat: :guilabel:`VAT` and
+:guilabel:`Country`. The country can be :ref:`manually set <intrastat/partner-country>` on the
+invoice or bill.
+
+# Generate the Intrastat report
+
+Generate the report by going to :menuselection:`Accounting --> Reporting --> Audit Reports:
+Intrastat Report`. It is automatically computed based on the :ref:`default configuration
+<intrastat/general-configuration>` and the information found on the :ref:`products
+<intrastat/product-configuration>`, :ref:`invoices and bills
+<intrastat/invoice-bill-configuration>`, and :ref:`partners <intrastat/partner>`.
+
+Export the report as a PDF, XLSX, or XML file to post it to your legal administration.
+
+Each report line refers to a single invoice line and contains the following information:
+
+- Invoice or bill reference number;
+- System, which is a code automatically generated depending on whether the document is an invoice
+  (dispatch) or a bill (arrival);
+- :ref:`Country <intrastat/partner-country>`, which is the vendor's country for arrivals and the
+  customer's country for dispatches;
+- :ref:`Transaction Code <intrastat/transaction-code>`;
+- (If your company is located in Belgium) :ref:`Region Code <intrastat/region-code>`;
+- :ref:`Commodity Code <intrastat/commodity-code>`;
+- :ref:`Origin Country <intrastat/origin-country>`;
+- :ref:`Partner VAT <intrastat/partner>`;
+- :ref:`Transport Code <intrastat/transport-code>`;
+- :doc:`Incoterm Code <../customer_invoices/incoterms>`;
+- :ref:`Weight <intrastat/quantity>`;
+- :ref:`Supplementary Units <intrastat/quantity>`; and
+- :ref:`Value <intrastat/value>`, which is always expressed in euros even if the original invoice or
+  bill used another currency.

package/payload/skills/odoo18-docs/references/docs/applications/finance/accounting/reporting/silverfin.md

@@ -0,0 +1,69 @@
+---
+title: "Silverfin integration"
+source_url: "https://docs.odoo.sbggai.top/applications/finance/accounting/reporting/silverfin.html"
+---
+
+=====================
+# Silverfin integration
+
+[Silverfin ](https://www.silverfin.com) is a third-party service provider that offers a cloud
+platform for accountants.
+
+Odoo and Silverfin provide an integration to automate the synchronization of data.
+
+# Configuration
+
+To configure this integration, you need to input the following data into your Silverfin account:
+
+- user's email address
+- :ref:`Odoo API key <silverfin/api-key>`
+- URL of the Odoo database
+- name of your Odoo database
+
+.. _silverfin/api-key:
+
+## Odoo API key
+
+You can create Odoo external API keys either :ref:`for a single database <silverfin/api-singledb>`
+(hosting: Odoo Online, On-premise, and Odoo.sh) or :ref:`for all databases managed by a single user
+<silverfin/api-multipledb>` (hosting: Odoo Online).
+
+> **important**:
+>    - These API keys are personal and provide full access to your user account. Store it securely.
+   - You can copy the API key only at its creation. It is not possible to retrieve it later.
+   - If you need it again, create a new API key (and delete the old one).
+
+.. seealso::
+   :doc:`/developer/reference/external_api`
+
+.. _silverfin/api-singledb:
+
+### Per database
+
+To add an API key to a **single** database, connect to the database, enable the :ref:`developer
+mode <developer-mode>`, click on the user menu, and then :guilabel:`My Profile` /
+:guilabel:`Preferences`. Under the :guilabel:`Account Security` tab, click on :guilabel:`New API
+Key`, confirm your password, give a descriptive name to your new key, and copy the API key.
+
+.. image:: silverfin/api-key-db.png
+   :alt: creation of an Odoo external API key for a database
+
+.. seealso::
+   :ref:`api/external_api/keys`
+
+.. _silverfin/api-multipledb:
+
+### For all databases (fiduciaries)
+
+To add an API key to **all** databases managed by a single user at the same time **(the easiest
+method for fiduciaries)**, navigate to [Odoo's website ](https://www.odoo.com)  and sign in with
+your administrator account. Next, open [your account security settings in developer mode
+](https://www.odoo.com/my/security?debug=1), click on :guilabel:`New API Key`, confirm your
+password, give a descriptive name to your new key, and copy the new API key.
+
+> **tip**:
+>    Open the [database manager ](https://www.odoo.com/my/databases) to view all databases that will
+   be linked to the single API key.
+
+.. image:: silverfin/api-key-user.png
+   :alt: creation of an Odoo external API key for an Odoo user