The MSPs that struggle most with ConnectWise to Xero sync are the ones with more than one site. The headline question is the same as everyone else's, but the operational question is different: how do I make sure the revenue, expenses and time from each location land in the right Xero report? This article is the practical answer.

The mechanism is Xero tracking categories. The work is in mapping ConnectWise locations (and where relevant, departments and business units) to Xero tracking-category options cleanly, at install time, before the first invoice syncs. Done well, you get a Xero profit-and-loss report split by location that finance trusts. Done poorly, you get a sync that works but feeds reports nobody can use.

What location and department mapping actually means

Location and department mapping in a ConnectWise to Xero sync means routing each synced invoice, expense and bill to the correct Xero tracking-category option so Xero reports can split revenue and expenses by physical site or organisational unit. The Xero developer documentation defines tracking categories as a mechanism for tagging transactions to a class or division for reporting (Xero developer documentation: Tracking Categories, accessed 23 May 2026). For MSPs, the most common use is one tracking category for location and a second for department or business unit.

Xero supports up to two tracking categories per organisation. Each category has up to 100 options. For nearly every MSP, this is plenty. The constraint to watch is not the option count: it is the discipline of keeping the options stable as the business changes.

Why this matters more than people expect

Most MSPs treat tracking categories as a finance concern. They are an operational concern that finance happens to consume. Once your ConnectWise sync is feeding tracking categories cleanly, the team can answer questions you could not previously answer without a side-spreadsheet: which location is running the highest margin per technician, which department has the most growth quarter on quarter, which business unit is carrying the largest agreement renewal risk.

A 2026 ConnectWise to Xero sync that does not feed tracking categories is functionally equivalent to a single-entity export. It works, it stays accurate, but it cannot answer multi-site questions without manual work.

Two tracking categories, one common pattern

The most common pattern across MSPs we see is:

• Tracking category 1: Location. One option per physical site or operating region. Examples: Adelaide, Melbourne, Brisbane. Or: Sydney North, Sydney South, Regional.
• Tracking category 2: Department or business unit. One option per cost centre. Examples: Managed Services, Project Work, Hardware Resale, Internal.

If you only need one, use Location. If you need both, use Location and Department in that order. Do not use both for the same purpose; that is the most common mistake, and it produces reports nobody can read.

How to map ConnectWise locations and departments to Xero tracking categories

Here is the step-by-step. Do all of the planning before you touch the sync configuration.

1. List your ConnectWise locations. Open the ConnectWise Manage System Setup and list every active location. Do not include archived locations. You may want to consolidate locations that exist for historical reasons but no longer have active work.
2. Decide your Xero tracking-category model. One category or two. If one, it is almost always Location. If two, the second is almost always Department or Business Unit. Write this down before you go further.
3. Create the tracking categories in Xero. Use the Xero Central documentation as the reference (Xero Central: Set up tracking categories, accessed 23 May 2026). Create the category with a name (Location, Department), then create each option (each location, each department) as a separate entry.
4. Build the mapping table. For each ConnectWise location, write down the matching Xero Location option. For each ConnectWise department (or business unit if you use those), write down the matching Xero Department option. The table is a small spreadsheet. Keep it; you will reference it every time you onboard a new location.
5. Configure the mapping in the sync. Every packaged ConnectWise to Xero sync supports a mapping table on the location dimension. The exact interface varies: some use a drop-down per location, some use a CSV import. Either way, the work is the same: every ConnectWise location has exactly one Xero Location option, and every ConnectWise department has exactly one Xero Department option.
6. Decide the routing rule for synced invoices. The standard rule is: an invoice carries the Xero Location matching its ConnectWise location, and the Xero Department matching the work-type or business unit on the invoice line. Some MSPs use the ConnectWise board or the work-role to drive the department rather than a literal department field. Pick one rule and document it.
7. Test on a single invoice. Before you turn the sync on for the full batch, sync one invoice and look at it in Xero. Confirm the tracking categories landed correctly. Do not skip this. The first invoice usually surfaces a mapping you forgot.
8. Build a reconciliation view. Open the Xero Profit and Loss report and filter by your Location tracking category. You should see one column per location. If you see "Unassigned" with a non-zero value, you have an invoice that escaped the mapping. Track it down before the next sync run.

That is the working pattern. Done in this order, the multi-location reporting works the first time.

Scenario: three locations, one Xero entity

This is the most common shape: an MSP with three physical sites (Adelaide, Melbourne, Brisbane), one ConnectWise install, one Xero organisation.

Setup: one tracking category in Xero called "Location" with three options. Mapping table is three rows. Each ConnectWise location maps to the matching Xero Location option. No second tracking category needed.

Result: Xero P&L splits by location automatically. Finance gets the three-column view. The mapping costs about half an hour to set up.

What to watch: a fourth location added in ConnectWise without a matching Xero option. The sync should fail loudly for invoices in the new location until the option is created and the mapping updated. Auto-creating the Xero option is convenient and dangerous, because it lets the model drift without finance noticing.

Scenario: one location, three departments

Self-contained answer: An MSP with one physical site but three operating departments (Managed Services, Projects, Hardware Resale) uses one Xero tracking category called "Department" with three options. The sync routes each invoice line to the matching Department based on a ConnectWise field, typically the work-type or board name. The Xero P&L then splits by Department, giving finance a three-column view of margin by service line.

Setup: one tracking category, three options, mapping driven by ConnectWise work-type rather than the company location.

What to watch: a single invoice with multiple work-types. The Xero invoice can carry one Department per line item, not per invoice. The sync needs to apply the routing rule at line level, not invoice level.

Scenario: multiple Xero entities plus tracking categories

Self-contained answer: An MSP that runs two trading entities (one for managed services, one for project work) with three sites each uses one Xero organisation per entity, with a Location tracking category in each. The sync routes the invoice first to the correct Xero entity (by ConnectWise company custom field or location), then applies the Location tracking category within that entity. Each entity has its own Location category, with no cross-pollination. Watch for MSP-internal cross-charge invoices between the two entities; the sync needs to know whether to apply the source location, the destination location, or both.

Scenario: location plus department on the same invoice

Self-contained answer: An MSP that needs to report on both location and department uses both tracking categories on each invoice. ConnectWise location drives the Location category. ConnectWise work-type or business unit drives the Department category. Each line item on the Xero invoice carries both. The Xero P&L can then be filtered by either dimension or both. Watch for line items that genuinely cross departments: a bundled package that includes managed services and project work needs to be split into multiple line items on the ConnectWise invoice, otherwise the Department dimension blurs.

Pitfalls that catch first-time setups

Four pitfalls show up regularly when MSPs set up location and department mapping for the first time.

The first is auto-creating Xero options from the ConnectWise side. Some packaged syncs offer to auto-create a missing tracking-category option if a ConnectWise location does not have a mapping. This is convenient and dangerous, because it lets the option list drift without finance review. Turn it off and let the sync fail loudly when a mapping is missing.

The second is using tracking categories for too many things. Two categories, used consistently, beats two where each line item carries an inconsistent third dimension via custom field hacks. If you find yourself wanting a third category, ask whether you really need one or whether you are over-modelling.

The third is changing a tracking-category option name after the sync has been running. Renaming does not break history, but it does break reports that filter on the old name. If you have to rename, do it at month-end and update every saved report.

The fourth is not validating after the first sync run. The "Unassigned" column in the Xero P&L is the canary. It should always be zero. If it is not, an invoice escaped the mapping.

How ConnectWise locations and departments are exposed

The ConnectWise Developer Network documents the Company endpoint as the source of location data on the Manage REST API (ConnectWise Developer Network, accessed 23 May 2026). Each company carries a Site, and the sync reads the Site ID off each company, looks it up in the mapping table, and writes the corresponding Xero tracking-category option onto the invoice line items. Homemade syncs often treat location as a free-text field rather than a structured lookup, which is where they drift.

There is no single ConnectWise field called "department". Most MSPs drive the Department tracking category from the ConnectWise work-type, because work-type is already attached to every line item on every invoice. If you use boards as your business-unit dimension, drive Department from the board instead. Either works; mixing them on the same install does not.

What to do at month-end

Three checks at month-end keep the tracking-category mapping clean over time.

The first is the Unassigned check. Open the Xero P&L, filter by your Location category, scan for a non-zero Unassigned column. If it is non-zero, an invoice escaped the mapping. Track it down.

The second is the new-option check. Open ConnectWise locations and Xero tracking-category options side by side. Any ConnectWise location without a matching Xero option, or any Xero option without a matching ConnectWise location, is a discrepancy. Fix it before month-end close.

The third is the rename check. Any Xero tracking-category option renamed in the past month should be reflected in the mapping. Some packaged syncs auto-detect this. Most do not. A two-minute check beats a quarter of rework.

Frequently asked questions