Comment by [email protected]:
I don't think it should be possible to change the amount. We have that in
OpenERP and it adds too much complexity. IMO account.payment.order.line
should be dropped and the relationship should be a one2many from
account.payment to account.move.line. If a user really needs to make a
partial payment of a move line (which has not been split by the payment
term), they can split the move line manually and then add it to the payment.
Although the relationship should be a one2many the widget should be a
many2many and this would also avoid the need of account.payment.order.add.
Making everything much simpler.
Although the concept is pretty clear to me, I'm ok if payment type is to be
added by another module, that doesn't impose the restriction of being able
to add only moves with a certain payment type but I'm not sure we don't
want payment.mode in the standard module. I think payment mode is the
equivalent to account.statement.journal. In fact it should probably be
called 'account.payment.journal'.
For more information:
https://code.google.com/p/tryton/wiki/PaymentOrder
--
--
[email protected] mailing list
