This module extends the functionality of account_move_base_import, in order to handle the file format used for Monetico card remitance
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets you import Monetico credit card payment files (.csv) as journal entries in Odoo, using the bank statement import framework. You select the Monetico format on a journal and upload the file.
This module adds a new import format for bank/journal imports, specifically for Monetico credit card remittance files in .csv format.
Where it appears: - On the journal configuration screen (Accounting), the import type field gains a new choice: "Monetico Credit Card .csv".
What it does: - When you import a Monetico .csv file on a journal configured with that format, the module reads the file using a dedicated parser. The file is expected to be semicolon-separated with a fixed set of columns (payment collection date, terminal number, payment reference, payment status, amount, currency, card type, etc.). - Each imported line becomes a journal item: the payment reference is used as the label, and the amount is placed on the credit side if positive or the debit side if negative. - Only lines whose payment status is "PA" (paid) are kept; other lines are discarded. - The journal entry date is set to the latest payment collection date found in the file.
It relies on the account_move_base_import module for the general import mechanism and only extends the account.journal model to add the new format option.
Depends on
Models and fields (1)
- account.journal · extends an existing modelimport_type
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/l10n-france.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.