Quickbooks -

Hi Team,

Having what I think is a localization issue with the Quickbooks Online Node. Hopefully someone can help.

Describe the issue/error/question

Can’t create Invoice/Quote due to error ‘missing a Tax Code element.’ I suspect it’s due to a localization issue? Australia/GST item not coming up when I select the line, looks like it should populate expected values but it just returns nothing and I can’t find a way to set the Tax. Module works fine for returning data and behaves as expected.

What is the error message (if any)?

400 - {“Fault”:{“Error”:[{“Message”:“A business validation error has occurred while processing your request”,“Detail”:“Business Validation Error: Make sure all your transactions have a GST rate before you save.”,“code”:“6000”,“element”:""}],“type”:“ValidationFault”},“time”:“2022-04-22T01:06:49.399-07:00”}```

Please share the workflow

Just using the default Quickbooks Node to create an invoice or quote.

Share the output returned by the last node

400 - {“Fault”:{“Error”:[{“Message”:“A business validation error has occurred while processing your request”,“Detail”:“Business Validation Error: Make sure all your transactions have a GST rate before you save.”,“code”:“6000”,“element”:""}],“type”:“ValidationFault”},“time”:“2022-04-22T01:06:49.399-07:00”}``’

Information on your n8n setup

  • n8n version: - Latest Version
  • Database you’re using (default: SQLite): SQLite
  • Running n8n with the execution process [own(default), main]: Main
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker

Hey @bitprecision, I am sorry to hear you’re having trouble here.

I tried to give that a go and didn’t run into trouble using our test account and node settings like this:

So there’s a good chance this might be a problem with differences between country-specific Quickbooks setup as you suspected. We’ll try to set up a Australian company and take a closer look in the next days

Just to make sure we’re not missing something here, could you confirm the exact settings of your Quickbooks node? You can simply select it on your n8n canvas, copy it with Ctrl+C and then paste it here on the forum.

Thanks so much!

Thanks mate,

Code below. Thanks for getting back to me so quickly. The node works fine for all queries, just can’t create it seems.

Just adding the JSON output from querying an estimate if that helps.

[
{
"domain": "QBO",
"sparse": false,
"Id": "28819",
"SyncToken": "0",
"MetaData": {
"CreateTime": "2022-04-07T19:50:35-07:00",
"LastUpdatedTime": "2022-04-07T19:50:39-07:00"
},
"CustomField": [
],
"DocNumber": "1325",
"TxnDate": "2022-04-08",
"CurrencyRef": {
"value": "AUD",
"name": "Australian Dollar"
},
"TxnStatus": "Pending",
"Line": [
{
"Id": "1",
"LineNum": 1,
"Description": "Remove Computer Equipment and Rack from premises and reinstall after completion of flooring",
"Amount": 545.45,
"DetailType": "SalesItemLineDetail",
"SalesItemLineDetail": {
"ItemRef": {
"value": "13",
"name": "IT Support Work:220 IT Procurement"
},
"UnitPrice": 136.3625,
"Qty": 4,
"TaxCodeRef": {
"value": "11"
}
}
},
{
"Amount": 545.45,
"DetailType": "SubTotalLineDetail",
"SubTotalLineDetail": {
}
}
],
"TxnTaxDetail": {
"TotalTax": 54.55,
"TaxLine": [
{
"Amount": 54.55,
"DetailType": "TaxLineDetail",
"TaxLineDetail": {
"TaxRateRef": {
"value": "20"
},
"PercentBased": true,
"TaxPercent": 10,
"NetAmountTaxable": 545.45
}
}
]
},
"CustomerRef": {
"value": "924",
"name": "Test Customer"
},
"CustomerMemo": {
"value": "Please find attached quote as requested, if you have any queries or would like to order please let us know. Thanks for your business. Bit Precision"
},
"GlobalTaxCalculation": "TaxInclusive",
"TotalAmt": 600,
"PrintStatus": "NotSet",
"EmailStatus": "EmailSent",
"BillEmail": {
"Address": "[email protected]"
},
"DeliveryInfo": {
"DeliveryType": "Email",
"DeliveryTime": "2022-04-07T19:50:39-07:00"
}
}
]
1 Like

Cheers @bitprecision, I had a look into this with @jon earlier today and we were able to confirm the problem. I have added this to our internal bug tracker and we’ll of course confirm once this is fixed.

We will also be releasing an update for the HTTP Request node very soon (as described here by @Nivb_6) which will let you use the Quickbooks credentials for any request. This should allow you to make the correct API request manually as a workaround until this problem is properly fixed in the Quickbooks node.

2 Likes