Business units

Business units let one Suprata account run multiple sub-brands or divisions. They affect how invoices are branded, how reports filter, and how data syncs to QuickBooks. Skip them if you don't need them.

Updated 3 days ago 16 views settings quickbooks business-units multi-brand reporting

Business units

A business unit is a sub-brand or division inside one Suprata tenant. Examples: ACME Plumbing and ACME HVAC sharing one office, one set of staff, but two different brands customers see; or a company with Service and Installation divisions that need separate revenue reporting.

If you only run one brand, skip this feature entirely. Setting up business units when you don't need them adds an extra dropdown on every invoice for the rest of time, and there's no benefit.

If you do run multiple brands or need clean per-division reporting, business units are the right tool — but they affect more than you'd expect, so set them up early.

When you'd use them

  • Multiple brands under one ownership. "ACME Plumbing" and "ACME HVAC" share staff and office but have different logos and customer-facing names.
  • Distinct divisions that need separate financials. Service vs. Installation, Residential vs. Commercial, Coastal vs. Inland.
  • Franchise-style operations where each unit needs its own brand presentation but they share back-office staff.
  • Compliance separation. A regulated division (e.g., HVAC requiring trade-license display on invoices) and an unregulated one needing different invoice templates.

When not to use them:

  • A single business with multiple service categories (HVAC service + HVAC installation isn't two business units; it's one brand with two job types).
  • Branches in different geographies but same brand (that's a Team or a Location, not a business unit).
  • Different price tiers (residential vs. commercial pricing isn't a unit; it's a customer segment / pricing strategy).

The threshold: would a customer interacting with one of your divisions notice a different name, logo, or invoice template than a customer of the other? If yes, business units. If no, you don't need them.

What they actually affect

When business units are turned on, every record that "belongs" somewhere can be tagged with a unit. The tagging propagates through:

  • Invoices — each invoice belongs to a unit. The customer-facing PDF can be branded per unit (different logo, different "From:" address, different terms).
  • Jobs — jobs belong to a unit. Reports filter accordingly.
  • Service agreements — each agreement belongs to a unit.
  • Reports — most reports add a "Business Unit" filter so you can run revenue, A/R, sales by unit cleanly.
  • QuickBooks sync — the unit usually maps to a QB Class. Your bookkeeper can then run P&L by Class, which is the QB-side equivalent of by-unit reporting.

The unit doesn't change operations — staff, the calendar, the dispatch board, the customer database are all shared. It changes attribution and branding.

Where to manage them

Sidebar: Settings → Business Units.

The screen lists existing units. Each unit has a name, an optional code (often used as the QB Class name), a logo override, address overrides, and any per-unit invoice-template settings.

Company Settings — the timezone and main brand info; business units extend from here

Note: the screenshot shows the main Company Settings screen; business unit configuration is reached from here as well as from the dedicated business-units settings area.

Setting one up

For each unit:

  1. Name — the customer-facing brand name. "ACME HVAC".
  2. Code — short identifier, often used for QuickBooks Class mapping. "HVAC".
  3. Logo — uploaded brand logo. Used on invoices, statements, and emails branded for this unit.
  4. Address — if the unit operates from a different address than the main company.
  5. License / regulatory text — for regulated trades, the trade license number or other required text on invoices.
  6. Invoice template — which template (if you have multiple) is used for invoices in this unit.
  7. Default terms / payment processor — sometimes per-unit, sometimes shared.

The pattern is: start the unit with the parent company's defaults, then override only what's actually different. Don't re-fill every field; let inheritance carry the shared bits.

QuickBooks integration

Business units are most powerful when they map cleanly to QuickBooks Classes:

  1. In QuickBooks, turn on Class Tracking (Account and Settings → Advanced → Categories).
  2. Create one Class per Suprata business unit, named to match.
  3. In Suprata's QB integration settings, enable "Map business unit to QB Class".
  4. Each invoice that syncs over carries its unit code as the Class.
  5. In QuickBooks, run P&L by Class — instant per-unit financials.

If you're not on QuickBooks Online (or don't want Class Tracking), you can still use business units for in-Suprata reporting; the QB mapping is optional.

Decisions before you set them up

Is each unit really a separate brand from the customer's perspective?

If a customer of "ACME HVAC" gets an invoice branded "ACME Plumbing" because the office staffer pulled up the wrong template, the customer is confused. Each unit's branding has to be set up consistently. If you can't commit to that consistency, maybe two units isn't right; maybe it's one brand with two service lines.

Are jobs always assignable to one unit?

Some businesses do work that legitimately spans units — a residential service call from the same crew that also does commercial new-construction. If a job is hard to attribute to one unit, business units are a poor fit; consider tagging or job categories instead.

Does your accounting / payroll structure mirror the units?

If your bookkeeper runs P&L by department in QuickBooks anyway, units that match those departments make life easier. If your accounting is one P&L per legal entity, units may not give you what you want; you might need separate Suprata tenants instead.

Will the customer ever interact with both units?

If yes, the customer record probably belongs to both units (or to "the company" rather than a specific unit). That's fine — the customer doesn't have to belong to a unit; only the invoice does. But it means staff have to be careful which unit they invoice from for which engagement.

Common mistakes

  • Setting up business units "for the future" before you actually have multiple brands. Extra clicks on every invoice for a feature you're not actually using. Wait until the second brand is real.
  • Treating geographic branches as business units. A "Houston Office" and a "Dallas Office" of the same brand aren't units; they're locations or teams. Use a different feature.
  • Inconsistent branding application. Half your ACME HVAC invoices go out branded ACME (parent) because someone forgot to set the unit. Customers notice. Train staff to set the unit on every job.
  • Mapping to QuickBooks Classes inconsistently. Suprata says "HVAC", QuickBooks says "HVAC Service" — sync errors or messy reports follow. Make the names match exactly.
  • Forgetting to set up the unit-specific invoice template. Your customer gets an invoice with the parent company's logo and address even though they're an ACME HVAC customer. Each unit needs its template tested before going live.
  • Trying to use business units for pricing differentiation. Different price lists per unit isn't really what units are for; consider price-list-per-customer-segment instead.
  • Setting up units after a year of operation without unit tagging. Now your historical data is "no unit" and your new data is properly tagged, and reports straddle the change awkwardly. If you're going to use units, set them up early; retrofitting is painful.

After setup — verify

Before going live with business units:

  1. Create a test job under each unit.
  2. Generate an invoice from that job.
  3. Open the PDF and confirm the branding matches the unit (logo, name, address).
  4. Sync the invoice to QuickBooks (if integrated) and verify it lands with the correct Class.
  5. Run a Sales by Business Unit report and confirm the test invoice appears under the right unit.

If any of those don't work as expected, fix the unit configuration before letting real invoices flow.

Common mistakes (continued)

  • Not training staff on which unit to use when. Especially for office staff who aren't field-facing — they need a clear rule for "an invoice for [this kind of work] goes under [this unit]".
  • Letting the unit dropdown be set wrong on a recurring invoice. Recurring invoices inherit the unit from the source. If the source was wrong, every recurrence is wrong; it's much harder to fix in retrospect than upfront.

Related articles