Am 27.04.2012 11:02, schrieb Cédric Krier:
On 27/04/12 10:37 +0200, Jan Grasnick | grasbauer ug wrote:
Am 27.04.2012 09:49, schrieb Cédric Krier:
On 27/04/12 09:39 +0200, Jan Grasnick | grasbauer ug wrote:
Am 26.04.2012 16:46, schrieb Cédric Krier:
On 26/04/12 16:32 +0200, Jan Grasnick | grasbauer ug wrote:
here comes a quick and dirty proof of concept of a module for bulk
paying Invoices listed on an advice [1] .
Could you explain what it is?
It sounds like the statement but I'm not sure.
Its similar to statement - but it covers a different use case:
In our case a company is doing serial produktion on demand for
different customers. This produces a lot of invoices. The customers
are paying always a bunch of invoices in one payment
So why not grouping invoices?
What means grouping?
Indeed of generate a lot of small invoices, just create one.
That's not a possibility in a lot of real world business connections :
Client want be billed project by project. Each invoice goes to the
project manager - he is signing the invoice as valid and is passing it
to the financial office. They are paying the invoices in groups,
sometimes accounting credit notes and cash discounts. This process is
disconnected from the content review of the invoice.
Don't know if account_statement covers this as well - if it is, that
was a good training for rapid tryton prototyping ;)
For me the statement manage the case of one payment for multiple
invoices. When you select an invoice on statement, if the amount is
greater than it creates on the fly a new line for the remaining.
ok - it's very similar but not the same: it creates positions on the
statements, which are not really existing. There exists only one
position with the total amount. And you have to do a lot clicks - so
I think my solution is nothing more than a "simplify things"-module
Normally, your problem is NP-Complete and I think it is "Subset sum
problem" [1]. That's why we decided to manage such payment matching by
just helping the user.
Ok. I'll take a deeper view to it.
--
tryton-dev@googlegroups.com mailing list