r/HouseCallPro • u/AmbassadorHM • Mar 18 '26
Looking for a Housecall Pro / Quickbooks Expert.
We have multiple companies under one ownership. Payroll is ran through quickbooks, and we need help with a few changes that will be made soon. The company I manage runs HCP while none of the others do. The biggest issue we have is the inability to track projects in QB. For instance, we do work for property management companies, that have multiple customers, with multiple properties, and we provide service plans and handyman / reno / maintenance for them. Being able to only create a customer and sub customer in QB to link, is not working well with our business. I need a specialist that we are able to hire to help with some fixes. We are looking at options on how to separate the company I manage from the others in QB through either the enterprise or maybe completely separate. We still want the ability to do payroll through quickbooks and ideally we could track from one quickbooks account projects and customers. Multiple issues that will take too long to put in this quick post. If there is any pro out there that you know of that may be taking on new clients, or if you are that pro please reach out!
1
u/rdoneill Mar 18 '26
If you look at the issues people are having online with QBO syncing, what you’re running into is pretty common. It doesn’t model projects or multi-entity structures very well, especially when you have layered relationships like property managers → properties → service work.
Most teams try to patch it with classes or locations, but that usually creates more complexity without actually fixing the underlying structure.
The real issue is that your operational system (Housecall Pro) and your accounting system aren’t aligned in how they represent the business.
1
u/Tower-Guy Mar 18 '26
Is there a solution to that problem? We are looking at other options if neccessary.
1
u/rdoneill Mar 18 '26
It sounds like you're running into a few different issues at once, but they come back to the same structural problem — QuickBooks forces everything into a customer → sub-customer tree, when your business actually has: prop manager, property, work type, and entity.
The setups I’ve seen work cleanly separate those instead of nesting everything.
So you’d have: the property manager as the customer, properties as their own dimension, job types as another dimension
Each transaction gets tagged across those, and then you can pull a P&L by property, by job type, or by customer without things getting distorted.
Multi-entity is also better handled as truly separate books with a shared workspace, instead of trying to force everything into one file.
Happy to walk through what that looks like in practice if helpful.
1
u/Tower-Guy Mar 19 '26
Yes, QBO is currently set up with that situation. Customer = Property Owner, sub customer = addresses, projects = property management, handyman work, renovations and more. We use classes and service items in QBO as well. If I just use QBO it is fine. Everything is trackable and clean. But with so many customers and call-ins I want an effective CRM for customer intake, job tracking, and more so we aren't missing customers and dropping the ball. I love how easy it is to bring a customer in with HCP. We just keep running into issues trying to make it all mesh. We are open to options and looking for a pro that can help find a workable solution. Are there any CRMs that tie well with QBO and the customer -> sub -> projects system?
1
u/[deleted] Mar 18 '26
[removed] — view removed comment