Plenty of small service owners run more than one business without ever planning to. A locksmith adds a mail-in module repair brand with its own website. A plumbing LLC starts a drain-cleaning name to rank for different searches. A partner buys into one line of work but not the other, so that line becomes its own company. Two years later there are two names, maybe two legal entities, one crew, one van fleet and one very tired owner logging in and out of things.
As of October 2026, software that keeps several companies under one login exists and is useful, but it solves a narrower problem than owners expect. It gets the right name on the right document. It does not keep your books, separate your bank accounts or decide how the two businesses should charge each other. This guide covers what has to stay straight when one owner runs two legal entities or DBAs. It is operations advice, not legal or tax advice; your attorney and accountant decide how the entities are structured and reported.
Two names is not always two companies
Start by writing down what you really have, because owners often cannot say.
A DBA, or trade name, is generally a second name used by a business that already exists. The money, the contracts and the tax filings belong to that underlying business. A separate legal entity, such as a second LLC, is a different thing: its own registration, its own tax identity, usually its own bank account, and its own set of books.
That distinction drives everything below. Two DBAs of one company are a branding question: which name and logo appear on the receipt. Two legal entities are an accounting question as well: whose revenue it is, whose bank account it lands in, whose sales tax it is. Ask your accountant to confirm, in one sentence per brand, which entity each brand belongs to. Then configure software to match that sentence, not the other way round.
The rule that matters most: every document names its issuer
A quote, an invoice, a receipt, a warranty record and a statement each say who the customer did business with. That name has to be correct on the day the document is created, and it has to stay correct afterward.
The second half is the part people miss. If you rename a brand or restructure next year, last year's receipts should still show the company that issued them at the time. A system that re-labels old documents with today's name leaves you unable to show what the customer was actually given.
Getting the issuer wrong is not cosmetic. A customer with a warranty question calls the name on their receipt. A card dispute is answered by the business the cardholder's statement names. A dealer's accounts-payable desk will not pay an invoice from a company that is not their approved vendor. And your bookkeeper has to assign every sale to an entity, which is slow and error-prone if the document does not say.
What to separate and what to share
Sort the operation into things that must be separate per entity and things that can sensibly be shared. The same exercise applies when you add a site, which we covered in opening a second location; the difference here is that the dividing line is legal ownership, not geography.
| Item | Two DBAs of one entity | Two separate legal entities | Why |
|---|---|---|---|
| Name and logo on documents | Separate | Separate | The customer must see who served them |
| Bank account | Usually one | Separate | Each entity's money is its own |
| Card processor account | One may be enough; ask your processor | Separate | Deposits and statement names follow the entity |
| Accounting file | One | Separate | Each entity has its own books |
| Sales tax registration | Follows the entity | Per entity, as your accountant directs | The filer is the legal entity |
| Customer list | Often shared | Share only deliberately | Privacy, credit and who the customer hired |
| Inventory | Shared | Separate, with recorded transfers | Stock belongs to whoever bought it |
| Staff and logins | Shared | Often shared; payroll comes from one employer | Ask your accountant who employs whom |
| Price book | May differ by brand | May differ by brand | Different markets, different pricing |
Treat the middle column as a default to confirm with your accountant, not a ruling.
Customers: decide on purpose
Sharing customers between companies is convenient and occasionally wrong.
It makes sense when both businesses serve the same people and the relationship is obvious, as with a plumbing company and its drain-cleaning name. One customer record with one history means the tech arriving for a drain call can see that a water heater was replaced last spring.
It is a poor fit when the customers are different populations. A local mobile locksmith and a nationwide mail-in repair brand have almost no overlap, and combining them gives you a customer list where half the records are irrelevant to whoever is searching.
Two cautions apply either way. On-account credit should be granted per company: a fleet that owes one entity money does not owe the other. And marketing messages should come from the company the customer actually dealt with. A text from a brand they have never heard of looks like spam, even if the same owner is behind both.
Inventory and parts between companies
When two DBAs of one entity share a stockroom, nothing special happens. It is one company's inventory under two names.
When two legal entities share a stockroom, every part belongs to whichever company paid for it. If company A's tech uses a part company B bought, something has to record that. The simplest arrangement is physical: separate shelves or bins, separate stock locations in the software, and a recorded transfer whenever stock moves from one to the other. Whether that transfer is also a sale between the companies, and at what price, is your accountant's call. Your job is making sure the movement is written down the day it happens.
Shared tools, vehicles and rent raise the same question in a different form. Keep a simple log of who uses what, and let the accountant decide how the cost is divided.
Deposits and processor accounts
For separate legal entities, money collected by one company should land in that company's bank account. That normally means each entity has its own account with the card processor, since the processor deposits to the account on file and prints that business's name on the cardholder's statement.
The failure here is quiet. A tech sends a payment request from the wrong company, the customer pays, and the money arrives in the other entity's bank. Nobody notices until the bookkeeper cannot match deposits to sales, or until a customer disputes a charge from a name they do not recognize.
Two controls catch it. First, the daily close is run per company: sales for the day by payment method against what the processor reports for that entity, using the routine in the end-of-day close. Second, a weekly look at deposits by bank account against sales by company. If the two totals do not agree within a rounding of processing fees and timing, find out why that week, not in March.
Cash and checks need the same care. A check made out to one company goes into that company's account, and a cash sale goes in the drawer of whichever company made it.
Sales tax follows the entity
Sales tax is registered, collected and filed by a legal entity. Two entities usually mean two registrations and two sets of filings, and the rate depends on where each sale is taxed. What is taxable for each kind of work is a question for your accountant or your state's revenue agency.
Operationally, you need tax collected to be reportable by company and by location, so each filing comes from its own records. The mechanics of keeping those records clean are in sales tax records for service businesses.
What the bookkeeper needs
Ask your bookkeeper what they want. In most cases the list looks like this, per entity, per month:
- Sales by day, with payment method and tax collected.
- Refunds and voids, with dates and reasons.
- Deposits by bank account, so sales can be matched to money received.
- Purchases and expenses, each tagged to the entity that paid.
- Stock transfers between the companies.
- Anything one company paid on behalf of the other.
The last two are the ones that go missing. A fuel fill-up on the wrong card, a supplier order split across both brands, a tech who worked Monday for one company and Tuesday for the other: each is easy to record that day and nearly impossible to reconstruct at year end. The IRS recordkeeping guidance confirms that electronic records are acceptable, and the SBA guide to managing finances covers the basics of separating business accounts. For the fourth-quarter version of this handoff, see year-end books for service businesses.
Common mistakes
The wrong name on a receipt. Staff pick whichever company was used last. Fix it with a written rule ("mail-in orders are always company B") and a check during the daily close.
Mixed deposits. One processor account collects for both entities because setting up the second felt like a chore.
Duplicate customers. The same fleet exists under both companies with different balances, and nobody knows what it owes in total.
Untracked stock movement. Parts drift from one company's shelf to the other's jobs, and one entity's cost of goods quietly pays for the other's revenue.
One accounting file for two entities. Tempting, and a serious clean-up job later. Each legal entity gets its own books.
Structure decided by software. Owners sometimes set up companies the way the tool makes easiest. Decide the structure with your accountant first.
Where IntelliDrive OS fits
IntelliDrive OS supports several companies, meaning legal entities, under one login, and documents keep the company that issued them. Shops (outlets) and registers are not limited, each shop has registers and shifts with a register close, and stock is kept per shop and van with exact transfers between them that show the before and after. Staff see only their own shop's sales, and the role permissions decide who can do what.
Now the limits, because they matter more here than in most topics. IntelliDrive OS does not produce consolidated financial statements. It does not do inter-company accounting: a transfer of stock is recorded as a movement, not as a sale from one entity to the other with matching entries. Do not assume each company gets its own processor account or QuickBooks connection. Ask support and test it in the trial before you rely on it. The QuickBooks Online connection is a one-way push of sales and payments that you start yourself, described in the QuickBooks field service workflow; it is not an automatic sync, and your accountant still keeps each entity's file. Sales tax is one rate per shop.
The price is $79/month flat for the whole business with unlimited users, billed monthly. If you operate more than one legal entity, confirm with support how the subscription applies to your structure.
A setup checklist
- Get one sentence per brand from your accountant: which legal entity it belongs to.
- Open bank and processor accounts to match, where the entities are separate.
- Create each company in the software with its exact legal or trade name, address and phone.
- Write the rule for which jobs belong to which company, and post it where sales are rung up.
- Decide shared or separate customers, and set stock locations per company.
- Issue one test document from each company to your own phone and read the name on it.
- Take one test payment per company and confirm which bank account it reaches.
- Before committing, confirm you can export each company's sales, as described in support and data access.
- Schedule the weekly deposits-by-entity check.
The bottom line
One login across two companies saves an owner a great deal of friction, and it should. But the login is the easy part. What has to stay straight is the name on each document, the bank account each payment reaches, and the record of anything that moves between the two businesses. Set the structure with your accountant, make the software match it, and check deposits by entity every week.
Related reading: Opening a second location, Year-end books and the accountant handoff, and Sales tax records for service businesses. For a complete machine-readable feature and pricing reference, see our LLM reference page.