Errors
There is already an invoice in QuickBooks for PN#1240449
The most common of all errors. Indicates that the Proposal has already been exported to quickbooks (e.g. an invoice with the same number already exists in QuickBooks).
The goal is to prevent a branch of exporting multiple copies of the same invoice by accident.
BadRequest. Details: Valid line TaxCodes for US should be TAX or NON. Supplied value: 13 ,
(Unconfirmed) Most likely means that the QuickBooks account is not set to use AutoTax.
This is one scenario that we currently don’t support for US accounts (use explicit taxgroups).
Exception creating invoice: An item with the same key has already been added. Key: 01tUJ000002JYiYYAW
(Unconfirmed) Most likely means that there is more than one copy of Corporate feed active for the branch (e.g. Daltile duplicated feeds)
PI can’t determine which one of the multiple matches to the Salesforce Product Id should be used.\
The key mentioned in the message will help identify the product/feed that has duplicates.
Exception creating invoice: BadRequest. Details: QueryParserError: …
Exception creating invoice: BadRequest. Details: QueryParserError: Encountered " <IDENTIFIER> "Donnell "" at line 1, column 52.
Was expecting one of:
<EOF>
<AND> ...
"iterator" ...
"maxresults" ...
<OR> ...
"order" ...
"orderby" ...
"startposition" ...
,
Most likely indicates that the customer, project or proposal name has a character that is not supported by QuickBooks for these fields.
Known issues are: ‘ (apostrophe), : and ”
Will require some changes in code to automatically replace those with supported characters.
BadRequest. Details: Element contains invalid characters. Bret Adams: Idaho Spine & Sports Physical Therapy ,
As the message indicates invalid characters in the names (e.g. &)
Will require some changes in code to automatically replace those with supported characters.
BadRequest. Details: Required parameter Line is missing in the request ,
(Unconfirmed) Most likely indicates that the proposal was empty, no line items.
BadRequest. Details: The name supplied already exists. : null ,
Have to investigate. Assume it is a mismatch between identifier and name. QuickBooks expects most names to be unique but also have a different unique identifier (that may or not be derived from the name). (wild guess) If QuickBooks has an “entity” with an id0/john and we try to add a id1/john we could get an error like this
Failed to initialize
Most likely cause is that the proposal was just created and the sync from salesforce to PI hasn’t happened since. It may also indicate a data corruption issue if the proposal was last modified more than an hour or so.
Exception creating invoice: Object reference not set to an instance of an object.
Internal error. Assume caused by not having synced down all the data. Have to investigate further.
Exception creating invoice: Missing configuration
Internal Error caused by missing configuration during a new deployment.
BadRequest. Details: There is no income account associated with the item “There is no income account associated with the item “MOBIQEB”. Is it marked for sale, and has an income account associated with it?”. Is it marked for sale, and has an income account associated with it? ,
(Unconfirmed) Most likely indicates that there was already an Product/Service in QuickBooks for this SKU but it was not associated with an income account 🙂
Since there was already one, LeadsPiper will not create a new one. But since it was not associated with an income account can’t be used in an invoice.
Most likely the fix is to edit the Product/Service in QuickBooks and associate it with the right account.
BadRequest. Details: Business Validation Error: Make sure all your transactions have a GST/HST rate before you save. ,
Should only happen to Canadian QuickBooks accounts. It indicates that there is a mismatch between the Tax Groups in Salesforce and QuickBooks. They MUST have the exact same name and for every tax group used in a Proposal there must he one in QuickBooks with the same name.
Worth consulting with Sanderson for details on how it was addressed.
Warnings
Didn’t find 7I0A900110: 01tUJ000003bfaLYAQ in Price book (added as service)
Couldn’t find a match for the Salesforce Product Catalog in LeadsPiper or QuickBooks, adds the item as a Service.
Most likely it will not be taxed correctly. The user should review the proposal in QuickBooks.
One possible solution is to manually create the Product in QuickBooks so it can be used in the future. A better solution is to figure out why a product that is no longer available was used.
Line Price mismatch for MOBCHCC: 50.39 * $6.35 = $319.9765 != $351.72
Indicates that the total for the line item does not match the total calculated by multiplying the quantity by the unit price and rounding the result.
Most of the time indicates a rounding issue.
User should expect the total for the invoice to not match exactly the proposal in Salesforce.
Item 01t41000003nQSRAA2 not in Price book but exists in QB: PRODISC #20
The Salesforce Product was not found in the Catalog Feeds for the zee but there is a match for it in QuickBooks so uses it.
It is not an issue. In most cases it is just because some of the Products (MOBs) in Salesforce actually don’t exist in PLM.
We will want to figure out a good way to add those to PLM so we can avoid the warning in the future.
Reuse existing Item SAVNFSK422S (“Savannah Oak Tree Top 3/4″ x 4″”)
The Product/Service already existed in QuickBooks (and was not originally created by LeadsPiper).
Not an issue. Just a heads up that since it wasn’t created by LeadsPiper we can’t guarantee that it was associated to the right supplier, account, …
Failed to get document contents
Failed to add proposal pdf to QuickBooks invoice.
Very poorly named 🙂