Bulk import journal entries, validated before they ever hit the ledger.
Upload CSV, Excel or DATEV files, catch every error on a row-level report before anything posts, and roll back an entire batch in one click if something goes wrong.
Finance teams import journal entries from banks, sub-ledgers and legacy systems using spreadsheet macros and one-off scripts. A single bad row — a mistyped account code, an unbalanced entry, a missing partner — can silently corrupt the ledger, and there is no safe way to undo a bad batch once it has already been posted.
Import Journal Entries validates the whole file up front, flags every row that fails an account, balance or reference check with a plain-English message, and only posts once you are satisfied. Each import is tracked as its own batch, so a bad run can be rolled back with a single click.
Everything a bulk journal import needs
Every capability below is implemented in the module.
CSV, Excel & DATEV
Upload plain CSV, Excel workbooks or DATEV EXTF exports. Common column headers — Soll/Haben, Buchungsdatum, Konto and more — are recognized automatically.
Full-file validation
Every row is parsed and checked before anything touches the ledger: missing accounts, unbalanced entries, invalid dates and unmatched partners are all caught up front.
Row-level error report
A colour-coded report lists every row with its status — OK, Warning or Error — alongside a human-readable message and the exact row number to fix.
Create or update entries
Choose to create brand-new journal entries or update existing ones, matched by reference or entry number, so re-imports do not create duplicates.
Draft or auto-post
Leave imported entries in Draft for review, or let Journal Import Managers auto-post straight to the ledger — the choice is made per batch.
Skip rows with errors
Tick one box to import only the valid rows in a batch while leaving the failed rows untouched for correction and re-validation.
Opening balance import
A dedicated Opening Balance Import mode makes it straightforward to bring historical trial balances into Odoo at go-live.
Import history & rollback
Every batch is kept as a permanent record with its file, row counts and creator, and can be rolled back in one click if it was posted in error.
Downloadable templates
Download a ready-made sample template for each file type so new imports start from a known-good column layout.
How it works
Upload your file
Attach a CSV, Excel or DATEV export, then pick the file type, default journal and import mode.
Load & Validate
The whole file is parsed and checked in one pass; every row gets an OK, Warning or Error status with a plain-English message.
Review the report
Fix flagged rows in the source file, or tick Skip Rows With Errors to proceed with only the valid ones.
Import & post
Create or update the journal entries, leave them in Draft or auto-post to the ledger, and roll back the whole batch anytime.
See it in action
From upload to a posted, traceable journal entry.
Every batch is tracked in one place: Draft, Validated and Imported batches with row, entry and error counts at a glance.
The row-level error report: a full-file validation summary plus colour-coded OK, Warning and Error rows with a plain-English message for each.
A completed import batch showing the entries it created, the balanced rows behind them and a full audit trail in the chatter.
The upload and options panel: file type, default journal, create-or-update mode, draft-vs-auto-post, opening balance import and the skip-errors toggle.
The journal entry created by the import, with the Import Batch reference and balanced journal items for full traceability.
Frequently asked
Which file formats are supported?
CSV, Excel (.xlsx) and DATEV (EXTF CSV) exports are all supported, with common column-header variants recognized automatically.
What happens if some rows in my file have errors?
Load & Validate checks the whole file up front and lists every problem row with a human-readable message. You can fix the source file and re-validate, or tick Skip Rows With Errors to import only the valid rows.
Can I undo an import if something was wrong?
Yes. Every import is tracked as its own batch, and a completed batch can be rolled back in one click, removing the journal entries it created.
Who can auto-post imported entries to the ledger?
By default, imported entries are left in Draft. Auto-posting to the ledger during import is gated to users in the Journal Import Manager group.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
Import Journal Entries — validated CSV, Excel and DATEV imports with a row-level error report and one-click rollback.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 1189 |
| Technical Name |
cerevantix_import_journal_entry |
| License | OPL-1 |
| Website | https://cerevantix.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module