Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

  • Home
  • Get Help
  • Troubleshooting
  • Failed to create a create invoice in QuickBooks Online: Invalid number: Sound in motion, QuickBooks field: CustomerRef.value
Best answer

Failed to create a create invoice in QuickBooks Online: Invalid number: Sound in motion, QuickBooks field: CustomerRef.value

kristinh

I’m trying to create a zap to generate a QBO invoice upon creative of a new sales order in Zoho Inventory. My trigger in Zoho is setup, then I have an action to find customer in QBO that seems to be functioning, then I have my create invoice action which produces this error:

“Invalid Number: Invalid Number : Sound In Motion, Quickbooks Field: CustomerRef.value”

Regardless of if I select the customer name from the Zoho connection, or the display name from the find customer action in QBO. 

What’s the issue? Thanks in advance. 

Best answer by Troy Tessalone

@kristinh 

The Customer field expects the internal QBO Customer ID from step 2.

 

The 123 next to the Product/Service field label indicates the field expects the internal QBO ID of the Product/Service instead of the Name.

 

Similar to how you did a QBO Find Customer step, you’d need to do the same for the Product/Service to get the internal QBO IDs.

 

View original
Did this topic help you find an answer to your question?
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

6 replies

Troy Tessalone
Forum|alt.badge.img+14

Hi @kristinh 

Good question.

Please post screenshots of the encountered error along with detailed screenshots with how your Zap steps are configured, thanks.

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
kristinh
  • kristinhBeginner
  • Author
  • Beginner
  • 5 replies
  • March 16, 2023

 

Troy Tessalone
Forum|alt.badge.img+14
  • Troy TessaloneZapier Expert
  • Zapier Expert
  • 31067 replies
  • Answer
  • March 16, 2023

@kristinh 

The Customer field expects the internal QBO Customer ID from step 2.

 

The 123 next to the Product/Service field label indicates the field expects the internal QBO ID of the Product/Service instead of the Name.

 

Similar to how you did a QBO Find Customer step, you’d need to do the same for the Product/Service to get the internal QBO IDs.

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
D
1 person likes this
  • D
    Dimitri1177
kristinh
  • kristinhBeginner
  • Author
  • Beginner
  • 5 replies
  • March 17, 2023

There is a help article that explains a common problem with QBO is that it looks for a display name, which is misleading, at least in this case. I have this setup per your instructions now and will test later on to see if its functioning. Thank you!

Charie
Forum|alt.badge.img+4
  • CharieZapier Staff
  • Zapier Staff
  • 238 replies
  • March 20, 2023

Hi @kristinh 

Just doing a follow up on this.

Have you already tried the set up recommended by Troy and see if it works?

Let me know if you have other questions! 😊

kristinh
  • kristinhBeginner
  • Author
  • Beginner
  • 5 replies
  • March 20, 2023

Yes, this worked but led to another issue which Zapier doesn’t have a solution for at this time. 

Terms & Conditions