+#: model:ir.module.module,description:base.module_account_coda
+msgid "\n"
+" Module to import CODA bank statements.\n"
+"\n"
+" Supported are CODA flat files in V2 format from Belgian bank accounts.\n"
+" - CODA v1 support.\n"
+" - CODA v2.2 support.\n"
+" - Foreign Currency support.\n"
+" - Support for all data record types (0, 1, 2, 3, 4, 8, 9).\n"
+" - Parsing & logging of all Transaction Codes and Structured Format Communications.\n"
+" - Automatic Financial Journal assignment via CODA configuration parameters.\n"
+" - Support for multiple Journals per Bank Account Number.\n"
+" - Support for multiple statements from different bank accounts in a single CODA file.\n"
+" - Support for 'parsing only' CODA Bank Accounts (defined as type='info' in the CODA Bank Account configuration records).\n"
+" - Multi-language CODA parsing, parsing configuration data provided for EN, NL, FR.\n"
+"\n"
+" The machine readable CODA Files are parsed and stored in human readable format in CODA Bank Statements.\n"
+" Also Bank Statements are generated containing a subset of the CODA information (only those transaction lines\n"
+" that are required for the creation of the Financial Accounting records).\n"
+" The CODA Bank Statement is a 'read-only' object, hence remaining a reliable representation of the original CODA file\n"
+" whereas the Bank Statement will get modified as required by accounting business processes.\n"
+"\n"
+" CODA Bank Accounts configured as type 'Info' will only generate CODA Bank Statements.\n"
+"\n"
+" A removal of one object in the CODA processing results in the removal of the associated objects.\n"
+" The removal of a CODA File containing multiple Bank Statements will also remove those associated\n"
+" statements.\n"
+"\n"
+" The following reconciliation logic has been implemented in the CODA processing:\n"
+" 1) The Company's Bank Account Number of the CODA statement is compared against the Bank Account Number field\n"
+" of the Company's CODA Bank Account configuration records (whereby bank accounts defined in type='info' configuration records are ignored).\n"
+" If this is the case an 'internal transfer' transaction is generated using the 'Internal Transfer Account' field of the CODA File Import wizard.\n"
+" 2) As a second step the 'Structured Communication' field of the CODA transaction line is matched against\n"
+" the reference field of in- and outgoing invoices (supported : Belgian Structured Communication Type).\n"
+" 3) When the previous step doesn't find a match, the transaction counterparty is located via the\n"
+" Bank Account Number configured on the OpenERP Customer and Supplier records.\n"
+" 4) In case the previous steps are not successful, the transaction is generated by using the 'Default Account\n"
+" for Unrecognized Movement' field of the CODA File Import wizard in order to allow further manual processing.\n"
+"\n"
+" In stead of a manual adjustment of the generated Bank Statements, you can also re-import the CODA\n"
+" after updating the OpenERP database with the information that was missing to allow automatic reconciliation.\n"
+"\n"
+" Remark on CODA V1 support:\n"
+" In some cases a transaction code, transaction category or structured communication code has been given a new or clearer description in CODA V2.\n"
+" The description provided by the CODA configuration tables is based upon the CODA V2.2 specifications.\n"
+" If required, you can manually adjust the descriptions via the CODA configuration menu.\n"
+"\n"
+" "
projects / odoo / odoo.git / blobdiff