I noticed a post 6 days ago, where AJD noted that when cloning Receipts and Payments, the reference number is brought into the clone. This was interfering with Automatic and Default references, as noted by Tut.
What I am concerned about, is that when I CREATE a receipt, and then clone it, not only is the reference number carrying forward into the cloned area, but the date is NOT. This has been an organizational tool (when instructing my data entry clerks) to have them clone all their entries after the first, so that the date will remain static, and all the A/R receipts posted for the day will be correct.
This only changed very recently. It is a major hassle, as I will have to go and manually check everyone’s entries now, or instruct them on generating a report to check themselves after each day’s batch is entered. I thought that was the purpose of CLONING…to carry forward the important info. (I agree with AJD that the Reference numbers shouldn’t necessarily be carried forward in a clone…how often will one customer’s reference number in a receipt-- their check number usually – match another customer’s??)
I have already seen where some inattentive clerks haven’t noticed that the date didn’t clone for them. This will create some trouble when reconciling bank statements.
Where can I make suggestions to have the cloning function return to its former behavior?