Compare commits
241 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
| 408f87e7e3 | |||
| f74679a1d8 | |||
| f775d1df3a | |||
| bdd8032b80 | |||
| 0cb2dc8545 | |||
| a8536b25ca | |||
| f5bbbb4885 | |||
| c075f0743d | |||
| 8f92fa4251 | |||
| cee6765d48 | |||
| 6caea007cb | |||
| 6da781ccf3 | |||
| e98c22f19e | |||
| 12561f96ff | |||
| 9b15efef14 | |||
| 2f505f9d2a | |||
| 02bc1136f6 | |||
| 44e1dba85d | |||
| 98bceb8317 | |||
| c9dbc4da09 | |||
| 650cccecca | |||
| ef3b6bc763 | |||
| 04ce02c019 | |||
| 1852679ad0 | |||
| b3b3a95d49 | |||
| f1fb08dc7c | |||
| fe8497b673 | |||
| 8cd200157c | |||
| e1d6eba30a | |||
| 4f1a4ec4fc | |||
| 4f35fd1b93 | |||
| c0ea9a5c7b | |||
| a3b9c5eba3 | |||
| bf816d13d4 | |||
| babf5e2e86 | |||
| 8ffb76a645 | |||
| 4472ac1e2b | |||
| 2a1ff2a57c | |||
| 0765eff401 | |||
| 0d72a967f4 | |||
| 4c97640126 | |||
| 27e915fe41 | |||
| 7c8b992104 | |||
| c08c2527d9 | |||
| 5bae4757f8 | |||
| 1b51eb756f | |||
| c91b4a549b | |||
| 6c9d67757a | |||
| e40850df69 | |||
| 7dd02462f2 | |||
| d935b3e8e5 | |||
| 489771d2cd | |||
| 41d2463ca9 | |||
| e9745781f4 | |||
| a30e36f4f1 | |||
| a906a85110 | |||
| 350a536c17 | |||
| 23cafed0e0 | |||
| 3ff0388c57 | |||
| 1275d4c523 | |||
| 97ece83b34 | |||
| af7d307b76 | |||
| 27175c3685 | |||
| 041740fd85 | |||
| e1eea953a4 | |||
| 8fa89877e7 | |||
| d833134fa3 | |||
| 7f346c319a | |||
| 57c2fc5916 | |||
| bd60ab9d2e | |||
| e946532b9b | |||
| a66f30a2b1 | |||
| eb2315acd9 | |||
| 739e538b7a | |||
| 432ff8f779 | |||
| 6a9a130585 | |||
| 21963b82a6 | |||
| 188a876a25 | |||
| 51bc9d0719 | |||
| f93fb12e6b | |||
| 93ae6ca2bd | |||
| 1af386916f | |||
| 9cce3b2294 | |||
| d00e0bd870 | |||
| e709090a62 | |||
| b87e51a130 | |||
| 0c88e48f7e | |||
| b3f119724d | |||
| 77f6d8897b | |||
| de2e347a2b | |||
| 0532a240c3 | |||
| 8ea2319065 | |||
| 5adc209e91 | |||
| bf7b48fe47 | |||
| 29bfb56d33 | |||
| 21ff81f8be | |||
| d5edc4566e | |||
| 74903d5c9f | |||
| 4b842d251c | |||
| c0157e0ade | |||
| 70c734769e | |||
| 55cc1f04a6 | |||
| a61b56745b | |||
| b78c6405e1 | |||
| ae09e682d7 | |||
| 172d7de99b | |||
| 1a5ba135b6 | |||
| b7243add65 | |||
| aae3e0f146 | |||
| 43c02a6561 | |||
| 60eadd4d57 | |||
| 10dd4e5936 | |||
| f639c52705 | |||
| 0d5cd136eb | |||
| 34310a683b | |||
| e3ab1c1267 | |||
| 23656806d3 | |||
| bdadc40f7b | |||
| 1841825534 | |||
| 24f84244e9 | |||
| 5004122011 | |||
| a40685b5d3 | |||
| e218ae4991 | |||
| 7c24b8e156 | |||
| 68805ae8d4 | |||
| 64e11ac906 | |||
| f5578ca10d | |||
| 26911cf6f6 | |||
| cbba672929 | |||
| 14c8a1b0e9 | |||
| f3bee4c64d | |||
| 611e16d2cc | |||
| 21b1add8a8 | |||
| 3077a9c30f | |||
| b0eed05bcd | |||
| cbbb2a459f | |||
| 73cba15619 | |||
| c1ae41a237 | |||
| b8f384663e | |||
| e9eab4fb08 | |||
| 44f625f22a | |||
| 5cd9ba3921 | |||
| dfdced9aa9 | |||
| cac1cbc562 | |||
| fc82654bef | |||
| 40f1536166 | |||
| e4dd269701 | |||
| 783fb68c68 | |||
| 6add09163d | |||
| e59726ce59 | |||
| f09d5af198 | |||
| c36a9e2bbc | |||
| 279c000548 | |||
| 8c1f32559f | |||
| e7b82d41b0 | |||
| ffb6948b4c | |||
| 3c85d536a4 | |||
| b4fb6c6ead | |||
| a029ba588b | |||
| 4b75a3c0b3 | |||
| 4973df7c89 | |||
| b32a07bd51 | |||
| 9b3ffe43cf | |||
| 615adf604b | |||
| bbe3b78352 | |||
| ef1e8b0da2 | |||
| 21cc6a4b29 | |||
| 971fc7c145 | |||
| dbf6a2c8b5 | |||
| c44bc48be2 | |||
| 3510373455 | |||
| 973bbfb59b | |||
| ef414bda27 | |||
| c05c44ba7f | |||
| 53e3161a80 | |||
| fb0cbbec0c | |||
| 35470e02fd | |||
| 0cca0b5dba | |||
| be58071b69 | |||
| b11a339786 | |||
| 761188dc57 | |||
| 9ce3eedc65 | |||
| e43df474d4 | |||
| bd00839c8f | |||
| bb710ab6b2 | |||
| 7d6191c005 | |||
| 9bcc411396 | |||
| e20a4e42b7 | |||
| 7d82513292 | |||
| c694bdbd0c | |||
| 47606228ea | |||
| c094ba8bee | |||
| 09d8b04773 | |||
| 3682b19a04 | |||
| 94194f306a | |||
| 4501fdd186 | |||
| 0fe45eead9 | |||
| 0d4d51b43c | |||
| c76eaf4cd0 | |||
| 568f507d9f | |||
| 67133b5c6e | |||
| e482f2bd1b | |||
| 1adc335a7c | |||
| c41ea1724f | |||
| 3ebf1728f6 | |||
| 5eee96289b | |||
| 8c27e0372c | |||
| 60d87e4e4a | |||
| c9ec5aef87 | |||
| 85994b65ce | |||
| 6a7f9aa898 | |||
| 3f3b213b6b | |||
| e6486dc4a9 | |||
| e0268afb0a | |||
| 607770aaee | |||
| b8209b8768 | |||
| eae02bfe38 | |||
| 29424279f4 | |||
| 2872337113 | |||
| f46c6cd0ec | |||
| a3b224036f | |||
| 8b99aef0ca | |||
| 89457036ce | |||
| 5807f94c02 | |||
| 54e7ed30ac | |||
| de137b0bcf | |||
| 3c44972f02 | |||
| 5b80ed551c | |||
| d664c7ca30 | |||
| 7b485f8049 | |||
| 42ac8df979 | |||
| d2ef4232fb | |||
| 06bd4b173a | |||
| 63358426e1 | |||
| 8620437a11 | |||
| 7cfe9c36ff | |||
| 3b54a96f3a | |||
| 2c6f8510a9 | |||
| c133276b76 | |||
| 2933ed4860 | |||
| 195c21067b |
@@ -2,157 +2,182 @@
|
||||
host = https://www.transifex.com
|
||||
type = PO
|
||||
|
||||
[odoo-13-doc.accounting]
|
||||
[odoo-14-doc.accounting]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/accounting.po
|
||||
source_file = locale/sources/accounting.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.applications]
|
||||
[odoo-14-doc.applications]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/applications.po
|
||||
source_file = locale/sources/applications.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.crm]
|
||||
[odoo-14-doc.contributing]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/contributing.po
|
||||
source_file = locale/sources/contributing.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-14-doc.crm]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/crm.po
|
||||
source_file = locale/sources/crm.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.db_management]
|
||||
[odoo-14-doc.db_management]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/db_management.po
|
||||
source_file = locale/sources/db_management.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.discuss]
|
||||
[odoo-14-doc.discuss]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/discuss.po
|
||||
source_file = locale/sources/discuss.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.ecommerce]
|
||||
[odoo-14-doc.ecommerce]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/ecommerce.po
|
||||
source_file = locale/sources/ecommerce.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.email_marketing]
|
||||
[odoo-14-doc.email_marketing]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/email_marketing.po
|
||||
source_file = locale/sources/email_marketing.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.expense]
|
||||
[odoo-14-doc.expense]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/expense.po
|
||||
source_file = locale/sources/expense.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.fsm]
|
||||
[odoo-14-doc.events]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/events.po
|
||||
source_file = locale/sources/events.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-14-doc.fsm]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/fsm.po
|
||||
source_file = locale/sources/fsm.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.general]
|
||||
[odoo-14-doc.general]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/general.po
|
||||
source_file = locale/sources/general.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.getting_started]
|
||||
[odoo-14-doc.getting_started]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/getting_started.po
|
||||
source_file = locale/sources/getting_started.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.helpdesk]
|
||||
[odoo-14-doc.helpdesk]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/helpdesk.po
|
||||
source_file = locale/sources/helpdesk.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.index]
|
||||
[odoo-14-doc.index]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/index.po
|
||||
source_file = locale/sources/index.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.inventory]
|
||||
[odoo-14-doc.inventory]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/inventory.po
|
||||
source_file = locale/sources/inventory.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.iot]
|
||||
[odoo-14-doc.iot]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/iot.po
|
||||
source_file = locale/sources/iot.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.livechat]
|
||||
[odoo-14-doc.livechat]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/livechat.po
|
||||
source_file = locale/sources/livechat.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.mobile]
|
||||
[odoo-14-doc.mobile]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/mobile.po
|
||||
source_file = locale/sources/mobile.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.marketing_automation]
|
||||
[odoo-14-doc.marketing_automation]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/marketing_automation.po
|
||||
source_file = locale/sources/marketing_automation.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.manufacturing]
|
||||
[odoo-14-doc.manufacturing]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/manufacturing.po
|
||||
source_file = locale/sources/manufacturing.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.planning]
|
||||
[odoo-14-doc.planning]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/planning.po
|
||||
source_file = locale/sources/planning.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.point_of_sale]
|
||||
[odoo-14-doc.point_of_sale]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/point_of_sale.po
|
||||
source_file = locale/sources/point_of_sale.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.portal]
|
||||
[odoo-14-doc.portal]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/portal.po
|
||||
source_file = locale/sources/portal.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.practical]
|
||||
[odoo-14-doc.practical]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/practical.po
|
||||
source_file = locale/sources/practical.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.project]
|
||||
[odoo-14-doc.project]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/project.po
|
||||
source_file = locale/sources/project.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.purchase]
|
||||
[odoo-14-doc.purchase]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/purchase.po
|
||||
source_file = locale/sources/purchase.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.quality]
|
||||
[odoo-14-doc.quality]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/quality.po
|
||||
source_file = locale/sources/quality.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.sales]
|
||||
[odoo-14-doc.sales]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/sales.po
|
||||
source_file = locale/sources/sales.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.sms_marketing]
|
||||
[odoo-14-doc.sms_marketing]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/sms_marketing.po
|
||||
source_file = locale/sources/sms_marketing.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.social_marketing]
|
||||
[odoo-14-doc.social_marketing]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/social_marketing.po
|
||||
source_file = locale/sources/social_marketing.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.support]
|
||||
[odoo-14-doc.studio]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/studio.po
|
||||
source_file = locale/sources/studio.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-14-doc.support]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/support.po
|
||||
source_file = locale/sources/support.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-13-doc.website]
|
||||
[odoo-14-doc.survey]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/survey.po
|
||||
source_file = locale/sources/survey.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-14-doc.timesheets]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/timesheets.po
|
||||
source_file = locale/sources/timesheets.pot
|
||||
source_lang = en
|
||||
|
||||
[odoo-14-doc.website]
|
||||
file_filter = locale/<lang>/LC_MESSAGES/website.po
|
||||
source_file = locale/sources/website.pot
|
||||
source_lang = en
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
{# note: if odoo.com/page/docs sub-menu's structure change, these links have to change as well #}
|
||||
|
||||
<li><a href="https://www.odoo.com/documentation/user/13.0/index.html">User</a></li>
|
||||
<li><a href="https://www.odoo.com/documentation/13.0/index.html">Developer</a></li>
|
||||
<li><a href="https://odoo.com/slides">eLearning</a></li>
|
||||
<li><a href="https://www.odoo.com/documentation/13.0/webservices/odoo.html">API</a></li>
|
||||
<li><a href="https://www.odoo.com/documentation/13.0/setup/install.html">Installation</a></li>
|
||||
<li><a href="https://www.odoo.com/documentation/user/14.0/index.html">User</a></li>
|
||||
<li><a href="https://www.odoo.com/documentation/14.0/index.html">Developer</a></li>
|
||||
<li><a href="https://training.odoo.com">Training Center</a></li>
|
||||
<li><a href="https://www.odoo.com/documentation/14.0/webservices/odoo.html">API</a></li>
|
||||
<li><a href="https://www.odoo.com/documentation/14.0/setup/install.html">Installation</a></li>
|
||||
<li><a href="https://www.odoo.com/page/odoo-white-paper">White Papers</a></li>
|
||||
<li><a href="https://www.odoo.com/page/legal">Legal</a></li>
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
|
After Width: | Height: | Size: 295 KiB |
|
After Width: | Height: | Size: 346 KiB |
|
After Width: | Height: | Size: 365 KiB |
|
After Width: | Height: | Size: 221 KiB |
|
After Width: | Height: | Size: 405 KiB |
@@ -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 |
@@ -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
|
||||
|
||||
@@ -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;
|
||||
}
|
||||
@@ -5,5 +5,4 @@ Miscellaneous
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
misc/batch
|
||||
misc/interbank
|
||||
@@ -1,146 +0,0 @@
|
||||
===============================
|
||||
Manage batch deposits of checks
|
||||
===============================
|
||||
|
||||
When your company's collections group receives checks from customers
|
||||
they will often place this money into their bank account in batches. As
|
||||
this money has been received in a physical form, someone in your company
|
||||
must manually bring the checks to the bank.
|
||||
|
||||
The bank will ask for a deposit ticket (also referred to as deposit
|
||||
slip) to be filled-in with the details of the checks or cash to be
|
||||
included in the transactions.
|
||||
|
||||
The bank statement will reflect the total amount that was deposited and
|
||||
the reference to the deposit ticket, not the individual checks.
|
||||
|
||||
Odoo assists you to prepare and print your deposit tickets, and later on
|
||||
reconcile them with your bank statement easily.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Install the batch deposit feature
|
||||
---------------------------------
|
||||
|
||||
In order to use the batch deposit feature, you need the module **Batch
|
||||
Deposit** to be installed.
|
||||
|
||||
.. note::
|
||||
|
||||
Usually, this module is automatically
|
||||
installed if checks are widely used in your country.
|
||||
|
||||
To verify that the **Batch Deposit** feature is installed, go to the
|
||||
:menuselection:`Configuration --> Settings` menu of the accounting application.
|
||||
Check the feature: **Allow batch deposit**.
|
||||
|
||||
.. image:: media/batch01.png
|
||||
:align: center
|
||||
|
||||
Activate the feature on your bank accounts
|
||||
------------------------------------------
|
||||
|
||||
Once you have installed this feature, Odoo automatically activate bank
|
||||
deposits on your main bank accounts.
|
||||
|
||||
To control which bank account can do batch deposit and which can not, go
|
||||
to the journal that you defined to pay your checks, usually called
|
||||
'Checks' or 'Bank' (see :doc:`../../receivables/customer_payments/check`,
|
||||
in the Accounting apps, :menuselection:`Configuration --> Accounting --> Journals`.
|
||||
|
||||
In **Advanced Settings** tab, in section **Miscellaneous**, set Debit Method to
|
||||
**Batch Deposit**.
|
||||
|
||||
.. image:: media/batch02.png
|
||||
:align: center
|
||||
|
||||
If you check **Batch Deposit** in your debit method field, it means that
|
||||
payments created using this Journal (called Payment method when you want
|
||||
to make or receive a payment) will be applicable for the creation of
|
||||
Batch Deposits afterwards.
|
||||
|
||||
From checks received to the bank
|
||||
================================
|
||||
|
||||
Receive customer checks
|
||||
-----------------------
|
||||
|
||||
Once your checks are received, record them on the bank account on
|
||||
which you plan to deposit them. Once you select the bank account (or
|
||||
check journal if you configured Odoo that way), Odoo proposes you to use
|
||||
a batch deposit. Select this option if you plan to deposit the check to
|
||||
your bank.
|
||||
|
||||
.. image:: media/batch03.png
|
||||
:align: center
|
||||
|
||||
In the memo field, you can set the reference of the check.
|
||||
|
||||
.. note::
|
||||
|
||||
payments can be registered from the menu :menuselection:`Sales --> Payments`,
|
||||
or directly on the related invoice, using the **Register Payment** button.
|
||||
|
||||
Prepare a batch deposit
|
||||
-----------------------
|
||||
|
||||
From the Accounting application, go to the menu :menuselection:`Sales --> Batch Deposit`,
|
||||
and create a new **Batch Deposit**.
|
||||
|
||||
.. image:: media/batch04.png
|
||||
:align: center
|
||||
|
||||
Select the bank, then select the payments (checks) you want to add in
|
||||
this deposit. By default, Odoo proposes you all the checks that have not
|
||||
been deposited yet. That way you can verify that you do not forget or
|
||||
lost a check.
|
||||
|
||||
.. image:: media/batch05.png
|
||||
:align: center
|
||||
|
||||
You can then print the batch deposit, which will be very useful
|
||||
to prepare the deposit slip that the bank usually requires to complete.
|
||||
|
||||
Reconciling the Deposit with the Bank Statement
|
||||
-----------------------------------------------
|
||||
|
||||
When you process the bank statement reconciliation you will see the
|
||||
deposit ticket number referenced in the statement. When the reconciliation
|
||||
process is run, the user will be able to select the batch deposit that
|
||||
matches with the bank statement line.
|
||||
|
||||
.. image:: media/batch06.png
|
||||
:align: center
|
||||
|
||||
If you select a batch deposit, Odoo will automatically fill all the
|
||||
checks contained in this deposit for the matching. (2 checks were in
|
||||
the batch deposit in the example below)
|
||||
|
||||
.. image:: media/batch07.png
|
||||
:align: center
|
||||
|
||||
Troubleshooting
|
||||
===============
|
||||
|
||||
I don't see the batch deposit link on bank statements?
|
||||
------------------------------------------------------
|
||||
|
||||
If you don't have a batch deposit link in your bank statement, there
|
||||
could be two reasons:
|
||||
|
||||
- After having installed the batch deposit features you need to reload
|
||||
the page so that the browser is aware of this new feature. Just
|
||||
click the reload button of your browser.
|
||||
|
||||
- You do not have a batch deposit created for this bank account.
|
||||
|
||||
What happens if a check was refused?
|
||||
------------------------------------
|
||||
|
||||
If you have a smaller amount in your bank statement than the actual
|
||||
amount in your batch deposit, it probably means that one of your check
|
||||
has been refused.
|
||||
|
||||
In this case click on the line related to this check to remove it from
|
||||
the bank statement matching.
|
||||
|
Before Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 22 KiB |
|
Before Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 11 KiB |
|
Before Width: | Height: | Size: 18 KiB |
|
Before Width: | Height: | Size: 9.9 KiB |
|
Before Width: | Height: | Size: 6.9 KiB |
@@ -6,10 +6,12 @@ Localizations
|
||||
:titlesonly:
|
||||
|
||||
localizations/argentina
|
||||
localizations/chile
|
||||
localizations/colombia
|
||||
localizations/colombia_ES
|
||||
localizations/france
|
||||
localizations/germany
|
||||
localizations/indonesia
|
||||
localizations/italy_IT
|
||||
localizations/mexico
|
||||
localizations/netherlands
|
||||
|
||||
@@ -2,6 +2,13 @@
|
||||
Argentina
|
||||
=========
|
||||
|
||||
Webinars
|
||||
========
|
||||
Below you can find videos with a general description of the localization and how to configure it.
|
||||
|
||||
- This is a V13 video, there aren't major changes in the workflow and configuration
|
||||
compared to V14 `VIDEO WEBINAR OF A COMPLETE DEMO <https://youtu.be/c41-8cVaYAI>`_.
|
||||
|
||||
Introduction
|
||||
============
|
||||
|
||||
|
||||
@@ -0,0 +1,694 @@
|
||||
=====
|
||||
Chile
|
||||
=====
|
||||
|
||||
Introduction
|
||||
============
|
||||
|
||||
The Chilean localization has been improved and extended in Odoo v13. In this version, the next
|
||||
modules are available:
|
||||
|
||||
- **l10n_cl:** Adds accounting features for the Chilean localization, which represent the minimal
|
||||
configuration required for a company to operate in Chile and under the SII
|
||||
(Servicio de Impuestos Internos) regulations and guidelines.
|
||||
|
||||
- **l10n_cl_edi:** Includes all technical and functional requirements to generate and receive
|
||||
Electronic Invoice via web service, based on the SII regulations.
|
||||
|
||||
- **l10n_cl_reports:** Adds the reports Propuesta F29 y Balance Tributario (8 columnas).
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Install the Chilean localization modules
|
||||
----------------------------------------
|
||||
|
||||
For this, go to *Apps* and search for Chile. Then click *Install* in the module **Chile
|
||||
E-invoicing**. This module has a dependency with **Chile - Accounting**. In case this last
|
||||
one is not installed, Odoo installs it automatically with E-invoicing.
|
||||
|
||||
.. image:: media/Chile01.png
|
||||
:align: center
|
||||
:alt: Chilean module to install on Odoo.
|
||||
|
||||
.. note::
|
||||
When you install a database from scratch selecting Chile as country, Odoo will automatically
|
||||
install the base module: Chile - Accounting.
|
||||
|
||||
|
||||
Company Settings
|
||||
----------------
|
||||
|
||||
Once the modules are installed, the first step is to set up your company data. Additional
|
||||
to the basic information, you need to add all the data and elements required for Electronic
|
||||
Invoice, the easiest way to configure it is in
|
||||
:menuselection:`Accounting --> Settings --> Chilean Localization`.
|
||||
|
||||
Fiscal Information
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Fill in the fiscal information for your company according to the SII register, follow the
|
||||
instructions on each section.
|
||||
|
||||
.. image:: media/Chile02.png
|
||||
:align: center
|
||||
:alt: Chilean company fiscal data.
|
||||
|
||||
Electronic Invoice Data
|
||||
~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
This is part of the main information required to generate electronic Invoice, select your
|
||||
environment and the legal information, as well as the email address to receive invoices
|
||||
from your vendors and the alias you use to send invoices to your customers.
|
||||
|
||||
.. image:: media/Chile03.png
|
||||
:align: center
|
||||
:alt: Chilean edi environment settings.
|
||||
|
||||
Configure DTE Incoming email server
|
||||
***********************************
|
||||
|
||||
In order to receive you the claim and acceptance emails from your customers, it is
|
||||
crucial to define the DTE incoming email server, considering this configuration:
|
||||
|
||||
.. image:: media/Chile03_2.png
|
||||
:align: center
|
||||
:alt: Incoming email server configuration for Chilean DTE.
|
||||
|
||||
.. tip::
|
||||
For your Go-live make sure you archive/remove from your inbox all the emails
|
||||
related to vendor bills that are not required to be processed in Odoo.
|
||||
|
||||
Certificate
|
||||
~~~~~~~~~~~
|
||||
|
||||
In order to generate the electronic invoice signature, a digital certificate with the extension ``.pfx``
|
||||
is required, proceed to this section and load your file and password.
|
||||
|
||||
.. image:: media/Chile03_3.png
|
||||
:align: center
|
||||
:alt: Digital certificate access.
|
||||
|
||||
.. image:: media/Chile04.png
|
||||
:align: center
|
||||
:alt: Digital certificate configuration.
|
||||
|
||||
A certificate can be shared between several users. If this is the case leave the user field empty,
|
||||
so all your billing users can use the same one. On the other hand, if you need to restrict the
|
||||
certificate for a particular user, just define the users in the certificate.
|
||||
|
||||
Financial Reports
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
The report Propuesta F29 requires two values that need to be defined as part of the company
|
||||
configuration:
|
||||
|
||||
.. image:: media/Chile05.png
|
||||
:align: center
|
||||
:alt: Fiscal reports parameters.
|
||||
|
||||
Multicurrency
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
The official currency rate in Chile is provided by the SBIF, you can find the SBIF
|
||||
synchronization service in the currency rate configuration and you can set a predefined interval
|
||||
for the rate updates.
|
||||
|
||||
.. image:: media/Chile05_2.png
|
||||
:align: center
|
||||
:scale: 25
|
||||
:alt: Currency reate service for Chile.
|
||||
|
||||
In order to configure your token, you need to enable developer mode and access to
|
||||
:menuselection:`Settings --> Technical --> System parameters` and search the parameter
|
||||
``sbif_api_key`` and in the field Value introduce your token provided by the SBIF:
|
||||
|
||||
.. image:: media/Chile05_3.png
|
||||
:align: center
|
||||
:alt: Token configuration for currency rate service.
|
||||
|
||||
Chart of accounts
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
The chart of accounts is installed by default as part of the set of data included in
|
||||
the localization module. The accounts are mapped automatically in:
|
||||
|
||||
- Taxes.
|
||||
- Default Account Payable.
|
||||
- Default Account Receivable.
|
||||
- Transfer Accounts.
|
||||
- Conversion Rate.
|
||||
|
||||
|
||||
Master Data
|
||||
-----------
|
||||
|
||||
Partner
|
||||
~~~~~~~
|
||||
|
||||
Identification Type and VAT
|
||||
***************************
|
||||
|
||||
As part of the Chilean localization, the identification types defined by the SII
|
||||
are now available on the Partner form. This information is essential for most transactions.
|
||||
|
||||
.. image:: media/Chile06.png
|
||||
:align: center
|
||||
:scale: 25
|
||||
:alt: Chilean identification types for partners.
|
||||
|
||||
TaxpayerType
|
||||
************
|
||||
|
||||
In Chile, the document type associated with customers and vendors transactions is defined
|
||||
based on the Taxpayer Type. This field should be defined in the partner form, when creating
|
||||
a customer is important you make sure this value is set:
|
||||
|
||||
.. image:: media/Chile07.png
|
||||
:align: center
|
||||
:alt: Chilean taxpayer types for partners.
|
||||
|
||||
|
||||
Electronic Invoice Data
|
||||
***********************
|
||||
|
||||
As part of the information that is sent in the electronic Invoice, you need to define the
|
||||
email that is going to appear as the sender of the electronic invoice to your customer, and
|
||||
the Industry description.
|
||||
|
||||
.. image:: media/Chile07_2.png
|
||||
:align: center
|
||||
:alt: Chilean electronic invoice data for partners.
|
||||
|
||||
|
||||
Taxes
|
||||
~~~~~
|
||||
|
||||
As part of the localization module, the taxes are created automatically with their related
|
||||
financial account and configuration.
|
||||
|
||||
.. image:: media/Chile08.png
|
||||
:align: center
|
||||
:alt: Chilean taxes list.
|
||||
|
||||
Taxes Types
|
||||
***********
|
||||
|
||||
Chile has several tax types, the most common ones are:
|
||||
|
||||
- VAT. Is the regular VAT and it can have several rates.
|
||||
- ILA (Impuesto a la Ley de Alcholes). Taxes for alcoholic drinks. It has a different rate.
|
||||
|
||||
|
||||
Fiscal Positions
|
||||
~~~~~~~~~~~~~~~~
|
||||
|
||||
Based on the purchase transactions, the VAT can have different affections. This will be done
|
||||
in Odoo using the default purchase fiscal positions.
|
||||
|
||||
|
||||
Document Types
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
In some Latin American countries, including Chile, some accounting transactions like invoices and
|
||||
vendor bills are classified by document types defined by the government fiscal authorities (In
|
||||
Chile case: SII).
|
||||
|
||||
The document type is essential information that needs to be displayed in the printed reports and
|
||||
that needs to be easily identified within the set of invoices as well of account moves.
|
||||
|
||||
Each document type can have a unique sequence per company. As part of the localization,
|
||||
the Document Type includes the country on which the document is applicable and the data
|
||||
is created automatically when the localization module is installed.
|
||||
|
||||
The information required for the document types is included by default so the user doesn't need to
|
||||
fill anything on this view:
|
||||
|
||||
.. image:: media/Chile09.png
|
||||
:align: center
|
||||
:alt: Chilean fiscal document types list.
|
||||
|
||||
.. note::
|
||||
There are several document types that are inactive by default but can be activated if needed.
|
||||
|
||||
|
||||
Use on Invoices
|
||||
***************
|
||||
|
||||
The document type on each transaction will be determined by:
|
||||
|
||||
- The Journal related to the Invoice, identifying if the journal uses documents.
|
||||
- Condition applied based on the type of Issues and Receiver (ex. Type of fiscal
|
||||
regimen of the buyer and type of fiscal regimen of the vendor).
|
||||
|
||||
|
||||
Journals
|
||||
--------
|
||||
|
||||
Usage
|
||||
~~~~~
|
||||
|
||||
Sales
|
||||
*****
|
||||
|
||||
Sales Journals in Odoo usually represent a business unit or location, example:
|
||||
|
||||
- Ventas Santiago.
|
||||
- Ventas Valparaiso.
|
||||
|
||||
For the retail stores is common to have one journal per POS:
|
||||
|
||||
- Cashier 1.
|
||||
- Cashier 2.
|
||||
|
||||
|
||||
Purchases
|
||||
*********
|
||||
|
||||
The transactions purchase can be managed with a single journal, but sometimes companies use
|
||||
more than one in order to handle some accounting transactions that are not related to vendor
|
||||
bills but can be easily registered using this model, for example:
|
||||
|
||||
- Tax Payments to government.
|
||||
- Employees payments.
|
||||
|
||||
|
||||
Configuration
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
When creating sales journals the next information must be filled in:
|
||||
|
||||
**Point of sale type**: If the Sales journal will be used for electronic documents, the option
|
||||
Online must be selected. Otherwise, if the journal is used for invoices imported from a previous
|
||||
system or if you are using the SII portal “Facturación MiPyme“ you can use the option Manual.
|
||||
|
||||
**Use Documents**: This field is used to define if the journal will use Document Types. It is only
|
||||
applicable to Purchase and Sales journals that can be related to the
|
||||
different sets of document types available in Chile. By default, all the sales journals created will
|
||||
use documents.
|
||||
|
||||
.. image:: media/Chile41.png
|
||||
:align: center
|
||||
:alt: Document type configuration on Journal.
|
||||
|
||||
.. important::
|
||||
For the Chilean localization it’s important to define the default Debt and Credit accounts
|
||||
as they are required for one of the debit notes use cases.
|
||||
|
||||
CAF
|
||||
---
|
||||
|
||||
A CAF (Folio Authorization Code) is required, for each document type that is issued to your
|
||||
customers, the CAF is a file the SII provides to the Emisor with the folio/sequence authorized
|
||||
for the electronic invoice documents.
|
||||
|
||||
Your company can make several requests for folios and obtain several CAFs, each one associated
|
||||
with different ranges of folios. The CAFs are shared within all the journals, this means
|
||||
that you only need one active CAF per document type and it will be applied on all journals.
|
||||
|
||||
Please refer to the SII documentation to check the detail on how to acquire the CAF:
|
||||
`SII Timbraje <https://palena.sii.cl/dte/mn_timbraje.html>`_.
|
||||
|
||||
|
||||
Configuration
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
Once you have the CAF files you need to associate them with a document type in Odoo,
|
||||
in order to add a CAF, just follow these steps:
|
||||
|
||||
1. Access to :menuselection:`Accounting --> Settings --> CAF`
|
||||
2. Upload the file.
|
||||
3. Save the CAF.
|
||||
|
||||
.. image:: media/Chile39.png
|
||||
:align: center
|
||||
:alt: Steps to add a new CAF.
|
||||
|
||||
Once loaded, the status changes to *In Use*. At this moment, when a transaction is used
|
||||
for this document type, the invoice number takes the first folio in the sequence.
|
||||
|
||||
.. important::
|
||||
In case you have used some folios in your previous system, make sure you set the next valid
|
||||
folio when the first transation is created.
|
||||
|
||||
|
||||
|
||||
Usage and Testing
|
||||
=================
|
||||
|
||||
Electronic Invoice Workflow
|
||||
---------------------------
|
||||
|
||||
In the Chilean localization the electronic Invoice workflow covers the Emission of
|
||||
Customer Invoices and the reception of Vendor Bills, in the next diagram we explain how
|
||||
the information transmitted to the SII and between the customers and Vendors.
|
||||
|
||||
.. image:: media/Chile14.png
|
||||
:align: center
|
||||
:alt: Diagram with Electronic invoice transactions.
|
||||
|
||||
|
||||
Customer invoice Emission
|
||||
-------------------------
|
||||
|
||||
After the partners and journals are created and configured, the invoices are created in
|
||||
the standard way, for Chile one of the differentiators is the document type which is selected
|
||||
automatically based on the Taxpayer.
|
||||
|
||||
You can manually change the document type if needed.
|
||||
|
||||
.. image:: media/Chile15.png
|
||||
:align: center
|
||||
:alt: Document type selection on invoices.
|
||||
|
||||
|
||||
Validation and DTE Status
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
When all the invoice information is filled, either manually or automatically when it’s created
|
||||
from a sales order, proceed to validate the invoice. After the invoice is posted:
|
||||
|
||||
- The DTE File (Electronic Tax Document) is created automatically and added in the chatter.
|
||||
- The DTE SII status is set as: Pending to be sent.
|
||||
|
||||
.. image:: media/Chile16.png
|
||||
:align: center
|
||||
:alt: DTE XML File displayed in chatter.
|
||||
|
||||
The DTE Status is updated automatically by Odoo with a scheduled action that runs every day
|
||||
at night, if you need to get the response from the SII immediately you can do it manually as well.
|
||||
The DTE status workflow is as follows:
|
||||
|
||||
.. image:: media/Chile17.png
|
||||
:align: center
|
||||
:alt: Transition of DTE statuses.
|
||||
|
||||
|
||||
1. In the first step the DTE is sent to the SII, you can manually send it using the button: Enviar
|
||||
Ahora, a SII Tack number is generated and assigned to the invoice, you can use this number to
|
||||
check the details the SII sent back by email. The DTE status is updated to Ask for Status.
|
||||
|
||||
|
||||
2. Once the SII response is received Odoo updates the DTE Status, in case you want to do it
|
||||
manually just click on the button: Verify on SII. The result can either be Accepted, Accepted
|
||||
With Objection or Rejected.
|
||||
|
||||
.. image:: media/Chile18.png
|
||||
:align: center
|
||||
:alt: Identification transaction for invoice and Status update.
|
||||
|
||||
|
||||
There are several internal status in the SII before you get Acceptance or Rejection, in
|
||||
case you click continuously the Button Verify in SII, you will receive in the chatter the
|
||||
detail of those intermediate statuses:
|
||||
|
||||
.. image:: media/Chile18_2.png
|
||||
:align: center
|
||||
:alt: Descprtion of each DTE status in the chatter.
|
||||
|
||||
3. The final response from the SII, can take on of these values:
|
||||
|
||||
|
||||
**Accepted:** Indicates the invoice information is correct, our document is now fiscally valid
|
||||
and it’s automatically sent to the customer.
|
||||
|
||||
**Accepted with objections:** Indicates the invoice information is correct but a minor issue
|
||||
was identified, nevertheless our document is now fiscally valid and it’s automatically
|
||||
sent to the customer.
|
||||
|
||||
.. image:: media/Chile19.png
|
||||
:align: center
|
||||
:alt: Email track once it is sent to the customer.
|
||||
|
||||
**Rejected:** Indicates the information in the invoice is incorrect and needs to be
|
||||
corrected, the detail of the issue is received in the emails you registered in the
|
||||
SII, if it is properly configured in Odoo, the details are also retrieved
|
||||
in the chatter once the email server is processed.
|
||||
|
||||
If the invoice is Rejected please follow this steps:
|
||||
|
||||
* Change the document to draft.
|
||||
* Make the required corrections based on the message received from the SII.
|
||||
* Post the invoice again.
|
||||
|
||||
.. image:: media/Chile20.png
|
||||
:align: center
|
||||
:alt: Message when an invoice is rejected.
|
||||
|
||||
|
||||
Crossed references
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
When the Invoice is created as a result of another fiscal document, the information related to the
|
||||
originator document must be registered in the Tab Cross Reference, which is commonly used for
|
||||
credit or debit notes, but in some cases can be used on Customer Invoices as well. In the case of the
|
||||
credit and debit notes, they are set automatically by Odoo:
|
||||
|
||||
.. image:: media/Chile21.png
|
||||
:align: center
|
||||
:alt: Invoice tab with origin document number and data.
|
||||
|
||||
Invoice PDF Report
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
After the invoice is Accepted and valdiated by the SII and the PDF is printed it includes the
|
||||
fiscal elements that indicates out document is fiscally valid:
|
||||
|
||||
.. image:: media/Chile22.png
|
||||
:align: center
|
||||
:alt: Barcode and fiscal elements in the invice report.
|
||||
|
||||
|
||||
Commercial Validation
|
||||
~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Once the invoice has been sent to the customer:
|
||||
|
||||
1. DTE partner status changes to “Sent”.
|
||||
2. The customer must send a reception confirmation email.
|
||||
3. Subsequently, if all the commercial terms and invoice data are correct, they will send the
|
||||
Acceptance confirmation, otherwise they send a Claim.
|
||||
4. The field DTE acceptation status is updated automatically.
|
||||
|
||||
.. image:: media/Chile23.png
|
||||
:align: center
|
||||
:alt: Message with the commercial acceptance from the customer.
|
||||
|
||||
|
||||
Processed for Claimed invoices
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Once the invoice has been Accepted by the SII **it can not be cancelled in Odoo**. In case you
|
||||
get a Claim for your customer the correct way to proceed is with a Credit Note to either cancel
|
||||
the Invoice or correct it. Please refer to the Credit Notes section for more details.
|
||||
|
||||
.. image:: media/Chile24.png
|
||||
:align: center
|
||||
:alt: Invoice Comercial status updated to Claimed.
|
||||
|
||||
Common Errors
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
There are multiple reasons behind a rejection from the SII, but these are some of the common errors
|
||||
you might have and which is the related solution.
|
||||
|
||||
- Error: RECHAZO- DTE Sin Comuna Origen.
|
||||
|
||||
*Hint:* Make sure the Company Address is properly filled including the State and City.
|
||||
|
||||
- Error en Monto : - IVA debe declararse.
|
||||
|
||||
*Hint:* The invoice lines should include one VAT tax, make sure you add one on each invoice line.
|
||||
|
||||
- Error: Rut No Autorizado a Firmar.
|
||||
|
||||
*Hint:* The invoice lines should include one VAT tax, make sure you add one on each invoice line.
|
||||
|
||||
- Error: Fecha/Número Resolucion Invalido RECHAZO- CAF Vencido : (Firma_DTE[AAAA-MM-DD] -
|
||||
CAF[AAAA-MM-DD]) > 6 meses.
|
||||
|
||||
*Hint:* Try to add a new CAF related to this document as the one you’re using is expired.
|
||||
|
||||
|
||||
|
||||
Credit Notes
|
||||
------------
|
||||
|
||||
When a cancellation or correction is needed over a validated invoice, a credit note must be
|
||||
generated. It is important to consider that a CAF file is required for the Credit Note,
|
||||
which is identified as document 64 in the SII.
|
||||
|
||||
.. image:: media/Chile40.png
|
||||
:align: center
|
||||
:alt: Creation of CAF for Credit notes.
|
||||
|
||||
|
||||
.. tip:: Refer to the CAF section where we described the process to load the CAF on each
|
||||
document type.
|
||||
|
||||
Use Cases
|
||||
~~~~~~~~~
|
||||
|
||||
Cancel Referenced document
|
||||
**************************
|
||||
|
||||
In case you need to cancel or invalid an Invoice, use the button Add Credit note and select Full
|
||||
Refund, in this case the SII reference Code is automatically set to: Anula Documento de referencia.
|
||||
|
||||
.. image:: media/Chile26.png
|
||||
:align: center
|
||||
:alt: Full invoice refund with SII reference code 1.
|
||||
|
||||
Corrects Referenced Document Text
|
||||
*********************************
|
||||
|
||||
If a correction in the invoice information is required, for example the Street Name, use the button
|
||||
Add Credit note,select Partial Refund and select the option “Solo corregir Texto”. In this case
|
||||
the SII reference Code is automatically set to: Corrige el monto del Documento de Referencia.
|
||||
|
||||
.. image:: media/Chile27.png
|
||||
:align: center
|
||||
:alt: Partial refund to correct text including the corrected value.
|
||||
|
||||
Odoo creates a Credit Note with the corrected text in an invoice and price 0.
|
||||
|
||||
.. image:: media/Chile28.png
|
||||
:align: center
|
||||
:alt: Credit note with the corrected value on the invoice lines.
|
||||
|
||||
.. important::
|
||||
It’s important to define the default credit account in the Sales journal as it
|
||||
is taken for this use case in specific.
|
||||
|
||||
Corrects Referenced Document Amount
|
||||
***********************************
|
||||
|
||||
When a correction on the amounts is required, use the button Add Credit note
|
||||
and select Partial Refund. In this case the SII reference Code is automatically
|
||||
set to: Corrige el monto del Documento de Referencia.
|
||||
|
||||
.. image:: media/Chile30.png
|
||||
:align: center
|
||||
:alt: Credit note for partial refund to correct amounts, using the SII reference code 3.
|
||||
|
||||
Debit Notes
|
||||
-----------
|
||||
|
||||
As part of the Chilean localization, besides creating credit notes from an existing document you
|
||||
can also create debit Notes. For this just use the button “Add Debit Note”. The two main use
|
||||
cases for debit notes are detailed below.
|
||||
|
||||
Use Cases
|
||||
~~~~~~~~~
|
||||
|
||||
Add debt on Invoices
|
||||
********************
|
||||
|
||||
The most common use case for debit notes is to increase the value of an existing invoice, you
|
||||
need to select option 3 in the field Reference code SII:
|
||||
|
||||
.. image:: media/Chile31.png
|
||||
:align: center
|
||||
:alt: Debit note for partial refund to crrect amounts, using the SII reference code 3.
|
||||
|
||||
|
||||
In this case Odoo automatically includes the source invoice in the cross reference section:
|
||||
|
||||
.. image:: media/Chile32.png
|
||||
:align: center
|
||||
:alt: Invoice data on crossed reference section for debit notes.
|
||||
|
||||
Cancel Credit Notes
|
||||
*******************
|
||||
|
||||
In Chile the debits notes are used to cancel a validated Credit Note, in this case just
|
||||
select the button Add debit note and select the first option in the wizard: *1: Anula
|
||||
Documentos de referencia.*
|
||||
|
||||
.. image:: media/Chile33.png
|
||||
:align: center
|
||||
:alt: Creating a debit note to cancel a credit note with the SII code reference 1.
|
||||
|
||||
|
||||
Vendor Bills
|
||||
------------
|
||||
|
||||
As part of the Chilean localization, you can configure your Incoming email server as the same you
|
||||
have register in the SII in order to:
|
||||
|
||||
- Automatically receive the vendor bills DTE and create the vendor bill based on this information.
|
||||
- Automatically Send the reception acknowledgement to your vendor.
|
||||
- Accept or Claim the document and send this status to your vendor.
|
||||
|
||||
|
||||
Reception
|
||||
~~~~~~~~~
|
||||
|
||||
As soon as the vendor email with the attached DTE is received:
|
||||
1. The vendor Bill mapping all the information included in the xml.
|
||||
2. An email is sent to the vendor with the Reception acknowledgement.
|
||||
3. The DTE status is set as: Acuse de Recibido Enviado
|
||||
|
||||
.. image:: media/Chile34.png
|
||||
:align: center
|
||||
:alt: Messages recorded in the chatter with the reception notification for the vendor.
|
||||
|
||||
Acceptation
|
||||
~~~~~~~~~~~
|
||||
|
||||
If all the commercial information is correct on your vendor bill, you can accept the document using
|
||||
the button: Aceptar Documento, once this is done the DTE Acceptation Status changes to: Accepted and
|
||||
an email of acceptance is sent to the vendor.
|
||||
|
||||
.. image:: media/Chile35.png
|
||||
:align: center
|
||||
:alt: Acceptance button in vendor bills to inform the vendor all the document is comercially accepted.
|
||||
|
||||
|
||||
Claim
|
||||
~~~~~
|
||||
|
||||
In case there is a commercial issue or the information is not correct on your vendor bill, you can
|
||||
Claim the document before validating it, using the button: Claim, once this is done the DTE
|
||||
Acceptation Status change to: Claim and an email of acceptance is sent to the vendor.
|
||||
|
||||
.. image:: media/Chile36.png
|
||||
:align: center
|
||||
:alt: Claim button in vendor bills to inform the vendor all the document is comercially rejected.
|
||||
|
||||
If you claim a vendor bill, the status changes from draft to cancel automatically. Considering this
|
||||
as best practice, all the Claim documents should be canceled as they won’t be valid for your
|
||||
accounting records.
|
||||
|
||||
|
||||
Financial Reports
|
||||
=================
|
||||
|
||||
Balance Tributario de 8 Columnas
|
||||
--------------------------------
|
||||
|
||||
This report presents the accounts in detail (with their respective balances), classifying them
|
||||
according to their origin and determining the level of profit or loss that the business had within
|
||||
the evaluated period of time, so that a real and complete knowledge of the status of a company.
|
||||
|
||||
You can find this report in :menuselection:`Accounting --> Accounting --> Reports`
|
||||
|
||||
.. image:: media/Chile37.png
|
||||
:align: center
|
||||
:alt: Columns and data displayed in the report Balance Tributario 8 Columnas.
|
||||
|
||||
Propuesta F29
|
||||
-------------
|
||||
|
||||
The form F29 is a new system that the SII enabled to taxpayers, and that replaces the Purchase and
|
||||
Sales Books. This report is integrated by Purchase Register (CR) and the Sales Register (RV).
|
||||
Its purpose is to support the transactions related to VAT, improving its control and declaration.
|
||||
|
||||
This record is supplied by the electronic tax documents (DTE’s) that have been received by the
|
||||
SII.
|
||||
|
||||
You can find this report in :menuselection:`Accounting --> Accounting --> Reports`
|
||||
|
||||
.. image:: media/Chile38.png
|
||||
:align: center
|
||||
:alt: Parameters to required to generate the Report Propuesta F29
|
||||
@@ -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.
|
||||
@@ -52,7 +52,7 @@ 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/13.0/setup/enterprise.html>`_
|
||||
`upgrade to Odoo Enterprise <https://www.odoo.com/documentation/14.0/setup/enterprise.html>`_
|
||||
or contact your Odoo service provider.
|
||||
|
||||
In case of non-conformity, your company risks a fine of €7,500.
|
||||
|
||||
@@ -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
|
||||
|
After Width: | Height: | Size: 25 KiB |
|
After Width: | Height: | Size: 38 KiB |
|
After Width: | Height: | Size: 60 KiB |
|
After Width: | Height: | Size: 40 KiB |
|
After Width: | Height: | Size: 15 KiB |
|
After Width: | Height: | Size: 26 KiB |
|
After Width: | Height: | Size: 23 KiB |
|
After Width: | Height: | Size: 55 KiB |
|
After Width: | Height: | Size: 9.1 KiB |
|
After Width: | Height: | Size: 52 KiB |
|
After Width: | Height: | Size: 60 KiB |
|
After Width: | Height: | Size: 16 KiB |
|
After Width: | Height: | Size: 94 KiB |
|
After Width: | Height: | Size: 49 KiB |
|
After Width: | Height: | Size: 27 KiB |
|
After Width: | Height: | Size: 86 KiB |
|
After Width: | Height: | Size: 46 KiB |
|
After Width: | Height: | Size: 105 KiB |
|
After Width: | Height: | Size: 12 KiB |
|
After Width: | Height: | Size: 131 KiB |
|
After Width: | Height: | Size: 178 KiB |
|
After Width: | Height: | Size: 140 KiB |
|
After Width: | Height: | Size: 62 KiB |
|
After Width: | Height: | Size: 64 KiB |
|
After Width: | Height: | Size: 69 KiB |
|
After Width: | Height: | Size: 111 KiB |
|
After Width: | Height: | Size: 38 KiB |
|
After Width: | Height: | Size: 26 KiB |
|
After Width: | Height: | Size: 43 KiB |
|
After Width: | Height: | Size: 65 KiB |
|
After Width: | Height: | Size: 29 KiB |
|
After Width: | Height: | Size: 22 KiB |
|
After Width: | Height: | Size: 57 KiB |
|
After Width: | Height: | Size: 17 KiB |
|
After Width: | Height: | Size: 157 KiB |
|
After Width: | Height: | Size: 83 KiB |
|
After Width: | Height: | Size: 55 KiB |
|
After Width: | Height: | Size: 21 KiB |
|
After Width: | Height: | Size: 4.8 KiB |
|
After Width: | Height: | Size: 28 KiB |
|
After Width: | Height: | Size: 37 KiB |
|
After Width: | Height: | Size: 48 KiB |
|
After Width: | Height: | Size: 31 KiB |
|
After Width: | Height: | Size: 25 KiB |
|
After Width: | Height: | Size: 19 KiB |
|
After Width: | Height: | Size: 75 KiB |
|
After Width: | Height: | Size: 25 KiB |
|
After Width: | Height: | Size: 43 KiB |
|
After Width: | Height: | Size: 70 KiB |
|
After Width: | Height: | Size: 67 KiB |
|
After Width: | Height: | Size: 43 KiB |
|
After Width: | Height: | Size: 59 KiB |
|
After Width: | Height: | Size: 71 KiB |
|
After Width: | Height: | Size: 112 KiB |
|
After Width: | Height: | Size: 53 KiB |
|
After Width: | Height: | Size: 60 KiB |
|
After Width: | Height: | Size: 52 KiB |
|
After Width: | Height: | Size: 8.8 KiB |
|
After Width: | Height: | Size: 95 KiB |
|
After Width: | Height: | Size: 94 KiB |
|
After Width: | Height: | Size: 23 KiB |
|
After Width: | Height: | Size: 9.5 KiB |
|
After Width: | Height: | Size: 23 KiB |
|
After Width: | Height: | Size: 18 KiB |
|
After Width: | Height: | Size: 27 KiB |
|
After Width: | Height: | Size: 25 KiB |
|
After Width: | Height: | Size: 7.3 KiB |
|
After Width: | Height: | Size: 9.8 KiB |
@@ -69,8 +69,8 @@ integrate with the normal invoicing flow in Odoo.
|
||||
.. _mx-legal-info:
|
||||
|
||||
|
||||
Set you legal information in the company
|
||||
----------------------------------------
|
||||
Set your legal information in the company
|
||||
-----------------------------------------
|
||||
|
||||
First, make sure that your company is configured with the correct data.
|
||||
Go in :menuselection:`Settings --> Users --> Companies`
|
||||
@@ -81,7 +81,7 @@ 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 **TCM970625MB1**.
|
||||
set the vat to **EKU9003173C9**.
|
||||
|
||||
.. image:: media/mexico03.png
|
||||
:align: center
|
||||
|
||||
@@ -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
|
||||
=========================
|
||||
|
||||
|
||||