Compare commits

...

35 Commits

Author SHA1 Message Date
khad-odoo 6caaf2bb88 Update 02_build_a_dashboard.rst
The useService("rpc") function is deprecated in odoo 18.

Now, the default way to call a controller which is not associated with a model is using the rpc function located in the web/static/src/core/network/rpc.js.

Therefore updated the "4. Call the server, add some statistics"  section to reflect the correct references in the odoo 18 tutorials/discover_js_framework docs.
2025-01-01 16:10:05 +05:30
Tiffany Chang (tic) d4841aee90 [I18N] *: export latest terms
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#11660

Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2024-12-31 16:47:48 +00:00
Felicious 80310b0e1c [ADD] inventory: compare packs and uom
closes odoo/documentation#11648

X-original-commit: 1ac6e5e975
Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
2024-12-31 10:30:54 +00:00
gmz-odoo 602d51c44b [IMP] accounting/l10n_pe: update GRE credentials section
closes odoo/documentation#11631

Context: after Odoo17 the menu changes on the settings from Accounting to Inventory, as this workflow is related to stock moves
X-original-commit: f3969af47e
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Signed-off-by: Gabriela Enriquez Manzano (gmz) <gmz@odoo.com>
2024-12-30 19:34:15 +00:00
Odoo Online 48a396a273 [I18N] Update translation terms from Transifex 2024-12-29 02:42:05 +01:00
Paolo Gatti 882b5a19e8 [FIX] fiscal_localizations: Italy, San Marino's destination code fix
Code is 2R4GTO8, not 2R4GT08.

task-4398355

closes odoo/documentation#11638

X-original-commit: 69e6279f65
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Paolo Gatti (pgi) <pgi@odoo.com>
2024-12-23 17:55:02 +00:00
Odoo Online 462b0b2f9e [I18N] Update translation terms from Transifex 2024-12-22 02:42:20 +01:00
Zachary Straub (ZST) a0c2f7220e [IMP] mrp: workcenter wording adjustment
closes odoo/documentation#11626

X-original-commit: 1a72b05e0a
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
2024-12-21 01:18:34 +00:00
emmi-odoo 2380a46300 [FIX] website/domain: add sub domain
task-4220363

closes odoo/documentation#11611

X-original-commit: 6cc9c9a75e
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Emmanuel Minga (EMMI) <emmi@odoo.com>
2024-12-20 07:36:26 +00:00
benderliz e7b6bdeb83 [FIX] payment_providers/authorize: update Excel import template
closes odoo/documentation#11588

X-original-commit: f552c117a8
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-12-19 15:36:13 +00:00
Donatienne (dopi) 45cd3403fb [IMP] ecommerce: shipping
taskid-4016678

closes odoo/documentation#11600

X-original-commit: 795afbb728
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
Signed-off-by: Donatienne Pirlot (dopi) <dopi@odoo.com>
2024-12-19 07:52:35 +00:00
Audrey (auva) 1f88cc3ee5 [IMP] fiscal_localization/philippines: updates for 18.0
Added sales WHT, QAP & SAWT report, and PH check printing documentation

Based on https://github.com/odoo/documentation/pull/11531

closes odoo/documentation#11595

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-12-18 10:53:20 +00:00
Jitendra Prajapat 7bba152676 [IMP] point_of_sale: remove start category feature from pos
In this commit:
==============
The "Start Category" feature has been removed from the Point of Sale.
This feature is now redundant due to the existing "Restrict Category" feature,
which provides similar functionality by limiting the available categories in POS

Task- 4405337

closes odoo/documentation#11582

Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-12-17 15:58:30 +00:00
Victorien (viso) bf0267d646 [IMP] fiscal_localization/italy: add configuration steps for fiscal printer
Since Odoo 18.0, we have introduced support for the italian fiscal printer.
These printers often come configured to use HTTP.
However for compliance reasons, Odoo POS is configured to only work with HTTPS.

That difference leads to errors connecting the POS to the printer.

This commit adds steps in the documentation for the users to configure their
printers and Odoo DB in order to resolve those issues.

While I think it's unconventional that we describe in our documentation the
steps to configure a third-party device, find below the only documentation
we were able to find from the manufacturers, while knowing EXCATLY what we were
looking for.
https://download4.epson.biz/sec_pubs/bs/pdf/Fiscal%20Printer%20Intelligent%20Features%20Guide%20Rev%20J.pdf
Given how cryptic this is, I highly doubt clients would make anything out of it,
resulting in many tickets.

here are already 4 tickets related to this issue
opw-4338402
opw-4306960
opw-4328481
opw-4351925

closes odoo/documentation#11485

Signed-off-by: Victorien Sonneville (viso) <viso@odoo.com>
2024-12-17 14:19:25 +00:00
afma-odoo 47cbfbef41 [IMP] accounting: update the analytic budgets page
task-4237563
task-4257623
task-4308176
task-4369415

closes odoo/documentation#11330

Signed-off-by: Anne-Françoise Marcq (afma) <afma@odoo.com>
2024-12-17 12:32:58 +00:00
xpl-odoo 9e98b8ebc1 [IMP] l10n: australia odoo 18 update
closes odoo/documentation#11482

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-12-17 12:32:54 +00:00
Louis Travaux 975564608b [ADD] sales: add Pricer discounts configuration
We added the support for discounts on pricer tags (electronic labels).
The documentation has been updated to describe the process of linking a pricelist to a tag.

closes odoo/documentation#11527

Task: 4060699
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-12-16 14:49:00 +00:00
xpl-odoo 15477ec14b [IMP] website: replace cloudflare's page rule by redirect rule
closes odoo/documentation#11578

X-original-commit: d1779bf4e5
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-12-16 11:37:29 +00:00
Odoo Online 19f574f7de [I18N] Update translation terms from Transifex 2024-12-15 02:43:01 +01:00
jero-odoo 6ce41f261b [ADD] Helpdesk: Stages
closes odoo/documentation#11565

Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>
Co-authored-by: larm-odoo <121518652+larm-odoo@users.noreply.github.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
2024-12-13 16:38:21 +00:00
Donatienne (dopi) b5dc2d1614 [IMP] website: URL translation note to be updated
taskid-4377816

closes odoo/documentation#11573

X-original-commit: 2e3e7ad35c
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
Signed-off-by: Donatienne Pirlot (dopi) <dopi@odoo.com>
2024-12-12 13:24:28 +00:00
Nathan Marotte (nama) c110917704 [FIX] Upgrade: Correct URL and text for post-upgrade issues
As stated on the sentence above, in case of an issue with the **production**
database, we should open a ticket with the label (production) and not
testing an upgrade.

This commits adapt the test to match the label currently present on
odoo.com/help and the URL to pre-select the correct stage as well

closes odoo/documentation#11563

X-original-commit: 08c43b3deb
Signed-off-by: Nathan Marotte (nama) <nama@odoo.com>
2024-12-12 08:29:39 +00:00
Vehiana Tepuhiarii cf05ed1c75 [IMP] ldap: disable referral chasing for Microsoft AD
based on https://github.com/odoo/documentation/pull/11462
reformat to comply with doc guidelines

closes odoo/documentation#11558

X-original-commit: 6e9de168d9
Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-12-12 06:54:28 +00:00
larm-odoo 02f8188b36 [IMP] Time Off: added multiple request section
closes odoo/documentation#11552

Signed-off-by: Lara Martini (larm) <larm@odoo.com>
2024-12-12 02:00:32 +00:00
“Chiara 8381d634f7 [ADD] accounting: e-invoicing regulations
task-4330898

closes odoo/documentation#11521

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-12-10 10:03:30 +00:00
Bastien PIERRE b66cad62fd [DOC] tours
closes odoo/documentation#11467

Signed-off-by: Bastien Pierre (ipb) <ipb@odoo.com>
2024-12-10 08:37:26 +00:00
xpl-odoo 8f0cd927c6 [IMP] general: remove mailjet notifications setup
closes odoo/documentation#11550

X-original-commit: a113cc42f5
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
2024-12-10 08:37:22 +00:00
LoredanaLrpz ff9a64e6f3 [IMP] l10n: pos 18.0 and on-premise certification
task-4391068

closes odoo/documentation#11544

X-original-commit: 50daadf7d1
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-12-09 18:51:53 +00:00
guillaume gallant (guga) 27b3c18816 [ADD] project: new top bar page
task-4277055

closes odoo/documentation#11519

Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com>
2024-12-09 07:55:56 +00:00
Odoo Online f1fca9af69 [I18N] Update translation terms from Transifex 2024-12-08 02:43:21 +01:00
benderliz 380cdb76b2 [IMP] Inventory: Update product type documentation
closes odoo/documentation#11409

Signed-off-by: Liz Bender (beli) <beli@odoo.com>
2024-12-05 00:50:03 +00:00
Sam Lieber (sali) 5060b34697 [IMP] accounting/avatax: update limitations for 18
closes odoo/documentation#11222

Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-12-04 22:31:26 +00:00
samueljlieber 7ead3df30d [IMP] sales: update settings navigation for multi address
closes odoo/documentation#11472

X-original-commit: c22f90137b
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Dina Klarisse Dugar (dikd) <dikd@odoo.com>
2024-12-04 14:52:56 +00:00
Sam Lieber (sali) 76e88f8f06 [FIX] tutorials: explicit translation function example
closes odoo/documentation#11525

X-original-commit: cb1f1e89d6
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
2024-12-04 14:52:54 +00:00
LoredanaLrpz 04111d2f04 [IMP] POS: returns and credit note
task-4016275

closes odoo/documentation#11501

X-original-commit: 208c1b8e81
Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>
2024-12-03 13:11:36 +00:00
370 changed files with 119456 additions and 82226 deletions
+2 -2
View File
@@ -390,8 +390,8 @@ few exceptions.
filestore before deploying the new version.
In case of an issue with your production database, you can request the assistance of Odoo by going
to the `Support page and selecting "An issue related to my future upgrade (I am testing an upgrade)"
<https://www.odoo.com/help?stage=migration>`_.
to the `Support page and selecting "An issue related to my upgrade (production)"
<https://www.odoo.com/help?stage=post_upgrade>`_.
.. _upgrade-sla:
@@ -13,49 +13,33 @@ some governments for fiscal control or to facilitate the administration.
Electronic invoicing of your documents such as customer invoices, credit notes or vendor bills is
one of the application of EDI.
Odoo supports, among others, the following formats.
Odoo supports e-invoicing in many countries. Refer to the country's page for more details:
.. list-table::
:header-rows: 1
* - Format Name
- Applicability
* - Factur-X (CII)
- All customers
* - Peppol BIS Billing 3.0
- All customers
* - XRechnung (UBL)
- All customers
* - Fattura PA (IT)
- Italian companies
* - CFDI (4.0)
- Mexican companies
* - Peru UBL 2.1
- Peruvian companies
* - SII IVA Llevanza de libros registro (ES)
- Spanish companies
* - UBL 2.1 (Columbia)
- Colombian companies
* - Egyptian Tax Authority
- Egyptian companies
* - E-Invoice (IN)
- Indian companies
* - NLCIUS (Netherlands)
- Dutch companies
* - EHF 3.0
- Norwegian companies
* - SG BIS Billing 3.0
- Singaporean companies
* - A-NZ BIS Billing 3.0
- All customers
.. note::
- The **Factur-X (CII)** format enables validation checks on the invoice and generates PDF/A-3
compliant files.
- Every PDF generated by Odoo includes an integrated **Factur-X** XML file.
- :doc:`Austria <electronic_invoicing/austria>`
- :doc:`Belgium <electronic_invoicing/belgium>`
- :doc:`Croatia <electronic_invoicing/croatia>`
- :doc:`Denmark <electronic_invoicing/denmark>`
- :doc:`Estonia <electronic_invoicing/estonia>`
- :doc:`Finland <electronic_invoicing/finland>`
- :doc:`France <electronic_invoicing/france>`
- :doc:`Germany <electronic_invoicing/germany>`
- :doc:`Hungary <electronic_invoicing/hungary>`
- :doc:`Ireland <electronic_invoicing/ireland>`
- :doc:`Italy <electronic_invoicing/italy>`
- :doc:`Latvia <electronic_invoicing/latvia>`
- :doc:`Lithuania <electronic_invoicing/lithuania>`
- :doc:`Luxembourg <electronic_invoicing/luxembourg>`
- :doc:`Netherlands <electronic_invoicing/netherlands>`
- :doc:`Norway <electronic_invoicing/norway>`
- :doc:`Poland <electronic_invoicing/poland>`
- :doc:`Portugal <electronic_invoicing/portugal>`
- :doc:`Romania <electronic_invoicing/romania>`
- :doc:`Slovenia <electronic_invoicing/slovenia>`
- :doc:`Spain <electronic_invoicing/spain>`
- :doc:`Spain - Basque Country <electronic_invoicing/basque_country>`
.. seealso::
:doc:`../../fiscal_localizations`
:doc:`Fiscal localizations documentation <../../fiscal_localizations>`
.. _e-invoicing/configuration:
@@ -0,0 +1,52 @@
:orphan:
====================================
Odoo electronic invoicing in Austria
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Austria's regulatory standards, and compatible with the European `Peppol
<https://peppol.org/about/>`_ framework.
Legal framework for e-invoicing in Austria
==========================================
In Austria, businesses must adhere to e-invoicing laws that ensure secure, authentic, and storable
transactions. The main regulation governing e-invoicing requirements in Austria is the `Austrian VAT
Act (UStG) <https://www.ris.bka.gv.at/GeltendeFassung.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10004873>`_
and its related e-invoicing standards for public procurement (`BGBI. I Nr. 32/2019 <https://360.lexisnexis.at/d/rechtsnorm-ris/32_bundesgesetz_mit_dem_das_beamten_dienstrechtsge/b_bgbl_2019_2019_I_32_46c550bf37>`_),
which aligns with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_.
These laws mandate that all businesses engaged in :abbr:`B2G (business-to-government)` transactions
must use e-invoicing, and increasingly, e-invoicing is encouraged for B2B transactions to improve
tax compliance and transparency.
Compliance with Austrian e-invoicing regulations
================================================
Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
invoices. Here is how Odoo ensures compliance:
- **Supported format**: Odoo supports standard e-invoice formats such as PDF with digital signatures
and XML in :abbr:`UBL (Universal Business Language)` format, which are fully compatible with
e-rechnung.gv.at, Austria's central electronic invoicing platform for public procurement
transactions. Any platform can be used if connected to the authentication services of the Federal
Service Portal (:abbr:`USP (Unternehmensserviceportal)`) e-rechnung.gv.at for e-invoicing
transmission.
- **Secure storage and retrieval**: In accordance with the Austrian requirement to store invoices
for a minimum of seven years, Odoo securely archives all invoices in a tamper-proof system,
ensuring that they can be easily retrieved during audits.
- **Automatic VAT calculation and reporting**: Odoo Invoicing helps businesses stay in line with
Austrian VAT requirements by automatically calculating and including VAT in invoices and ensuring
that each invoice follows the legal format for B2B and :abbr:`B2G (business-to-government)`
transactions.
.. seealso::
:doc:`Austria fiscal localization documentation <../../../fiscal_localizations/austria>`
.. admonition:: Disclaimer
This page provides an overview of Austrian e-invoicing laws and how Odoo Invoicing supports
compliance with the Austrian VAT Act (UStG) and related regulations. It does does not constitute
legal advice. We recommend consulting with a tax advisor or legal professional familiar with
Austrian e-invoicing regulations to ensure full compliance tailored to your specific business
requirements.
@@ -0,0 +1,50 @@
:orphan:
===============================================
Odoo electronic invoicing in the Basque Country
===============================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to meet Basque Country's regulatory standards.
Legal framework for e-invoicing in the Basque Country
=====================================================
In the Basque Country, electronic invoicing is governed by Spanish national legislation and regional
implementations, including the `Ley de Facturación Electrónica <https://www.facturae.gob.es/face/Paginas/FACE.aspx>`_
and compliance with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_.
For :abbr:`B2G (business-to-government)` transactions, e-invoicing is mandatory, and suppliers must
submit e-invoices through the FACe platform or the regional system, e-Factura Euskadi, specifically
designed for the Basque Country. These platforms ensure the secure submission of invoices to public
administrations. While B2B e-invoicing is not yet mandatory, its use is growing, supported by the
implementation of the TicketBAI system, which is specific to the Basque Country and promotes tax
transparency.
Compliance with Basque e-invoicing regulations
==============================================
Odoo Invoicing is fully prepared to help businesses meet the Basque Country's e-invoicing
requirements while complying with broader Spanish and EU standards. Here is how Odoo ensures
compliance:
- **Supported formats**: Odoo supports formats such as Facturae XML, required for compliance with
the FACe and e-Factura Euskadi platforms. Additionally, Odoo integrates with the TicketBAI system,
ensuring all invoices meet the technical and legal standards for secure submission to tax
authorities. Odoo enables businesses to submit e-invoices seamlessly to the FACe platform for
national compliance and the e-Factura Euskadi system for regional public administration
transactions. Furthermore, Odoo supports compliance with the TicketBAI initiative, specific to the
Basque Country.
- **Secure storage and retrieval**: In accordance with regulations requiring invoices to be stored
for a minimum of 6 years, Odoo provides a secure, tamper-proof archive for all invoices, allowing
easy access for audits and tax reviews.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations, ensuring
invoices adhere to Basque Country VAT requirements for B2G and B2B transactions while facilitating
compliance with the SII (Immediate Supply of Information) system for real-time VAT reporting.
.. admonition:: Disclaimer
This page provides an overview of e-invoicing laws in the Basque Country and how Odoo Invoicing
supports compliance with the Ley de Facturación Electrónica, e-Factura Euskadi, TicketBAI system,
and FACe platform. It is not intended as legal advice. We recommend consulting with a tax advisor
or legal professional familiar with e-invoicing regulations in the Basque Country to ensure
compliance tailored to your specific business needs.
@@ -0,0 +1,53 @@
:orphan:
====================================
Odoo electronic invoicing in Belgium
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Belgium's regulatory standards, and compatible with the European `Peppol
<https://peppol.org/about/>`_ framework.
Legal framework for e-invoicing in Belgium
==========================================
In Belgium, businesses must adhere to e-invoicing laws that ensure secure, authentic, and storable
transactions. The primary regulation governing e-invoicing requirements in Belgium is the `Belgian
VAT Code <https://finances.belgium.be/fr/sur_le_spf/r%C3%A9glementation/r%C3%A9glementation-2023/tva>`_
and its related `e-invoicing standards for public procurement <https://www.ejustice.just.fgov.be/cgi_loi/article.pl?language=fr&sum_date=&pd_search=2023-09-21&numac_search=2023045155&page=1&lg_txt=F&caller=list&2023045155=0&trier=promulgation&fr=f&nm_ecran=2023045155&choix1=et&choix2=et>`_,
which align with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_.
These laws mandate that all businesses engaged in :abbr:`B2G (business-to-government)` transactions
must use e-invoicing via Mercurius, Belgium's official electronic invoicing platform for public
procurement transactions. Additionally, Belgium is part of the Peppol network, which provides a
standardized framework for cross-border e-invoicing across Europe. Increasingly, e-invoicing is also
encouraged for B2B transactions to enhance tax compliance and transparency.
Compliance with Belgian e-invoicing regulations
===============================================
Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
invoices. Here is how Odoo ensures compliance:
- **Peppol-compliant formats**: Odoo supports the standardized XML (:abbr:`UBL (Universal Business
Language)`) format for Peppol, ensuring compliance with both Belgian and European e-invoicing
standards. This ensures your invoices meet the legal requirements for public procurement in
Belgium and other EU countries. Odoo enables businesses to send e-invoices directly to government
entities in compliance with Belgian regulations through Belgiums Mercurius platform for public
procurement.
- **Secure storage and retrieval**: In accordance with Belgian requirements to store invoices for a
minimum of seven years, Odoo securely archives all invoices in a tamper-proof system, ensuring
that they can be easily retrieved during audits.
- **Automatic VAT calculation and reporting**: Odoo Invoicing helps businesses comply with Belgian
VAT requirements by automatically calculating and including VAT in invoices and ensuring that each
invoice follows the legal format for B2B and :abbr:`B2G (business-to-government)` transactions.
.. seealso::
:doc:`Belgium fiscal localization documentation <../../../fiscal_localizations/belgium>`
.. admonition:: Disclaimer
This page provides an overview of Belgian e-invoicing laws and how Odoo Invoicing supports
compliance with the Belgian VAT Code, Peppol standards, and related regulations. It does not
constitute legal advice. We recommend consulting with a tax advisor or legal professional
familiar with Belgian e-invoicing regulations to ensure full compliance tailored to your specific
business requirements.
@@ -0,0 +1,50 @@
:orphan:
====================================
Odoo electronic invoicing in Croatia
====================================
Odoo Invoicing is our trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Croatia's regulatory standards.
Legal framework for e-invoicing in Croatia
==========================================
In Croatia, businesses must comply with e-invoicing regulations to ensure secure, authentic, and
storable transactions. The main legal framework governing e-invoicing in Croatia is the
Fiscalization Act and its related requirements for public procurement, which are aligned with `EU
Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_ on
e-invoicing in public procurement. Under these regulations, all businesses involved in :abbr:`B2G
(business-to-government)` transactions are required to use electronic invoicing via the :abbr:`CIS
(Central Invoice System)`, Croatias official platform for public sector e-invoicing. Croatia is
also part of the Peppol network, facilitating standardized cross-border e-invoicing within the
European Union. Furthermore, e-invoicing is increasingly encouraged for B2B transactions, promoting
greater transparency and tax compliance.
Compliance with Croatian e-invoicing regulations
================================================
Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
invoices. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports standard e-invoice formats, such as PDF with digital
signatures and XML in :abbr:`UBL (Universal Business Language)` format, which are fully compatible
with Croatia's :abbr:`CIS (Central Invoice System)` for public procurement transactions.
Additionally, Odoo enables transmission of e-invoices through any platform connected to the Peppol
network, as the *Servis eRačun za državu* reached via Peppol, ensuring compliance with both
Croatian and EU standards.
- **Secure storage and retrieval**: In accordance with Croatian regulations to store invoices for a
minimum of eleven years, Odoo securely archives all invoices in a tamper-proof system, ensuring
they can be easily retrieved during audits.
- **Automatic VAT calculation and reporting**: Odoo Invoicing helps businesses stay in line with
Croatian VAT requirements by automatically calculating and including VAT in invoices and ensuring
that each invoice follows the legal format for both B2B and :abbr:`B2G (business-to-government)`
transactions.
.. admonition:: Disclaimer
This page provides an overview of Croatian e-invoicing laws and how Odoo Invoicing supports
compliance with the Fiscalization Act, Peppol standards, and other relevant regulations. It does
not constitute legal adviceWe recommend consulting with a tax advisor or legal professional
familiar with Croatian e-invoicing regulations to ensure compliance tailored to your specific
business needs.
@@ -0,0 +1,47 @@
:orphan:
====================================
Odoo electronic invoicing in Denmark
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Denmark's regulatory standards.
Legal framework for e-invoicing in Denmark
==========================================
In Denmark, e-invoicing is governed by `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
mandating the use of e-invoicing for :abbr:`B2G (business-to-government)` transactions. Danish
public sector entities require invoices to be submitted through NemHandel, the national e-invoicing
platform, using the OIOUBL format (a local version of :abbr:`UBL (Universal Business Language)` and
XML). Denmark is also a key member of the Peppol network, enabling streamlined, standardized, and
secure cross-border e-invoicing for transactions within the European Union. While e-invoicing is not
mandatory for B2B transactions, its adoption is growing as businesses seek greater efficiency and
compliance.
Compliance with Danish e-invoicing regulations
==============================================
Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
invoices. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports OIOUBL, which is required for public sector invoicing via
NemHandel. It also supports UBL XML for transactions through the Peppol network, ensuring
compatibility with Denmarks and Europes e-invoicing standards. Odoo enables businesses to send
e-invoices through NemHandel, directly to Danish public entities in the required format. For
international transactions, Odoo ensures compatibility with Peppol Access Points,
facilitating cross-border invoicing.
- **Secure storage and retrieval**: In line with Danish regulations, which require businesses to
store invoices for at least five years, Odoo securely archives all invoices in a tamper-proof
system, ensuring easy access for audits and compliance checks.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and
ensures invoices are formatted to meet Denmarks legal requirements for B2G and B2B transactions,
helping businesses comply with local tax laws.
.. admonition:: Disclaimer
This page provides an overview of Danish e-invoicing laws and how Odoo Invoicing supports
compliance with NemHandel, OIOUBL standards, Peppol standards, and other relevant regulations. It
does not constitute legal advice. We recommend consulting with a tax advisor or legal
professional familiar with Danish e-invoicing regulations to ensure compliance tailored to your
specific business needs.
@@ -0,0 +1,47 @@
:orphan:
====================================
Odoo electronic invoicing in Estonia
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Estonia's regulatory standards.
Legal framework for e-invoicing in Estonia
==========================================
In Estonia, businesses must comply with e-invoicing regulations to ensure secure, authentic, and
storable transactions. The main legal framework governing e-invoicing in Estonia is the `Accounting
Act <https://www.riigiteataja.ee/en/eli/ee/514052021001/consolide/current>`_ and its provisions
related to e-invoicing, which align with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_
on e-invoicing in public procurement. Since 2019, :abbr:`B2G (business-to-government)` transactions
must use electronic invoices via Estonia's Rik's e-Invoicing System, the government's platform for
public sector e-invoicing. Estonia is also part of the Peppol network, which ensures standardized
cross-border e-invoicing across Europe. Additionally, the use of e-invoicing is encouraged for B2B
transactions, promoting better transparency, efficiency, and compliance with VAT requirements.
Compliance with Estonian e-invoicing regulations
================================================
Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
invoices. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports standard e-invoice formats, such as XML in :abbr:`UBL
(Universal Business Language)` format, which is fully compatible with Estonia's Riks e-Invoicing
System for public procurement transactions. Additionally, Odoo enables seamless transmission of
e-invoices through platforms connected to the Peppol network, ensuring compliance with Estonian
and EU e-invoicing standards.
- **Secure storage and retrival**: In accordance with Estonian regulations to store invoices for a
minimum of seven years, Odoo securely archives all invoices in a tamper-proof system, making them
easily retrievable during audits.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
invoices are formatted to meet Denmarks legal requirements for :abbr:`B2G
(business-to-government)` and B2B transactions, helping businesses compliant with local tax laws.
.. admonition:: Disclaimer
This page provides an overview of Estonian e-invoicing laws and how Odoo Invoicing supports
compliance with the Accounting Act, Peppol standards, and other relevant regulations. It does not
constitute legal advice. We recommend consulting with a tax advisor or legal professional
familiar with Estonian e-invoicing regulations to ensure compliance tailored to your specific
business needs.
@@ -0,0 +1,47 @@
:orphan:
====================================
Odoo electronic invoicing in Finland
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Finland's regulatory standards.
Legal framework for e-invoicing in Finland
==========================================
In Finland, businesses must comply with e-invoicing regulations to ensure secure, authentic, and
storable transactions. The primary legal framework governing e-invoicing is the `Act on Electronic
Invoicing (241/2019) <https://www.finlex.fi/fi/laki/alkup/2019/20190241#Pidp446241968>`_, which
aligns with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_
on electronic invoicing in public procurement. Under Finnish law, all :abbr:`B2G
(business-to-government)` transactions require the use of electronic invoices via Apix Messaging or
other Peppol-connected platforms, Finlands standard for public sector e-invoicing. Finland is also
part of the Peppol network, ensuring interoperability and standardization for cross-border
e-invoicing within the EU. Additionally, e-invoicing is widely adopted for B2B transactions,
promoting efficient processes and improved tax compliance.
Compliance with Finnish e-invoicing regulations
===============================================
Odoo invoicing module makes it easy for businesses to adhere to Finland's e-invoicing regulations.
Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the e-invoicing formats widely used in Finland, including
TEAPPSXML, Finvoice, and the standardized XML in :abbr:`UBL (Universal Business Language)` format
required for Peppol compliance. This ensures compatibility with Finnish platforms such as Handi
for public sector invoicing and eKuitti for enhanced receipt management and e-invoicing.
- **Secure storage and retrieval**: In accordance with Finnish regulations requiring businesses to
store invoices for a minimum of seven years, Odoo securely archives all invoices in a tamper-proof
system, allowing for easy retrieval during audits.
- **Automatic VAT calculation and reporting**: Odoo Invoicing ensures compliance with Finnish VAT
requirements by automatically calculating and including VAT in invoices and formatting them to
meet the legal standards for both B2B and :abbr:`B2G (business-to-government)` transactions.
.. admonition:: Disclaimer
This page provides an overview of Finnish e-invoicing laws and how Odoo Invoicing supports
compliance with the Act on Electronic Invoicing, Peppol standards, and other relevant
regulations. It is not intended as legal advice. We recommend consulting with a tax advisor or
legal professional familiar with Finnish e-invoicing regulations to ensure compliance tailored to
your specific business needs.
@@ -0,0 +1,50 @@
:orphan:
===================================
Odoo electronic invoicing in France
===================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to France's regulatory standards.
Legal framework for e-invoicing in France
=========================================
In France, electronic invoicing is regulated by the `Ordonnance n° 2019-359
<https://www.legifrance.gouv.fr/jorf/id/JORFTEXT000038410002>`_, which is aligned with `EU Directive
2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_, and requires
mandatory :abbr:`B2G (business-to-government)` e-invoicing through the Chorus Pro platform. Starting
in 2024, B2B e-invoicing will be progressively implemented, becoming mandatory for all businesses by
2026. This reform aims to combat tax fraud, improve VAT collection, and enhance business
transparency. The Factur-X hybrid format (a combination of PDF and XML data) is widely used in
France, ensuring compliance with both local and European e-invoicing standards.
Compliance with French e-invoicing regulations
==============================================
Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
invoices. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the Factur-X hybrid format (PDF with embedded XML) required
for compliance with French e-invoicing standards. It is also compatible with :abbr:`UBL (Universal
Business Language)` XML for transactions via the Peppol network, facilitating both local and
international invoicing. Odoo enables businesses, through Chorus Pro Frances official e-invoicing
platform, to submit compliant e-invoices directly to public authorities and soon to private sector
recipients as B2B e-invoicing becomes mandatory.
- **Secure storage and retrieval**: In compliance with French regulations, which require invoices to
be stored for a minimum of 10 years, Odoo securely archives all invoices in a tamper-proof system,
ensuring easy access for audits and inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations, ensuring
invoices meet French VAT requirements and are formatted correctly for both B2G and B2B
transactions, supporting seamless compliance with evolving standards.
.. seealso::
:doc:`France fiscal localization documentation <../../../fiscal_localizations/france>`
.. admonition:: Disclaimer
This page provides an overview of French e-invoicing laws and how Odoo Invoicing supports
compliance with the Chorus Pro platform, Factur-X standard, Peppol network, and other relevant
regulations. It does not constitute legal advice. We recommend consulting with a tax advisor or
legal professional familiar with French e-invoicing regulations to ensure compliance tailored to
your specific business needs.
@@ -0,0 +1,47 @@
:orphan:
====================================
Odoo electronic invoicing in Germany
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Germany's regulatory standards.
Legal framework for e-invoicing in Germany
==========================================
In Germany, e-invoicing is governed by the `E-Rechnungsgesetz <https://www.bgbl.de/xaver/bgbl/start.xav?start=%2F%2F*%5B%40attr_id%3D%27bgbl117s0770.pdf%27%5D#__bgbl__%2F%2F*%5B%40attr_id%3D%27bgbl117s0770.pdf%27%5D__1733401471138>`_,
which is aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
requiring e-invoicing for all :abbr:`B2G (business-to-government)` transactions. Invoices to public
sector entities must comply with the XRechnung format or the Peppol BIS Billing 3.0 standard.
Submission is typically handled through platforms like :abbr:`ZRE (Zentraler Rechnungseingang)` or
:abbr:`OZG-RE (Onlinezugangsgesetz-Rechnungseingang)`. While B2B e-invoicing is not yet mandatory,
its adoption is increasing as businesses seek to enhance compliance, efficiency, and transparency.
Compliance with German e-invoicing regulations
==============================================
Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
invoices. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports both XRechnung (XML), the mandatory format for public sector
e-invoicing, and Peppol BIS Billing 3.0, enabling seamless compliance with Germanys national and
European standards.
- **Secure storage and retrieval**: In line with German regulations, which require invoices to be
stored for at least ten years, Odoo securely archives all invoices in a tamper-proof system,
ensuring they are easily accessible for audits and compliance checks.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations, ensuring
compliance with German VAT requirements and proper formatting for both :abbr:`B2G
(business-to-government)` and B2B transactions, supporting efficient reporting and legal
adherence.
.. seealso::
:doc:`Germany fiscal localization documentation <../../../fiscal_localizations/germany>`
.. admonition:: Disclaimer
This page provides an overview of German e-invoicing laws and how Odoo Invoicing supports
compliance with E-Rechnungsgesetz, XRechnung, Peppol standards, and other relevant regulations.
It does not constitute legal advice. We recommend consulting with a tax advisor or legal
professional familiar with German e-invoicing regulations to ensure compliance tailored to your
specific business needs.
@@ -0,0 +1,46 @@
:orphan:
====================================
Odoo electronic invoicing in Hungary
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Hungary's regulatory standards.
Legal framework for e-invoicing in Hungary
==========================================
In Hungary, businesses must adhere to e-invoicing regulations to ensure secure, authentic, and
storable transactions. The primary legal framework is the Hungarian VAT Act (Act CXXVII of 2007),
which mandates real-time reporting of invoices to the NAV Online invoice system, Hungary's
government e-invoicing platform. As of 2021, all B2B and B2C invoices must be reported in real-time,
regardless of value. Hungary's regulations do not currently require :abbr:`B2G
(business-to-government)` e-invoicing, but public sector invoicing is encouraged via the Peppol
network. Common formats for e-invoicing include XML for NAV submissions and other structured formats
to streamline compliance.
Compliance with Hungarian e-invoicing regulations
=================================================
Odoo invoicing module is designed to help businesses meet Hungary's e-invoicing and VAT reporting
requirements. Here is how Odoo ensures compliance:
- **Supported Formats**: Odoo supports the standardized XML format required for integration with the
NAV (Nemzeti Adó és Vámhivatal) Online Invoice System, ensuring seamless real-time invoice
reporting. The module also supports formats compatible with Peppol for cross-border transactions,
promoting compliance with EU e-invoicing standards. Odoo enables businesses to automatically
report invoices to the Hungarian tax authorities in real-time, as required by law.
- **Secure storage and retrieval**: In accordance with Hungarian regulations, which mandate storing
invoices for a minimum of eight years, Odoo securely archives all invoices in a tamper-proof
system, allowing for easy retrieval during audits.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
invoices meet the strict requirements of the Hungarian VAT Act, simplifying compliance for B2B and
B2C transactions.
.. admonition:: Disclaimer
This page provides an overview of Hungarian e-invoicing laws and how Odoo Invoicing supports
compliance with the Hungarian VAT Act, NAV Online Invoice System, Peppol standards, and other
relevant regulations. It does not constitute legal advice. We recommend consulting with a tax
advisor or legal professional familiar with Hungarian e-invoicing regulations to ensure
compliance tailored to your specific business needs.
@@ -0,0 +1,46 @@
:orphan:
====================================
Odoo electronic invoicing in Ireland
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Ireland's regulatory standards.
Legal framework for e-invoicing in Ireland
==========================================
In Ireland, businesses must comply with e-invoicing regulations to ensure secure, authentic, and
storable transactions. The legal framework for e-invoicing is primarily shaped by `EU Directive
2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_, which
mandates the use of electronic invoicing in :abbr:`B2G (business-to-government)` transactions. Irish
public sector bodies must accept electronic invoices that comply with the European Standard EN
16931. E-invoicing in the public sector is facilitated through the Peppol network, providing a
streamlined and standardized platform for invoicing. While not mandatory for B2B transactions,
e-invoicing is increasingly encouraged to enhance efficiency, transparency, and compliance.
Compliance with Irish e-invoicing regulations
=============================================
Odoo Invoicing is equipped to meet Ireland's e-invoicing requirements, ensuring businesses
can operate with confidence. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the XML and :abbr:`UBL (Universal Business Language)` formats
required for Peppol compliance and ensures compatibility with the European Standard EN 16931,
which is the basis for public sector e-invoicing in Ireland. Odoo seamlessly integrates with the
Peppol network, enabling businesses to send compliant e-invoices directly to Irish public sector
bodies and facilitating cross-border invoicing in line with EU standards.
- **Secure storage and retrieval**: In accordance with Irish regulations that require businesses to
retain invoices for a minimum of six years, Odoo securely archives all invoices in a tamper-proof
system, ensuring they can be easily accessed during audits or inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing ensures full compliance with Irish VAT
regulations by automatically calculating and including VAT in invoices, while formatting them to
meet the legal requirements for both B2B and :abbr:`B2G (business-to-government)` transactions.
.. admonition:: Disclaimer
This page provides an overview of Irish e-invoicing laws and how Odoo Invoicing supports
compliance with EU Directive 2014/55/EU, Peppol standards, and other relevant regulations. It
does not constitute legal advice. We recommend consulting with a tax advisor or legal
professional familiar with Irish e-invoicing regulations to ensure compliance tailored to your
specific business needs.
@@ -0,0 +1,50 @@
:orphan:
==================================
Odoo electronic invoicing in Italy
==================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Italy's regulatory standards.
Legal framework for e-invoicing in Italy
========================================
Italy has one of the most advanced e-invoicing frameworks in Europe, governed by the `Italian budget
law <https://www.gazzettaufficiale.it/eli/id/2022/12/29/22G00211/sg>`_ and regulations issued by the
Agenzia delle Entrate. Since 2019, e-invoicing is mandatory for B2B, B2C, and :abbr:`B2G
(business-to-government)` transactions. All e-invoices must be submitted through the :abbr:`Sdi
(Sistema di Interscambio)`, the Italian government's centralized exchange system. The format for
e-invoices is FatturaPA, a structured XML format specifically designed for compliance with Italian
regulations. As part of its compliance with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
Italy also supports Peppol standards for cross-border e-invoicing.
Compliance with Italian e-invoicing regulations
===============================================
Odoo Invoicing is fully equipped to meet Italy's e-invoicing requirements. Here is how Odoo ensures
compliance:
- **Supported formats**: Odoo supports the FatturaPA XML format required by the :abbr:`Sdi (Sistema
di Interscambio)` for all domestic e-invoices, as well as :abbr:`UBL (Universal Business
Language)` XML for cross-border invoicing via the Peppol network, ensuring compliance with both
Italian and EU standards. Odoo has an easy access to the :abbr:`Sdi (Sistema di Interscambio)`
platform, allowing businesses to send, validate, and track invoices in real-time, ensuring
seamless compliance with Italian regulations.
- **Secure storage and retrieval**: In accordance with Italian law, which requires invoices to be
stored for a minimum of ten years, Odoo securely archives all invoices in a tamper-proof system,
ensuring they can be easily retrieved for audits or inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
invoices adhere to the strict formatting and reporting requirements of Italian law for B2B, B2C,
and :abbr:`B2G (business-to-government)` transactions.
.. seealso::
:doc:`Italy fiscal localization documentation <../../../fiscal_localizations/italy>`
.. admonition:: Disclaimer
This page provides an overview of Italian e-invoicing laws and how Odoo Invoicing supports
compliance with the Italian Budget Law, :abbr:`Sdi (Sistema di Interscambio)`, FatturaPA format,
Peppol standards, and other relevant regulations. It does not constitute legal advice. We
recommend consulting with a tax advisor or legal professional familiar with Italian e-invoicing
regulations to ensure compliance tailored to your specific business needs.
@@ -0,0 +1,45 @@
:orphan:
===================================
Odoo electronic invoicing in Latvia
===================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Latvia's regulatory standards.
Legal framework for e-invoicing in Latvia
=========================================
In Latvia, electronic invoicing is governed by the `Law on Accounting <https://eur-lex.europa.eu/legal-content/LV/TXT/PDF/?uri=CELEX:72014L0055LVA_270633>`_
and regulations aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
mandating the use of e-invoicing in :abbr:`B2G (business-to-government)` transactions. All public
sector invoices must be sent in the European Standard EN 16931 format through platforms such as
eInvoicing.lv, Latvias official e-invoicing infrastructure. Latvia is also connected to the Peppol
network, facilitating standardized cross-border e-invoicing across the European Union.
Compliance with Latvian e-invoicing regulations
===============================================
Odoo Invoicing is designed to help businesses comply with Latvia's specific e-invoicing
requirements. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the XML :abbr:`UBL (Universal Business Language)` format,
compliant with European Standard EN 16931, which is required for public sector e-invoicing in
Latvia. Odoo also facilitates e-invoicing through the Peppol network, ensuring seamless
cross-border compatibility. Odoo integrates with Latvian e-invoicing platforms, such as
eInvoicing.lv, allowing businesses to send compliant e-invoices directly to government entities
while adhering to legal standards.
- **Secure storage and retrieval**: In accordance with Latvian regulations requiring invoices to be
stored for a minimum of five years, Odoo securely archives all invoices in a tamper-proof system,
ensuring they can be easily accessed during audits or inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
invoices adhere to the legal requirements for :abbr:`B2G (business-to-government)` and B2B
transactions, helping businesses comply with Latvian VAT laws.
.. admonition:: Disclaimer
This page provides an overview of Latvian e-invoicing laws and how Odoo Invoicing supports
compliance with the Law on Accounting, European Standard EN 16931, eInvoicing.lv, Peppol
standards, and other relevant regulations. It does not constitute legal advice. We recommend
consulting with a tax advisor or legal professional familiar with Latvian e-invoicing regulations
to ensure compliance tailored to your specific business needs.
@@ -0,0 +1,46 @@
:orphan:
======================================
Odoo electronic invoicing in Lithuania
======================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Lithuania's regulatory standards.
Legal framework for e-invoicing in Lithuania
============================================
In Lithuania, e-invoicing is regulated under the `Law on Accounting <https://www.e-tar.lt/portal/lt/legalAct/207ad17030a011e78397ae072f58c508>`_
and aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_
for mandatory :abbr:`B2G (business-to-government)` e-invoicing. Businesses working with public
sector entities must use e-invoicing, and invoices must be submitted through the E.sąskaita
platform, Lithuanias centralized invoicing system for public procurement. Lithuania also
participates in the Peppol network, enabling seamless cross-border e-invoicing. While B2B
e-invoicing is currently optional, its use is encouraged to enhance tax compliance and operational
efficiency.
Compliance with Lithuanian e-invoicing regulations
==================================================
Odoo invoicing module is fully equipped to meet Lithuania's e-invoicing requirements and ensure
compliance with local and EU standards. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports Peppol BIS Billing 3.0 and XML formats required for
compliance with E.sąskaita, ensuring e-invoices meet the mandatory standards for public
procurement and cross-border transactions. Odoo enables businesses to send e-invoices directly to
public entities with Lithuanias E.sąskaita platform. For international invoicing, Odoo supports
the Peppol network.
- **Secure storage and retrieval**: In compliance with Lithuanian regulations, which require
invoices to be stored for a minimum of ten years, Odoo securely archives all invoices in a
tamper-proof system, ensuring they are accessible for audits and tax inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
invoices meet Lithuanias VAT requirements for both B2G and B2B transactions, reducing the risk of
non-compliance.
.. admonition:: Disclaimer
This page provides an overview of Lithuanian e-invoicing laws and how Odoo Invoicing supports
compliance with the Law on Accounting, E.sąskaita platform, Peppol standards, and other relevant
regulations. It does not constitute legal advice. We recommend consulting with a tax advisor or
legal professional familiar with Lithuanian e-invoicing regulations to ensure compliance tailored
to your specific business needs.
@@ -0,0 +1,47 @@
:orphan:
=======================================
Odoo electronic invoicing in Luxembourg
=======================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Luxembourg's regulatory standards.
Legal framework for e-invoicing in Luxembourg
=============================================
In Luxembourg, e-invoicing is regulated in accordance with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
requiring the use of electronic invoicing in :abbr:`B2G (business-to-government)` transactions.
Public sector entities in Luxembourg must accept e-invoices in the European Standard EN 16931
format. The government supports e-invoicing through the Peppol network, ensuring streamlined
communication and compliance for cross-border transactions. While e-invoicing is not yet mandatory
for B2B transactions, its adoption is encouraged to promote operational efficiency and tax
compliance across industries.
Compliance with Luxembourgish e-invoicing regulations
=====================================================
Odoo invoicing is equipped to support businesses in adhering to Luxembourg's e-invoicing standards.
Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the XML :abbr:`UBL (Universal Business Language)` format,
compliant with European Standard EN 16931, meeting the requirements for public sector e-invoicing
in Luxembourg. It also facilitates e-invoicing through the Peppol network, ensuring
interoperability for cross-border invoicing.
- **Secure storage and retrieval**: In line with Luxembourgs requirement to retain invoices for a
minimum of ten years, Odoo securely archives all invoices in a tamper-proof system, ensuring easy
access during audits or inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing ensures full compliance with
Luxembourg's VAT regulations by automating VAT calculations and formatting invoices to meet the
legal standards for :abbr:`B2G (business-to-government)` and B2B transactions.
.. seealso::
:doc:`Luxembourg fiscal localization documentation <../../../fiscal_localizations/luxembourg>`
.. admonition:: Disclaimer
This page provides an overview of Luxembourg's e-invoicing laws and how Odoo Invoicing supports
compliance with EU Directive 2014/55/EU, European Standard EN 16931, Peppol standards, and other
relevant regulations. It does not constitute legal advice. We recommend consulting with a tax
advisor or legal professional familiar with Luxembourgs e-invoicing regulations to ensure
compliance tailored to your specific business needs.
@@ -0,0 +1,46 @@
:orphan:
============================================
Odoo electronic invoicing in the Netherlands
============================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to the Netherlands' regulatory standards.
Legal framework for e-invoicing in the Netherlands
==================================================
In the Netherlands, e-invoicing is regulated under `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
requiring :abbr:`B2G (business-to-government)` transactions to adhere to the European Standard EN
16931. Public sector entities must accept e-invoices through platforms such as Digipoort, the Dutch
government's official gateway for electronic data exchange. The Netherlands is also a prominent
member of the Peppol network, which enables secure and standardized e-invoicing for cross-border
transactions across Europe. While e-invoicing is not yet mandatory for B2B transactions, it is
strongly encouraged to enhance transparency and efficiency in business processes.
Compliance with Dutch e-invoicing regulations
=============================================
Odoo invoicing is equipped to support businesses with the Netherlands' e-invoicing requirements.
Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports :abbr:`UBL (Universal Business Language)` XML, which is the
standard format for e-invoicing in the Netherlands. It ensures compatibility with both Digipoort
for domestic B2G transactions and the Peppol network for international e-invoicing.
- **Secure storage and retrieval**: In accordance with Dutch regulations, which require businesses
to store invoices for a minimum of seven years, Odoo securely archives all invoices in a
tamper-proof system, ensuring they are accessible during audits or inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and formats
invoices to meet Dutch VAT requirements, ensuring compliance with legal standards for both
:abbr:`B2G (business-to-government)` and B2B transactions.
.. seealso::
:doc:`Netherlands fiscal localization documentation <../../../fiscal_localizations/netherlands>`
.. admonition:: Disclaimer
This page provides an overview of Dutch e-invoicing laws and how Odoo Invoicing supports
compliance with EU Directive 2014/55/EU, Digipoort, Peppol standards, and other relevant
regulations. It does not constitute legal advice. We recommend consulting with a tax advisor or
legal professional familiar with Dutch e-invoicing regulations to ensure compliance tailored to
your specific business needs.
@@ -0,0 +1,44 @@
:orphan:
===================================
Odoo electronic invoicing in Norway
===================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Norway's regulatory standards.
Legal framework for e-invoicing in Norway
=========================================
In Norway, e-invoicing is governed by regulations aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
requiring :abbr:`B2G (business-to-government)` transactions to comply with mandatory e-invoicing
standards. Norwegian public sector entities mandate the use of the EHF (Elektronisk Handelsformat)
standard for e-invoices, ensuring uniformity and security. Norway is a member of the Peppol network,
which supports standardized and interoperable cross-border e-invoicing throughout Europe. Although
not mandatory for B2B transactions, e-invoicing is widely encouraged and adopted across the private
sector to boost efficiency, transparency, and compliance.
Compliance with Norwegian e-invoicing regulations
=================================================
Odoo invoicing is designed to fully support businesses in meeting Norway's e-invoicing standards.
Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the EHF (Elektronisk Handelsformat) standard, which is
required for public sector e-invoicing in Norway. Odoo is also compatible with :abbr:`UBL
(Universal Business Language)` XML for transactions through the Peppol network, ensuring adherence
to both Norwegian and EU e-invoicing requirements.
- **Secure storage and retrieval**: In compliance with Norwegian regulations that mandate the
retention of invoices for a minimum of five years, Odoo securely archives all invoices in a
tamper-proof system, ensuring accessibility and security during audits or inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations, ensuring
that invoices meet Norwegian VAT requirements while adhering to the correct format for both
:abbr:`B2G (business-to-government)` and B2B transactions.
.. admonition:: Disclaimer
This page provides an overview of Norwegian e-invoicing laws and how Odoo Invoicing supports
compliance with the EHF standard, Peppol network, and other relevant regulations. It does not
constitute legal advice. We recommend consulting with a tax advisor or legal professional
familiar with Norwegian e-invoicing regulations to ensure compliance tailored to your specific
business needs.
@@ -0,0 +1,45 @@
:orphan:
===================================
Odoo electronic invoicing in Poland
===================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Poland's regulatory standards.
Legal framework for e-invoicing in Poland
=========================================
In Poland, e-invoicing is governed by the `Polish VAT Act <https://isap.sejm.gov.pl/isap.nsf/DocDetails.xsp?id=WDU20230001598>`_
and the National e-Invoicing System (KSeF Krajowy System e-Faktur), which became operational in
2022. While :abbr:`B2G (business-to-government)` e-invoicing is mandatory under `EU Directive
2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_, B2B
e-invoicing is mandatory for all businesses starting July 2024, following Poland's adoption of the
e-invoicing scheme. E-invoices must be issued in the FA_VAT (structured XML) format and transmitted
through the KSeF platform, ensuring compliance with tax reporting and transparency goals.
Compliance with Polish e-invoicing regulations
==============================================
Odoo Invoicing is fully equipped to help businesses comply with Poland's evolving e-invoicing
requirements. Here is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the FA_VAT (structured XML) format required for submission to
the KSeF platform. It also supports Peppol BIS Billing 3.0 for cross-border transactions, ensuring
compliance with Polish and European standards. Odoo enables businesses to issue and transmit
structured e-invoices to public authorities and other businesses through the KSeF platform.
Additionally, Odoo facilitates cross-border invoicing through the Peppol network.
- **Secure storage and retrieval**: In accordance with Polish regulations, which require invoices to
be stored for at least five years, Odoo securely archives all invoices in a tamper-proof system,
ensuring easy access for audits and compliance checks.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
invoices meet Polish VAT requirements for both B2G and B2B transactions, streamlining compliance
and tax reporting processes.
.. admonition:: Disclaimer
This page provides an overview of Polish e-invoicing laws and how Odoo Invoicing supports
compliance with the VAT Act, KSeF platform, Peppol standards, and other relevant regulations. It
does not constitute legal advice. We recommend consulting with a tax advisor or legal
professional familiar with Polish e-invoicing regulations to ensure compliance tailored to your
specific business needs.
@@ -0,0 +1,48 @@
:orphan:
=====================================
Odoo electronic invoicing in Portugal
=====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Portugal's regulatory standards.
Legal framework for e-invoicing in Portugal
===========================================
In Portugal, e-invoicing is regulated under the Portuguese VAT Code and in compliance with `EU
Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_ for
:abbr:`B2G (business-to-government)` transactions. E-invoicing has been mandatory for public sector
suppliers since 2021. Businesses must use structured e-invoices in the :abbr:`CIUS-PT (Customizable
Invoice User Specification for Portugal)` format, which aligns with European standards. While B2B
e-invoicing is not yet mandatory, its adoption is encouraged to improve tax compliance and
efficiency. Additionally, e-invoices must be validated and certified under Portugal's SAF-T (PT)
system, which integrates with the tax authority for reporting.
Compliance with Portuguese e-invoicing regulations
==================================================
Odoo Invoicing is fully equipped to meet Portugal's e-invoicing and tax reporting requirements. Here
is how Odoo ensures compliance:
- **Supported formats**: Odoo supports the :abbr:`CIUS-PT (Customizable Invoice User Specification
for Portugal)` format, ensuring compatibility with Portugal's public procurement e-invoicing
requirements. For cross-border transactions, Odoo also supports the Peppol BIS Billing 3.0 format,
facilitating seamless compliance with EU standards. Integration with SAF-T (PT) and Tax Authority
Systems enables businesses to generate, validate, and report certified e-invoices to the tax
authority in compliance with local regulations.
- **Secure storage and retrieval**: In accordance with Portuguese regulations, which require
invoices to be stored for at least ten years, Odoo securely archives all invoices in a
tamper-proof system, ensuring they are accessible for audits and inspections.
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
that invoices meet Portuguese VAT requirements for both :abbr:`B2G (business-to-government)` and
B2B transactions, supporting efficient and accurate tax reporting.
.. admonition:: Disclaimer
This page provides an overview of Portuguese e-invoicing laws and how Odoo Invoicing supports
compliance with the VAT Code, :abbr:`CIUS-PT (Customizable Invoice User Specification for
Portugal)` format, SAF-T (PT) system, Peppol standards, and other relevant regulations. It does
not constitute legal advice. We recommend consulting with a tax advisor or legal professional
familiar with Portuguese e-invoicing regulations to ensure compliance tailored to your specific
business needs.
@@ -0,0 +1,54 @@
:orphan:
====================================
Odoo electronic invoicing in Romania
====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Romania's regulatory standards.
Legal framework for e-invoicing in Romania
==========================================
In Romania, e-invoicing is regulated under the `Fiscal Code <http://www.dreptonline.ro/carti/start_carte.php?id_carte=324>`_
and aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
which mandates e-invoicing for :abbr:`B2G (business-to-government)` transactions. Romania has
implemented the RO e-Factura system, the national platform for issuing and receiving electronic
invoices in a standardized format. The use of RO e-Factura is mandatory for :abbr:`B2G
(business-to-government)` transactions and for specific high-risk B2B sectors, with further
expansion anticipated. Romania is also integrated with the Peppol network, facilitating cross-border
e-invoicing and compliance within the European Union.
Compliance with Romanian e-invoicing regulations
================================================
Odoo invoicing module is fully equipped to help businesses comply with Romanias specific
e-invoicing requirements. Heres 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.
@@ -0,0 +1,45 @@
:orphan:
=====================================
Odoo electronic invoicing in Slovenia
=====================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Slovenia's regulatory standards.
Legal framework for e-invoicing in Slovenia
===========================================
In Slovenia, e-invoicing is regulated under the `Slovenian VAT Act <https://www.uradni-list.si/glasilo-uradni-list-rs/vsebina/2019-01-2291?sop=2019-01-2291>`_
and complies with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
mandating the use of e-invoices for :abbr:`B2G (business-to-government)` transactions. Suppliers to
public sector entities must submit e-invoices in the e-SLOG XML format, which is the national
standard for e-invoicing. These invoices are transmitted via the UJP (Uradni list Republike
Slovenije - Agency for Public Payments) e-invoicing platform. While B2B e-invoicing remains
optional, its adoption is encouraged to promote transparency and tax compliance.
Compliance with Slovenian e-invoicing regulations
=================================================
Odoo Invoicing is fully equipped to support businesses in meeting Slovenias 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 Slovenias 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.
@@ -0,0 +1,50 @@
:orphan:
==================================
Odoo electronic invoicing in Spain
==================================
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
solutions tailored to Spain's regulatory standards.
Legal framework for e-invoicing in Spain
========================================
In Spain, e-invoicing is governed by the `Ley de Facturación Electrónica <https://www.facturae.gob.es/face/Paginas/FACE.aspx>`_
and aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
mandating e-invoicing for :abbr:`B2G (business-to-government)` transactions. All invoices to public
sector entities must be submitted through the FACe platform, Spains 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.
@@ -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.
Lets 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 dont 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 projects 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:
Lets 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.
Binary file not shown.

Before

Width:  |  Height:  |  Size: 9.9 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.9 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 5.0 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.0 KiB

@@ -24,10 +24,8 @@ programming interface)` integration.
.. important::
Some limitations exist in Odoo while using AvaTax for tax calculation:
- AvaTax is **not** supported in Odoo's **Point of Sale** app, because a dynamic tax
calculation model is excessive for transactions within a single delivery address, such as
stores or restaurants.
- AvaTax and Odoo use the company address, **not** the warehouse address.
- AvaTax uses the company address by default. To use the warehouse address, enable :doc:`Allow
Ship Later <../../../sales/point_of_sale/shop/ship_later>` in the **POS** app settings.
- Excise tax is **not** supported. This includes tobacco/vape taxes, fuel taxes, and other
specific industries.
File diff suppressed because it is too large Load Diff
Binary file not shown.

Before

Width:  |  Height:  |  Size: 9.3 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 24 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 34 KiB

After

Width:  |  Height:  |  Size: 42 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 28 KiB

After

Width:  |  Height:  |  Size: 28 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 37 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.4 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.5 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 31 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 34 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 28 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 24 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 31 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 10 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 14 KiB

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 36 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 14 KiB

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 20 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 19 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 42 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 47 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 19 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 30 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 28 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 59 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 32 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 47 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 25 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 25 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 60 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 35 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 20 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 21 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 43 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 8.3 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 10 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 38 KiB

Some files were not shown because too many files have changed in this diff Show More