Autotask PSA Integration · Live Today

Every subscription change in Work 365 shows up in Autotask.

Work 365 records every subscription change in the License Change Log. Those changes push to Autotask as Service Adjustments immediately, without waiting for a monthly invoice run. When a customer adds seats in the morning, your Autotask contracts reflect it before lunch.

Live todayNo invoice needed firstReal-timeAzure and NCE covered

License Change Log: changes queued for Autotask

Contoso Ltd: +5 seats M365 Business Premium

2 min agoQueued

Northwind: New sub, D365 Business

18 min agoQueued

Fabrikam: Azure usage October

1 hr agoQueued

Push to Autotask as Service Adjustments

Autotask PSA

Contracts updated with Service Adjustments

One-way

LCL

Push unit

Near real-time

Invoices needed

LCL-based

Changes push as they happen, not after invoice generation. Work 365 pushes, Autotask receives.

Real Time

No invoice needed first. Subscription changes push as Service Adjustments immediately.

Full stack

M365, D365, Azure, NCE — all billing types covered in every push.

How data maps

Work 365 and Autotask: the translation layer.

Work 365 and Autotask use different terms for the same business objects. Every Work 365 entity has an Autotask equivalent.

Account → Account

Autotask is where your team manages customer relationships. Accounts need a valid phone number before mapping.

Billing Contract → Contract

One billing contract in Work 365 maps to one Contract in Autotask. Start date must match or precede Autotask contract start date.

License Change Log → Service Adjustment

This is the core push unit. Every subscription change in Work 365 becomes a Service Adjustment in Autotask.

Subscription (license) → Service

License-based subscriptions map as Services. Usage items and non-recurring charges map as Products.

Azure usage → Product (non-recurring)

Azure usage pushes as a non-recurring Product charge in Autotask, not a recurring Service Adjustment. Must be pushed monthly.

Integration direction

Work 365 is always the source of truth.

Work 365

Billing engine
Source of truth

One-way

Autotask PSA

PSA tool
Receives data

Your billing logic stays in one system. Autotask receives only the changes Work 365 has already resolved.

No Work 365 invoice needs to be generated first. Changes push straight from the License Change Log, so your Autotask contracts reflect a seat change in near real time.

Subscription changes in Autotask. Always. Without waiting.

The billing cycle

From subscription change to Autotask Service Adjustment.

The Autotask integration runs from the License Change Log. Every change queues immediately and can be pushed without waiting for invoice generation.

Step 1 · Immediate

Subscription change

A customer adds seats, cancels, or renews. Work 365 syncs from Partner Center and logs a License Change Log entry.

Step 2 · Real-time

LCL entry queues

The change queues in the Changes tab in Work 365’s PSA Integration screen. Review the queue before each push.

Step 3 · No invoice needed

Push to Autotask

Push queued LCL entries to Autotask as Service Adjustments. No invoice generation required first. Status updates to Synced after push.

Step 4 · Automated

Autotask invoices the customer

Autotask builds the customer invoice from the accumulated Service Adjustments. Your service team sees every change that was billed.

What syncs

Everything an Autotask integration needs to do — handled.

Work 365 pushes subscription changes as Service Adjustments. Autotask never has to figure out what changed, it just builds the invoice from what Work 365 already pushed.

Products & pricing

Work 365 updates pricing in the Autotask product catalog. Price updates to contract lines are triggered by subscription change events.

Accounts & contacts

Account and contact records stay consistent across both systems. Accounts need a valid phone number before mapping to Autotask.

Contracts

One billing contract in Work 365 maps to one Contract in Autotask. Billing contract start date must match or precede the Autotask contract start date.

Service Adjustments

Every subscription change in Work 365 becomes a Service Adjustment in Autotask. Autotask builds its invoices from these accumulated adjustments.

Azure & NCE

Azure usage pushes as a non-recurring Product charge. NCE subscription changes push as Service Adjustments. M365, D365, and legacy SKUs all covered.

No invoice needed first

Unlike ConnectWise, Autotask does not require a generated Work 365 invoice before pushing. Changes push directly from the License Change Log.

Proof

What billing accuracy looks like at scale.

Real outcomes from Microsoft CSP partners running Work 365 in production.

2–3%

★★★★★

“Revenue leakage plugged. Manual, error-prone billing was costing 2–3% of revenue. ROI inside three months.”

GadellNet

Microsoft CSP Partner

-4 headcounts

★★★★★

“That nervousness around revenue leakage has gone away.”

15,000+ subscriptions, 125 vendors, four fewer finance ops roles.

Paula McTeer, TSG

Head of Finance Operations

Read the full story →

300%

★★★★★

“300% CSP growth without adding headcount. Work 365 scaled the billing operation so the team did not have to.”

Innovia Consulting

Microsoft CSP Partner

The platform behind the integration

Work 365 is more than one connector.

The Autotask integration is one piece of the Work 365 revenue and operations platform for Microsoft CSP partners.

CSP billing platform

Subscription billing, automation, and recurring revenue management for Microsoft CSPs.

Explore →

Azure usage billing

Automated Azure consumption billing with margin control, per customer.

Explore →

Customer self-service

Let customers manage their own subscriptions, upgrades, and renewals without raising a ticket.

Explore →

Work 365 is built natively on Microsoft Dataverse and Power Platform. Used by CSP partners in 25+ countries.

Frequently asked questions

Does Work 365 integrate with Autotask?+

Yes. Work 365 has a live integration with Autotask PSA (Datto). It pushes subscription changes as Service Adjustments to Autotask Contracts via the License Change Log. The integration is one-way: Work 365 pushes to Autotask.

Does Work 365 sync subscription quantities to Autotask contracts?+

Yes. Subscription changes including quantity increases, reductions, new subscriptions, and cancellations push to Autotask as Service Adjustments. Quantities on contract lines stay in sync with what is billed in Work 365.

Does Work 365 automatically update prices on individual Autotask contracts?+

Work 365 updates pricing in the Autotask product catalog. Price updates to individual customer contract lines are triggered by subscription change events in Work 365. For partners managing price changes ahead of Microsoft billing cycles, Work 365 surfaces those changes and provides tools to action them. Speak to our team about the right workflow for your billing cycle.

Do I need to generate a Work 365 invoice before pushing to Autotask?+

No. The Autotask integration pushes directly from the License Change Log without needing a generated invoice first. This makes near real-time sync possible. The ConnectWise integration works differently and does require a completed invoice before pushing.

How is the Autotask integration different from the ConnectWise integration?+

The Autotask integration is change-based: subscription changes push as Service Adjustments via the License Change Log, no invoice needed. The ConnectWise integration is invoice-based: Work 365 generates an invoice first, then pushes lines as Additions to ConnectWise Agreements. Both are one-way integrations.

Does Work 365 also integrate with ConnectWise?+

Yes. Work 365 integrates with both Autotask PSA and ConnectWise Manage. The ConnectWise integration pushes completed invoice lines as Additions to Agreements and requires a Work 365 invoice to be generated first.

Subscription changes in Work 365. Service Adjustments in Autotask. Book a demo.

See how a seat change in Work 365 pushes to Autotask as a Service Adjustment, without waiting for invoice generation.