<a class="reference external image-reference" href="https://www.gnu.org/licenses/agpl"><img alt="License: AGPL-3" src="https://img.shields.io/badge/license-AGPL--3-blue.png" /></a> <a name="module-to-import-coda-bank-statements"></a> <h2>Module to import CODA bank statements</h2> <a name="features"></a> <h3>Features</h3> <blockquote> <ul class="simple"> <li>CODA v1 support.</li> <li>CODA v2.x support.</li> <li>Foreign Currency support.</li> <li>Support for all data record types (0, 1, 2, 3, 4, 8, 9).</li> <li>Parsing &amp; logging of all Transaction Codes and Structured Format Communications.</li> <li>Automatic Financial Journal assignment via CODA configuration parameters.</li> <li>Support for multiple Journals per Bank Account Number.</li> <li>Support for multiple statements from different bank accounts in a single CODA file.</li> <li>Multi-language CODA parsing, parsing configuration data provided for EN, NL, FR.</li> <li>Support for 'globalisation' of transactions (performed by the customer or the bank). A globalised transaction is presented in the bank statement with its global level (or levels) showing the total amount. Also the individual transactions are available for further bank statement processing.</li> <li>All information supplied in the CODA file is presented in the bank statement. This includes also non-transactional data such as 'free communication' supplied by the bank via the CODA File. Transaction specific information can be found in the 'Notes' field of the transaction. Generic communication is available via the 'CODA Notes' field of the Bank Statement.</li> <li>Support for zip files containing multiple CODA files</li> </ul> </blockquote> <a name="reconciliation-logic"></a> <h3>Reconciliation logic</h3> <blockquote> <ol class="arabic simple"> <li>The Company's Bank Account Number of the CODA statement is compared against the Bank Account Number field of the Company's CODA Bank Account configuration records (whereby CODA Bank Accounts defined as type='info' configuration records are ignored). If this is the case an 'internal transfer' transaction is generated using the Internal Transfer Account' field of the CODA File Import wizard.</li> <li>Outgoing payments are matched with the corresponding invoice/refund via the SEPA EndToEndReference field (requires <strong>l10n_be_coda_pain</strong> module).</li> <li>As a next step the 'Structured Communication' field of the CODA transaction line is matched against the reference field of in- and outgoing invoices (supported: Belgian Structured Communication Type). In case of such a match, the transaction will be reconciled automatically (full or partial).</li> <li>When a 'Free Format Communication' is used, a lookup is performed on outstanding invoices. Reconciliation will take place when all of the following conditions are met:<ul> <li>exact match of transaction amount</li> <li>invoice/refund number (case insensitive) or structured communication is present within the Free Format Communication string (substring match).</li> </ul> </li> <li>If the Sale Order number is found in the 'Free Format Communication' the matching will be performed with the Sale Order Invoices (requires <strong>account_coda_sale</strong> module).</li> <li>If no matching accounting entry is found via the originating business transactions (Payment Order, Invoice, Sales Order) a lookup is performed directly on the accounting entries. Reconciliation will take place when all of the following conditions are met:<ul> <li>exact match of transaction amount</li> <li>the payment communication needs to be a subset of the accounting entry 'name' field</li> </ul> </li> <li>When the previous steps do not result in a match, the transaction counterparty is located via the Bank Account Number configured on the OpenERP Customer and Supplier records.</li> <li>Partner records are updated automatically with the partner's bank account information supplied in the CODA file.</li> <li>After the previous steps, the Account Mapping Rules engine determines the general account to assign for the transaction. Also the required action is defined such as the automatic creation of accounting moves with resulting account and tax case.</li> </ol> </blockquote> <a name="coda-v1-support"></a> <h3>CODA v1 support</h3> <p>In some cases a transaction code, transaction category or structured communication code has been given a new or clearer description in CODA v2. The description provided by the CODA configuration tables is based upon the CODA v2 specifications. If required, you can manually adjust the descriptions via the CODA configuration menu.</p> <a name="installation-instructions"></a> <h3>Installation instructions</h3> <blockquote> <ol class="arabic"> <li><p class="first">This module is <strong>NOT</strong> compatible with the <strong>l10n_be_coda</strong> module.</p> </li> <li><p class="first">We recommend to run this module in combination with the following Noviat modules:</p> <ul class="simple"> <li>l10n_be_coda_pain</li> <li>l10n_be_coda_sale</li> </ul> <p>You can download these from the apps.odoo.com.</p> </li> </ol> </blockquote> <a name="assistance"></a> <h3>Assistance</h3> <p>Contact <a class="reference external" href="mailto:info&#64;noviat.com">info&#64;noviat.com</a> for help with the implementation of Advanced CODA processing in Odoo.</p>