Hi,
although at TUL we discussed a little bit about payment terms with the german 
guys, and it seems that is not much of a problem for them, I'd like to explain 
a little bit the improvements we're working on, and which we already discussed 
with B2CK.

The idea is to remove "PaymentTermLineDelay" (which lets the user choose 
between netdays and end of the month). And replace it with three fields: 
"months", "days" and "day". Note that months is not the same as 30 days as 
with months with more or less than exactly 30 days, the due date is different, 
and that is important in Spain. For the "day" it will be possible to set "31" 
as a replacement for "end of the month".

"PaymentTermLineType" is also replaced by a selection field which will allow 
four options. The existing "fixed", "percent" and "remainder" as well as the 
new "division" option. The latter is more intuitive as allows users to say 
that the amount is divided by 3 instead of setting the "33.333333" percent.

Another important change is that the whole invoice amount will be passed to 
payment term lines for calculation instead of the remainder. This means that 
if an invoice is splitted in three payments, you currently must configure:

first => 33.33333 percent
second => 50 percent
third => remainder

With this change:

first => 33.33333 percent
second => 33.33333 percent
third => remainder

This makes amounts more predictable (apart from being able use the division 
option).

Out of the standard account_invoice module we're working on two new modules: 
account_payment_days and account_payment_holidays.

*account_payment_days* will add a new field to party's where one ore more 
payment days can be configured. That is, if the party has days 10 and 20 as 
payment days, and after applying the party's payment term the due date is the 
5th, it will be moved to the 10th. If the due date is the 11th it will be 
moved to the 20th (if it's in the 21th, it will be moved to the 10th of next 
month).

*account_payment_holidays* will depend on account_payment_days and will allow 
to configure per party payment holidays. That is, periods in which the party 
will not pay and the due date will automatically be moved after the holidays. 

Regarding this module I hesitate how to do it. Should we have a party_holidays 
module in which we could set when the party closes for holidays? Also, in many 
companies, those holiday are recurring each year. Any idea on how to make that 
smart so users do not need to input the holidays each year? 

Then, the account_payment_holidays module could add the "does not pay on 
holidays"  checkbox. Opinions? 

-- 
Albert Cervera i Areny
http://www.NaN-tic.com
Tel: +34 93 553 18 03

http://twitter.com/albertnan 
http://www.nan-tic.com/blog

-- 
tryton-dev@googlegroups.com mailing list

Reply via email to