You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If multiple invoices for the same buyer are issued, it will be handy to have them stored in the database.
The same is true for seller which will most probably will usually be the only one.
These models can be separate and inherited from common abstract InvoiceUserModel, but this can be discussed (we can only use a single model)
The text was updated successfully, but these errors were encountered:
Yes this is true to a certain point. Both buyer and seller cound change the data and the old invoices have to stay the same... For example if the buyer moves he would have different address and only new invoices should be amended.
Currently we have the duplicate function so it also creates an invoice with the details so there is less work.
If multiple invoices for the same buyer are issued, it will be handy to have them stored in the database.
The same is true for seller which will most probably will usually be the only one.
These models can be separate and inherited from common abstract InvoiceUserModel, but this can be discussed (we can only use a single model)
The text was updated successfully, but these errors were encountered: