[IMP] finance/accounting: add Delivery Guide to CL localization

closes odoo/documentation#2647

X-original-commit: a6f2c55896
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>

content/applications/finance/accounting/fiscal_localizations/localizations/chile.rst

@@ -17,13 +17,13 @@ The Chilean localization has been improved and extended in Odoo v13. In this ver
 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.
+  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). 
+- **l10n_cl_reports:** Adds the reports Propuesta F29 y Balance Tributario (8 columnas).
 
 Configuration
 =============
@@ -100,8 +100,8 @@ crucial to define the DTE incoming email server, considering this configuration:
 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. 
+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:: chile/Chile03_3.png
    :align: center
@@ -112,13 +112,13 @@ is required, proceed to this section and load your file and password.
    :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
+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.
 
 .. note::
    In some cases, depending on the certificate format, it is possible that the field Subject Serial
    Number is not loaded automatically. If this is the case, you can manually edit this field by
-   filling it with the Certificate’s legal representative RUT.
+   filling it with the Certificate's legal representative RUT.
 
 Financial Reports
 ~~~~~~~~~~~~~~~~~
@@ -134,8 +134,8 @@ Multicurrency
 ~~~~~~~~~~~~~
 
 The official currency rate in Chile is provided by the Chilean service `mindicador.cl
-<https://mindicador.cl>`_. You can find this service in the currency rate configuration, and you can
-set a predefined interval for the rate updates.
+<https://mindicador.cl>`_. You can find this service in the currency rate configuration, and you
+can set a predefined interval for the rate updates.
 
 .. image:: chile/Chile05_2.png
    :align: center
@@ -230,7 +230,7 @@ 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,
+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.
 
@@ -296,9 +296,8 @@ Online must be selected. Otherwise, if the journal is used for invoices imported
 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. 
+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:: chile/Chile41.png
    :align: center
@@ -308,6 +307,8 @@ use documents.
    For the Chilean localization, it is important to define the default Debit and Credit accounts
    as they are required for one of the debit notes use cases.
 
+.. _chile/caf-documentation:
+
 CAF
 ---
 
@@ -319,8 +320,8 @@ Your company can make several requests for folios and obtain several CAFs, each
 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>`_.
+Please refer to the `SII documentation <https://palena.sii.cl/dte/mn_timbraje.html>`_ to check the
+detail on how to acquire the CAF.
 
 .. important::
    The CAFs required by the SII are different from Production to Test (Certification mode). Make
@@ -356,9 +357,9 @@ 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. 
+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:: chile/Chile14.png
    :align: center
@@ -368,8 +369,8 @@ the information transmitted to the SII and between the customers and Vendors.
 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
+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.
@@ -382,11 +383,13 @@ You can manually change the document type if needed.
    Documents type 33: Electronic Invoice must have at least one item with tax, otherwise the SII
    rejects the document validation.
 
+.. _chile/electronic-invoice-validation:
+
 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:
+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.
@@ -418,9 +421,9 @@ The DTE status workflow is as follows:
       :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:
+   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:: chile/Chile18_2.png
       :align: center
@@ -428,22 +431,21 @@ The DTE status workflow is as follows:
 
 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. 
+   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.
+   **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:: chile/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.
+   **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:
 
@@ -461,8 +463,8 @@ 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:
+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:: chile/Chile21.png
    :align: center
@@ -501,9 +503,9 @@ Once the invoice has been sent to 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. 
+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 :ref:`chile/credit-notes` section for more details.
 
 .. image:: chile/Chile24.png
    :align: center
@@ -530,7 +532,7 @@ you might have and which is the related solution.
 - Error: ``Fecha/Número Resolucion Invalido RECHAZO- CAF Vencido : (Firma_DTE[AAAA-MM-DD] -
   CAF[AAAA-MM-DD]) &gt; 6 meses.``
 
-  *Hint:* Try to add a new CAF related to this document as the one you’re using is expired.
+  *Hint:* Try to add a new CAF related to this document as the one you're using is expired.
 
 - Error: ``Element '{http://www.sii.cl/SiiDte%7DRutReceptor': This element is not expected. Expected
   is ( {http://www.sii.cl/SiiDte%7DRutEnvia ).``
@@ -543,10 +545,10 @@ you might have and which is the related solution.
   *Hint:* This error indicates that most likely, your company has not passed the `Certification
   process <https://www.sii.cl/factura_electronica/factura_mercado/proceso_certificacion.htm>`_ in
   the SII - Sistema de Facturación de Mercado. If this is the case, please contact your Account
-  Manager or Customer Support as this certification is not part of the the Odoo services,
-  but we can give you some alternatives.
-
+  Manager or Customer Support as this certification is not part of the the Odoo services, but we
+  can give you some alternatives.
 
+.. _chile/credit-notes:
 
 Credit Notes
 ------------
@@ -560,8 +562,9 @@ which is identified as document 64 in the SII.
    :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.
+.. tip::
+   Refer to the :ref:`CAF section <chile/caf-documentation>` where we described the process to load
+   the CAF on each document type.
 
 Use Cases
 ~~~~~~~~~
@@ -569,7 +572,7 @@ Use Cases
 Cancel Referenced document
 **************************
 
-In case you need  to cancel or invalid an Invoice, use the button Add Credit note and select Full
+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:: chile/Chile26.png
@@ -594,15 +597,15 @@ Odoo creates a Credit Note with the corrected text in an invoice and price 0.
    :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
+   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.
+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:: chile/Chile30.png
    :align: center
@@ -612,8 +615,8 @@ 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. 
+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
 ~~~~~~~~~
@@ -646,7 +649,6 @@ Documentos de referencia.*
    :align: center
    :alt: Creating a debit note to cancel a credit note with the SII code reference 1.
 
-
 Vendor Bills
 ------------
 
@@ -657,14 +659,13 @@ have register in the SII in order to:
 - 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
+3. The DTE status is set as: Acuse de Recibido Enviado
 
 .. image:: chile/Chile34.png
    :align: center
@@ -673,30 +674,198 @@ As soon as the vendor email with the attached DTE is received:
 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. 
+If all the commercial information is correct on your vendor bill then you can accept the document
+using the :guilabel:`Aceptar Documento` button. Once this is done the DTE Acceptation Status
+changes to :guilabel:`Accepted`` and an email of acceptance is sent to the vendor.
 
 .. image:: chile/Chile35.png
    :align: center
-   :alt: Acceptance button in vendor bills to inform the vendor all the document is comercially accepted.
-   
+   :alt: Acceptance button in vendor bills to inform vendor 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. 
+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:: chile/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
+as best practice, all the Claim documents should be canceled as they won't be valid for your
 accounting records.
 
+Delivery Guide
+--------------
+
+To install the Delivery Guide module, go to :menuselection:`Apps` and search for :guilabel:`Chile
+(l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile - E-Invoicing Delivery
+Guide`.
+
+.. note::
+   *Chile - E-Invoicing Delivery Guide* has a dependency with *Chile - Facturación Electrónica*.
+   Odoo will install the dependency automatically when the Delivery Guide module is installed.
+
+The Delivery Guide module includes sending the DTE to SII and the stamp in PDF reports for
+deliveries.
+
+.. image:: chile/chile42.png
+   :align: center
+   :alt: Install Delivery Guide Module
+
+Once all configurations have been made for electronic invoices (e.g., uploading a valid company
+certificate, setting up master data, etc.), Delivery Guides need their own CAFs. Please refer to the
+:ref:`CAF documentation <chile/caf-documentation>` to check the details on how to acquire the CAFs
+for electronic Delivery Guides.
+
+Verify the following important information in the *Price for the Delivery Guide* configuration:
+
+- :guilabel:`From Sales Order`: Delivery Guide takes the product price from the Sales Order and
+  shows it on the document.
+- :guilabel:`From Product Template`: Odoo takes the price configured in the product template and
+  shows it on the document.
+- :guilabel:`No show price`: no price is shown in the Delivery Guide.
+
+Electronic delivery guides are used to move stock from one place to another and they can represent
+sales, sampling, consignment, internal transfers, and basically any product move.
+
+Delivery Guide from a Sales Process
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When a Sales Order is created and confirmed, a Delivery Order is generated. After validating the
+Delivery Order, the option to create a Delivery Guide is activated.
+
+.. image:: chile/chile43.png
+   :align: center
+   :alt: Create Delivery Guide Button
+
+When clicking on :guilabel:`Create Delivery Guide` for the first time, a warning message pops up,
+showing the following:
+
+.. image:: chile/chile44.png
+   :align: center
+   :alt: An example sequence error when creating a Delivery Guide in Odoo
+
+This warning message means the user needs to indicate the next sequence number Odoo has to take to
+generate the Delivery Guide, and only only happens the *first time* a Delivery Guide is created in
+Odoo. After the first document has been correctly generated, Odoo takes the CAFs next available
+number to generate the following Delivery Guide and so on.
+
+After the Delivery Guide is created:
+
+- The DTE file (Electronic Tax Document) is automatically created and added to the chatter.
+- The DTE SII status is set as: Pending to be sent.
+
+.. image:: chile/chile45.png
+   :align: center
+   :alt: DTE Status in SII and creation of DTE/XML
+
+The DTE Status is automatically updated by Odoo with a scheduled action that runs every day at
+night. To get a response from the SII immediately, press the :guilabel:`Send now to SII` button.
+
+Once the Delivery Guide is sent, it may then be printed by clicking on the :guilabel:`Print
+Delivery Guide` button.
+
+.. image:: chile/chile46.png
+   :align: center
+   :alt: Printing Delivery Guide PDF
+
+Electronic Receipt
+------------------
+
+To install the Electronic Receipt module, go to :menuselection:`Apps` and search for
+:guilabel:`Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile -
+Electronic Receipt`.
+
+.. note::
+   *Chile - Electronic Receipt* has a dependency with *Chile - Facturación Electrónica*. Odoo will
+   install the dependency automatically when the E-invoicing Delivery Guide module is installed.
+
+This module contains the electronic receipt and daily sales report, which are automatically sent to
+SII.
+
+.. image:: chile/chile47.png
+   :align: center
+   :alt: Install Electronic Receipt module
+
+Once all configurations have been made for Electronic Invoices (e.g., uploading a valid company
+certificate, setting up master data, etc.), Electronic Receipts need their own CAFs. Please refer
+to the :ref:`CAF documentation <chile/caf-documentation>` to check the details on how to acquire the
+CAFs for Electronic Receipts.
+
+Electronic Receipts are useful when clients do not need an Electronic Invoice. By default, there is
+a partner in the database called *Anonymous Final Consumer* with a generic RUT 66666666-6 and
+taxpayer type of *Final Consumer*. This partner can be used for Electronic Receipts or a new record
+may be created for the same purpose.
+
+Although Electronic Receipts should be used for final consumers with a generic RUT, it can also be
+used for specific partners. After the partners and journals are created and configured, the
+Electronic Receipts are created in the standard way as Electronic Invoice, but the type of document
+:guilabel:`(39) Electronic Receipt` should be selected, like so:
+
+.. image:: chile/chile48.png
+   :align: center
+   :alt: Select type of Document: (39) Boleta Electrónica
+
+Validation and DTE Status
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When all of the Electronic Receipt information is filled, either manually or automatically from a
+Sales Order, proceed to validate the receipt. By default, Electronic Invoice is selected as the
+Document Type, however in order to validate the receipt correctly, make sure to edit the Document
+Type and change to Electronic Receipt.
+
+After the receipt is posted:
+
+- The DTE file (Electronic Tax Document) is created automatically and added to the chatter.
+- The DTE SII status is set as: Pending to be sent.
+
+.. image:: chile/chile49.png
+   :align: center
+   :alt: DTE status in SII and creation of DTE/XML
+
+The DTE Status is automatically updated by Odoo with a scheduled action that runs every day at
+night. To get a response from the SII immediately, press the :guilabel:`Send now to SII` button.
+
+Please refer to the :ref:`DTE Workflow <chile/electronic-invoice-validation>` for Electronic
+Invoices as the workflow for Electronic Receipt follows the same process.
+
+Daily Sales Report
+~~~~~~~~~~~~~~~~~~
+
+Once Electronic Receipts have been created, the system creates a daily sales report containing all
+Electronic Receipts per day. This report is electronically stamped and sent to the SII overnight in
+XML format. These daily reports can be found in :menuselection:`Reports --> Daily Sales Reports`.
+
+.. image:: chile/chile50.png
+   :align: center
+   :alt: Find Electronic Receipts in the Reports menu, under Daily Sales Reports
+
+A list of daily reports is displayed with all daily DTE sent to SII.
+
+.. image:: chile/chile51.png
+   :align: center
+   :alt: List of Daily Reports
+
+If no Electronic Receipt was made on a particular day, the report is sent but it will not have any
+receipts in it. The report will also have an answer from the SII if it was accepted or rejected
+(depending on the company's certificate and validated receipts).
+
+.. image:: chile/chile52.png
+   :align: center
+   :alt: Daily Sales Book example
+
+.. important::
+   For Chilean localization, note that the feature tax included in the price is *not* supported for
+   the Electronic Receipt.
+
+   If a Daily Sales Report has already been created for a specific day in another system, the daily
+   report in Odoo will be rejected due to the sequence number used. If that is the case, the user
+   has to manually click on :guilabel:`Retry` in order for a new sequence number to be generated
+   (this action is automatically done by Odoo). Afterwards, users can manually verify report status
+   with SII or wait for Odoo to update status later at night.
 
 Financial Reports
 =================
@@ -721,7 +890,7 @@ The form F29 is a new system that the SII enabled to taxpayers, and that replace
 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
+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`