Check printing basic features
This module offers the basic functionalities to make payments by printing checks.
It must be used as a dependency for modules that provide country-specific check templates.
The check settings are located in the accounting journals configuration page.

Batch Payments
=======================================
Batch payments allow grouping payments.

They are used namely, but not only, to group several cheques before depositing them in a single batch to the bank.
The total amount deposited will then appear as a single transaction on your bank statement.
When you reconcile, simply select the corresponding batch payment to reconcile all the payments in the batch.

Module to import QIF bank statements.
======================================

This module allows you to import the machine readable QIF Files in CBMS ODOO: they are parsed and stored in human readable format in
Accounting Bank and Cash Bank Statements.

Important Note
---------------------------------------------
Because of the QIF format limitation, we cannot ensure the same transactions aren't imported several times or handle multicurrency.
Whenever possible, you should use a more appropriate file format like OFX.

Module to import OFX bank statements.
======================================

This module allows you to import the machine readable OFX Files in CBMS ODOO: they are parsed and stored in human readable format in
Accounting Bank and Cash Bank Statements.

Bank Statements may be generated containing a subset of the OFX information (only those transaction lines that are required for the
creation of the Financial Accounting records).

Module to import CSV bank statements.
======================================

This module allows you to import CSV Files in CBMS ODOO: they are parsed and stored in human readable format in
Accounting Bank and Cash Bank Statements.

Important Note
---------------------------------------------
Because of the CSV format limitation, we cannot ensure the same transactions aren't imported several times or handle multicurrency.
Whenever possible, you should use a more appropriate file format like OFX.

Module to import CAMT bank statements.
======================================

Improve the import of bank statement feature to support the SEPA recommended Cash Management format (CAMT.053).

<p> Generic Wizard to Import Bank Statements.</p>
<p>(This module does not include any type of import format.)</p>
<p>OFX and QIF imports are available in Enterprise version.</p>

<p>
Account Automatic Transfers<br>
===========================<br>
Manage automatic transfers between your accounts.</p>

Manage assets with fleets

Check printing enterprise addons
This module adds the possibility to filter by check number in the reconciliation
widget.

Manage 3-way matching on vendor bills
=====================================

In the manufacturing industry, people often receive the vendor bills before
receiving their purchase, but they don't want to pay the bill until the goods
have been delivered.

The solution to this situation is to create the vendor bill when you get it
(based on ordered quantities) but only pay the invoice when the received
quantities (on the PO lines) match the recorded vendor bill.

This module introduces a "release to pay" mechanism that marks for each vendor
bill whether it can be paid or not.

Each vendor bill receives one of the following three states:

- Yes (The bill can be paid)
- No (The bill cannot be paid, nothing has been delivered yet)
- Exception (Received and invoiced quantities differ)

Purchase Orders, Receipts, Vendor Bills for Stock

Landed Costs
Landed Costs Management
=======================
This module allows you to easily add extra costs on pickings and decide the split of these costs among their stock moves in order to take them into account in your stock valuation.

Functional
----------

Be able to create journals in CBMS ODOO to create electronic customer invoices and report then to AFIP (via webservices).
The options available are:

* Electronic Invoice - Web Service
* Export Voucher - Web Service
* Electronic Fiscal Bond - Web Service

In the electronic journals if you validate an invoice this one will be validated in both CBMS ODOO and AFIP. This validation is
made at the instant and we recieve and "approved/approved with observation/rejected" state from AFIP. If the invoice has
been rejected by AFIP will not be post in the system and a pop up message will be shown with both the error detail (reject reasons)
we recieve and a HINT about what the problem could be.

For auditing and troubleshooting purposes we also add a menu "Consulit Invoice in AFIP" that let us to consult invoices previously
sent to AFIP and last number used as support for any possible issues on the sequences synchronization between CBMS ODOO and AFIP.

NOTE: From the Journal's form view we are able to force a sync between the CBMS ODOO sequences to each of the document types in
with the last numbers registered in AFIP.

From vendor bills, we have added a functionality that can be configured in the accounting settings to be able to verify
vendor bills in AFIP to check if the vendor bills are real (more information please review the setting description).

Configuration:

1. Go to the Accounting Settings > Argentinean Localization section

1.1. Configure the AFIP Web Services mode:

* Testing environment in order to use demo certificates that will be use to test the instance and to make NOT
real invoices to AFIP. is just for testing. For demo instaces is already pre-defined you will not need to configure
it (commonly named in AFIP as Homologation environment).
* Production environment in order to generate real certificates and legal invoices to AFIP,

1.2. Configure your AFIP Certificate: If you are in a demo instance this one will be have been set by default. If you
are in production instance just need to go to upload your AFIP Certificate

1.3. Optionally you can define if you like to be eable to verify vendor bills in AFIP.

2. Create Sales journals that will represent each one of your AFIP POS (Available in AFIP Portal) you want to use in CBMS ODOO.

2.1. Use Documents field is set by default please dont change
2.2. Set AFIP POS System for one of the electronic ones.

* Electronic Invoice - Web Service'
* Electronic Fiscal Bond - Web Service'
* Export Voucher - Web Service'

2.3. Set the AFIP POS Number and AFIP POS Address taking into account what you have configured in your AFIP Portal.

NOTE: You can use the "Check Available AFIP POS" button in Journal's form to corroborate the to use to create the journals.

For more information about Argentinean Electronic invoicing please go to http://www.afip.gob.ar/fe/ayuda.asp

Technical
---------

The web services that are implemented are the ones that are the most common:

* wsfev1 - "Factura Electrónica" (Electronic Invoice)
* wsbfev1 - "Bono Fiscal Electrónico" (Electronic Fiscal Bond)
* wsfexv1 - "Factura de Exportación Electrónica" (Electronic Exportation Invoice - same as Export Voucher)
* wscdc - "Constatación de Comprobantes" (Invoices Verification)

For Development information go to http://www.afip.gob.ar/fe/documentos/WSBFEv1 - Manual para el desarrollador.pdf

The delivery guide (guia de despacho) is needed as a proof
that you are sending goods between A and B.

It is configurable on the partner if prices are needed on the
delivery guide and if they need to come from the sale order
or the product itself.

It is only when a delivery order is validated that you can create the delivery
guide. Then it will follow the same flow as for the invoices, sending it to
the SII.

Purpose of the Module:
======================

As part of the SII requirements (Legal requirement in Chile),
beginning on March 2021 boletas transactions must be sent to the SII under the
electronic workflow using a different web service than the one used for electronic Invoices.
Previously, there was no need to send the boletas to the SII, just a daily report.

Additionally of sending the Boleta individually (with the EDI workflow),
at the end of the day, a daily summary with all the Boletas transactions
should be sent to the SII - electronically (also a legal requirement).
This is called "Libro de ventas diarias" (former "reporte de consumo de folios" or RCOF).


Differences between Electronic boletas vs Electronic Invoicing Workflows:
=========================================================================

These workflows have some important differences that lead us to do this PR with the specific changes.
Here are the differences:

* The mechanism for sending the electronic boletas information needs dedicated servers, different from those used at the reception electronic invoice ("Palena" for the production environment - palena.sii.cl and "Maullin" for the test environment - maullin.sii.cl).
* The authentication services, querying the status of a delivery and the status of a document will be different.
* The authentication token obtained
* The XML schema for sending the electronic boletas was updated with the incorporation of new tags
* The validation diagnosis of electronic boletas will be delivered through a "REST" web service that has as an input the track-id of the delivery. Electronic Invoices will continue to receive their diagnoses via e-mail.
* The track-id ("identificador de envío") associated with the electronic boletas will be 15 digits long. (Electronics Invoice is 10)

Highlights from this SII Guide:
https://www.sii.cl/factura_electronica/factura_mercado/Instructivo_Emision_Boleta_Elect.pdf