Autotask PSA to Xero invoice sync, for MSPs

Autotask to Xero, with you at the controls.

NexumPilot turns every Autotask invoice into the Xero invoice you would have keyed yourself, automatically: one line per billing item, the right account and tax rate on every line, and VAT that equals Autotask's to the penny. Anything that does not add up is held for you instead of posted.

For Autotask PSA and Xero. UK VAT. Data held in the EU.

Autotask Invoice 20187
Harbour Lane Dental LtdAccount HLD001
Billing itemQtyRateAmount
Managed service, per userMS-USER2338.5000885.50
Microsoft 365 Business PremiumLIC-M365BP2318.1000416.30
Microsoft 365 backupBK-SAAS232.750063.25
Contract setup feeNo billing code10.000045.00
Net1,410.05
VAT282.01
Total (GBP)1,692.06
Xero Sent to Xero
Harbour Lane Dental LtdMatched by account number
LineAccount · TaxAmount
Managed service, per user23 × 38.5000400020% (VAT on Income)885.50
Microsoft 365 Business Premium23 × 18.1000410020% (VAT on Income)416.30
Microsoft 365 backup23 × 2.7500411020% (VAT on Income)63.25
Contract setup fee1 × 45.0000, from the amount4200Mapped by item type45.00
VAT282.01 Matches Autotask
Total (GBP)1,692.06
Passed every check, so it went to Xero on its own. What gets held?

Example invoice. Company, codes and amounts are illustrative.

1 to 1

Every Autotask billing item becomes its own Xero line. No merged lines.

4 dp

Unit prices reach Xero as Autotask stores them. No averaged rates.

To the penny

Invoice VAT equal to what Autotask charged, every time.

6 levels

of mapping rule, from a single company down to item type.

Why MSPs still check every synced invoice

The small errors that make you re-check every invoice.

Most syncs get an invoice into Xero. The trouble is the pennies, the merged lines and the contacts nobody asked for. NexumPilot was built around each of these.

Typical sync
NexumPilot

Lines merged, rates averaged

Several billing items become one Xero line with an averaged unit price. On one real invoice that lost 22p.

One Xero line per billing item

Real quantities and unit prices, to four decimal places, exactly as Autotask holds them.

VAT that drifts by a penny

Xero recalculates VAT line by line and the total lands a penny or two away from what Autotask charged.

VAT equal to Autotask's

NexumPilot sends each line's VAT, adjusted by at most a penny, so the invoice's VAT matches Autotask to the penny.

Duplicate contacts

Every slight difference in a company name becomes another Xero contact, and the duplicates pile up.

Matched first, created when it is new

Matched by account number, then exact name. A genuinely new company gets a new Xero contact, or waits for you if you prefer. Near matches and archived contacts always come to a person.

Exempt clients charged VAT

A default tax rate ignores a company's tax status in Autotask, and VAT appears where it should not.

A tax check on every line

Tax exempt companies get their own mapping. Any line whose Xero tax rate disagrees with what Autotask charged is held.

How it works

Set it up once. Then it runs on its own.

Setup is a guided checklist, and all of it is read-only, so you can run NexumPilot alongside whatever you use today. Once you switch it on, clean invoices go to Xero by themselves. Only the ones that fail a check come to you.

  1. Connect

    Sign in and connect

    Sign in with Microsoft 365, connect Xero and an Autotask API user, and load your lists and invoices. Nothing changes in either system.

  2. Map

    Map each code once

    Map every tax category and billing code. Same-name matches are offered to tick.

  3. Match

    Match contacts

    Confirm matches in bulk, and choose whether new companies get a new Xero contact.

  4. Compare

    Shadow run

    See the invoice NexumPilot would send beside the one already in Xero, line by line, before you switch over.

  5. Switch on

    Turn on the sync

    From then on, every invoice that passes its checks goes to Xero automatically.

  6. Exceptions

    Clear what is held

    A tax mismatch, a missing mapping or an unsure contact holds the invoice. Each one says why. Fix it and release it.

Mapping

Map a billing code once. Override it where it matters.

A billing code rule sets the Xero account, and optionally the tax rate. When one client or contract needs something different, add a more specific rule. Each line takes the most specific rule that applies.

  • Nothing is mapped by default. You choose every mapping during setup, so nothing lands in an account you did not pick.
  • Lines without a billing code, such as contract setup fees, are mapped by Autotask item type.
  • Xero works out the VAT from the tax rate you map to each Autotask tax category, and NexumPilot checks it against what Autotask charged.
Example line

Microsoft 365 backup BK-SAAS for Harbour Lane Dental, contract C-1042

  1. CompanyNo rule for Harbour Lane Dentalnone
  2. Service or bundleNo rule for this servicenone
  3. ContractBackup on C-1042 goes to backup income4110
  4. Billing codeBK-SAAS rule, overridden4100
  5. Item typeNot reached4000
  6. Fallback accountOptional, not reached4999
The line goes to 4110. Its tax rate comes from the billing code rule, the most specific rule that sets one.
Shadow run

Check it against your real invoices before it touches Xero.

For every imported invoice, NexumPilot builds the exact Xero invoice it would send and compares it with the one already in Xero, read-only. Autotask is the source of truth, and every figure says where it came from.

Example shadow run · 5 invoices 3 match1 fixes a sync error1 needs review
Invoice Company TotalAutotask TotalNexumPilot TotalXero now Result
20183Riverside Accountants3,118.403,118.403,118.40Matches
20184Elm Park Vets642.18642.18641.96Fixes sync error
Xero merged two lines and averaged the rate. 22p short.
20185Castle Street Solicitors1,204.801,204.801,204.80Matches
20186St Helier Wealth Ltd480.00480.00576.00Needs review
Tax exempt in Autotask. Xero charged 20% VAT.
20187Harbour Lane Dental Ltd1,692.061,692.061,692.06Matches

Example data. Unexpected differences are fixed, or marked as intended with a note. A confirmation lapses if the values change.

Access and security

Your invoices, your groups, your rules.

NexumPilot sits between your PSA and your books, so it is built to be boring about access.

Microsoft 365 sign-in

Access comes from Entra security groups you already manage. Remove someone from a group and their access ends within a working day.

Three roles

Owners, admins and reviewers. Reviewers can release held invoices without being able to change connections.

Encrypted credentials

Xero tokens and Autotask secrets are encrypted with AES-GCM, and each value is bound to your tenant so it cannot be reused elsewhere.

Held in the EU

Your data is stored in the EU on Cloudflare's network.

Activity log

Connections, sync runs, mapping changes and released invoices are recorded with who did what, and when.

Read-only until you switch it on

Setup and the shadow run only read. Nothing is written to Xero until you turn the sync on, and nothing is ever written to Autotask.

Case study

41 invoices. 41 matched to the penny.

A UK managed service provider on Autotask and Xero had a sync that merged lines, rounded VAT its own way and filled Xero with duplicate contacts. They ran NexumPilot in shadow over a month of invoices before switching anything over. It matched Autotask's net and VAT on every one, and flagged the invoices where the old sync had not.

Invoices compared41
Matched Autotask's net and VAT41 of 41
Errors caught in the old syncMerged lines, averaged rates
During the shadow runRead-only throughout
Early access

Run it against last month's invoices.

We are onboarding a small number of MSPs on Autotask and Xero. We will set you up, run a shadow run over a month of your invoices, and show you every difference before you decide anything.

We use these details to reply about early access. See our privacy notice.
Questions

Before you connect anything.

Does every invoice need approving?

No. Invoices that pass every check go to Xero automatically. Only the ones that fail a check are held, and each says why.

Does NexumPilot change anything in Autotask?

No. It reads invoices, companies and billing codes from Autotask through an API-only user. Your invoices in Autotask stay as they are.

Can I run it alongside my current sync?

Yes. Importing, mapping and the shadow run are read-only, so you can compare NexumPilot's invoices with the ones your current sync posts until you are happy to switch.

Will it create contacts in Xero?

Yes, if you want it to, and that is the default. Companies are matched to existing Xero contacts by account number or exact name first. A company with no match gets a new contact. Near matches and archived contacts are held for a person, and you can switch creation off so every unmatched company waits.

What about clients who do not pay VAT?

Companies marked Tax Exempt in Autotask use their own tax mapping on every line. Their invoices are held until it is set, and they never fall back to a default VAT rate.

Who deals with held invoices?

Anyone in the security group you map to the reviewer role. Admins manage connections and settings, and owners manage everything.

What if I reconnect Xero to a different organisation?

NexumPilot releases the old connection and clears that organisation's lists and contact matches, so nothing from the old books carries over.