Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Tryton Tryton
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 712
    • Issues 712
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 82
    • Merge requests 82
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TrytonTryton
  • TrytonTryton
  • Issues
  • #3694
Closed
Open
Issue created Feb 20, 2014 by Raphaël Hertzog@rhertzog

Allow integration of existing moves in an account statement

While trying to use the account_statement module, I am often annoyed by the
impossibility to integrate existing moves. I understand that in the perfect
situation you can have a new statement whenever you want and you should create
all the moves from the account_statement module but that's not realistic in many
cases and clearly impossible in some other cases.

The case where it's clearly impossible is when you have a move between two
accounts which are both managed by account_statement. I can't create the same
move from both sides, yet the move clearly appears on both statements and it
needs to be taken into account if I want my end balance to match.

The cases that are not always realistic is that not everybody gets bank
statement as often as they'd like to update their accounting. I for one get
monthly bank statement and there are times where I want to do my accounting
before I get the final bank statement. (Please don't blame my bank or my choice
of bank, ERP are meant to be adaptable to all use cases and I prefer to discuss
how we can improve Tryton to match my needs than discuss the merits of my bank)

Thus I would suggest to improve the account_statement module to be able to
import existing (posted) moves provided they are not part of another statement
on the account. But it should be possible to import a move that is part of a
statement that affects another account (provided that the move also affects the
account for which the current statement is about).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking