Skip to main content

Belgium - Import Bank CODA Statements

Project description

Supported are CODA flat files in V2 format from Belgian bank accounts.

  • CODA v1 support.
  • CODA v2.2 support.
  • Foreign Currency support.
  • Support for all data record types (0, 1, 2, 3, 4, 8, 9).
  • Parsing & logging of all Transaction Codes and Structured Format Communications.
  • Automatic Financial Journal assignment via CODA configuration parameters.
  • Support for multiple Journals per Bank Account Number.
  • Support for multiple statements from different bank accounts in a single CODA file.
  • Support for ‘parsing only’ CODA Bank Accounts (defined as type=’info’ in the CODA Bank Account configuration records).
  • Multi-language CODA parsing, parsing configuration data provided for EN, NL, FR.

The machine readable CODA Files are parsed and stored in human readable format in CODA Bank Statements. Also Bank Statements are generated containing a subset of the CODA information (only those transaction lines that are required for the creation of the Financial Accounting records). The CODA Bank Statement is a ‘read-only’ object, hence remaining a reliable representation of the original CODA file whereas the Bank Statement will get modified as required by accounting business processes.

CODA Bank Accounts configured as type ‘Info’ will only generate CODA Bank Statements.

A removal of one object in the CODA processing results in the removal of the associated objects. The removal of a CODA File containing multiple Bank Statements will also remove those associated statements.

The following reconciliation logic has been implemented in the CODA processing:

  1. 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 bank accounts defined in 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.
  2. As a second 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).
  3. When the previous step doesn’t find a match, the transaction counterparty is located via the Bank Account Number configured on the OpenERP Customer and Supplier records.
  4. In case the previous steps are not successful, the transaction is generated by using the ‘Default Account for Unrecognized Movement’ field of the CODA File Import wizard in order to allow further manual processing.

In stead of a manual adjustment of the generated Bank Statements, you can also re-import the CODA after updating the OpenERP database with the information that was missing to allow automatic reconciliation.

Remark on CODA V1 support:

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.2 specifications. If required, you can manually adjust the descriptions via the CODA configuration menu.

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

openerp-l10n-be-coda-7.0.406.tar.gz (732.9 kB view hashes)

Uploaded source

Supported by

AWS AWS Cloud computing Datadog Datadog Monitoring Facebook / Instagram Facebook / Instagram PSF Sponsor Fastly Fastly CDN Google Google Object Storage and Download Analytics Huawei Huawei PSF Sponsor Microsoft Microsoft PSF Sponsor NVIDIA NVIDIA PSF Sponsor Pingdom Pingdom Monitoring Salesforce Salesforce PSF Sponsor Sentry Sentry Error logging StatusPage StatusPage Status page