How to Track a DBA's Income and Expenses Separately in QuickBooks

Imagine a company that has operated one business for several years. The owner launches a new DBA to offer a different service, ABC Construction LLC, DBA: ABC Millwork. The new DBA uses the same bank account, has its own customers, generates its own revenue, and carries its own project-specific costs.

Not necessarily. The appropriate setup depends first on the legal and tax structure, then on the level of financial reporting the business actually needs. For a DBA that remains part of the same legal entity, the goal may be to create separate financial visibility, not to duplicate the entire accounting system.

What a DBA Actually Means

A DBA Is a Business Name, Not Automatically a Separate Legal Entity

DBA stands for "doing business as." It generally represents a name under which an existing business operates, Smith Holdings LLC, DBA: Smith Home Services, for instance. The DBA itself does not automatically mean a new LLC or corporation exists.

Don't decide your QuickBooks structure based solely on the fact that you registered a DBA. The first question is whether the DBA is part of the same legal entity or a separate one.

DBA vs. Separate Legal Entity: Why the Difference Matters

Same Legal Entity, Different Business Line

If ABC LLC operates both a Construction division and a Millwork DBA under one entity, management may simply want to track the two business activities separately for reporting purposes, without any legal separation involved.

Separate LLC or Corporation

ABC Construction LLC and XYZ Millwork LLC, by contrast, are different entities. The accounting requirements are fundamentally different, and QuickBooks itself states that each business should have its own company file when maintaining separate businesses. When the legal or tax structure isn't clear, this is exactly the kind of question worth confirming directly with the company's CPA or tax professional before setting up the books one way or the other.

When You Can Track the DBA Inside the Existing QuickBooks File

If the DBA is simply a business segment of the same entity, one accounting file with additional tracking dimensions is often sufficient. QuickBooks Desktop's class tracking is specifically designed to track different parts of a business, such as departments, locations, properties, and business units.

In practice, this means a single QuickBooks company , ABC Construction LLC, with classes for Construction and Millwork DBA. Transactions tied to the Millwork side of the business are then assigned to the Millwork class, keeping everything in one file while still producing separate reporting.

How to Use QuickBooks Classes to Track the DBA

Step 1  Turn on Class Tracking

Classes exist to let a single company file report on distinct parts of the business without maintaining separate books for each. In QuickBooks Desktop, class tracking is enabled under Edit → Preferences → Accounting → Company Preferences, via "Use class tracking for transactions." QuickBooks also offers an option to prompt users to assign a class on every transaction, reducing unclassified entries later.

Step 2  Create a Class for the DBA

A simple class list, Main Business and Millwork DBA, is usually enough. Keep the structure simple; creating dozens of classes tends to make reporting harder to interpret, not easier.

Step 3  Assign DBA Revenue to the Class

Millwork sales, installation revenue, design fees, and project revenue should each be tagged consistently to the correct class. Each transaction needs to identify the relevant business segment every time, not just when it's convenient.

Step 4  Assign Direct Expenses to the DBA

Materials, subcontractor costs, direct labor, delivery, project-specific supplies, and equipment used specifically for the DBA all need the same consistent tagging. This step is critical,  a DBA P&L isn't useful if revenue is separated but costs aren't.

How to Handle Shared Expenses Between the Main  Business and DBA

Some expenses belong clearly to the DBA. Others benefit the entire company, and treating them the same way distorts the resulting report. $8,000 of millwork materials is a direct cost, assigned straight to Millwork. $5,000 of monthly office rent supports both businesses, that's shared overhead, and it needs a different approach.

Don't Automatically Assign Every Expense to the DBA

The distinction between a direct cost and shared overhead matters more than it might seem. Assigning shared costs directly to the DBA, or leaving them out entirely, both produce a misleading picture of what the business line actually costs to run.

Create a Reasonable Allocation Method

Allocation can be based on revenue, square footage, headcount, labor hours, usage, or transaction volume, whichever method makes economic sense for the specific cost being allocated, applied consistently once chosen. The goal isn't to make the DBA look artificially profitable. The goal is to understand what resources this business line actually consumes.

How to Create a Separate P&L for the DBA

The output this entire structure is building toward looks something like this:

Financial Metric	Main Business	Millwork DBA
Revenue	$500,000	$150,000
Direct Costs	$250,000	$95,000
Gross Profit	$250,000	$55,000
Allocated Overhead	$100,000	$20,000
Net Profit	$150,000	$35,000

QuickBooks supports Profit & Loss by Class reporting, which allows income and expenses to be analyzed by business segment directly from this structure. The purpose isn't merely to produce a prettier report, it's to answer, with real numbers, whether the DBA is actually profitable.

Can the DBA Use the Same Bank Account?

Separate Reporting Does Not Require Separate Bank Accounts in Every Case

If the DBA is part of the same legal entity, management can typically track its transactions separately within the same accounting file. The accounting system distinguishes transactions through classes and other dimensions, without needing a physically separate account to do so.

But Separate Reporting Does Not Mean Separate Cash

This distinction matters enormously. If the shared bank account holds $100,000, and reporting shows Millwork generated $30,000 of profit, that doesn't mean there's literally $30,000 sitting in a dedicated Millwork account somewhere. Separate P&L does not equal separate cash, the reporting is analytical, not a physical division of funds, and treating it as the latter leads to real cash management mistakes.

How to Track Job Costs for the DBA

Business-Level Profitability vs. Job-Level Profitability

These are genuinely different questions. "Is the Millwork DBA profitable?" is a business-level question. "Which Millwork projects are profitable?" is a job-level question, and a firm needs both answers, not just one.

Example of DBA + Job Costing

A transaction tagged to the Millwork DBA class, tied to customer ABC Construction, on the Office Renovation job, tracking revenue, materials, labor, subcontractors, delivery, and other direct costs, lets management evaluate DBA-level profitability and individual job profitability as two separate, complementary views.

When Should You Create a Separate QuickBooks Company File?

The DBA Is Actually a Separate Legal Entity

If the business is legally separate, separate accounting is likely appropriate regardless of how much simpler a single file would be.

Separate Tax Reporting Is Required

Tax and legal considerations should drive this decision, not management preference or convenience.

Ownership Is Different

If Company A owns the construction business and Company B owns the millwork business, that's a fundamentally different situation than a DBA operated under one entity, and the accounting needs to reflect that difference.

Separate Financial Statements Are Required

If the business genuinely needs separate books, bank accounts, liabilities, equity, and reporting, a separate company file likely makes more sense than trying to force everything through classes. QuickBooks supports multiple company files, but those files maintain entirely separate financial data from one another.

Class vs. Job vs. Separate Company File: Which One Should You Use?

Tool/Structure	What It Helps Track
Class	Business segments or divisions
Customer	Who the business sells to
Job	Specific projects/matters
Account	Type of revenue or expense
Separate company file	Separate business/entity

These tools work together rather than compete with each other. A single transaction might flow through ABC Construction LLC, tagged to the Millwork DBA class, under customer ABC Construction, on the Office Renovation job, each layer answering a different question about the same dollar.

Common Mistakes When Tracking a DBA in QuickBooks

Creating a Separate Company File Too Quickly

A DBA does not automatically mean a separate legal entity, and jumping to a separate file adds unnecessary complexity.

Treating the DBA Like a Separate Entity

Creating artificial intercompany transactions when there isn't actually a second entity introduces confusion without any real benefit.

Tracking Revenue but Not Expenses

A separate revenue report isn't enough on its own, without matched direct costs, it says nothing about profitability.

Ignoring Shared Overhead

A DBA may look highly profitable simply because its share of overhead isn't being considered.

Inconsistent Class Assignment

If some Millwork transactions carry a class and others don't, the resulting P&L becomes unreliable. QuickBooks specifically provides reporting for unclassified transactions, since missing class assignments directly undermine class-based reporting.

Confusing Separate P&L With Separate Cash

Financial reporting can separate profitability analytically without physically separating the underlying cash, conflating the two leads to poor cash decisions.

A Simple Decision Framework

Start by asking whether the DBA is part of the same legal entity. If not, separate company accounting deserves serious consideration. If so, ask whether separate management reporting is actually needed, if it is, class or business-segment tracking is the next step. From there, determine whether job-level profitability matters for this business, which calls for customer and job tracking layered on top. If shared costs are significant, establish a consistent allocation methodology rather than leaving them unaddressed. Finally, review the results monthly, revenue, direct costs, gross profit, allocated overhead, net profit, and the resulting cash impact, so the reporting stays a living tool rather than a one-time setup exercise.

The Real Goal Is Financial Visibility, Not Another QuickBooks File

A separate DBA report isn't valuable simply because it looks separate. It's valuable because it helps management understand whether that business line is generating enough revenue and profit to justify the resources it consumes. The chain that matters runs from revenue, to direct costs, to gross profit, through overhead, to net profit, to cash flow, and finally to the investment decision at the end of it.

From Separate Reporting to Better Business Decisions

The right QuickBooks structure isn't the one that looks the most sophisticated, it's the one that answers the questions management actually needs answered. For most DBAs operating under the same legal entity, that means classes, consistent cost assignment, and disciplined overhead allocation, not a second company file. Once that structure is in place, the conversation shifts from bookkeeping mechanics to real strategy: whether the business line is worth the resources it's consuming. If you're not sure your current QuickBooks setup can answer that question, that's worth resolving, and it's exactly the kind of financial clarity Self Made CFO is built to provide.

About The Author

Ashley Bennett is an accountant at Self-Made CFO with three years of exclusive experience serving law firms. Her background in legal accounting has given her a sophisticated understanding of the financial structure, reporting expectations, and operational nuances unique to legal practices.