Comment 19 for bug 662821

I am testing the account_sequence module, and understanding what it does, i get this:

Configure my journal with :
 * 2 different sequence ( sequence_id and internal_sequence_id fields)
 * Sale type

Make and Validate one Invoice -> the account move create get name and internal_sequence_number set the values with sequences from journal.
Create manually a move in the same journal and again and both fields are set name and internal_sequence_number.
Results:
Move from invoice: name: 2010/01 internal_sequence_number: 2010/01
Manual move: name: 2010/02 internal_sequence_number: 2010/02

As you see *both* sequence are called, the account_sequence must consider in the code if the move does not comes from Invoice document just use internal_sequence_id from Journal adn write the value in name and internal_sequence_number fields, this keeps the sequence_id ( aka. Invoice sequence).

This[1] is the code in post method redefined in account_sequence.py file from account_move i think the post method must redefined completely and dont use super call, so in parent post method the name field is wrote with Entry Sequence (sequence_id field from journal).

Waiting your feedback, regards,

[1] http://paste.pocoo.org/show/307565/

PS: i'll post a patch