CRM has no way of distinguishing between an original invoice and an original invoice that has been amended (i.e. client has had a change of mind). An amended invoice will be imported as a new sales transaction which is a big problem on data analysis
Obviously if QuickBooks update their API to handle this better (by for example exposing an internal, permanent and immutable ID like lots of other API's do) then we could definitely look at this again. But unless that happens there is nothings we can do at our end (other than as I've said, advise customers not to change this ID).
Is this being caused by changing the Invoice ID/Reference in QuickBooks?
Unfortunately the QuickBooks API doesnt distinguish between an invoice with a new reference, and a new invoice. This is QuickBook's unique ID for the invoice, so if this is what's causing your issues, I can only recomend that you dont change the reference in QuickBooks.
Sorry I can't be more helpful, but as I say, there's no way to tell that this has happened via the QuickBooks API. It just doesn't handle that scenario. Everything in the QuickBooks API is dependent upon this ID.
Obviously if QuickBooks update their API to handle this better (by for example exposing an internal, permanent and immutable ID like lots of other API's do) then we could definitely look at this again. But unless that happens there is nothings we can do at our end (other than as I've said, advise customers not to change this ID).
Is this being caused by changing the Invoice ID/Reference in QuickBooks?
Unfortunately the QuickBooks API doesnt distinguish between an invoice with a new reference, and a new invoice. This is QuickBook's unique ID for the invoice, so if this is what's causing your issues, I can only recomend that you dont change the reference in QuickBooks.
Sorry I can't be more helpful, but as I say, there's no way to tell that this has happened via the QuickBooks API. It just doesn't handle that scenario. Everything in the QuickBooks API is dependent upon this ID.