Roofing software for multiple locations: what happens to QuickBooks
Two roofing platforms document the same limit: every location you run syncs into one QuickBooks Online file. What that does to per-branch job costing, and the five things to settle first.
Do three branches get three sets of books? On the two roofing platforms that document it, no. Every location syncs into one QuickBooks Online file. Below is what that costs in job costing, and five things to settle before you move a second location.
Do your branches get separate books?
No, not by default, and not on the platforms that publish how their accounting connection works.
JobNimbus documents locations, and you can run more than one inside a single account. The narrower question, rarely asked on a demo, is what happens when the software pushes an invoice into accounting. It lands in one file. Both companies publish that limit in their own help centres rather than leaving you to find it after you migrate.
What the documentation says about one QuickBooks file per account
JobNimbus's help documentation on what syncs to QuickBooks Online states that all JobNimbus locations can sync to only a single QuickBooks Online file. The same article lists what does not cross at all: Vendors never sync, Estimates, Invoices and Credit Memos will not sync while in Draft status, Taxes are one-way from QuickBooks, and JobNimbus cannot create Projects in QuickBooks. We went through that list record by record in what doesn't sync between JobNimbus and QuickBooks.
Roofr's help centre says the same thing differently: one QuickBooks company per Roofr account. Roofr also documents the integration as QuickBooks Online only, US only, no QuickBooks Desktop support, and Manager or Owner permissions to set up. As of July 2026 it is still labelled BETA and sits on Roofr's top plan.
Checked against the vendors' own published documentation in July 2026. Here it is in the shape you can take into a sales call.
| Per-branch question | What the documentation says | What to ask your vendor |
|---|---|---|
| Can each branch have its own books? | JobNimbus syncs all locations to one QuickBooks Online file. Roofr allows one QuickBooks company per account | If we open a second company file, what happens? |
| Which QuickBooks does it cover? | Roofr: QuickBooks Online only, US only, no Desktop | Which product and country, today? |
| Who can connect it? | Roofr requires Manager or Owner permissions | Who can connect it, and who can disconnect it? |
| Do projects come across? | JobNimbus cannot create Projects in QuickBooks. Sync only imports them as jobs | Which system owns a job record? |
| What never crosses? | JobNimbus: Vendors, plus Draft Estimates, Invoices and Credit Memos | List the record types that stay behind |
How do you cost jobs by branch when there is only one QuickBooks file?
One accounting file across every branch does not stop you costing jobs by branch. It means the branch is not something the accounting system was told about. It is something your team types.
Whatever separates branch one from branch two in the books (a naming convention, a tag, a field on every transaction) gets applied by whoever creates the record, every time, in both locations, forever. Miss it on a dozen invoices in March and the branch margin you read in April is wrong. Nothing tells you.
The documented gaps do not help. Vendors never sync, so supplier records sit on one side. Estimates, Invoices and Credit Memos stay outside the books until somebody clears them out of Draft, so a branch's committed cost is invisible until an admin gets to it. Both are documented, deliberate behaviour, and each is a place where a second location doubles what somebody chases. More on that side in roofing job costing in QuickBooks.
Five things to establish before you add a second location
None of this is a reason not to buy something. It is a reason to get five answers before you sign.
- Which accounting file each branch lands in.JobNimbus syncs all locations to a single QuickBooks Online file, and Roofr allows one QuickBooks company per account. If you assumed one file per branch, find out now.
- Who is allowed to connect it.Roofr requires Manager or Owner permissions. Decide who holds that, and whether a branch manager should.
- How a branch is marked on every record.With one file, the branch is whatever your people type. Agree the convention before location two starts entering work. Retrofitting means touching everything already in there.
- Which record types never cross, and which only cross one way.JobNimbus publishes the list. Vendors never sync, Estimates, Invoices and Credit Memos will not sync while in Draft, and Taxes sync one way, from QuickBooks into JobNimbus.
- Which product and country it covers.Roofr's is QuickBooks Online, US only, and explicitly not QuickBooks Desktop. Check yours before assuming your accountant's setup is supported.
What does per-branch reporting look like when the system knows what a branch is?
When the branch is part of the record from the moment a job is created, per-branch reporting stops being something a person assembles. Revenue, material cost and margin by location come out because the system knows a location exists.
That is not an argument about whether software connects to other tools. Connecting is the good part. The difference is who picks. Off-the-shelf gives you the connection the vendor chose, to the depth the vendor chose, while a purpose-built system connects to the accounting you already run, on those same third-party APIs, shaped around the number of branches you have.
If you run one location, none of this costs you anything and off the shelf is a reasonable call. If you run two or three and month-end already takes someone a full extra day, get the answer before you sign. It does not get easier to ask after you have migrated.
Frequently asked questions
Does JobNimbus support multiple locations?
Yes. JobNimbus has locations, and you can run more than one inside a single account. The limit is on the accounting side. Its own help documentation states that all JobNimbus locations can sync to only a single QuickBooks Online file, so multiple branches do not become multiple sets of books.
Does the Roofr QuickBooks integration work with QuickBooks Desktop?
No. Roofr's help centre documents the integration as QuickBooks Online only, and available in the US only. It also allows one QuickBooks company per Roofr account, requires Manager or Owner permissions to set up, and is still labelled BETA on Roofr's top plan as of July 2026.
Can I run two roofing branches with separate QuickBooks files?
Not through the sync on either platform that documents this. JobNimbus states that all of its locations sync to only a single QuickBooks Online file, and Roofr's help centre allows one QuickBooks company per Roofr account. A second set of books can exist, but a person maintains it outside the integration.
How do I track job costs by branch if everything lands in one QuickBooks file?
By convention rather than by the sync. With one file, nothing in the connection marks which branch a record came from, so whatever separates them (a naming convention, a tag, a field) is applied by whoever creates the record, in both locations. Agree that convention before location two starts entering work.
What should I ask a roofing software vendor before opening a second location?
Five things, all answerable from published documentation. Which accounting file each branch lands in, who is allowed to connect the integration, how a branch gets marked on every record, which record types never cross or only cross one way, and which QuickBooks product and country the integration covers.
Keep reading
