Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • erp5 erp5
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 149
    • Merge requests 149
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • erp5erp5
  • Merge requests
  • !2232

Open
Created Jan 20, 2026 by Titouan Soulard@tsoulardDeveloper
  • Report abuse
Report abuse

Implement CSV import for Bank Reconciliation

  • Overview 8
  • Commits 11
  • Pipelines 2
  • Changes 160

/cc @jerome

We discussed about it some time ago, and I finally took time to finalize everything. This may only be a first try, since I am sure issues will emerge, but at least we can ship the feature.

The added test should describe everything, and I did not changed anything to the old tests, so to keep full backward compatibility. In fact, an user not using lines will not see any change at all, apart from the added « Business Process » field on the Bank Reconciliation document, which is obviously optional.

Mainly, there are two important things for the user: the possibility to import a Spreadsheet through OOo Import, which will create individual lines, and a new grouping form for Bank Reconciliations with lines, which allow reconiling each line with a different accounting transaction.

1768924344_grim

In terms of datamodel, I kept something close to the old one, but while it is still possible to aggregate Bank Reconciliation to Accounting Transaction Lines, we can now also aggregate Bank Reconciliation Lines. The SQL request will select both, so backward compatibility also work if the user decides to switch to the new system ("Reconcilied Amount" will be correct without migration nor intermediate document).

On top of usual code review (I think most of the code is quite clean), there are two main points still open:

  • importing dates from CSV often results in wrong date order (mistakes month and day). I cannot think of a way to fix that, and it can be handled in another MR, which means user have to import ODS documents, which can easily be made from a CSV;
  • I committed rules, Business Process, builder, etc on the main BT5. A split might be useful, or maybe we do not want to commit these at all and create dynamically in tests, or maybe there is already a good place for them, I do not really know, tell me what you think we should do.
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: reconcile-with-banks
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7