TL;DR
ConnectWise procurement records, vendor bills, and reimbursable receipts flow into Xero through three distinct paths: direct vendor-bill creation in Xero Bills Awaiting Payment, project pass-through (cost in, on-charged out in the next invoice), and reimbursable expense claim (paid back to the staff member). Connect Zero handles all three, preserving receipt attachments. The 2026 Xero file-attachment limit is 10 MB per attachment.
The three expense paths from ConnectWise to Xero
An MSP running ConnectWise PSA records three different kinds of expense data, each of which lands in Xero through a different path. Understanding which path is which is the first step in setting up a clean expense sync.
Path 1: Direct vendor bills. The MSP buys something from a vendor (a Microsoft 365 licence batch, a hardware order from a distributor, a cloud services bill) and receives a vendor bill. The bill is recorded in ConnectWise procurement, then flows to Xero as a Bills Awaiting Payment item. The MSP pays the vendor from the business bank account. The accounting treatment is a payable, settled by a bank transfer.
Path 2: Project pass-through expenses. The MSP buys hardware or services on behalf of a customer as part of a ConnectWise project. The cost flows to Xero as a bill (the cost side), and the project's on-charge logic adds the cost (typically with a margin uplift) to the next customer invoice for that project (the revenue side). The accounting treatment is two journal entries against the project tracking category: one cost, one revenue.
Path 3: Reimbursable staff expenses. An MSP staff member pays for something out-of-pocket (a travel expense, a small parts purchase, a customer lunch) and submits an expense claim through ConnectWise. The claim flows to Xero as a reimbursable expense claim. The MSP reimburses the staff member through payroll or a direct bank transfer. The accounting treatment is a payable to the staff member, settled by the reimbursement.
These three paths exist in every MSP. The sync layer needs to handle all three correctly, or one of them ends up in the wrong Xero account.
Path 1 walkthrough: direct vendor bills
The most common path. The MSP receives an invoice from a vendor. The procurement coordinator records the bill in ConnectWise (vendor name, bill number, date, line items, tax treatment). The bill is flagged for sync.
Connect Zero reads the bill, creates a matching record in Xero under Bills Awaiting Payment, maps the line items to the appropriate Xero expense accounts (using the vendor and product mappings configured in the sync admin), preserves the tax codes (GST 10 percent for Australian MSPs, or zero-rated for exempt items), and re-attaches any receipt or invoice PDF that was attached to the ConnectWise bill.
The MSP's bookkeeper opens Xero Bills Awaiting Payment, reviews the new bills, approves them, and schedules them for payment in the next payment run. The Xero treatment is identical to a bill manually entered into Xero; the sync just removes the data-entry step.
Typical volume for a 12-person Australian MSP: 40 to 60 vendor bills per month, totalling AUD 25k to AUD 60k. Connect Zero processes them at the same cadence as invoices (near-real-time by default, batch optional).
Path 2 walkthrough: project pass-through expenses
Common for MSPs doing project work. The MSP buys AUD 4,500 of hardware on behalf of a customer for a project. The cost is recorded in ConnectWise procurement and tagged with the project ID. The cost has a margin uplift configured at the project level (say 15 percent), which means the customer will be invoiced AUD 5,175 for the same hardware.
Connect Zero handles this in two steps. Step 1: the bill is created in Xero (AUD 4,500 payable to the hardware vendor, tagged with project tracking category). Step 2: when the project's next invoice is generated in ConnectWise, the AUD 5,175 line is included on the customer invoice, which flows to Xero as a Sales Invoice (AUD 5,175 receivable from the customer, tagged with the same project tracking category).
The Xero P&L for the project shows AUD 4,500 in cost of goods sold and AUD 5,175 in project revenue, producing a gross margin of AUD 675 on the hardware pass-through. The tracking category lets the CFO slice the project P&L cleanly. Combined with the patterns in the tracking categories guide, this gives the MSP a per-project view of profitability.
Path 3 walkthrough: reimbursable staff expenses
Less common but operationally annoying when it goes wrong. A field engineer pays for AUD 85 of parts at Bunnings on the way to a customer site. They submit the receipt through the ConnectWise mobile app on the day; the expense gets approved by their team lead.
Connect Zero reads the approved expense, creates a matching record in Xero under Expense Claims (Xero's native expense-claim feature, available on the Standard and Premium plans as of May 2026 per Xero pricing, accessed 24 May 2026), maps the line items to the appropriate Xero expense accounts, and re-attaches the receipt photo. The bookkeeper opens Xero Expense Claims, approves them, and the next payroll run reimburses the staff member via direct bank transfer.
The Xero treatment is a journal: debit the expense account (Parts and Materials, in this case), credit the Expense Claims clearing account. When the reimbursement is paid, the clearing account is reduced and the bank account is reduced.
For staff with corporate credit cards (a different pattern), the bill flows through Path 1 rather than Path 3; the cost lands directly as a payable to the credit card provider.
Receipt attachment workflow
One of the most common questions MSPs ask before installing a sync vendor: do receipt attachments survive the sync? The answer for Connect Zero is yes.
The mechanism: ConnectWise stores attachments against the procurement or expense record. Connect Zero downloads the file via the ConnectWise API, then attaches it to the corresponding Xero record (Bill, Sales Invoice, or Expense Claim) via the Xero files API.
Xero's 2026 attachment limits: 10 MB per file, up to 10 attachments per record (Xero file attachment documentation, accessed 24 May 2026). Connect Zero respects both limits; files larger than 10 MB get skipped with a sync warning, and the 11th attachment onward is silently dropped (rare in practice; most MSP records have one or two attachments).
Supported formats: PDF, JPG, PNG, HEIC. The HEIC support is recent (Xero added HEIC in 2025) and matters because iPhone photos of physical receipts default to HEIC.
Pitfalls
- Mapping all bills to a single Xero expense account. The sync becomes useful only at the vendor-name level, not at the account level. Map vendors to the appropriate expense accounts (Software, Hardware, Cloud Services, Parts, etc.) so the Xero P&L stays meaningful.
- Ignoring tax-code overrides. Australian MSPs occasionally buy from overseas vendors with GST-free imports. If the sync defaults every bill to 10 percent GST, you end up over-claiming GST credits and your BAS goes wrong. Configure tax-code overrides per vendor.
- Treating reimbursable expense as the same as a vendor bill. The accounting flow is different (Expense Claims clearing account vs Bills Awaiting Payment); the reimbursement mechanism is different (payroll vs vendor payment). Map reimbursables to the Expense Claims path explicitly.
- Forgetting the receipt attachment. A bill with no attached receipt is hard to audit. If the original ConnectWise record had no receipt attached, the sync can't invent one. Train staff to attach the receipt at the ConnectWise side, not at the Xero side.
- Project pass-through invoicing lag. If the customer invoice for a project is monthly and the procurement bill arrives mid-month, the cost lands in Xero before the revenue. The cash-flow lag is real; bridge it via the project's working capital allowance.
Numeric scenario: monthly expense volume for a 12-person MSP
Concrete numbers for a typical 12-person Australian MSP doing AUD 1.5 million in revenue. One representative month in 2026 Q2.
| Path | Volume per month | Total value | Xero record type |
|---|---|---|---|
| Path 1 (direct vendor bills) | 48 bills | AUD 42k | Bills Awaiting Payment |
| Path 2 (project pass-through) | 11 bills | AUD 18k cost / AUD 21k on-charged | Bill + Sales Invoice line |
| Path 3 (reimbursable expense) | 14 claims | AUD 1.2k | Expense Claim |
| Total | 73 expense events | AUD 61.2k |
The 73-events-per-month volume is the data-entry cost the sync removes. Without the sync, an admin assistant spends roughly 4 hours per month re-typing this data from ConnectWise into Xero. With the sync, the same time is spent reviewing Xero Bills Awaiting Payment and approving them; typically 60 to 90 minutes per month.
Why MSPs care: the reconciliation downstream
The expense side of the sync feeds the same Xero reconciliation pattern as the invoice side. Per the monthly reconciliation guide, the bookkeeper compares ConnectWise expense totals against Xero Bills Awaiting Payment + Expense Claims totals at month-end. Variance under AUD 30 for a typical 70-event month is the green-light threshold; over AUD 100 indicates a mapping that needs to be revisited.
The most common drift signal on the expense side is a new vendor that didn't get added to the Connect Zero vendor mapping table. The bill lands in Xero but gets routed to a default expense account rather than the correct one. The fix is to add the vendor mapping; the historical bill can be reclassified in Xero with a journal entry.
Related context
For the broader sync architecture, see the Connect Zero hub. For the invoice side (the revenue side), see how to sync invoices without double-entry. For the reconciliation step that ties expenses and revenue together at month-end, see the monthly reconciliation guide. For purchase order treatment specifically, see the PO sync guide.
Frequently asked questions
Does Connect Zero sync vendor bills from ConnectWise to Xero?
Yes, for ConnectWise procurement records flagged for sync. The bill arrives in Xero as a Bills Awaiting Payment item with the vendor, due date, line items, and any attached receipt files preserved.
What is the difference between an expense and a vendor bill in this context?
A vendor bill is a payable owed to a vendor (a hardware supplier, a cloud licence vendor) that gets paid from the business bank account. An expense is typically reimbursable to a staff member who paid out-of-pocket. Both end up in Xero, but through different account paths.
Are receipt attachments preserved through the sync?
Yes. Connect Zero downloads any receipt file attached to the ConnectWise expense record and re-attaches it to the Xero bill or expense claim. Xero accepts PDF, JPG, PNG, and HEIC attachments up to 10 MB each (Xero file attachment documentation, accessed 24 May 2026).
What about project pass-through expenses?
For expenses booked against a ConnectWise project that the MSP will on-charge to a customer, the sync creates the bill in Xero (the cost side) and includes the cost in the next customer invoice for that project (the revenue side). The two appear in Xero as separate lines tied to the same project tracking category.
About this article
Written by the Connect Zero team, an Australian-built ConnectWise to Xero sync sold by Auswide IT, an Australian MSP integration vendor based in Adelaide. We process roughly 80,000 expense records per month across our customer base. Last updated 24 May 2026.
