Microsoft Changes
For most Microsoft partners, your PSA is the operational backbone of your business.
It tracks work, manages contracts, and generates invoices. But here’s the reality finance and operations teams deal with every month:
Generating an invoice is not the same as accurate, compliant, and collectible billing.
That gap is where revenue leakage, reconciliation issues, and operational friction begin.
What PSA Billing Actually Solves (and What It Doesn’t)
What PSA billing is designed for
PSA systems like ConnectWise and Autotask are optimized for:
- Time & materials billing
- Fixed-fee projects
- Recurring service contracts
- Service delivery workflows
They answer:
“What did we deliver, and what can we invoice?”
What PSA billing is not designed for
Modern Microsoft CSP and MSP businesses require billing systems that handle:
- Subscription lifecycle management (NCE, renewals, upgrades)
- Azure and usage-based billing
- Mid-cycle license changes with accurate proration
- Multi-entity, multi-currency operations
- Tax compliance across jurisdictions
- Payment collection and dunning workflows
This is where PSA systems start to break down.
Why PSA Billing Breaks in Subscription-Heavy MSP Models
1. Subscription complexity exceeds PSA design
Modern MSP revenue includes:
- Microsoft licenses (NCE monthly/annual commitments)
- Azure consumption
- Bundled services
- Discounts, promos, and tiered pricing
PSAs were not built to model this level of subscription granularity and lifecycle change.
Take NCE as a concrete example: a customer on an annual commitment and a customer on a monthly commitment are not the same product. They have different pricing, different change rules, and different billing mechanics.
In Work 365, these exist as separate Product Price records — and they sync to your PSA as two distinct line items, so your billing always reflects the commitment term your customer actually signed up for. A PSA has no concept of this. You end up managing the distinction manually.
2. Mid-cycle changes create proration problems PSAs can't solve
This is one of the biggest and least-talked-about sources of revenue leakage.
When a customer adds five licenses on the 14th of the month, someone has to calculate the prorated charge for the remainder of the billing period. In a PSA-only world, that calculation happens manually or it doesn't happen at all.
Work 365 handles proration automatically. By the time billing data reaches your PSA, every mid-cycle change has already been calculated and resolved. What ConnectWise receives is a completed billing record with the correct prorated amount — no adjustments needed in the PSA, no manual math, no missed charges.
That automated proration is where the "2–5% revenue leakage" figure most growing CSPs experience actually comes from. It's not one big billing error. It's dozens of small mid-cycle changes that never get picked up.
3. Usage-based billing requires auditability
Azure billing is not just about invoicing — it's about traceability.
You must be able to answer:
- Where did this charge come from?
- Which subscription generated it?
- Does it match Microsoft's invoice?
Work 365 ties usage → provider invoice → customer invoice, so finance teams can explain the why, not just the what.
This is also why Azure doesn't fit neatly into a PSA's recurring contract model. Azure usage is not a fixed monthly charge — it's a non-recurring product charge that accumulates month to month and must be reconciled against actual consumption. Autotask, for example, receives Azure usage as a non-recurring product charge, not a recurring service adjustment. Trying to force Azure into a recurring services structure in a PSA breaks the billing model and makes reconciliation nearly impossible.
4. Tax compliance doesn’t scale manually
- 13,000+ US tax jurisdictions
- Constantly changing rules
- Multi-region expansion
Manual or PSA-based tax handling creates:
- Compliance risk
- Audit gaps
- Incorrect invoicing
This is a dedicated problem that requires a dedicated solution — not a workaround in your service delivery platform.
5. Payments and collections are a separate discipline
Sending invoices ≠ collecting cash.
Finance teams need:
- Automated payment capture
- Dunning workflows
- Payment reconciliation
This is why systems like Business Central handle AR separately from PSA workflows. The same principle applies here.
Struggling with Azure usage, NCE changes, or billing reconciliation? See how CSPs automate billing with Work 365.
The Missing Layer: A Billing Control System
To scale a CSP business, you need a system that answers:
“Can we bill accurately, compliantly, repeatedly—and get paid?”
That requires a dedicated billing layer, not just a PSA.
Where Work 365 Fits and How the Integration Actually Works
Work 365 is a subscription management and billing automation platform built for Microsoft CSPs.
- Built on Dynamics 365 + Power Platform
- Native to Dataverse (single source of truth)
- Integrated with Partner Center and distributors
It’s designed to sit on top of your PSA, not replace it.
Here is what that integration concretely looks like.
For ConnectWise customers: Work 365 generates the invoice first — with every charge already calculated, including prorations for mid-cycle changes, annual subscriptions billed monthly, and NCE commitment differences. Your team then pushes those invoice lines into the mapped ConnectWise Agreement as Additions. ConnectWise receives completed financial records. It does not need to perform any calculations. It generates and sends the customer-facing invoice from those Additions.
For Autotask customers: Work 365 pushes License Change Log (LCL) entries — timestamped records of every subscription change — directly to Autotask as Service Adjustments. Autotask is built around this model: it accumulates service adjustments and builds the invoice internally. There is no need to generate a Work 365 invoice first. Changes flow from Work 365 to Autotask in near real time as they occur.
In both cases, Work 365 is the source of truth. If something looks wrong in your PSA, the fix always starts in Work 365. Correcting billing data directly in the PSA does not update Work 365 — and your next billing cycle will push the same incorrect data again.
This is the operational principle your team needs to internalize before go-live: one system calculates, one system delivers.
What Work 365 Adds on Top of PSA Billing
1. Contract-driven billing (not invoice-driven)
Every charge is tied to a billing contract:
- Subscriptions
- Usage
- One-time services
This enables:
- Advance + arrears billing
- Accurate revenue alignment
2. Full subscription model support
Supports:
- Recurring billing
- Usage-based billing (Azure)
- Tiered and bundled pricing
- Multi-currency + multi-entity
Reflecting how CSPs actually generate revenue.
3. Built-in tax and payment automation
- Avalara integration → tax compliance
- Payment integrations (Stripe, GoCardless, Authorize.Net)
- Auto-charging with stored payment profiles
Without storing sensitive payment data (PCI-aligned approach).
4. Microsoft-native CSP alignment
- Bi-directional sync with Partner Center
- Handles NCE changes, subscriptions, invoices
- Keeps billing aligned with Microsoft updates
When Microsoft changes NCE rules or pricing, Work 365 picks it up. Your PSA does not.
5. Designed for scale and complexity
Supports:
- Multi-entity billing
- Parent–child hierarchies
- Global operations
Helping eliminate revenue leakage (often 2–5% in growing CSPs).
Who This Matters For
Finance Leaders (CFOs)
- Reduce revenue leakage
- Ensure tax compliance
- Improve audit readiness
Licensing & Operations Teams
- Handle NCE changes and renewals without manual intervention
- Reduce manual errors
- Align billing with Microsoft updates
Business Leaders
- Scale recurring revenue without adding headcount
- Gain a single source of truth
- Stop managing two systems that store the same customer data separately
Work 365 and your PSA are not alternatives. They are complementary systems with different jobs. The PSA manages service delivery and generates the customer-facing invoice. Work 365 manages subscriptions and ensures the data going into that invoice is accurate, complete, and compliant.
The Bottom Line
Your PSA tells you:
“What did we deliver?”
Work 365 ensures:
“We billed it correctly, compliantly, and at scale—and got paid.”
If you’re evaluating billing maturity, don’t ask:
“Can we generate invoices?”
Ask:
“Can our billing system handle CSP complexity without breaking?”
That’s the difference between operational billing and revenue control.
Looking to modernize CSP billing without replacing your PSA?