It can be reused. Just assign a different vendor.
-derek
Sent using my mobile device. Please excuse any typos.
On October 23, 2019 12:41:12 PM Mark Hedges <[email protected]> wrote:
On Tue, Oct 22, 2019 at 1:13 PM Derek Atkins <[email protected]> wrote:
>> The recommended procedure is to change the bill/invoice number to
>> something like “use next”. You can additionally create a placeholder
>> customer and vendor to assign them to if you like.
>>
>> Then just try to remember at some point to search for any bills/invoices
>> numbered “use next” and edit them to reflect a real new bill/invoice.
>
> Instead of letting people correct bad data?
This is how you correct bad data -- by re-using the underlying data
structure. The assumption is that the user will make more invoices, so
re-using vs creating is not an extreme burden.
Vendor A has Job X. I created an invoice for Vendor B and assigned
Job X. The invoice was created for Vendor A (from the Job) but I
didn't notice, so I had to unpost it. It's the same job from my
company's perspective, and the same person, but A was him personally
and B was his new LLC. I wasn't able to change the vendor from the
invoice edit screen. The erroneous invoice cannot be re-used. I
created a new Job Y for Vendor B and created a new invoice.
Mark
_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
