One HubSpot portal can sell for several legal entities, but the entity has to be marked on every deal, usually with a pipeline per entity or a required deal property. HubSpot's knowledge base doesn't describe enforcing a quote template per pipeline. HubSpot's workflow actions let you pick which QuickBooks account an invoice is created in, so a workflow can route each entity's invoices to its own company. Payments are the hard limit: a HubSpot account connects one Stripe account, so every entity's money lands in the same place.
Checked against HubSpot's knowledge base on 22 October 2026. HubSpot changes these tools often, so the changelog at the end records each update.
A group with several legal entities often runs sales from one HubSpot portal. One team, one contact base, one set of pipelines. Then the deal closes and each part of the money side asks the same question: which company is this for?
This post walks through that question the way RevOps teams ask it in the HubSpot Community. Each answer comes from HubSpot's own knowledge base. The community threads are linked for the questions only. HubSpot Brands, business units and multi-account management covers the brand side. This post is about legal entities, which a brand doesn't separate.
Throughout, the example is a group with three LLCs, Denver LLC, Phoenix LLC and Portland LLC, selling from one portal. Each LLC is its own legal entity, with its own bank account and books.
Is it possible to manage three separate companies on one HubSpot?
That's the title of a community thread about three businesses that wanted their own teams and user access in one portal.
There are two ways to set it up, and they suit different groups:
- One portal for every entity. The entities share contacts, pipelines and users. You mark each deal with its entity and work out the quote, invoice and payment for each one. The rest of this post is about this setup.
- A portal for each entity, joined with multi-account management. The main account needs an Enterprise subscription and can connect up to 29 more accounts, each on Professional or Enterprise. HubSpot's article on it doesn't mention payments, invoices or quotes. (HubSpot: set up multi-account management)
A portal per entity keeps each company's money apart because each portal has its own payment setup. It also means a paid subscription for every entity. For a group with one sales team, that's a lot to pay to separate the money alone.
How do you know which legal entity sold or invoiced a deal?
A community thread on telling apart deals owned by several legal entities asks the same thing: which entity sold and invoiced each deal, and to which customer.
HubSpot gives you two ways to mark it:
- A pipeline per entity. Custom pipelines need Starter or higher. Restricting a pipeline to a team needs Professional or Enterprise. (HubSpot: set up and customize pipelines)
- A custom deal property. You can create custom properties on every plan, including a dropdown select with one option per entity. (HubSpot: create and edit properties)
A property can also be required at a stage. HubSpot's pipeline article says conditional stage properties show when a record is moved to a stage, and a required one has to be filled in before the record can be saved. So "Selling entity" can be required before a deal reaches the quote or closed won stage.
Pick one marker and use it everywhere. Every step below depends on that one field being right.
Can quote templates be enforced per entity?
A community thread on US and French quoting asks exactly this: whether a quote template can be enforced for each entity's deals.
HubSpot's own article on quote templates matches that. It describes publishing a template so that users in the account can build quotes with it, and assigning a template to a brand. It doesn't describe a default template per pipeline or limiting a template to a team. Seller details on the quote come from the user who creates it, and the seller's company comes from the account's company information, though both can be updated on the template. (HubSpot: create quote templates)
Quotes and quote templates need Revenue Hub Professional or Enterprise. HubSpot invoicing and quotes covers how quotes work from a deal.
Can invoices carry each entity's own company details?
A community idea asks for invoices from several entities within one HubSpot account.
HubSpot's invoice article covers brands. If you use Brands, which needs Marketing Hub Enterprise, you can assign an invoice to a brand and it takes that brand's logo, colours and fonts. You can't customise the brand for invoices created from quotes. (HubSpot: create and manage invoices) The article describes the look of the invoice. It doesn't describe a separate legal name, address or tax ID for each brand. If each entity's invoice has to carry its own legal details, confirm with HubSpot how that would work before you rely on it.
Which QuickBooks Online company does the invoice sync to?
Groups with an LLC per location often keep a QuickBooks Online company for each entity. QuickBooks multiple companies explains how that works.
HubSpot's QuickBooks Online article describes connecting a QuickBooks account. It doesn't cover choosing a company file deal by deal. (HubSpot: connect HubSpot and QuickBooks Online) HubSpot's workflow actions do take an account. The "Create a QuickBooks invoice" action asks which QuickBooks account to create the invoice for. Workflows need a Professional or Enterprise subscription. (HubSpot: use QuickBooks actions in workflows)
Community threads on several QuickBooks accounts and QuickBooks Online with multiple companies discuss the same setup.
So in the example, a workflow reads the deal's entity field and sends Phoenix LLC's invoice to Phoenix LLC's company. If the field is wrong, the invoice lands in the wrong books. The HubSpot QuickBooks integration covers what syncs and what doesn't, and the HubSpot Xero integration covers the Xero side.
Which Stripe account gets paid?
This is where one portal stops. A HubSpot account can't have more than one Stripe account connected, and if you use Brands, every brand uses the connected one. (HubSpot: connect your Stripe account) HubSpot payments has the same shape: one instance per HubSpot account, shared by every brand. (HubSpot: set up HubSpot payments)
Stripe, for its part, requires a separate account for each legal entity. (Stripe: billing for a multi-entity business) So Denver LLC, Phoenix LLC and Portland LLC need three Stripe accounts, and the portal can connect one.
There is a community idea asking HubSpot to connect several Stripe accounts to one portal. Can you connect multiple Stripe accounts to HubSpot? sets out the three options: share one account, run a portal per entity, or add an app that routes each deal's payment.
What does reporting by entity look like?
Reporting follows the marker on the deal. HubSpot's custom report builder, on Professional or Enterprise, can break a report down by a field, so a deal report can be split by the selling-entity property. (HubSpot: create reports with the custom report builder) The revenue analytics suite has invoice reports such as balance due and invoice status, and payment reports such as total payment volume. Its reports can be grouped or broken down by a selected property, though the filters vary by report. (HubSpot: create reports in the revenue analytics suite)
Those reports describe the deal side. The money side is different. If every entity's payments go through one Stripe account, they reach one bank account, and the split by entity has to be made in the books afterwards. When each entity has its own Stripe account, Stripe's own guide suggests exporting every account's data to a warehouse for a combined view. (Stripe: billing for a multi-entity business) Reconciling Stripe payouts per location covers the month-end side.
What should you settle before you set it up?
- The entity marker. A pipeline per entity or a required deal property. One field, set on every deal.
- Quotes. How the right template gets picked, given that the knowledge base doesn't describe a default per pipeline.
- Invoice details. Whether a brand's look is enough, or each entity's legal name and tax details have to appear.
- Books. Which QuickBooks or Xero company each entity's invoices reach, and the workflow that routes them.
- Payments. Where each entity's money lands, since the portal connects one Stripe account.
- Structure. Whether each location really is its own LLC. One LLC per location, or one for all? covers the trade-off.
For schools, clinics and service businesses with an LLC per location, the money side is often the step that decides the setup.
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 routes each deal in one HubSpot portal to the right entity's template, Stripe account and QuickBooks or Xero file, using rules on each template.
Book 15 minutes