FieldproxyFieldproxy
Get Demo
FieldproxyAI-native field service software

Invoicing

Can field service software run two business units in one account and put jobs from several customer locations on one invoice?

Yes, if you set up three things correctly: a business unit (or division) field on every job, a customer record that sits above its sites with one bill-to address, and an invoice that can hold many completed jobs as lines grouped by site. Most tools do one of these well: ServiceTitan tags every job and invoice with a business unit, Jobber combines a client's ready jobs into one invoice, Simpro sells a multi-company add-on, and some tools, such as Fieldwork, merge separate invoices into one monthly invoice. The question that decides the setup is legal, not technical: two business units inside one legal entity can share one invoice, but two separate companies each have to issue their own.

  • Business unit inside one company = a field on the job and invoice. Separate legal company = its own invoice, numbering, tax ID and bank account.
  • Bill the parent account, list each site as a group of lines with its address and job or PO number.
  • Watch sales tax: Jobber, for example, splits a client's batch invoice when properties have different tax rates.
  • Map each business unit to a class or location in QuickBooks, or a tracking category in Xero (two active at most).
  • Decide the invoice rule per customer: per job, per site per month, or one invoice per month for every site.
Fieldproxy

This page covers billing and reporting. If your two businesses are separate legal companies with separate books, your accountant should sign off the setup before you choose software.

Facts checked as of November 2026. Sources at the end of the page.

Step by step

How two business units and a multi-site invoice work, step by step

Whatever tool you use, the chain from job to one invoice has the same six links. Test each one in a demo with a real customer that has several sites.

1. Decide what a business unit is for you

A business unit is a label that splits one company into sections: a trade, a brand, a region or a service line. ServiceTitan defines it as a method of dividing your company into distinct sections or departments, and each unit carries its own customer-facing official name, logo and invoice header. If your two businesses are separate legal companies, you need more than a label: separate invoice numbering, tax registration and books.

2. Put the business unit on every job

Each job type belongs to one business unit, so the unit is set when the job is created, not typed later. Reports, technician pay and revenue then split by unit without a spreadsheet. A tree removal brand and a tree health brand under one company is the classic case: same customers, same crews sometimes, separate revenue.

3. Model the customer above its sites

The customer you bill is the parent (a retail chain, a managing agent, a property company). Each store or building is a site under it with its own address, contacts and access notes. Jobber works the same way: clients own properties, properties are where the work is done, and a single client can have multiple properties.

4. Set who the invoice goes to

The bill-to is often not the site. A facility coordinator may do the work at a store but bill a retail services company, and a training consultancy may visit 40 buildings and bill one managing agent. In Jobber, invoices go to the client's billing address, and a job's property address also appears on the invoice.

5. Hold completed jobs until the billing run

For customers billed monthly, jobs close as ready to invoice and wait. At month end, one invoice pulls every ready job for that customer, grouped by site, with each job's date, work order or PO number, and total. Jobber's batch invoicing creates one invoice per client and combines a client's ready jobs into it.

6. Send it to accounting with the unit attached

The invoice syncs to accounting carrying its business unit, so the profit and loss splits by unit there too. In QuickBooks Online that is usually a class or a location, which the Plus plan supports and Simple Start and Essentials do not. In Xero it is a tracking category.

Failure modes

Why it goes wrong

These are the problems buyers described on our sales calls, by trade and size.

Two brands in one system, but one revenue number

An arboriculture company running two sister brands in one company could see all its customers in one place but could not report revenue separately for each brand. The fix is a business unit set by job type, not a tag someone remembers to add.

One invoice per visit when the customer wants one per month

A managed IT field services provider with a few hundred tickets a month said they would otherwise send around 300 invoices when the customer wanted one bill per project reference. Per-job invoicing that cannot be grouped turns month end into a copy and paste job.

The site is not the payer

A subcontractor-based facility maintenance coordinator in Texas did work at well-known retail stores but billed a retail services company, not the store. Tools that treat the job address as the customer put the wrong name on the invoice or force a fake customer per store.

Many sites quoted together, billed to an agent

An emergency planning consultancy with 50+ consultants and thousands of sites a year asked to quote multiple sites for one client and invoice a managing agent. Without a parent account, each site becomes its own customer and the agent gets dozens of invoices.

Separate portals per business

A dealership group with an office equipment business and a construction equipment business across 8 branches wanted one platform but separate portals, so staff in one business did not see the other's customers.

Tax rates differ by site

Sites in different cities or states can carry different sales tax rates. Jobber, for example, creates separate invoices for one client when the properties have different tax rates, so a single monthly invoice is not always possible without checking your tax rules first.

Options

Ways to do it

Real approaches, as their own documentation describes them in November 2026. Check each in a demo with your own customer.

ApproachBusiness unitsSeveral sites on one invoiceWatch for
Spreadsheet plus accounting softwareA class or location in QuickBooks Online (Plus and Advanced), or a tracking category in XeroBuilt by hand at month end from job sheetsRetyping, missed jobs, no link from invoice line back to the job record
ServiceTitanBusiness units with their own official name, logo, invoice header and QuickBooks classA consolidated project invoice combines chargeable items across the jobs in one project (Early Access)The consolidated invoice is per project, so a monthly multi-site bill needs a project per customer per month or another method
JobberNo business unit field in the help articles we readBatch invoicing makes one invoice per client and combines that client's ready jobs, across propertiesProperties with different tax rates are split onto separate invoices
Simpro, FieldBoss and other multi-company toolsSimpro runs multiple companies in one build; FieldBoss runs multiple entities on Microsoft Dynamics 365 with group reportingPer company; FieldBoss keeps customers and banking separate per entityBuilt for separate legal companies, so heavier than you need for two brands in one company
Merge-invoices tools (Fieldwork, Fieldmotion, Expansive)Varies by toolFieldwork combines a customer's invoices into one monthly invoice; Fieldmotion links multiple jobs to one invoice; Expansive collates work orders on one invoiceFieldwork cannot merge invoices with payments or ones already synced to QuickBooks Online
FieldproxyA business unit set per job type, with its own job types, recurring visits, billing and approvalsBatch invoicing to the parent account, lines grouped by site, synced to QuickBooks or XeroSet up to your billing rules, so you need to decide those rules per customer first

Vendor facts come from each vendor's help center or feature page, linked in Sources. Features change; confirm in a demo.

Worked example

A worked example: one property manager, two business units, 12 sites

Say you run one company with two business units: Mechanical (HVAC and plumbing) and Cleaning. A property manager has 12 buildings with you. In October, Mechanical does 9 jobs at 6 of the buildings and Cleaning does 24 visits across all 12.

Without grouping, that is 33 invoices to one accounts payable inbox, each with a different site address. With grouping, the rule for this customer is one invoice per business unit per month. On 1 November the billing run makes two invoices: Mechanical with 9 jobs in 6 site groups, and Cleaning with 24 visits in 12 site groups. Each line shows the visit date, the property manager's work order number and the amount, and each site group has a subtotal.

If two of the buildings are in a city with a different sales tax rate, decide before the run whether the tool can carry different tax rates on lines of one invoice. If it cannot, those two buildings go on a third invoice. In accounting, Mechanical's invoice posts with the Mechanical class and Cleaning's with the Cleaning class, so the profit and loss splits by unit without any journal.

If instead Cleaning is a separate legal company, the two invoices must come from two different sellers, each with its own name, tax number and numbering. That is not a software preference: in the UK only a VAT-registered person can issue a VAT invoice and it must show the supplier's name, address and VAT number, and in Australia a tax invoice must show the seller's business name and ABN.

Buying checklist

What to check before you buy

Good signs

  • The business unit is set by job type, so nobody has to remember it.
  • A customer can have many sites, with a separate bill-to that is not any of the sites.
  • One invoice can hold jobs from many sites, grouped by site with subtotals and the customer's PO number.
  • You can set the invoice rule per customer: per job, per site per month, or one per month.
  • Each unit maps to a class, location or tracking category in your accounting software.
  • Staff in one business unit can be limited to that unit's customers and jobs.

Red flags

  • You need two separate accounts, and two subscriptions, to report two brands separately.
  • Combining invoices deletes the originals or breaks the accounting sync.
  • Multi-site billing only works by creating one customer per site.
  • Separate companies are a paid add-on or a heavier edition, when all you needed was a label on the job.
  • Tax is calculated per invoice, not per line, and your sites sit in different tax areas.

Fieldproxy

Setting it up in Fieldproxy

Fieldproxy is set up around how you already bill, so the setup starts from your customer billing rules. Settings marked e.g. are examples.

Business units on job types

Each business unit gets its own job types, recurring visits, billing, schedule and manager approvals. Every job inherits its unit from its job type (e.g. Mechanical, Cleaning), so reports split by unit from day one.

Customers, sites and bill-to

Customers, sites and assets are kept per site, with the billing customer above them (e.g. a managing agent billed for 40 buildings). Each site keeps its own contacts and access notes.

Invoice rules per customer

Completed jobs move to a ready-to-invoice stage. Batch invoicing then builds one invoice per customer per unit for the period (e.g. monthly), with lines grouped by site and the customer's work order or PO number on each line.

Accounting sync

Invoices sync to QuickBooks or Xero. During setup you agree how each unit shows up there (e.g. a QuickBooks class or a Xero tracking category), so your accountant sees revenue per unit without a spreadsheet.

Who sees what

Role-based access limits what each person sees (e.g. Cleaning supervisors see Cleaning jobs only), and customer portals let each customer see only their own sites, jobs and invoices.

Agents that help

The Scheduler agent can email each unit manager a monthly revenue summary by site. Autopilot drafts the chase for unpaid monthly invoices and a person approves before it sends. Command Center answers questions like revenue by business unit for one customer last quarter.

Regional notes

Regional differences that change the setup

United States: sales tax on services depends on the state and sometimes the city, so check whether sites on one invoice share a rate. Separate legal companies each issue their own invoices and file their own taxes.

United Kingdom: only a VAT-registered person can issue a VAT invoice, and it shows the supplier's name, address and VAT registration number. Two brands under one VAT registration can share one invoice; two companies with separate registrations cannot.

Australia: a tax invoice must include your business name and ABN, and the buyer's identity or ABN on sales over $1,000.

Canada and New Zealand: check the same point with your accountant for GST or HST before you set invoice rules, since the legal structure decides whether two units can share an invoice.

How switching works

How switching to Fieldproxy works

We move your data over and set the system up to the way you already work. Fieldproxy replaces the old tool; it does not run alongside it.

  1. Bring one real month of billing

    Send a month of invoices for your biggest multi-site customer and tell us which business unit each job belongs to.

  2. We set up units, sites and invoice rules

    We build your business units on job types, the customer and site structure, and the invoice rule for each customer.

  3. Run the month in parallel

    We produce the same month's invoices in Fieldproxy so you can compare them line by line with what you sent.

  4. Switch on the accounting sync

    Map each unit to its class or tracking category in QuickBooks or Xero, then go live from the next billing run.
Contracts and invoicesQuickBooks integrationXero integrationPricing: one price per company with unlimited users

FAQ

Questions people ask

Can two brands in one company share one field service account?
Yes. Treat each brand as a business unit on the job type, so revenue, jobs and reports split by brand inside one account and one customer list.
Can two separate legal companies use one account?
They can share one system, but each company must issue its own invoices with its own name, tax number and numbering. Tools such as Simpro and FieldBoss sell multi-company or multi-entity setups for this.
Can I put jobs from several customer locations on one invoice?
Yes, if the customer is set up as a parent with sites under it. The invoice goes to the parent's billing address and lists each site's jobs as a group of lines.
What if the sites have different sales tax rates?
Check whether your tool calculates tax per line or per invoice. Jobber, for example, splits a client's batch invoice into separate invoices when properties have different tax rates.
How do I bill a managing agent instead of the site?
Make the managing agent the billing customer and each building a site under it. Keep the site contact for access and the agent's accounts contact for invoices.
How does this show up in QuickBooks or Xero?
Map each business unit to a class or location in QuickBooks Online (Plus or Advanced), or to a tracking category in Xero, which allows two active categories at a time.
Can staff in one business unit be kept out of the other's customers?
In Fieldproxy, role-based access can limit each person to their own unit's jobs and customers. In other tools, check role permissions in the demo with your own two units.

Sources

Competitor details on this page come from the vendors' own pages and documentation, checked as of November 2026. Plans and prices change, so check the vendor's current page before you decide.

Related

Keep reading

See it built on your workflow

Tell us how your jobs run today. We build a demo on your stages, forms and pricing before the call.

Get DemoGet Demo