QuickBooks Online can hold several companies under one sign-in, but each company is its own file with its own subscription, so a group with an LLC per location usually runs one company per entity. When sales runs from one HubSpot or Pipedrive portal, something has to decide which company each deal is invoiced from and which entity's payment account collects it. The CRMs' own QuickBooks apps describe connecting a QuickBooks account, not choosing one per deal. Some connector apps connect several and ask the user to pick at invoice time. A billing tool with a template per entity can pick by rule. Whichever you use, the invoice, the payment and the payout should all land in the same entity.
Checked against HubSpot's knowledge base (article last updated 21 July 2026), Pipedrive's support center (last updated 3 September 2026) and Stripe's documentation on 22 October 2026. These tools change often, so the changelog at the end records each update.
Can QuickBooks Online have multiple companies?
Yes. One sign-in can open several QuickBooks Online companies, but each company is a separate file with its own paid subscription, its own users and its own bank connections. QuickBooks multiple companies covers the setup and what the companies share.
That answers the accounting question. This post is about the next one. Your reps sell from one HubSpot or Pipedrive portal. Denver LLC, Phoenix LLC and Portland LLC each keep their own QuickBooks company. How does a deal closed for Phoenix become an invoice in Phoenix's file and a payment in Phoenix's account?
What has to line up for each deal?
Four things, and they all have to name the same entity:
| The deal is for | Invoice created in | Payment collected into | Payout lands in |
|---|---|---|---|
| Denver | Denver LLC's QuickBooks company | Denver LLC's Stripe account | Denver LLC's bank account |
| Phoenix | Phoenix LLC's QuickBooks company | Phoenix LLC's Stripe account | Phoenix LLC's bank account |
| Portland | Portland LLC's QuickBooks company | Portland LLC's Stripe account | Portland LLC's bank account |
The payment column is set by your processor's rules. Stripe says you can only associate each account "with the tax ID and legal entity of one business", and that separate legal entities need separate accounts. Each account can pay out to its own bank account. (Stripe: multiple separate accounts) So the three LLCs need at least three Stripe accounts.
The CRM is the one place where all three locations meet. Somewhere between the deal and QuickBooks, something has to choose the company.
Can HubSpot's QuickBooks integration bill several companies?
HubSpot's article on its QuickBooks Online app describes connecting a QuickBooks Online account: you click Connect to QuickBooks Online and enter your QuickBooks login. You then set up the sync and its filters. The article doesn't describe connecting more than one QuickBooks company, or choosing a company deal by deal. (HubSpot: connect HubSpot and QuickBooks Online)
If your entities each keep their own company, ask HubSpot how your setup would work before you connect. The HubSpot QuickBooks integration covers what the app syncs and what it leaves out.
The payment side has its own limit. A HubSpot account connects one Stripe account, or one instance of HubSpot payments. Can you connect multiple Stripe accounts to HubSpot? covers the options.
Can Pipedrive's QuickBooks app bill several companies?
Pipedrive's article describes installing QuickBooks from Tools and apps, then Invoicing, and saving your QuickBooks preferences for your Pipedrive company account. It doesn't say whether one Pipedrive account can connect more than one QuickBooks company. (Pipedrive: QuickBooks integration)
The app also creates the invoice and shows its status. It doesn't charge a saved card or bank account on a schedule. The Pipedrive QuickBooks integration has the details. Ask Pipedrive how several companies would work before you rely on it.
What about connector apps?
Some invoicing apps that sit between a CRM and QuickBooks connect more than one QuickBooks company. Ask the vendor how it picks the company for each deal, and whether a rep chooses it by hand.
That works, with one catch. A person picks the company, every time. When a rep picks Denver for a Phoenix deal, the invoice lands in the wrong file.
Questions to ask any connector:
- How is the company chosen? By the user at invoice time, or by a field on the deal?
- Which payment account collects it? An invoice in Phoenix's file paid into Denver's Stripe account is still a mismatch.
- What happens to the payment? Is it recorded against the invoice in the same company, as it's collected?
- What about a payment plan? Is each scheduled payment charged and recorded, or just the invoice created?
What about a billing tool with a template per entity?
Here each entity is set up once in the billing tool, with its own QuickBooks connection and its own payment account. A rule on each template says which deals belong to it, such as the deal's pipeline, a location field or the company record. The deal is matched to the template, and the template decides the company file and the payment account.
The difference from a connector is who decides. A rule set up once replaces a choice made on every invoice. The rule is only as good as the field it reads, so the location field on the deal has to be filled in, and filled in correctly.
What goes wrong when the routing is wrong?
- The invoice lands in the wrong company. Phoenix's sale shows as Denver's revenue. It has to be voided or deleted and created again in the right file.
- The payment is recorded in the wrong company. The invoice is in Phoenix's file but the payment shows up in Denver's, so Phoenix's invoice stays open and Denver has cash it can't match.
- The money lands in the wrong entity. A $1,108.33 payment for Phoenix collected into Denver's Stripe account pays out to Denver's bank. Now it's an intercompany transaction: a due-to entry in one set of books, a due-from in the other, then a transfer to settle it.
- Month end takes longer. Every misrouted item shows up again in the intercompany reconciliation, and the balances have to agree before the entities can be combined.
One mistake is a correction. A few a month across several entities is a standing job for whoever closes the books.
How do you check it's working?
After the first few deals, for each entity:
- Each invoice is in the company file for the entity that made the sale.
- Each payment is applied to that invoice, in the same file.
- Each Stripe payout matches deposits in that entity's bank feed. Reconciling Stripe payouts per location walks through one.
- No intercompany entries appeared that nobody planned.
Which option fits?
| Option | Who picks the company | What to check |
|---|---|---|
| The CRM's own QuickBooks app | Not described for several companies | Ask the CRM vendor how several companies would work |
| A connector app | The user, at invoice time | Wrong picks, and which payment account collects |
| A billing tool with a template per entity | A rule on the deal | The location field is always filled in |
| Separate CRM portals, one per entity | The portal the deal is in | Reps and reports split across portals |
Getting the entity right at the deal matters more than which accounting software you use later. Multi-entity accounting software covers what QuickBooks, Xero and the larger systems do once the money is in the books. One LLC per location covers the structure question itself, which is one for your CPA and attorney.
General information, not accounting or tax advice.
Changelog
- 22 October 2026: first published.
Payment plans built from the deal in HubSpot or Pipedrive, with each location paid into its own account and books.
Paycove bills every entity from the deal in your CRM and lands each invoice and payment in that entity's own QuickBooks Online file and Stripe account.
Book 15 minutes