Entries by Statements - shortcoming

Registered by Ferdinand

see also discussion
<email address hidden>
subject: Entries by Statements - shortcoming

and bugfix here
https://bugs.launchpad.net/openobject-addons/+bug/523800

* date must generate period (which might be overidden for special
purpose)

* Journal selection must generate Journal number (currently random
apparently because of more than one cash journals)

** IMHO all move_lines increment the same number as the journal itself
the lines should another sequence.
Suggestion:
*** "Invoice" Sequence = Journal Number = Bank draft number
*** Entry Sequence = numbering of the lines.

** to be discussed - when to generate the journal number without
blocking
*** selecting the journal - what to do if the wrong journal was taken
and hence the wrong number and sequence were used - how to revert
(without admin rights) ?
*** posting the journal - it's to late if something went wrong -same
problem as above
*** best would be a preview popup of the next journal number +
confirmation

* new detail line must copy journal date (instead of current date)

* compute should (also) show difference between calculated and ending
balance ( the 2 data fields are badly located to compare)
* (fixed) confirmed statements must be completely read only

missing features
* handling of bank / cash moves which require VAT calculation
** workaround - create net and vat lines manually
* analytic account coding for such moves.
* (fixed) select customer/supplier from res_partner

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.