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.

Best answer

Service Date not showing on QBO Invoice when using Bundle (GroupLineDetail) via Zapier

  • February 18, 2026
  • 6 replies
  • 27 views
G

I'm automating invoice creation in QuickBooks Online via Zapier, and I'm running into an issue specifically with Bundle line items and the Service Date field

- When I create an invoice with a regular product/service item, the Service Date is submitted and displays correctly on the invoice.
- When I use a Bundle item instead (same Zap, same date input, same format), the Service Date is submitted but does not appear on the invoice.

From my research, I understand this is likely because Zapier's QBO integration uses SalesItemLineDetail for regular items (which supports ServiceDate), but switches to GroupLineDetail for bundles — and the ServiceDate field does not carry through in that structure.

My invoice must remain as a single grouped Bundle line item, so breaking it into individual components is not an option.

Has anyone found a working solution for this? Specifically, has anyone successfully used Code by Zapier to construct a custom GroupLineDetail payload that includes the ServiceDate field when calling the QBO API?

Best answer by SamB

Hey there ​@Gervasio Ramirez SA 👋

I can see you've already been in touch with our Support team and they've submitted a bug report for this issue. It's not been resolved yet but you'll get an automatic email notification from us as soon as it is.

Did you have any luck with any of the workarounds that Troy and drtanvisachar suggested here? Want to make sure you’re all set in the meantime!

6 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Troy TessaloneZapier Orchestrator & Solution Partner
  • Zapier Orchestrator & Solution Partner
  • February 18, 2026

Hi ​@Gervasio Ramirez SA 

You’ll likely have to explore using the QBO API to make a custom API request.

 

OPTIONS

 

 

⚡ Troy Tessalone - AutomationAce.com | Top Zapier Solution Partner | #1 Zapier Community Contributor
    drtanvisachar
    Forum|alt.badge.img+5
    • drtanvisacharZapier Solution Partner
    • Zapier Solution Partner
    • February 20, 2026

    Hello ​@Gervasio Ramirez SA 

    You’ve got it right. In the QBO API, bundle items use GroupLineDetail, and ServiceDate isn’t supported at the group level like it is for SalesItemLineDetail. So even with Code by Zapier or a fully custom Webhooks request, there’s nowhere for QBO to store and display that date on the bundled line.

    Best workarounds while keeping it as one bundle line

    Put the service date in the bundle line Description so it prints
    Use an invoice level Custom Field for the service date
    If you set ServiceDate on the member lines inside the group, QBO may accept it, but it usually still won’t render on the grouped summary line

    Dr. Tanvi Sachar
    Monday Certified Partner, Tuesday Wizard

    Zapier Solutions Partner-Tuesday Wizard
    AutomateMyBiz
    Forum|alt.badge.img
    • AutomateMyBizZapier Solution Partner
    • Zapier Solution Partner
    • February 21, 2026

    If the field is in a line item, use loop to get them.

     

    If you need further assistance on this, book a free 20min troubleshooting call from my calendar here: —LINK REMOVED—

    Let me see if we can solve the issue on that call
     

    Fahad S
    Founder @ AutomateMyBiz.ai. | Zapier Platinum Partner

    This post has been edited by a moderator to remove self-promotional calendar booking link as per our Community Code of Conduct.

    Zapier Platinum Solution Partner @AutomateMyBiz.ai | 15,000+ Automations Built | Team of 15
    SamB
    Community Manager
    Forum|alt.badge.img+11
    • SamBCommunity Manager
    • Community Manager
    • Answer
    • February 27, 2026

    Hey there ​@Gervasio Ramirez SA 👋

    I can see you've already been in touch with our Support team and they've submitted a bug report for this issue. It's not been resolved yet but you'll get an automatic email notification from us as soon as it is.

    Did you have any luck with any of the workarounds that Troy and drtanvisachar suggested here? Want to make sure you’re all set in the meantime!

    G

    Hi Tanvi and Sam,

    Thanks for answering my question!

    I followed the suggestion the Support team made via email and changed the zap “Create Invoice” to “API Request (beta)”.
    This made it possible to submit exactly ServiceDate into GroupLineDetail.
    It takes a bit of a minute reading QBO documentation on how to format the body when doing the POST to create the invocie.

     

    Hopefully “API Request” stays as a feature, or eventually you can fix the bug via “Create Invoice”

    Thanks, you can close this ticket.
    Best,

    Gervasio

      SamB
      Community Manager
      Forum|alt.badge.img+11
      • SamBCommunity Manager
      • Community Manager
      • March 6, 2026

      Thanks for the update ​@Gervasio Ramirez SA 🤗 I’m so glad Troy's suggestion of using the API Request action did the trick for now - thank you ​@Troy Tessalone! 

      I'll keep this thread open for now so if anyone else is affected by the same issue, just comment below to let us know and we'll make sure you're added to the bug report. 🙂

      Terms & ConditionsAccessibility statement