odoo-forge-bundle 0.1.0

package/payload/skills/odoo18-docs/references/docs/applications/finance/accounting/customer_invoices/electronic_invoicing/romania.md

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

package/payload/skills/odoo18-docs/references/docs/applications/finance/accounting/customer_invoices/electronic_invoicing/slovenia.md

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

package/payload/skills/odoo18-docs/references/docs/applications/finance/accounting/customer_invoices/electronic_invoicing/spain.md

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

package/payload/skills/odoo18-docs/references/docs/applications/finance/accounting/customer_invoices/electronic_invoicing/uruguay.md

@@ -0,0 +1,58 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/finance/accounting/customer_invoices/electronic_invoicing/uruguay.html"
+---
+
+: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.

package/payload/skills/odoo18-docs/references/docs/applications/finance/accounting/customer_invoices/electronic_invoicing.md

@@ -0,0 +1,294 @@
+---
+title: "Electronic invoicing (:abbr:`EDI (electronic data interchange)`)"
+source_url: "https://docs.odoo.sbggai.top/applications/finance/accounting/customer_invoices/electronic_invoicing.html"
+---
+
+================================================================
+# Electronic invoicing (:abbr:`EDI (electronic data interchange)`)
+
+EDI, or electronic data interchange, is the inter-company communication of business documents, such
+as purchase orders and invoices, in a standard format. Sending documents according to an EDI
+standard ensures that the machine receiving the message can interpret the information correctly.
+Various EDI file formats exist and are available depending on your company's country.
+
+EDI feature enables automating the administration between companies and might also be required by
+some governments for fiscal control or to facilitate the administration.
+
+Electronic invoicing of your documents such as customer invoices, credit notes or vendor bills is
+one of the application of EDI.
+
+Odoo supports e-invoicing in many countries. Refer to the country's page for more details:
+
+- :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>`
+- :doc:`Germany <electronic_invoicing/germany>`
+- :doc:`Hungary <electronic_invoicing/hungary>`
+- :doc:`Ireland <electronic_invoicing/ireland>`
+- :doc:`Italy <electronic_invoicing/italy>`
+- :doc:`Latvia <electronic_invoicing/latvia>`
+- :doc:`Lithuania <electronic_invoicing/lithuania>`
+- :doc:`Luxembourg <electronic_invoicing/luxembourg>`
+- :doc:`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>`
+
+.. _e-invoicing/configuration:
+
+# Configuration
+
+By default, the format available in the :ref:`send window <e-invoicing/generation>` depends on your
+customer's country.
+
+You can define a specific e-invoicing format for each customer. To do so, go to
+:menuselection:`Accounting --> Customers --> Customers`, open the customer form, go to the
+:guilabel:`Accounting` tab and select the appropriate format.
+
+.. image:: electronic_invoicing/customer-form.png
+   :alt: Select an EDI format for a specific customer
+
+## National electronic invoicing
+
+Depending on your company's country (e.g., :doc:`Italy <../../fiscal_localizations/italy>`,
+:doc:`Spain <../../fiscal_localizations/spain>`, :doc:`Mexico
+<../../fiscal_localizations/mexico>`, etc.), you may be required to issue e-invoicing documents in
+a specific format for all your invoices. In this case, you can define a default e-invoicing format
+for your sales journal.
+
+To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, open your sales journal,
+go to the :guilabel:`Advanced Settings` tab, and enable the formats you need for this journal.
+
+.. _e-invoicing/generation:
+
+# E-invoices generation
+
+From a confirmed invoice, click :guilabel:`Send & Print` to open the send window. Check the
+e-invoicing option to generate and attach the e-invoice file.
+
+.. image:: electronic_invoicing/send-window.png
+   :alt: The Peppol option is checked and an e-invoicing XML file is attached to the email.
+
+# Peppol
+
+The [Peppol ](https://peppol.org/about/) network ensures the exchange of documents and information
+between enterprises and governmental authorities. It is primarily used for electronic invoicing, and
+its access points (connectors to the Peppol network) allow enterprises to exchange electronic
+documents.
+
+Odoo is an **access point** and an :abbr:`SMP (Service Metadata Publisher)`, enabling electronic
+invoicing transactions without the need to send invoices and bills by email or post.
+
+If not done yet, :ref:`install <general/install>` the :guilabel:`Peppol` module (`account_peppol`).
+
+> **important**:
+>    - Peppol registration is **free** and available in Odoo Community
+   - You can send **Customer Invoices** and **Credit Notes** and receive **Vendor Bills** and
+     **Refunds** via Peppol.
+   - You can send and receive in one of the following supported document formats:
+     **BIS Billing 3.0, XRechnung CIUS, NLCIUS**.
+   - | The following **countries** are eligible for **Peppol registration in Odoo**:
+     | Andorra, Albania, Austria, Bosnia and Herzegovina, Belgium, Bulgaria, Switzerland, Cyprus,
+       Czech Republic, Germany, Denmark, Estonia, Spain, Finland, France, United Kingdom, Greece,
+       Croatia, Hungary, Ireland, Iceland, Italy, Liechtenstein, Lithuania, Luxembourg, Latvia,
+       Monaco, Montenegro, North Macedonia, Malta, Netherlands, Norway, Poland, Portugal, Romania,
+       Serbia, Sweden, Slovenia, Slovakia, San Marino, Turkey, Holy See (Vatican City State)
+
+## Registration
+
+Go to :menuselection:`Accounting --> Configuration --> Settings`. If you do not have the
+Peppol module installed, first tick the :guilabel:`Enable PEPPOL` checkbox and then **manually
+save**. Click :guilabel:`Start sending via Peppol` to open the registration form.
+
+> **note**:
+>    This registration form also pops up if you choose to :guilabel:`Send & Print` an
+   invoice via Peppol without completing the registration process.
+
+.. image:: electronic_invoicing/peppol-registration-settings.png
+   :alt: Peppol registration button
+
+You can register either as a sender or a receiver. A sender can only send invoices and credit notes
+on Odoo via Peppol, without ever registering as a Peppol participant on Odoo SMP. If you have an
+existing Peppol registration elsewhere that you want to keep, but want to send invoices from your
+Odoo database and receive other documents in another software, register as a **sender**.
+
+> **tip**:
+>    - You can always register as a sender first and register to receive documents later.
+   - When registering, you can specify if you would also like to receive documents.
+
+.. image:: electronic_invoicing/peppol-registration-wizard.png
+   :alt: Peppol registration form
+
+Fill in the following information:
+
+- Check the receiver box if you want to register on Odoo SMP. If you are migrating from another
+  service provider, insert the :guilabel:`Migration key` from the previous provider (the field
+  becomes visible after you tick the checkbox).
+- :guilabel:`E-Address Scheme`: the Peppol Electronic Address Scheme usually depends on your
+  company's country. Odoo often prefills this with the most commonly used EAS code in your country.
+  For example, the preferred EAS code for most companies in Belgium is `0208`.
+- :guilabel:`Endpoint`: this is usually a Company Registry number or a VAT number.
+- :guilabel:`Phone`: phone number including the country code (e.g., `+32` in Belgium).
+- :guilabel:`Email`: this is the email Odoo can use to contact you regarding your Peppol
+  registration.
+
+If you want to explore or demo Peppol, you can choose to register in :guilabel:`Demo` mode.
+Otherwise, select :guilabel:`Live`.
+
+> **tip**:
+>    - Selecting :guilabel:`Demo` simulates everything in Odoo. There is no sending, receiving, or
+     partner verification.
+   - For **advanced users only**, it is possible to run tests on Peppol's test network. The server
+     allows to register on Peppol and send/receive test invoices to/from other participants.
+     To do so, enable the :ref:`developer-mode`, open the **Settings** app, go to
+     :menuselection:`Technical --> System Parameters`, and search for `account_peppol.edi.mode`.
+     Click the parameter and change the :guilabel:`Value` to `test`. Go back to the Peppol setup
+     menu in the **Settings** app. The option :guilabel:`Test` is now available.
+
+   .. image:: electronic_invoicing/peppol-system-parameter.png
+      :alt: Peppol test mode parameter
+
+.. seealso::
+   - [Peppol EAS - European Commision ](https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Code+lists/)
+   - [Peppol Endpoint - OpenPeppol eDEC Code Lists ](https://docs.peppol.eu/edelivery/codelists/)
+     (open the "Participant Identifier Schemes" as HTML page)
+
+When set up, request a verification code to be sent to you by clicking :guilabel:`Send a
+registration code by SMS`. A text message containing a code is sent to the phone number provided to
+finalize the verification process.
+
+.. image:: electronic_invoicing/peppol-phone-verification.png
+   :alt: phone validation
+
+Once you enter the code and click :guilabel:`Register`, your Peppol participant status is updated.
+If you chose to only send documents, then the status changes to :guilabel:`Can send but
+not receive`.
+If you opted to receive documents as well, the status changes to :guilabel:`Can send, pending
+registration to receive`. In that case, it should be automatically activated within a day.
+
+Then, set the default journal for receiving vendor bills in the :guilabel:`Incoming Invoices
+Journal`.
+
+> **tip**:
+>    To manually trigger the cron that checks the registration status, enable the
+   :ref:`developer-mode`, then go to :menuselection:`Settings --> Technical --> Scheduled Actions`,
+   and search for the :guilabel:`PEPPOL: update participant status` action.
+
+Your receiver application status should be updated soon after you are registered on the Peppol
+network.
+
+.. image:: electronic_invoicing/peppol-receiver.png
+   :alt: receiver application
+
+All invoices and vendor bills can now be sent directly using the Peppol network.
+
+> **important**:
+>    To update the email that Odoo can use to contact you, modify the email and click
+   :guilabel:`Update contact details`.
+
+## Configure Peppol services
+
+Once you are registered on Odoo SMP, the :guilabel:`Configure Peppol Services` button
+becomes visible to allow you to enable or disable document formats that other participants
+can send you via Peppol. By default, all document formats supported by Odoo are enabled (depending
+on the installed modules).
+
+## Contact verification
+
+Before sending an invoice to a contact using the Peppol network, it is necessary to verify that they
+are also registered as a Peppol participant.
+
+To do so, go to :menuselection:`Accounting --> Customers --> Customers` and open the customer's
+form. Then go to :menuselection:`Accounting tab --> Electronic Invoicing`, select the correct
+format, and make sure their :guilabel:`Peppol EAS code` and the :guilabel:`Endpoint` are filled in.
+Then, click :guilabel:`Verify`. If the contact exists on the network, their Peppol endpoint validity
+is set to Valid.
+
+.. image:: electronic_invoicing/peppol-contact-verify.png
+   :alt: verify contact registration
+
+> **important**:
+>    While Odoo prefills both the EAS code and the Endpoint number based on the information available
+   for a contact, it is better to confirm these details directly with the contact.
+
+It is possible to verify the Peppol participant status of several customers at once.
+To do so, go to :menuselection:`Accounting --> Customers --> Customers` and switch to the list view.
+Select the customers you want to verify and then click :menuselection:`Actions --> Verify Peppol`.
+
+If the participant is registered on the Peppol network but cannot receive the format you selected
+for them, the :guilabel:`Peppol endpoint validity` label changes to :guilabel:`Cannot
+receive this format`.
+
+.. image:: electronic_invoicing/peppol-participant-format.png
+   :alt: verify contact ubl format
+
+## Send invoices
+
+Once ready to send an invoice via the Peppol network, simply click :guilabel:`Send & Print` on the
+invoice form. To queue multiple invoices, select them in the list view and click
+:menuselection:`Actions --> Send & Print`; they will be sent in a batch later on. Both
+:guilabel:`BIS Billing 3.0` and :guilabel:`Send via PEPPOL` checkboxes need to be ticked.
+
+.. image:: electronic_invoicing/peppol-send-print.png
+   :alt: Send peppol invoice
+
+Posted invoices that can be sent via Peppol are marked as :guilabel:`Peppol Ready`.
+To display them, use the :guilabel:`Peppol Ready` filter or access the Accounting dashboard and
+click :guilabel:`Peppol ready invoices` on the corresponding sales journal.
+
+.. image:: electronic_invoicing/peppol-ready-invoices.png
+   :alt: Filter Peppol ready invoices
+
+Once the invoices are sent via Peppol, the status is changed to :guilabel:`Processing`. The
+status is changed to `Done` after they have been successfully delivered to the contact's Access
+Point.
+
+.. image:: electronic_invoicing/peppol-message-processing.png
+   :alt: Peppol message status
+
+> **tip**:
+>    By default, the Peppol status column is hidden on the Invoices list view. You can choose to have
+   it displayed by selecting it from the optional columns, accessible from the top right corner of
+   the Invoices list view.
+
+A cron runs regularly to check the status of these invoices. It is possible to check the status
+before the cron runs by clicking :guilabel:`Fetch Peppol invoice status` in the corresponding
+sales journal on the Accounting dashboard.
+
+.. image:: electronic_invoicing/peppol-fetch-message-status.png
+   :alt: Fetch invoice Peppol status
+
+## Receive vendor bills
+
+Once a day, a cron checks whether any new documents have been sent to you via the Peppol network.
+These documents are imported, and the corresponding vendor bills are created automatically as
+drafts.
+
+.. image:: electronic_invoicing/peppol-receive-bills.png
+   :alt: peppol receive bills
+
+If you want to retrieve incoming Peppol documents before the cron runs, you can do so from the
+Accounting dashboard on the main Peppol purchase journal that you set up in the settings. Just click
+:guilabel:`Fetch from Peppol`.
+
+.. image:: electronic_invoicing/peppol-fetch-bills.png
+   :alt: Fetch bills from Peppol

package/payload/skills/odoo18-docs/references/docs/applications/finance/accounting/customer_invoices/epc_qr_code.md

@@ -0,0 +1,62 @@
+---
+title: "EPC QR codes"
+source_url: "https://docs.odoo.sbggai.top/applications/finance/accounting/customer_invoices/epc_qr_code.html"
+---
+
+============
+# EPC QR codes
+
+European Payments Council quick response codes, or **EPC QR codes**, are two-dimensional barcodes
+that customers can scan with their **mobile banking applications** to initiate a **SEPA credit
+transfer (SCT)** and pay their invoices instantly.
+
+In addition to bringing ease of use and speed, it greatly reduces typing errors that would
+potentially make for payment issues.
+
+> **note**:
+>    This feature is only available for companies in several European countries such as Austria,
+   Belgium, Finland, Germany, and the Netherlands.
+
+.. seealso::
+   - :doc:`../bank`
+   - [Odoo Academy: QR Code on Invoices for European Customers ](https://www.odoo.com/r/VuU)
+
+# Configuration
+
+Go to :menuselection:`Accounting --> Configuration --> Settings` and activate the :guilabel:`QR
+Codes` feature in the :guilabel:`Customer Payments` section.
+
+## Configure your bank account's journal
+
+Make sure that your :guilabel:`Bank Account` is correctly configured in Odoo with your IBAN and BIC.
+
+To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, open your bank journal,
+then fill out the :guilabel:`Account Number` and :guilabel:`Bank` under the :guilabel:`Bank Account
+Number` column.
+
+.. image:: epc_qr_code/bank-journal.png
+   :alt: Bank account number column in the bank journal
+
+# Issue invoices with EPC QR codes
+
+EPC QR codes are added automatically to your invoices. Customers whose bank supports making payments
+via EPC QR codes will be able to scan the code and pay the invoice.
+
+Go to :menuselection:`Accounting --> Customers --> Invoices`, and create a new invoice.
+
+Before posting it, open the :guilabel:`Other Info` tab. Odoo automatically fills out the
+:guilabel:`Recipient Bank` field with your IBAN.
+
+> **note**:
+>    In the :guilabel:`Other Info` tab, the account indicated in the :guilabel:`Recipient Bank` field
+   is used to receive your customer's payment. Odoo automatically populates this field with your
+   IBAN by default and uses it to generate the EPC QR code.
+
+When the invoice is printed or previewed, the QR code is included at the bottom.
+
+.. image:: epc_qr_code/invoice-qr-code.png
+   :alt: QR code on a customer invoice
+
+> **tip**:
+>    If you want to issue an invoice without an EPC QR code, remove the IBAN indicated in the
+   :guilabel:`Recipient Bank` field, under the :guilabel:`Other Info` tab of the invoice.

package/payload/skills/odoo18-docs/references/docs/applications/finance/accounting/customer_invoices/incoterms.md

@@ -0,0 +1,59 @@
+---
+title: "Incoterms"
+source_url: "https://docs.odoo.sbggai.top/applications/finance/accounting/customer_invoices/incoterms.html"
+---
+
+=========
+# Incoterms
+
+:abbr:`Incoterms (International Commercial Terms)` are standardized trade terms used in
+international transactions to define the rights and responsibilities of buyers and sellers. They
+establish the obligations related to the delivery of goods, the transfer of risks, and the
+distribution of costs between the parties involved. Incoterms specify important details, such as the
+point at which the risk and costs transfer from the seller to the buyer, the responsibility for
+transportation, insurance, customs clearance, and other relevant aspects of the transaction.
+
+> **note**:
+>    By default, all 11 Incoterms are available in Odoo:
+
+   - **EXW**: Ex works
+   - **FCA**: Free carrier
+   - **FAS**: Free alongside ship
+   - **FOB**: Free on board
+   - **CFR**: Cost and freight
+   - **CIF**: Cost, insurance and freight
+   - **CPT**: Carriage paid to
+   - **CIP**: Carriage and insurance paid to
+   - **DPU**: Delivered at place unloaded
+   - **DAP**: Delivered at place
+   - **DDP**: Delivered duty paid
+
+.. seealso::
+   - :doc:`../reporting/intrastat`
+   - :doc:`../customer_invoices`
+   - :doc:`../vendor_bills`
+
+.. _incoterms/invoices:
+
+# Define an Incoterm
+
+To define an Incoterm manually, create an invoice or bill, click the :guilabel:`Other Info` tab, and
+select the :guilabel:`Incoterm`.
+
+## Incoterm location
+
+A location relevant to the chosen Incoterm can be added to the invoice or bill under
+:guilabel:`Other Info` in the :guilabel:`Incoterm Location` field.
+
+.. example::
+   If the chosen Incoterm code is `CIF` (Cost, Insurance, Freight), the associated location might be
+   the destination port where the goods will be delivered.
+
+.. _incoterms/default:
+
+# Default Incoterm configuration
+
+You can set a default Incoterm rule to **automatically** populate the Incoterm field on all newly
+created invoices and bills. Under :menuselection:`Accounting/Invoicing --> Configuration -->
+Settings`, scroll down to the :guilabel:`Customer Invoices` section, and select an Incoterm in the
+:guilabel:`Default Incoterm` field.