mirror of
https://github.com/odoo/documentation.git
synced 2026-01-02 09:49:17 +07:00
Compare commits
4 Commits
maal-odoo-
...
master-aut
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
8c48281fe7 | ||
|
|
f9f24c04d1 | ||
|
|
90803ab56f | ||
|
|
a89d5ea8d6 |
@@ -60,4 +60,4 @@ source_lang = en
|
||||
[odoo-14-doc.websites]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/websites.po
|
||||
source_file = locale/sources/websites.pot
|
||||
source_lang = en
|
||||
source_lang = en
|
||||
|
||||
@@ -43,4 +43,4 @@ To **report a content issue**, **request new content** or **ask a question**, us
|
||||
|
||||
To learn more about Odoo, in addition to the documentation, have a look at
|
||||
[the official eLearning](https://odoo.com/slides) and
|
||||
[Scale-up, The Business Game](https://www.odoo.com/page/scale-up-business-game).
|
||||
[Scale-up, The Business Game](https://www.odoo.com/page/scale-up-business-game).
|
||||
|
||||
@@ -16,4 +16,4 @@
|
||||
# [REM] = Removal
|
||||
# [REF] = Refactoring (restructuring)
|
||||
# [MOV] = Move/rename
|
||||
#
|
||||
#
|
||||
|
||||
@@ -392,7 +392,7 @@ The solutions to support livechat/motifications in a WSGI application are:
|
||||
|
||||
* Deploy a threaded version of Odoo (instead of a process-based preforking
|
||||
one) and redirect only requests to URLs starting with ``/websocket/`` to
|
||||
that Odoo, this is the simplest and the websocket URL can double up as the cron
|
||||
that Odoo, this is the simplest and the websocket URL can double up as the cron
|
||||
instance.
|
||||
* Deploy an evented Odoo via ``odoo-gevent`` and proxy requests starting
|
||||
with ``/websocket/`` to
|
||||
@@ -410,7 +410,7 @@ a static HTTP server.
|
||||
Serving static files
|
||||
--------------------
|
||||
|
||||
Odoo static files are located in each module's :file:`static/` folder, so static files can be served
|
||||
Odoo static files are located in each module's :file:`static/` folder, so static files can be served
|
||||
by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up the right module
|
||||
(and file) in the various addons paths.
|
||||
|
||||
@@ -420,13 +420,13 @@ by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up
|
||||
|
||||
Using the above NGINX (https) configuration, the following location block should be added to
|
||||
serve static files via NGINX.
|
||||
|
||||
|
||||
.. code-block:: nginx
|
||||
|
||||
|
||||
location @odoo {
|
||||
# copy-paste the content of the / location block
|
||||
}
|
||||
|
||||
|
||||
# Serve static files right away
|
||||
location ~ ^/[^/]+/static/.+$ {
|
||||
root /usr/lib/python3/dist-packages/odoo/addons;
|
||||
@@ -444,11 +444,11 @@ by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up
|
||||
serve static files via NGINX.
|
||||
|
||||
.. code-block:: nginx
|
||||
|
||||
|
||||
location @odoo {
|
||||
# copy-paste the content of the / location block
|
||||
}
|
||||
|
||||
|
||||
# Serve static files right away
|
||||
location ~ ^/[^/]+/static/.+$ {
|
||||
root /opt/odoo;
|
||||
@@ -483,7 +483,7 @@ X-Sendfile and X-Accel).
|
||||
- The X-Accel extension for NGINX **does** require the following additionnal configuration:
|
||||
|
||||
.. code-block:: nginx
|
||||
|
||||
|
||||
location /web/filestore {
|
||||
internal;
|
||||
alias /path/to/odoo/data-dir/filestore;
|
||||
|
||||
@@ -17,7 +17,7 @@ You can use a custom domain name to access your Odoo database and websites:
|
||||
``odoo.com`` for both the URL and the emails (e.g., ``https://example.odoo.com``).
|
||||
|
||||
.. important::
|
||||
Odoo offers a :ref:`free custom domain name <domain-name/odoo-register>` to all Odoo Online
|
||||
Odoo offers a :ref:`free custom domain name <domain-name/odoo-register>` to all Odoo Online
|
||||
databases for one year. Visitors can then access your website with an address such as
|
||||
``www.example.com`` rather than the default ``example.odoo.com``.
|
||||
|
||||
|
||||
@@ -41,7 +41,7 @@ On Linux, using an installer
|
||||
.. code-block:: console
|
||||
|
||||
$ sudo dpkg -i <path_to_enterprise_deb>
|
||||
|
||||
|
||||
* Update your database to the enterprise packages using
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
@@ -123,7 +123,7 @@ server in Odoo. The configuration automatically loads the token in Odoo, and a t
|
||||
:align: center
|
||||
:alt: Configure Outgoing Email Servers in Odoo.
|
||||
|
||||
Finally, save the settings and :guilabel:`Test the Connection`. A confirmation message should
|
||||
Finally, save the settings and :guilabel:`Test the Connection`. A confirmation message should
|
||||
appear. The Odoo database can now send safe, secure emails through Google using OAuth
|
||||
authentication.
|
||||
|
||||
|
||||
@@ -85,4 +85,3 @@ From Odoo.sh to on-premises
|
||||
|
||||
1. Grab a :ref:`backup of your Odoo.sh production database <odoo_sh_branches_backups>`.
|
||||
2. Restore it from the database manager on your local server.
|
||||
|
||||
|
||||
@@ -29,4 +29,3 @@ We advise that:
|
||||
- Your scheduled actions should be
|
||||
`idempotent <https://stackoverflow.com/a/1077421/3332416>`_: they must not
|
||||
cause side-effects if they are started more often than expected.
|
||||
|
||||
|
||||
@@ -259,16 +259,16 @@ This server only keeps one month of backups: 7 daily and 4 weekly backups.
|
||||
Dedicated backup servers keep the same backups, as well as 3 additional monthly backups.
|
||||
To restore or download one of these monthly backups, please `contact us <https://www.odoo.com/help>`_.
|
||||
|
||||
If you merge a commit updating the version of one or several modules (in :file:`__manifest__.py`), or their linked python
|
||||
dependencies (in :file:`requirements.txt`), then Odoo.sh performs a backup automatically (flagged with type Update in the list),
|
||||
as either the container will be changed by the installation of new pip packages, either the database itself will be
|
||||
changed with the module update triggered afterwards. In these two cases, we are doing a backup as it may potentially
|
||||
If you merge a commit updating the version of one or several modules (in :file:`__manifest__.py`), or their linked python
|
||||
dependencies (in :file:`requirements.txt`), then Odoo.sh performs a backup automatically (flagged with type Update in the list),
|
||||
as either the container will be changed by the installation of new pip packages, either the database itself will be
|
||||
changed with the module update triggered afterwards. In these two cases, we are doing a backup as it may potentially
|
||||
break things.
|
||||
|
||||
If you merge a commit that only changes some code without the above-mentioned modifications, then no backup is done
|
||||
by Odoo.sh, as neither the container nor the database is modified so the platform considers this safe enough. Of course,
|
||||
as an extra precaution, you can make a backup manually before making big changes in your production sources in case
|
||||
something goes wrong (those manual backups are available for about one week). To avoid abuse, we limit manual backups
|
||||
If you merge a commit that only changes some code without the above-mentioned modifications, then no backup is done
|
||||
by Odoo.sh, as neither the container nor the database is modified so the platform considers this safe enough. Of course,
|
||||
as an extra precaution, you can make a backup manually before making big changes in your production sources in case
|
||||
something goes wrong (those manual backups are available for about one week). To avoid abuse, we limit manual backups
|
||||
to 5 per day.
|
||||
|
||||
The *import database* feature accepts database archives in the format provided by:
|
||||
|
||||
@@ -254,4 +254,4 @@ Agreement <upgrade>` page.
|
||||
.. seealso::
|
||||
- :doc:`upgrade/faq`
|
||||
- :doc:`odoo_sh`
|
||||
- :doc:`maintain/supported_versions`
|
||||
- :doc:`maintain/supported_versions`
|
||||
|
||||
@@ -56,4 +56,4 @@ Depending on your contract, the upgrade of your custom modules can be done
|
||||
|
||||
#. by yourself.
|
||||
#. by your Partner.
|
||||
#. by Odoo (if you hold a subscription to 'Maintenance of Customizations').
|
||||
#. by Odoo (if you hold a subscription to 'Maintenance of Customizations').
|
||||
|
||||
@@ -11,4 +11,4 @@ Finance
|
||||
finance/expenses
|
||||
finance/documents
|
||||
finance/sign
|
||||
finance/payment_providers
|
||||
finance/payment_providers
|
||||
|
||||
@@ -59,4 +59,4 @@ transaction written on the original bank statement.
|
||||
|
||||
.. note::
|
||||
The **Ending Balance** and the **Computed Balance** should have the same amount. If this is not
|
||||
the case, make sure there are no mistakes in the transactions’ amounts.
|
||||
the case, make sure there are no mistakes in the transactions’ amounts.
|
||||
|
||||
@@ -80,12 +80,12 @@ FAQ
|
||||
I have an error when I try to delete my synchronization within Odoo
|
||||
-------------------------------------------------------------------
|
||||
|
||||
Odoo can't permanently delete the connection you have created with the banking institution. However,
|
||||
it can revoke the consent you gave so that Odoo won't be able to access your account anymore. The
|
||||
error you are seeing is probably a message telling you that the consent was revoked, but the record
|
||||
could not be deleted as it still exists within Salt edge. If you want to remove the connection
|
||||
completely, please connect to your `Salt Edge account <https://www.saltedge.com/dashboard>`_
|
||||
and manually delete your synchronization. Once this is done, you can go back to Odoo to delete the
|
||||
Odoo can't permanently delete the connection you have created with the banking institution. However,
|
||||
it can revoke the consent you gave so that Odoo won't be able to access your account anymore. The
|
||||
error you are seeing is probably a message telling you that the consent was revoked, but the record
|
||||
could not be deleted as it still exists within Salt edge. If you want to remove the connection
|
||||
completely, please connect to your `Salt Edge account <https://www.saltedge.com/dashboard>`_
|
||||
and manually delete your synchronization. Once this is done, you can go back to Odoo to delete the
|
||||
record.
|
||||
|
||||
I have an error saying that I have already synchronized this account
|
||||
|
||||
@@ -7,4 +7,4 @@ Miscellaneous
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
misc/interbank
|
||||
misc/interbank
|
||||
|
||||
@@ -144,4 +144,4 @@ Bank journal entry
|
||||
- $1,000
|
||||
* - Bank Account (BANK B)
|
||||
- **$1,000**
|
||||
-
|
||||
-
|
||||
|
||||
@@ -8,4 +8,4 @@ Bank reconciliation
|
||||
:titlesonly:
|
||||
|
||||
reconciliation/use_cases
|
||||
reconciliation/reconciliation_models
|
||||
reconciliation/reconciliation_models
|
||||
|
||||
@@ -126,4 +126,4 @@ line*.
|
||||
|
||||
- :doc:`use_cases`
|
||||
- :doc:`../feeds/bank_synchronization`
|
||||
- :doc:`../../receivables/customer_invoices/cash_discounts`
|
||||
- :doc:`../../receivables/customer_invoices/cash_discounts`
|
||||
|
||||
@@ -102,4 +102,4 @@ right and validate all related payments :
|
||||
:align: center
|
||||
|
||||
.. seealso::
|
||||
* :doc:`../feeds/bank_synchronization`
|
||||
* :doc:`../feeds/bank_synchronization`
|
||||
|
||||
@@ -114,4 +114,4 @@ gains/losses** have been adjusted.
|
||||
|
||||
.. image:: foreign_currency/foreign-adjustment.png
|
||||
:align: center
|
||||
:alt: Unrealized Currency Gains/Losses report once adjusted.
|
||||
:alt: Unrealized Currency Gains/Losses report once adjusted.
|
||||
|
||||
@@ -11,7 +11,7 @@ Configuration
|
||||
.. image:: manage_cash_register/journal.png
|
||||
:align: center
|
||||
|
||||
1. Configure the Cash journal in :menuselection:`Accounting --> Configuration -->
|
||||
1. Configure the Cash journal in :menuselection:`Accounting --> Configuration -->
|
||||
Journals`.
|
||||
|
||||
2. In the tab Journal Entries, the Default Debit and Credit Account can be
|
||||
|
||||
@@ -8,4 +8,4 @@ Fiscal localizations
|
||||
:titlesonly:
|
||||
|
||||
fiscal_localizations/overview
|
||||
fiscal_localizations/localizations
|
||||
fiscal_localizations/localizations
|
||||
|
||||
@@ -23,9 +23,9 @@ modules are available:
|
||||
- **l10n_ar_reports**: Add VAT Book report which is a legal requirement in Argentine and that holds
|
||||
the VAT detail info of sales or purchases recorded on the journal entries. This module includes as
|
||||
well the VAT summary report that is used to analyze the invoice
|
||||
|
||||
- **l10n_ar_edi**: This module includes all technical and functional requirements to generate
|
||||
Electronic Invoice via web service, based on the AFIP regulations.
|
||||
|
||||
- **l10n_ar_edi**: This module includes all technical and functional requirements to generate
|
||||
Electronic Invoice via web service, based on the AFIP regulations.
|
||||
|
||||
|
||||
Configuration
|
||||
@@ -48,7 +48,7 @@ fiscal obligation and structure of the company:
|
||||
|
||||
.. image:: argentina/argentina02.png
|
||||
:align: center
|
||||
|
||||
|
||||
|
||||
Chart of Account
|
||||
~~~~~~~~~~~~~~~~
|
||||
@@ -75,9 +75,9 @@ Environment
|
||||
|
||||
The AFIP infrastructure is replicated in two separate environments, Testing and Production.
|
||||
|
||||
Testing is provided so that the Companies can test their developments until they are ready to move
|
||||
into the Production environment. As these two environments are completely isolated from each other,
|
||||
the digital certificates of one instance are not valid in the other one.
|
||||
Testing is provided so that the Companies can test their developments until they are ready to move
|
||||
into the Production environment. As these two environments are completely isolated from each other,
|
||||
the digital certificates of one instance are not valid in the other one.
|
||||
|
||||
Go to :menuselection:`Accounting --> Settings --> Argentinian Localization` to select the environment:
|
||||
|
||||
@@ -87,10 +87,10 @@ Go to :menuselection:`Accounting --> Settings --> Argentinian Localization` to s
|
||||
|
||||
AFIP Certificates
|
||||
*****************
|
||||
The electronic invoice and other afip services work with WebServices (WS) provided by the AFIP.
|
||||
The electronic invoice and other afip services work with WebServices (WS) provided by the AFIP.
|
||||
|
||||
In order to enable communication with the AFIP, the first step is to request a Digital Certificate
|
||||
if you don’t have one already.
|
||||
if you don’t have one already.
|
||||
|
||||
#. Generate certificate Sign Request (Odoo). When this option is selected a file with extension
|
||||
``.csr`` (certificate signing request) is generated to be used the AFIP portal to request the
|
||||
@@ -101,7 +101,7 @@ if you don’t have one already.
|
||||
#. Generate Certificate (AFIP). Access the AFIP portal and follow the instructions described in the
|
||||
next document in order to get a certificate. `Get AFIP Certificate
|
||||
<http://www.afip.gob.ar/ws/WSAA/wsaa_obtener_certificado_produccion.pdf>`_.
|
||||
|
||||
|
||||
#. Upload Certificate and Private Key (Odoo). Once the certificate has been generated, it needs to
|
||||
be uploaded in Odoo, using the pencil next in the field “Certificado” and selecting the
|
||||
corresponding file.
|
||||
@@ -109,7 +109,7 @@ if you don’t have one already.
|
||||
.. image:: argentina/argentina_edi_03.png
|
||||
|
||||
.. tip::
|
||||
In case you need to configure the Homologation Certificate, please refer to the AFIP official
|
||||
In case you need to configure the Homologation Certificate, please refer to the AFIP official
|
||||
documentation: `Homologation Certificate
|
||||
<http://www.afip.gob.ar/ws/documentacion/certificados.asp>`_.
|
||||
|
||||
@@ -244,11 +244,11 @@ defines as well:
|
||||
#. The structure and data of the electronic invoice file.
|
||||
|
||||
Web Services
|
||||
************
|
||||
- ``wsfev1: Electronic Invoice.`` This is the most common service,
|
||||
is used to generated invoices for document types A, B, C, M with no detail per item.
|
||||
- ``wsbfev1: Electronic Fiscal Bond.`` For those who invoice capital goods and wish
|
||||
to access the benefit of the Electronic Tax Bonds granted by the Ministry of Economy. For more
|
||||
************
|
||||
- ``wsfev1: Electronic Invoice.`` This is the most common service,
|
||||
is used to generated invoices for document types A, B, C, M with no detail per item.
|
||||
- ``wsbfev1: Electronic Fiscal Bond.`` For those who invoice capital goods and wish
|
||||
to access the benefit of the Electronic Tax Bonds granted by the Ministry of Economy. For more
|
||||
detail you can refer to the next link: `Fiscal Bond
|
||||
<https://www.argentina.gob.ar/acceder-un-bono-por-fabricar-bienes-de-capital>`_.
|
||||
- ``wsfexv1: Electronic Exportation Invoice.`` Used to generate invoices for international customers
|
||||
@@ -282,8 +282,8 @@ can be used:
|
||||
:align: center
|
||||
|
||||
.. note::
|
||||
When creating the Purchase journals, it's possible to define if they can be related to document
|
||||
types or not. In case that the option to use documents is selected, there is no need to manually
|
||||
When creating the Purchase journals, it's possible to define if they can be related to document
|
||||
types or not. In case that the option to use documents is selected, there is no need to manually
|
||||
associate the document type sequences as the document number is provided by the vendor.
|
||||
|
||||
|
||||
@@ -326,22 +326,22 @@ responsibility type but it can be updated manually by the user.
|
||||
|
||||
Electronic Invoice elements
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
When using electronic invoice, if all the information is correct the Invoice is posted in the
|
||||
standard way, in case that something needs to be addressed (check the section common errors for more
|
||||
detail), an error message is raised indicating the issue/proposed solution and the invoice remains
|
||||
in draft until the related data is corrected.
|
||||
When using electronic invoice, if all the information is correct the Invoice is posted in the
|
||||
standard way, in case that something needs to be addressed (check the section common errors for more
|
||||
detail), an error message is raised indicating the issue/proposed solution and the invoice remains
|
||||
in draft until the related data is corrected.
|
||||
|
||||
Once the invoice is posted, the information related to the AFIP validation and status is displayed
|
||||
in the AFIP Tab, including:
|
||||
Once the invoice is posted, the information related to the AFIP validation and status is displayed
|
||||
in the AFIP Tab, including:
|
||||
|
||||
- AFIP Autorisation: CAE number.
|
||||
- Expiration date: Deadline to deliver the invoice to the customers. Normally 10 days after the
|
||||
CAE is generated.
|
||||
- Expiration date: Deadline to deliver the invoice to the customers. Normally 10 days after the
|
||||
CAE is generated.
|
||||
- Result:
|
||||
|
||||
- Aceptado en AFIP.
|
||||
- Aceptado con Observaciones.
|
||||
|
||||
- Aceptado con Observaciones.
|
||||
|
||||
.. image:: argentina/argentina_edi_15.png
|
||||
:align: center
|
||||
|
||||
@@ -378,7 +378,7 @@ Special Use Cases
|
||||
Invoices for Services
|
||||
*********************
|
||||
For electronic invoices that include Services, the AFIP requires to report the service starting
|
||||
and ending date, this information can be filled in the tab “Other Info”:
|
||||
and ending date, this information can be filled in the tab “Other Info”:
|
||||
|
||||
.. image:: argentina/argentina_edi_06.png
|
||||
:align: center
|
||||
@@ -392,34 +392,34 @@ filled automatically considering the beginning and day of the invoice month:
|
||||
|
||||
Exportation Invoices
|
||||
********************
|
||||
The invoices related to Exportation transactions required a Journal that used the AFIP POS
|
||||
The invoices related to Exportation transactions required a Journal that used the AFIP POS
|
||||
System “Expo Voucher - Web Service” so the proper document type be associated:
|
||||
|
||||
.. image:: argentina/argentina_edi_08.png
|
||||
:align: center
|
||||
|
||||
When the customer selected in the Invoice has set the AFIP responsibility type as “Cliente /
|
||||
When the customer selected in the Invoice has set the AFIP responsibility type as “Cliente /
|
||||
Proveedor del Exterior” or “IVA Liberado – Ley Nº 19.640”, Odoo automatically assigned:
|
||||
|
||||
- Journal related to the exportation Web Service.
|
||||
- Exportation document type .
|
||||
- Fiscal position: Compras/Ventas al exterior.
|
||||
- Concepto AFIP: Products / Definitive export of goods.
|
||||
- Exempt Taxes.
|
||||
- Exempt Taxes.
|
||||
|
||||
.. image:: argentina/argentina_edi_09.png
|
||||
:align: center
|
||||
|
||||
.. note::
|
||||
The Exportation Documents required the Incoterm in :menuselection:`Other Info --> Accounting`:
|
||||
|
||||
|
||||
.. image:: argentina/argentina_edi_13.png
|
||||
:align: center
|
||||
|
||||
|
||||
|
||||
|
||||
Fiscal Bond
|
||||
***********
|
||||
The Electronic Fiscal bond is used for those who invoice capital goods and wish to access
|
||||
The Electronic Fiscal bond is used for those who invoice capital goods and wish to access
|
||||
the benefit of the Electronic Tax Bonds granted by the Ministry of Economy.
|
||||
|
||||
For these transactions it’s important to have into consideration the next requirements:
|
||||
@@ -435,77 +435,77 @@ For these transactions it’s important to have into consideration the next requ
|
||||
- Quantity.
|
||||
- Unit of measurement.
|
||||
- Bonus.
|
||||
- VAT rate.
|
||||
- VAT rate.
|
||||
|
||||
|
||||
Electronic Credit Invoice MiPyme (FCE)
|
||||
Electronic Credit Invoice MiPyme (FCE)
|
||||
**************************************
|
||||
|
||||
**Invoices:** There are several document types classified as Mipyme also known as
|
||||
Electronic Credit Invoice (FCE in spanish), which is used to impulse the SME, its purpose is
|
||||
to develop a mechanism that improves the financing conditions of these companies and allows
|
||||
them to increase their productivity, through the early collection of credits and receivables
|
||||
issued to their clients and / or vendors.
|
||||
Electronic Credit Invoice (FCE in spanish), which is used to impulse the SME, its purpose is
|
||||
to develop a mechanism that improves the financing conditions of these companies and allows
|
||||
them to increase their productivity, through the early collection of credits and receivables
|
||||
issued to their clients and / or vendors.
|
||||
|
||||
For these transactions it’s important to have into consideration the next requirements:
|
||||
|
||||
- Specific document types (201, 202, 206, etc).
|
||||
- The emisor should be eligible by the AFIP to MiPyme transactions.
|
||||
- The amount should be bigger than 100,000 ARS.
|
||||
- A bank account type CBU must be related to the emisor, otherwise the invoice can’t
|
||||
be validated, having these errors messages for example:
|
||||
|
||||
- The emisor should be eligible by the AFIP to MiPyme transactions.
|
||||
- The amount should be bigger than 100,000 ARS.
|
||||
- A bank account type CBU must be related to the emisor, otherwise the invoice can’t
|
||||
be validated, having these errors messages for example:
|
||||
|
||||
.. image:: argentina/argentina_edi_10.png
|
||||
:align: center
|
||||
|
||||
**Credit& Debit Notes:** When creating a Credit/Debit note related to a FCE document, it is
|
||||
**Credit& Debit Notes:** When creating a Credit/Debit note related to a FCE document, it is
|
||||
important take the next points into consideration:
|
||||
|
||||
- Use the Credit and Debit Note buttons, so the correct reference of the originator
|
||||
document passed to the note.
|
||||
- Use the Credit and Debit Note buttons, so the correct reference of the originator
|
||||
document passed to the note.
|
||||
|
||||
.. image:: argentina/argentina_edi_11.png
|
||||
:align: center
|
||||
|
||||
|
||||
- The document letter should be the same than the originator document (either A or B).
|
||||
- The same currency as the source document must be used. When using a secondary currency
|
||||
there is an exchange difference if the currency rate is different between the emission day
|
||||
and the payment date, it’s possible to create a credit/debit note to decrease/increase the
|
||||
amount to pay in ARS.
|
||||
- The same currency as the source document must be used. When using a secondary currency
|
||||
there is an exchange difference if the currency rate is different between the emission day
|
||||
and the payment date, it’s possible to create a credit/debit note to decrease/increase the
|
||||
amount to pay in ARS.
|
||||
|
||||
In the workflow we can have two scenarios:
|
||||
|
||||
#. The FCE is rejected so the Credit Note should have the field “FCE, is Cancellation?” as True.
|
||||
#. The Credit Note, is created with the negative amount to annulate the FCE document,
|
||||
in this case the field “FCE, is Cancellation?” must be empty (false).
|
||||
#. The FCE is rejected so the Credit Note should have the field “FCE, is Cancellation?” as True.
|
||||
#. The Credit Note, is created with the negative amount to annulate the FCE document,
|
||||
in this case the field “FCE, is Cancellation?” must be empty (false).
|
||||
|
||||
.. image:: argentina/argentina_edi_12.png
|
||||
:align: center
|
||||
|
||||
|
||||
Invoice printed report
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
The PDF report related to electronic invoices that have been validated by the AFIP includes
|
||||
a barcode at the bottom of the format which represent the CAE number, the Expiration Date is
|
||||
also displayed as it’s legal requirement:
|
||||
|
||||
The PDF report related to electronic invoices that have been validated by the AFIP includes
|
||||
a barcode at the bottom of the format which represent the CAE number, the Expiration Date is
|
||||
also displayed as it’s legal requirement:
|
||||
|
||||
.. image:: argentina/argentina_edi_14.png
|
||||
:align: center
|
||||
|
||||
|
||||
Troubleshooting and Auditing
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
For auditing and troubleshooting purposes you can get the detailed information of an
|
||||
invoice number that has been previously sent to the AFIP,
|
||||
For auditing and troubleshooting purposes you can get the detailed information of an
|
||||
invoice number that has been previously sent to the AFIP,
|
||||
|
||||
.. image:: argentina/argentina_edi_23.png
|
||||
:align: center
|
||||
|
||||
|
||||
.. image:: argentina/argentina_edi_24.png
|
||||
:align: center
|
||||
:align: center
|
||||
|
||||
|
||||
You can also get the last number used in AFIP for a specific Document Type and POS Number
|
||||
as support for any possible issues on the sequence synchronization between Odoo and AFIP.
|
||||
You can also get the last number used in AFIP for a specific Document Type and POS Number
|
||||
as support for any possible issues on the sequence synchronization between Odoo and AFIP.
|
||||
|
||||
.. image:: argentina/argentina_edi_22.png
|
||||
:align: center
|
||||
@@ -514,8 +514,8 @@ as support for any possible issues on the sequence synchronization between Odoo
|
||||
Vendor Bills
|
||||
------------
|
||||
|
||||
Based on the purchase journal selected for the vendor bill, the document type is now a required field.
|
||||
This value is auto populated based on the AFIP Responsibility type of Issuer and Customer, but the
|
||||
Based on the purchase journal selected for the vendor bill, the document type is now a required field.
|
||||
This value is auto populated based on the AFIP Responsibility type of Issuer and Customer, but the
|
||||
value can be switched if necessary.
|
||||
|
||||
.. image:: argentina/argentina16.png
|
||||
@@ -528,20 +528,20 @@ expected.
|
||||
.. image:: argentina/argentina17.png
|
||||
:align: center
|
||||
|
||||
The vendor bill number is structured in the same way that the invoices with the difference
|
||||
The vendor bill number is structured in the same way that the invoices with the difference
|
||||
that the document sequence is input by the user: “Document Prefix - Letter - Document number".
|
||||
|
||||
|
||||
Validate Vendor Bill number in AFIP
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
As most companies have internal controls to verify that the vendor bill is related to an AFIP
|
||||
valid document, an automatic validation can be set in :menuselection:`Accounting --> Settings -->
|
||||
Argentinian Localization --> Validate document in the AFIP`, considering the following levels:
|
||||
valid document, an automatic validation can be set in :menuselection:`Accounting --> Settings -->
|
||||
Argentinian Localization --> Validate document in the AFIP`, considering the following levels:
|
||||
|
||||
- **Not available:** The verification is not done (this is the default value).
|
||||
- **Available:** The verification is done, in case the number is not valid
|
||||
it only raises a warning but it allows you to post the vendor bill.
|
||||
- **Required:** The verification is done and it doesn't allow the user to
|
||||
- **Available:** The verification is done, in case the number is not valid
|
||||
it only raises a warning but it allows you to post the vendor bill.
|
||||
- **Required:** The verification is done and it doesn't allow the user to
|
||||
post the vendor bill if the document number is not valid.
|
||||
|
||||
.. image:: argentina/argentina_edi_16.png
|
||||
@@ -549,13 +549,13 @@ Argentinian Localization --> Validate document in the AFIP`, considering the fol
|
||||
|
||||
How to use it in Odoo
|
||||
*********************
|
||||
This tool incorporates in the vendor bill a new "Verify on AFIP" button located
|
||||
next to the AFIP Authorization code.
|
||||
This tool incorporates in the vendor bill a new "Verify on AFIP" button located
|
||||
next to the AFIP Authorization code.
|
||||
|
||||
.. image:: argentina/argentina_edi_17.png
|
||||
:align: center
|
||||
|
||||
In case it’s not a valid AFIP authorization the value “Rejected” will be
|
||||
In case it’s not a valid AFIP authorization the value “Rejected” will be
|
||||
displayed and the details of the validation will be added to the chatter.
|
||||
|
||||
.. image:: argentina/argentina_edi_18.png
|
||||
@@ -566,8 +566,8 @@ Special Use cases
|
||||
~~~~~~~~~~~~~~~~~
|
||||
Untaxed Concepts
|
||||
****************
|
||||
There are some transactions that include items that are not part of the VAT base amount,
|
||||
this is commonly used in fuel and gasoline invoices.
|
||||
There are some transactions that include items that are not part of the VAT base amount,
|
||||
this is commonly used in fuel and gasoline invoices.
|
||||
|
||||
The vendor bill will be registered using 1 item for each product that is part of the VAT
|
||||
base amount and an additional item to register the amount of the Exempt concept:
|
||||
@@ -577,23 +577,23 @@ base amount and an additional item to register the amount of the Exempt concept
|
||||
|
||||
Perception Taxes
|
||||
****************
|
||||
The vendor bill will be registered using 1 item for each product that is part of the
|
||||
VAT base amount, the perception tax can be added in any of the product lines, as result
|
||||
we will have one tax group for the VAT and one for the perception, the perception default
|
||||
value is always 1.00.
|
||||
The vendor bill will be registered using 1 item for each product that is part of the
|
||||
VAT base amount, the perception tax can be added in any of the product lines, as result
|
||||
we will have one tax group for the VAT and one for the perception, the perception default
|
||||
value is always 1.00.
|
||||
|
||||
.. image:: argentina/argentina_edi_20.png
|
||||
:align: center
|
||||
|
||||
You should use the pencil that is the next to the Perception amount to edit it
|
||||
and set the correct amount.
|
||||
You should use the pencil that is the next to the Perception amount to edit it
|
||||
and set the correct amount.
|
||||
|
||||
.. image:: argentina/argentina_edi_21.png
|
||||
:align: center
|
||||
|
||||
After this is done the invoice can be validated.
|
||||
|
||||
|
||||
|
||||
After this is done the invoice can be validated.
|
||||
|
||||
|
||||
Reports
|
||||
=======
|
||||
|
||||
|
||||
@@ -73,4 +73,4 @@ The accounts used by KeyPay are defined in the section **Payroll settings**.
|
||||
|
||||
For the API to work, you need to create the same accounts as the default accounts of your KeyPay
|
||||
business (**same name and same code**) in Odoo. You also need to choose the correct account types in
|
||||
Odoo to generate accurate financial reports.
|
||||
Odoo to generate accurate financial reports.
|
||||
|
||||
@@ -599,4 +599,4 @@ Medidas en Odoo
|
||||
|
||||
- Los productos que fueron actualizados deberá ser reconfigurados a su IVA original.
|
||||
- En caso de que se detecte alguna Orden de venta facturar en la cual se incluya IVA de Bienes
|
||||
Cubiertos, se deberá realizar actualización manual correspondiente al IVA convencional.
|
||||
Cubiertos, se deberá realizar actualización manual correspondiente al IVA convencional.
|
||||
|
||||
@@ -9,7 +9,7 @@ The chart of accounts SKR03 and SKR04 are both supported in Odoo. You can choose
|
||||
one you want by going in :menuselection:`Accounting --> Configuration` then choose the
|
||||
package you want in the Fiscal Localization section.
|
||||
|
||||
Be careful, you can only change the accounting package as long as you have not created any accounting entry.
|
||||
Be careful, you can only change the accounting package as long as you have not created any accounting entry.
|
||||
|
||||
.. tip::
|
||||
|
||||
@@ -20,7 +20,7 @@ German Accounting Reports
|
||||
|
||||
Here is the list of German-specific reports available on Odoo Enterprise:
|
||||
|
||||
- Balance Sheet
|
||||
- Balance Sheet
|
||||
- Profit & Loss
|
||||
- Tax Report (Umsatzsteuervoranmeldung)
|
||||
- Partner VAT Intra
|
||||
@@ -330,4 +330,4 @@ What happens if you are not compliant?
|
||||
--------------------------------------
|
||||
|
||||
In the event of an infringement, you can expect a fine but also a court order demanding the
|
||||
implementation of specific measures.
|
||||
implementation of specific measures.
|
||||
|
||||
@@ -125,4 +125,4 @@ Correct an invoice that has been posted but not downloaded yet: Reset e-Faktur
|
||||
and re-assign a new serial number.
|
||||
|
||||
.. image:: indonesia/indonesia-e-faktur-reset.png
|
||||
:align: center
|
||||
:align: center
|
||||
|
||||
@@ -37,7 +37,7 @@ Give Odoo permission to process files
|
||||
Since the files are transmitted through Odoo's server before being sent to SDICoop or received by
|
||||
your database, you need to authorize Odoo to process your files from your database.
|
||||
|
||||
To do this, go to :menuselection:`Accounting --> Settings --> Electronic Invoicing` and click on
|
||||
To do this, go to :menuselection:`Accounting --> Settings --> Electronic Invoicing` and click on
|
||||
*Register*.
|
||||
|
||||
.. image:: italy/register.png
|
||||
|
||||
@@ -128,4 +128,3 @@ cliccare su invia. Il documento verrà poi mostrato tra gli allegati.
|
||||
|
||||
.. image:: italy_IT/italy_IT06.png
|
||||
:align: center
|
||||
|
||||
|
||||
@@ -5,20 +5,20 @@ Peru
|
||||
Introduction
|
||||
============
|
||||
|
||||
The Peruvian localization has been improved and extended, in this version the next modules are
|
||||
The Peruvian localization has been improved and extended, in this version the next modules are
|
||||
available:
|
||||
|
||||
- **l10n_pe**: Adds accounting features for the Peruvian localization, which represent the minimal
|
||||
configuration required for a company to operate in Peru and under the SUNAT regulations and
|
||||
guidelines. The main elements included in this module are: Chart of account, taxes,
|
||||
document types.
|
||||
configuration required for a company to operate in Peru and under the SUNAT regulations and
|
||||
guidelines. The main elements included in this module are: Chart of account, taxes,
|
||||
document types.
|
||||
|
||||
- **l10n_pe_edi**: includes all technical and functional requirements to generate and validate
|
||||
Electronic Invoice, based on the SUNAT specification to create and process valid electronic
|
||||
documents, for more technical detail you can access the
|
||||
- **l10n_pe_edi**: includes all technical and functional requirements to generate and validate
|
||||
Electronic Invoice, based on the SUNAT specification to create and process valid electronic
|
||||
documents, for more technical detail you can access the
|
||||
`SUNAT EDI specifications <https://cpe.sunat.gob.pe/node/88/>`_,
|
||||
that keeps track of new changes and updates.
|
||||
The features of this module are based on the resolutions published on the
|
||||
that keeps track of new changes and updates.
|
||||
The features of this module are based on the resolutions published on the
|
||||
`SUNAT Legislation <https://www.sunat.gob.pe/legislacion/general/index.html/>`_.
|
||||
|
||||
Configuration
|
||||
@@ -27,24 +27,24 @@ Configuration
|
||||
Install the Peruvian localization modules
|
||||
-----------------------------------------
|
||||
|
||||
Go to *Apps* and search for Peru, then click Install in the module Peru EDI. This module has a
|
||||
Go to *Apps* and search for Peru, then click Install in the module Peru EDI. This module has a
|
||||
dependency with *Peru - Accounting*. In case this last one is not installed, Odoo installs it
|
||||
automatically within EDI.
|
||||
|
||||
.. image:: peru/peru-modules.png
|
||||
:align: center
|
||||
:alt: The "Module" filter is set on "Peru"
|
||||
:alt: The "Module" filter is set on "Peru"
|
||||
|
||||
.. note::
|
||||
When you install a database from scratch selecting Peru as country, Odoo automatically
|
||||
When you install a database from scratch selecting Peru as country, Odoo automatically
|
||||
installs the base module: Peru - Accounting.
|
||||
|
||||
|
||||
Configure your company
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
In addition to the basic information in the Company, we need to set Peru as the Country, this is
|
||||
essential for the Electronic Invoice to work properly. The field **Address Type Code** represents
|
||||
the establishment code assigned by the SUNAT when companies register their RUC (Unique Contributor
|
||||
essential for the Electronic Invoice to work properly. The field **Address Type Code** represents
|
||||
the establishment code assigned by the SUNAT when companies register their RUC (Unique Contributor
|
||||
Registration):
|
||||
|
||||
.. image:: peru/peru-company.png
|
||||
@@ -53,18 +53,18 @@ Registration):
|
||||
|
||||
|
||||
.. tip::
|
||||
In case the Address type code is unknown, you can set it as the default value: 0000. Be aware
|
||||
that if an incorrect value is entered, the Electronic invoice validation might have errors.
|
||||
|
||||
In case the Address type code is unknown, you can set it as the default value: 0000. Be aware
|
||||
that if an incorrect value is entered, the Electronic invoice validation might have errors.
|
||||
|
||||
.. note::
|
||||
The NIF should be set following the RUC format.
|
||||
|
||||
|
||||
|
||||
Chart of Account
|
||||
~~~~~~~~~~~~~~~~
|
||||
|
||||
The chart of accounts is installed by default as part of the set of data included in the
|
||||
localization module, the accounts are mapped automatically in:
|
||||
The chart of accounts is installed by default as part of the set of data included in the
|
||||
localization module, the accounts are mapped automatically in:
|
||||
|
||||
- Taxes
|
||||
- Default Account Payable.
|
||||
@@ -77,20 +77,20 @@ accounting.
|
||||
Accounting Settings
|
||||
-------------------
|
||||
|
||||
Once the modules are installed and the basic information of your company is set, you need to
|
||||
configure the elements required for Electronic Invoice. For this, go to :menuselection:`Accounting
|
||||
Once the modules are installed and the basic information of your company is set, you need to
|
||||
configure the elements required for Electronic Invoice. For this, go to :menuselection:`Accounting
|
||||
--> Settings --> Peruvian Localization`.
|
||||
|
||||
Basic Concepts
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
Here are some terms that are essential on the Peruvian localization:
|
||||
Here are some terms that are essential on the Peruvian localization:
|
||||
|
||||
- **EDI**: Electronic Data Interchange, which in this refers to the Electronic Invoice.
|
||||
- **EDI**: Electronic Data Interchange, which in this refers to the Electronic Invoice.
|
||||
- **SUNAT**: is the organization that enforces customs and taxation in Peru.
|
||||
- **OSE**: Electronic Service Operator, `OSE SUNAT's definition
|
||||
- **OSE**: Electronic Service Operator, `OSE SUNAT's definition
|
||||
<https://cpe.sunat.gob.pe/aliados/ose#:~:text=El%20Operador%20de%20Servicios%20Electr%C3%B3nicos%20(OSE)%20es%20qui%C3%A9n%20se%20encarga,otro%20documento%20que%20se%20emita>`_.
|
||||
- **CDR**: Receipt certificate (Constancia de Recepción).
|
||||
- **CDR**: Receipt certificate (Constancia de Recepción).
|
||||
- **SOL Credentials**: Sunat Operaciones en Línea. User and password are provided by the SUNAT and
|
||||
grant access to Online Operations systems.
|
||||
|
||||
@@ -112,12 +112,12 @@ IAP (Odoo In-App Purchase)
|
||||
**************************
|
||||
|
||||
This is the default and the suggested option, considering the digital ceritificate is included as
|
||||
part of the service.
|
||||
part of the service.
|
||||
|
||||
.. image:: peru/peru-IAP.png
|
||||
:align: center
|
||||
:alt: IAP option as signature providers
|
||||
|
||||
|
||||
What is the IAP?
|
||||
^^^^^^^^^^^^^^^^
|
||||
|
||||
@@ -146,34 +146,34 @@ Package.
|
||||
| 20,000 | 440 |
|
||||
+---------+-----+
|
||||
|
||||
The credits are consumed per each document that is sent to the OSE.
|
||||
The credits are consumed per each document that is sent to the OSE.
|
||||
|
||||
.. important::
|
||||
If you have a validation error and the document needs to be sent one more time, one additional
|
||||
credit will be charged. Therefore, it is paramount that you verify all information is correct
|
||||
If you have a validation error and the document needs to be sent one more time, one additional
|
||||
credit will be charged. Therefore, it is paramount that you verify all information is correct
|
||||
before sending your document to the OSE.
|
||||
|
||||
What do you need to do?
|
||||
^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
- In Odoo, once your enterprise contract is activated and you start working in Production, you
|
||||
- In Odoo, once your enterprise contract is activated and you start working in Production, you
|
||||
need to buy credits once the first 1000 are consumed.
|
||||
- As Digiflow is the OSE used in the IAP, you need to affiliate it as the official OSE for your
|
||||
- As Digiflow is the OSE used in the IAP, you need to affiliate it as the official OSE for your
|
||||
company on the SUNAT website. This is a simple process. For more information, please check
|
||||
`OSE Affiliation guide
|
||||
`OSE Affiliation guide
|
||||
<https://drive.google.com/file/d/1BkrMTZIiJyi5XI0lGMi3rbMzHddOL1pa/view?usp=sharing>`_.
|
||||
- Register Digiflow as the authorized PSE, please check
|
||||
`PSE Affiliation guide
|
||||
`PSE Affiliation guide
|
||||
<https://drive.google.com/file/d/1QZoqWvtQERpS0pqp6LcKmw7EBlm9EroU/view?usp=sharing>`_.
|
||||
|
||||
Digiflow
|
||||
********
|
||||
|
||||
This option can be used as an alternative, instead of using the IAP services you can send your
|
||||
This option can be used as an alternative, instead of using the IAP services you can send your
|
||||
document validation directly to Digiflow. In this case you need to consider:
|
||||
|
||||
- Buy your own digital Certificate: For more detail regarding the official vendor list, and the
|
||||
process to acquire it, please refer to `SUNAT Digital Ceritifcates
|
||||
- Buy your own digital Certificate: For more detail regarding the official vendor list, and the
|
||||
process to acquire it, please refer to `SUNAT Digital Ceritifcates
|
||||
<https://cpe.sunat.gob.pe/informacion_general/certificados_digitales/>`_.
|
||||
- Sign a service agreement directly with `Digiflow <https://www.digiflow.pe/>`_.
|
||||
- Provide your SOL credentials.
|
||||
@@ -185,14 +185,14 @@ document validation directly to Digiflow. In this case you need to consider:
|
||||
SUNAT
|
||||
*****
|
||||
|
||||
In case your company wants to sign directly with the SUNAT, it is possible to select this option
|
||||
In case your company wants to sign directly with the SUNAT, it is possible to select this option
|
||||
in your configuration. In this case you need to consider:
|
||||
- Get the SUNAT Certification process accepted.
|
||||
|
||||
- Buy your own digital Certificate: For more detail regarding the official vendor list, and the
|
||||
process to acquire it, please refer to `SUNAT Digital Ceritifcates
|
||||
- Buy your own digital Certificate: For more detail regarding the official vendor list, and the
|
||||
process to acquire it, please refer to `SUNAT Digital Ceritifcates
|
||||
<https://cpe.sunat.gob.pe/informacion_general/certificados_digitales/>`_.
|
||||
|
||||
|
||||
- Provide you SOL credentials.
|
||||
|
||||
.. important::
|
||||
@@ -202,14 +202,14 @@ in your configuration. In this case you need to consider:
|
||||
Testing environment
|
||||
~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Odoo provides a testing environment that can be activated before your company goes into production.
|
||||
Odoo provides a testing environment that can be activated before your company goes into production.
|
||||
|
||||
When using the testing environment and the IAP signature, you don’t need to buy testing credits
|
||||
When using the testing environment and the IAP signature, you don’t need to buy testing credits
|
||||
for your transactions as all of them are validated by default.
|
||||
|
||||
.. tip::
|
||||
By default the databases are set to work on production, make sure to enable the testing mode
|
||||
if needed.
|
||||
By default the databases are set to work on production, make sure to enable the testing mode
|
||||
if needed.
|
||||
|
||||
Certificate
|
||||
~~~~~~~~~~~
|
||||
@@ -221,17 +221,17 @@ password.
|
||||
.. image:: peru/peru-Certificate.png
|
||||
:align: center
|
||||
:alt: EDI Certificate wizard
|
||||
|
||||
|
||||
Multicurrency
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
The official currency exchange rate in Peru is provided by the Bank of Peru. Odoo can connect
|
||||
The official currency exchange rate in Peru is provided by the Bank of Peru. Odoo can connect
|
||||
directly to its services and get the currency rate either automatically or manually.
|
||||
|
||||
.. image:: peru/peru-multicurrency.png
|
||||
:align: center
|
||||
:alt: Bank of Peru is displayed in Multicurrency Service option
|
||||
|
||||
|
||||
Please refer to the next section in our documentation for more information about
|
||||
:doc:`multicurrencies <../../others/multi_currency>`.
|
||||
|
||||
@@ -241,7 +241,7 @@ Configure Master data
|
||||
Taxes
|
||||
~~~~~
|
||||
|
||||
As part of the localization module the taxes are created automatically with their related
|
||||
As part of the localization module the taxes are created automatically with their related
|
||||
financial account and electronic invoice configuration.
|
||||
|
||||
.. image:: peru/peru-taxes.png
|
||||
@@ -251,9 +251,9 @@ financial account and electronic invoice configuration.
|
||||
EDI Configuration
|
||||
*****************
|
||||
|
||||
As part of the taxes configuration, there are three new fields required for electronic invoice,
|
||||
the taxes created by default have this data included, but in case you create new taxes make
|
||||
sure you fill in the fields:
|
||||
As part of the taxes configuration, there are three new fields required for electronic invoice,
|
||||
the taxes created by default have this data included, but in case you create new taxes make
|
||||
sure you fill in the fields:
|
||||
|
||||
.. image:: peru/peru-taxes-edi.png
|
||||
:align: center
|
||||
@@ -272,15 +272,15 @@ There are two main fiscal positions included by default when you install the Per
|
||||
Document Types
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
In some Latin American countries, including Peru, some accounting transactions like invoices and
|
||||
vendor bills are classified by document types, defined by the government fiscal authorities, in
|
||||
this case by the SUNAT.
|
||||
In some Latin American countries, including Peru, some accounting transactions like invoices and
|
||||
vendor bills are classified by document types, defined by the government fiscal authorities, in
|
||||
this case by the SUNAT.
|
||||
|
||||
Each document type can have a unique sequence per journal where it is assigned. As part of the
|
||||
localization, the Document Type includes the country on which the document is applicable;the data
|
||||
Each document type can have a unique sequence per journal where it is assigned. As part of the
|
||||
localization, the Document Type includes the country on which the document is applicable;the data
|
||||
is created automatically when the localization module is installed.
|
||||
|
||||
The information required for the document types is included by default so the user does not need
|
||||
|
||||
The information required for the document types is included by default so the user does not need
|
||||
to fill anything on this view:
|
||||
|
||||
.. image:: peru/peru-document-type.png
|
||||
@@ -288,7 +288,7 @@ to fill anything on this view:
|
||||
:alt: Document Type list
|
||||
|
||||
.. warning::
|
||||
Currently the documents supported on customer invoices are: Invoice, Boleta, Debit Note and
|
||||
Currently the documents supported on customer invoices are: Invoice, Boleta, Debit Note and
|
||||
Credit Note.
|
||||
|
||||
Journals
|
||||
@@ -297,17 +297,17 @@ Journals
|
||||
When creating Sales Journals, the following information must be filled, in addition to the standard
|
||||
fields on the Journals:
|
||||
|
||||
Use Documents
|
||||
Use Documents
|
||||
*************
|
||||
|
||||
This field is used to define if the journal uses Document Types. It is only applicable to
|
||||
Purchase and Sales journals, which are the ones that can be related to the different set of
|
||||
document types available in Peru. By default, all the sales journals created use documents.
|
||||
This field is used to define if the journal uses Document Types. It is only applicable to
|
||||
Purchase and Sales journals, which are the ones that can be related to the different set of
|
||||
document types available in Peru. By default, all the sales journals created use documents.
|
||||
|
||||
Electronic Data Interchange
|
||||
***************************
|
||||
|
||||
This section indicates which EDI workflow is used in the invoice, for Peru we must select
|
||||
This section indicates which EDI workflow is used in the invoice, for Peru we must select
|
||||
“Peru UBL 2.1”.
|
||||
|
||||
.. image:: peru/peru-journal-edi.png
|
||||
@@ -323,8 +323,8 @@ Partner
|
||||
Identification Type and VAT
|
||||
***************************
|
||||
|
||||
As part of the Peruvian localization, the identification types defined by the SUNAT are now
|
||||
available on the Partner form, this information is essential for most transactions either on
|
||||
As part of the Peruvian localization, the identification types defined by the SUNAT are now
|
||||
available on the Partner form, this information is essential for most transactions either on
|
||||
the sender company and in the customer, make sure you fill in this information in your records.
|
||||
|
||||
.. image:: peru/peru-id-type.png
|
||||
@@ -335,8 +335,8 @@ the sender company and in the customer, make sure you fill in this information i
|
||||
Product
|
||||
~~~~~~~
|
||||
|
||||
Additional to the basic information in your products, for the Peruvian localization, the UNSPC
|
||||
Code on the product is a required value to be configured.
|
||||
Additional to the basic information in your products, for the Peruvian localization, the UNSPC
|
||||
Code on the product is a required value to be configured.
|
||||
|
||||
.. image:: peru/peru-unspc-code.png
|
||||
:align: center
|
||||
@@ -354,27 +354,27 @@ EDI Elements
|
||||
|
||||
Once you have configured your master data, the invoices can be created from your sales order or
|
||||
manually. Additional to the basic invoice information described on :doc:`our page about the
|
||||
invoicing process <../../receivables/customer_invoices/overview>`, there are a couple of fields
|
||||
invoicing process <../../receivables/customer_invoices/overview>`, there are a couple of fields
|
||||
required as part of the Peru EDI:
|
||||
|
||||
- **Document type**: The default value is “Factura Electronica” but you can manually change the
|
||||
document type if needed and select Boleta for example.
|
||||
- **Document type**: The default value is “Factura Electronica” but you can manually change the
|
||||
document type if needed and select Boleta for example.
|
||||
|
||||
.. image:: peru/peru-invoice-document-type.png
|
||||
:align: center
|
||||
:alt: Invoice document type field on invoices
|
||||
|
||||
- **Operation type**: This value is required for Electronic Invoice and indicates the transaction
|
||||
type, the default value is “Internal Sale” but another value can be selected manually when needed,
|
||||
for example Export of Goods.
|
||||
- **Operation type**: This value is required for Electronic Invoice and indicates the transaction
|
||||
type, the default value is “Internal Sale” but another value can be selected manually when needed,
|
||||
for example Export of Goods.
|
||||
|
||||
.. image:: peru/peru-operation-type.png
|
||||
:align: center
|
||||
:alt: Invoice operation type field on invoices
|
||||
|
||||
- **EDI Affectation Reason**: In the invoice lines, additional to the Tax there is a field “EDI
|
||||
Affectation Reason” that determines the tax scope based on the SUNAT list that is displayed.
|
||||
All the taxes loaded by default are associated with a default EDI affection reason, if needed
|
||||
- **EDI Affectation Reason**: In the invoice lines, additional to the Tax there is a field “EDI
|
||||
Affectation Reason” that determines the tax scope based on the SUNAT list that is displayed.
|
||||
All the taxes loaded by default are associated with a default EDI affection reason, if needed
|
||||
you can manually select another one when creating the invoice.
|
||||
|
||||
.. image:: peru/peru-tax-affectation-reason.png
|
||||
@@ -385,70 +385,70 @@ Invoice validation
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Once you check all the information in your invoice is correct, you can proceed to validate it. This
|
||||
action registers the account move and triggers the Electronic invoice workflow to send it to the
|
||||
action registers the account move and triggers the Electronic invoice workflow to send it to the
|
||||
OSE and the SUNAT. The following message is displayed at the top of the invoice:
|
||||
|
||||
.. image:: peru/peru-posted-invoice.png
|
||||
:align: center
|
||||
:alt: Sending of EDI Invoice in blue
|
||||
|
||||
Asynchronous means that the document is not sent automatically after the invoice has been posted.
|
||||
Asynchronous means that the document is not sent automatically after the invoice has been posted.
|
||||
|
||||
Electronic Invoice Status
|
||||
*************************
|
||||
|
||||
**To be Sent**: To be sent: Indicates the document is ready to be sent to the OSE, this can be
|
||||
done either automatically by Odoo with a *cron* that runs every hour, or the user can send it
|
||||
**To be Sent**: To be sent: Indicates the document is ready to be sent to the OSE, this can be
|
||||
done either automatically by Odoo with a *cron* that runs every hour, or the user can send it
|
||||
immediately by clicking on the button “Sent now”.
|
||||
|
||||
.. image:: peru/peru-sent-manual.png
|
||||
:align: center
|
||||
:alt: Send EDI manually
|
||||
|
||||
**Sent**: Indicates the document was sent to the OSE and was successfully validated. As part of
|
||||
the validation a ZIP file is downloaded and a message is logged in the chatter indicating the
|
||||
correct Government validation.
|
||||
**Sent**: Indicates the document was sent to the OSE and was successfully validated. As part of
|
||||
the validation a ZIP file is downloaded and a message is logged in the chatter indicating the
|
||||
correct Government validation.
|
||||
|
||||
.. image:: peru/peru-invoice-sent.png
|
||||
:align: center
|
||||
:alt: Message on chatter when the invoice is valid
|
||||
|
||||
In case there is a validation error the Electronic Invoice status remains in “To be sent” so the
|
||||
corrections can be made and the invoice can be sent again.
|
||||
In case there is a validation error the Electronic Invoice status remains in “To be sent” so the
|
||||
corrections can be made and the invoice can be sent again.
|
||||
|
||||
.. warning::
|
||||
One credit is consumed each time that you send a document for validation, in this sense if an
|
||||
error is detected on an invoice and you send it one more time, two credits are consumed in
|
||||
One credit is consumed each time that you send a document for validation, in this sense if an
|
||||
error is detected on an invoice and you send it one more time, two credits are consumed in
|
||||
total.
|
||||
|
||||
Common Errors
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
There are multiple reasons behind a rejection from the OSE or the SUNAT, when this happens Odoo
|
||||
sends a message at the top of the invoice indicating the error details and in the most common
|
||||
cases a hint to fix the issue.
|
||||
There are multiple reasons behind a rejection from the OSE or the SUNAT, when this happens Odoo
|
||||
sends a message at the top of the invoice indicating the error details and in the most common
|
||||
cases a hint to fix the issue.
|
||||
|
||||
If a validation error is received, you have two options:
|
||||
If a validation error is received, you have two options:
|
||||
|
||||
- In case the error is related to master data on the partner, customer or taxes, you can simply
|
||||
apply the change on the record (example customer identification type) and once it is done click
|
||||
on the Retry button.
|
||||
- If the error is related to some data recorded on the invoice directly (Operation type, missing
|
||||
data on the invoice lines), the correct solution is to reset the invoice to Draft, apply the
|
||||
changes, and then send the invoice again to the SUNAT for another validation.
|
||||
apply the change on the record (example customer identification type) and once it is done click
|
||||
on the Retry button.
|
||||
- If the error is related to some data recorded on the invoice directly (Operation type, missing
|
||||
data on the invoice lines), the correct solution is to reset the invoice to Draft, apply the
|
||||
changes, and then send the invoice again to the SUNAT for another validation.
|
||||
|
||||
.. image:: peru/peru-errors.png
|
||||
:align: center
|
||||
:alt: List of common errors on invoices
|
||||
|
||||
|
||||
For more detail please refert to `Common errors in SUNAT
|
||||
For more detail please refert to `Common errors in SUNAT
|
||||
<https://www.nubefact.com/codigos-error-sunat/>`_.
|
||||
|
||||
Invoice PDF Report
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
After the invoice is accepted and validated by the SUNAT, the invoice PDF report can be printed.
|
||||
After the invoice is accepted and validated by the SUNAT, the invoice PDF report can be printed.
|
||||
The report includes a QR code, indicating the invoice is a valid fiscal document.
|
||||
|
||||
.. image:: peru/peru-PDF.png
|
||||
@@ -458,18 +458,18 @@ The report includes a QR code, indicating the invoice is a valid fiscal document
|
||||
IAP Credits
|
||||
~~~~~~~~~~~
|
||||
|
||||
Odoo’s Electronic IAP offers 1000 credits for free, after these credits are consumed in your
|
||||
production database, your company must buy new credits in order to process your transactions.
|
||||
Odoo’s Electronic IAP offers 1000 credits for free, after these credits are consumed in your
|
||||
production database, your company must buy new credits in order to process your transactions.
|
||||
|
||||
Once you run out of credits a red label is displayed at the top of the invoice indicating that
|
||||
additional credits are required, you can easily buy them by accessing the link provided in
|
||||
the message.
|
||||
Once you run out of credits a red label is displayed at the top of the invoice indicating that
|
||||
additional credits are required, you can easily buy them by accessing the link provided in
|
||||
the message.
|
||||
|
||||
.. image:: peru/peru-credits-IAP.png
|
||||
:align: center
|
||||
:alt: Buying credits in the IAP
|
||||
|
||||
In the IAP service includes packages with different pricing based on the number of credits.
|
||||
In the IAP service includes packages with different pricing based on the number of credits.
|
||||
The price list in the IAP is always displayed in EUR.
|
||||
|
||||
Special Use cases
|
||||
@@ -478,30 +478,30 @@ Special Use cases
|
||||
Cancellation process
|
||||
********************
|
||||
|
||||
Some scenarios require an invoice cancellation, for example, when an invoice was created by mistake.
|
||||
If the invoice was already sent and validated by the SUNAT, the correct way to proceed is by
|
||||
Some scenarios require an invoice cancellation, for example, when an invoice was created by mistake.
|
||||
If the invoice was already sent and validated by the SUNAT, the correct way to proceed is by
|
||||
clicking on the button Request Cancellation:
|
||||
|
||||
.. image:: peru/peru-cancellation.png
|
||||
:align: center
|
||||
:alt: Request invoice cancellation button
|
||||
|
||||
In order to cancel an invoice, please provide a cancellation Reason.
|
||||
In order to cancel an invoice, please provide a cancellation Reason.
|
||||
|
||||
Electronic Invoice Status
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
**To Cancel**: Indicates the cancellation request is ready to be sent to the OSE, this can be done
|
||||
either automatically by Odoo with a *cron* that runs every hour, or the user can send it
|
||||
immediately by clicking on the button “Send now”. Once it is sent, a cancellation ticket is
|
||||
**To Cancel**: Indicates the cancellation request is ready to be sent to the OSE, this can be done
|
||||
either automatically by Odoo with a *cron* that runs every hour, or the user can send it
|
||||
immediately by clicking on the button “Send now”. Once it is sent, a cancellation ticket is
|
||||
created, as a result the next message and CDR File are logged in the chatter:
|
||||
|
||||
.. image:: peru/peru-cancellation-cdr.png
|
||||
:align: center
|
||||
:alt: Cancellation CDR sent by the SUNAT
|
||||
|
||||
**Cancelled**: Indicates the cancellation request was sent to the OSE and was successfully
|
||||
validated. As part of the validation a ZIP file is downloaded and a message is logged in the
|
||||
|
||||
**Cancelled**: Indicates the cancellation request was sent to the OSE and was successfully
|
||||
validated. As part of the validation a ZIP file is downloaded and a message is logged in the
|
||||
chatter indicating the correct Government validation.
|
||||
|
||||
.. image:: peru/peru-cancelled.png
|
||||
@@ -510,14 +510,14 @@ chatter indicating the correct Government validation.
|
||||
|
||||
.. warning::
|
||||
One credit is consumed on each cancellation request.
|
||||
|
||||
|
||||
Cancellation process
|
||||
********************
|
||||
|
||||
When creating exportation invoices, take into account the next considerations:
|
||||
|
||||
- The Identification type on your customer must be Foreign ID.
|
||||
- Operation type in your invoice must be an Exportation one.
|
||||
- The Identification type on your customer must be Foreign ID.
|
||||
- Operation type in your invoice must be an Exportation one.
|
||||
- The taxes included in the invoice lines should be EXP taxes.
|
||||
|
||||
.. image:: peru/peru-exp-invoice.png
|
||||
@@ -527,24 +527,24 @@ When creating exportation invoices, take into account the next considerations:
|
||||
Advance Payments
|
||||
****************
|
||||
|
||||
#. Create the advance payment Invoice and apply its related payment.
|
||||
#. Create the final invoice without considering the advance payment.
|
||||
#. Create a credit note for the Final invoice with the advance payment amount.
|
||||
#. Reconcile the Credit note with the final invoice.
|
||||
#. The remaining balance on the final invoice should be paid with a regular payment transaction.
|
||||
#. Create the advance payment Invoice and apply its related payment.
|
||||
#. Create the final invoice without considering the advance payment.
|
||||
#. Create a credit note for the Final invoice with the advance payment amount.
|
||||
#. Reconcile the Credit note with the final invoice.
|
||||
#. The remaining balance on the final invoice should be paid with a regular payment transaction.
|
||||
|
||||
|
||||
Detraction Invoices
|
||||
Detraction Invoices
|
||||
********************
|
||||
|
||||
When creating invoices that is subject to Detractions, take into account the next considerations:
|
||||
When creating invoices that is subject to Detractions, take into account the next considerations:
|
||||
|
||||
#. All the products included in the invoice must have these fields configured:
|
||||
#. All the products included in the invoice must have these fields configured:
|
||||
|
||||
.. image:: peru/peru-detraction.png
|
||||
:align: center
|
||||
:alt: Detraction fields on products
|
||||
|
||||
|
||||
#. Operation type in your invoice must be ``1001``
|
||||
|
||||
.. image:: peru/peru-detraction-invoice.png
|
||||
@@ -554,8 +554,8 @@ When creating invoices that is subject to Detractions, take into account the nex
|
||||
Credit Notes
|
||||
------------
|
||||
|
||||
When a correction or refund is needed over a validated invoice, a credit note must be generated,
|
||||
for this just click on the button “Add Credit Note”, a part of the Peruvian localization you need
|
||||
When a correction or refund is needed over a validated invoice, a credit note must be generated,
|
||||
for this just click on the button “Add Credit Note”, a part of the Peruvian localization you need
|
||||
to prove a Credit Reason selecting one of the options in the list.
|
||||
|
||||
.. image:: peru/peru-credit-note.png
|
||||
@@ -563,9 +563,9 @@ to prove a Credit Reason selecting one of the options in the list.
|
||||
:alt: Add Credit Note from invoice
|
||||
|
||||
.. tip::
|
||||
When creating your first credit Note, select the Credit Method: Partial Refund, this allows you
|
||||
to define the credit note sequence.
|
||||
|
||||
When creating your first credit Note, select the Credit Method: Partial Refund, this allows you
|
||||
to define the credit note sequence.
|
||||
|
||||
By default the Credit Note is set in the document type:
|
||||
|
||||
.. image:: peru/peru-credit-note-document.png
|
||||
@@ -576,13 +576,13 @@ To finish the workflow please follow the instructions on :doc:`our page about Cr
|
||||
<../../receivables/customer_invoices/credit_notes>`.
|
||||
|
||||
.. note::
|
||||
The EDI workflow for the Credit notes works in the same way as the invoices.
|
||||
The EDI workflow for the Credit notes works in the same way as the invoices.
|
||||
|
||||
|
||||
Debit Notes
|
||||
------------
|
||||
|
||||
As part of the Peruvian localization, besides creating credit notes from an existing document
|
||||
As part of the Peruvian localization, besides creating credit notes from an existing document
|
||||
you can also create debit Notes. For this just use the button “Add Debit Note”.
|
||||
|
||||
By default the Debit Note is set in the document type.
|
||||
|
||||
@@ -9,12 +9,12 @@ In Odoo, there are several Spanish Chart of Accounts that are available by defau
|
||||
|
||||
- PGCE PYMEs 2008
|
||||
- PGCE Completo 2008
|
||||
- PGCE Entitades
|
||||
- PGCE Entitades
|
||||
|
||||
You can choose the one you want by going in :menuselection:`Accounting --> Configuration`
|
||||
then choose the package you want in the **Fiscal Localization** section.
|
||||
then choose the package you want in the **Fiscal Localization** section.
|
||||
|
||||
Be careful, you can only change the accounting package as long as you have not created any accounting entry.
|
||||
Be careful, you can only change the accounting package as long as you have not created any accounting entry.
|
||||
|
||||
.. tip::
|
||||
When you create a new Odoo Online database, the PGCE PYMEs 2008 is installed by default.
|
||||
@@ -24,8 +24,7 @@ Spanish Accounting Reports
|
||||
|
||||
If the Spanish Accounting Localization is installed, you will have access to accounting reports specific to Spain:
|
||||
|
||||
- Balance Sheet
|
||||
- Balance Sheet
|
||||
- Tax Report (Modelo 111)
|
||||
- Tax Report (Modelo 115)
|
||||
- Tax Report (Modelo 303)
|
||||
|
||||
- Tax Report (Modelo 303)
|
||||
|
||||
@@ -12,7 +12,7 @@ called *Print ISR*.
|
||||
.. image:: switzerland/switzerland00.png
|
||||
:align: center
|
||||
|
||||
.. tip::
|
||||
.. tip::
|
||||
The button *Print ISR* only appears there is well a bank account
|
||||
defined on the invoice. You can use CH6309000000250097798 as bank
|
||||
account number and 010391391 as CHF ISR reference.
|
||||
@@ -142,4 +142,4 @@ odoo.com/help.
|
||||
.. tip::
|
||||
Don't forget to update your fiscal positions. If you have a version
|
||||
11.1 (or higher), there is nothing to do. Otherwise, you will also
|
||||
have to update your fiscal positions accordingly.
|
||||
have to update your fiscal positions accordingly.
|
||||
|
||||
@@ -8,4 +8,4 @@ Overview
|
||||
:titlesonly:
|
||||
|
||||
overview/fiscal_localization_packages
|
||||
overview/localizations_list
|
||||
overview/localizations_list
|
||||
|
||||
@@ -41,4 +41,4 @@ Please refer to the documentation listed below for more information.
|
||||
- :doc:`../../getting_started/initial_configuration/chart_of_accounts`
|
||||
- :doc:`../../taxation/taxes/taxes`
|
||||
|
||||
.. todo:: update list of linked docs, and link with the future one about country-specific statements.
|
||||
.. todo:: update list of linked docs, and link with the future one about country-specific statements.
|
||||
|
||||
@@ -83,4 +83,4 @@ Fiscal localization packages available
|
||||
- Vietnam - Accounting
|
||||
|
||||
.. seealso::
|
||||
- :doc:`fiscal_localization_packages`
|
||||
- :doc:`fiscal_localization_packages`
|
||||
|
||||
@@ -191,4 +191,4 @@ Send yourself a sample invoice by email to make sure everything is correctly con
|
||||
* :doc:`chart_of_accounts`
|
||||
* :doc:`../../bank/feeds/bank_synchronization`
|
||||
* :doc:`../../fiscal_localizations/overview/fiscal_localization_packages`
|
||||
* `Odoo Tutorials: Accounting Basics <https://www.odoo.com/r/lsZ>`_
|
||||
* `Odoo Tutorials: Accounting Basics <https://www.odoo.com/r/lsZ>`_
|
||||
|
||||
@@ -17,7 +17,7 @@ From Vendor Bill to Payment
|
||||
Record a new vendor bill
|
||||
------------------------
|
||||
|
||||
When a vendor bill is received, you can record it from :menuselection:`Purchases --> Vendor Bills`
|
||||
When a vendor bill is received, you can record it from :menuselection:`Purchases --> Vendor Bills`
|
||||
in the Accounting application. As a shortcut,
|
||||
you can also use the **New Bill** feature on the accounting dashboard.
|
||||
|
||||
@@ -36,12 +36,12 @@ Save the invoice to update the pre tax and tax amounts at the bottom of
|
||||
the screen. You will most likely need to configure the prices of your
|
||||
products without taxes as Odoo will compute the tax for you.
|
||||
|
||||
.. note::
|
||||
On the bottom left corner, Odoo shows a summary table of all taxes on the vendor bill.
|
||||
In several countries, different methods are accepted to round the totals (round per line,
|
||||
or round globally). The default rounding method in Odoo is to round the final prices
|
||||
per line (as you may have different taxes per product. E.g. Alcohol and cigarettes).
|
||||
However if your vendor has a different tax amount on their bill, you can change the
|
||||
.. note::
|
||||
On the bottom left corner, Odoo shows a summary table of all taxes on the vendor bill.
|
||||
In several countries, different methods are accepted to round the totals (round per line,
|
||||
or round globally). The default rounding method in Odoo is to round the final prices
|
||||
per line (as you may have different taxes per product. E.g. Alcohol and cigarettes).
|
||||
However if your vendor has a different tax amount on their bill, you can change the
|
||||
amount in the bottom left table to adjust and match.
|
||||
|
||||
Validate The Vendor Bill
|
||||
@@ -91,8 +91,8 @@ if set it correctly).
|
||||
|
||||
|
||||
.. note::
|
||||
You can also register a payment to a vendor directly without applying it to a vendor bill.
|
||||
To do that, :menuselection:`Purchases --> Payments`. Then,
|
||||
You can also register a payment to a vendor directly without applying it to a vendor bill.
|
||||
To do that, :menuselection:`Purchases --> Payments`. Then,
|
||||
from the vendor bill you will be able to reconcile this payment with directly.
|
||||
|
||||
Printing vendor Checks
|
||||
@@ -141,4 +141,4 @@ while you're looking through the report, you can print directly to Excel
|
||||
or PDF and get exactly what you see on the screen.
|
||||
|
||||
.. seealso::
|
||||
* :doc:`customer_invoice`
|
||||
* :doc:`customer_invoice`
|
||||
|
||||
@@ -10,4 +10,4 @@ Others
|
||||
others/multi_currency
|
||||
others/analytic
|
||||
others/adviser
|
||||
others/inventory
|
||||
others/inventory
|
||||
|
||||
@@ -7,4 +7,4 @@ Adviser
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
adviser/budget
|
||||
adviser/budget
|
||||
|
||||
@@ -7,9 +7,9 @@ Overview
|
||||
|
||||
Managing budgets is an essential part of running a business. Budgets help
|
||||
people become more intentional with the way money is spent and direct people
|
||||
to organize and prioritize their work to meet financial goals. They allows
|
||||
you to plan your desired financial outcome and then measure your actual
|
||||
performance against the plan. Odoo manages budgets using both General and Analytic
|
||||
to organize and prioritize their work to meet financial goals. They allows
|
||||
you to plan your desired financial outcome and then measure your actual
|
||||
performance against the plan. Odoo manages budgets using both General and Analytic
|
||||
Accounts.
|
||||
|
||||
We will use the following example to illustrate. We just started a
|
||||
@@ -17,7 +17,7 @@ project with Smith&Co and we would like to budget the incomes and
|
||||
expenses of that project. We plan to have a revenue of 1000 and we don't
|
||||
want to spend more than 700.
|
||||
|
||||
Configuration
|
||||
Configuration
|
||||
=============
|
||||
|
||||
First we need to install the relevant apps to use budgeting. The main
|
||||
@@ -40,17 +40,17 @@ Budgetary Positions
|
||||
Budgetary positions are lists of accounts for which you want to keep
|
||||
budgets (typically expense or income accounts). They need to be defined
|
||||
so Odoo can know it which accounts he needs to go get the budget
|
||||
information.
|
||||
information.
|
||||
|
||||
The budgetary positions act as a type of restriction on what can be recorded
|
||||
in the 'practical amount' column in a budget.
|
||||
|
||||
Each budgetary position can have any number of accounts from the general
|
||||
ledger (the main chart of accounts) assigned to it, though it must have at least one.
|
||||
Each budgetary position can have any number of accounts from the general
|
||||
ledger (the main chart of accounts) assigned to it, though it must have at least one.
|
||||
|
||||
If you record a transaction that has an analytic account assigned to it that *is*
|
||||
included in a budget line but one of the general ledger accounts *is not* included
|
||||
in the budgetary position for that same budget line, it will not appear within the
|
||||
If you record a transaction that has an analytic account assigned to it that *is*
|
||||
included in a budget line but one of the general ledger accounts *is not* included
|
||||
in the budgetary position for that same budget line, it will not appear within the
|
||||
'practical amount' column of that budget line.
|
||||
|
||||
Some budgetary positions might be already installed with your chart of
|
||||
@@ -155,4 +155,3 @@ purchase lines booked in the accounts and will display them in the
|
||||
is 1200 for 12 months (january to december), and today is 31 of january, the
|
||||
theoretical amount will be 100, since this is the actual amount that could
|
||||
have been realised.
|
||||
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
=====================================================
|
||||
How to do a year end in Odoo? (close a fiscal year)
|
||||
=====================================================
|
||||
=====================================================
|
||||
|
||||
@@ -9,4 +9,4 @@ Analytic
|
||||
|
||||
analytic/usage
|
||||
analytic/timesheets
|
||||
analytic/purchases_expenses
|
||||
analytic/purchases_expenses
|
||||
|
||||
@@ -19,7 +19,7 @@ First, install the three applications necessary to use this
|
||||
functionality, namely **Accounting**, **Sales** and **Timesheet**. Enter the apps
|
||||
module name and install them.
|
||||
|
||||
.. image:: timesheets/timesheets14.png
|
||||
.. image:: timesheets/timesheets14.png
|
||||
:align: center
|
||||
|
||||
.. image:: timesheets/timesheets05.png
|
||||
@@ -51,14 +51,14 @@ cost of 18 euros / hours. We will thus fill in 18 in this field.
|
||||
.. image:: timesheets/timesheets07.png
|
||||
:align: center
|
||||
|
||||
.. note::
|
||||
.. note::
|
||||
If you want the employee to be able to enter timesheets he
|
||||
needs to be related to a User.
|
||||
|
||||
Repeat the operation to create the Cedric Digory employee. Don't forget
|
||||
to specify its related user and **Timesheet Costs**.
|
||||
|
||||
Issue a Sales Order
|
||||
Issue a Sales Order
|
||||
--------------------
|
||||
|
||||
We created two employees called Harry Potter and Cedric Diggory in the
|
||||
@@ -121,7 +121,7 @@ Without filters
|
||||
|
||||
If we pointed all our costs and revenues of the project on the correct
|
||||
analytical account we can easily retrieve the cost and revenues related
|
||||
to this analytical account. Enter the *Accounting* app, select
|
||||
to this analytical account. Enter the *Accounting* app, select
|
||||
:menuselection:`Adviser --> Analytic Accounts --> Open Charts`.
|
||||
|
||||
Note : you can specify a period for **Analysis**. If you want to open the
|
||||
|
||||
@@ -7,4 +7,4 @@ Miscellaneous
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
misc/forecast
|
||||
misc/forecast
|
||||
|
||||
@@ -48,4 +48,4 @@ sure to apply the :doc:`payment terms <../../receivables/customer_invoices/payme
|
||||
**bills** *instead* of the invoices.
|
||||
|
||||
.. seealso::
|
||||
:doc:`../../receivables/customer_invoices/payment_terms`
|
||||
:doc:`../../receivables/customer_invoices/payment_terms`
|
||||
|
||||
@@ -13,11 +13,11 @@ Iceland, Norway, Switzerland, Andorra, Monaco and San Marino.
|
||||
With Odoo, once you decide to pay a vendor, you can select to pay the
|
||||
bill with SEPA. Then, at the end of the day, the manager can generate
|
||||
the SEPA file containing all bank wire transfers and send it to the
|
||||
bank.
|
||||
bank.
|
||||
|
||||
By default,the file follows the SEPA Credit Transfer **'pain.001.001.03'**
|
||||
specifications. This is a well-defined standard that makes consensus
|
||||
among banks. However, according to the country set on your company,
|
||||
among banks. However, according to the country set on your company,
|
||||
another format can be used : **'pain.001.001.03.ch.02'** for Switzerland
|
||||
and **'pain.001.003.03'** for Germany.
|
||||
|
||||
|
||||
@@ -253,4 +253,4 @@ You have three choices for the **Automate Assets** field:
|
||||
fully automate its purchase. (see: :ref:`product-assets-account`).
|
||||
|
||||
.. seealso::
|
||||
* :doc:`../../getting_started/initial_configuration/chart_of_accounts`
|
||||
* :doc:`../../getting_started/initial_configuration/chart_of_accounts`
|
||||
|
||||
@@ -192,4 +192,4 @@ You have three choices for the **Automate Deferred Expense** field:
|
||||
products`_).
|
||||
|
||||
.. seealso::
|
||||
* :doc:`../../getting_started/initial_configuration/chart_of_accounts`
|
||||
* :doc:`../../getting_started/initial_configuration/chart_of_accounts`
|
||||
|
||||
@@ -94,4 +94,4 @@ and click on :guilabel:`Buy credits`, or go to :menuselection:`Settings --> Odoo
|
||||
|
||||
.. seealso::
|
||||
- `Our Privacy Policy <https://iap.odoo.com/privacy#header_6>`_
|
||||
- :doc:`/applications/general/in_app_purchase`
|
||||
- :doc:`/applications/general/in_app_purchase`
|
||||
|
||||
@@ -65,4 +65,4 @@ match the payment with the two related journal entries.
|
||||
|
||||
.. seealso::
|
||||
* :doc:`../../receivables/customer_invoices/payment_terms`
|
||||
* :doc:`../../bank/reconciliation/reconciliation_models`
|
||||
* :doc:`../../bank/reconciliation/reconciliation_models`
|
||||
|
||||
@@ -3,11 +3,11 @@ Cash rounding
|
||||
=============
|
||||
|
||||
**Cash rounding** is required when the lowest physical denomination
|
||||
of currency, or the smallest coin, is higher than the minimum unit
|
||||
of currency, or the smallest coin, is higher than the minimum unit
|
||||
of account.
|
||||
|
||||
For example, some countries require their companies to round up or
|
||||
down the total amount of an invoice to the nearest five cents, when
|
||||
For example, some countries require their companies to round up or
|
||||
down the total amount of an invoice to the nearest five cents, when
|
||||
the payment is made in cash.
|
||||
|
||||
Configuration
|
||||
@@ -19,22 +19,22 @@ and enable *Cash Rounding*, then click on *Save*.
|
||||
.. image:: cash_rounding/cash_rounding01.png
|
||||
:align: center
|
||||
|
||||
Go to :menuselection:`Accounting --> Configuration --> Cash Roundings`,
|
||||
Go to :menuselection:`Accounting --> Configuration --> Cash Roundings`,
|
||||
and click on *Create*.
|
||||
|
||||
Define here your *Rounding Precision*, *Rounding Strategy*, and
|
||||
Define here your *Rounding Precision*, *Rounding Strategy*, and
|
||||
*Rounding Method*.
|
||||
|
||||
Odoo supports two **rounding strategies**:
|
||||
|
||||
1. **Add a rounding line**: a *rounding* line is added on the invoice.
|
||||
1. **Add a rounding line**: a *rounding* line is added on the invoice.
|
||||
You have to define which account records the cash roundings.
|
||||
|
||||
|
||||
2. **Modify tax amount**: the rounding is applied in the taxes section.
|
||||
|
||||
Apply roundings
|
||||
===============
|
||||
|
||||
When editing a draft invoice, open the *Other Info* tab, go to the
|
||||
*Accounting Information* section, and select the appropriate *Cash
|
||||
Rounding Method*.
|
||||
*Accounting Information* section, and select the appropriate *Cash
|
||||
Rounding Method*.
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
========================
|
||||
Credit notes and refunds
|
||||
========================
|
||||
A **credit note**, or **credit memo**, is a document issued
|
||||
to a customer that notifies them that they have been credited
|
||||
A **credit note**, or **credit memo**, is a document issued
|
||||
to a customer that notifies them that they have been credited
|
||||
a certain amount.
|
||||
|
||||
There are several reasons that can lead to a credit note, such as:
|
||||
@@ -11,19 +11,19 @@ There are several reasons that can lead to a credit note, such as:
|
||||
* the goods delivered are damaged
|
||||
|
||||
.. note::
|
||||
Issuing a credit note is the only legal way to cancel,
|
||||
refund or modify a validated invoice. Don’t forget to
|
||||
Issuing a credit note is the only legal way to cancel,
|
||||
refund or modify a validated invoice. Don’t forget to
|
||||
*register the payment* afterward if you need to send money
|
||||
back to your customer.
|
||||
|
||||
Issue a Credit Note
|
||||
===================
|
||||
You can create a credit note from scratch by going to
|
||||
:menuselection:`Accounting --> Customers --> Credit Notes`,
|
||||
and by clicking on *Create*. Filling the Credit Note’s form
|
||||
You can create a credit note from scratch by going to
|
||||
:menuselection:`Accounting --> Customers --> Credit Notes`,
|
||||
and by clicking on *Create*. Filling the Credit Note’s form
|
||||
works the same way as the Invoice’s form.
|
||||
|
||||
However, most of the time, credit notes are generated directly
|
||||
However, most of the time, credit notes are generated directly
|
||||
from the invoices they are related to.
|
||||
|
||||
To do so, open the *Customer Invoice*, and click on *Add Credit Note*.
|
||||
@@ -37,15 +37,15 @@ You can choose between three options:
|
||||
- Full refund and new draft invoice
|
||||
|
||||
.. note::
|
||||
Credit Notes’ numbers start with “R” and are followed by the
|
||||
number of the document they are related to (e.g., RINV/2019/0004).
|
||||
Credit Notes’ numbers start with “R” and are followed by the
|
||||
number of the document they are related to (e.g., RINV/2019/0004).
|
||||
|
||||
Partial Refund
|
||||
--------------
|
||||
Odoo creates a draft credit note already prefilled with all the
|
||||
Odoo creates a draft credit note already prefilled with all the
|
||||
necessary information from the original invoice.
|
||||
|
||||
This is the option to choose to do a partial refund, or if you
|
||||
This is the option to choose to do a partial refund, or if you
|
||||
want to modify any detail on the credit note.
|
||||
|
||||
.. note::
|
||||
@@ -53,19 +53,19 @@ want to modify any detail on the credit note.
|
||||
|
||||
Full Refund
|
||||
-----------
|
||||
Odoo creates a credit note, automatically validates it, and
|
||||
Odoo creates a credit note, automatically validates it, and
|
||||
reconciles the original invoice with it.
|
||||
|
||||
.. image:: credit_notes/credit_notes02.png
|
||||
:align: center
|
||||
|
||||
This is the option to choose to do a full refund or cancel
|
||||
This is the option to choose to do a full refund or cancel
|
||||
a validated invoice.
|
||||
|
||||
Full refund and new draft invoice
|
||||
---------------------------------
|
||||
Odoo creates a credit note, automatically validates it, reconciles
|
||||
the original invoice with it, and open a new draft invoice
|
||||
Odoo creates a credit note, automatically validates it, reconciles
|
||||
the original invoice with it, and open a new draft invoice
|
||||
prefilled with the same details from the original invoice.
|
||||
|
||||
This is the option to choose to modify the content of a validated invoice.
|
||||
@@ -74,22 +74,22 @@ Record a Vendor Refund
|
||||
======================
|
||||
**Vendor Refunds** are recorded the same way you would do with invoices’ credit notes:
|
||||
|
||||
You can either create a credit note from scratch by going
|
||||
to :menuselection:`Accounting --> Vendors --> Refund`, and
|
||||
by clicking on *Create*, or by opening the validated *Vendor Bill*,
|
||||
You can either create a credit note from scratch by going
|
||||
to :menuselection:`Accounting --> Vendors --> Refund`, and
|
||||
by clicking on *Create*, or by opening the validated *Vendor Bill*,
|
||||
and clicking on *Add Credit Note*.
|
||||
|
||||
|
||||
Journal Entries
|
||||
===============
|
||||
Issuing a credit note from an invoice creates a **reverse entry**
|
||||
that zeroes out the journal items generated by the original invoice.
|
||||
Issuing a credit note from an invoice creates a **reverse entry**
|
||||
that zeroes out the journal items generated by the original invoice.
|
||||
|
||||
Here is an example of an invoice’s journal entry:
|
||||
|
||||
.. image:: credit_notes/credit_notes03.png
|
||||
:align: center
|
||||
|
||||
And here is the credit note’s journal entry generated to reverse
|
||||
And here is the credit note’s journal entry generated to reverse
|
||||
the original invoice above:
|
||||
|
||||
.. image:: credit_notes/credit_notes04.png
|
||||
|
||||
@@ -42,7 +42,7 @@ Configuration --> Chart of Accounts`, click on *Create*, and fill out the form.
|
||||
|
||||
.. note::
|
||||
This account's type must be either *Current Liabilities* or *Non-current Liabilities*
|
||||
|
||||
|
||||
Post an income to the right account
|
||||
-----------------------------------
|
||||
|
||||
@@ -64,7 +64,7 @@ save.
|
||||
|
||||
.. image:: deferred_revenues/deferred_revenues03.png
|
||||
:align: center
|
||||
:alt: Change of the Income Account for a product in Odoo
|
||||
:alt: Change of the Income Account for a product in Odoo
|
||||
|
||||
.. tip::
|
||||
It is possible to automate the creation of revenue entries for these products (see:
|
||||
@@ -75,11 +75,11 @@ Change the account of a posted journal item
|
||||
|
||||
To do so, open your Sales Journal by going to
|
||||
:menuselection:`Accounting --> Accounting --> Sales`, select the journal item you
|
||||
want to modify, click on the account, and select the right one.
|
||||
want to modify, click on the account, and select the right one.
|
||||
|
||||
.. image:: deferred_revenues/deferred_revenues04.png
|
||||
:align: center
|
||||
:alt: Modification of a posted journal item's account in Odoo Accounting
|
||||
:alt: Modification of a posted journal item's account in Odoo Accounting
|
||||
|
||||
Deferred Revenues entries
|
||||
=========================
|
||||
@@ -107,8 +107,8 @@ recognize your revenue, and at which date.
|
||||
|
||||
.. image:: deferred_revenues/deferred_revenues06.png
|
||||
:align: center
|
||||
:alt: Revenue Board in Odoo Accounting
|
||||
|
||||
:alt: Revenue Board in Odoo Accounting
|
||||
|
||||
What does "Prorata Temporis" mean?
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
@@ -126,7 +126,7 @@ Deferred Entry from the Sales Journal
|
||||
|
||||
You can create a deferred entry from a specific journal item in your **Sales Journal**.
|
||||
|
||||
To do so, open your Sales Journal by going to
|
||||
To do so, open your Sales Journal by going to
|
||||
:menuselection:`Accounting --> Accounting --> Sales`, and select the journal item you want to defer.
|
||||
Make sure that it is posted in the right account (see:
|
||||
`Change the account of a posted journal item`_).
|
||||
@@ -192,4 +192,4 @@ You have three choices for the **Automate Deferred Revenue** field:
|
||||
|
||||
.. seealso::
|
||||
* :doc:`../../getting_started/initial_configuration/chart_of_accounts`
|
||||
* `Odoo Academy: Deferred Revenues (Recognition) <https://www.odoo.com/r/EWO>`_
|
||||
* `Odoo Academy: Deferred Revenues (Recognition) <https://www.odoo.com/r/EWO>`_
|
||||
|
||||
@@ -1,36 +1,36 @@
|
||||
============================
|
||||
Add EPC QR Codes to invoices
|
||||
============================
|
||||
European Payments Council Quick Response Code,
|
||||
or **EPC QR Code**, are two-dimensional barcodes
|
||||
that customers can scan with their **mobile banking
|
||||
European Payments Council Quick Response Code,
|
||||
or **EPC QR Code**, are two-dimensional barcodes
|
||||
that customers can scan with their **mobile banking
|
||||
applications** to initiate a **SEPA Credit Transfer
|
||||
(SCT)**, and pay their invoices instantly.
|
||||
|
||||
In addition to bringing ease of use and speed,
|
||||
it greatly reduces typing errors that would potentially
|
||||
make for payment issues.
|
||||
In addition to bringing ease of use and speed,
|
||||
it greatly reduces typing errors that would potentially
|
||||
make for payment issues.
|
||||
|
||||
.. note::
|
||||
This feature is only available in several European
|
||||
countries such as Austria, Belgium, Finland, Germany,
|
||||
This feature is only available in several European
|
||||
countries such as Austria, Belgium, Finland, Germany,
|
||||
and The Netherlands.
|
||||
|
||||
|
||||
Configuration
|
||||
=============
|
||||
Go to :menuselection:`Accounting --> Configuration --> Settings`
|
||||
Go to :menuselection:`Accounting --> Configuration --> Settings`
|
||||
and activate the **SEPA QR Code** feature.
|
||||
|
||||
.. image:: epc_qr_code/epc_qr_code01.png
|
||||
:align: center
|
||||
|
||||
|
||||
Configure your Bank Account’s journal
|
||||
-------------------------------------
|
||||
Make sure that your *Bank Account* is correctly configured
|
||||
Make sure that your *Bank Account* is correctly configured
|
||||
on Odoo with your IBAN and BIC.
|
||||
|
||||
To do so, go to :menuselection:`Accounting --> Configuration
|
||||
--> Journals`, open your *bank journal*, then fill out the
|
||||
To do so, go to :menuselection:`Accounting --> Configuration
|
||||
--> Journals`, open your *bank journal*, then fill out the
|
||||
*Bank Account* and *Bank* under the *Bank Account* tab.
|
||||
|
||||
.. image:: epc_qr_code/epc_qr_code02.png
|
||||
@@ -38,28 +38,28 @@ To do so, go to :menuselection:`Accounting --> Configuration
|
||||
|
||||
Issue Invoices with EPC QR Codes
|
||||
================================
|
||||
EPC QR Codes are added automatically to your invoices, as
|
||||
long as you issue them to customers that are located in a
|
||||
EPC QR Codes are added automatically to your invoices, as
|
||||
long as you issue them to customers that are located in a
|
||||
country where this feature is available.
|
||||
|
||||
Go to :menuselection:`Accounting --> Customers --> Invoices`,
|
||||
and create a new invoice.
|
||||
Go to :menuselection:`Accounting --> Customers --> Invoices`,
|
||||
and create a new invoice.
|
||||
|
||||
Before posting it, open the *Other Info* tab. Odoo automatically
|
||||
Before posting it, open the *Other Info* tab. Odoo automatically
|
||||
fills out the *Bank Account* field with your IBAN.
|
||||
|
||||
Make sure that the account indicated is the one you want to use to
|
||||
receive your customer’s payment as Odoo uses this field to generate
|
||||
Make sure that the account indicated is the one you want to use to
|
||||
receive your customer’s payment as Odoo uses this field to generate
|
||||
the EPC QR Code.
|
||||
|
||||
.. image:: epc_qr_code/epc_qr_code03.png
|
||||
:align: center
|
||||
|
||||
|
||||
.. tip::
|
||||
If you want to issue an invoice without an EPC QR Code,
|
||||
remove the IBAN indicated in the *Bank Account* field,
|
||||
If you want to issue an invoice without an EPC QR Code,
|
||||
remove the IBAN indicated in the *Bank Account* field,
|
||||
under the *Other Info* tab of the invoice.
|
||||
|
||||
.. seealso::
|
||||
* :doc:`../../bank/setup/bank_accounts`
|
||||
* `Odoo Academy: QR Code on Invoices for European Customers <https://www.odoo.com/r/VuU>`_
|
||||
* `Odoo Academy: QR Code on Invoices for European Customers <https://www.odoo.com/r/VuU>`_
|
||||
|
||||
@@ -97,4 +97,4 @@ payment before validating the bank reconciliation.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`recording`
|
||||
- :doc:`batch_sdd`
|
||||
- :doc:`batch_sdd`
|
||||
|
||||
@@ -72,7 +72,7 @@ their SEPA Direct Debit mandate.
|
||||
.. todo::
|
||||
Add link to future **Payment Provider** documentation.
|
||||
|
||||
Close or revoke a mandate
|
||||
Close or revoke a mandate
|
||||
-------------------------
|
||||
|
||||
Direct Debit mandates are closed automatically after their *End Date*. If this field is left blank,
|
||||
@@ -95,7 +95,7 @@ included in the next SDD XML file.
|
||||
Get paid with SDD Batch Payments
|
||||
================================
|
||||
|
||||
Customer Invoices
|
||||
Customer Invoices
|
||||
-----------------
|
||||
|
||||
You can register SDD payments for invoices issued to customers who have an active SDD mandate.
|
||||
@@ -146,4 +146,4 @@ Finally, upload this file to your online banking interface to process the paymen
|
||||
* :doc:`../../bank/setup/bank_accounts`
|
||||
* `Odoo Academy: SEPA Direct Debit Mandates (SDD) <https://www.odoo.com/r/Zxs>`_
|
||||
* `List of all SEPA countries
|
||||
<https://www.europeanpaymentscouncil.eu/document-library/other/epc-list-sepa-scheme-countries>`_
|
||||
<https://www.europeanpaymentscouncil.eu/document-library/other/epc-list-sepa-scheme-countries>`_
|
||||
|
||||
@@ -6,14 +6,14 @@ There are two ways to handle payments received by checks. Odoo support
|
||||
both approaches so that you can use the one that better fits your
|
||||
habits.
|
||||
|
||||
1. **Undeposited Funds:**
|
||||
1. **Undeposited Funds:**
|
||||
once you receive the check, you record a payment
|
||||
by check on the invoice. (using a Check journal and posted on the
|
||||
Undeposited Fund account) Then, once the check arrives in your
|
||||
bank account, move money from Undeposited Funds to your bank
|
||||
account.
|
||||
|
||||
2. **One journal entry only:**
|
||||
2. **One journal entry only:**
|
||||
once your receive the check, you record a
|
||||
payment on your bank, paid by check, without going through the
|
||||
**Undeposited Funds**. Once you process your bank statement, you do
|
||||
@@ -28,7 +28,7 @@ Even if the first method is cleaner, Odoo support the second approach
|
||||
because some accountants are used to it (quickbooks and peachtree
|
||||
users).
|
||||
|
||||
.. Note::
|
||||
.. Note::
|
||||
You may have a look at the *Deposit Ticket feature* if you deposit
|
||||
several checks to your bank accounts in batch.
|
||||
|
||||
@@ -90,7 +90,7 @@ If you use this approach to manage received checks, you get the list of
|
||||
checks that have not been cashed in the **Undeposit Funds** account
|
||||
(accessible, for example, from the general ledger).
|
||||
|
||||
.. Note::
|
||||
.. Note::
|
||||
Both methods will produce the same data in your accounting at the
|
||||
end of the process. But, if you have checks that have not been cashed,
|
||||
this one is cleaner because those checks have not been reported yet on
|
||||
@@ -135,7 +135,7 @@ books:
|
||||
| Bank | | 100.00 | |
|
||||
+----------------------+-------------------+----------+----------+
|
||||
|
||||
.. tip::
|
||||
.. tip::
|
||||
You may also record the payment directly without going on the
|
||||
customer invoice, using the menu :menuselection:`Sales --> Payments`. This method may
|
||||
be more convenient if you have a lot of checks to record in a batch but
|
||||
@@ -148,4 +148,4 @@ received or paid by the bank. (this report is available from the **More**
|
||||
option from the Accounting dashboard on the related bank account).
|
||||
|
||||
.. image:: check/check01.png
|
||||
:align: center
|
||||
:align: center
|
||||
|
||||
@@ -20,7 +20,7 @@ Make sure your :ref:`Payment Providers are correctly configured <payment_provide
|
||||
By default, ":doc:`Wire Transfer </applications/finance/payment_providers/wire_transfer>`" is the only
|
||||
Payment Provider activated, but you still have to fill out the payment details.
|
||||
|
||||
To activate the Invoice Online Payment, go to :menuselection:`Accounting --> Configuration -->
|
||||
To activate the Invoice Online Payment, go to :menuselection:`Accounting --> Configuration -->
|
||||
Settings --> Customer Payments`, enable **Invoice Online Payment**, and click on *Save*.
|
||||
|
||||
Customer Portal
|
||||
|
||||
@@ -8,4 +8,4 @@ Reporting
|
||||
:titlesonly:
|
||||
|
||||
reporting/overview
|
||||
reporting/declarations
|
||||
reporting/declarations
|
||||
|
||||
@@ -8,4 +8,4 @@ Declarations
|
||||
:titlesonly:
|
||||
|
||||
declarations/tax_returns
|
||||
declarations/intrastat
|
||||
declarations/intrastat
|
||||
|
||||
@@ -26,4 +26,3 @@ Go to :menuselection:`Accounting --> Settings --> Customer Invoices`, then enabl
|
||||
<general/upgrade>` the ``account_intrastat`` module to add the new transaction codes and
|
||||
:ref:`install <general/install>` the ``account_intrastat_expiry`` module to archive the old
|
||||
codes.
|
||||
|
||||
|
||||
@@ -122,4 +122,4 @@ with the amount you have to pay or be refunded.
|
||||
.. seealso::
|
||||
* :doc:`../../taxation/taxes/taxes`
|
||||
* :doc:`../../getting_started/initial_configuration/setup`
|
||||
* :doc:`../../fiscal_localizations/overview/fiscal_localization_packages`
|
||||
* :doc:`../../fiscal_localizations/overview/fiscal_localization_packages`
|
||||
|
||||
@@ -10,4 +10,4 @@ Overview
|
||||
overview/main_reports
|
||||
overview/customize
|
||||
overview/data_inalterability
|
||||
overview/tax_carryover
|
||||
overview/tax_carryover
|
||||
|
||||
@@ -46,7 +46,7 @@ Add lines in your custom reports
|
||||
=================================
|
||||
|
||||
After you've created the report, you need to fill it with lines. They
|
||||
all need a **name**, a **code** (that is used to refer to the line), a
|
||||
all need a **name**, a **code** (that is used to refer to the line), a
|
||||
**sequence number** and a **level** (Used for the line rendering).
|
||||
|
||||
.. image:: customize/customize04.png
|
||||
|
||||
@@ -60,4 +60,4 @@ corresponding hash.
|
||||
|
||||
.. image:: data_inalterability/data-consistency-check.png
|
||||
:align: center
|
||||
:alt: Data consistency check report for a journal
|
||||
:alt: Data consistency check report for a journal
|
||||
|
||||
@@ -31,7 +31,7 @@ Balance Sheet
|
||||
The **Balance Sheet** shows a snapshot of the assets, liabilities and equity
|
||||
of your organisation as at a particular date.
|
||||
|
||||
.. image:: main_reports/main_reports09.png
|
||||
.. image:: main_reports/main_reports09.png
|
||||
:align: center
|
||||
|
||||
Profit and Loss
|
||||
@@ -41,7 +41,7 @@ The **Profit and Loss** report (or **Income Statement**) shows your
|
||||
organisation's net income, by deducting expenses from revenue for the
|
||||
report period.
|
||||
|
||||
.. image:: main_reports/main_reports10.png
|
||||
.. image:: main_reports/main_reports10.png
|
||||
:align: center
|
||||
|
||||
Executive Summary
|
||||
@@ -58,36 +58,36 @@ reporting :
|
||||
The contribution each individual sale made
|
||||
by your business less any direct costs needed to make those sales
|
||||
(things like labour, materials, etc).
|
||||
- **Net profit margin:**
|
||||
- **Net profit margin:**
|
||||
The contribution each individual sale made by
|
||||
your business less any direct costs needed to make those sales,
|
||||
as well as any fixed overheads your company has (things like
|
||||
rent, electricity, taxes you need to pay as a result of those
|
||||
sales).
|
||||
- **Return on investment (p.a.):**
|
||||
- **Return on investment (p.a.):**
|
||||
The ratio of net profit made, to the
|
||||
amount of assets the company used to make those profits.
|
||||
- **Position:**
|
||||
- **Average debtor days:**
|
||||
- **Average debtor days:**
|
||||
The average number of days it takes your
|
||||
customers to pay you (fully), across all your customer invoices.
|
||||
- **Average creditor days:**
|
||||
The average number of days it takes you to
|
||||
pay your suppliers (fully) across all your bills.
|
||||
- **Short term cash forecast:**
|
||||
- **Short term cash forecast:**
|
||||
How much cash is expected in or out of
|
||||
your organisation in the next month i.e. balance of your **Sales
|
||||
account** for the month less the balance of your **Purchases account**
|
||||
for the month.
|
||||
- **Current assets to liabilities:**
|
||||
Also referred to as **current ratio**, this is the ratio
|
||||
- **Current assets to liabilities:**
|
||||
Also referred to as **current ratio**, this is the ratio
|
||||
of current assets (assets that could be
|
||||
turned into cash within a year) to the current liabilities
|
||||
(liabilities which will be due in the next year). This is
|
||||
typically used as as a measure of a company's ability to service
|
||||
its debt.
|
||||
|
||||
.. image:: main_reports/main_reports01.png
|
||||
.. image:: main_reports/main_reports01.png
|
||||
:align: center
|
||||
|
||||
General Ledger
|
||||
@@ -99,7 +99,7 @@ account and from there you can view a detailed transaction report or any
|
||||
exceptions. This report is useful for checking every transaction that
|
||||
occurred during a certain period of time.
|
||||
|
||||
.. image:: main_reports/main_reports05.png
|
||||
.. image:: main_reports/main_reports05.png
|
||||
:align: center
|
||||
|
||||
Aged Payable
|
||||
@@ -109,7 +109,7 @@ Run the **Aged Payable Details** report to display information on individual
|
||||
bills, credit notes and overpayments owed by you, and how long these
|
||||
have gone unpaid.
|
||||
|
||||
.. image:: main_reports/main_reports02.png
|
||||
.. image:: main_reports/main_reports02.png
|
||||
:align: center
|
||||
|
||||
Aged Receivable
|
||||
@@ -118,7 +118,7 @@ Aged Receivable
|
||||
The **Aged Receivables** report shows the sales invoices that were awaiting
|
||||
payment during a selected month and several months prior.
|
||||
|
||||
.. image:: main_reports/main_reports07.png
|
||||
.. image:: main_reports/main_reports07.png
|
||||
:align: center
|
||||
|
||||
Cash Flow Statement
|
||||
@@ -128,7 +128,7 @@ The **Cash Flow Statement** shows how changes in balance sheet accounts and
|
||||
income affect cash and cash equivalents, and breaks the analysis down to
|
||||
operating, investing and financing activities.
|
||||
|
||||
.. image:: main_reports/main_reports03.png
|
||||
.. image:: main_reports/main_reports03.png
|
||||
:align: center
|
||||
|
||||
Tax Report
|
||||
@@ -137,11 +137,11 @@ Tax Report
|
||||
This report allows you to see the **net** and **tax amounts** for all the taxes
|
||||
grouped by type (sale/purchase).
|
||||
|
||||
.. image:: main_reports/main_reports04.png
|
||||
.. image:: main_reports/main_reports04.png
|
||||
:align: center
|
||||
|
||||
Bank Reconciliation
|
||||
-------------------
|
||||
|
||||
.. image:: main_reports/main_reports06.png
|
||||
.. image:: main_reports/main_reports06.png
|
||||
:align: center
|
||||
|
||||
@@ -8,4 +8,4 @@ Taxation
|
||||
:titlesonly:
|
||||
|
||||
taxation/taxes
|
||||
taxation/fiscal_year
|
||||
taxation/fiscal_year
|
||||
|
||||
@@ -8,4 +8,4 @@ Fiscal year
|
||||
:titlesonly:
|
||||
|
||||
fiscal_year/fiscal_year
|
||||
fiscal_year/close_fiscal_year
|
||||
fiscal_year/close_fiscal_year
|
||||
|
||||
@@ -90,4 +90,4 @@ whether or not the current year earnings in the **Balance Sheet** is
|
||||
correctly reporting a 0 balance.
|
||||
|
||||
.. seealso::
|
||||
* :doc:`fiscal_year`
|
||||
* :doc:`fiscal_year`
|
||||
|
||||
@@ -29,6 +29,6 @@ You can then configure your fiscal years in
|
||||
You only have to create fiscal years if they last more or less
|
||||
than 12 months.
|
||||
|
||||
.. seealso::
|
||||
.. seealso::
|
||||
|
||||
* :doc:`close_fiscal_year`
|
||||
|
||||
@@ -11,9 +11,9 @@ Taxes
|
||||
taxes/default_taxes
|
||||
taxes/fiscal_positions
|
||||
taxes/eu_distance_selling
|
||||
taxes/avatax
|
||||
taxes/avatax
|
||||
taxes/taxcloud
|
||||
taxes/retention
|
||||
taxes/B2B_B2C
|
||||
taxes/cash_basis_taxes
|
||||
taxes/vat_validation
|
||||
taxes/vat_validation
|
||||
|
||||
@@ -114,19 +114,19 @@ Setting your products
|
||||
|
||||
Your company must be configured with tax excluded by default. This is
|
||||
usually the default configuration, but you can check your **Default Sale
|
||||
Tax** from the menu :menuselection:`Configuration --> Settings`
|
||||
Tax** from the menu :menuselection:`Configuration --> Settings`
|
||||
of the Accounting application.
|
||||
|
||||
.. image:: B2B_B2C/price_B2C_B2B01.png
|
||||
:align: center
|
||||
|
||||
Once done, you can create a **B2C** pricelist. You can activate the
|
||||
pricelist feature per customer from the menu:
|
||||
:menuselection:`Configuration --> Settings` of the Sale application.
|
||||
pricelist feature per customer from the menu:
|
||||
:menuselection:`Configuration --> Settings` of the Sale application.
|
||||
Choose the option **different prices per customer segment**.
|
||||
|
||||
Once done, create a B2C pricelist from the menu
|
||||
:menuselection:`Configuration --> Pricelists`.
|
||||
Once done, create a B2C pricelist from the menu
|
||||
:menuselection:`Configuration --> Pricelists`.
|
||||
It's also good to rename the default pricelist into B2B to avoid confusion.
|
||||
|
||||
Then, create a product at 8.26€, with a tax of 21% (defined as tax not
|
||||
@@ -141,8 +141,8 @@ Setting the B2C fiscal position
|
||||
-------------------------------
|
||||
|
||||
From the accounting application, create a B2C fiscal position from this
|
||||
menu: :menuselection:`Configuration --> Fiscal Positions`.
|
||||
This fiscal position should map the VAT 21% (tax excluded of price)
|
||||
menu: :menuselection:`Configuration --> Fiscal Positions`.
|
||||
This fiscal position should map the VAT 21% (tax excluded of price)
|
||||
with a VAT 21% (tax included in price)
|
||||
|
||||
.. image:: B2B_B2C/price_B2C_B2B03.png
|
||||
@@ -151,8 +151,8 @@ with a VAT 21% (tax included in price)
|
||||
Test by creating a quotation
|
||||
============================
|
||||
|
||||
Create a quotation from the Sale application, using the
|
||||
:menuselection:`Sales --> Quotations` menu. You should have the
|
||||
Create a quotation from the Sale application, using the
|
||||
:menuselection:`Sales --> Quotations` menu. You should have the
|
||||
following result: 8.26€ + 1.73€ = 9.99€.
|
||||
|
||||
.. image:: B2B_B2C/price_B2C_B2B04.png
|
||||
|
||||
@@ -37,4 +37,4 @@ To change your **Default Taxes**, go to :menuselection:`Accounting --> Configura
|
||||
|
||||
- :doc:`taxes`
|
||||
- :doc:`fiscal_positions`
|
||||
- :doc:`../../fiscal_localizations/overview/fiscal_localization_packages`
|
||||
- :doc:`../../fiscal_localizations/overview/fiscal_localization_packages`
|
||||
|
||||
@@ -108,4 +108,4 @@ To manually select which Fiscal Position to use for a new Sales Order, Invoice,
|
||||
|
||||
* :doc:`taxes`
|
||||
* :doc:`taxcloud`
|
||||
* :doc:`B2B_B2C`
|
||||
* :doc:`B2B_B2C`
|
||||
|
||||
@@ -40,8 +40,8 @@ Once the tax is defined, you can use it in your products, sales order or
|
||||
invoices.
|
||||
|
||||
.. tip::
|
||||
If the retention is a percentage of a regular tax, create a Tax with a
|
||||
**Tax Computation** as a **Tax Group** and set the two taxes in this group
|
||||
If the retention is a percentage of a regular tax, create a Tax with a
|
||||
**Tax Computation** as a **Tax Group** and set the two taxes in this group
|
||||
(normal tax and retention).
|
||||
|
||||
Applying retention taxes on invoices
|
||||
@@ -55,9 +55,9 @@ invoice line.
|
||||
:align: center
|
||||
|
||||
.. note::
|
||||
When you see the customer invoice on the screen, you get only a
|
||||
**Taxes line** summarizing all the taxes (normal taxes & retentions).
|
||||
But when you print or send the invoice, Odoo does the correct
|
||||
When you see the customer invoice on the screen, you get only a
|
||||
**Taxes line** summarizing all the taxes (normal taxes & retentions).
|
||||
But when you print or send the invoice, Odoo does the correct
|
||||
grouping amongst all the taxes.
|
||||
|
||||
The printed invoice will show the different amounts in each tax group.
|
||||
|
||||
@@ -148,4 +148,4 @@ the tax computation is correct. Indeed, a 3.5% tax on the full price is the equi
|
||||
on half the price, but this might be unexpected from a user point of view.
|
||||
|
||||
.. seealso::
|
||||
:doc:`fiscal_positions`
|
||||
:doc:`fiscal_positions`
|
||||
|
||||
@@ -279,4 +279,4 @@ directly to a product line.
|
||||
- :doc:`fiscal_positions`
|
||||
- :doc:`B2B_B2C`
|
||||
- :doc:`taxcloud`
|
||||
- :doc:`../../reporting/declarations/tax_returns`
|
||||
- :doc:`../../reporting/declarations/tax_returns`
|
||||
|
||||
@@ -40,4 +40,4 @@ VAT number is invalid.
|
||||
|
||||
.. seealso::
|
||||
|
||||
- `European Commission: VIES search engine <https://ec.europa.eu/taxation_customs/vies/vatRequest.html>`__
|
||||
- `European Commission: VIES search engine <https://ec.europa.eu/taxation_customs/vies/vatRequest.html>`__
|
||||
|
||||
@@ -120,4 +120,4 @@ Select the *Actions* tab to set up your action. You can simultaneously:
|
||||
|
||||
.. image:: documents/workflow-action-example.png
|
||||
:align: center
|
||||
:alt: Example of a workflow action Odoo Documents
|
||||
:alt: Example of a workflow action Odoo Documents
|
||||
|
||||
@@ -14,7 +14,7 @@ How to set expense types
|
||||
========================
|
||||
|
||||
The first step to track expenses is to configure the expense types (managed as products in Odoo)
|
||||
that your company allows, from the *Configuration* menu.
|
||||
that your company allows, from the *Configuration* menu.
|
||||
When a specific expense is reimbursed at a fixed price, set a cost on the product.
|
||||
Otherwise keep the cost at 0.0 and employees will report the real cost per expense.
|
||||
|
||||
@@ -37,16 +37,16 @@ Here are some examples:
|
||||
|
||||
* Cost: 0.0
|
||||
|
||||
Don't forget to set an expense tax on each expense type
|
||||
(and an account if you use Odoo Accounting).
|
||||
It's usually a good practice to use a tax that is configured
|
||||
Don't forget to set an expense tax on each expense type
|
||||
(and an account if you use Odoo Accounting).
|
||||
It's usually a good practice to use a tax that is configured
|
||||
with :ref:`Tax Included in Price <taxes/included-in-price>`.
|
||||
That way, employees report expenses with
|
||||
That way, employees report expenses with
|
||||
prices including taxes, which is usually the expected behaviour.
|
||||
|
||||
.. tip::
|
||||
The *Sales* app allows you to specify units of measure for your
|
||||
expense types (units, miles, nights, etc.).
|
||||
.. tip::
|
||||
The *Sales* app allows you to specify units of measure for your
|
||||
expense types (units, miles, nights, etc.).
|
||||
Go to :menuselection:`Sales --> Configuration --> Settings` and check
|
||||
*Some products may be sold/purchased in different units of measure (advanced)*.
|
||||
|
||||
@@ -57,20 +57,20 @@ How to record expenses
|
||||
Manually
|
||||
--------
|
||||
|
||||
As an employee (Employee in user access rights), you can record
|
||||
As an employee (Employee in user access rights), you can record
|
||||
expenses from :menuselection:`My Expenses --> Expenses to Submit`.
|
||||
|
||||
.. image:: expenses/submit_01.png
|
||||
:align: center
|
||||
|
||||
1. Select the related product and enter either the total amount
|
||||
you paid (with Quantity = 1) or the unit price if Quantity is
|
||||
1. Select the related product and enter either the total amount
|
||||
you paid (with Quantity = 1) or the unit price if Quantity is
|
||||
countable (e.g. number of hotel nights).
|
||||
2. Enter the expense date.
|
||||
3. Choose if you paid the bill on your own (and expect to be reimbursed)
|
||||
3. Choose if you paid the bill on your own (and expect to be reimbursed)
|
||||
or if the company paid directly (e.g. if you used a company's credit card).
|
||||
4. Set the bill reference, add some notes if requested and attach a
|
||||
photo/scan of the receipt from the discussion thread.
|
||||
4. Set the bill reference, add some notes if requested and attach a
|
||||
photo/scan of the receipt from the discussion thread.
|
||||
That will help the manager and the accountant validate it.
|
||||
|
||||
.. image:: expenses/submit_02.png
|
||||
@@ -79,56 +79,56 @@ expenses from :menuselection:`My Expenses --> Expenses to Submit`.
|
||||
In one click from emails
|
||||
------------------------
|
||||
|
||||
Let your employees record their expenses from a simple email.
|
||||
Let your employees record their expenses from a simple email.
|
||||
Make a snapshot of the receipt and send it by email, or simply forward a bill!
|
||||
|
||||
The only thing to do is setting up an email alias in
|
||||
:menuselection:`Expenses --> Configuration --> Settings` (e.g. *expenses* @mycompany.odoo.com).
|
||||
For security purposes, only authenticated employee emails
|
||||
The only thing to do is setting up an email alias in
|
||||
:menuselection:`Expenses --> Configuration --> Settings` (e.g. *expenses* @mycompany.odoo.com).
|
||||
For security purposes, only authenticated employee emails
|
||||
(cfr. *Work Email* in employee detail form) are accepted.
|
||||
|
||||
.. tip::
|
||||
The expense product is set automatically if the mail subject contains
|
||||
The expense product is set automatically if the mail subject contains
|
||||
the product's internal reference in first position.
|
||||
Type the expense amount in the mail subject to set it on the expense too (e.g. Ref001 Food 100€).
|
||||
|
||||
How to submit expenses to managers
|
||||
==================================
|
||||
|
||||
When you are ready to submit your expenses to your manager
|
||||
(e.g. at the end of a business trip, or once a month),
|
||||
go to the menu :menuselection:`My Expenses --> Expenses to Submit`. Select all expenses
|
||||
When you are ready to submit your expenses to your manager
|
||||
(e.g. at the end of a business trip, or once a month),
|
||||
go to the menu :menuselection:`My Expenses --> Expenses to Submit`. Select all expenses
|
||||
from the list view and click on :menuselection:`Action --> Submit to Manager`.
|
||||
Save the newly created expense report (i.e. set of expenses),
|
||||
Save the newly created expense report (i.e. set of expenses),
|
||||
and wait for your manager to approve it.
|
||||
|
||||
.. image:: expenses/submit_03.png
|
||||
:align: center
|
||||
|
||||
You can also submit expenses one by one from the *Submit to Manager*
|
||||
You can also submit expenses one by one from the *Submit to Manager*
|
||||
button on the form view of an expense.
|
||||
|
||||
All your submitted expense reports can be found in
|
||||
All your submitted expense reports can be found in
|
||||
:menuselection:`Expenses --> My Expenses --> Expense Reports`.
|
||||
|
||||
|
||||
How to approve expenses
|
||||
=======================
|
||||
|
||||
HR and team managers get an overview of all expense reports to
|
||||
validate from the top menu :menuselection:`To Approve --> Expense Reports to Approve`.
|
||||
HR and team managers get an overview of all expense reports to
|
||||
validate from the top menu :menuselection:`To Approve --> Expense Reports to Approve`.
|
||||
Such users must have at least *Officers* access rights for *Expenses*.
|
||||
|
||||
.. image:: expenses/approval_01.png
|
||||
:align: center
|
||||
|
||||
They can review expense reports, approve or reject them, as well as providing
|
||||
They can review expense reports, approve or reject them, as well as providing
|
||||
feedback thanks to the integrated communication tool.
|
||||
|
||||
.. image:: expenses/approval_02.png
|
||||
:align: center
|
||||
|
||||
As a team manager you can easily find the expense reports of your team members.
|
||||
As a team manager you can easily find the expense reports of your team members.
|
||||
You need to be set as manager in the detail form of those employees.
|
||||
|
||||
.. image:: expenses/approval_03.png
|
||||
@@ -138,27 +138,27 @@ You need to be set as manager in the detail form of those employees.
|
||||
How to post expenses in accounting
|
||||
==================================
|
||||
|
||||
Once expense reports approved by managers, the accounting department
|
||||
goes to :menuselection:`Expenses --> Accountant --> Expense Reports To Post` to check
|
||||
accounts, products and taxes. They can click *Post Journal Entries*
|
||||
to post related journal entries into your books.
|
||||
Once expense reports approved by managers, the accounting department
|
||||
goes to :menuselection:`Expenses --> Accountant --> Expense Reports To Post` to check
|
||||
accounts, products and taxes. They can click *Post Journal Entries*
|
||||
to post related journal entries into your books.
|
||||
To do so, the user must have following access rights:
|
||||
|
||||
* Accounting: Accountant or Adviser
|
||||
* Expenses: Manager
|
||||
|
||||
.. note::
|
||||
To post an expense, a *Home Address* must be set on the employee.
|
||||
If you get a related blocking message when posting, click the employee,
|
||||
go to *Personal Information* tab and select/create the contact of your employee
|
||||
in the address book.
|
||||
To post an expense, a *Home Address* must be set on the employee.
|
||||
If you get a related blocking message when posting, click the employee,
|
||||
go to *Personal Information* tab and select/create the contact of your employee
|
||||
in the address book.
|
||||
A contact has been automatically created if this person is using Odoo.
|
||||
|
||||
How to reimburse employees
|
||||
==========================
|
||||
|
||||
You can now see all the expense reports to reimburse in
|
||||
:menuselection:`Expenses --> Accountant --> Expense Reports To Pay`.
|
||||
You can now see all the expense reports to reimburse in
|
||||
:menuselection:`Expenses --> Accountant --> Expense Reports To Pay`.
|
||||
To record the payment or pay by check, click *Register a Payment*.
|
||||
|
||||
See how you can easily manage the payment process in Odoo:
|
||||
@@ -223,7 +223,7 @@ Submit, validate and post expenses
|
||||
Invoice expenses
|
||||
----------------
|
||||
|
||||
Now you can invoice the order. It shows up in
|
||||
Now you can invoice the order. It shows up in
|
||||
:menuselection:`Sales --> Invoicing --> Sales`
|
||||
to Invoice. The expenses have been added automatically in the order
|
||||
lines. Such items show up in blue (i.e. to invoice).
|
||||
@@ -231,4 +231,4 @@ lines. Such items show up in blue (i.e. to invoice).
|
||||
.. image:: expenses/invoicing_04.png
|
||||
:align: center
|
||||
|
||||
e (i.e. to invoice).
|
||||
e (i.e. to invoice).
|
||||
|
||||
@@ -10,7 +10,7 @@ countries, currencies and payment methods in Latin America.
|
||||
Configuration on Mercado Pago Dashboard
|
||||
=======================================
|
||||
|
||||
#. Log into `Mercado Pago Dashboard <https://www.mercadopago.com.mx/developers/panel>`_
|
||||
#. Log into `Mercado Pago Dashboard <https://www.mercadopago.com.mx/developers/panel>`_
|
||||
and go to your **Application** or *create* a new one.
|
||||
#. Go to :menuselection:`Production Credentials` or :menuselection:`Credentials` if your are in
|
||||
a *Test* environment and copy your **Access Token**
|
||||
@@ -22,7 +22,7 @@ Configuration on Odoo
|
||||
|
||||
#. :ref:`Navigate to the payment provider Mercado Pago <payment_providers/add_new>` and change its
|
||||
state to :guilabel:`Enabled`.
|
||||
#. In the :guilabel:`Credentials` tab, fill the :guilabel:`Access Token` with the value
|
||||
#. In the :guilabel:`Credentials` tab, fill the :guilabel:`Access Token` with the value
|
||||
you saved at the step :ref:`payment_providers/mercado_pago/configure_dashboard`.
|
||||
#. Configure the rest of the options to your liking.
|
||||
|
||||
|
||||
@@ -36,4 +36,4 @@ check. To do so, just rename *Wire Transfer* or duplicate it.
|
||||
:align: center
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_providers`
|
||||
- :doc:`../payment_providers`
|
||||
|
||||
@@ -118,4 +118,4 @@ before it is completed.
|
||||
|
||||
.. image:: sign/tip-placeholder.png
|
||||
:align: center
|
||||
:alt: Tip and placeholder example in Odoo Sign
|
||||
:alt: Tip and placeholder example in Odoo Sign
|
||||
|
||||
@@ -14,4 +14,3 @@ Miscellaneous
|
||||
general/digest_emails
|
||||
general/in_app_purchase
|
||||
general/developer_mode
|
||||
|
||||
|
||||
@@ -72,5 +72,3 @@ To complete the uninstallation, click on *Confirm*.
|
||||
|
||||
.. danger::
|
||||
Uninstalling an app also uninstalls all its dependencies and permanently erases their data.
|
||||
|
||||
|
||||
|
||||
@@ -70,7 +70,7 @@ Credentials
|
||||
|
||||
#. Select **Web Application** as the Application type. Now configure the allowed pages on which you
|
||||
will be redirected.
|
||||
|
||||
|
||||
In order to achieve this, in the **Authorized redirect URIs** field, enter your database's domain
|
||||
immediately followed by ``/auth_oauth/signin``. For example:
|
||||
``https://mydomain.odoo.com/auth_oauth/signin``, then click on *Create*.
|
||||
@@ -106,7 +106,7 @@ Odoo activation
|
||||
|
||||
.. note::
|
||||
You may have to log in again after this step.
|
||||
|
||||
|
||||
#. Go back to :menuselection:`General Settings --> Integrations`, activate **Google
|
||||
Authentication**, then fill out the *Client ID* with the key from the Google API Dashboard, and
|
||||
*Save*.
|
||||
|
||||
@@ -8,4 +8,4 @@ Calendars
|
||||
:titlesonly:
|
||||
|
||||
calendars/outlook/outlook_calendar
|
||||
calendars/google/google_calendar_credentials
|
||||
calendars/google/google_calendar_credentials
|
||||
|
||||
@@ -101,4 +101,4 @@ The synchronization is a two-way process, meaning that events are reconciled in
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../../productivity/mail_plugins/outlook`
|
||||
- :doc:`../google/google_calendar_credentials`
|
||||
- :doc:`../google/google_calendar_credentials`
|
||||
|
||||
@@ -38,7 +38,7 @@ Activate through the command palette
|
||||
|
||||
The command palette tool has a command to activate the debug mode: open it with
|
||||
the keyboard shortcut `ctrl+k`, then type `debug`: a command will show up to
|
||||
activate the debug mode.
|
||||
activate the debug mode.
|
||||
|
||||
.. image:: developer_mode/command_palette.png
|
||||
:align: center
|
||||
@@ -78,4 +78,3 @@ It contains some useful menu items such as:
|
||||
.. image:: developer_mode/button_location.png
|
||||
:align: center
|
||||
:alt: Overview of a console page and the debug icon being shown in Odoo
|
||||
|
||||
|
||||
@@ -54,7 +54,7 @@ Custom digest emails
|
||||
To do so, click on **Configure Digest Emails** and then **Create**.
|
||||
|
||||
From there, give your Digest Email a title, specify periodicity, and choose your desired KPIs and
|
||||
recipients fields as needed.
|
||||
recipients fields as needed.
|
||||
|
||||
After you click **Save**, your new custom Digest Email is available as a selection in the **General
|
||||
Settings** dropdown menu.
|
||||
@@ -111,4 +111,4 @@ Computed values reference table
|
||||
| POS Sales | `kpi_pos_total_value` |
|
||||
+-----------------------+-------------------------------------------+
|
||||
| New Employees | `kpi_hr_recruitment_new_colleagues_value` |
|
||||
+-----------------------+-------------------------------------------+
|
||||
+-----------------------+-------------------------------------------+
|
||||
|
||||
@@ -20,7 +20,7 @@ If your database is hosted on our cloud (Odoo Online or Odoo.sh), it is not nece
|
||||
outgoing email server to send emails from your custom domain. You can enjoy this feature by using
|
||||
the default Odoo email server.
|
||||
|
||||
.. important::
|
||||
.. important::
|
||||
The Odoo server is subject to a daily email limit to prevent abuse. The default limit is 200
|
||||
emails sent per day for databases with an Enterprise subscription. This limit can be increased
|
||||
under certain conditions. See our :doc:`FAQ <faq>` or contact support for more
|
||||
@@ -38,19 +38,19 @@ Be SPF compliant
|
||||
================
|
||||
|
||||
The Sender Policy Framework (SPF) protocol allows the owner of a domain name to specify which
|
||||
servers are allowed to send email from that domain. When a server receives an incoming email,
|
||||
it checks whether the IP address of the sending server is on the list of allowed IPs according
|
||||
servers are allowed to send email from that domain. When a server receives an incoming email,
|
||||
it checks whether the IP address of the sending server is on the list of allowed IPs according
|
||||
to the SPF record of the sender.
|
||||
|
||||
.. note::
|
||||
.. note::
|
||||
The SPF verification is performed on the domain mentioned in the Return-Path field of the email.
|
||||
In the case of an email sent by Odoo, this domain corresponds to the value of the
|
||||
`mail.catchall.domain` key in the database system parameters.
|
||||
|
||||
See the :ref:`documentation on incoming emails <email_communication/inbound_messages>`.
|
||||
|
||||
The SPF policy of a domain is set using a TXT record. How to create or modify a TXT record depends
|
||||
on the provider hosting the DNS zone of your domain name. In order for the verification to work
|
||||
The SPF policy of a domain is set using a TXT record. How to create or modify a TXT record depends
|
||||
on the provider hosting the DNS zone of your domain name. In order for the verification to work
|
||||
properly, each domain can only have one SPF record.
|
||||
|
||||
If your domain name does not yet have an SPF record, the content of the record to create is as
|
||||
@@ -66,7 +66,7 @@ new one).
|
||||
If your TXT record is `v=spf1 include:_spf.google.com ~all`, you need to edit it to add
|
||||
`include:_spf.odoo.com`: `v=spf1 include:_spf.odoo.com include:_spf.google.com ~all`
|
||||
|
||||
You can check if your SPF record is valid with a free tool like
|
||||
You can check if your SPF record is valid with a free tool like
|
||||
`MXToolbox SPF <https://mxtoolbox.com/spf.aspx>`_.
|
||||
|
||||
.. _email_communication/DKIM_compliant:
|
||||
@@ -86,13 +86,13 @@ To enable DKIM, you must add a CNAME record to the DNS zone of your domain name:
|
||||
``odoo._domainkey IN CNAME odoo._domainkey.odoo.com.``
|
||||
|
||||
.. tip::
|
||||
If your domain name is `mycompany.com`, you need to create a subdomain
|
||||
If your domain name is `mycompany.com`, you need to create a subdomain
|
||||
`odoo._domainkey.mycompany.com` whose canonical name is `odoo._domainkey.odoo.com.`.
|
||||
|
||||
How to create or modify a CNAME record depends on the provider hosting the DNS zone of your domain
|
||||
name. The most common providers are list below.
|
||||
|
||||
You can check if your DKIM record is valid with a free tool like
|
||||
You can check if your DKIM record is valid with a free tool like
|
||||
`DKIM Core <https://dkimcore.org/tools/>`_. If a selector is asked, enter `odoo`.
|
||||
|
||||
Check your DMARC policy
|
||||
@@ -110,7 +110,7 @@ There are three DMARC policies:
|
||||
``p=quarantine`` and ``p=reject`` instruct the server that receives an email to quarantine that
|
||||
email or ignore it if the SPF and/or DKIM check fails.
|
||||
|
||||
If your domain name uses DMARC and has defined one of these policies, it is therefore imperative
|
||||
If your domain name uses DMARC and has defined one of these policies, it is therefore imperative
|
||||
to be SPF compliant or to enable DKIM.
|
||||
|
||||
.. danger::
|
||||
@@ -118,7 +118,7 @@ to be SPF compliant or to enable DKIM.
|
||||
strongly advise against using an *@yahoo.com* or *@aol.com* address for your users. These emails
|
||||
will never reach their recipient.
|
||||
|
||||
``p=none`` is used for the domain owner to receive reports about entities using their domain. It
|
||||
``p=none`` is used for the domain owner to receive reports about entities using their domain. It
|
||||
should not impact the deliverability if the DMARC check fails.
|
||||
|
||||
You can check the DMARC record of a domain name with a tool like
|
||||
@@ -127,12 +127,12 @@ You can check the DMARC record of a domain name with a tool like
|
||||
If one of your partners, customer or vendor, uses DMARC and has defined one of these policies, the
|
||||
Odoo server cannot relay emails from this partner to your users.
|
||||
|
||||
You need to :ref:`handle user notifications in Odoo <discuss_app/notification_preferences>`, or replace the
|
||||
You need to :ref:`handle user notifications in Odoo <discuss_app/notification_preferences>`, or replace the
|
||||
email address of the partner with a default email address.
|
||||
|
||||
.. _email_communication/SPFDKIM_common_providers:
|
||||
|
||||
SPF, DKIM & DMARC documentation of common providers
|
||||
SPF, DKIM & DMARC documentation of common providers
|
||||
===================================================
|
||||
|
||||
- `OVH DNS <https://docs.ovh.com/us/en/domains/web_hosting_how_to_edit_my_dns_zone/>`_
|
||||
@@ -145,8 +145,8 @@ SPF, DKIM & DMARC documentation of common providers
|
||||
- `Google Domains <https://support.google.com/domains/answer/3290350?hl=en>`_
|
||||
- `Azure DNS <https://docs.microsoft.com/en-us/azure/dns/dns-getstarted-portal>`_
|
||||
|
||||
To fully test your configuration, the tool `Mail-Tester <https://www.mail-tester.com/>`_ will give
|
||||
you a full overview of the content and configuration you have in one email sent! Mail-Tester can
|
||||
To fully test your configuration, the tool `Mail-Tester <https://www.mail-tester.com/>`_ will give
|
||||
you a full overview of the content and configuration you have in one email sent! Mail-Tester can
|
||||
also be used for other lesser known providers.
|
||||
|
||||
Use a default email address
|
||||
@@ -156,8 +156,8 @@ To force the email address from which emails are sent, you need to create the fo
|
||||
the System Parameters of the database:
|
||||
|
||||
- If ``mail.default.from`` is set, and contains a full email address, all outgoing emails are sent
|
||||
from the given address. This is a requirement to use `Outlook with Odoo
|
||||
from the given address. This is a requirement to use `Outlook with Odoo
|
||||
<https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365#option-1-authenticate-your-device-or-application-directly-with-a-microsoft-365-or-office-365-mailbox-and-send-mail-using-smtp-auth-client-submission>`_.
|
||||
|
||||
You access the **System Parameters** in :ref:`developer mode <developer-mode>` in the :menuselection:`Settings -->
|
||||
Technical --> Parameters --> System Parameters` menu.
|
||||
Technical --> Parameters --> System Parameters` menu.
|
||||
|
||||
@@ -10,15 +10,15 @@ improving their overall experience with the company.
|
||||
|
||||
.. note::
|
||||
The email templates use QWeb. The composer allows you to edit emails in their final rendering,
|
||||
making customizations more robust as you don’t have to edit code.
|
||||
making customizations more robust as you don’t have to edit code.
|
||||
|
||||
Defining a default reply to on your mail template
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Although the field *reply to* is available within the mail templates, **this field is only used
|
||||
for mass mailing** mode (this means when sending templates on what we call bulk emailing). You
|
||||
can send emails in bulk in almost every app that has a list view. Select the records you want
|
||||
and click on the action button. If you have an option to send an email, you will see a mail
|
||||
Although the field *reply to* is available within the mail templates, **this field is only used
|
||||
for mass mailing** mode (this means when sending templates on what we call bulk emailing). You
|
||||
can send emails in bulk in almost every app that has a list view. Select the records you want
|
||||
and click on the action button. If you have an option to send an email, you will see a mail
|
||||
composer with possible values to define:
|
||||
|
||||
.. image:: email_template/composer-mass-mailing-quotations.png
|
||||
@@ -31,12 +31,12 @@ You can also define them by default on the template:
|
||||
:align: center
|
||||
:alt: Reply-to field on template.
|
||||
|
||||
Because of this, setting a value in this field is useless as the value defined will be totally
|
||||
ignored. The default *reply-to* value is the default catchall email address to ensure a
|
||||
Because of this, setting a value in this field is useless as the value defined will be totally
|
||||
ignored. The default *reply-to* value is the default catchall email address to ensure a
|
||||
communication between your customer and your Odoo database. For more information about the way
|
||||
the catchall works, please check :ref:`how to manage inbound messages <email_communication/inbound_messages>`.
|
||||
|
||||
Transactional emails and corresponding URL for each company
|
||||
Transactional emails and corresponding URL for each company
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
When using Odoo, multiple events trigger the sending of automated emails. These emails are known
|
||||
@@ -45,36 +45,36 @@ as transactional emails and sometimes contain links pointing to your Odoo databa
|
||||
By default, links generated by the database use the dynamic web.base.url key defined in the system
|
||||
parameters. More information about this :ref:`parameter <domain-name/web-base-url>`.
|
||||
|
||||
If the website application isn't installed, the web.base.url key will always be the default
|
||||
If the website application isn't installed, the web.base.url key will always be the default
|
||||
parameter used to generate all the links.
|
||||
|
||||
It’s important to know that this key can only have a single value, meaning that in a
|
||||
multi-website/company database environment, even if you have a specific domain name for each
|
||||
It’s important to know that this key can only have a single value, meaning that in a
|
||||
multi-website/company database environment, even if you have a specific domain name for each
|
||||
website, the links generated to share a document or within a transactional email might remain the
|
||||
same, whatever the website/company related to the sending of the email/document.
|
||||
|
||||
This is not always the case as some Odoo applications have a link established in the database with
|
||||
the website application, meaning that in this case, if a specific domain is defined for the
|
||||
This is not always the case as some Odoo applications have a link established in the database with
|
||||
the website application, meaning that in this case, if a specific domain is defined for the
|
||||
websites, the URL generated in the email template will use the domain defined on the corresponding
|
||||
website of the company.
|
||||
|
||||
.. caution::
|
||||
A document shared using the documents application will always use the web.base.url key, as the
|
||||
document shared isn't associated with any particular website. Meaning that the URL will always be
|
||||
the same (the web.base.url key value), whatever the company it's shared from, this is a known
|
||||
A document shared using the documents application will always use the web.base.url key, as the
|
||||
document shared isn't associated with any particular website. Meaning that the URL will always be
|
||||
the same (the web.base.url key value), whatever the company it's shared from, this is a known
|
||||
limitation!
|
||||
|
||||
On the other hand, sales orders made by a customer on one of your Odoo e-commerce websites have a
|
||||
link established with the website from which the order was made. As a result, the e-mail sent for
|
||||
On the other hand, sales orders made by a customer on one of your Odoo e-commerce websites have a
|
||||
link established with the website from which the order was made. As a result, the e-mail sent for
|
||||
the sales orders uses the domain name defined for the corresponding website to generate the links.
|
||||
|
||||
For more information about how to configure your domains, we invite you to check :doc:`our domain name
|
||||
For more information about how to configure your domains, we invite you to check :doc:`our domain name
|
||||
documentation </administration/maintain/domain_names>`.
|
||||
|
||||
Updating translations within email templates
|
||||
********************************************
|
||||
|
||||
Email templates are automatically translated. Changing the translations shouldn’t be necessary.
|
||||
Email templates are automatically translated. Changing the translations shouldn’t be necessary.
|
||||
However, if for a specific reason you’d like to change some of the translations, this can be done.
|
||||
|
||||
Like any modification in the code, keep in mind that modifications that aren’t done correctly (for
|
||||
@@ -89,7 +89,7 @@ In order to edit your translations, follow these steps from the template.
|
||||
:align: left
|
||||
:alt: Edit the language of a template
|
||||
|
||||
#. A pop-up window with the different languages installed on the database will be displayed. From
|
||||
#. A pop-up window with the different languages installed on the database will be displayed. From
|
||||
here, editing the translations will be possible. Don't forget to hit the save button to preserve
|
||||
your changes.
|
||||
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
===
|
||||
FAQ
|
||||
FAQ
|
||||
===
|
||||
|
||||
This document contains an explanation of the most recurring mailing concerns.
|
||||
|
||||
We will start by addressing issues of outgoing emails (ex: my client has not received my email),
|
||||
We will start by addressing issues of outgoing emails (ex: my client has not received my email),
|
||||
and then, of incoming emails (ex: I do not receive responses from my customers in the database).
|
||||
|
||||
Outgoing emails
|
||||
@@ -27,15 +27,15 @@ Common error messages
|
||||
|
||||
.. _email_communication/daily_limit_mail:
|
||||
|
||||
You reached your daily limit:
|
||||
You reached your daily limit:
|
||||
*****************************
|
||||
|
||||
.. image:: faq/email-limit.png
|
||||
:align: center
|
||||
:alt: Warning in Odoo upon email limit reached
|
||||
|
||||
Each email service provider has its own email sending limits. The limits may be daily, hourly,
|
||||
and sometimes even per minute. This is the same for Odoo, we have to limit our customers to prevent
|
||||
Each email service provider has its own email sending limits. The limits may be daily, hourly,
|
||||
and sometimes even per minute. This is the same for Odoo, we have to limit our customers to prevent
|
||||
our e-mail servers from being blacklisted.
|
||||
|
||||
Here are the default limits for new databases:
|
||||
@@ -48,18 +48,18 @@ Here are the default limits for new databases:
|
||||
|
||||
In case you hit the limit, you can:
|
||||
|
||||
- Ask our support team to increase your daily limit. We will analyze the situation of your database
|
||||
- Ask our support team to increase your daily limit. We will analyze the situation of your database
|
||||
depending on (non-exhaustive list):
|
||||
|
||||
- How many users in your database,
|
||||
- How many users in your database,
|
||||
- Which apps are installed,
|
||||
- Your bounce rate: the percentage of email addresses that did not receive your emails because
|
||||
- Your bounce rate: the percentage of email addresses that did not receive your emails because
|
||||
it was returned by a mail server on its way to the final recipient. You can contact the `support
|
||||
<https://www.odoo.com/help>`_.
|
||||
|
||||
- Use your own outgoing email server to be independent of Odoo’s mail limit (please refer
|
||||
- Use your own outgoing email server to be independent of Odoo’s mail limit (please refer
|
||||
to :doc:`the corresponding documentation </applications/general/email_communication/email_servers>`),
|
||||
- Wait until 11pm UTC for the reset and click on the retry button: The :ref:`Developer mode <developer-mode>`
|
||||
- Wait until 11pm UTC for the reset and click on the retry button: The :ref:`Developer mode <developer-mode>`
|
||||
must be activated. Then, go to :menuselection:`Settings --> Technical --> Emails`
|
||||
|
||||
.. image:: faq/email-retry-technical.png
|
||||
@@ -70,54 +70,54 @@ In case you hit the limit, you can:
|
||||
The daily limit is global to your database and can rise quickly! By default an internal message,
|
||||
a notification, a note, etc. counts as an email in your daily limit if it notifies someone.
|
||||
|
||||
You can mitigate this by receiving your :ref:`notifications in Odoo <discuss_app/notification_preferences>`
|
||||
instead of by emails.
|
||||
You can mitigate this by receiving your :ref:`notifications in Odoo <discuss_app/notification_preferences>`
|
||||
instead of by emails.
|
||||
|
||||
SMTP Error
|
||||
**********
|
||||
|
||||
You can find out why an email wasn't transmitted successfully by reviewing the Simple Mail
|
||||
Transport Protocol (SMTP) error messages. SMTP is a protocol to describe the email structure
|
||||
and transmit it over the Internet, and the error messages generated by email services are helpful
|
||||
You can find out why an email wasn't transmitted successfully by reviewing the Simple Mail
|
||||
Transport Protocol (SMTP) error messages. SMTP is a protocol to describe the email structure
|
||||
and transmit it over the Internet, and the error messages generated by email services are helpful
|
||||
tools to diagnose and troubleshoot email problems.
|
||||
|
||||
No Error
|
||||
********
|
||||
|
||||
Odoo is not always capable of providing information for the reason it failed. The different
|
||||
providers implement a personalized policy of the bounce emails and it is not always possible
|
||||
Odoo is not always capable of providing information for the reason it failed. The different
|
||||
providers implement a personalized policy of the bounce emails and it is not always possible
|
||||
for Odoo to interpret it correctly.
|
||||
|
||||
If you have this problem on a recurring basis with the same client or the same domain, please
|
||||
If you have this problem on a recurring basis with the same client or the same domain, please
|
||||
do not hesitate to contact `Odoo Support <https://www.odoo.com/help>`_ for help in finding a reason.
|
||||
|
||||
Note: in such case, one of the most common reasons is related to :ref:`SPF <email_communication/spf_compliant>`
|
||||
Note: in such case, one of the most common reasons is related to :ref:`SPF <email_communication/spf_compliant>`
|
||||
and/or :ref:`DKIM <email_communication/DKIM_compliant>` configuration.
|
||||
|
||||
Why is my email sent late?
|
||||
**************************
|
||||
|
||||
It may happen that you schedule an email campaign but it is not sent on time. We know that
|
||||
we use a delayed job to send emails that we consider as not urgent (Newsletters concept
|
||||
such as mass mailing, marketing automation, events). The system utility **cron** can be used
|
||||
to schedule programs to run automatically at predetermined intervals. We use that policy in order
|
||||
to avoid cluttering the mail servers and prioritize the communication.
|
||||
It may happen that you schedule an email campaign but it is not sent on time. We know that
|
||||
we use a delayed job to send emails that we consider as not urgent (Newsletters concept
|
||||
such as mass mailing, marketing automation, events). The system utility **cron** can be used
|
||||
to schedule programs to run automatically at predetermined intervals. We use that policy in order
|
||||
to avoid cluttering the mail servers and prioritize the communication.
|
||||
|
||||
The emails considered urgent (communication from one person to another one such as
|
||||
Sales Orders, Invoices, Purchase Orders, etc.) are sent directly.
|
||||
The emails considered urgent (communication from one person to another one such as
|
||||
Sales Orders, Invoices, Purchase Orders, etc.) are sent directly.
|
||||
|
||||
.. image:: faq/email-scheduled-later.png
|
||||
:align: center
|
||||
:alt: Email scheduled to be sent later.
|
||||
|
||||
By default, the Mass Mailing cron runs every 60 minutes. So, you should wait maximum an hour
|
||||
By default, the Mass Mailing cron runs every 60 minutes. So, you should wait maximum an hour
|
||||
before the campaign is actually sent.
|
||||
|
||||
Incoming emails
|
||||
===============
|
||||
|
||||
When you have an issue with incoming emails, there might not be an indication per se in Odoo.
|
||||
This is the client who tries to contact a database who will get a bounce (most of the
|
||||
When you have an issue with incoming emails, there might not be an indication per se in Odoo.
|
||||
This is the client who tries to contact a database who will get a bounce (most of the
|
||||
time 550: mailbox unavailable).
|
||||
|
||||
Emails are not received
|
||||
@@ -127,22 +127,22 @@ Depending on the platform you are using:
|
||||
|
||||
- The **Odoo.sh** users can find their live logs on the folder :file:`~/logs/`.
|
||||
|
||||
- The folder :file:`~/logs/` (preferably accessed by the command line) of an Odoo.sh contains
|
||||
a list of files containing the logs of the database. The log files are created everyday
|
||||
at 5:00 AM UTC. The two last days are not compressed, while the older ones are, in order
|
||||
to gain space. The naming of the files for Today and Yesterday are :file:`odoo.log` and
|
||||
- The folder :file:`~/logs/` (preferably accessed by the command line) of an Odoo.sh contains
|
||||
a list of files containing the logs of the database. The log files are created everyday
|
||||
at 5:00 AM UTC. The two last days are not compressed, while the older ones are, in order
|
||||
to gain space. The naming of the files for Today and Yesterday are :file:`odoo.log` and
|
||||
:file:`odoo.log.1`. For the following, they are named with their dates and compressed.
|
||||
See the Odoo.sh documentation about :ref:`logs <odoosh/logs>`. Use the command ``grep`` and
|
||||
See the Odoo.sh documentation about :ref:`logs <odoosh/logs>`. Use the command ``grep`` and
|
||||
``zgrep`` (for the compressed ones) to search through the files.
|
||||
|
||||
- **Odoo Online** users won’t have access to their logs. However you can still contact
|
||||
`Odoo Support <https://www.odoo.com/help>`_ , if you have a recurring issue
|
||||
`Odoo Support <https://www.odoo.com/help>`_ , if you have a recurring issue
|
||||
with the same client or domain.
|
||||
|
||||
Get help from support
|
||||
---------------------
|
||||
|
||||
In order to get helped efficiently, please provide as much information as possible. Here is a list
|
||||
In order to get helped efficiently, please provide as much information as possible. Here is a list
|
||||
of what can be helpful:
|
||||
|
||||
- The **EML** of the email, stating for *Electronic Mail*, is the file format containing all the
|
||||
@@ -171,4 +171,4 @@ of what can be helpful:
|
||||
- Is it a generic issue or is it specific to a use case? If yes, which one exactly?
|
||||
|
||||
- Is it working as expected? In case the email is sent using Odoo, the bounce email should reach
|
||||
the Odoo database and display the :ref:`red envelope <red_envelop>`.
|
||||
the Odoo database and display the :ref:`red envelope <red_envelop>`.
|
||||
|
||||
@@ -408,4 +408,4 @@ import the records of the related object first from their own list menu.
|
||||
|
||||
You can do it using either the name of the related record or its ID. The ID is expected when
|
||||
two records have the same name. In such a case add " / ID" at the end of the column title
|
||||
(e.g. for product attributes: Product Attributes / Attribute / ID).
|
||||
(e.g. for product attributes: Product Attributes / Attribute / ID).
|
||||
|
||||
@@ -16,7 +16,7 @@ SET default_tablespace = '';
|
||||
SET default_with_oids = false;
|
||||
|
||||
--
|
||||
-- Name: companies; Type: TABLE; Schema: public; Owner: fp; Tablespace:
|
||||
-- Name: companies; Type: TABLE; Schema: public; Owner: fp; Tablespace:
|
||||
--
|
||||
|
||||
CREATE TABLE companies (
|
||||
@@ -56,7 +56,7 @@ SELECT pg_catalog.setval('companies_id_seq', 3, true);
|
||||
|
||||
|
||||
--
|
||||
-- Name: persons; Type: TABLE; Schema: public; Owner: fp; Tablespace:
|
||||
-- Name: persons; Type: TABLE; Schema: public; Owner: fp; Tablespace:
|
||||
--
|
||||
|
||||
CREATE TABLE persons (
|
||||
@@ -134,7 +134,7 @@ COPY persons (id, company_id, person_name) FROM stdin;
|
||||
|
||||
|
||||
--
|
||||
-- Name: companies_pkey; Type: CONSTRAINT; Schema: public; Owner: fp; Tablespace:
|
||||
-- Name: companies_pkey; Type: CONSTRAINT; Schema: public; Owner: fp; Tablespace:
|
||||
--
|
||||
|
||||
ALTER TABLE ONLY companies
|
||||
@@ -152,4 +152,3 @@ ALTER TABLE ONLY persons
|
||||
--
|
||||
-- PostgreSQL database dump complete
|
||||
--
|
||||
|
||||
|
||||
@@ -29,7 +29,7 @@ Settings --> IAP Account`.
|
||||
|
||||
.. image:: in_app_purchase/image2.png
|
||||
:align: center
|
||||
|
||||
|
||||
IAP Portal
|
||||
==========
|
||||
|
||||
@@ -62,7 +62,7 @@ Different services are available depending on the hosting type of your Database:
|
||||
- *Odoo.sh and Odoo Enterprise (on-premise)*: both the services provided by Odoo and by third-party
|
||||
apps can be used.
|
||||
|
||||
Offering my own services
|
||||
Offering my own services
|
||||
========================
|
||||
|
||||
I am more than welcome to offer my own IAP services through Odoo Apps! It is the perfect opportunity
|
||||
|
||||
@@ -17,4 +17,3 @@ can be applied. Users and access rights can be added and changed at any point.
|
||||
users/language
|
||||
users/access_rights
|
||||
users/companies
|
||||
|
||||
|
||||
@@ -64,4 +64,4 @@ is the technical name given to a model. For each model, enable the following opt
|
||||
.. important::
|
||||
Making changes in access rights can have a big impact on the database. For this reason, we
|
||||
recommend you to contact your Odoo Business Analyst or our Support Team, unless you have
|
||||
knowledge about Domains in Odoo.
|
||||
knowledge about Domains in Odoo.
|
||||
|
||||
@@ -131,4 +131,4 @@ at an invoice/bills level or at a sales/purchase orders level.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`Multi-company Guidelines </developer/howtos/company>`
|
||||
- :doc:`../../finance/accounting/others/multi_currency`
|
||||
- :doc:`../../finance/accounting/others/multi_currency`
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user