Search 1.9 billion lines of Odoo code on GitHub

l10n_be_invoice_bba_customer_supplier

Author: Noviat
License: AGPL-3
Branch: 12-add-accounting-modules
Repository: brain-tec/noviat-apps
Dependencies: account, and account_supplier_invoice_number
Languages: Python (288, 80.7%), XML (41, 11.5%), and reStructuredText (28, 7.8%)
Other repositories: luc-demeyer/noviat-apps, suningwz/noviat-apps, and van-orsouw-consultancy/noviat-apps

<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="customer-and-supplier-invoices-with-belgian-structured-communication"></a> <h2>Customer and Supplier invoices with Belgian structured communication</h2> <p>This module is an alternative to the 'l10n_be_invoice_bba' module of the standard addons.</p> <p>Difference with this module:</p> <ul> <li><p class="first">Support for Customer and Supplier invoices with digits check.</p> </li> <li><p class="first">Payment reference type</p> <p>On an invoice the 'reference_type' field can be set to 'bba' to enforce the use of the Belgian structured communication.</p> <p>By doing so automated processing of bank statements and outgoing payments can be optimised for performance, matching and transaction integrity.</p> </li> <li><p class="first">Configurable per partner</p> <p>The communication type and algorithm can be configured on the partner records thereby allowing to use other payment references for e.g. foreign customers or customise the payment reference for different customer segments.</p> </li> <li><p class="first">Localisation module</p> <p>This module has no dependancy on a localisation module (no dependancy on 'l10n_be') and hence can be installed with other localisation modules.</p> </li> <li><p class="first">Customisation capabilities</p> <p>The code has been designed to facilitate customisation by IT specialists with Odoo programming skills, e.g. to avoid duplicate structured communications (on customer invoices, sale orders, ...) or to use your own algorithm.</p> </li> </ul> <a name="known-issues-roadmap"></a> <h3>Known issues / Roadmap</h3> <ul class="simple"> <li>Move to 'reference_type' field to a generic module to be used as a building block for Belgian as well as other (e.g. ISO 11649) structured communication type.</li> <li>Add migration script to migrate the reference type fields used for this purpose in previous versions</li> </ul>