QuickBooks Online Limits Each Invoice to a Single Project
QuickBooks Online ties every invoice to one customer or project. We explain the rule behind it, the workarounds, and what each option costs you.
If you run two projects under one customer, you might expect to bill both on a single invoice. QuickBooks Online will not let you. Every invoice carries exactly one customer or project, so billing two projects means raising two invoices and sending them together. That feels clumsy, and the frustration is fair. The limit is deliberate, though, and we think it helps to understand the reasoning before you pick a workaround.
Why can’t one invoice cover two projects?
Intuit builds projects as sub-customers under the parent customer record. The customer or project field on an invoice takes a single selection, and every line inherits it. There is no second field and no way to attach another project alongside the first.
Billable time and expenses follow the same pattern. Tag hours to a job and they queue up on that job’s invoice, ready to be pulled in. Those links are how the software keeps each project’s income and costs matched.
The same single-customer rule governed jobs in QuickBooks Desktop, so this is long-standing design rather than a recent change.
What happens if you bill the parent customer instead?
Nothing stops you from invoicing the parent and leaving the project field empty. QuickBooks accepts it, and the client receives one document. The trade-off lands in your reports. Costs you tagged to each project stay put, but the invoice income attaches to the customer, not to a project. Each project’s profitability report then shows costs with little or no matching income, so healthy jobs can look like they are losing money.
Workarounds that keep project reporting intact
Most firms simply raise one invoice per project and let the count grow. Each invoice feeds the project reports correctly, which is the point of tagging the work in the first place. If the real complaint is the client’s experience, statements soften it considerably.
QuickBooks statements bundle every open invoice for a customer into a single document with a running balance. Sending a statement alongside the invoices gives the client one page to reconcile even though the billing stays split.
Class tracking is the other route when a single invoice matters more than project tooling. Set class tracking to one class per row, and each invoice line can carry its own class, so the Profit and Loss by Class report splits the revenue. The exchange is real: you lose project-specific features such as unbilled time tracking and per-project profitability.
Choosing between one document and clean reports
Ask what the single invoice is actually for. If the client just wants one PDF, keep the per-project invoices and put a statement on top. If job reporting barely matters to you, bill the parent customer and track the split in a spreadsheet. If you need both a single invoice and income allocated per job, QuickBooks has no native way to deliver that today, and the statement route is the closest fit.
Before your next billing run, open the Project profitability report and compare income to costs on every active job. It shows quickly whether the separate-invoice workflow is earning its keep, and it flags any older parent-customer invoices that left income sitting on the customer record instead of the project.