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.
Splitting is not a solution for many reasons:
- lost the link between the invoices and the move line
- it will generate a reconciliation which will trigger wrong event
I really think it is an important feature to be able to decide the amount
to pay.
More over, it should be possible also to generate a payment without having
a account move line.
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'.
I don't understand how it could be similar to "account.statement.journal"?
As I said, it just defines how you will communicate the payment so it will
be added by sub-module that will implement a standard.
For more information:
https://code.google.com/p/tryton/wiki/PaymentOrder
--
--
[email protected] mailing list
