On Sat, Feb 25, 2017 at 5:04 PM, Cédric Krier <[email protected]> wrote:
> On 2017-02-25 09:01, Khurram Shahzad wrote: > > > But I have a question, why do you want to generate the supplier invoice > > > instead of encoding the one you will receive? > > > > > > > The idea is good. But, in this case system will not be showing the > correct > > account payable as the payable to supplier is not posted. > > It will once you post the supplier invoice which will always be the case > no matter the workflow. You can not post in your accounting without > having the actual supplier invoice. > > > Moreover, how > > will we validate or confirm that every line in the invoice sent by > supplier > > is corresponding to a patient sale line. > > You do not trust your supplier? The hard way is to generate purchase for > each order and re-construct the supplier invoice with the invoice line > generated by the purchase. But this will be long process. > > The other way could be that you just matter about the quantities and so > you create a simple report base on the sale orders which gives you the > quantity orders over the invoiced period and check it against the > supplier invoice. > > > > Also how are the services sold/managed? Are you encoding a sale order > > > every day for every patient? This seems a very hard work to do. > > > > > > We have one sale order for exactly one hospitalized patient. Every food > > item consumed by the patient appears in his sale order as sale lines. > > So I guess this sale order is generated at the end of the > hospitalization otherwise how will you manage when the stay last longer > or shorted or when they are changes about the order etc. > Thank you so much for such a brief response. I think, we should go with invoices from suppliers and will validate it using some report from patient sales. -- You received this message because you are subscribed to the Google Groups "tryton" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton/CAM3N3CyZLCMk5zsTMjh7LmSfG0idBW%2Bw5%3Dwtr4n2iT6A3tL0Ow%40mail.gmail.com.
