[MERGE] Forward port of 13.0 to 13.2
This commit is contained in:
Martin Trigaux
commit
b11a339786
@ -1,4 +1,6 @@
|
||||
{% extends "basic/layout.html" %}
|
||||
{% set html5_doctype = True %}
|
||||
|
||||
{%- block scripts %}
|
||||
{{ super() }}
|
||||
<script type="text/javascript" src="{{ pathto('_static/jquery.min.js', 1) }}"></script>
|
||||
@ -16,14 +18,9 @@
|
||||
{% set classes = classes + ['has_code_col'] %}
|
||||
{% endif %}
|
||||
|
||||
{%- block doctype -%}
|
||||
<!doctype html>
|
||||
{%- endblock -%}
|
||||
{%- block htmltitle -%}
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
{{ super() }}
|
||||
{%- endblock -%}
|
||||
{% if 'classes' in meta %}
|
||||
{% set classes = classes + meta['classes'].split() %}
|
||||
{% endif %}
|
||||
|
||||
{%- block linktags -%}
|
||||
{% for code, url in language_codes %}
|
||||
|
||||
@ -32,10 +32,6 @@ class BootstrapTranslator(nodes.NodeVisitor, object):
|
||||
html_subtitle = 'html_subtitle'
|
||||
|
||||
# <meta> tags
|
||||
meta = [
|
||||
'<meta http-equiv="X-UA-Compatible" content="IE=edge">',
|
||||
'<meta name="viewport" content="width=device-width, initial-scale=1">'
|
||||
]
|
||||
|
||||
def __init__(self, builder, document):
|
||||
# order of parameter swapped between Sphinx 1.x and 2.x, check if
|
||||
@ -45,6 +41,11 @@ class BootstrapTranslator(nodes.NodeVisitor, object):
|
||||
|
||||
super(BootstrapTranslator, self).__init__(document)
|
||||
self.builder = builder
|
||||
self.meta = [
|
||||
'', '',
|
||||
'\n <meta http-equiv="X-UA-Compatible" content="IE=edge">',
|
||||
'\n <meta name="viewport" content="width=device-width, initial-scale=1">'
|
||||
]
|
||||
self.body = []
|
||||
self.fragment = self.body
|
||||
self.html_body = self.body
|
||||
@ -74,6 +75,9 @@ class BootstrapTranslator(nodes.NodeVisitor, object):
|
||||
0xa0: u' '
|
||||
})
|
||||
|
||||
def add_meta(self, meta):
|
||||
self.meta.append('\n ' + meta)
|
||||
|
||||
def starttag(self, node, tagname, **attributes):
|
||||
tagname = tagname.lower()
|
||||
|
||||
@ -130,6 +134,14 @@ class BootstrapTranslator(nodes.NodeVisitor, object):
|
||||
def depart_document(self, node):
|
||||
pass
|
||||
|
||||
def visit_meta(self, node):
|
||||
if node.hasattr('lang'):
|
||||
node['xml:lang'] = node['lang']
|
||||
meta = self.starttag(node, 'meta', **node.non_default_attributes())
|
||||
self.add_meta(meta)
|
||||
def depart_meta(self, node):
|
||||
pass
|
||||
|
||||
def visit_section(self, node):
|
||||
# close "parent" or preceding section, unless this is the opening of
|
||||
# the first section
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 146 KiB After Width: | Height: | Size: 195 KiB |
BIN
_static/banners/studio.png
Normal file
BIN
_static/banners/studio.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 221 KiB |
73
_static/icons/pdf_missing.svg
Normal file
73
_static/icons/pdf_missing.svg
Normal file
@ -0,0 +1,73 @@
|
||||
<?xml version="1.0" encoding="iso-8859-1"?>
|
||||
<!-- Generator: Adobe Illustrator 16.0.0, SVG Export Plug-In . SVG Version: 6.00 Build 0) -->
|
||||
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
|
||||
<svg version="1.1" id="Capa_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
|
||||
width="32px" height="32px" fill="#ccc" viewBox="0 0 550.801 550.801" style="enable-background:new 0 0 550.801 550.801;"
|
||||
xml:space="preserve">
|
||||
<g>
|
||||
<g>
|
||||
<path d="M267.342,414.698c-6.613,0-10.884,0.585-13.413,1.165v85.72c2.534,0.586,6.616,0.586,10.304,0.586
|
||||
c26.818,0.189,44.315-14.576,44.315-45.874C308.738,429.079,292.803,414.698,267.342,414.698z"/>
|
||||
<path d="M152.837,414.313c-6.022,0-10.104,0.58-12.248,1.16v38.686c2.531,0.58,5.643,0.78,9.903,0.78
|
||||
c15.757,0,25.471-7.973,25.471-21.384C175.964,421.506,167.601,414.313,152.837,414.313z"/>
|
||||
<path d="M475.095,131.992c-0.032-2.526-0.833-5.021-2.568-6.993L366.324,3.694c-0.021-0.034-0.062-0.045-0.084-0.076
|
||||
c-0.633-0.707-1.36-1.29-2.141-1.804c-0.232-0.15-0.475-0.285-0.718-0.422c-0.675-0.366-1.382-0.67-2.13-0.892
|
||||
c-0.19-0.058-0.38-0.14-0.58-0.192C359.87,0.114,359.037,0,358.203,0H97.2C85.292,0,75.6,9.693,75.6,21.601v507.6
|
||||
c0,11.913,9.692,21.601,21.6,21.601H453.6c11.908,0,21.601-9.688,21.601-21.601V133.202
|
||||
C475.2,132.796,475.137,132.398,475.095,131.992z M193.261,463.873c-10.104,9.523-25.072,13.806-42.569,13.806
|
||||
c-3.882,0-7.391-0.2-10.102-0.58v46.839h-29.35V394.675c9.131-1.55,21.967-2.721,40.047-2.721
|
||||
c18.267,0,31.292,3.501,40.036,10.494c8.363,6.612,13.985,17.497,13.985,30.322C205.308,445.605,201.042,456.49,193.261,463.873z
|
||||
M318.252,508.392c-13.785,11.464-34.778,16.906-60.428,16.906c-15.359,0-26.238-0.97-33.637-1.94V394.675
|
||||
c10.887-1.74,25.083-2.721,40.046-2.721c24.867,0,41.004,4.472,53.645,13.995c13.61,10.109,22.164,26.241,22.164,49.37
|
||||
C340.031,480.4,330.897,497.697,318.252,508.392z M439.572,417.225h-50.351v29.932h47.039v24.11h-47.039v52.671H359.49V392.935
|
||||
h80.082V417.225z M97.2,366.752V21.601h250.203v110.515c0,5.961,4.831,10.8,10.8,10.8H453.6l0.011,223.836H97.2z"/>
|
||||
<path d="M386.205,232.135c-0.633-0.059-15.852-1.448-39.213-1.448c-7.319,0-14.691,0.143-21.969,0.417
|
||||
c-46.133-34.62-83.919-69.267-104.148-88.684c0.369-2.138,0.623-3.828,0.741-5.126c2.668-28.165-0.298-47.179-8.786-56.515
|
||||
c-5.558-6.101-13.721-8.131-22.233-5.806c-5.286,1.385-15.071,6.513-18.204,16.952c-3.459,11.536,2.101,25.537,16.708,41.773
|
||||
c0.232,0.246,5.189,5.44,14.196,14.241c-5.854,27.913-21.178,88.148-28.613,117.073c-17.463,9.331-32.013,20.571-43.277,33.465
|
||||
l-0.738,0.844l-0.477,1.013c-1.16,2.437-6.705,15.087-2.542,25.249c1.901,4.62,5.463,7.995,10.302,9.767l1.297,0.349
|
||||
c0,0,1.17,0.253,3.227,0.253c9.01,0,31.25-4.735,43.179-48.695l2.89-11.138c41.639-20.239,93.688-26.768,131.415-28.587
|
||||
c19.406,14.391,38.717,27.611,57.428,39.318l0.611,0.354c0.907,0.464,9.112,4.515,18.721,4.524l0,0
|
||||
c13.732,0,23.762-8.427,27.496-23.113l0.189-1.004c1.044-8.393-1.065-15.958-6.096-21.872
|
||||
C407.711,233.281,387.978,232.195,386.205,232.135z M142.812,319.744c-0.084-0.1-0.124-0.194-0.166-0.3
|
||||
c-0.896-2.157,0.179-7.389,1.761-11.222c6.792-7.594,14.945-14.565,24.353-20.841
|
||||
C159.598,317.039,146.274,319.603,142.812,319.744z M200.984,122.695L200.984,122.695c-14.07-15.662-13.859-23.427-13.102-26.041
|
||||
c1.242-4.369,6.848-6.02,6.896-6.035c2.824-0.768,4.538-0.617,6.064,1.058c3.451,3.791,6.415,15.232,5.244,36.218
|
||||
C202.764,124.557,200.984,122.695,200.984,122.695z M193.714,256.068l0.243-0.928l-0.032,0.011
|
||||
c7.045-27.593,17.205-67.996,23.047-93.949l0.211,0.201l0.021-0.124c18.9,17.798,47.88,43.831,82.579,70.907l-0.39,0.016
|
||||
l0.574,0.433C267.279,235.396,228.237,241.84,193.714,256.068z M408.386,265.12c-2.489,9.146-7.277,10.396-11.665,10.396l0,0
|
||||
c-5.094,0-9.998-2.12-11.116-2.632c-12.741-7.986-25.776-16.688-38.929-25.998c0.105,0,0.2,0,0.316,0
|
||||
c22.549,0,37.568,1.369,38.158,1.411c3.766,0.14,15.684,1.9,20.82,7.938C407.984,258.602,408.755,261.431,408.386,265.12z"/>
|
||||
</g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
</svg>
|
||||
|
After Width: | Height: | Size: 4.1 KiB |
59
_static/icons/txt_missing.svg
Normal file
59
_static/icons/txt_missing.svg
Normal file
@ -0,0 +1,59 @@
|
||||
<?xml version="1.0" encoding="iso-8859-1"?>
|
||||
<!-- Generator: Adobe Illustrator 16.0.0, SVG Export Plug-In . SVG Version: 6.00 Build 0) -->
|
||||
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
|
||||
<svg version="1.1" id="Capa_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
|
||||
width="32px" height="32px" fill="#ccc" viewBox="0 0 550.801 550.801" style="enable-background:new 0 0 550.801 550.801;"
|
||||
xml:space="preserve">
|
||||
<g>
|
||||
<g>
|
||||
<path d="M475.095,131.992c-0.032-2.526-0.844-5.021-2.579-6.993L366.324,3.694c-0.031-0.034-0.062-0.045-0.084-0.076
|
||||
c-0.633-0.707-1.371-1.29-2.151-1.804c-0.232-0.15-0.464-0.285-0.707-0.422c-0.675-0.366-1.382-0.67-2.13-0.892
|
||||
c-0.201-0.058-0.38-0.14-0.58-0.192C359.87,0.114,359.037,0,358.193,0H97.2C85.292,0,75.6,9.693,75.6,21.601v507.6
|
||||
c0,11.913,9.692,21.601,21.6,21.601H453.6c11.908,0,21.601-9.688,21.601-21.601V133.202
|
||||
C475.2,132.796,475.137,132.398,475.095,131.992z M210.558,418.605h-35.764v106.128h-29.734V418.605h-35.184v-24.874h100.683
|
||||
V418.605z M298.814,524.733l-11.855-23.714c-4.856-9.134-7.973-15.937-11.662-23.52h-0.388
|
||||
c-2.724,7.583-6.022,14.386-10.104,23.52l-10.887,23.714h-33.827L258,458.452l-36.547-64.727h34.016l11.476,23.91
|
||||
c3.881,7.963,6.803,14.381,9.911,21.769h0.391c3.101-8.358,5.632-14.19,8.933-21.769l11.085-23.91h33.824l-36.936,63.946
|
||||
l38.876,67.062H298.814z M440.923,418.605h-35.765v106.128h-29.742V418.605h-35.189v-24.874h100.686v24.874H440.923z
|
||||
M97.2,366.752V21.601h250.192v110.515c0,5.961,4.842,10.8,10.801,10.8H453.6v223.836H97.2z"/>
|
||||
<path d="M174.351,148.269h119.812c3.966,0,7.203-3.225,7.203-7.198s-3.237-7.193-7.203-7.193H174.351
|
||||
c-3.977,0-7.193,3.22-7.193,7.193S170.374,148.269,174.351,148.269z"/>
|
||||
<path d="M370.797,191.432H174.161c-3.974,0-7.193,3.217-7.193,7.192c0,3.974,3.219,7.198,7.193,7.198h196.636
|
||||
c3.976,0,7.203-3.225,7.203-7.198C378,194.648,374.772,191.432,370.797,191.432z"/>
|
||||
<path d="M370.797,248.58H174.161c-3.974,0-7.193,3.217-7.193,7.198c0,3.974,3.219,7.198,7.193,7.198h196.636
|
||||
c3.976,0,7.203-3.225,7.203-7.198C378,251.796,374.772,248.58,370.797,248.58z"/>
|
||||
<path d="M370.797,307.099H174.161c-3.974,0-7.193,3.223-7.193,7.198c0,3.977,3.219,7.193,7.193,7.193h196.636
|
||||
c3.976,0,7.203-3.217,7.203-7.193C378,310.321,374.772,307.099,370.797,307.099z"/>
|
||||
</g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
<g>
|
||||
</g>
|
||||
</svg>
|
||||
|
After Width: | Height: | Size: 2.4 KiB |
@ -82,7 +82,7 @@
|
||||
\renewcommand{\footrulewidth}{0.1pt}
|
||||
|
||||
\renewcommand{\maketitle}{%
|
||||
\noindent\rule{\textwidth}{1pt}\par
|
||||
\vspace*{-2.5cm}
|
||||
\begin{flushright}
|
||||
\sphinxlogo
|
||||
\py@HeaderFamily
|
||||
@ -95,6 +95,21 @@
|
||||
}
|
||||
|
||||
|
||||
% For sphinx 1.8.3+, the command is \sphinxmaketitle and the
|
||||
% layout is slightly different on the titlepage
|
||||
\providecommand\sphinxmaketitle{}
|
||||
\renewcommand{\sphinxmaketitle}{%
|
||||
\vspace*{-2.5cm}
|
||||
\begin{flushright}
|
||||
\sphinxlogo
|
||||
\py@HeaderFamily
|
||||
{\hspace{-0.5cm} \huge \@title }\par
|
||||
\end{flushright}
|
||||
\@thanks
|
||||
\setcounter{footnote}{0}
|
||||
\let\thanks\relax\let\maketitle\relax
|
||||
}
|
||||
|
||||
\newcommand{\makeodootitleold}{%
|
||||
\begin{titlepage}
|
||||
\titlepagedecoration
|
||||
|
||||
18
_static/legal.css
Normal file
18
_static/legal.css
Normal file
@ -0,0 +1,18 @@
|
||||
|
||||
section#terms-and-conditions table td {
|
||||
/* make sure icons and links aren't wrapped */
|
||||
white-space: nowrap;
|
||||
}
|
||||
|
||||
section#terms-and-conditions table th {
|
||||
text-align: center;
|
||||
}
|
||||
|
||||
section#terms-and-conditions table img.img-responsive {
|
||||
margin: 0px;
|
||||
}
|
||||
|
||||
section#terms-and-conditions table td:nth-child(2),
|
||||
section#terms-and-conditions table th:nth-child(2) {
|
||||
background-color: #f3f3f3;
|
||||
}
|
||||
@ -10,6 +10,7 @@ Localizations
|
||||
localizations/colombia_ES
|
||||
localizations/france
|
||||
localizations/germany
|
||||
localizations/indonesia
|
||||
localizations/italy_IT
|
||||
localizations/mexico
|
||||
localizations/netherlands
|
||||
|
||||
@ -85,7 +85,7 @@ Contacto (Tercero)
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
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
|
||||
@ -102,7 +102,7 @@ terceros.
|
||||
|
||||
|
||||
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
|
||||
@ -291,3 +291,305 @@ 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.
|
||||
|
||||
Consideraciones del Anexo 1.7
|
||||
=============================
|
||||
|
||||
Contexto
|
||||
--------
|
||||
|
||||
Contexto Normativo
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
| Soporte Normativo:
|
||||
| Resolución DIAN Número 000042 ( 5 de Mayo de 2020) Por la cual se desarrollan:
|
||||
|
||||
- Los sistemas de facturación,
|
||||
- Los proveedores tecnológicos,
|
||||
- El registro de la factura electrónica de venta como título valor,
|
||||
- Se expide el anexo técnico de factura electrónica de venta y
|
||||
- Se dictan otras disposiciones en materia de sistemas de facturación.
|
||||
|
||||
Anexo 1.7: Principales Cambios
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
- Cambios en la definición de Consumidor Final.
|
||||
- Informar bienes cubiertos para los 3 dias sin IVA.
|
||||
- Actualización de descripción de Impuestos.
|
||||
- Se agrega concepto para IVA Excluido.
|
||||
- Informar la fecha efectiva de entrega de los bienes.
|
||||
- Adecuaciones en la representación Gráfica (PDF).
|
||||
|
||||
Calendario
|
||||
~~~~~~~~~~
|
||||
|
||||
Se tiene varias fechas límites para la salida a producción bajo las condiciones del Anexo 1.7 las
|
||||
cuales dependen de los siguientes factores:
|
||||
|
||||
#. Calendario de implementación de acuerdo con la actividad económica principal en el RUT:
|
||||
|
||||
.. image:: media/colombia-es-calendario-rut.png
|
||||
:align: center
|
||||
|
||||
#. Calendario de implementación, para otros sujetos obligados:
|
||||
|
||||
.. image:: media/colombia-es-calendario-otros-obligados.png
|
||||
:align: center
|
||||
|
||||
#. Calendario de implementación permanente:
|
||||
|
||||
.. image:: media/colombia-es-calendario-permanente.png
|
||||
:align: center
|
||||
|
||||
Requerimientos en Odoo
|
||||
----------------------
|
||||
|
||||
Con la finalidad de facilitar el proceso de preparación de las bases de Odoo estándar V12 y v13,
|
||||
únicamente será necesario que los administradores actualicen algunos módulos y creen los datos
|
||||
maestros relacionados a los nuevos procesos.
|
||||
|
||||
Actualización de listado de Apps
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Utilizando el modo desarrollador, acceder al módulo de Aplicaciones y seleccionar el menú
|
||||
*Actualizar Lista*.
|
||||
|
||||
.. image:: media/colombia-es-actualizar-lista.png
|
||||
:align: center
|
||||
|
||||
Actualización de Módulos
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Una vez actualizado Buscar *Colombia*, los siguientes módulos serán desplegados, se requieren
|
||||
actualizar dos módulos.
|
||||
|
||||
#. Colombia - Contabilidad - l10n_co
|
||||
#. Electronic invoicing for Colombia with Carvajal UBL 2.1 - l10n_co_edi_ubl_2_1
|
||||
|
||||
.. image:: media/colombia-es-modulos.png
|
||||
:align: center
|
||||
|
||||
En cada módulo o ícono hay que desplegar el menú opciones utilizando los 3 puntos de la esquina
|
||||
superior derecha y seleccionamos *Actualizar*.
|
||||
|
||||
Primero lo hacemos con en el módulo l10n_co:
|
||||
|
||||
.. image:: media/colombia-es-actualizar-contabilidad.png
|
||||
:align: center
|
||||
|
||||
Posteriormente lo hacemos con el módulo l10n_co_edi_ubl_2_1:
|
||||
|
||||
.. image:: media/colombia-es-actualizar-electronic-invoicing.png
|
||||
:align: center
|
||||
|
||||
Creación de Datos Maestros
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Las bases de datos existentes a Junio 2020 tanto en V12 como V13, deberán crear algunos datos
|
||||
maestros necesarios para operar correctamente con los cambios del Anexo 1.7.
|
||||
|
||||
Consumidor Final
|
||||
****************
|
||||
|
||||
La figura del consumidor final será utilizada para aquellas ventas sobre las cuales no es posible
|
||||
identificar toda la información fiscal y demográfica del cliente por lo que la factura se genera a
|
||||
nombre de este registro genérico.
|
||||
|
||||
Es importante coordinar y definir los casos de uso en los que dependiendo de su empresa se tendrá
|
||||
permitido utilizar este registro genérico.
|
||||
|
||||
Dentro de Odoo se tendrá que crear un contacto con las siguientes características, es importante que
|
||||
se defina de esta manera debido a que son los parámetros definidos por la DIAN.
|
||||
|
||||
- **Tipo de contacto:** Individuo
|
||||
- **Nombre:** Consumidor Final
|
||||
- **Tipo de documento:** Cedula de Ciudadania
|
||||
- **Numero de Identificacion:** 222222222222
|
||||
|
||||
.. image:: media/colombia-es-consumidor-final-nuevo-contacto.png
|
||||
:align: center
|
||||
|
||||
Dentro de la pestaña Ventas y Compras, en la sección Información Fiscal, del campo Obligaciones y
|
||||
Responsabilidades colocaremos el valor: **R-99-PN**.
|
||||
|
||||
.. image:: media/colombia-es-consumidor-final-r-99-pn.png
|
||||
:align: center
|
||||
|
||||
IVA Excluido - Bienes Cubiertos
|
||||
*******************************
|
||||
|
||||
Para reportar las transacciones realizadas mediante Bienes Cubiertos para los tres días sin IVA,
|
||||
será necesario crear un nuevo Impuesto al cual se le debe de asociar un grupo de impuestos
|
||||
específico que será utilizado por Odoo para agregar la sección requerida en el XML de factura
|
||||
electrónica.
|
||||
|
||||
Para el crear el impuesto accederemos a Contabilidad dentro del menú :menuselection:`Configuración
|
||||
--> Impuestos`:
|
||||
|
||||
.. image:: media/colombia-es-menu-impuestos.png
|
||||
:align: center
|
||||
|
||||
Procedemos a crear un nuevo Impuesto con importe 0% considerando los siguientes parámetros:
|
||||
|
||||
.. image:: media/colombia-es-nuevo-impuesto.png
|
||||
:align: center
|
||||
|
||||
El nombre del Impuesto puede ser definido a preferencia del usuario, sin embargo el campo clave es
|
||||
**Grupo de Impuestos** dentro de Opciones avanzadas, el cual debe ser: *bienes cubiertos* y el campo
|
||||
**Tipo de Valor**: *IVA*.
|
||||
|
||||
.. image:: media/colombia-es-nuevo-impuesto-opciones-avanzadas.png
|
||||
:align: center
|
||||
|
||||
Actualización de descripción de Departamentos
|
||||
*********************************************
|
||||
|
||||
Es necesario actualizar la descripción de algunos departamentos, para lo cual accederemos a módulo
|
||||
de Contactos y dentro del menú de :menuselection:`Configuración --> Provincias`.
|
||||
|
||||
.. image:: media/colombia-es-menu-provincias.png
|
||||
:align: center
|
||||
|
||||
Posteriormente, podemos agregar por País para identificar claramente las provincias (Departamentos)
|
||||
de Colombia:
|
||||
|
||||
.. image:: media/colombia-es-provincias-agrupar.png
|
||||
:align: center
|
||||
|
||||
Una vez agrupados buscar los siguientes departamentos para actualizarlos con el valor indicado en la
|
||||
columna **Nombre actualizado**:
|
||||
|
||||
+------------------------------+---------------------+--------------------------+
|
||||
| Nombre de provincia | Código de Provincia | Nombre actualizado |
|
||||
+==============================+=====================+==========================+
|
||||
| D.C. | DC | Bogotá |
|
||||
+------------------------------+---------------------+--------------------------+
|
||||
| Quindio | QUI | Quindío |
|
||||
+------------------------------+---------------------+--------------------------+
|
||||
| Archipiélago de San Andrés, | SAP | San Andrés y Providencia |
|
||||
| Providencia y Santa Catalina | | |
|
||||
+------------------------------+---------------------+--------------------------+
|
||||
|
||||
Ejemplo:
|
||||
|
||||
.. image:: media/colombia-es-provincias-ejemplo.png
|
||||
:align: center
|
||||
|
||||
Verificación de Código postal
|
||||
*****************************
|
||||
|
||||
Dentro del Anexo 1.7 se comienza a validar que el código postal de las direcciones para contactos
|
||||
colombianos corresponda a las tablas oficiales definidas por la DIAN, por lo que se debe verificar
|
||||
que este campo está debidamente diligenciado de acuerdo a los definidos en la sigueinte fuente:
|
||||
`Codigos_Postales_Nacionales.csv
|
||||
<http://visor.codigopostal.gov.co/472/visor/Codigos_Postales_Nacionales.csv>`_
|
||||
|
||||
Consideraciones Operativas
|
||||
--------------------------
|
||||
|
||||
Consumidor Final
|
||||
~~~~~~~~~~~~~~~~
|
||||
|
||||
Una vez que resgistro de Consumidor final ha sido creado este deberá ser utilizado a demanda,
|
||||
generalmente será utilizado en las transacciones de facturación del punto de punto de venta.
|
||||
|
||||
- El proceso de validación de la Factura será realizado de forma convencional en Odoo y la factura
|
||||
será generada de la misma manera. Al detectar que el número de identificación corresponde a
|
||||
consumidor Final, el XML que se envía a Carvajal será generado con las consideraciones y secciones
|
||||
correspondientes.
|
||||
- Contablemente todos los registros de Consumidor final quedarán asociados al identificador generico:
|
||||
|
||||
.. image:: media/colombia-es-consumidor-final-asociado.png
|
||||
:align: center
|
||||
|
||||
IVA Excluido - Bienes Cubiertos
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
El 21 mayo del 2020 fue publicado el El Decreto 682 el cual establece Excepción especial en el
|
||||
Impuesto sobre las ventas. El principal objetivo de este decreto es reactivar la economía en
|
||||
Colombia por las bajas ventas generadas a causa del COVID.
|
||||
|
||||
Fechas
|
||||
******
|
||||
|
||||
Días de excención del impuesto sobre las ventas – IVA para bienes cubiertos (3 días SIN IVA).
|
||||
|
||||
- **Primer día**: 19 de junio de 2020
|
||||
- **Segundo día**: 3 de Julio de 2020
|
||||
- **Tercer día**: 19 de Julio de 2020
|
||||
|
||||
Condiciones
|
||||
***********
|
||||
|
||||
Debido a que estas transacciones serán generadas de forma excepcional y que se tiene una combinación
|
||||
de varios factores y condiciones, los productores debera ser actualizados de forma manual en Odoo
|
||||
asignados temporalmente el impuesto de venta *IVA exento - Bienes cubierto* en cada empresa según
|
||||
corresponda.
|
||||
|
||||
A continuación se mencionan algunas de las principales condiciones, sin embargo, cabe mencionar que
|
||||
las empresas deben de verificar todos los detalles en el `Decreto 682
|
||||
<https://dapre.presidencia.gov.co/normativa/normativa/DECRETO%20682%20DEL%2021%20DE%20MAYO%20DE%202020.pdf>`_.
|
||||
|
||||
- Tipo de productos y precio Máximo:
|
||||
|
||||
+-----------------------------+---------------------------------------+
|
||||
| Tipo de Productos | Precio Máximo |
|
||||
+=============================+=======================================+
|
||||
| Electrodomesticos | 40 UVT: $1,4 millones. |
|
||||
+-----------------------------+---------------------------------------+
|
||||
| Vestuario y complementos | | 3 UVT: $106.000 |
|
||||
| | | En el caso de los complementos es: |
|
||||
| | | 10 UVT- $356.000 |
|
||||
+-----------------------------+---------------------------------------+
|
||||
| Elementos deportivos | 10 UVT- $356.000 |
|
||||
+-----------------------------+---------------------------------------+
|
||||
| Juguetes y Utiles Escolares | 5 UVT - $178.035 |
|
||||
+-----------------------------+---------------------------------------+
|
||||
| Utiles Escolares | 5 UVT - $178.035 |
|
||||
+-----------------------------+---------------------------------------+
|
||||
| Bienes o servicios para | 80 UVT - $2.848.560 |
|
||||
| el sector agropecuario | |
|
||||
+-----------------------------+---------------------------------------+
|
||||
|
||||
- Métodos de Pago:
|
||||
|
||||
- El pago debe realizarse por medios electrónico por ejemplo tarjetas de crédito/débito o bien mecanismos de pago online.
|
||||
|
||||
- Limite de unidades:
|
||||
|
||||
- Cada cliente puede adquirir únicamente 3 unidades como máximo de cada producto.
|
||||
|
||||
Medidas en Odoo
|
||||
***************
|
||||
|
||||
- **Preparación de datos**
|
||||
|
||||
- Crear el Impuesto para Bienes cubiertos de acuerdo a lo indicado en este punto: Datos maestros.
|
||||
- Identificar los productos y transacciones a los cuales les aplicará la Exclusión de IVA de
|
||||
acuerdo a las condiciones establecidas en el decreto 682. En caso de ser un porcentaje
|
||||
significativo de productos, se recomienda actualizar el impuesto de forma temporal en Odoo.
|
||||
- Exportar un listado con los productos que serán afectados incluyendo el campo IVA Venta el cual
|
||||
será sustituido temporalmente por el IVA de Bienes Cubiertos.
|
||||
- Al finalizar las operaciones del día anterior a las fechas establecidas de día sin IVA, se debe
|
||||
hacer la actualización temporal a IVA de Bienes Cubiertos.
|
||||
|
||||
.. image:: media/columbia-es-producto-iva-bienes-cubiertos.png
|
||||
:align: center
|
||||
|
||||
- **Durante el día SIN IVA**
|
||||
|
||||
- Por defecto los productos previamente considerados con IVA de Bienes cubiertos serán generados
|
||||
con este parámetro tanto en Órdenes de venta como facturas creadas durante ese mismo día.
|
||||
|
||||
.. image:: media/columbia-es-factura-iva-bienes-cubiertos.png
|
||||
:align: center
|
||||
|
||||
- Las órdenes de venta generadas con este impuesto deberán ser facturas el mismo día.
|
||||
- En caso de que alguna de las condiciones no sea cumplida (ejemplo el pago es realizado en
|
||||
efectivo) el impuesto deberá ser actualizado manualmente al momento de facturar.
|
||||
|
||||
- **Posterior al día SIN IVA**
|
||||
|
||||
- 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.
|
||||
128
accounting/fiscal_localizations/localizations/indonesia.rst
Normal file
128
accounting/fiscal_localizations/localizations/indonesia.rst
Normal file
@ -0,0 +1,128 @@
|
||||
=========
|
||||
Indonesia
|
||||
=========
|
||||
|
||||
.. _localization_indonesia/e-faktur:
|
||||
|
||||
E-Faktur Module
|
||||
===============
|
||||
|
||||
The **E-Faktur Module** is installed by default with the Indonesian localization module. It allows
|
||||
one to generate a CSV file for one tax invoice or for a batch of tax invoices to upload to the
|
||||
**Tax Office e-Faktur** application.
|
||||
|
||||
.. _localization_indonesia/npwp_nik:
|
||||
|
||||
NPWP/NIK settings
|
||||
-----------------
|
||||
|
||||
- | **Your Company**
|
||||
| This information is used in the FAPR line in the effect file format. You need to set a VAT
|
||||
number on the related partner of your Odoo company. If you don't, it won't be possible to create
|
||||
an e-Faktur from an invoice.
|
||||
- | **Your Clients**
|
||||
| You need to set the checkbox *ID PKP* to generate e-fakturs for a customer. You can use the VAT
|
||||
field on the customer's contact to set the NPWP needed to generate the e-Faktur file. If your
|
||||
customer does not have an NPWP, just enter the NIK in the same VAT field.
|
||||
|
||||
.. image:: media/indonesia-partner-nik.png
|
||||
:align: center
|
||||
|
||||
.. _localization_indonesia/e-faktur_usage:
|
||||
|
||||
Usage
|
||||
-----
|
||||
|
||||
.. _localization_indonesia/tax_invoice_sn:
|
||||
|
||||
Generate Tax Invoice Serial Number
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
#. Go to :menuselection:`Accounting --> Customers --> e-Faktur`. In order to be able to export
|
||||
customer invoices as e-Faktur for the Indonesian government, you need to put here the ranges of
|
||||
numbers you were assigned by the government. When you validate an invoice, a number will be
|
||||
assigned based on these ranges. Afterwards, you can filter the invoices still to export in the
|
||||
invoices list and click on *Action*, then on *Download e-Faktur*.
|
||||
#. After receiving new serial numbers from the Indonesian Revenue Department, you can create a set
|
||||
of tax invoice serial numbers group through this list view. You only have to specify the Min and
|
||||
Max of each serial numbers' group and Odoo will format the number automatically to a 13-digits
|
||||
number, as requested by the Indonesia Tax Revenue Department.
|
||||
#. There is a counter to inform you how many unused numbers are left in that group.
|
||||
|
||||
.. image:: media/indonesia-sn-count.png
|
||||
:align: center
|
||||
|
||||
.. _localization_indonesia/csv:
|
||||
|
||||
Generate e-faktur csv for a single invoice or a batch invoices
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
#. Create an invoice from :menuselection:`Accounting --> Customers --> Invoices`. If the invoice
|
||||
customer's country is Indonesia and the customer is set as *ID PKP*, Odoo will allow you to
|
||||
create an e-Faktur.
|
||||
#. Set a Kode Transaksi for the e-Faktur. There are constraints related to the Kode transaksi and
|
||||
the type of VAT applied to invoice lines.
|
||||
|
||||
.. image:: media/indonesia-kode-transaksi.png
|
||||
:align: center
|
||||
|
||||
#. Odoo will automatically pick the next available serial number from the e-Faktur number table (see
|
||||
the :ref:`section above <localization_indonesia/tax_invoice_sn>`) and generate the e-faktur
|
||||
number as a concatenation of Kode Transaksi and serial number. You can see this from the invoice
|
||||
form view under the page *Extra Info* in the box *Electronic Tax*.
|
||||
|
||||
.. image:: media/indonesia-e-faktur-sn.png
|
||||
:align: center
|
||||
|
||||
#. Once the invoice is posted, you can generate and download the e-Faktur from the *Action* menu
|
||||
item *Download e-faktur*. The checkbox *CSV created* will be set.
|
||||
|
||||
.. image:: media/indonesia-csv-created.png
|
||||
:align: center
|
||||
|
||||
#. You can select multiple invoices in list view and generate a batch e-Faktur .csv.
|
||||
|
||||
.. _localization_indonesia/kode_transaksi_fp:
|
||||
|
||||
Kode Transaksi FP (Transaction Code)
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
The following codes are available when generating an e-Faktur.
|
||||
- 01 Kepada Pihak yang Bukan Pemungut PPN (Customer Biasa)
|
||||
- 02 Kepada Pemungut Bendaharawan (Dinas Kepemerintahan)
|
||||
- 03 Kepada Pemungut Selain Bendaharawan (BUMN)
|
||||
- 04 DPP Nilai Lain (PPN 1%)
|
||||
- 06 Penyerahan Lainnya (Turis Asing)
|
||||
- 07 Penyerahan yang PPN-nya Tidak Dipungut (Kawasan Ekonomi Khusus/ Batam)
|
||||
- 08 Penyerahan yang PPN-nya Dibebaskan (Impor Barang Tertentu)
|
||||
- 09 Penyerahan Aktiva (Pasal 16D UU PPN)
|
||||
|
||||
.. _localization_indonesia/replace_invoice:
|
||||
|
||||
Correct an invoice that has been posted and downloaded: Replace Invoice feature
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
#. Cancel the original wrong invoice in Odoo. For instance, we will change the Kode Transakski from 01
|
||||
to 03 for the INV/2020/0001.
|
||||
#. Create a new invoice and set the canceled invoice in the *Replace Invoice* field. In this field,
|
||||
we can only select invoices in *Cancel* state from the same customer.
|
||||
#. As you validate, Odoo will automatically use the same e-Faktur serial number as the canceled and
|
||||
replaced invoice replacing the third digit of the original serial number with *1* (as requested
|
||||
to upload a replacement invoice in the e-Faktur app).
|
||||
|
||||
.. image:: media/indonesia-replace-invoice.png
|
||||
:align: center
|
||||
|
||||
|
||||
.. _localization_indonesia/reset_e-faktur:
|
||||
|
||||
Correct an invoice that has been posted but not downloaded yet: Reset e-Faktur
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
#. Reset the invoice to draft and cancel it.
|
||||
#. Click on the button *Reset e-Faktur* on the invoice form view.
|
||||
#. The serial number will be unassigned, and we will be able to reset the invoice to draft, edit it
|
||||
and re-assign a new serial number.
|
||||
|
||||
.. image:: media/indonesia-e-faktur-reset.png
|
||||
:align: center
|
||||
@ -25,7 +25,7 @@ elettronica sono i seguenti:
|
||||
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 :doc:`guida <../../../discuss/email_servers>`.
|
||||
puo’ consultare la relativa :doc:`guida <../../../discuss/advanced/email_servers>`.
|
||||
|
||||
- Indirizzo PEC dell’ Azienda, tale indirizzo deve essere lo stesso
|
||||
registrato presso l’Agenzia delle Entrate per l’utilizzo dei servizi
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 31 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 25 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 75 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 25 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 43 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 70 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 67 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 43 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 59 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 71 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 112 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 53 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 60 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 52 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 8.8 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 95 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 94 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 23 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 9.5 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 23 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 27 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 25 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 7.3 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 9.8 KiB |
@ -28,12 +28,27 @@ Then you open a pdf with the ISR.
|
||||
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 :
|
||||
:menuselection:`Accounting --> Configuration --> Settings --> Customer Invoices`
|
||||
and enable **Print bank on ISR**:
|
||||
|
||||
.. image:: media/switzerland03.png
|
||||
:align: center
|
||||
|
||||
ISR reference on invoices
|
||||
-------------------------
|
||||
|
||||
To ease the reconciliation process, you can add your ISR reference as **Payment Reference** on your
|
||||
invoices.
|
||||
|
||||
To do so, you need to configure the Journal you usually use to issue invoices. Go to
|
||||
:menuselection:`Accounting --> Configuration --> Journals`, open the Journal you want to modify (By
|
||||
default, the Journal is named *Customer Invoices*), click en *Edit*, and open the *Advanced
|
||||
Settings* tab. In the **Communication Standard** field, select *Switzerland*, and click on *Save*.
|
||||
|
||||
.. image:: media/switzerland-isr-reference.png
|
||||
:align: center
|
||||
:alt: Configure your Journal to display your ISR as payment reference on your invoices in Odoo
|
||||
|
||||
Currency Rate Live Update
|
||||
=========================
|
||||
|
||||
|
||||
@ -7,9 +7,10 @@ Taxes
|
||||
|
||||
taxes/create
|
||||
taxes/default_taxes
|
||||
taxes/application
|
||||
taxes/fiscal_positions
|
||||
taxes/taxcloud
|
||||
taxes/tax_included
|
||||
taxes/retention
|
||||
taxes/B2B_B2C
|
||||
taxes/cash_basis_taxes
|
||||
taxes/cash_basis_taxes
|
||||
taxes/vat_validation
|
||||
@ -1,87 +0,0 @@
|
||||
=================================================
|
||||
Adapt taxes to my customer status or localization
|
||||
=================================================
|
||||
|
||||
Most often sales tax rates depend on your customer status or localization.
|
||||
To map taxes, Odoo brings the so-called *Fiscal Positions*.
|
||||
|
||||
Create tax mapping
|
||||
==================
|
||||
|
||||
A fiscal position is just a set of rules that maps default taxes (as defined
|
||||
on product form) into other taxes. In the screenshot below, foreign customers
|
||||
get a 0% tax instead of the default 15%, for both sales and purchases.
|
||||
|
||||
.. image:: media/application02.png
|
||||
:align: center
|
||||
|
||||
The main fiscal positions are automatically created according to your
|
||||
localization. But you may have to create fiscal positions for specific use cases.
|
||||
To define fiscal positions, go to
|
||||
:menuselection:`Invoicing/Accounting --> Configuration --> Fiscal Positions`.
|
||||
|
||||
.. note::
|
||||
If you use Odoo Accounting, you can also map the Income/Expense accounts according to the fiscal
|
||||
position. For example, in some countries, revenues from sales are not posted in
|
||||
the same account than revenues from sales in foreign countries.
|
||||
|
||||
Adapt taxes to your customer status
|
||||
===================================
|
||||
|
||||
If a customer falls into a specific taxation rule, you need to apply a tax-mapping.
|
||||
To do so, create a fiscal position and assign it to your customers.
|
||||
|
||||
.. image:: media/application01.png
|
||||
:align: center
|
||||
|
||||
Odoo will use this specific fiscal position for any order/invoice recorded for the customer.
|
||||
|
||||
.. note::
|
||||
If you set the fiscal position in the sales order or invoice manually, it will only
|
||||
apply to this document and not to future orders/invoices of the same customer.
|
||||
|
||||
Adapt taxes to your customer address (destination-based)
|
||||
========================================================
|
||||
|
||||
Depending on your localization, sales taxes may be origin-based or destination-based.
|
||||
Most states or countries require you to collect taxes at the rate of the destination
|
||||
(i.e. your buyer’s address) while some others require to collect them at the rate effective
|
||||
at the point of origin (i.e. your office or warehouse).
|
||||
|
||||
If you are under the destination-based rule, create one fiscal position per tax-mapping to apply.
|
||||
|
||||
* Check the box *Detect Automatically*.
|
||||
* Select a country group, country, state or city to trigger the tax-mapping.
|
||||
|
||||
.. image:: media/application04.png
|
||||
:align: center
|
||||
|
||||
This way if no fiscal position is set on the customer, Odoo will choose the fiscal position matching the
|
||||
shipping address on creating an order.
|
||||
|
||||
.. note::
|
||||
For eCommerce orders, the tax of the visitor's cart will automatically
|
||||
update and apply the new tax after the visitor has logged in or filled
|
||||
in his shipping address.
|
||||
|
||||
Specific use cases
|
||||
==================
|
||||
|
||||
If, for some fiscal positions, you want to remove a tax, instead of
|
||||
replacing by another, just keep the *Tax to Apply* field empty.
|
||||
|
||||
.. image:: media/application03.png
|
||||
:align: center
|
||||
|
||||
If, for some fiscal positions, you want to replace a tax by two other
|
||||
taxes, just create two lines having the same *Tax on Product*.
|
||||
|
||||
.. note::
|
||||
The fiscal positions are not applied on assets and deferred revenues.
|
||||
|
||||
.. seealso::
|
||||
|
||||
* :doc:`create`
|
||||
* :doc:`taxcloud`
|
||||
* :doc:`tax_included`
|
||||
* :doc:`B2B_B2C`
|
||||
@ -66,5 +66,5 @@ Advanced configuration
|
||||
|
||||
.. seealso::
|
||||
|
||||
* :doc:`application`
|
||||
* :doc:`fiscal_positions`
|
||||
* :doc:`tax_included`
|
||||
|
||||
@ -1,31 +1,40 @@
|
||||
=================
|
||||
Set default taxes
|
||||
=================
|
||||
=============
|
||||
Default Taxes
|
||||
=============
|
||||
|
||||
Taxes applied in your country are installed automatically for most localizations.
|
||||
**Default Taxes** define which :doc:`taxes <create>` are automatically selected when there is no
|
||||
other indication about which tax to use. For example, Odoo prefills the **Taxes** field with the
|
||||
Default Taxes when you create a new product or add a new line on an invoice.
|
||||
|
||||
Default taxes set in orders and invoices come from each product's Invoicing tab.
|
||||
Such taxes are used when you sell to companies that are in the same country/state than you.
|
||||
|
||||
.. image:: media/application05.png
|
||||
.. image:: media/default-taxes-invoice-line.png
|
||||
:align: center
|
||||
:alt: Odoo fills out the Tax field automatically according to the Default Taxes
|
||||
|
||||
To change the default taxes set for any new product created go to
|
||||
:menuselection:`Invoicing/Accounting --> Configuration --> Settings`.
|
||||
.. important::
|
||||
:doc:`Fiscal Positions <fiscal_positions>` take the Default Tax into account. Therefore, if a
|
||||
Fiscal Position is applied to an invoice, Odoo applies the related tax instead of the Default
|
||||
Taxes, as mapped in the Fiscal Position.
|
||||
|
||||
.. image:: media/create04.png
|
||||
Configuration
|
||||
=============
|
||||
|
||||
**Default Taxes** are automatically set up according to the country selected at the creation of your
|
||||
database, or when you set up a :doc:`Fiscal Localization Package
|
||||
<../../fiscal_localizations/overview/fiscal_localization_packages>` for your company.
|
||||
|
||||
To change your **Default Taxes**, go to :menuselection:`Accounting --> Configuration --> Settings
|
||||
--> Taxes --> Default Taxes`, select the appropriate taxes for your default **Sales Tax** and
|
||||
**Purchase Tax**, and click on *Save*.
|
||||
|
||||
.. image:: media/default-taxes-configuration.png
|
||||
:align: center
|
||||
:alt: Define which taxes to use by default on Odoo
|
||||
|
||||
.. tip::
|
||||
If you work in a multi-companies environment, the sales and
|
||||
purchase taxes may have a different value according to the
|
||||
company you work for. You can login into two different companies
|
||||
and change this field for each company.
|
||||
.. note::
|
||||
Databases with multiple companies: the Default Taxes values are company-specific.
|
||||
|
||||
.. seealso::
|
||||
|
||||
* :doc:`create`
|
||||
* :doc:`application`
|
||||
* :doc:`taxcloud`
|
||||
* :doc:`B2B_B2C`
|
||||
* :doc:`tax_included`
|
||||
- :doc:`create`
|
||||
- :doc:`fiscal_positions`
|
||||
- :doc:`../../fiscal_localizations/overview/fiscal_localization_packages`
|
||||
|
||||
111
accounting/fiscality/taxes/fiscal_positions.rst
Normal file
111
accounting/fiscality/taxes/fiscal_positions.rst
Normal file
@ -0,0 +1,111 @@
|
||||
==========================================
|
||||
Fiscal Positions (tax and account mapping)
|
||||
==========================================
|
||||
|
||||
Default taxes and accounts are set on products and customers to create new transactions on the fly.
|
||||
However, you might have to use different taxes and record the transactions on different accounts,
|
||||
according to your customers' and providers' localizations and business types.
|
||||
|
||||
**Fiscal Positions** allow you to create *sets of rules* to automatically adapt the taxes and the
|
||||
accounts used for a transaction.
|
||||
|
||||
.. image:: media/fiscal-positions-intra-community.png
|
||||
:align: center
|
||||
:alt: Example: Belgian to Intra-Community tax mapping with Fiscal Positions in Odoo Accounting
|
||||
|
||||
They can be applied in various ways:
|
||||
|
||||
- :ref:`automatically applied, based on some rules <fiscal_positions/automatic>`
|
||||
- :ref:`manually applied on a transaction <fiscal_positions/partner>`
|
||||
- :ref:`assigned to a partner, on its contact form <fiscal_positions/transaction>`
|
||||
|
||||
.. note::
|
||||
A few Fiscal Positions are already preconfigured on your database, as part of your :doc:`Fiscal
|
||||
Localization Package <../../fiscal_localizations/overview/fiscal_localization_packages>`.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Tax and Account Mapping
|
||||
-----------------------
|
||||
|
||||
To edit or create a Fiscal Position, go to :menuselection:`Accounting --> Configuration --> Fiscal
|
||||
Positions`, and open the entry you want to modify or click on *Create*.
|
||||
|
||||
The mapping of taxes and accounts is based on the default taxes and accounts defined in the
|
||||
products' forms.
|
||||
|
||||
- To map to another tax or account, fill out the right column (**Tax to Apply**/**Account to Use
|
||||
Instead**).
|
||||
- To remove a tax, rather than replacing it with another, leave the field **Tax to Apply** empty.
|
||||
- To replace a tax with multiple other taxes, add multiple lines with the same **Tax on Product**.
|
||||
|
||||
.. note::
|
||||
The mapping only works with *active* taxes. Therefore, make sure they are active by going to
|
||||
:menuselection:`Accounting --> Configuration --> Taxes`.
|
||||
|
||||
.. _fiscal_positions/automatic:
|
||||
|
||||
Automatic application
|
||||
---------------------
|
||||
|
||||
You can configure your Fiscal Positions to be applied automatically, following a set of conditions.
|
||||
|
||||
To do so, open the Fiscal Position you want to modify and click on **Detect Automatically**. You can
|
||||
configure a few conditions:
|
||||
|
||||
- **VAT Required**: The VAT number *must* be indicated in the customer's contact form.
|
||||
- **Country Group** / **Country**: The Fiscal Position is applied to these countries.
|
||||
|
||||
.. image:: media/fiscal-positions-automatic.png
|
||||
:align: center
|
||||
:alt: Example of settings to apply a Fiscal Position automatically
|
||||
|
||||
.. note::
|
||||
Taxes on **eCommerce orders** are automatically updated once the visitor has logged in or filled
|
||||
out their billing details.
|
||||
|
||||
.. important::
|
||||
The Fiscal Positions' **sequence** - the order in which they are arranged - defines which
|
||||
Fiscal Position to apply if the conditions are met in multiple Fiscal Positions.
|
||||
|
||||
For example, if the first Fiscal Position targets *country A*, and the second Fiscal Position
|
||||
targets a *Country Group* that also comprises *country A*, only the first Fiscal Position will be
|
||||
applied to customers from *country A*.
|
||||
|
||||
.. _fiscal_positions/application:
|
||||
|
||||
Application
|
||||
===========
|
||||
|
||||
.. _fiscal_positions/partner:
|
||||
|
||||
Assign a Fiscal Position to a partner
|
||||
--------------------------------------
|
||||
|
||||
You can manually define which Fiscal Position must be used by default for a specific partner.
|
||||
|
||||
To do so, open the partner's contact form, go to the **Sales & Purchase** tab, edit the **Fiscal
|
||||
Position** field, and click on *Save*.
|
||||
|
||||
.. image:: media/fiscal-positions-partner.png
|
||||
:align: center
|
||||
:alt: Selection of a Fiscal Position on a Sales Order / Invoice / Bill in Odoo Accounting
|
||||
|
||||
.. _fiscal_positions/transaction:
|
||||
|
||||
Choose Fiscal Positions manually on Sales Orders, Invoices, and Bills
|
||||
---------------------------------------------------------------------
|
||||
|
||||
To manually select which Fiscal Position to use for a new Sales Order, Invoice, or Bill, go to the
|
||||
**Other Info** tab and select the right **Fiscal Position** *before* adding product lines.
|
||||
|
||||
.. image:: media/fiscal-positions-transaction.png
|
||||
:align: center
|
||||
:alt: Selection of a Fiscal Position on a Sales Order / Invoice / Bill in Odoo Accounting
|
||||
|
||||
.. seealso::
|
||||
|
||||
* :doc:`create`
|
||||
* :doc:`taxcloud`
|
||||
* :doc:`B2B_B2C`
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 25 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 15 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 5.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.9 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.7 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 8.2 KiB |
BIN
accounting/fiscality/taxes/media/default-taxes-configuration.png
Normal file
BIN
accounting/fiscality/taxes/media/default-taxes-configuration.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 4.5 KiB |
BIN
accounting/fiscality/taxes/media/default-taxes-invoice-line.png
Normal file
BIN
accounting/fiscality/taxes/media/default-taxes-invoice-line.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 6.0 KiB |
BIN
accounting/fiscality/taxes/media/fiscal-positions-automatic.png
Normal file
BIN
accounting/fiscality/taxes/media/fiscal-positions-automatic.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 3.0 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
BIN
accounting/fiscality/taxes/media/fiscal-positions-partner.png
Normal file
BIN
accounting/fiscality/taxes/media/fiscal-positions-partner.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 7.8 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 7.2 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 3.2 KiB |
BIN
accounting/fiscality/taxes/media/vat-validation-contact-form.png
Normal file
BIN
accounting/fiscality/taxes/media/vat-validation-contact-form.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 6.8 KiB |
BIN
accounting/fiscality/taxes/media/vat-validation-error.png
Normal file
BIN
accounting/fiscality/taxes/media/vat-validation-error.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 5.4 KiB |
@ -47,7 +47,7 @@ How it works
|
||||
============
|
||||
|
||||
Salestax is calculated in Odoo based on fiscal positions
|
||||
(see :doc:`application`).
|
||||
(see :doc:`fiscal_positions`).
|
||||
A Fiscal Position for the United States is created when installing *TaxCloud*.
|
||||
Everything works out-of-the-box.
|
||||
|
||||
@ -90,4 +90,4 @@ price is the equivalent of a 7% tax on half the price), but this might be surpri
|
||||
point of view.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`application`
|
||||
- :doc:`fiscal_positions`
|
||||
|
||||
43
accounting/fiscality/taxes/vat_validation.rst
Normal file
43
accounting/fiscality/taxes/vat_validation.rst
Normal file
@ -0,0 +1,43 @@
|
||||
===========================
|
||||
VIES VAT numbers validation
|
||||
===========================
|
||||
|
||||
**VAT Information Exchange System** - abbreviated **VIES** - is a tool provided by the European
|
||||
Commission that allows you to check the validity of VAT numbers of companies registered in the
|
||||
European Union.
|
||||
|
||||
Odoo provides a feature to **Verify VAT Numbers** when you save a contact. This helps you make sure
|
||||
that your contacts provided you with a valid VAT number without leaving Odoo interface.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
To enable this feature, go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes`,
|
||||
enable the **Verify VAT Numbers** feature, and click on *Save*.
|
||||
|
||||
.. image:: media/vat-validation-configuration.png
|
||||
:align: center
|
||||
:alt: Enable "Verify VAT Numbers" in Odoo Accounting
|
||||
|
||||
VAT Number validation
|
||||
=====================
|
||||
|
||||
Whenever you create or modify a contact, make sure to fill out the **Country** and **VAT** fields.
|
||||
|
||||
.. image:: media/vat-validation-contact-form.png
|
||||
:align: center
|
||||
:alt: Fill out the contact form with the country and VAT number before clicking on *Save*
|
||||
|
||||
When you click on *Save*, Odoo runs a VIES VAT number check, and displays an error message if the
|
||||
VAT number is invalid.
|
||||
|
||||
.. image:: media/vat-validation-error.png
|
||||
:align: center
|
||||
:alt: Odoo displays an error message instead of saving when the VAT number is invalid
|
||||
|
||||
.. important::
|
||||
This tool checks the VAT number's validity but does not check the other fields' validity.
|
||||
|
||||
.. seealso::
|
||||
|
||||
- `European Commission: VIES search engine <https://ec.europa.eu/taxation_customs/vies/vatRequest.html>`__
|
||||
@ -6,7 +6,7 @@ Customer Payments
|
||||
:titlesonly:
|
||||
|
||||
customer_payments/recording
|
||||
customer_payments/credit_cards
|
||||
customer_payments/online_payment
|
||||
customer_payments/check
|
||||
customer_payments/batch_sdd
|
||||
customer_payments/followup
|
||||
|
||||
@ -1,167 +0,0 @@
|
||||
=========================================
|
||||
Register credit card payments on invoices
|
||||
=========================================
|
||||
|
||||
There are two ways to handle payments received by credit cards. Odoo
|
||||
support both approaches so that you can use the one that better fits
|
||||
your habits.
|
||||
|
||||
1. **Undeposited Funds** (mostly used in european countries): once you
|
||||
receive the credit card payment authorization, you record a
|
||||
payment by credit card on the invoice (using a Credit card
|
||||
journal and posted on the Undeposited Fund account). Then, once
|
||||
the credit card payments arrives in your bank account, move money
|
||||
from Undeposited Funds to your bank account.
|
||||
|
||||
2. **One journal entry only** (mostly used in the U.S.): once your
|
||||
receive the credit card payment, you record a payment on your
|
||||
bank, paid by credit card, without going through the Undeposited
|
||||
Funds. Once you process your bank statement, you do the matching
|
||||
with your bank feed and the credit card payment, without creating
|
||||
a dedicated journal entry .
|
||||
|
||||
We recommend the first approach as it is more accurate (your bank
|
||||
account balance is accurate, taking into accounts credit cards that have
|
||||
not been cashed yet). Both approaches require the same effort.
|
||||
|
||||
If you use eCommerce and an automated payment gateway, you will only
|
||||
need to take care of the bank reconciliation part as paid invoice will
|
||||
be automatically recorded in the right journal. You will use the second
|
||||
approach.
|
||||
|
||||
Even if the first method is cleaner, Odoo support the second approach
|
||||
because some accountants are used to it (*QuickBooks* and *Peachtree*
|
||||
users).
|
||||
|
||||
Option 1: Undeposited Funds
|
||||
===========================
|
||||
|
||||
Configuration
|
||||
-------------
|
||||
|
||||
On the Accounting module, go to :menuselection:`Configuration --> Journals --> Create`
|
||||
|
||||
Create a Journal called 'Credit card payments' with the following data:
|
||||
|
||||
- **Journal Name**: Credit card
|
||||
- **Default debit account**: Credit cards
|
||||
- **Default credit account**: Credit cards
|
||||
|
||||
The account type should be "Credit Card". Once it's done, don't forget to set the "Credit cards" account as "Allow
|
||||
Reconciliation".
|
||||
|
||||
.. image:: ./media/credit01.png
|
||||
:align: center
|
||||
|
||||
From credit card payments to bank statements
|
||||
--------------------------------------------
|
||||
|
||||
The first way to handle credit cards is to create a credit card journal.
|
||||
Thus, credit cards become a payment method in itself and you will record
|
||||
two transactions.
|
||||
|
||||
Once you receive a customer credit card payment, go to the related
|
||||
invoice and click on Register Payment. Fill in the information about the
|
||||
payment:
|
||||
|
||||
- **Payment method**: Credit card
|
||||
|
||||
- **Memo**: write the invoice reference
|
||||
|
||||
.. image:: ./media/credit02.png
|
||||
:align: center
|
||||
|
||||
This operation will produce the following journal entry:
|
||||
|
||||
+----------------------+-------------------+----------+----------+
|
||||
| Account | Statement Match | Debit | Credit |
|
||||
+======================+===================+==========+==========+
|
||||
| Account Receivable | | | 100.00 |
|
||||
+----------------------+-------------------+----------+----------+
|
||||
| Credit Cards | | 100.00 | |
|
||||
+----------------------+-------------------+----------+----------+
|
||||
|
||||
The invoice is marked as paid as soon as you record the credit card
|
||||
payment.
|
||||
|
||||
Then, once you get the bank statements, you will match this statement
|
||||
with the credit card that is in the 'Credit card' account.
|
||||
|
||||
+----------------+-------------------+----------+----------+
|
||||
| Account | Statement Match | Debit | Credit |
|
||||
+================+===================+==========+==========+
|
||||
| Credit cards | X | | 100.00 |
|
||||
+----------------+-------------------+----------+----------+
|
||||
| Bank | | 100.00 | |
|
||||
+----------------+-------------------+----------+----------+
|
||||
|
||||
If you use this approach to manage credit cards payments, you get the
|
||||
list of credit cards payments that have not been cashed in the "Credit
|
||||
card" account (accessible, for example, from the general ledger).
|
||||
|
||||
.. note::
|
||||
Both methods will produce the same data in your accounting at the end of the
|
||||
process. But, if you have credit cards that have not been cashed, this one
|
||||
is cleaner because those credit cards have not been reported yet on your bank
|
||||
account.
|
||||
|
||||
Option 2: One journal entry only
|
||||
================================
|
||||
|
||||
Configuration
|
||||
-------------
|
||||
|
||||
There is nothing to configure if you plan to manage your credit cards
|
||||
using this method.
|
||||
|
||||
From credit card payments to bank statements
|
||||
--------------------------------------------
|
||||
|
||||
Once you receive a customer credit card payment, go to the related
|
||||
invoice and click on Register Payment. Fill in the information about the
|
||||
payment:
|
||||
|
||||
- **Payment method**: the bank that will be used for the deposit
|
||||
|
||||
- **Memo**: write the credit card transaction number
|
||||
|
||||
.. image:: ./media/credit03.png
|
||||
:align: center
|
||||
|
||||
The invoice is marked as paid as soon as the credit card payment has
|
||||
been recorded. Once you receive the bank statements, you will do the
|
||||
matching with the statement and this actual payment (technically: point
|
||||
this payment and relate it to the statement line).
|
||||
|
||||
With this approach, you will get the following journal entry in your
|
||||
books:
|
||||
|
||||
+----------------------+-------------------+----------+----------+
|
||||
| Account | Statement Match | Debit | Credit |
|
||||
+======================+===================+==========+==========+
|
||||
| Account Receivable | X | | 100.00 |
|
||||
+----------------------+-------------------+----------+----------+
|
||||
| Bank | | 100.00 | |
|
||||
+----------------------+-------------------+----------+----------+
|
||||
|
||||
.. tip::
|
||||
You may also record the payment directly without going on the customer
|
||||
invoice, using the top menu :menuselection:`Sales --> Payments`. This method may be more
|
||||
convenient if you have a lot of credit cards to record in a batch but you
|
||||
will have to reconcile entries afterwards (matching payments with invoices).
|
||||
|
||||
If you use this approach to manage received credit cards, you can use
|
||||
the report "Bank Reconciliation Report" to verify which credit cards
|
||||
have been received or paid by the bank (this report is available from
|
||||
the "More" option from the Accounting dashboard on the related bank
|
||||
account).
|
||||
|
||||
.. image:: ./media/credit04.png
|
||||
:align: center
|
||||
|
||||
.. seealso::
|
||||
|
||||
* :doc:`recording`
|
||||
* :doc:`../../bank/feeds/paypal`
|
||||
* :doc:`check`
|
||||
* :doc:`followup`
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 20 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: 4.9 KiB |
45
accounting/receivables/customer_payments/online_payment.rst
Normal file
45
accounting/receivables/customer_payments/online_payment.rst
Normal file
@ -0,0 +1,45 @@
|
||||
======================
|
||||
Invoice Online Payment
|
||||
======================
|
||||
|
||||
To make it more convenient for your customers to pay the invoices you issue, you can activate the
|
||||
**Invoice Online Payment** feature, which adds a *Pay Now* button on their **Customer Portal**. This
|
||||
allows your customers to see their invoices online and pay directly with their favorite payment
|
||||
method, making the payment process much easier.
|
||||
|
||||
.. image:: media/online-payment-acquirers.png
|
||||
:align: center
|
||||
:alt: Payment acquirer choice after having clicked on "Pay Now"
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Make sure your :ref:`Payment Acquirers are correctly configured <payment_acquirers/configuration>`.
|
||||
|
||||
.. note::
|
||||
By default, ":doc:`Wire Transfer <../../../general/payment_acquirers/wire_transfer>`" is the only
|
||||
Payment Acquirer activated, but you still have to fill out the payment details.
|
||||
|
||||
To activate the Invoice Online Payment, go to :menuselection:`Accounting --> Configuration -->
|
||||
Settings --> Customer Payments`, enable **Invoice Online Payment**, and click on *Save*.
|
||||
|
||||
Customer Portal
|
||||
===============
|
||||
|
||||
After issuing the invoice, click on *Send & Print* and send the invoice by email to the customer.
|
||||
They will receive an email with a link that redirects them to the invoice on their **Customer
|
||||
Portal**.
|
||||
|
||||
.. image:: media/online-payment-view-invoice.png
|
||||
:align: center
|
||||
:alt: Email with a link to view the invoice online on the Customer Portal.
|
||||
|
||||
They can choose which Payment Acquirer to use by clicking on *Pay Now*.
|
||||
|
||||
.. image:: media/online-payment-pay-now.png
|
||||
:align: center
|
||||
:alt: "Pay now" button on an invoice in the Customer Portal.
|
||||
|
||||
.. seealso::
|
||||
|
||||
- :doc:`../../../general/payment_acquirers/payment_acquirers`
|
||||
@ -121,7 +121,7 @@ payments.
|
||||
|
||||
|
||||
.. seealso::
|
||||
- :doc:`credit_cards`
|
||||
- :doc:`online_payment`
|
||||
- :doc:`../../bank/feeds/paypal`
|
||||
- :doc:`check`
|
||||
- :doc:`followup`
|
||||
|
||||
@ -77,4 +77,5 @@ Applications
|
||||
events
|
||||
survey
|
||||
expense/expense
|
||||
mobile/firebase
|
||||
studio
|
||||
mobile/firebase
|
||||
|
||||
3
conf.py
3
conf.py
@ -231,7 +231,7 @@ latex_documents = [
|
||||
('legal/terms/i18n/partnership_tex_fr', 'odoo_partnership_agreement_fr.tex', 'Odoo Partnership Agreement (FR)', '', 'howto'),
|
||||
('legal/terms/i18n/terms_of_sale_fr', 'terms_of_sale_fr.tex', u'Conditions Générales de Vente Odoo', '', 'howto'),
|
||||
|
||||
#('legal/terms/i18n/enterprise_tex_nl', 'odoo_enterprise_agreement_nl.tex', 'Odoo Enterprise Subscription Agreement (NL)', '', 'howto'),
|
||||
('legal/terms/i18n/enterprise_tex_nl', 'odoo_enterprise_agreement_nl.tex', 'Odoo Enterprise Subscription Agreement (NL)', '', 'howto'),
|
||||
#('legal/terms/i18n/partnership_tex_nl', 'odoo_partnership_agreement_nl.tex', 'Odoo Partnership Agreement (NL)', '', 'howto'),
|
||||
|
||||
('legal/terms/i18n/enterprise_tex_de', 'odoo_enterprise_agreement_de.tex', 'Odoo Enterprise Subscription Agreement (DE)', '', 'howto'),
|
||||
@ -322,6 +322,7 @@ LANGUAGES = {
|
||||
|
||||
def setup(app):
|
||||
app.add_stylesheet('accounting.css')
|
||||
app.add_stylesheet('legal.css')
|
||||
app.add_javascript('prefixfree.min.js')
|
||||
app.add_javascript('atom.js')
|
||||
app.add_javascript('immutable.js')
|
||||
|
||||
@ -52,7 +52,7 @@ This is an In-App Purchase feature, each generated lead will cost you one credit
|
||||
If you choose to get contact information each contact will also cost us one additional credit.
|
||||
Here is the pricing for this `feature <https://iap.odoo.com/iap/in-app-services/167?>`__,
|
||||
To buy credits you can either go to :menuselection:`CRM --> Configuration --> Settings --> Buy
|
||||
Credits`; or go to `Settings --> In-App Purchases --> View my Services`.
|
||||
Credits`; or go to :menuselection: `Settings --> In-App Purchases --> View my Services`.
|
||||
|
||||
.. image:: media/LM6.png
|
||||
:align: center
|
||||
|
||||
@ -9,3 +9,4 @@ Optimize your Day-to-Day work
|
||||
optimize/onsip
|
||||
optimize/setup
|
||||
optimize/partner_autocomplete
|
||||
optimize/gamification
|
||||
|
||||
86
crm/optimize/gamification.rst
Normal file
86
crm/optimize/gamification.rst
Normal file
@ -0,0 +1,86 @@
|
||||
==========================================
|
||||
How to motivate and reward my salespeople?
|
||||
==========================================
|
||||
|
||||
Challenging your employees to reach specific targets with goals and rewards is an excellent way to
|
||||
reinforce good habits and improve your salespeople productivity. The Gamification module gives you
|
||||
simple and creative ways to motivate and evaluate your employees with real-time recognition and
|
||||
badges inspired by game mechanics.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Install the *Gamification* module, or the *CRM gamification* one, which adds some useful data
|
||||
(goals and challenges) that can be used on *CRM/Sale*.
|
||||
|
||||
.. image:: media/gamification_module_install.png
|
||||
:align: center
|
||||
:alt: View of the gamification module being installed in Odoo
|
||||
|
||||
Create a challenge
|
||||
==================
|
||||
|
||||
Now, create your first challenge by going to :menuselection:`Settings --> Gamification Tools
|
||||
--> Challenges`.
|
||||
|
||||
.. note::
|
||||
As the gamification tool is a one-time technical setup, you need to activate the technical
|
||||
features in order to access the configuration. To do so, go to *Settings* and *Activate the
|
||||
developer mode*.
|
||||
|
||||
.. image:: media/gamification_tools_menu.png
|
||||
:align: center
|
||||
:alt: View if the gamification tools menu in Odoo Settings
|
||||
|
||||
A challenge is a mission that you send to your sales team. It can include one or several goals, set
|
||||
for a specific period of time. Configure your challenge as follows:
|
||||
|
||||
#. Assign the salespeople to be challenged;
|
||||
#. Assign a responsible;
|
||||
#. Set up the periodicity along with the start and the end date;
|
||||
#. Select your goals;
|
||||
#. Set up your rewards (badges).
|
||||
|
||||
.. note::
|
||||
Badges are granted when a challenge is finished. This is either at the end of a running period
|
||||
(eg: end of the month for a monthly challenge), at the end date of a challenge (if no periodicity
|
||||
is set), or when the challenge is manually closed.
|
||||
|
||||
In the example below, 2 employees are being challenged with a *Monthly Sales Target*. The challenge
|
||||
is based on 2 goals: the total amount invoiced and number of new leads generated. At the end of the
|
||||
month, the winner will be granted with a badge.
|
||||
|
||||
.. image:: media/challenges.png
|
||||
:align: center
|
||||
:alt: View of the challenge form and a challenge being created for Odoo Sales
|
||||
|
||||
Set up goals
|
||||
------------
|
||||
|
||||
| The users can be evaluated using goals and numerical objectives to reach.
|
||||
| **Goals** are assigned through *challenges* that evaluate (see image above) and compare members of
|
||||
a team throughout time.
|
||||
| You can create a new goal on the fly from a *Challenge* by clicking on *Add new item*, under
|
||||
*Goals*. Select the business object according to your company's needs. Examples: number of new
|
||||
leads, time to qualify a lead, total amount invoiced in a specific week, month or any other time
|
||||
frame based on your management preferences, etc.
|
||||
|
||||
.. image:: media/goal_definitions.png
|
||||
:align: center
|
||||
:alt: View of the goal definition form and a goal definition being created for Odoo Sales
|
||||
|
||||
.. note::
|
||||
Goals may include your database setup as well (e.g. set your company data and a timezone,
|
||||
create new users, etc.).
|
||||
|
||||
Set up rewards
|
||||
--------------
|
||||
|
||||
For non-numerical achievements, **Badges** can be granted to users. From a simple thank you to an
|
||||
exceptional achievement, a badge is an easy way to express gratitude to a user for their good work.
|
||||
To create and grant badges to your employees based on their performance, go to
|
||||
:menuselection:`Settings --> Gamification Tools --> Badges`.
|
||||
|
||||
.. image:: media/badges.png
|
||||
:align: center
|
||||
:alt: View of the badges page in Odoo
|
||||
BIN
crm/optimize/media/badges.png
Normal file
BIN
crm/optimize/media/badges.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
BIN
crm/optimize/media/challenges.png
Normal file
BIN
crm/optimize/media/challenges.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
BIN
crm/optimize/media/gamification_module_install.png
Normal file
BIN
crm/optimize/media/gamification_module_install.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 27 KiB |
BIN
crm/optimize/media/gamification_tools_menu.png
Normal file
BIN
crm/optimize/media/gamification_tools_menu.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 44 KiB |
BIN
crm/optimize/media/goal_definitions.png
Normal file
BIN
crm/optimize/media/goal_definitions.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
@ -5,6 +5,6 @@ Organize the pipeline
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
../discuss/plan_activities
|
||||
../discuss/overview/plan_activities
|
||||
pipeline/lost_opportunities
|
||||
pipeline/multi_sales_team
|
||||
|
||||
@ -8,11 +8,4 @@ Discuss
|
||||
:titlesonly:
|
||||
|
||||
discuss/overview
|
||||
discuss/tracking
|
||||
discuss/monitoring
|
||||
discuss/mentions
|
||||
discuss/team_communication
|
||||
discuss/plan_activities
|
||||
discuss/mail_twitter
|
||||
discuss/email_servers
|
||||
discuss/advanced
|
||||
@ -6,4 +6,5 @@ Advanced
|
||||
:titlesonly:
|
||||
:glob:
|
||||
|
||||
advanced/emailtemplate
|
||||
advanced/email_servers
|
||||
advanced/email_template
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
============================================================
|
||||
How to use my mail server to send and receive emails in Odoo
|
||||
How to Use my Mail Server to Send and Receive Emails in Odoo
|
||||
============================================================
|
||||
|
||||
If you are a user of Odoo Online or Odoo.sh...
|
||||
@ -105,6 +105,10 @@ you should add a DNS "odoo._domainkey" CNAME record to
|
||||
For example, for "foo.com" they should have a record "odoo._domainkey.foo.com"
|
||||
that is a CNAME with the value "odoo._domainkey.odoo.com".
|
||||
|
||||
Restriction
|
||||
-----------
|
||||
Please note that the port 25 is blocked for security reasons. Try using 587, 465 or 2525.
|
||||
|
||||
How to manage inbound messages
|
||||
==============================
|
||||
|
||||
|
Before Width: | Height: | Size: 2.6 KiB After Width: | Height: | Size: 2.6 KiB |
|
Before Width: | Height: | Size: 37 KiB After Width: | Height: | Size: 37 KiB |
|
Before Width: | Height: | Size: 43 KiB After Width: | Height: | Size: 43 KiB |
|
Before Width: | Height: | Size: 58 KiB After Width: | Height: | Size: 58 KiB |
@ -1,41 +0,0 @@
|
||||
====================================
|
||||
How to follow Twitter feed from Odoo
|
||||
====================================
|
||||
|
||||
.. image:: media/twitter_user-image.png
|
||||
:align: center
|
||||
|
||||
You can follow specific hashtags on Twitter and see the tweets within the
|
||||
Odoo Discuss channels of your choice. The tweets are retrieved periodically from Twitter.
|
||||
An authenticated user can retweet the messages.
|
||||
|
||||
Setting up the App on Twitter's side
|
||||
====================================
|
||||
|
||||
Twitter uses an "App" on its side which is opens a gate to which Odoo asks for
|
||||
tweets, and through which a user can retweet.
|
||||
To set up this app, go to http://apps.twitter.com/app/new and put in the values:
|
||||
|
||||
- Name: this is the name of the application on Twitter
|
||||
|
||||
- Website: this is the external url of your Odoo database, with "/web" added.
|
||||
For example, if your Odoo instance is hosted at "http://www.example.com", you
|
||||
should put "http://www.example.com/web" in this field.
|
||||
|
||||
- Callback URL: this is the address on which Twitter will respond. Following the
|
||||
previous example you should write "http://www.example.com/web/twitter/callback".
|
||||
|
||||
Do not forget to accept the terms **Developer agreement** of use and click on
|
||||
**Create your Twitter application** at the bottom of the page.
|
||||
|
||||
|
||||
Getting the API key and secret
|
||||
==============================
|
||||
|
||||
When on the App dashboard, switch to the **Keys and Access Tokens** tab.
|
||||
|
||||
.. image:: media/api_key.png
|
||||
:align: center
|
||||
|
||||
And copy those values in Odoo in :menuselection:`Settings--> General Settings--> Twitter discuss integration`
|
||||
and click on **Save** to save the settings.
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.4 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.2 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.0 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 5.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.2 KiB |
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user