On 10/07/11 11:26 +0200, Albert Cervera i Areny wrote: > We're starting to work on the Spanish localization and one of the many things > in the TODO list involves improvements to account.invoice.payment_term model. > Let me list the required changes: > > 1) Add the possibility that the delay is calculated in months instead of > days. > So January 30th + 1 month = 28 February (instead of 2 of March if one > specified > 30 days)
You can add a delay type of "net_months". > 2) Add the possibility of dividing instead of making a percentage. So if an > invoice must have 3 payments we "Type" is set to "Division" and the value to > "3". So the division is always correct (instead of having to write > "33.3333333"). You can add a type for "division". > 3) Add the possibility of several payment days. In Spain, some companies only > pay at day 15th of each month (or day 20th, or 30th, or whatever), but some > of > them have two payment days (15th and 30th of each month for example). For > example: > - A customer pays after 1 month at days 15th or 30th. > - If we create an invoice on January 5th it will be paid on February 15th. > - If we create an invoice on January 16th it will be paid on February 28th. This is some different delay types. > The days in which a party pays should, ideally be stored on party.party, > not > account.invoice.payment_term. The reason is that the number of possibilities > in payment terms explodes a lot with the payment day condition. I don't understand, you mean that some companies have different rules for each customers? That's sound strange. -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgpnNdMKK8sgp.pgp
Description: PGP signature
