• Replies 8 replies
  • Subscribers 2 subscribers
  • Views 0 views
  • Users 0 members are here
Options
Related

Anyone using FieldPulse with QuickBooks — how are you handling billing?

Mike Dolan

We've had the QuickBooks integration running for about three months now and I'm still fighting with the billing handoff. Jobs finish in FieldPulse, invoices create in QBO, but there's always something that needs manual cleanup.

Specific pain points:

  • Line items don't always map the way our accountant expects them to
  • Tax rates occasionally come across wrong, especially on jobs with mixed taxable/non-taxable services
  • Partial payments recorded in FieldPulse aren't syncing back status correctly

How are others actually using this day to day? Are you invoicing out of FieldPulse and letting it push to QBO, or are you doing something manual at the end?

Not looking for theory. Want to know what works.

  • We invoice out of FieldPulse and let it push. Cleanest path we found.

    Key thing: set up your Service Types in FieldPulse to match your QBO Items exactly before you toggle the sync on. We learned that the hard way — had 200 jobs with mismatched codes that needed manual reconciliation.

    For taxes, we disabled tax calculation in FieldPulse entirely and let QBO handle it. One source of truth.

  • Thanks Brandon! Question — when you say you disabled tax in FieldPulse, do your techs still see pricing at all? Or are they working blind on quotes?

    We tried the FieldPulse-first approach and our accountant had a fit because the GL mapping was all over the place. But I'm worried if we push to QBO and invoice there, we'll lose visibility on what was actually billed vs. quoted.

    What does your workflow look like end to end?

  • in reply to Deja Washington

    Techs see flat rates. We set up price books in FieldPulse with customer-facing totals, no tax line. They quote what the customer pays. Back office adds tax in QBO when we invoice.

    Not elegant but it eliminated the sync errors. Your call on what hurts more.

  • In my experience the sync works better if you don't let it automatically create invoices. We sync completed jobs as "estimates" in QBO, then our bookkeeper reviews and converts to invoice. Extra step but catches the mapping problems before they hit the customer.

    Takes an extra day but saved us from some embarrassing invoices.

  • Estimates route is interesting. That would have caught last week's disaster where a $4,200 job came across as $42,000 because of a misplaced decimal in a custom field.

    How much overhead does that add for you? We're doing 80-100 jobs a week.

  • in reply to Mike Dolan

    About 15 minutes a day for our bookkeeper. She batches them. Says it's faster than fixing screwed up invoices.

  • Happy to help clarify the sync behavior here, Mike.

    What you're describing with partial payments is a known gap — payment status currently syncs one-way from QBO to FieldPulse, not bidirectionally. For the most reliable workflow, we recommend recording payments in QBO and letting those sync back to FieldPulse to update job status.

    For tax configuration, this article covers the recommended setup: Tax rate not being applied correctly when syncing to QuickBooks Online

    I'll flag the partial payments feedback to the product team — this comes up regularly.

  • That's useful, thanks. Reverse flow on payments explains a lot.

    Still wish the integration was less fragile. But the estimate workaround from Art might hold us over.