Invoicing behaviour
Submitted by ppvs on Mon, 13/05/2013 - 10:32
Hi,
Wondering if this is the correct behaviour?
I charged thru charges on Saturday an eliz collar and left as billed - patient visit was a no reason completed visit.
Dog came in for visit today - Monday - and a new visit was started and invoiced thru invoices which added on to the exisiting charge of the eliz.
In the patient summary now there is an eliz collar under the no reason visit form Saturday and also an eliz collar under todays skin visit but the client has only been charged for one collar.
Is it correct that this charge should be copied on to the new visit?
Thanks,
Bernie
Re: Invoicing behaviour
Sounds like a bug to me...
I am betting that a relationship is created between the VISIT and the Invoice Items each time the invoice is marked as completed. (I am assuming the client didnt actually take the collar Saturday) The Client was charged Saturday and the invoice left open(unfinalized) you then added to the same invoice on monday
My advice that will avoid this is finalize invoices if a pet is NOT in hospital. So if a client walks out with a collar finalize the bill even if there is intention to see them the following day....because NO matter what they now owe you for the collar...you dont want any confusion as to whether they took it or not...a finalized invoice in my mind says they did.
Re: Invoicing behaviour
Thanks Ben,
Yes they did take the collar and booked to come in Monday.
Previously we would not have finalised the invoice so it would be one ongoing invoice. I see your point but I suspect open still should not do this duplicate behaviour?
Cheers,
Bernie
Re: Invoicing behaviour
Would anyone have any thoughts on this "error/bug".
Again today we had meds ready yesterday - collected at visit today with todays injection and duplicated records on the file.
I understand the finalised invoice idea but my thoughts are this same scenario is also going to happen with ongoing care hospital patients.
Thanks,
Bernie
Re: Invoicing behaviour
This is an error Bernie, it will need to be corrected for 1.7, I wouldnt task it as critical but I will create a JIRA (bug entry for it)
https://openvpms.atlassian.net/browse/OVPMS-1302
Bernie could you just confirm that both entries are still present even once the INVOICE is finalised.
Re: Invoicing behaviour
Yes they are Tony.
Thank you
Re: Invoicing behaviour
I've been able to reproduce and fix this bug for 1.7.
The workaround for 1.6 is to finalise invoices after each visit. To be on the safe side, your implementer can also make some changes that will prevent this occurring. These are documented in the JIRA.
-Tim