Compare commits
1 Commits
master-16.
...
master-doc
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
f0548c755b |
@@ -61,8 +61,8 @@ To resolve the issue:
|
||||
your **network and firewall settings** allow the Odoo server to open outgoing connections
|
||||
towards:
|
||||
|
||||
- Odoo 18.0 and above: `services.odoo.com` on port `80`
|
||||
- Odoo 17.0 and below: `services.openerp.com` on port `80`
|
||||
- Odoo 18.0 and above: `services.odoo.com` on port `443` (or `80`)
|
||||
- Odoo 17.0 and below: `services.openerp.com` on port `443` (or `80`)
|
||||
|
||||
These ports must be kept open even after registering a database, as the update notification runs
|
||||
once a week.
|
||||
@@ -85,6 +85,12 @@ To resolve the issue, either:
|
||||
displayed in the message to validate the upsell quotation and pay for the extra users.
|
||||
- :ref:`Deactivate users <users/deactivate>` and **reject** the upsell quotation.
|
||||
|
||||
.. important::
|
||||
If you are on a monthly subscription plan, the database will automatically update to reflect the
|
||||
added user(s). If you are on a yearly or multi-year plan, an expiration banner will appear in the
|
||||
database. You can create the upsell quotation by clicking the banner to update the subscription
|
||||
or `send a support ticket <https://www.odoo.com/help>`_ to resolve the issue.
|
||||
|
||||
Once your database has the correct number of users, the expiration message disappears automatically
|
||||
after a few days, when the next verification occurs.
|
||||
|
||||
|
||||
@@ -38,13 +38,13 @@ This matrix shows the support status of every version.
|
||||
- October 2024
|
||||
- October 2027 (planned)
|
||||
* - Odoo SaaS 17.4
|
||||
- |red|
|
||||
- |green|
|
||||
- N/A
|
||||
- N/A
|
||||
- July 2024
|
||||
-
|
||||
* - Odoo SaaS 17.2
|
||||
- |red|
|
||||
- |green|
|
||||
- N/A
|
||||
- N/A
|
||||
- April 2024
|
||||
|
||||
@@ -3,7 +3,7 @@ Upgrade
|
||||
=======
|
||||
|
||||
An upgrade involves moving a database from an older version to a newer supported version (e.g., from
|
||||
Odoo 16.0 to Odoo 18.0). Regular upgrades are crucial as each version offers new features, bug
|
||||
Odoo 15.0 to Odoo 17.0). Regular upgrades are crucial as each version offers new features, bug
|
||||
fixes, and security patches. Using a :doc:`supported version <supported_versions>` is strongly
|
||||
recommended. Each major version is supported for three years.
|
||||
|
||||
@@ -13,11 +13,11 @@ Depending on the hosting type and Odoo version used, a database upgrade can be *
|
||||
|
||||
.. group-tab:: Odoo Online
|
||||
|
||||
- If a database is on a **major version** (e.g., 16.0, 17.0, 18.0), an upgrade is mandatory
|
||||
- If a database is on a **major version** (e.g., 15.0, 16.0, 17.0), an upgrade is mandatory
|
||||
every two years.
|
||||
- If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade is mandatory
|
||||
a few weeks after the next version is released. Minor versions are usually released every
|
||||
two months.
|
||||
three months.
|
||||
|
||||
.. group-tab:: Odoo.sh
|
||||
|
||||
@@ -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 upgrade (production)"
|
||||
<https://www.odoo.com/help?stage=post_upgrade>`_.
|
||||
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>`_.
|
||||
|
||||
.. _upgrade-sla:
|
||||
|
||||
|
||||
@@ -28,13 +28,15 @@ select a record, tick the checkbox next to the corresponding record. Finally, cl
|
||||
then :guilabel:`Export`.
|
||||
|
||||
.. image:: export_import_data/list-view-export.png
|
||||
:align: center
|
||||
:alt: View of the different things to enable/click to export data.
|
||||
|
||||
When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over window appears, with
|
||||
several options for the data to export:
|
||||
|
||||
.. image:: export_import_data/export-data-overview.png
|
||||
:alt: Overview of options to consider when exporting data in Odoo.
|
||||
:align: center
|
||||
:alt: Overview of options to consider when exporting data in Odoo..
|
||||
|
||||
#. With the :guilabel:`I want to update data (import-compatable export)` option ticked, the system
|
||||
only shows the fields that can be imported. This is helpful in the case where the :ref:`existing
|
||||
@@ -85,6 +87,7 @@ data into an Odoo database.
|
||||
options: :guilabel:`Track history during import` and :guilabel:`Allow matching with subfields`.
|
||||
|
||||
.. image:: export_import_data/advanced-import.png
|
||||
:align: center
|
||||
:alt: Advanced import options when developer mode is activated.
|
||||
|
||||
If the model uses openchatter, the :guilabel:`Track history during import` option sets up
|
||||
@@ -93,8 +96,6 @@ data into an Odoo database.
|
||||
Should the :guilabel:`Allow matching with subfields` option be selected, then all subfields
|
||||
within a field are used to match under the :guilabel:`Odoo Field` while importing.
|
||||
|
||||
.. _essentials/export_import_data/get-started:
|
||||
|
||||
Get started
|
||||
-----------
|
||||
|
||||
@@ -102,32 +103,30 @@ Data can be imported on any Odoo business object using either Excel (`.xlsx`) or
|
||||
(Comma-separated Values)` (`.csv`) formats. This includes: contacts, products, bank statements,
|
||||
journal entries, and orders.
|
||||
|
||||
Open the view of the object to which the data should be imported/populated, click the :icon:`fa-cog`
|
||||
(:guilabel:`gear`) icon and select :guilabel:`Import records`.
|
||||
Open the view of the object to which the data should be imported/populated, and click on
|
||||
:menuselection:`⚙️ (Action) --> Import records`.
|
||||
|
||||
.. image:: export_import_data/import-button.png
|
||||
:align: center
|
||||
:alt: Action menu revealed with the import records option highlighted.
|
||||
|
||||
Click :icon:`fa-download`:guilabel:`Import Template for Customers` at the center of the page to
|
||||
download a :ref:`template <essentials/export_import_data/adapt-a-template>` and populate it with
|
||||
the company's own data. Such templates can be imported in one click since the data mapping is
|
||||
already preconfigured.
|
||||
After clicking :guilabel:`Import records`, Odoo reveals a separate page with templates that can be
|
||||
downloaded and populated with the company's own data. Such templates can be imported in one click,
|
||||
since the data mapping is already done. To download a template click :guilabel:`Import Template for
|
||||
Customers` at the center of the page.
|
||||
|
||||
To upload the downloaded template or your own file, follow the next steps:
|
||||
.. important::
|
||||
When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides :guilabel:`Formatting`
|
||||
options. These options do **not** appear when importing the proprietary Excel file type (`.xls`,
|
||||
`.xlsx`).
|
||||
|
||||
#. Click :guilabel:`Upload Data File` and select the desired file.
|
||||
#. Adjust the :guilabel:`Formatting` options as needed (for CSV files only).
|
||||
#. Ensure all data in the :guilabel:`File Column` is correctly mapped to the appropriate
|
||||
:guilabel:`Odoo Field` and free of errors.
|
||||
#. (Optional) Click :guilabel:`Load Data File` to reload the same file or upload a different one.
|
||||
#. Click :guilabel:`Test` to verify that the data is valid.
|
||||
#. Click :guilabel:`Import`.
|
||||
.. image:: export_import_data/formatting.png
|
||||
:align: center
|
||||
:alt: Formatting options presented when a CVS file is imported in Odoo.
|
||||
|
||||
.. note::
|
||||
The :guilabel:`Formatting` options do **not** appear when importing the proprietary Excel file
|
||||
type (i.e., `.xls` or `.xlsx`).
|
||||
|
||||
.. _essentials/export_import_data/adapt-a-template:
|
||||
Make necessary adjustments to the *Formatting* options, and ensure all columns in the
|
||||
:guilabel:`Odoo field` and :guilabel:`File Column` are free of errors. Finally, click
|
||||
:guilabel:`Import` to import the data.
|
||||
|
||||
Adapt a template
|
||||
----------------
|
||||
@@ -145,6 +144,7 @@ Once the template is downloaded, proceed to follow these steps:
|
||||
(ID) column.
|
||||
|
||||
.. image:: export_import_data/dragdown.gif
|
||||
:align: center
|
||||
:alt: An animation of the mouse dragging down the ID column, so each record has a unique ID.
|
||||
|
||||
.. note::
|
||||
@@ -153,6 +153,7 @@ Once the template is downloaded, proceed to follow these steps:
|
||||
Search the drop-down menu for the corresponding field.
|
||||
|
||||
.. image:: export_import_data/field_list.png
|
||||
:align: center
|
||||
:alt: Drop-down menu expanded in the initial import screen on Odoo.
|
||||
|
||||
Then, use this field's label in the import file to ensure future imports are successful.
|
||||
@@ -202,6 +203,7 @@ If this happens, check the :guilabel:`Show fields of relation fields (advanced)
|
||||
complete list of fields becomes available for each column.
|
||||
|
||||
.. image:: export_import_data/field_list.png
|
||||
:align: center
|
||||
:alt: Searching for the field to match the tax column.
|
||||
|
||||
Change data import format
|
||||
@@ -399,33 +401,6 @@ respective contacts:
|
||||
- :download:`Customers and their respective contacts
|
||||
<export_import_data/o2m_customers_contacts.csv>`
|
||||
|
||||
Import image files
|
||||
------------------
|
||||
|
||||
To import image files along with the :ref:`uploaded <essentials/export_import_data/get-started>`
|
||||
CSV or Excel file, follow the next steps:
|
||||
|
||||
#. Add the image file names to the relevant :guilabel:`Image` column in the data file.
|
||||
#. :ref:`Upload the data file <essentials/export_import_data/get-started>` or reload it by
|
||||
clicking :guilabel:`Load Data File`.
|
||||
#. Click :guilabel:`Upload your files` under the :guilabel:`Files to import` section.
|
||||
#. Select the relevant image files. The number of files selected appears next to the button.
|
||||
#. Click :guilabel:`Test` to verify that all data is valid.
|
||||
#. Click :guilabel:`Import`. During the import process, Odoo performs a file check to automatically
|
||||
link the uploaded images to the imported data file. If there is no match, the data file is
|
||||
imported without any image.
|
||||
|
||||
.. note::
|
||||
- The :guilabel:`Files to import` section is enabled if your product template has an
|
||||
:guilabel:`Image` column with all fields populated.
|
||||
- The image file names in the data file must correspond to the uploaded image files.
|
||||
- When importing a large number of images, you can specify the maximum batch size in megabytes
|
||||
and set a delay to prevent the system from becoming overloaded. To do so, :doc:`enable the
|
||||
developer mode <../general/developer_mode>` and fill in the :guilabel:`Max size per
|
||||
batch` and the :guilabel:`Delay after each batch` fields in the :guilabel:`Files to import`
|
||||
section. By default, the delay meets the RPC/API call limit defined in the `Odoo Cloud -
|
||||
Acceptable Use Policy <https://www.odoo.com/acceptable-use>`_.
|
||||
|
||||
Import records several times
|
||||
----------------------------
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ To check if your bank is compatible with Odoo, go to `Odoo Accounting Features
|
||||
<https://www.odoo.com/page/accounting-features>`_, and click on
|
||||
:guilabel:`See list of supported institutions`.
|
||||
|
||||
Odoo supports more than 26,000 institutions around the world.
|
||||
Odoo supports more than 25,000 institutions around the world.
|
||||
|
||||
To connect to the banks, Odoo uses multiple web-services:
|
||||
|
||||
|
||||
@@ -4,251 +4,225 @@
|
||||
Customer invoices
|
||||
=================
|
||||
|
||||
A customer invoice is a document issued by a company for products and/or services sold to a
|
||||
customer. It records receivables as they are sent to customers. Customer invoices can include
|
||||
amounts due for the goods and/or services provided, applicable sales taxes, shipping and handling
|
||||
fees, and other charges.
|
||||
Odoo supports multiple invoicing and payment workflows.
|
||||
From Customer Invoice to Payments Collection
|
||||
============================================
|
||||
|
||||
.. seealso::
|
||||
:doc:`/applications/finance/accounting/customer_invoices/overview`
|
||||
Odoo supports multiple invoicing and payment workflows, so you can
|
||||
choose and use the ones that match your business needs. Whether you want
|
||||
to accept a single payment for a single invoice, or process a payment
|
||||
spanning multiple invoices and taking discounts for early payments, you
|
||||
can do so efficiently and accurately.
|
||||
|
||||
From draft invoice to profit and loss report, the process involves several steps once the goods (or
|
||||
services) have been ordered/shipped (or rendered) to a customer, depending on the invoicing policy:
|
||||
From Draft Invoice to Profit and Loss
|
||||
-------------------------------------
|
||||
|
||||
- :ref:`accounting/invoice/creation`
|
||||
- :ref:`accounting/invoice/confirmation`
|
||||
- :ref:`accounting/invoice/sending`
|
||||
- :ref:`accounting/invoice/paymentandreconciliation`
|
||||
- :ref:`accounting/invoice/followup`
|
||||
- :ref:`accounting/invoice/reporting`
|
||||
If we pick up at the end of a typical 'order to cash' scenario, after
|
||||
the goods have been shipped, you will: issue an invoice; receive
|
||||
payment; deposit that payment at the bank; make sure the Customer
|
||||
Invoice is closed; follow up if Customers are late; and finally present
|
||||
your Income on the Profit and Loss report and show the decrease in
|
||||
Assets on the Balance Sheet report.
|
||||
|
||||
.. _accounting/invoice/creation:
|
||||
Invoicing in most countries occurs when a contractual obligation is met.
|
||||
If you ship a box to a customer, you have met the terms of the contract
|
||||
and can bill them. If your supplier sends you a shipment, they have met
|
||||
the terms of that contract and can bill you. Therefore, the terms of the
|
||||
contract is fulfilled when the box moves to or from the truck. At this
|
||||
point, Odoo supports the creation of what is called a Draft Invoice by
|
||||
Warehouse staff.
|
||||
|
||||
Invoice creation
|
||||
================
|
||||
----------------
|
||||
|
||||
Draft invoices can be created directly from documents like sales orders or purchase orders or
|
||||
manually from the :guilabel:`Customer Invoices` journal in the :guilabel:`Accounting Dashboard`.
|
||||
Draft invoices can be manually generated from other documents such as
|
||||
Sales Orders, Purchase Orders,etc. Although you can create a draft
|
||||
invoice directly if you would like.
|
||||
|
||||
An invoice must include the required information to enable the customer to pay promptly for their
|
||||
goods and services. Make sure the following fields are appropriately completed:
|
||||
An invoice must be provided to the customer with the necessary
|
||||
information in order for them to pay for the goods and services ordered
|
||||
and delivered. It must also include other information needed to pay the
|
||||
invoice in a timely and precise manner.
|
||||
|
||||
- :guilabel:`Customer`: When a customer is selected, Odoo automatically pulls information from the
|
||||
customer record like the invoice address,
|
||||
:doc:`preferred payment terms <customer_invoices/payment_terms>`,
|
||||
:doc:`fiscal positions <taxes/fiscal_positions>`, receivable account, and more onto the invoice.
|
||||
To change these values for this specific invoice, edit them directly on the invoice. To change
|
||||
them for future invoices, change the values on the contact record.
|
||||
- :guilabel:`Invoice Date`: If not set manually, this field is automatically set as the current date
|
||||
upon confirmation.
|
||||
- :guilabel:`Due Date` or :doc:`payment terms <customer_invoices/payment_terms>`: To specify when
|
||||
the customer has to pay the invoice.
|
||||
- :guilabel:`Journal`: Is automatically set and can be changed if needed.
|
||||
- :doc:`Currency <get_started/multi_currency>`
|
||||
- :guilabel:`Product`: Click :guilabel:`Add a line` to add a product.
|
||||
- :guilabel:`Quantity`
|
||||
- :guilabel:`Price`
|
||||
- :doc:`Taxes <taxes>` (if applicable)
|
||||
Draft invoices
|
||||
--------------
|
||||
|
||||
.. tip::
|
||||
To display the total amount of the invoice in words, go to :menuselection:`Accounting -->
|
||||
Configuration --> Settings` and activate the :guilabel:`Total amount of invoice in letters`
|
||||
option.
|
||||
The system generates invoice which are initially set to the Draft state.
|
||||
While these invoices remain unvalidated, they have no accounting impact within the system.
|
||||
There is nothing to stop users from creating their own draft invoices.
|
||||
|
||||
The :guilabel:`Journal Items` tab displays the accounting entries created.
|
||||
Additional invoice information such as the :guilabel:`Customer Reference`, :doc:`Fiscal Positions
|
||||
<taxes/fiscal_positions>`, :doc:`Incoterms <customer_invoices/incoterms>`, and more can be added or
|
||||
modified in the :guilabel:`Other Info` tab.
|
||||
Let's create a customer invoice with following information:
|
||||
|
||||
.. note::
|
||||
Odoo initially creates invoices in :guilabel:`Draft` status. Draft invoices have no accounting
|
||||
impact until they are :ref:`confirmed <accounting/invoice/confirmation>`.
|
||||
- Customer: Agrolait
|
||||
- Product: iMac
|
||||
- Quantity: 1
|
||||
- Unit Price: 100
|
||||
- Taxes: Tax 15%
|
||||
|
||||
.. seealso::
|
||||
:doc:`/applications/sales/sales/invoicing/proforma`
|
||||
.. image:: customer_invoices/invoice01.png
|
||||
|
||||
.. _accounting/invoice/confirmation:
|
||||
.. image:: customer_invoices/invoice02.png
|
||||
|
||||
Invoice confirmation
|
||||
====================
|
||||
The document is composed of three parts:
|
||||
|
||||
Click :guilabel:`Confirm` when the document is completed. The document's status changes to
|
||||
:guilabel:`Posted`, and a journal entry is generated based on the invoice configuration. On
|
||||
confirmation, Odoo assigns each document a unique number from a defined
|
||||
:ref:`sequence <accounting/invoice/sequence>`.
|
||||
- the top of the invoice, with customer information,
|
||||
- the main body of the invoice, with detailed invoice lines,
|
||||
- the bottom of the page, with detail about the taxes, and the totals.
|
||||
|
||||
.. note::
|
||||
- Once confirmed, an invoice can no longer be updated. Click :guilabel:`Reset to draft` if
|
||||
changes are needed.
|
||||
- If required, invoices and other journal entries can be locked once posted
|
||||
using the :ref:`Secure posted entries with hash <data-inalterability/restricted>` feature.
|
||||
Open or Pro-forma invoices
|
||||
--------------------------
|
||||
|
||||
.. _accounting/invoice/sending:
|
||||
An invoice will usually include the quantity and the price of goods
|
||||
and/or services, the date, any parties involved, the unique invoice
|
||||
number, and any tax information.
|
||||
|
||||
Invoice sending
|
||||
===============
|
||||
"Validate" the invoice when you are ready to approve it. The invoice
|
||||
then moves from the Draft state to the Open state.
|
||||
|
||||
To send the invoice to the customer, click :guilabel:`Send & Print`. A :guilabel:`Configure your
|
||||
document layout` pop-up window will appear if a :ref:`default invoice layout
|
||||
<studio/pdf-reports/default-layout>` hasn't been customized. Then, select how to send this invoice
|
||||
to the customer in the :guilabel:`Send` window.
|
||||
When you have validated an invoice, Odoo gives it a unique number from a
|
||||
defined, and modifiable, sequence.
|
||||
|
||||
To send and print multiple invoices, go to :menuselection:`Accounting --> Customers --> Invoices`
|
||||
and select them. Then click the :icon:`fa-cog` :guilabel:`Actions` menu and select
|
||||
:guilabel:`Send & Print`. A banner will appear on the selected invoices to indicate they are part of
|
||||
an ongoing send and print batch. This helps prevent the process from being triggered manually again,
|
||||
as it may take some time to complete for exceptionally large batches.
|
||||
.. image:: customer_invoices/invoice03.png
|
||||
|
||||
.. _accounting/invoice/paymentandreconciliation:
|
||||
Accounting entries corresponding to this invoice are automatically
|
||||
generated when you validate the invoice. You can see the details by
|
||||
clicking on the entry in the Journal Entry field in the "Other Info"
|
||||
tab.
|
||||
|
||||
Payment and reconciliation
|
||||
==========================
|
||||
.. image:: customer_invoices/invoice04.png
|
||||
|
||||
In Odoo, an invoice is considered :guilabel:`Paid` when the associated accounting entry has been
|
||||
reconciled with a corresponding bank transaction.
|
||||
Send the invoice to customer
|
||||
----------------------------
|
||||
|
||||
.. seealso::
|
||||
- :doc:`payments`
|
||||
- :doc:`bank/reconciliation`
|
||||
After validating the customer invoice, you can directly send it to the
|
||||
customer via the 'Send by email' functionality.
|
||||
|
||||
.. _accounting/invoice/followup:
|
||||
.. image:: customer_invoices/invoice05.png
|
||||
|
||||
Payment follow-up
|
||||
=================
|
||||
A typical journal entry generated from a validated invoice will look
|
||||
like as follows:
|
||||
|
||||
Odoo's :doc:`follow-up actions <payments/follow_up>` help companies follow up on customer invoices.
|
||||
Different actions can be set up to remind customers to pay their outstanding invoices, depending on
|
||||
how much the customer is overdue. These actions are bundled into follow-up levels that trigger when
|
||||
an invoice is overdue by a certain number of days. If there are multiple overdue invoices for the
|
||||
same customer, the actions are performed on the most overdue invoice.
|
||||
+-----------------------+---------------+----------------+-------------+--------------+
|
||||
| **Account** | **Partner** | **Due date** | **Debit** | **Credit** |
|
||||
+=======================+===============+================+=============+==============+
|
||||
| Accounts Receivable | Agrolait | 01/07/2015 | 115 | |
|
||||
+-----------------------+---------------+----------------+-------------+--------------+
|
||||
| Taxes | Agrolait | | | 15 |
|
||||
+-----------------------+---------------+----------------+-------------+--------------+
|
||||
| Sales | | | | 100 |
|
||||
+-----------------------+---------------+----------------+-------------+--------------+
|
||||
|
||||
.. _accounting/invoice/sequence:
|
||||
Payment
|
||||
-------
|
||||
|
||||
Sequence
|
||||
========
|
||||
In Odoo, an invoice is considered to be paid when the associated
|
||||
accounting entry has been reconciled with the payment entries. If there
|
||||
has not been a reconciliation, the invoice will remain in the Open state
|
||||
until you have entered the payment.
|
||||
|
||||
The sequence that Odoo assigns to each document is a unique number made up of a prefix and a number.
|
||||
The prefix combines the journal code and the entry date and is used to group entries by period. The
|
||||
number is unique for each period and is used to identify the entry. The default sequence on customer
|
||||
invoices is INV/YYYY/number. In some specific cases,
|
||||
:ref:`resequencing <accounting/invoice/resequencing>` invoices might be necessary.
|
||||
A typical journal entry generated from a payment will look like as
|
||||
follows:
|
||||
|
||||
.. _accounting/invoice/resequencing:
|
||||
+-----------------------+---------------+----------------+-------------+--------------+
|
||||
| **Account** | **Partner** | **Due date** | **Debit** | **Credit** |
|
||||
+=======================+===============+================+=============+==============+
|
||||
| Bank | Agrolait | | 115 | |
|
||||
+-----------------------+---------------+----------------+-------------+--------------+
|
||||
| Accounts Receivable | Agrolait | | | 115 |
|
||||
+-----------------------+---------------+----------------+-------------+--------------+
|
||||
|
||||
Resequencing
|
||||
------------
|
||||
Receive a partial payment through the bank statement
|
||||
----------------------------------------------------
|
||||
|
||||
Resequencing is not possible:
|
||||
You can manually enter your bank statements in Odoo, or you can import
|
||||
them in from a csv file or from several other predefined formats
|
||||
according to your accounting localisation.
|
||||
|
||||
- When entries are before a lock date.
|
||||
- When the sequence leads to a duplicate.
|
||||
- When the :guilabel:`Invoice Date` doesn't match the date contained in the new sequence number,
|
||||
e.g., if the sequence is changed to INV/2023/XXXXX for a document with an :guilabel:`Invoice Date`
|
||||
of 2024.
|
||||
Create a bank statement from the accounting dashboard with the related
|
||||
journal and enter an amount of $100 .
|
||||
|
||||
To change the invoice sequence with the structure INV/YYYY/MM/number, add `/MM` with the number of
|
||||
the month of the :guilabel:`Invoice date`. Odoo will recognize the "/" term as a month and update
|
||||
the future invoice sequence appropriately with the month of the :guilabel:`Invoice date`. For
|
||||
example, if the invoice date is January, change the sequence to `INV/2024/01/XXXXX`.
|
||||
.. image:: customer_invoices/invoice06.png
|
||||
|
||||
In this case, if the :guilabel:`Invoice date` isn't aligned with the sequence number, a
|
||||
:guilabel:`Validation Error` message appears.
|
||||
Reconcile
|
||||
---------
|
||||
|
||||
.. note::
|
||||
Now let's reconcile!
|
||||
|
||||
- All sequence changes are logged in the chatter to keep the information.
|
||||
- Sequence changes also affect the format of future invoices' sequences.
|
||||
.. image:: customer_invoices/invoice07.png
|
||||
|
||||
.. _accounting/invoice/resequencing-one-invoice:
|
||||
You can now go through every transaction and reconcile them or you can mass reconcile with instructions at the bottom.
|
||||
|
||||
Resequencing a single invoice
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
After reconciling the items in the sheet, the related invoice will now
|
||||
display "You have outstanding payments for this customer. You can
|
||||
reconcile them to pay this invoice. "
|
||||
|
||||
To resequence the last confirmed invoice, click :guilabel:`Reset to Draft`, then change the
|
||||
sequence. The invoice now appears in red on the :guilabel:`Customer Invoices` list.
|
||||
.. image:: customer_invoices/invoice08.png
|
||||
|
||||
.. _accounting/invoice/mass-resequencing:
|
||||
.. image:: customer_invoices/invoice09.png
|
||||
|
||||
Mass-resequencing invoices
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
Apply the payment. Below, you can see that the payment has been added to
|
||||
the invoice.
|
||||
|
||||
It can be helpful to resequence multiple invoice numbers. For example, when importing invoices from
|
||||
another invoicing or accounting system and the reference originates from the previous software,
|
||||
continuity for the current year must be maintained without restarting from the beginning.
|
||||
.. image:: customer_invoices/invoice10.png
|
||||
|
||||
.. note::
|
||||
This feature is only available to users with administrator or advisor access.
|
||||
Payment Followup
|
||||
----------------
|
||||
|
||||
Follow these steps to resequence invoice numbers:
|
||||
There's a growing trend of customers paying bills later and later.
|
||||
Therefore, collectors must make every effort to collect money and
|
||||
collect it faster.
|
||||
|
||||
#. Activate the :ref:`developer mode <developer-mode>`.
|
||||
#. From the :guilabel:`Accounting Dashboard`, open the :guilabel:`Customer Invoices` journal.
|
||||
#. Select the invoices that need a new sequence.
|
||||
#. Click the :icon:`fa-cog` :guilabel:`Actions` menu and select :guilabel:`Resequence`.
|
||||
#. In the :guilabel:`Ordering` field, choose to
|
||||
Odoo will help you define your follow-up strategy. To remind customers
|
||||
to pay their outstanding invoices, you can define different actions
|
||||
depending on how severely overdue the customer is. These actions are
|
||||
bundled into follow-up levels that are triggered when the due date of an
|
||||
invoice has passed a certain number of days. If there are other overdue
|
||||
invoices for the same customer, the actions of the most overdue invoice
|
||||
will be executed.
|
||||
|
||||
- :guilabel:`Keep current order`: The order of the numbers remains the same.
|
||||
- :guilabel:`Reorder by accounting date`: The number is reordered by accounting date.
|
||||
#. Set the :guilabel:`First New Sequence`.
|
||||
#. :guilabel:`Preview Modifications` and click :guilabel:`Confirm`.
|
||||
By going to the customer record and diving into the "Overdue Payments"
|
||||
you will see the follow-up message and all overdue invoices.
|
||||
|
||||
The first invoice using the new sequence appears in red in the :guilabel:`Customer Invoices` list.
|
||||
.. image:: customer_invoices/invoice11.png
|
||||
|
||||
.. image:: customer_invoices/invoice-sequencing.png
|
||||
:alt: Resequence options window
|
||||
.. image:: customer_invoices/invoice12.png
|
||||
|
||||
.. _accounting/invoice/reporting:
|
||||
.. _customer-invoices/aging-report:
|
||||
|
||||
Reporting
|
||||
=========
|
||||
Customer aging report:
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. _accounting/invoice/partner-reports:
|
||||
The customer aging report will be an additional key tool for the
|
||||
collector to understand the customer credit issues, and to prioritize
|
||||
their work.
|
||||
|
||||
Partner reports
|
||||
Use the aging report to determine which customers are overdue and begin
|
||||
your collection efforts.
|
||||
|
||||
.. image:: customer_invoices/invoice13.png
|
||||
|
||||
Profit and loss
|
||||
---------------
|
||||
|
||||
.. _accounting/invoices/partner-ledger:
|
||||
The Profit and Loss statement displays your revenue and expense details.
|
||||
Ultimately, this gives you a clear image of your Net Profit and Loss. It
|
||||
is sometimes referred to as the "Income Statement" or "Statement of
|
||||
Revenues and Expenses."
|
||||
|
||||
Partner Ledger
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
The :guilabel:`Partner Ledger` report shows the balance of customers and suppliers. To access it,
|
||||
go to :menuselection:`Accounting --> Reporting --> Partner Ledger`.
|
||||
|
||||
.. _accounting/invoices/aging-report:
|
||||
|
||||
Aged Receivable
|
||||
~~~~~~~~~~~~~~~
|
||||
|
||||
To review outstanding customer invoices and their related due dates, use the
|
||||
:ref:`Aged Receivable <accounting/reporting/aged-receivable>` report. To access it, go to
|
||||
:menuselection:`Accounting --> Reporting --> Aged Receivable`.
|
||||
|
||||
.. _accounting/invoices/aged-payable:
|
||||
|
||||
Aged Payable
|
||||
~~~~~~~~~~~~
|
||||
|
||||
To review outstanding vendor bills and their related due dates, use the
|
||||
:ref:`Aged Payable <accounting/reporting/aged-payable>` report. To access it, go to
|
||||
:menuselection:`Accounting --> Reporting --> Aged Payable`.
|
||||
|
||||
.. _accounting/invoices/profit-and-loss:
|
||||
|
||||
Profit and Loss
|
||||
---------------
|
||||
|
||||
The :ref:`Profit and Loss <accounting/reporting/profit-and-loss>` statement shows details of income
|
||||
and expenses.
|
||||
|
||||
.. _accounting/invoices/balance-sheet:
|
||||
.. image:: customer_invoices/invoice14.png
|
||||
|
||||
Balance sheet
|
||||
-------------
|
||||
|
||||
The :ref:`Balance Sheet <accounting/reporting/balance-sheet>` summarizes the company's assets,
|
||||
liabilities, and equity at a specific time.
|
||||
The balance sheet summarizes your company's liabilities,
|
||||
assets and equity at a specific moment in time.
|
||||
|
||||
.. image:: customer_invoices/invoice15.png
|
||||
|
||||
.. image:: customer_invoices/invoice16.png
|
||||
|
||||
For example, if you manage your inventory using the perpetual accounting
|
||||
method, you should expect a decrease in account "Current Assets" once
|
||||
the material has been shipped to the customer.
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
@@ -13,33 +13,49 @@ some governments for fiscal control or to facilitate the administration.
|
||||
Electronic invoicing of your documents such as customer invoices, credit notes or vendor bills is
|
||||
one of the application of EDI.
|
||||
|
||||
Odoo supports e-invoicing in many countries. Refer to the country's page for more details:
|
||||
Odoo supports, among others, the following formats.
|
||||
|
||||
- :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>`
|
||||
.. 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.
|
||||
|
||||
.. seealso::
|
||||
:doc:`Fiscal localizations documentation <../../fiscal_localizations>`
|
||||
:doc:`../../fiscal_localizations`
|
||||
|
||||
.. _e-invoicing/configuration:
|
||||
|
||||
|
||||
@@ -1,52 +0,0 @@
|
||||
: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.
|
||||
@@ -1,50 +0,0 @@
|
||||
: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.
|
||||
@@ -1,53 +0,0 @@
|
||||
: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 Belgium’s 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.
|
||||
@@ -1,50 +0,0 @@
|
||||
: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)`, Croatia’s 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.
|
||||
@@ -1,47 +0,0 @@
|
||||
: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 Denmark’s and Europe’s 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 Denmark’s 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.
|
||||
@@ -1,47 +0,0 @@
|
||||
: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 Rik’s 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 Denmark’s 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.
|
||||
@@ -1,47 +0,0 @@
|
||||
: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, Finland’s 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.
|
||||
@@ -1,50 +0,0 @@
|
||||
: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 France’s 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.
|
||||
@@ -1,47 +0,0 @@
|
||||
: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 Germany’s 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.
|
||||
@@ -1,46 +0,0 @@
|
||||
: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.
|
||||
@@ -1,46 +0,0 @@
|
||||
: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.
|
||||
@@ -1,50 +0,0 @@
|
||||
: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.
|
||||
@@ -1,45 +0,0 @@
|
||||
: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, Latvia’s 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.
|
||||
@@ -1,46 +0,0 @@
|
||||
: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, Lithuania’s 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 Lithuania’s 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 Lithuania’s 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.
|
||||
@@ -1,47 +0,0 @@
|
||||
: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 Luxembourg’s 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 Luxembourg’s e-invoicing regulations to ensure
|
||||
compliance tailored to your specific business needs.
|
||||
@@ -1,46 +0,0 @@
|
||||
: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.
|
||||
@@ -1,44 +0,0 @@
|
||||
: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.
|
||||
@@ -1,45 +0,0 @@
|
||||
: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.
|
||||
@@ -1,48 +0,0 @@
|
||||
: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.
|
||||
@@ -1,54 +0,0 @@
|
||||
:orphan:
|
||||
|
||||
====================================
|
||||
Odoo electronic invoicing in Romania
|
||||
====================================
|
||||
|
||||
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
|
||||
solutions tailored to Romania's regulatory standards.
|
||||
|
||||
Legal framework for e-invoicing in Romania
|
||||
==========================================
|
||||
|
||||
In Romania, e-invoicing is regulated under the `Fiscal Code <http://www.dreptonline.ro/carti/start_carte.php?id_carte=324>`_
|
||||
and aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
|
||||
which mandates e-invoicing for :abbr:`B2G (business-to-government)` transactions. Romania has
|
||||
implemented the RO e-Factura system, the national platform for issuing and receiving electronic
|
||||
invoices in a standardized format. The use of RO e-Factura is mandatory for :abbr:`B2G
|
||||
(business-to-government)` transactions and for specific high-risk B2B sectors, with further
|
||||
expansion anticipated. Romania is also integrated with the Peppol network, facilitating cross-border
|
||||
e-invoicing and compliance within the European Union.
|
||||
|
||||
Compliance with Romanian e-invoicing regulations
|
||||
================================================
|
||||
|
||||
Odoo invoicing module is fully equipped to help businesses comply with Romania’s specific
|
||||
e-invoicing requirements. Here’s how Odoo supports compliance:
|
||||
|
||||
- **Supported formats**: Odoo supports XML in :abbr:`UBL (Universal Business Language)` and the
|
||||
structured formats required by RO e-Factura, ensuring compliance with Romania's e-invoicing
|
||||
standards for B2G and high-risk B2B transactions. Additionally, Odoo supports formats compatible
|
||||
with the Peppol network, enabling seamless cross-border invoicing. Odoo integrates with the RO
|
||||
e-Factura system, allowing businesses to generate, validate, and submit e-invoices directly to
|
||||
Romanian public authorities or private entities as required by law. Odoo helps businesses comply
|
||||
with eTransport requirements by generating and managing the data necessary for reporting the
|
||||
movement of high-fiscal risk goods. This includes shipment details such as the nature of the
|
||||
goods, vehicle information, and delivery destinations, ensuring timely submission to the
|
||||
:abbr:`ANAF (Romanian National Agency for Fiscal Administration)`.
|
||||
- **Secure storage and retrieval**: In compliance with Romanian regulations, which require invoices
|
||||
to be stored for a minimum of ten years, Odoo securely archives all invoices in a tamper-proof
|
||||
system, ensuring accessibility during audits or inspections.
|
||||
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and formats
|
||||
invoices to comply with Romanian VAT requirements, ensuring accuracy and adherence to legal
|
||||
standards for both :abbr:`B2G (business-to-government)` and B2B transactions.
|
||||
|
||||
.. seealso::
|
||||
:doc:`Romania fiscal localization documentation <../../../fiscal_localizations/romania>`
|
||||
|
||||
.. admonition:: Disclaimer
|
||||
|
||||
This page provides an overview of Romanian e-invoicing laws and how Odoo Invoicing supports
|
||||
compliance with the Fiscal Code, RO e-Factura, Peppol standards, and other relevant regulations.
|
||||
It does not constitute legal advice. We recommend consulting with a tax advisor or legal
|
||||
professional familiar with Romanian e-invoicing regulations to ensure compliance tailored to your
|
||||
specific business needs.
|
||||
@@ -1,45 +0,0 @@
|
||||
:orphan:
|
||||
|
||||
=====================================
|
||||
Odoo electronic invoicing in Slovenia
|
||||
=====================================
|
||||
|
||||
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
|
||||
solutions tailored to Slovenia's regulatory standards.
|
||||
|
||||
Legal framework for e-invoicing in Slovenia
|
||||
===========================================
|
||||
|
||||
In Slovenia, e-invoicing is regulated under the `Slovenian VAT Act <https://www.uradni-list.si/glasilo-uradni-list-rs/vsebina/2019-01-2291?sop=2019-01-2291>`_
|
||||
and complies with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
|
||||
mandating the use of e-invoices for :abbr:`B2G (business-to-government)` transactions. Suppliers to
|
||||
public sector entities must submit e-invoices in the e-SLOG XML format, which is the national
|
||||
standard for e-invoicing. These invoices are transmitted via the UJP (Uradni list Republike
|
||||
Slovenije - Agency for Public Payments) e-invoicing platform. While B2B e-invoicing remains
|
||||
optional, its adoption is encouraged to promote transparency and tax compliance.
|
||||
|
||||
Compliance with Slovenian e-invoicing regulations
|
||||
=================================================
|
||||
|
||||
Odoo Invoicing is fully equipped to support businesses in meeting Slovenia’s e-invoicing
|
||||
requirements. Here is how Odoo ensures compliance:
|
||||
|
||||
- **Supported formats**: Odoo supports the e-SLOG XML format, enabling businesses to comply with
|
||||
public procurement requirements in Slovenia. For cross-border transactions, Odoo also supports the
|
||||
Peppol BIS Billing 3.0 format, ensuring compliance with EU standards. Odoo allows businesses to
|
||||
send e-invoices directly to public entities in compliance with national e-invoicing regulations
|
||||
through Slovenia’s UJP platform.
|
||||
- **Secure storage and retrieval**: In line with Slovenian regulations, which require invoices to be
|
||||
stored for a minimum of ten years, Odoo securely archives all invoices in a tamper-proof system,
|
||||
ensuring they are easily accessible for audits and inspections.
|
||||
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
|
||||
invoices meet Slovenian VAT requirements for both B2G and B2B transactions, simplifying tax
|
||||
reporting and ensuring accuracy.
|
||||
|
||||
.. admonition:: Disclaimer
|
||||
|
||||
This page provides an overview of Slovenian e-invoicing laws and how Odoo Invoicing supports
|
||||
compliance with the VAT Act, e-SLOG XML format, UJP platform, Peppol standards, and other
|
||||
relevant regulations. It does not constitute legal advice. We recommend consulting with a tax
|
||||
advisor or legal professional familiar with Slovenian e-invoicing regulations to ensure
|
||||
compliance tailored to your specific business needs.
|
||||
@@ -1,50 +0,0 @@
|
||||
:orphan:
|
||||
|
||||
==================================
|
||||
Odoo electronic invoicing in Spain
|
||||
==================================
|
||||
|
||||
Odoo Invoicing is your trusted partner for safe, efficient, and legally compliant e-invoicing
|
||||
solutions tailored to Spain's regulatory standards.
|
||||
|
||||
Legal framework for e-invoicing in Spain
|
||||
========================================
|
||||
|
||||
In Spain, e-invoicing is governed by the `Ley de Facturación Electrónica <https://www.facturae.gob.es/face/Paginas/FACE.aspx>`_
|
||||
and aligned with `EU Directive 2014/55/EU <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055>`_,
|
||||
mandating e-invoicing for :abbr:`B2G (business-to-government)` transactions. All invoices to public
|
||||
sector entities must be submitted through the FACe platform, Spain’s official electronic invoicing
|
||||
hub, using the required Facturae format. Additionally, the :abbr:`SII (Immediate Supply of
|
||||
Information)` system mandates near real-time reporting of VAT-related invoice data for certain
|
||||
companies, reinforcing transparency and compliance. While e-invoicing is not yet mandatory for B2B
|
||||
transactions, its adoption is expected to expand in the near future.
|
||||
|
||||
Compliance with Spanish e-invoicing regulations
|
||||
===============================================
|
||||
|
||||
Odoo Invoicing is fully equipped to help businesses meet Spain's e-invoicing and VAT reporting
|
||||
requirements. Here is how Odoo ensures compliance:
|
||||
|
||||
- **Supported formats**: Odoo supports the Facturae (XML) format required by the FACe platform for
|
||||
public sector e-invoicing in Spain. It is also compatible with XML in :abbr:`UBL (Universal
|
||||
Business Language)` formats used within the Peppol network for cross-border transactions. Odoo
|
||||
integrates with FACe, allowing businesses to submit e-invoices directly to Spanish public
|
||||
authorities. Odoo also facilitates compliance with the SII system, enabling automated and near
|
||||
real-time reporting of VAT-related data to the Spanish Tax Agency.
|
||||
- **Secure storage and retrieval**: In compliance with Spanish regulations requiring invoices to be
|
||||
stored for a minimum of four years, Odoo securely archives all invoices in a tamper-proof system,
|
||||
ensuring easy access during audits or inspections.
|
||||
- **Automatic VAT calculation and reporting**: Odoo Invoicing automates VAT calculations and ensures
|
||||
invoices are formatted to meet Spanish requirements for both :abbr:`B2G (business-to-government)`
|
||||
and B2B transactions, helping businesses comply with national and EU standards.
|
||||
|
||||
.. seealso::
|
||||
:doc:`Spain fiscal localization documentation <../../../fiscal_localizations/spain>`
|
||||
|
||||
.. admonition:: Disclaimer
|
||||
|
||||
This page provides an overview of Spanish e-invoicing laws and how Odoo Invoicing supports
|
||||
compliance with the Ley de Facturación Electrónica, FACe platform, SII system, Peppol standards,
|
||||
and other relevant regulations. It does not constitute legal advice. We recommend consulting with
|
||||
a tax advisor or legal professional familiar with Spanish e-invoicing regulations to ensure
|
||||
compliance tailored to your specific business needs.
|
||||
|
Before Width: | Height: | Size: 12 KiB |
|
After Width: | Height: | Size: 21 KiB |
|
After Width: | Height: | Size: 15 KiB |
|
After Width: | Height: | Size: 23 KiB |
|
After Width: | Height: | Size: 21 KiB |
|
After Width: | Height: | Size: 25 KiB |
|
After Width: | Height: | Size: 18 KiB |
|
After Width: | Height: | Size: 6.1 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 19 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 7.9 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 15 KiB |
|
After Width: | Height: | Size: 19 KiB |
|
After Width: | Height: | Size: 15 KiB |
@@ -116,7 +116,7 @@ for every computed *due date*.
|
||||
This makes for easier :doc:`follow-ups </applications/finance/accounting/payments/follow_up>` and
|
||||
:doc:`reconciliation </applications/finance/accounting/bank/reconciliation>` since Odoo takes each
|
||||
due date into account, rather than just the balance due date. It also helps to get an accurate
|
||||
:ref:`aged receivable report <accounting/invoices/aging-report>`.
|
||||
:ref:`aged receivable report <customer-invoices/aging-report>`.
|
||||
|
||||
.. example::
|
||||
.. image:: payment_terms/journal-entry.png
|
||||
|
||||
@@ -6,16 +6,12 @@ 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
|
||||
=================
|
||||
|
||||
@@ -29,14 +25,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 <accounting/analytic_accounting/analytic_plans>`;
|
||||
- :guilabel:`Plan`: add an :ref:`analytic plan <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.
|
||||
|
||||
.. _accounting/analytic_accounting/analytic_plans:
|
||||
.. _analytic_accounting/analytic_plans:
|
||||
|
||||
Analytic plans
|
||||
==============
|
||||
@@ -87,8 +83,6 @@ 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
|
||||
=====================
|
||||
|
||||
@@ -104,8 +98,6 @@ accounts by modifying the percentage.
|
||||
|
||||
.. _analytic_distribution_models:
|
||||
|
||||
.. _accounting/analytic_accounting/analytic-distribution-models:
|
||||
|
||||
Analytic distribution models
|
||||
----------------------------
|
||||
|
||||
|
||||
@@ -1,170 +1,102 @@
|
||||
=======
|
||||
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
|
||||
================
|
||||
|
||||
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>`.
|
||||
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**.
|
||||
|
||||
To activate the option for creating analytic budgets, go to :menuselection:`Accounting -->
|
||||
Configuration --> Settings`, and enable :guilabel:`Budget Management` in the :guilabel:`Analytics`
|
||||
section.
|
||||
Configuration
|
||||
=============
|
||||
|
||||
.. 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.
|
||||
Go to :menuselection:`Accounting --> Configuration --> Settings --> Analytics section`, and enable
|
||||
:guilabel:`Budget Management`.
|
||||
|
||||
.. _accounting/budgets/analytic-budget-set:
|
||||
Budgetary positions
|
||||
-------------------
|
||||
|
||||
Set an analytic budget
|
||||
----------------------
|
||||
Budgetary positions are lists of accounts for which you want to keep budgets (typically expense or
|
||||
income 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.
|
||||
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.
|
||||
|
||||
.. note::
|
||||
- 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.
|
||||
Each budgetary position can have any number of accounts from the chart of accounts, though it
|
||||
must have at least one.
|
||||
|
||||
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.
|
||||
Use case
|
||||
========
|
||||
|
||||
.. image:: budget/budget.png
|
||||
:alt: open budget with committed, achieved, and theoretical amounts
|
||||
Let’s illustrate this with an example.
|
||||
|
||||
.. note::
|
||||
Deleting a budget is only allowed in the :guilabel:`Draft` and :guilabel:`Cancelled` stages.
|
||||
We just started a project with *Smith & Co*, and we would like to budget the income and expenses of
|
||||
that project. We plan on having a revenue of 1000, and we don’t want to spend more than 700.
|
||||
|
||||
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`.
|
||||
First, we need to define what accounts relate to our project’s expenses. Go to
|
||||
:menuselection:`Accounting --> Configuration --> Management: Budgetary positions`, and click
|
||||
:guilabel:`New` to add a position. Add the accounts wherein expenses will be booked.
|
||||
|
||||
.. _accounting/budgets/analytic-budget-generate:
|
||||
.. image:: budget/smith-and-co-expenses.png
|
||||
:align: center
|
||||
:alt: display the Smith and Co expenses
|
||||
|
||||
Generate periodic budgets
|
||||
-------------------------
|
||||
Let's repeat the steps to create a budgetary position that reflects the 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:
|
||||
.. image:: budget/smith-and-co-revenue.png
|
||||
:align: center
|
||||
:alt: display the Smith and Co revenue
|
||||
|
||||
- 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.
|
||||
Analytical accounts
|
||||
-------------------
|
||||
|
||||
To generate periodic budgets, follow these steps:
|
||||
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*.
|
||||
|
||||
#. 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`.
|
||||
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`.
|
||||
|
||||
.. image:: budget/generate-budgets.png
|
||||
:alt: all the options to generate periodical budgets
|
||||
When creating a new customer invoice and/or vendor bill, you have to refer to this analytic account.
|
||||
|
||||
#. 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.
|
||||
.. image:: budget/analytic-accounts.png
|
||||
:align: center
|
||||
:alt: add analytic accounts in a new invoice or bill.
|
||||
|
||||
.. _accounting/budgets/analytic-budget-reporting:
|
||||
Define the budget
|
||||
-----------------
|
||||
|
||||
Reporting
|
||||
---------
|
||||
Let’s set our targets. We specified that we expect to gain 1000 with this project, and we would like
|
||||
not to spend more than 700. Go to :menuselection:`Accounting --> Management: Budgets` and click
|
||||
:guilabel:`New` to create a new budget for *Smith & Co* project.
|
||||
|
||||
To perform various reporting actions, go to :menuselection:`Accounting --> Reporting -->
|
||||
Budget Report`, then:
|
||||
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`.
|
||||
|
||||
- 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.
|
||||
.. image:: budget/define-the-budget.png
|
||||
:align: center
|
||||
:alt: budget lines display
|
||||
|
||||
.. _accounting/budgets/financial:
|
||||
.. Note::
|
||||
When recording a planned amount related to expenses, the amount must be negative.
|
||||
|
||||
Financial budgets
|
||||
=================
|
||||
Check your budget
|
||||
-----------------
|
||||
|
||||
Financial budgets are structured around specific income and expense accounts and transactions for
|
||||
official financial reporting and compliance purposes.
|
||||
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.
|
||||
|
||||
.. note::
|
||||
Financial budgets are available on the :ref:`Profit and Loss
|
||||
<accounting/reporting/profit-and-loss>` report.
|
||||
The :guilabel:`Practical Amount` evolves when a new journal entry related to your analytic account
|
||||
and an account from your budgetary position is created.
|
||||
|
||||
.. _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.
|
||||
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.
|
||||
|
||||
|
After Width: | Height: | Size: 9.9 KiB |
|
Before Width: | Height: | Size: 22 KiB |
|
After Width: | Height: | Size: 23 KiB |
|
Before Width: | Height: | Size: 6.9 KiB |
|
After Width: | Height: | Size: 5.0 KiB |
|
After Width: | Height: | Size: 4.0 KiB |
@@ -35,6 +35,9 @@ To do so, go to :menuselection:`Accounting --> Configuration --> Settings`. Unde
|
||||
- :guilabel:`Reminder`: define when Odoo should remind you to submit your tax return;
|
||||
- :guilabel:`Journal`: select the journal in which to record the tax return.
|
||||
|
||||
.. image:: tax_returns/tax_return_periodicity.png
|
||||
:align: center
|
||||
:alt: Configure how often tax returns have to be made in Odoo Accounting
|
||||
|
||||
.. note::
|
||||
This is usually configured during the :doc:`app's initial set up <../get_started>`.
|
||||
@@ -50,11 +53,16 @@ You can see the :guilabel:`Tax Grids` by opening the :guilabel:`Journal Items` t
|
||||
invoice and bill.
|
||||
|
||||
.. image:: tax_returns/tax_return_grids.png
|
||||
:align: center
|
||||
:alt: see which tax grids are used to record transactions in Odoo Accounting
|
||||
|
||||
To configure your tax grids, go to :menuselection:`Accounting --> Configuration --> Taxes`,
|
||||
and open the tax you want to modify. There, you can edit your tax settings, along with the tax
|
||||
grids that are used to record invoices or refunds.
|
||||
grids that are used to record invoices or credit notes.
|
||||
|
||||
.. image:: tax_returns/tax_return_taxes.png
|
||||
:align: center
|
||||
:alt: Configure taxes and their tax grids in Odoo Accounting
|
||||
|
||||
.. note::
|
||||
Taxes and reports are usually already pre-configured in Odoo: a :ref:`fiscal localization package
|
||||
@@ -68,41 +76,40 @@ Close a tax period
|
||||
|
||||
.. _tax-returns/lock-date:
|
||||
|
||||
Tax lock date
|
||||
Tax Lock Date
|
||||
-------------
|
||||
|
||||
Any new transaction whose accounting date prior to the :guilabel:`Lock Tax Return` date has its tax
|
||||
values moved to the next open tax period. This is useful to make sure that no change can be made to
|
||||
a report once its period is closed.
|
||||
Any new transaction whose accounting date prior to the :guilabel:`Tax Lock Date` has its tax values
|
||||
moved to the next open tax period. This is useful to make sure that no change can be made to a
|
||||
report once its period is closed.
|
||||
|
||||
Therefore, we recommend locking your tax date before working on your
|
||||
:guilabel:`Closing Journal Entry`.
|
||||
This way, other users cannot modify or add transactions that would have an impact on the
|
||||
:guilabel:`Closing Journal Entry`, which can help you avoid some tax declaration errors.
|
||||
|
||||
To check the current :guilabel:`Lock Tax Return` date, or to edit it, go to
|
||||
:menuselection:`Accounting --> Accounting --> Lock Dates`.
|
||||
To check the current :guilabel:`Tax Lock Date`, or to edit it, go to
|
||||
:menuselection:`Accounting --> Accounting --> Actions: Lock Dates`.
|
||||
|
||||
.. image:: tax_returns/tax_return_lock.png
|
||||
:align: center
|
||||
:alt: Lock your tax for a specific period in Odoo Accounting
|
||||
|
||||
.. _tax-returns/report:
|
||||
|
||||
Tax return
|
||||
Tax Report
|
||||
----------
|
||||
|
||||
Once all the transactions involving taxes have been posted for the period you want to report, open
|
||||
the :guilabel:`Tax Return` report by going to :menuselection:`Accounting --> Reporting --> Tax
|
||||
Return`. Select the period you want to declare using the date filter to have an overview of the tax
|
||||
return. Then, click :guilabel:`Closing Entry` to create a tax closing journal entry. Odoo
|
||||
automatically proposes the details of the journal entry. Make any necessary changes and click
|
||||
:guilabel:`Post`.
|
||||
your :guilabel:`Tax Report` by going to :menuselection:`Accounting --> Reporting -->
|
||||
Audit Reports: Tax Report`. Make sure to select the right period you want to declare by using the
|
||||
date filter, this way you can have an overview of your tax report. From this view, you can easily
|
||||
access different formats of your tax report, such as `PDF` and XLSX. These include all the values to
|
||||
report to the tax authorities, along with the amount you have to pay or be refunded.
|
||||
|
||||
From the report, click :guilabel:`PDF` to download a PDF of the tax return. Alternatively, click the
|
||||
:icon:`fa-cog` (:guilabel:`gear`) icon, then click :guilabel:`Download Excel` to download an XLSX of
|
||||
the tax return. To save the report to the Documents app, click the :icon:`fa-cog` (:guilabel:`gear`)
|
||||
icon, then click :guilabel:`Copy to Documents`. Select the format to :guilabel:`Export to`, the
|
||||
:guilabel:`Documents Name`, the :guilabel:`Folder` to store it in, and add any :guilabel:`Tags`.
|
||||
|
||||
The report includes all the values to report to the tax authorities, along with the amount to be
|
||||
paid or refunded.
|
||||
.. image:: tax_returns/tax_return_report.png
|
||||
:align: center
|
||||
:alt: download the PDF with your Tax Report in Odoo Accounting
|
||||
|
||||
.. note::
|
||||
If you forgot to lock your tax date before clicking on :guilabel:`Closing Journal Entry`, then
|
||||
|
||||
|
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 11 KiB |
|
After Width: | Height: | Size: 4.7 KiB |
|
After Width: | Height: | Size: 7.6 KiB |
|
After Width: | Height: | Size: 70 KiB |
|
After Width: | Height: | Size: 11 KiB |
@@ -24,8 +24,10 @@ programming interface)` integration.
|
||||
.. important::
|
||||
Some limitations exist in Odoo while using AvaTax for tax calculation:
|
||||
|
||||
- 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.
|
||||
- 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.
|
||||
- Excise tax is **not** supported. This includes tobacco/vape taxes, fuel taxes, and other
|
||||
specific industries.
|
||||
|
||||
|
||||
@@ -4,163 +4,128 @@
|
||||
Fiscal localizations
|
||||
====================
|
||||
|
||||
Fiscal localizations are country-specific modules that allow you to be compliant with a country's
|
||||
fiscal requirements. Most of these modules are related to the :ref:`Accounting
|
||||
<fiscal_localizations/accounting>` or :ref:`Payroll <fiscal_localizations/payroll>` app, but they
|
||||
can also be necessary for other apps such as Point of Sale, eCommerce, etc., depending on a
|
||||
country's fiscal requirements.
|
||||
|
||||
.. _fiscal_localizations/packages:
|
||||
|
||||
Configuration
|
||||
=============
|
||||
Fiscal localization packages
|
||||
============================
|
||||
|
||||
Odoo should automatically install the required fiscal localization modules based on the company's
|
||||
country when the related app is installed. Refer to the :ref:`list of countries
|
||||
<fiscal_localizations/countries-list>` to view the currently supported countries and access their
|
||||
specific documentation.
|
||||
**Fiscal Localization Packages** are country-specific modules that install pre-configured taxes,
|
||||
fiscal positions, chart of accounts, and legal statements on your database. Some additional
|
||||
features, such as the configuration of specific certificates, are also added to your Accounting app,
|
||||
following your fiscal administration requirements.
|
||||
|
||||
.. note::
|
||||
Each company in a multi-company environment can use different fiscal localization modules.
|
||||
Odoo continuously adds new localizations and improves the existing packages.
|
||||
|
||||
.. _fiscal_localizations/accounting:
|
||||
Configuration
|
||||
-------------
|
||||
|
||||
Accounting
|
||||
----------
|
||||
Odoo automatically installs the appropriate package for your company, according to the country
|
||||
selected at the creation of the database.
|
||||
|
||||
Verify the right package of modules is installed by going to :menuselection:`Accounting -->
|
||||
Configuration --> Settings` and checking the :guilabel:`Package` field under the :guilabel:`Fiscal
|
||||
Localization` section. Select another one if necessary.
|
||||
.. important::
|
||||
As long as you haven't posted any entry, you can still select another package.
|
||||
|
||||
.. warning::
|
||||
Selecting another package is only possible if no entry has been posted.
|
||||
To select a fiscal localization package for your company, go to :menuselection:`Accounting -->
|
||||
Configuration --> Settings --> Fiscal Localization`, select the appropriate package from the list
|
||||
and save.
|
||||
|
||||
These packages require fine-tuning the chart of accounts, activating the taxes to be used,
|
||||
configuring the country-specific statements and certifications, and sometimes more.
|
||||
.. image:: fiscal_localizations/package-selection.png
|
||||
:alt: Select your country's fiscal localization package in Odoo Accounting.
|
||||
|
||||
.. _fiscal_localizations/payroll:
|
||||
Use
|
||||
---
|
||||
|
||||
Payroll
|
||||
-------
|
||||
These packages require you to fine-tune your chart of accounts according to your needs, activate the
|
||||
taxes you use, and configure your country-specific statements and certifications.
|
||||
|
||||
Localization settings can be accessed by going to :menuselection:`Payroll --> Configuration -->
|
||||
Settings` and searching for the country's **Localization** section.
|
||||
.. seealso::
|
||||
- :doc:`accounting/get_started/chart_of_accounts`
|
||||
- :doc:`accounting/taxes`
|
||||
|
||||
.. _fiscal_localizations/countries-list:
|
||||
|
||||
List of countries
|
||||
=================
|
||||
List of supported countries
|
||||
===========================
|
||||
|
||||
Fiscal localization modules are available for the countries listed below.
|
||||
Odoo Accounting can be used in many countries out of the box by installing the appropriate module.
|
||||
Here is a list of all :ref:`fiscal localization package <fiscal_localizations/packages>` that are
|
||||
available on Odoo.
|
||||
|
||||
.. note::
|
||||
New countries are frequently added to this list and Odoo keeps expanding and improving existing
|
||||
localizations and the related documentation.
|
||||
|
||||
- Algeria
|
||||
- :doc:`Argentina <fiscal_localizations/argentina>`
|
||||
- :doc:`Australia <fiscal_localizations/australia>`
|
||||
- :doc:`Austria <fiscal_localizations/austria>`
|
||||
- Bangladesh
|
||||
- :doc:`Belgium <fiscal_localizations/belgium>`
|
||||
- Benin
|
||||
- Bolivia
|
||||
- :doc:`Brazil <fiscal_localizations/brazil>`
|
||||
- Burkina Faso
|
||||
- Bulgaria
|
||||
- Cameroon
|
||||
- :doc:`Canada <fiscal_localizations/canada>`
|
||||
- Central African Republic
|
||||
- Chad
|
||||
- :doc:`Chile <fiscal_localizations/chile>`
|
||||
- China
|
||||
- :doc:`Colombia <fiscal_localizations/colombia>`
|
||||
- Comoros
|
||||
- Congo
|
||||
- Costa Rica
|
||||
- Croatia
|
||||
- Cyprus
|
||||
- Czech Republic
|
||||
- Democratic Republic of the Congo
|
||||
- Denmark
|
||||
- Dominican Republic
|
||||
- :doc:`Ecuador <fiscal_localizations/ecuador>`
|
||||
- :doc:`Egypt <fiscal_localizations/egypt>`
|
||||
- Equatorial Guinea
|
||||
- Estonia
|
||||
- Ethiopia
|
||||
- Finland
|
||||
- :doc:`France <fiscal_localizations/france>`
|
||||
- Gabon
|
||||
- Algeria - Accounting
|
||||
- :doc:`Argentina - Accounting <fiscal_localizations/argentina>`
|
||||
- :doc:`Australian - Accounting <fiscal_localizations/australia>`
|
||||
- :doc:`Austria - Accounting <fiscal_localizations/austria>`
|
||||
- :doc:`Belgium - Accounting <fiscal_localizations/belgium>`
|
||||
- Bolivia - Accounting
|
||||
- :doc:`Brazilian - Accounting <fiscal_localizations/brazil>`
|
||||
- :doc:`Canada - Accounting <fiscal_localizations/canada>`
|
||||
- :doc:`Chile - Accounting <fiscal_localizations/chile>`
|
||||
- China - Accounting
|
||||
- :doc:`Colombia - Accounting <fiscal_localizations/colombia>`
|
||||
- Costa Rica - Accounting
|
||||
- Croatia - Accounting (RRIF 2012)
|
||||
- Czech - Accounting
|
||||
- Denmark - Accounting
|
||||
- Dominican Republic - Accounting
|
||||
- :doc:`Ecuadorian - Accounting <fiscal_localizations/ecuador>`
|
||||
- :doc:`Egypt - Accounting <fiscal_localizations/egypt>`
|
||||
- Ethiopia - Accounting
|
||||
- Finnish Localization
|
||||
- :doc:`France - Accounting <fiscal_localizations/france>`
|
||||
- Generic - Accounting
|
||||
- :doc:`Germany <fiscal_localizations/germany>`
|
||||
- Guinea
|
||||
- Greece
|
||||
- Guatemala
|
||||
- Guinea-Bissau
|
||||
- Honduras
|
||||
- :doc:`Hong Kong <fiscal_localizations/hong_kong>`
|
||||
- Hungary
|
||||
- :doc:`India <fiscal_localizations/india>`
|
||||
- :doc:`Indonesia <fiscal_localizations/indonesia>`
|
||||
- :doc:`Italy <fiscal_localizations/italy>`
|
||||
- Ivory Coast
|
||||
- Japan
|
||||
- Jordan
|
||||
- Kazakhstan
|
||||
- :doc:`Kenya <fiscal_localizations/kenya>`
|
||||
- Kuwait
|
||||
- Latvia
|
||||
- Lithuania
|
||||
- :doc:`Luxembourg <fiscal_localizations/luxembourg>`
|
||||
- Mali
|
||||
- Malta
|
||||
- Mauritius
|
||||
- :doc:`Malaysia <fiscal_localizations/malaysia>`
|
||||
- :doc:`Mexico <fiscal_localizations/mexico>`
|
||||
- Mongolia
|
||||
- Morocco
|
||||
- Mozambique
|
||||
- :doc:`Netherlands <fiscal_localizations/netherlands>`
|
||||
- :doc:`New Zealand <fiscal_localizations/new_zealand>`
|
||||
- Niger
|
||||
- Nigeria
|
||||
- Norway
|
||||
- Pakistan
|
||||
- Panama
|
||||
- :doc:`Peru <fiscal_localizations/peru>`
|
||||
- :doc:`Philippines <fiscal_localizations/philippines>`
|
||||
- Poland
|
||||
- Portugal
|
||||
- Qatar
|
||||
- :doc:`Romania <fiscal_localizations/romania>`
|
||||
- Rwanda
|
||||
- :doc:`Saudi Arabia <fiscal_localizations/saudi_arabia>`
|
||||
- Senegal
|
||||
- Serbia
|
||||
- :doc:`Singapore <fiscal_localizations/singapore>`
|
||||
- Slovakia
|
||||
- Slovenia
|
||||
- South Africa
|
||||
- :doc:`Spain <fiscal_localizations/spain>`
|
||||
- Sweden
|
||||
- :doc:`Switzerland <fiscal_localizations/switzerland>`
|
||||
- Taiwan
|
||||
- Tanzania
|
||||
- :doc:`Thailand <fiscal_localizations/thailand>`
|
||||
- Tunisia
|
||||
- Türkiye
|
||||
- Uganda
|
||||
- Ukraine
|
||||
- :doc:`United Arab Emirates <fiscal_localizations/united_arab_emirates>`
|
||||
- :doc:`United Kingdom <fiscal_localizations/united_kingdom>`
|
||||
- :doc:`United States of America <fiscal_localizations/united_states>`
|
||||
- :doc:`Uruguay <fiscal_localizations/uruguay>`
|
||||
- Venezuela
|
||||
- :doc:`Vietnam <fiscal_localizations/vietnam>`
|
||||
- Zambia
|
||||
|
||||
.. seealso::
|
||||
:doc:`Employment Hero Payroll documentation <fiscal_localizations/employment_hero>`
|
||||
- Germany SKR03 - Accounting
|
||||
- Germany SKR04 - Accounting
|
||||
|
||||
- Greece - Accounting
|
||||
- Guatemala - Accounting
|
||||
- Honduras - Accounting
|
||||
- :doc:`Hong Kong - Accounting <fiscal_localizations/hong_kong>`
|
||||
- Hungarian - Accounting
|
||||
- :doc:`Indian - Accounting <fiscal_localizations/india>`
|
||||
- :doc:`Indonesian - Accounting <fiscal_localizations/indonesia>`
|
||||
- Ireland - Accounting
|
||||
- Israel - Accounting
|
||||
- :doc:`Italy - Accounting <fiscal_localizations/italy>`
|
||||
- Japan - Accounting
|
||||
- :doc:`Kenya - Accounting <fiscal_localizations/kenya>`
|
||||
- Lithuania - Accounting
|
||||
- :doc:`Luxembourg - Accounting <fiscal_localizations/luxembourg>`
|
||||
- :doc:`Malaysia - Accounting <fiscal_localizations/malaysia>`
|
||||
- Maroc - Accounting
|
||||
- :doc:`Mexico - Accounting <fiscal_localizations/mexico>`
|
||||
- Mongolia - Accounting
|
||||
- :doc:`Netherlands - Accounting <fiscal_localizations/netherlands>`
|
||||
- :doc:`New Zealand - Accounting <fiscal_localizations/new_zealand>`
|
||||
- Norway - Accounting
|
||||
- OHADA - Accounting
|
||||
- Pakistan - Accounting
|
||||
- Panama - Accounting
|
||||
- :doc:`Peru - Accounting <fiscal_localizations/peru>`
|
||||
- :doc:`Philippines - Accounting <fiscal_localizations/philippines>`
|
||||
- Poland - Accounting
|
||||
- Portugal - Accounting
|
||||
- :doc:`Romania - Accounting <fiscal_localizations/romania>`
|
||||
- :doc:`Saudi Arabia - Accounting <fiscal_localizations/saudi_arabia>`
|
||||
- :doc:`Singapore - Accounting <fiscal_localizations/singapore>`
|
||||
- Slovak - Accounting
|
||||
- Slovenian - Accounting
|
||||
- South Africa - Accounting
|
||||
- :doc:`Spain - Accounting (PGCE 2008) <fiscal_localizations/spain>`
|
||||
- Sweden - Accounting
|
||||
- :doc:`Switzerland - Accounting <fiscal_localizations/switzerland>`
|
||||
- Taiwan - Accounting
|
||||
- :doc:`Thailand - Accounting <fiscal_localizations/thailand>`
|
||||
- Turkey - Accounting
|
||||
- :doc:`United Arab Emirates - Accounting <fiscal_localizations/united_arab_emirates>`
|
||||
- :doc:`UK - Accounting <fiscal_localizations/united_kingdom>`
|
||||
- Ukraine - Accounting
|
||||
- :doc:`United States - Accounting <fiscal_localizations/united_states>`
|
||||
- :doc:`Uruguay - Accounting <fiscal_localizations/uruguay>`
|
||||
- Venezuela - Accounting
|
||||
- :doc:`Vietnam - Accounting <fiscal_localizations/vietnam>`
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
|
After Width: | Height: | Size: 9.3 KiB |
|
After Width: | Height: | Size: 24 KiB |
|
Before Width: | Height: | Size: 23 KiB |
|
After Width: | Height: | Size: 23 KiB |
|
Before Width: | Height: | Size: 42 KiB After Width: | Height: | Size: 34 KiB |
|
Before Width: | Height: | Size: 28 KiB After Width: | Height: | Size: 28 KiB |
|
After Width: | Height: | Size: 37 KiB |
|
After Width: | Height: | Size: 4.4 KiB |
|
Before Width: | Height: | Size: 6.5 KiB |
|
Before Width: | Height: | Size: 31 KiB |
|
Before Width: | Height: | Size: 34 KiB |
|
Before Width: | Height: | Size: 28 KiB |
|
After Width: | Height: | Size: 24 KiB |
|
After Width: | Height: | Size: 31 KiB |
|
After Width: | Height: | Size: 10 KiB |
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 36 KiB |
|
After Width: | Height: | Size: 29 KiB |
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 26 KiB |
|
Before Width: | Height: | Size: 20 KiB |
|
Before Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 42 KiB |
|
Before Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 17 KiB |
|
Before Width: | Height: | Size: 47 KiB |
|
Before Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 30 KiB |
|
Before Width: | Height: | Size: 28 KiB |
|
Before Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 59 KiB |
|
Before Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 18 KiB |
|
Before Width: | Height: | Size: 32 KiB |
|
Before Width: | Height: | Size: 47 KiB |
|
Before Width: | Height: | Size: 13 KiB |