[REF][MOV] documentation apocalypse
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
This commit is contained in:
Antoine Vandevenne (anv)
committed by
Antoine Vandevenne (anv)
Antoine Vandevenne (anv)
parent
eac5e9f865
commit
e3fee2cf46
@@ -0,0 +1,248 @@
|
||||
========
|
||||
Colombia
|
||||
========
|
||||
|
||||
Introduction
|
||||
~~~~~~~~~~~~
|
||||
|
||||
Electronic invoicing for Colombia is available from Odoo 12 and
|
||||
requires the next modules:
|
||||
|
||||
#. **l11n_co**: All the basic data to manage the accounting module,
|
||||
contains the default setup for: chart of accounts, taxes,
|
||||
retentions, identification document types
|
||||
#. **l10n_co_edi**: This module includes all the extra fields that are
|
||||
required for the Integration with Carvajal T&S and generate the
|
||||
electronic invoice, based on the DIAN legal requirements.
|
||||
|
||||
Workflow
|
||||
~~~~~~~~
|
||||
|
||||
.. image:: media/colombia01.png
|
||||
:align: center
|
||||
|
||||
Configuration
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
1. Install the Colombian localization modules
|
||||
---------------------------------------------
|
||||
|
||||
For this, go in Apps and search for Colombia. Then click Install for
|
||||
the first two modules.
|
||||
|
||||
.. image:: media/colombia02.png
|
||||
:align: center
|
||||
|
||||
2. Configure credentials for Carvajal T&S web service
|
||||
-----------------------------------------------------
|
||||
|
||||
Once that the modules are installed, in order to be able to connect
|
||||
with Carvajal T&S Web Service, it's necessary to configure the user
|
||||
and credentials, this information will be provided by Carvajal T&S.
|
||||
|
||||
Go to :menuselection:`Accounting --> Configuration --> Settings` and
|
||||
look for the *Colombian Electronic Invoice* section.
|
||||
|
||||
.. image:: media/colombia03.png
|
||||
:align: center
|
||||
|
||||
Using the Testing mode it is possible to connect with a Carvajal T&S
|
||||
testing environment. This allows users to test the complete workflow
|
||||
and integration with the CEN Financiero portal, which is accessible
|
||||
here: https://cenfinancierolab.cen.biz
|
||||
|
||||
Once that Odoo and Carvajal T&S is fully configured and ready for
|
||||
production the testing environment can be disabled.
|
||||
|
||||
3. Configure your report data
|
||||
-----------------------------
|
||||
|
||||
As part of the configurable information that is sent in the XML, you
|
||||
can define the data for the fiscal section and the bank information in
|
||||
the PDF.
|
||||
|
||||
Go to :menuselection:`Accounting --> Configuration --> Settings` and
|
||||
look for the *Colombian Electronic Invoice* section.
|
||||
|
||||
.. image:: media/colombia04.png
|
||||
:align: center
|
||||
|
||||
4. Configure data required in the XML
|
||||
-------------------------------------
|
||||
|
||||
4.1 Partner
|
||||
+++++++++++
|
||||
|
||||
4.1.1 Identification
|
||||
^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
As part of the Colombian Localization, the document types defined by
|
||||
the DIAN are now available on the Partner form. Colombian partners
|
||||
have to have their identification number and document type set:
|
||||
|
||||
.. image:: media/colombia05.png
|
||||
:align: center
|
||||
|
||||
.. tip:: When the document type is RUT the identification number needs
|
||||
to be configured in Odoo including the verification digit, Odoo
|
||||
will split this number when the data to the third party vendor is
|
||||
sent.
|
||||
|
||||
4.1.2 Fiscal structure (RUT)
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
The partner's responsibility codes (section 53 in the RUT document)
|
||||
are included as part of the electronic invoice module given that is
|
||||
part of the information required by the DIAN .
|
||||
|
||||
These fields can be found in :menuselection:`Partner --> Sales &
|
||||
Purchase Tab --> Fiscal Information`
|
||||
|
||||
.. image:: media/colombia06.png
|
||||
:align: center
|
||||
|
||||
Additionally two booleans fields were added in order to specify the
|
||||
fiscal regimen of the partner.
|
||||
|
||||
4.2 Taxes
|
||||
+++++++++
|
||||
|
||||
If your sales transactions include products with taxes, it's important
|
||||
to consider that an extra field *Value Type* needs to be configured
|
||||
per tax. This option is located in the Advanced Options tab.
|
||||
|
||||
.. image:: media/colombia07.png
|
||||
:align: center
|
||||
|
||||
Retention tax types (ICA, IVA, Fuente) are also included in the
|
||||
options to configure your taxes. This configuration is used in order
|
||||
to correctly display taxes in the invoice PDF.
|
||||
|
||||
.. image:: media/colombia08.png
|
||||
:align: center
|
||||
|
||||
4.3 Journals
|
||||
++++++++++++
|
||||
|
||||
Once the DIAN has assigned the official sequence and prefix for the
|
||||
electronic invoice resolution, the Sales journals related to your
|
||||
invoice documents need to be updated in Odoo. The sequence can be
|
||||
accessed using developer mode: :menuselection:`Accounting --> Settings
|
||||
--> Configuration Setting --> Journals`.
|
||||
|
||||
.. image:: media/colombia09.png
|
||||
:align: center
|
||||
|
||||
Once that the sequence is opened, the Prefix and Next Number fields
|
||||
should be configured and synchronized with the CEN Financiero.
|
||||
|
||||
.. image:: media/colombia10.png
|
||||
:align: center
|
||||
|
||||
4.4 Users
|
||||
+++++++++
|
||||
|
||||
The default template that is used by Odoo on the invoice PDF includes
|
||||
the job position of the salesperson, so these fields should be
|
||||
configured:
|
||||
|
||||
.. image:: media/colombia11.png
|
||||
:align: center
|
||||
|
||||
Usage and testing
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
1. Invoice
|
||||
----------
|
||||
|
||||
When all your master data and credentials has been configured, it's
|
||||
possible to start testing the electronic invoice workflow.
|
||||
|
||||
1.1 Invoice creation
|
||||
++++++++++++++++++++
|
||||
|
||||
The functional workflow that takes place before an invoice validation
|
||||
doesn't change. The main changes that are introduced with the
|
||||
electronic invoice are the next fields:
|
||||
|
||||
.. image:: media/colombia12.png
|
||||
:align: center
|
||||
|
||||
There are three types of documents:
|
||||
|
||||
- **Factura Electronica**: This is the regular type of document and
|
||||
its applicable for Invoices, Credit Notes and Debit Notes.
|
||||
- **Factura de Importación**: This should be selected for importation
|
||||
transactions.
|
||||
- **Factura de contingencia**: This is an exceptional type that is
|
||||
used as a manual backup in case that the company is not able to use
|
||||
the ERP and it's necessary to generate the invoice manually, when
|
||||
this invoice is added to the ERP, this invoice type should be
|
||||
selected.
|
||||
|
||||
1.2 Invoice validation
|
||||
++++++++++++++++++++++
|
||||
|
||||
After the invoice is validated an XML file is created and sent
|
||||
automatically to Carvajal, this file is displayed in the chatter.
|
||||
|
||||
.. image:: media/colombia13.png
|
||||
:align: center
|
||||
|
||||
An extra field is now displayed in "Other Info" tab with the name of
|
||||
the XML file. Additionally there is a second extra field that is
|
||||
displayed with the Electronic Invoice status, with the initial value
|
||||
"In progress":
|
||||
|
||||
.. image:: media/colombia14.png
|
||||
:align: center
|
||||
|
||||
1.3 Reception of legal XML and PDF
|
||||
++++++++++++++++++++++++++++++++++
|
||||
|
||||
The electronic invoice vendor receives the XML file and proceeds to
|
||||
validate the structure and the information in it, if everything is
|
||||
correct the invoice status changes to "Validated" after using the
|
||||
"Check Carvajal Status" button in the Action dropdown. They then
|
||||
proceed to generate a Legal XML which includes a digital signature and
|
||||
a unique code (CUFE), a PDF invoice that includes a QR code and the
|
||||
CUFE is also generated.
|
||||
|
||||
After this:
|
||||
|
||||
- A ZIP containing the legal XML and the PDF is downloaded and
|
||||
displayed in the invoice chatter:
|
||||
|
||||
.. image:: media/colombia15.png
|
||||
:align: center
|
||||
|
||||
.. image:: media/colombia16.png
|
||||
:align: center
|
||||
|
||||
- The Electronic Invoice status changes to "Accepted"
|
||||
|
||||
1.4 Common errors
|
||||
+++++++++++++++++
|
||||
|
||||
During the XML validation the most common errors are usually related
|
||||
to missing master data. In such cases, error messages are shown in the
|
||||
chatter after updating the electronic invoice status.
|
||||
|
||||
.. image:: media/colombia17.png
|
||||
:align: center
|
||||
|
||||
After the master data is corrected, it's possible to reprocess the XML
|
||||
with the new data and send the updated version, using the following
|
||||
button:
|
||||
|
||||
.. image:: media/colombia18.png
|
||||
:align: center
|
||||
|
||||
.. image:: media/colombia19.png
|
||||
:align: center
|
||||
|
||||
2. Additional use cases
|
||||
-----------------------
|
||||
|
||||
The process for credit and debit notes is exactly the same as the
|
||||
invoice, the functional workflow remains the same as well.
|
||||
@@ -0,0 +1,283 @@
|
||||
=============
|
||||
Colombia (ES)
|
||||
=============
|
||||
|
||||
**Facturación Electrónica para Colombia**
|
||||
|
||||
Introducción
|
||||
============
|
||||
|
||||
La Facturación Electrónica para Colombia está disponible en Odoo V12 y
|
||||
requiere los siguientes Módulos:
|
||||
|
||||
1. **l11n_co**:** Contiene los datos básicos para manejar el
|
||||
módulo de contabilidad, incluyendo la configuración por defecto
|
||||
de los siguientes puntos:
|
||||
|
||||
| a. Plan Contable
|
||||
| b. Impuestos
|
||||
| c. Retenciones
|
||||
| d. Tipos de Documentos de Identificación
|
||||
|
||||
1. **l10n_co_edi**: Este módulo incluye todos los campos
|
||||
adicionales que son requeridos para la Integración entre Carvajal
|
||||
T&S y la generación de la Factura Electrónica, basado en los
|
||||
requisitos legales de la DIAN.
|
||||
|
||||
Flujo General
|
||||
-------------
|
||||
|
||||
Configuración
|
||||
=============
|
||||
|
||||
1. Instalación de los módulos de Localización Colombiana
|
||||
--------------------------------------------------------
|
||||
|
||||
Para esto ve a las aplicaciones y busca “Colombia”, luego da click en
|
||||
Instalar a los primeros dos módulos:
|
||||
|
||||
cz
|
||||
|
||||
2. Configuración de las credenciales del Servicio Web de Carvajal T&S
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
| Una vez que los módulos están instalados, para poderte conectar con el
|
||||
Servicio Web de Carvajal T&S, es necesario configurar el Usuario y las
|
||||
Credenciales. Esta información será provista por Carvajal T&S.
|
||||
| Ve a Facturación –> Configuración –> Configuración y busca la sección
|
||||
**Facturación Electrónica Colombiana**
|
||||
|
||||
.. image:: media/colombia_ES02.png
|
||||
:align: center
|
||||
|
||||
| La funcionalidad de pruebas le permite conectarse e interactuar con el
|
||||
ambiente piloto de Carvajal T&S, esto permite a los usuarios probar el
|
||||
flujo completo y la integración con el Portal Financiero CEN, al cual
|
||||
se accede a través de la siguiente liga: `Cenfinanciero <https://cenfinancierolab.cen.biz>`__,
|
||||
|
||||
Una vez que el ambiente de producción está listo en Odoo y en Carvajal
|
||||
T&S el ambiente de pruebas debe ser deshabilitado para poder enviar la
|
||||
información al ambiente de producción de Carvajal, para el cual es
|
||||
utilizada la siguiente URL: `Cenfinanciero <https://cenfinancierolab.cen.biz>`__,
|
||||
|
||||
3. Configuración de Información para PDF
|
||||
----------------------------------------
|
||||
|
||||
| Como parte de la información configurable que es enviada en el XML,
|
||||
puedes definir los datos de la sección fiscal del PDF, así como de la
|
||||
información Bancaria.
|
||||
| Ve a Contabilidad – Configuración – Ajustes y busca la sección
|
||||
**Facturación Electrónica Colombiana**.
|
||||
|
||||
.. image:: media/colombia_ES03.png
|
||||
:align: center
|
||||
|
||||
4. Configuración de los Datos Principales Requeridos en el XML
|
||||
--------------------------------------------------------------
|
||||
|
||||
4.1 Contacto (Tercero)
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
4.1.1 Identificación
|
||||
~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
|
||||
Como parte de la Localización Colombiana, los tipos de documentos
|
||||
definidos por la DIAN ahora están disponibles en el formulario de
|
||||
Contactos, por lo cual ya es posible asignarles su número de
|
||||
identificación asociado al tipo de documento correspondiente.
|
||||
|
||||
.. image:: media/colombia_ES04.png
|
||||
:align: center
|
||||
|
||||
Nota: Cuando el tipo de documento es RUT la identificación necesita ser
|
||||
ingresada en Odoo incluyendo el Dígito de Verificación. Odoo separará
|
||||
este número cuando la información sea enviada a los proveedores
|
||||
terceros.
|
||||
|
||||
4.1.2 Estructura Fiscal (RUT)
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Los Códigos de tipo de Obligación aplicables a los terceros (sección 53
|
||||
en el documento de RUT), son incluidos como parte del módulo de
|
||||
Facturación Electrónica, dado que es información requerida por la DIAN.
|
||||
|
||||
Estos campos se encuentran en Contactos –> Pestaña de Ventas y Compras
|
||||
–> Información Fiscal
|
||||
|
||||
.. image:: media/colombia_ES05.png
|
||||
:align: center
|
||||
|
||||
Adicionalmente dos últimos campos fueron agregados para especificar el
|
||||
régimen fiscal del contacto. Cabe aclarar que para envío de Factura
|
||||
electrónica de Carvajal, únicamente se hace distinción de entre Grandes
|
||||
Contribuyentes y Régimen simplificado, por lo se muestran solo estas dos
|
||||
opciones.
|
||||
|
||||
4.2 Impuestos
|
||||
-------------
|
||||
|
||||
| Si tus transacciones de ventas incluyen productos con impuestos, es
|
||||
importante considerar que un campo adicional llamado *Tipo de Valor*
|
||||
necesita ser configurado en la siguiente ruta:
|
||||
| Contabilidad – > Configuración –> Impuestos: –> Opciones Avanzadas
|
||||
–>Tipo de Valor
|
||||
|
||||
.. image:: media/colombia_ES06.png
|
||||
:align: center
|
||||
|
||||
Los impuestos para Retenciones (ICA, IVA y Fuente) también están
|
||||
incluidos en las opciones para configurar tus impuestos, esta
|
||||
configuración es considerada para desplegar correctamente los impuestos
|
||||
en la representación gráfica de la Factura. (PDF)
|
||||
|
||||
.. image:: media/colombia_ES07.png
|
||||
:align: center
|
||||
|
||||
4.3 Diarios
|
||||
-----------
|
||||
|
||||
Una vez que la DIAN ha asignado la secuencia y prefijo oficiales para la
|
||||
resolución de la Facturación Electrónica, los Diarios de Ventas
|
||||
relacionados con tus documentos de facturación necesitan ser
|
||||
actualizados en Odoo.
|
||||
|
||||
La secuencia es configurada usando el modo de desarrollador en la
|
||||
siguiente ruta:
|
||||
|
||||
Contabilidad –> Configuración –> Diarios –> Liga de Secuencia
|
||||
|
||||
.. image:: media/colombia_ES08.png
|
||||
:align: center
|
||||
|
||||
Una vez que la secuencia es abierta, los campos de Prefijo y Siguiente
|
||||
Número deben ser configurados y sincronizados con el CEN Financiero.
|
||||
|
||||
.. image:: media/colombia_ES09.png
|
||||
:align: center
|
||||
|
||||
4.4 Usuarios
|
||||
------------
|
||||
|
||||
La plantilla por defecto que es usada por Odoo en la representación
|
||||
gráfica incluye el nombre del Vendedor, así que estos campos deben ser
|
||||
considerados:
|
||||
|
||||
.. image:: media/colombia_ES10.png
|
||||
:align: center
|
||||
|
||||
Uso y Pruebas
|
||||
=============
|
||||
|
||||
Facturas
|
||||
--------
|
||||
|
||||
Una vez que toda la información principal y las credenciales han sido
|
||||
configuradas, es posible empezar a probar el flujo de la Facturación
|
||||
Electrónica siguiendo las instrucciones que se detallan a continuación:
|
||||
|
||||
1. Invoice Creation
|
||||
~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
El flujo de trabajo funcional que lleva lugar antes de la validación de
|
||||
una factura continua siendo igual con Facturación Electrónica,
|
||||
independientemente de si es creada desde una Orden de Venta o si es
|
||||
creado manualmente.
|
||||
|
||||
Los cambios principales que son introducidos con la Facturación
|
||||
Electrónica son los siguientes:
|
||||
|
||||
Hay tres tipos de documentos
|
||||
|
||||
- **Factura electrónica**. Este es el documento normal y aplica
|
||||
para Facturas, Notas de Crédito y Notas de Débito.
|
||||
|
||||
- **Factura de Importación**. Debe ser seleccionada para
|
||||
transacciones de importación.
|
||||
|
||||
- **Factura de Contingencia**. Esta es un caso excepcional y es
|
||||
utilizada como un respaldo manual en caso que la compañía no
|
||||
pueda usar el ERP y hay necesidad de crear la factura
|
||||
manualmente. Al ingresar esta factura en el ERP, se debe
|
||||
seleccionar este tipo.
|
||||
|
||||
.. image:: media/colombia_ES11.png
|
||||
:align: center
|
||||
|
||||
1. Invoice Validation
|
||||
~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Después que la factura fue validada, un archivo XML es creado y enviado
|
||||
automáticamente al proveedor de la factura electrónica. Este archivo es
|
||||
desplegado en el historial.
|
||||
|
||||
.. image:: media/colombia_ES12.png
|
||||
:align: center
|
||||
|
||||
Un campo adicional es ahora desplegado en la pestaña de “Otra
|
||||
Información” con el nombre del archivo XML. Adicionalmente hay un
|
||||
segundo campo adicional que es desplegado con el estatus de la Factura
|
||||
Electrónica, con el valor inicial **En Proceso**.
|
||||
|
||||
.. image:: media/colombia_ES13.png
|
||||
:align: center
|
||||
|
||||
1. Recepción del XML y PDF Legal
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
| El proveedor de la Factura Electrónica recibe el archivo XML y procede
|
||||
a validar la información y la estructura contenida. Si todo es
|
||||
correcto, el estatus de la Factura cambia a “Validado”. Como parte de
|
||||
este proceso se generar el XML Legal, el cual incluye una firma
|
||||
digital y un código único (CUFE) y generan el PDF de la Factura (el
|
||||
cual incluye un código QR) y el CUFE.
|
||||
|
||||
| Odoo envía una petición de actualización automáticamente para
|
||||
verificar que el XML fue creado. Si este es el caso, las siguientes
|
||||
acciones son hechas automáticamente.
|
||||
|
||||
- El XML Legal y el PDF son incluidos en un archivo ZIP y desplegados
|
||||
en el historial de la Factura.
|
||||
|
||||
.. image:: media/colombia_ES14.png
|
||||
:align: center
|
||||
|
||||
- El estatus de la Factura Electrónica es cambiado a “Aceptado”.
|
||||
|
||||
.. image:: media/colombia_ES15.png
|
||||
:align: center
|
||||
|
||||
Nota: En caso que el PDF y el XML sean requeridos inmediatamente, es
|
||||
posible mandar manualmente la petición del estatus usando el siguiente
|
||||
botón:
|
||||
|
||||
.. image:: media/colombia_ES16.png
|
||||
:align: center
|
||||
|
||||
1. Errores Frecuentes
|
||||
~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Durante la validación del XML los errores más comunes usualmente están
|
||||
relacionados con información principal faltante. En estos casos, los
|
||||
detalles del error son recuperados en la petición de actualización y
|
||||
desplegados en el historial.
|
||||
|
||||
.. image:: media/colombia_ES17.png
|
||||
:align: center
|
||||
|
||||
Si la información principal es corregida, es posible re procesar el XML
|
||||
con la nueva información y mandar la versión actualizada usando el
|
||||
siguiente botón:
|
||||
|
||||
.. image:: media/colombia_ES18.png
|
||||
:align: center
|
||||
|
||||
.. image:: media/colombia_ES19.png
|
||||
:align: center
|
||||
|
||||
Casos de Uso adicionales
|
||||
------------------------
|
||||
|
||||
El proceso para las Notas de Crédito y Débito (Proveedores) es
|
||||
exactamente el mismo que en las Facturas. Su flujo de trabajo funcional
|
||||
se mantiene igual.
|
||||
Binary file not shown.
Binary file not shown.
@@ -0,0 +1,195 @@
|
||||
======
|
||||
France
|
||||
======
|
||||
|
||||
FEC
|
||||
===
|
||||
|
||||
If you have installed the French Accounting, you will be able to download the FEC.
|
||||
For this, go in :menuselection:`Accounting --> Reporting --> France --> FEC`.
|
||||
|
||||
.. tip::
|
||||
If you do not see the submenu **FEC**, go in **Apps** and search for the module
|
||||
called **France-FEC** and verify if it is well installed.
|
||||
|
||||
French Accounting Reports
|
||||
=========================
|
||||
|
||||
If you have installed the French Accounting, you will have access to some accounting reports specific to France:
|
||||
|
||||
- Bilan comptable
|
||||
- Compte de résultats
|
||||
- Plan de Taxes France
|
||||
|
||||
Get the VAT anti-fraud certification with Odoo
|
||||
==============================================
|
||||
|
||||
As of January 1st 2018, a new anti-fraud legislation comes into effect
|
||||
in France and DOM-TOM. This new legislation stipulates certain criteria
|
||||
concerning the inalterability, security, storage and archiving of sales data.
|
||||
These legal requirements are implemented in Odoo, version 9 onward,
|
||||
through a module and a certificate of conformity to download.
|
||||
|
||||
Is my company required to use an anti-fraud software?
|
||||
-----------------------------------------------------
|
||||
|
||||
Your company is required to use an anti-fraud cash register software like
|
||||
Odoo (CGI art. 286, I. 3° bis) if:
|
||||
|
||||
* You are taxable (not VAT exempt) in France or any DOM-TOM,
|
||||
* Some of your customers are private individuals (B2C).
|
||||
|
||||
This rule applies to any company size. Auto-entrepreneurs are exempted from
|
||||
VAT and therefore are not affected.
|
||||
|
||||
Get certified with Odoo
|
||||
-----------------------
|
||||
|
||||
Getting compliant with Odoo is very easy.
|
||||
|
||||
Your company is requested by the tax administration to deliver a certificate
|
||||
of conformity testifying that your software complies with the anti-fraud
|
||||
legislation. This certificate is granted by Odoo SA to Odoo Enterprise users
|
||||
`here <https://www.odoo.com/my/contract/french-certification/>`__.
|
||||
If you use Odoo Community, you should
|
||||
`upgrade to Odoo Enterprise <https://www.odoo.com/documentation/online/setup/enterprise.html>`__
|
||||
or contact your Odoo service provider.
|
||||
|
||||
In case of non-conformity, your company risks a fine of €7,500.
|
||||
|
||||
To get the certification just follow the following steps:
|
||||
|
||||
* Install the anti-fraud module fitting your Odoo environment from the
|
||||
*Apps* menu:
|
||||
|
||||
* if you use Odoo Point of Sale: *l10n_fr_pos_cert*: France - VAT Anti-Fraud Certification for Point of Sale (CGI 286 I-3 bis)
|
||||
|
||||
* in any other case: *l10n_fr_certification*: France - VAT Anti-Fraud Certification (CGI 286 I-3 bis)
|
||||
* Make sure a country is set on your company, otherwise your entries won’t be
|
||||
encrypted for the inalterability check. To edit your company’s data,
|
||||
go to :menuselection:`Settings --> Users & Companies --> Companies`.
|
||||
Select a country from the list; Do not create a new country.
|
||||
* Download the mandatory certificate of conformity delivered by Odoo SA `here <https://www.odoo.com/my/contract/french-certification/>`__.
|
||||
|
||||
.. note:: * To install the module in any system created before
|
||||
December 18th 2017, you should update the modules list.
|
||||
To do so, activate the developer mode from the *Settings* menu.
|
||||
Then go to the *Apps* menu and press *Update Modules List* in the top-menu.
|
||||
* In case you run Odoo on-premise, you need to update your installation
|
||||
and restart your server beforehand.
|
||||
* If you have installed the initial version of the anti-fraud module
|
||||
(prior to December 18th 2017), you need to update it.
|
||||
The module's name was *France - Accounting - Certified CGI 286 I-3 bis*.
|
||||
After an update of the modules list, search for
|
||||
the updated module in *Apps*, select it and click *Upgrade*.
|
||||
Finally, make sure the following module *l10n_fr_sale_closing*
|
||||
is installed.
|
||||
|
||||
Anti-fraud features
|
||||
-------------------
|
||||
|
||||
The anti-fraud module introduces the following features:
|
||||
|
||||
* **Inalterability**: deactivation of all the ways to cancel or modify
|
||||
key data of POS orders, invoices and journal entries;
|
||||
* **Security**: chaining algorithm to verify the inalterability;
|
||||
* **Storage**: automatic sales closings with computation of both period
|
||||
and cumulative totals (daily, monthly, annually).
|
||||
|
||||
Inalterability
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
All the possible ways to cancel and modify key data of paid POS orders,
|
||||
confirmed invoices and journal entries are deactivated,
|
||||
if the company is located in France or in any DOM-TOM.
|
||||
|
||||
.. note:: If you run a multi-companies environment, only the documents of
|
||||
such companies are impacted.
|
||||
|
||||
Security
|
||||
~~~~~~~~
|
||||
|
||||
To ensure the inalterability, every order or journal entry is encrypted
|
||||
upon validation.
|
||||
This number (or hash) is calculated from the key data of the document as
|
||||
well as from the hash of the precedent documents.
|
||||
|
||||
The module introduces an interface to test the data inalterability.
|
||||
If any information is modified on a document after its validation,
|
||||
the test will fail. The algorithm recomputes all the hashes and compares them
|
||||
against the initial ones. In case of failure, the system points out the first
|
||||
corrupted document recorded in the system.
|
||||
|
||||
Users with *Manager* access rights can launch the inalterability check.
|
||||
For POS orders, go to
|
||||
:menuselection:`Point of Sales --> Reporting --> French Statements`.
|
||||
For invoices or journal entries,
|
||||
go to :menuselection:`Invoicing/Accounting --> Reporting --> French Statements`.
|
||||
|
||||
Storage
|
||||
~~~~~~~
|
||||
|
||||
The system also processes automatic sales closings on a daily, monthly
|
||||
and annual basis.
|
||||
Such closings distinctly compute the sales total of the period as well as
|
||||
the cumulative grand totals from the very first sales entry recorded
|
||||
in the system.
|
||||
|
||||
Closings can be found in the *French Statements* menu of Point of Sale,
|
||||
Invoicing and Accounting apps.
|
||||
|
||||
.. note::
|
||||
* Closings compute the totals for journal entries of sales journals (Journal Type = Sales).
|
||||
|
||||
* For multi-companies environments, such closings are performed by company.
|
||||
|
||||
* POS orders are posted as journal entries at the closing of the POS session.
|
||||
Closing a POS session can be done anytime.
|
||||
To prompt users to do it on a daily basis, the module prevents from resuming
|
||||
a session opened more than 24 hours ago.
|
||||
Such a session must be closed before selling again.
|
||||
|
||||
* A period’s total is computed from all the journal entries posted after the
|
||||
previous closing of the same type, regardless of their posting date.
|
||||
If you record a new sales transaction for a period already closed,
|
||||
it will be counted in the very next closing.
|
||||
|
||||
.. tip:: For test & audit purposes such closings can be manually generated in the
|
||||
developer mode. Go to
|
||||
:menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`
|
||||
to do so.
|
||||
|
||||
|
||||
Responsibilities
|
||||
----------------
|
||||
|
||||
Do not uninstall the module! If you do so, the hashes will be reset and none
|
||||
of your past data will be longer guaranteed as being inalterable.
|
||||
|
||||
Users remain responsible for their Odoo instance and must use it with
|
||||
due diligence. It is not permitted to modify the source code which guarantees
|
||||
the inalterability of data.
|
||||
|
||||
Odoo absolves itself of all and any responsibility in case of changes
|
||||
in the module’s functions caused by 3rd party applications not certified by Odoo.
|
||||
|
||||
|
||||
More Information
|
||||
----------------
|
||||
|
||||
You will find more information about this legislation in the official documents:
|
||||
|
||||
* `Frequently Asked Questions <https://www.economie.gouv.fr/files/files/directions_services/dgfip/controle_fiscal/actualites_reponses/logiciels_de_caisse.pdf>`__
|
||||
* `Official Statement <http://bofip.impots.gouv.fr/bofip/10691-PGP.html?identifiant=BOI-TVA-DECLA-30-10-30-20160803>`__
|
||||
* `Item 88 of Finance Law 2016 <https://www.legifrance.gouv.fr/affichTexteArticle.do?idArticle=JORFARTI000031732968&categorieLien=id&cidTexte=JORFTEXT000031732865>`__
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -0,0 +1,34 @@
|
||||
=======
|
||||
Germany
|
||||
=======
|
||||
|
||||
German Chart of Accounts
|
||||
========================
|
||||
|
||||
The chart of accounts SKR03 and SKR04 are both supported in Odoo. You can choose the
|
||||
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.
|
||||
|
||||
.. tip::
|
||||
|
||||
When you create a new SaaS database, the SKR03 is installed by default.
|
||||
|
||||
German Accounting Reports
|
||||
=========================
|
||||
|
||||
Here is the list of German-specific reports available on Odoo Enterprise:
|
||||
|
||||
- Balance Sheet
|
||||
- Profit & Loss
|
||||
- Tax Report (Umsatzsteuervoranmeldung)
|
||||
- Partner VAT Intra
|
||||
|
||||
Export from Odoo to Datev
|
||||
=========================
|
||||
|
||||
It is possible to export your accounting entries from Odoo to Datev. To be able to use this
|
||||
feature, the german accounting localization needs to be installed on your Odoo Enterprise database.
|
||||
Then you can go in :menuselection:`Accounting --> Reporting --> General Ledger` then click on the
|
||||
**Export Datev (csv)** button.
|
||||
@@ -0,0 +1,126 @@
|
||||
==========
|
||||
Italy (IT)
|
||||
==========
|
||||
|
||||
Questa guida spiegherà come utilizzare la fattura elettronica in Odoo e
|
||||
come configurare correttamente i dati aziendali, i contatti e la
|
||||
contabilità. Per testare la fattura elettronica i dati devono essere
|
||||
reali e non inventati, altrimenti il sistema dell’agenzia delle entrate
|
||||
non riconoscerà l’interscambio di informazioni.
|
||||
|
||||
Configurare le informazioni sulla tua Azienda
|
||||
=============================================
|
||||
|
||||
Il passo successivo è la configurazione delle informazioni necessarie al
|
||||
funzionamento della fatturazione elettronica. Si può accedere alla
|
||||
schermata dall’applicazione Impostazioni: selezionare “Utenti e aziende”
|
||||
e scegliere Aziende. Accedere quindi alle informazioni sulla Azienda per
|
||||
cui si desidera configurare la fatturazione elettronica.
|
||||
|
||||
I dati necessari al funzionamento dello strumento di fatturazione
|
||||
elettronica sono i seguenti:
|
||||
|
||||
- Server PEC. Le informazioni sul server utilizzato dal tuo indirizzo
|
||||
di posta elettronica certificata sono fornite dal tuo fornitore o dal
|
||||
Ministero. Lo stesso server deve essere configurato come server che
|
||||
gestisce tutta la corrispondenza mail in Odoo, per saperne di più si
|
||||
puo’ consultare la relativa
|
||||
`guida <https://www.odoo.com/documentation/user/12.0/discuss/email_servers.html>`__.
|
||||
|
||||
- Indirizzo PEC dell’ Azienda, tale indirizzo deve essere lo stesso
|
||||
registrato presso l’Agenzia delle Entrate per l’utilizzo dei servizi
|
||||
di fatturazione elettronica.
|
||||
|
||||
- Indirizzo PEC dell’Agenzia delle Entrate. La mail sarà fornito al
|
||||
momento della registrazione della tua PEC presso l’Agenzia delle
|
||||
Entrate, ricorda che l’Agenzia delle Entrate potrebbe cambiare questo
|
||||
indirizzo in seguito, previa comunicazione.
|
||||
|
||||
- Partita IVA e Codice Fiscale. Per far si che la Fatturazione
|
||||
Elettronica funzioni correttamente, questi cambi devono essere
|
||||
compilati correttamente.
|
||||
|
||||
- Regime Fiscale. Il regime fiscale a cui è sottoposta l’Azienda deve
|
||||
essere selezionato scegliendo dalla lista precompilata fornita da
|
||||
Odoo. Chiedi al commercialista qual’è il corretto regime fiscale!
|
||||
|
||||
- Numero di Iscrizione nel registro delle Imprese.
|
||||
|
||||
.. image:: media/italy_IT01.png
|
||||
:align: center
|
||||
|
||||
|
||||
1. Configurare le impostazioni per la Fatturazione Elettronica
|
||||
--------------------------------------------------------------
|
||||
|
||||
- Numero di iscrizione nel registro Imprese tenuto presso la Camera di
|
||||
Commercio.
|
||||
|
||||
- Rappresentate Fiscale. Questa opzione è dedicata ad aziende con sede
|
||||
al di fuori del territorio nazionale ma conducenti attività
|
||||
commerciali in Italia rilevanti ai fini dell’IVA. È possibile
|
||||
indicare in questo campo se l’Azienda si avvale di un Rappresentate
|
||||
Fiscale in Italia.
|
||||
|
||||
.. image:: media/italy_IT02.png
|
||||
:align: center
|
||||
|
||||
|
||||
1. Configurare il profilo dei clienti
|
||||
-------------------------------------
|
||||
|
||||
Per un corretto utilizzo dell’applicazione, il profilo di clienti e
|
||||
fornitori, nell’applicazione contatti, deve essere configurato con le
|
||||
necessarie informazioni legali.
|
||||
|
||||
Selezionando il nome del cliente e accedendo quindi ai suoi dati, si
|
||||
trovano i seguenti campi che devono essere compilati: Indirizzo PEC,
|
||||
Codice Fiscale e Indice PA *che deve contere i 6-7 caratteri
|
||||
contenuti nell’indice PA e necessari per la comunicazione tramite
|
||||
fattura elettronica*.
|
||||
|
||||
.. image:: media/italy_IT03.png
|
||||
:align: center
|
||||
|
||||
|
||||
Il processo di fatturazione
|
||||
===========================
|
||||
|
||||
Si può procedere ad emettere una fattura seguendo le indicazioni
|
||||
dell’applicazione. Il momento che determina il formale invio della
|
||||
fattura è il momento in cui viene selezionata l’opzione “Valida”. La
|
||||
fattura viene quindi inviata: lo stato della sua consegna verrà
|
||||
notificato all’utente tramite pop-up sulla parte iniziale della
|
||||
schermata della fattura.
|
||||
|
||||
.. image:: media/italy_IT04.png
|
||||
:align: center
|
||||
|
||||
.. image:: media/italy_IT05.png
|
||||
:align: center
|
||||
|
||||
I messaggi che possono apparire sono i seguenti:
|
||||
|
||||
1. Fattura invitata. In attesa di accettazione
|
||||
|
||||
2. Invio fallito. Puoi modificare la fattura ed inviarla di nuovo
|
||||
|
||||
3. La fattura è stata correttamente inviata ed accettata dal
|
||||
destinatario.
|
||||
|
||||
I vari stadi di spedizione e recezione della fattura sono visibili anche
|
||||
dall’elenco delle Fatture nella forma di icone, accanto alla colonna
|
||||
“Stato” dall’applicazione contabilità.
|
||||
|
||||
*Icona Rossa:* Invio fallito
|
||||
|
||||
*Icona Gialla:* Fattura invitata. In attesa di accettazione
|
||||
|
||||
*Icona Verde:* Fattura inviata e accettata dal destinatario
|
||||
|
||||
Per inviare la fattura tramite PEC e generare il file XML, basterà
|
||||
cliccare su invia. Il documento verrà poi mostrato tra gli allegati.
|
||||
|
||||
.. image:: media/italy_IT06.png
|
||||
:align: center
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 86 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 5.6 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 5.3 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 5.6 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 10 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 9.6 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 26 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 25 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 3.0 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 43 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 55 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 54 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 6.9 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 8.8 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 47 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 64 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 46 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 5.5 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 6.8 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 72 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 8.2 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 6.1 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 2.3 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 2.7 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 2.4 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 3.9 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 7.3 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 8.2 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 5.2 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 54 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 56 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 57 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 2.6 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 6.3 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 6.1 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 3.1 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 44 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 7.7 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 23 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 8.8 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 10 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 22 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 48 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 61 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 58 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 39 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 30 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 5.1 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 800 B |
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 22 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 4.9 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
@@ -0,0 +1,663 @@
|
||||
======
|
||||
Mexico
|
||||
======
|
||||
|
||||
.. note::
|
||||
This documentation is written assuming that you follow and know the official
|
||||
documentation regarding Invoicing, Sales and Accounting and that you have
|
||||
experience working with odoo on such areas, we are not intended to put
|
||||
here procedures that are already explained on those documents, just the
|
||||
information necessary to allow you use odoo in a Company with the country
|
||||
"Mexico" set.
|
||||
|
||||
Introduction
|
||||
~~~~~~~~~~~~
|
||||
|
||||
The mexican localization is a group of 3 modules:
|
||||
|
||||
1. **l10n_mx:** All basic data to manage the accounting, taxes and the
|
||||
chart of account, this proposed chart of account installed is a intended
|
||||
copy of the list of group codes offered by the `SAT`_.
|
||||
2. **l10n_mx_edi**: All regarding to electronic transactions, CFDI 3.2 and 3.3,
|
||||
payment complement, invoice addendum.
|
||||
3. **l10n_mx_reports**: All mandatory electronic reports for electronic
|
||||
accounting are here (Accounting app required).
|
||||
|
||||
With the Mexican localization in Odoo you will be able not just to comply
|
||||
with the required features by law in México but to use it as your
|
||||
accounting and invoicing system due to all the set of normal requirements for
|
||||
this market, becoming your Odoo in the perfect solution to administer your
|
||||
company in Mexico.
|
||||
|
||||
Configuration
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
.. tip::
|
||||
After the configuration we will give you the process to test everything,
|
||||
try to follow step by step in order to allow you to avoid expend time on
|
||||
fix debugging problems. In any step you can recall the step and try again.
|
||||
|
||||
1. Install the Mexican Accounting Localization
|
||||
----------------------------------------------
|
||||
|
||||
For this, go in Apps and search for Mexico. Then click on *Install*.
|
||||
|
||||
.. image:: media/mexico01.png
|
||||
:align: center
|
||||
|
||||
.. tip::
|
||||
When creating a database from www.odoo.com, if you choose Mexico
|
||||
as country when creating your account, the mexican localization will be
|
||||
automatically installed.
|
||||
|
||||
2. Electronic Invoices (CDFI 3.2 and 3.3 format)
|
||||
------------------------------------------------
|
||||
|
||||
To enable this requirement in Mexico go to configuration in accounting Go in
|
||||
:menuselection:`Accounting --> Settings` and enable the option on the image
|
||||
with this you will be able to generate the signed invoice (CFDI 3.2 and 3.3)
|
||||
and generate the payment complement signed as well (3.3 only) all fully
|
||||
integrate with the normal invoicing flow in Odoo.
|
||||
|
||||
.. image:: media/mexico02.png
|
||||
:align: center
|
||||
|
||||
.. _mx-legal-info:
|
||||
|
||||
3. Set you legal information in the company
|
||||
-------------------------------------------
|
||||
|
||||
First, make sure that your company is configured with the correct data.
|
||||
Go in :menuselection:`Settings --> Users --> Companies`
|
||||
and enter a valid address and VAT for
|
||||
your company. Don’t forget to define a mexican fiscal position on your
|
||||
company’s contact.
|
||||
|
||||
.. tip::
|
||||
If you want use the Mexican localization on test mode, you can put any known
|
||||
address inside Mexico with all fields for the company address and
|
||||
set the vat to **EKU9003173C9**.
|
||||
|
||||
.. image:: media/mexico03.png
|
||||
:align: center
|
||||
|
||||
.. warning::
|
||||
From a legal point of view, a Mexican company must use the local currency (MXN).
|
||||
Therefore, Odoo does not provide features to manage an alternative configuration.
|
||||
If you want to manage another currency, let MXN be the default currency and use
|
||||
price list instead.
|
||||
|
||||
4. Set the proper "Fiscal Position" on the partner that represent the company
|
||||
-----------------------------------------------------------------------------
|
||||
|
||||
Go In the same form where you are editing the company save the record in
|
||||
order to set this form as a readonly and on readonly view click on the partner
|
||||
link, then edit it and set in the *Invoicing* tab the proper Fiscal Information
|
||||
(for the **Test Environment** this must be *601 - General de Ley Personas
|
||||
Morales*, just search it as a normal Odoo field if you can't see the option).
|
||||
|
||||
5. Enabling CFDI Version 3.3
|
||||
----------------------------
|
||||
|
||||
.. warning::
|
||||
This steps are only necessary when you will enable the CFDI 3.3 (only available
|
||||
for V11.0 and above) if you do not have Version 11.0 or above on your
|
||||
SaaS instance please ask for an upgrade sending a ticket to support in
|
||||
https://www.odoo.com/help.
|
||||
|
||||
Enable debug mode:
|
||||
|
||||
.. image:: media/mexico10.png
|
||||
:align: center
|
||||
|
||||
Go and look the following technical parameter, on
|
||||
:menuselection:`Settings --> Technical --> Parameters --> System Parameters`
|
||||
and set the parameter called *l10n_mx_edi_cfdi_version* to 3.3 (Create it if
|
||||
the entry with this name does not exist).
|
||||
|
||||
.. warning::
|
||||
The CFDI 3.2 will be legally possible until November 30th 2017 enable the
|
||||
3.3 version will be a mandatory step to comply with the new `SAT resolution`_
|
||||
in any new database created since v11.0 released CFDI 3.3 is the default
|
||||
behavior.
|
||||
|
||||
.. image:: media/mexico11.png
|
||||
:align: center
|
||||
|
||||
Important considerations when yo enable the CFDI 3.3
|
||||
====================================================
|
||||
|
||||
Your tax which represent the VAT 16% and 0% must have the "Factor Type" field
|
||||
set to "Tasa".
|
||||
|
||||
.. image:: media/mexico12.png
|
||||
:align: center
|
||||
.. image:: media/mexico13.png
|
||||
:align: center
|
||||
|
||||
You must go to the Fiscal Position configuration and set the proper code (it is
|
||||
the first 3 numbers in the name) for example for the test one you should set
|
||||
601, it will look like the image.
|
||||
|
||||
.. image:: media/mexico14.png
|
||||
:align: center
|
||||
|
||||
All products must have for CFDI 3.3 the "SAT code" and the field "Reference"
|
||||
properly set, you can export them and re import them to do it faster.
|
||||
|
||||
.. image:: media/mexico15.png
|
||||
:align: center
|
||||
|
||||
6. Configure the PAC in order to sign properly the invoices
|
||||
-----------------------------------------------------------
|
||||
|
||||
To configure the EDI with the **PACs**, you can go in
|
||||
:menuselection:`Accounting --> Settings --> Electronic Invoicing (MX)`.
|
||||
You can choose a PAC within the **List of supported PACs** on the *PAC field*
|
||||
and then enter your PAC username and PAC password.
|
||||
|
||||
.. warning::
|
||||
Remember you must sign up in the refereed PAC before hand, that process
|
||||
can be done with the PAC itself on this case we will have two
|
||||
(2) availables `Finkok`_ and `Solución Factible`_.
|
||||
|
||||
You must process your **Private Key (CSD)** with the SAT institution before
|
||||
follow this steps, if you do not have such information please try all the
|
||||
"Steps for Test" and come back to this process when you finish the process
|
||||
proposed for the SAT in order to set this information for your production
|
||||
environment with real transactions.
|
||||
|
||||
.. image:: media/mexico04.png
|
||||
:align: center
|
||||
|
||||
.. tip::
|
||||
If you ticked the box *MX PAC test environment* there is no need
|
||||
to enter a PAC username or password.
|
||||
|
||||
.. image:: media/mexico05.png
|
||||
:align: center
|
||||
|
||||
.. tip::
|
||||
Here is a SAT certificate you can use if you want to use the *Test
|
||||
Environment* for the Mexican Accounting Localization.
|
||||
|
||||
:download:` Certificate <files/certificate.cer>`
|
||||
:download:` Certificate Key <files/certificate.key>`
|
||||
- **Password:** 12345678a
|
||||
|
||||
7. Configure the tag in sales taxes
|
||||
-----------------------------------
|
||||
|
||||
This tag is used to set the tax type code, transferred or withhold, applicable
|
||||
to the concept in the CFDI.
|
||||
So, if the tax is a sale tax the "Tag" field should be "IVA", "ISR" or "IEPS".
|
||||
|
||||
.. image:: media/mexico33.png
|
||||
:align: center
|
||||
|
||||
Note that the default taxes already has a tag assigned, but when you create a
|
||||
new tax you should choose a tag.
|
||||
|
||||
Usage and testing
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
Invoicing
|
||||
---------
|
||||
|
||||
To use the mexican invoicing you just need to do a normal invoice following
|
||||
the normal Odoo's behaviour.
|
||||
|
||||
Once you validate your first invoice a correctly signed invoice should look
|
||||
like this:
|
||||
|
||||
|
||||
.. image:: media/mexico07.png
|
||||
:align: center
|
||||
|
||||
You can generate the PDF just clicking on the Print button on the invoice or
|
||||
sending it by email following the normal process on odoo to send your invoice
|
||||
by email.
|
||||
|
||||
.. image:: media/mexico08.png
|
||||
:align: center
|
||||
|
||||
Once you send the electronic invoice by email this is the way it should looks
|
||||
like.
|
||||
|
||||
.. image:: media/mexico09.png
|
||||
:align: center
|
||||
|
||||
Cancelling invoices
|
||||
-------------------
|
||||
|
||||
The cancellation process is completely linked to the normal cancellation in Odoo.
|
||||
|
||||
If the invoice is not paid.
|
||||
|
||||
- Go to to the customer invoice journal where the invoice belong to
|
||||
|
||||
.. image:: media/mexico28.png
|
||||
:align: center
|
||||
|
||||
.. image:: media/mexico29.png
|
||||
:align: center
|
||||
|
||||
- Check the "Allow cancelling entries" field
|
||||
|
||||
.. image:: media/mexico29.png
|
||||
:align: center
|
||||
|
||||
- Go back to your invoice and click on the button "Cancel Invoice"
|
||||
|
||||
.. image:: media/mexico30.png
|
||||
:align: center
|
||||
|
||||
- For security reasons it is recommendable return the check on the to allow
|
||||
cancelling to false again, then go to the journal and un check such field.
|
||||
|
||||
**Legal considerations**
|
||||
|
||||
- A cancelled invoice will automatically cancelled on the SAT.
|
||||
- If you retry to use the same invoice after cancelled, you will have as much
|
||||
cancelled CFDI as you tried, then all those xml are important to maintain a
|
||||
good control of the cancellation reasons.
|
||||
- You must unlink all related payment done to an invoice on odoo before
|
||||
cancel such document, this payments must be cancelled to following the same
|
||||
approach but setting the "Allow Cancel Entries" in the payment itself.
|
||||
|
||||
Payments (Just available for CFDI 3.3)
|
||||
--------------------------------------
|
||||
|
||||
To generate the payment complement you only need to follow the normal payment
|
||||
process in Odoo, this considerations to understand the behavior are important.
|
||||
|
||||
1. To generate payment complement the payment term in the invoice must be
|
||||
PPD, because It is the expected behavior legally required for
|
||||
"Cash payment".
|
||||
|
||||
**1.1. How can I generate an invoice with payment term `PUE`?**
|
||||
|
||||
`According to the SAT documentation`_ a payment is classified as ``PUE`` if
|
||||
the invoice was agreed to be fully payed before the 17th of the next
|
||||
calendar month (the next month of the CFDI date), any other condition
|
||||
will generate a ``PPD`` invoice.
|
||||
|
||||
**1.2. How can I get this with Odoo?**
|
||||
|
||||
In order to set the appropriate CFDI payment term (PPD or PUE), you can
|
||||
easily set it by using the ``Payment Terms`` defined in the invoice.
|
||||
|
||||
- If an invoice is generated without ``Payment Term`` the attribute
|
||||
``MetodoPago`` will be ``PUE``.
|
||||
|
||||
- Today, if is the first day of the month and is generated an invoice with
|
||||
``Payment Term`` ``30 Net Days`` the ``Due Date`` calculated is going to
|
||||
be the first day of the following month, this means its before the 17th
|
||||
of the next month, then the attribute ``MetodoPago`` will be ``PUE``.
|
||||
|
||||
- Today, if an invoice is generated with ``Payment Term`` ``30 Net Days``
|
||||
and the ``Due Date`` is higher than the day 17 of the next month the
|
||||
``MetodoPago`` will be ``PPD``.
|
||||
|
||||
- If having a ``Payment Term`` with 2 lines or more, for example
|
||||
``30% Advance End of Following Month``, this is an installments term,
|
||||
then the attribute ``MetodoPago`` will be ``PPD``.
|
||||
|
||||
2. To test a normal signed payment just create an invoice with payment term
|
||||
``30% Advance End of Following Month`` and then register a payment to it.
|
||||
3. You must print the payment in order to retrieve the PDF properly.
|
||||
4. Regarding the "Payments in Advance" you must create a proper invoice with
|
||||
the payment in advance itself as a product line setting the proper SAT code
|
||||
following the procedure on the official documentation `given by the SAT`_
|
||||
in the section **Apéndice 2 Procedimiento para la emisión de los CFDI en el
|
||||
caso de anticipos recibidos**.
|
||||
5. Related to topic 4 it is blocked the possibility to create a Customer
|
||||
Payment without a proper invoice.
|
||||
|
||||
Accounting
|
||||
----------
|
||||
The accounting for Mexico in odoo is composed by 3 reports:
|
||||
|
||||
1. Chart of Account (Called and shown as COA).
|
||||
2. Electronic Trial Balance.
|
||||
3. DIOT report.
|
||||
|
||||
1 and 2 are considered as the electronic accounting, and the DIOT is a report
|
||||
only available on the context of the accounting.
|
||||
|
||||
You can find all those reports in the original report menu on Accounting app.
|
||||
|
||||
.. image:: media/mexico16.png
|
||||
:align: center
|
||||
|
||||
Electronic Accounting (Requires Accounting App)
|
||||
===============================================
|
||||
|
||||
Electronic Chart of account CoA
|
||||
-------------------------------
|
||||
|
||||
The electronic accounting never has been easier, just go to
|
||||
:menuselection:`Accounting --> Reporting --> Mexico --> COA` and click on the
|
||||
button **Export for SAT (XML)**
|
||||
|
||||
.. image:: media/mexico19.png
|
||||
:align: center
|
||||
|
||||
**How to add new accounts?**
|
||||
|
||||
If you add an account with the coding convention NNN.YY.ZZ where NNN.YY is a
|
||||
SAT coding group then your account will be automatically configured.
|
||||
|
||||
Example to add an Account for a new Bank account go to
|
||||
:menuselection:`Accounting --> Settings --> Chart of Account` and then create
|
||||
a new account on the button "Create" and try to create an account with the
|
||||
number 102.01.99 once you change to set the name you will see a tag
|
||||
automatically set, the tags set are the one picked to be used in the COA on
|
||||
xml.
|
||||
|
||||
.. image:: media/mexico20.png
|
||||
:align: center
|
||||
|
||||
**What is the meaning of the tag?**
|
||||
|
||||
To know all possible tags you can read the `Anexo 24`_ in the SAT
|
||||
website on the section called **Código agrupador de cuentas del SAT**.
|
||||
|
||||
.. tip::
|
||||
When you install the module l10n_mx and yous Chart of Account rely on it
|
||||
(this happen automatically when you install setting Mexico as country on
|
||||
your database) then you will have the more common tags if the tag you need
|
||||
is not created you can create one on the fly.
|
||||
|
||||
Electronic Trial Balance
|
||||
------------------------
|
||||
|
||||
Exactly as the COA but with Initial balance debit and credit, once you have
|
||||
your coa properly set you can go to :menuselection:`Accounting --> Reports --> Mexico --> Trial Balance`
|
||||
this is automatically generated, and can be exported to XML using the button
|
||||
in the top **Export for SAT (XML)** with the previous selection of the
|
||||
period you want to export.
|
||||
|
||||
.. image:: media/mexico21.png
|
||||
:align: center
|
||||
|
||||
All the normal auditory and analysis features are available here also as any
|
||||
regular Odoo Report.
|
||||
|
||||
DIOT Report (Requires Accounting App)
|
||||
=====================================
|
||||
|
||||
**What is the DIOT and the importance of presenting it SAT**
|
||||
|
||||
When it comes to procedures with the SAT Administration Service we know that
|
||||
we should not neglect what we present. So that things should not happen in Odoo.
|
||||
|
||||
The DIOT is the Informational Statement of Operations with Third Parties (DIOT),
|
||||
which is an an additional obligation with the VAT, where we must give the status
|
||||
of our operations to third parties, or what is considered the same, with our
|
||||
providers.
|
||||
|
||||
This applies both to individuals and to the moral as well, so if we have VAT
|
||||
for submitting to the SAT and also dealing with suppliers it is necessary to.
|
||||
submit the DIOT:
|
||||
|
||||
**When to file the DIOT and in what format?**
|
||||
|
||||
It is simple to present the DIOT, since like all format this you can obtain
|
||||
it in the page of the SAT, it is the electronic format A-29 that you can find
|
||||
in the SAT website.
|
||||
|
||||
Every month if you have operations with third parties it is necessary to
|
||||
present the DIOT, just as we do with VAT, so that if in January we have deals
|
||||
with suppliers, by February we must present the information pertinent to
|
||||
said data.
|
||||
|
||||
**Where the DIOT is presented?**
|
||||
|
||||
You can present DIOT in different ways, it is up to you which one you will
|
||||
choose and which will be more comfortable for you than you will present every
|
||||
month or every time you have dealings with suppliers.
|
||||
|
||||
The A-29 format is electronic so you can present it on the SAT page, but this
|
||||
after having made up to 500 records.
|
||||
|
||||
Once these 500 records are entered in the SAT, you must present them to the
|
||||
Local Taxpayer Services Administration (ALSC) with correspondence to your tax
|
||||
address, these records can be presented in a digital storage medium such as a
|
||||
CD or USB, which once validated you will be returned, so do not doubt that you
|
||||
will still have these records and of course, your CD or USB.
|
||||
|
||||
**One more fact to know: the Batch load?**
|
||||
|
||||
When reviewing the official SAT documents on DIOT, you will find the Batch
|
||||
load, and of course the first thing we think is what is that ?, and according
|
||||
to the SAT site is:
|
||||
|
||||
The "batch upload" is the conversion of records databases of transactions with
|
||||
suppliers made by taxpayers in text files (.txt). These files have the
|
||||
necessary structure for their application and importation into the system of
|
||||
the Informative Declaration of Operations with third parties, avoiding the
|
||||
direct capture and consequently, optimizing the time invested in its
|
||||
integration for the presentation in time and form to the SAT.
|
||||
|
||||
You can use it to present the DIOT, since it is allowed, which will make this
|
||||
operation easier for you, so that it does not exist to avoid being in line
|
||||
with the SAT in regard to the Information Statement of Operations with
|
||||
Third Parties.
|
||||
|
||||
You can find the `official information here`_.
|
||||
|
||||
**How Generate this report in odoo?**
|
||||
|
||||
- Go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions with third partied (DIOT)`.
|
||||
|
||||
.. image:: media/mexico23.png
|
||||
:align: center
|
||||
|
||||
- A report view is shown, select last month to report the immediate before
|
||||
month you are or left the current month if it suits to you.
|
||||
|
||||
.. image:: media/mexico25.png
|
||||
:align: center
|
||||
|
||||
- Click on "Export (TXT).
|
||||
|
||||
.. image:: media/mexico24.png
|
||||
:align: center
|
||||
|
||||
- Save in a secure place the downloaded file and go to SAT website and follow
|
||||
the necessary steps to declare it.
|
||||
|
||||
Important considerations on your Supplier and Invice data for the DIOT
|
||||
======================================================================
|
||||
|
||||
- All suppliers must have set the fields on the accounting tab called "DIOT
|
||||
Information", the *L10N Mx Nationality* field is filled with just select the
|
||||
proper country in the address, you do not need to do anything else there, but
|
||||
the *L10N Mx Type Of Operation* must be filled by you in all your suppliers.
|
||||
|
||||
.. image:: media/mexico22.png
|
||||
:align: center
|
||||
|
||||
- There are 3 options of VAT for this report, 16%, 0% and exempt, an invoice
|
||||
line in odoo is considered exempt if no tax on it, the other 2 taxes are
|
||||
properly configured already.
|
||||
- Remember to pay an invoice which represent a payment in advance you must
|
||||
ask for the invoice first and then pay it and reconcile properly the payment
|
||||
following standard odoo procedure.
|
||||
- You do not need all you data on partners filled to try to generate the
|
||||
supplier invoice, you can fix this information when you generate the report
|
||||
itself.
|
||||
- Remember this report only shows the Supplier Invoices that were actually paid.
|
||||
|
||||
If some of this considerations are not taken into account a message like this
|
||||
will appear when generate the DIOT on TXT with all the partners you need to
|
||||
check on this particular report, this is the reason we recommend use this
|
||||
report not just to export your legal obligation but to generate it before
|
||||
the end of the month and use it as your auditory process to see all your
|
||||
partners are correctly set.
|
||||
|
||||
.. image:: media/mexico26.png
|
||||
:align: center
|
||||
|
||||
Extra Recommended features
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Contact Module (Free)
|
||||
---------------------
|
||||
|
||||
If you want to administer properly your customers, suppliers and addresses
|
||||
this module even if it is not a technical need, it is highly recommended to
|
||||
install.
|
||||
|
||||
Multi currency (Requires Accounting App)
|
||||
----------------------------------------
|
||||
|
||||
In Mexico almost all companies send and receive payments in different
|
||||
currencies if you want to manage such capability you should enable the multi
|
||||
currency feature and you should enable the synchronization with **Banxico**,
|
||||
such feature allow you retrieve the proper exchange rate automatically
|
||||
retrieved from SAT and not being worried of put such information daily in the
|
||||
system manually.
|
||||
|
||||
Go to settings and enable the multi currency feature.
|
||||
|
||||
.. image:: media/mexico17.png
|
||||
:align: center
|
||||
|
||||
Enabling Explicit errors on the CFDI using the XSD local validator (CFDI 3.3)
|
||||
-----------------------------------------------------------------------------
|
||||
|
||||
Frequently you want receive explicit errors from the fields incorrectly set
|
||||
on the xml, those errors are better informed to the user if the check is
|
||||
enable, to enable the Check with xsd feature follow the next steps (with
|
||||
debug mode enabled).
|
||||
|
||||
- Go to :menuselection:`Settings --> Technical --> Actions --> Server Actions`
|
||||
- Look for the Action called "Download XSD files to CFDI"
|
||||
- Click on button "Create Contextual Action"
|
||||
- Go to the company form :menuselection:`Settings --> Users&Companies --> Companies`
|
||||
- Open any company you have.
|
||||
- Click on "Action" and then on "Download XSD file to CFDI".
|
||||
|
||||
.. image:: media/mexico18.png
|
||||
:align: center
|
||||
|
||||
Now you can make an invoice with any error (for example a product without
|
||||
code which is pretty common) and an explicit error will be shown instead a
|
||||
generic one with no explanation.
|
||||
|
||||
.. note::
|
||||
If you see an error like this:
|
||||
|
||||
The cfdi generated is not valid
|
||||
|
||||
attribute decl. 'TipoRelacion', attribute 'type': The QName value
|
||||
'{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_TipoRelacion' does
|
||||
not resolve to a(n) simple type definition., line 36
|
||||
|
||||
This can be caused because of a database backup restored in anothe server,
|
||||
or when the XSD files are not correctly downloaded. Follow the same steps
|
||||
as above but:
|
||||
|
||||
- Go to the company in which the error occurs.
|
||||
- Click on "Action" and then on "Download XSD file to CFDI".
|
||||
|
||||
|
||||
FAQ
|
||||
~~~
|
||||
|
||||
- **Error message** (Only applicable on CFDI 3.3):
|
||||
|
||||
:9:0:ERROR:SCHEMASV:SCHEMAV_CVC_MINLENGTH_VALID: Element '{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': [facet 'minLength'] The value '' has a length of '0'; this underruns the allowed minimum length of '1'.
|
||||
|
||||
:9:0:ERROR:SCHEMASV:SCHEMAV_CVC_PATTERN_VALID: Element '{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': [facet 'pattern'] The value '' is not accepted by the pattern '[^|]{1,100}'.
|
||||
|
||||
.. tip::
|
||||
**Solution:** You forget to set the proper "Reference" field in the product,
|
||||
please go to the product form and set your internal reference properly.
|
||||
|
||||
- **Error message**:
|
||||
|
||||
:6:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}RegimenFiscal': The attribute 'Regimen' is required but missing.
|
||||
|
||||
:5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'RegimenFiscal' is required but missing.
|
||||
|
||||
.. tip::
|
||||
**Solution:** You forget to set the proper "Fiscal Position" on the
|
||||
partner of the company, go to customers, remove the customer filter and
|
||||
look for the partner called as your company and set the proper fiscal
|
||||
position which is the kind of business you company does related to SAT
|
||||
list of possible values, antoher option can be that you forgot follow the
|
||||
considerations about fiscal positions.
|
||||
|
||||
Yo must go to the Fiscal Position configuration and set the proper code (it is
|
||||
the first 3 numbers in the name) for example for the test one you should set
|
||||
601, it will look like the image.
|
||||
|
||||
.. image:: media/mexico27.png
|
||||
:align: center
|
||||
|
||||
.. tip::
|
||||
For testing purposes this value must be *601 - General de Ley Personas Morales*
|
||||
which is the one required for the demo VAT.
|
||||
|
||||
- **Error message**:
|
||||
|
||||
:2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'FormaPago': [facet 'enumeration'] The value '' is not an element of the set {'01', '02', '03', '04', '05', '06', '08', '12', '13', '14', '15', '17', '23', '24', '25', '26', '27', '28', '29', '30', '99'}
|
||||
|
||||
.. tip::
|
||||
**Solution:** The payment method is required on your invoice.
|
||||
|
||||
.. image:: media/mexico31.png
|
||||
:align: center
|
||||
|
||||
- **Error message**:
|
||||
|
||||
:2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': [facet 'enumeration'] The value '' is not an element of the set {'00
|
||||
:2:0:ERROR:SCHEMASV:SCHEMAV_CVC_DATATYPE_VALID_1_2_1: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': '' is not a valid value of the atomic type '{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_CodigoPostal'.
|
||||
:5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'Rfc' is required but missing.
|
||||
|
||||
.. tip::
|
||||
**Solution:** You must set the address on your company properly, this is a
|
||||
mandatory group of fields, you can go to your company configuration on
|
||||
:menuselection:`Settings --> Users & Companies --> Companies` and fill
|
||||
all the required fields for your address following the step
|
||||
:ref:`mx-legal-info`.
|
||||
|
||||
- **Error message**:
|
||||
|
||||
:2:0:ERROR:SCHEMASV:SCHEMAV_CVC_DATATYPE_VALID_1_2_1: Element '{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': '' is not a valid value of the atomic type '{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_CodigoPostal'.
|
||||
|
||||
.. tip::
|
||||
**Solution:** The postal code on your company address is not a valid one
|
||||
for Mexico, fix it.
|
||||
|
||||
.. image:: media/mexico32.png
|
||||
:align: center
|
||||
|
||||
- **Error message**:
|
||||
|
||||
:18:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is required but missing.
|
||||
:34:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element '{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is required but missing.", '')
|
||||
|
||||
.. tip::
|
||||
**Solution:** Set the mexican name for the tax 0% and 16% in your system
|
||||
and used on the invoice.
|
||||
|
||||
Your tax which represent the VAT 16% and 0% must have the "Factor Type" field
|
||||
set to "Tasa".
|
||||
|
||||
.. image:: media/mexico12.png
|
||||
:align: center
|
||||
.. image:: media/mexico13.png
|
||||
:align: center
|
||||
|
||||
.. _SAT: http://www.sat.gob.mx/fichas_tematicas/buzon_tributario/Documents/Anexo24_05012015.pdf
|
||||
.. _Finkok: https://www.finkok.com/contacto.html
|
||||
.. _`Solución Factible`: https://solucionfactible.com/sf/v3/timbrado.jsp
|
||||
.. _`SAT resolution`: http://sat.gob.mx/informacion_fiscal/factura_electronica/Paginas/Anexo_20_version3.3.aspx
|
||||
.. _`According to the SAT documentation`: https://www.sat.gob.mx/cs/Satellite?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1461173400586&ssbinary=true
|
||||
.. _`given by the SAT`: http://sat.gob.mx/informacion_fiscal/factura_electronica/Documents/GuiaAnexo20DPA.pdf
|
||||
.. _`Anexo 24`: http://www.sat.gob.mx/fichas_tematicas/buzon_tributario/Documents/Anexo24_05012015.pdf
|
||||
.. _`official information here`: http://www.sat.gob.mx/fichas_tematicas/declaraciones_informativas/Paginas/declaracion_informativa_terceros.aspx
|
||||
@@ -0,0 +1,23 @@
|
||||
Netherlands
|
||||
===========
|
||||
|
||||
XAF Export
|
||||
----------
|
||||
|
||||
With the Dutch accounting localization installed, you will be able to
|
||||
export all your accounting entries in XAF format. For this, you have to
|
||||
go in :menuselection:`Accounting --> Reporting --> General Ledger`, you
|
||||
define the entries you want to export using the filters (period, journals, ...)
|
||||
and then you click on the button **EXPORT (XAF)**.
|
||||
|
||||
Dutch Accounting Reports
|
||||
------------------------
|
||||
|
||||
If you install the Dutch accounting localization, you will have access
|
||||
to some reports that are specific to the Netherlands such as :
|
||||
|
||||
- Profit & Loss
|
||||
|
||||
- Tax Report (Aangifte omzetbelasting)
|
||||
|
||||
- Intrastat Report (ICP)
|
||||
@@ -0,0 +1,31 @@
|
||||
=====
|
||||
Spain
|
||||
=====
|
||||
|
||||
Spanish Chart of Accounts
|
||||
=========================
|
||||
|
||||
In Odoo, there are several Spanish Chart of Accounts that are available by default:
|
||||
|
||||
- PGCE PYMEs 2008
|
||||
- PGCE Completo 2008
|
||||
- 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.
|
||||
|
||||
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 SaaS database, the PGCE PYMEs 2008 is installed by default.
|
||||
|
||||
Spanish Accounting Reports
|
||||
==========================
|
||||
|
||||
If the Spanish Accounting Localization is installed, you will have access to accounting reports specific to Spain:
|
||||
|
||||
- Balance Sheet
|
||||
- Tax Report (Modelo 111)
|
||||
- Tax Report (Modelo 115)
|
||||
- Tax Report (Modelo 303)
|
||||
|
||||
@@ -0,0 +1,130 @@
|
||||
===========
|
||||
Switzerland
|
||||
===========
|
||||
|
||||
ISR (In-payment Slip with Reference number)
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
The ISRs are payment slips used in Switzerland. You can print them
|
||||
directly from Odoo. On the customer invoices, there is a new button
|
||||
called *Print ISR*.
|
||||
|
||||
.. image:: media/switzerland00.png
|
||||
:align: center
|
||||
|
||||
.. 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.
|
||||
|
||||
.. image:: media/switzerland01.png
|
||||
:align: center
|
||||
|
||||
Then you open a pdf with the ISR.
|
||||
|
||||
.. image:: media/switzerland02.png
|
||||
:align: center
|
||||
|
||||
There exists two layouts for ISR: one with, and one without the bank
|
||||
coordinates. To choose which one to use, there is an option to print the
|
||||
bank information on the ISR. To activate it, go in
|
||||
:menuselection:`Accounting --> Configuration --> Settings --> Accounting Reports`
|
||||
and tick this box :
|
||||
|
||||
.. image:: media/switzerland03.png
|
||||
:align: center
|
||||
|
||||
Currency Rate Live Update
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
You can update automatically your currencies rates based on the Federal
|
||||
Tax Administration from Switzerland. For this, go in
|
||||
:menuselection:`Accounting --> Settings`, activate the multi-currencies setting and choose the service
|
||||
you want.
|
||||
|
||||
.. image:: media/switzerland04.png
|
||||
:align: center
|
||||
|
||||
Updated VAT for January 2018
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Starting from the 1st January 2018, new reduced VAT rates will be
|
||||
applied in Switzerland. The normal 8.0% rate will switch to 7.7% and the
|
||||
specific rate for the hotel sector will switch from 3.8% to 3.7%.
|
||||
|
||||
How to update your taxes in Odoo Enterprise (SaaS or On Premise)?
|
||||
-----------------------------------------------------------------
|
||||
|
||||
If you have the V11.1 version, all the work is already been done, you
|
||||
don't have to do anything.
|
||||
|
||||
If you have started on an earlier version, you first have to update the
|
||||
module "Switzerland - Accounting Reports". For this, you go in
|
||||
:menuselection:`Apps --> remove the filter "Apps" --> search for "Switzerland - Accounting Reports" --> open the module --> click on "upgrade"`.
|
||||
|
||||
.. image:: media/switzerland05.png
|
||||
:align: center
|
||||
|
||||
Once it has been done, you can work on creating new taxes for the
|
||||
updated rates.
|
||||
|
||||
.. tip::
|
||||
**Do not suppress or modify the existing taxes** (8.0% and 3.8%).
|
||||
You want to keep them since you may have to use both rates for a short
|
||||
period of time. Instead, remember to archive them once you have encoded
|
||||
all your 2017 transactions.
|
||||
|
||||
The creation of such taxes should be done in the following manner:
|
||||
|
||||
- **Purchase taxes**: copy the origin tax, change its name, label on
|
||||
invoice, rate and tax group (effective from v10 only)
|
||||
|
||||
- **Sale taxes**: copy the origin tax, change its name, label on
|
||||
invoice, rate and tax group (effective from v10 only). Since the
|
||||
vat report now shows the details for old and new rates, you
|
||||
should also set the tags accordingly to
|
||||
|
||||
- For 7.7% taxes: Switzerland VAT Form: grid 302 base, Switzerland
|
||||
VAT Form: grid 302 tax
|
||||
|
||||
- For 3.7% taxes: Switzerland VAT Form: grid 342 base, Switzerland
|
||||
VAT Form: grid 342 tax
|
||||
|
||||
You'll find below, as examples, the correct configuration for all taxes
|
||||
included in Odoo by default
|
||||
|
||||
+-------------------------------------------------+------------+------------------------+--------------------------------------+-----------------+---------------------------------------------------------------------------+
|
||||
| **Tax Name** | **Rate** | **Label on Invoice** | **Tax Group (effective from V10)** | **Tax Scope** | **Tag** |
|
||||
+=================================================+============+========================+======================================+=================+===========================================================================+
|
||||
| TVA 7.7% sur achat B&S (TN) | 7.7% | 7.7% achat | TVA 7.7% | Purchases | Switzerland VAT Form: grid 400 |
|
||||
+-------------------------------------------------+------------+------------------------+--------------------------------------+-----------------+---------------------------------------------------------------------------+
|
||||
| TVA 7.7% sur achat B&S (Incl. TN) | 7.7% | 7.7% achat Incl. | TVA 7.7% | Purchases | Switzerland VAT Form: grid 400 |
|
||||
+-------------------------------------------------+------------+------------------------+--------------------------------------+-----------------+---------------------------------------------------------------------------+
|
||||
| TVA 7.7% sur invest. et autres ch. (TN) | 7.7% | 7.7% invest. | TVA 7.7% | Purchases | Switzerland VAT Form: grid 405 |
|
||||
+-------------------------------------------------+------------+------------------------+--------------------------------------+-----------------+---------------------------------------------------------------------------+
|
||||
| TVA 7.7% sur invest. et autres ch. (Incl. TN) | 7.7% | 7.7% invest. Incl. | TVA 7.7% | Purchases | Switzerland VAT Form: grid 405 |
|
||||
+-------------------------------------------------+------------+------------------------+--------------------------------------+-----------------+---------------------------------------------------------------------------+
|
||||
| TVA 3.7% sur achat B&S (TS) | 3.7% | 3.7% achat | TVA 3.7% | Purchases | Switzerland VAT Form: grid 400 |
|
||||
+-------------------------------------------------+------------+------------------------+--------------------------------------+-----------------+---------------------------------------------------------------------------+
|
||||
| TVA 3.7% sur achat B&S (Incl. TS) | 3.7% | 3.7% achat Incl. | TVA 3.7% | Purchases | Switzerland VAT Form: grid 400 |
|
||||
+-------------------------------------------------+------------+------------------------+--------------------------------------+-----------------+---------------------------------------------------------------------------+
|
||||
| TVA 3.7% sur invest. et autres ch. (TS) | 3.7% | 3.7% invest | TVA 3.7% | Purchases | Switzerland VAT Form: grid 405 |
|
||||
+-------------------------------------------------+------------+------------------------+--------------------------------------+-----------------+---------------------------------------------------------------------------+
|
||||
| TVA 3.7% sur invest. et autres ch. (Incl. TS) | 3.7% | 3.7% invest Incl. | TVA 3.7% | Purchases | Switzerland VAT Form: grid 405 |
|
||||
+-------------------------------------------------+------------+------------------------+--------------------------------------+-----------------+---------------------------------------------------------------------------+
|
||||
| TVA due a 7.7% (TN) | 7.7% | 7.7% | TVA 7.7% | Sales | Switzerland VAT Form: grid 302 base, Switzerland VAT Form: grid 302 tax |
|
||||
+-------------------------------------------------+------------+------------------------+--------------------------------------+-----------------+---------------------------------------------------------------------------+
|
||||
| TVA due à 7.7% (Incl. TN) | 7.7% | 7.7% Incl. | TVA 7.7% | Sales | Switzerland VAT Form: grid 302 base, Switzerland VAT Form: grid 302 tax |
|
||||
+-------------------------------------------------+------------+------------------------+--------------------------------------+-----------------+---------------------------------------------------------------------------+
|
||||
| TVA due à 3.7% (TS) | 3.7% | 3.7% | TVA 3.7% | Sales | Switzerland VAT Form: grid 342 base, Switzerland VAT Form: grid 342 tax |
|
||||
+-------------------------------------------------+------------+------------------------+--------------------------------------+-----------------+---------------------------------------------------------------------------+
|
||||
| TVA due a 3.7% (Incl. TS) | 3.7% | 3.7% Incl. | TVA 3.7% | Sales | Switzerland VAT Form: grid 342 base, Switzerland VAT Form: grid 342 tax |
|
||||
+-------------------------------------------------+------------+------------------------+--------------------------------------+-----------------+---------------------------------------------------------------------------+
|
||||
|
||||
If you have questions or remarks, please contact our support using
|
||||
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.
|
||||
Reference in New Issue
Block a user