Business Process Consideration

Discussion created by Hudi on Dec 1, 2013
Latest reply on Dec 8, 2013 by Hudi

Hi All,


Hope your holidays were pleasant.


I would love some input regarding the issue of why you need an invoice table.


I have a client who creates invoices based off his projects table. When something gets invoiced the status of the project simply changes to 'invoiced'. Now why is that wrong, or at least not recommended?



2 reasons I came up with:


1. If you want to create multiple invoices for a project, current system does not allow for that.

2. If you need to void an invoice, and create a new one, you have no record of that voided invoice.


Bottom line is that it's messy. But if they are surviving without it, are there any other reasons why I should press them to create an Invoices table (and all the scripts, layouts etc)?