Sync 365 vs Gradient MSP Reconcile
For Microsoft and Azure recurring billing, Sync 365 automates rules before they reach the PSA. Gradient MSP Reconcile compares data across vendors and distributors; connected sources can sync, while file-based sources need a current usage report uploaded before review.
What Sync 365 does differently
A licence count is only the starting point. Sync 365 maps new subscriptions, builds the quantities your MSP sells, and routes each result to the right supported PSA record.
Major differentiator
Set the licence, commitment-term, billing-profile and PSA destination rules once. When matching subscriptions appear, AutoMap can apply those rules automatically or queue them for approval.
Custom licences
Create the active-user or managed-user count your MSP actually sells, then use it across related support, backup, security and filtering lines in the PSA.
Explore custom licence billing
Calculated custom licences
Add and subtract Microsoft licences, subscriptions, users, custom licences or fixed quantities to model bundles, included seats and overages before the result reaches the PSA.
Explore calculated billing
Filters and split billing
Split one Microsoft tenant into separate billable populations using office, city, state, country, department, company, domain, Entra ID group or custom attributes.
Explore filters and split billingAt a glance
Compare where repeat work remains: new-subscription routing, custom and calculated quantities, split-tenant rules, Azure controls, reconciliation review, and the final PSA update.
| What matters | Automates repeat billing workSync 365 | Gradient MSP Reconcile | Why it matters |
|---|---|---|---|
| Primary billing job | Microsoft billing automationAutomates recurring Microsoft licence, Azure, managed-user, contact, custom, and calculated billing logic while the supported PSA remains the invoicing system of record.[6][2][5] | Vendor reconciliation workflowGradient MSP Reconcile compares vendor and distributor usage with PSA records, surfaces mismatches for review or approval, and writes approved updates back. Its Microsoft add-on also automates Microsoft quantity, cost, and price synchronisation.[7][8][9] | Choose the workflow that removes repeat effort from your actual bottleneck: creating Microsoft-derived billing quantities or reviewing mismatches across a wider vendor stack. |
| Vendor data collection | Direct Microsoft retrievalSync 365 retrieves configured Microsoft licence and Azure data for recurring billing workflows, then applies the MSP’s mapping, calculation, filtering, and approval rules before supported PSA updates.[1][5] | Integration or file importGradient MSP Reconcile accepts vendor usage through connected integrations or file imports. For a file-based source, an operator exports and uploads the latest usage report; saved mappings reduce setup, but the counts refresh only when a new file is uploaded. For Azure, Gradient documents Pax8 and Liongard integrations, while an MSP billing directly with Microsoft imports a Partner Center invoice-reconciliation CSV.[11][12][15] | A reconciliation workflow can still contain a recurring collection task, so buyers should count who obtains each vendor file, when it becomes available, and how it reaches the platform. |
| New subscription mapping | Reusable subscription rulesAutoMap applies reusable Microsoft licence and commitment-term rules to matching new subscriptions, routing each to the configured billing profile and PSA destination automatically or pending review.[1] | Mapping before vendor syncGradient MSP Reconcile's Microsoft add-on markets automated quantity, cost, and price synchronisation. Its mapping guide says exact-name matches can map during setup, while new accounts or services seen later require mapping before vendor sync.[10][9] | A reusable route for newly appearing subscriptions reduces repeated setup and the chance that a new charge waits for manual mapping before billing cutoff. |
| Custom recurring services | User-driven service billingA configured Microsoft or managed-user count can keep support, backup, antivirus, security, filtering, and other related recurring PSA lines aligned.[2] | Imported bespoke usageGradient MSP Reconcile can ingest bespoke positive whole-number usage through file imports or a self-hosted integration. Where no suitable integration exists, the MSP prepares and uploads the current source file before reconciliation.[12][14] | MSPs often sell a service bundle around each user, not only the underlying Microsoft licence. |
| Calculated quantities and overage | Calculated billing rulesCalculated custom licences add and subtract Microsoft licences, subscriptions, users, custom licences, or fixed values to produce bundles, included-seat deductions, and overage quantities.[3] | MSP-built transformation logicGradient MSP Reconcile supports imported or integrated usage quantities; its PowerShell SDK leaves vendor retrieval and transformation logic to the MSP rather than documenting a native add-and-subtract recurring expression builder.[12][14] | The correct quantity may be a formula—such as protected mailboxes minus users already included in the bundle—not a copied vendor count. |
| Location, department, and split billing | Attribute-based split billingOffice, city, state, country, department, company, domain, Entra group, and custom attributes can split one tenant into separate billable populations and PSA records.[4] | Vendor-service mappingGradient MSP Reconcile is designed around vendor/customer/service mappings. The reviewed documentation does not describe Microsoft or Entra attributes directly splitting one tenant into several PSA billing destinations.[10][7] | One Microsoft tenant can represent several sites, departments, franchises, cost centres, or legal billing entities. |
| Azure consumption workflow | Azure review and postingAzure consumption can move through billing profiles, markup, billing-period review, approval or configured auto-approval, and supported PSA posting.[5] | Reconciled Azure importsGradient MSP Reconcile documents Azure reconciliation through Pax8 arrears, Partner Center CSV, or Liongard; its July 2026 guide says there is no direct Azure API integration. Results move through its review and PSA-update workflow.[15][16][8] | Azure automation should be compared end to end: data source, markup, billing-period handling, review, approval, exceptions, and the final PSA record—not only ingestion. |
| PSA ownership and scope | Multi-PSA billing layerSync 365 supports ConnectWise Manage, Autotask PSA, and HaloPSA workflows while the PSA remains responsible for invoices.[6] | Broad vendor-PSA matrixGradient MSP Reconcile supports a broad matrix of vendor and PSA combinations, with approved service cards updating the PSA.[7][16] | Clear system ownership prevents overlapping automations and keeps finance confident about which record becomes the invoice. |
Beyond one-to-one sync
Start with Microsoft, managed-user or recurring-service data. Apply the commercial rule. Keep the related PSA lines aligned without rebuilding the logic in a spreadsheet each month.
Billing sources
Sync 365 billing rules
Automated PSA billing
Workflow differences
These are the practical differences to test with your own customer data—not a generic feature-score exercise.
AutoMap is term-aware, destination-aware, and designed to keep applying the rule after initial setup.
With Sync 365
Configure monthly and annual Microsoft commitment-term defaults, the Sync 365 billing profile, the company or filter-group PSA destination, and automatic or pending approval. Matching new subscriptions can then follow that route.[1]
With Gradient MSP Reconcile
Gradient MSP Reconcile's Microsoft add-on markets automated quantity, cost, and price synchronisation. Its Reconcile mapping guide says exact-name matches can map during setup, while new accounts or services seen later require mapping before vendor sync.[10][9]
Why it matters
The useful distinction is not whether a product can sync a count. It is whether new Microsoft subscriptions inherit the right commercial and PSA-routing decisions without repeated setup.
Turn the trusted user or licence count into the support, backup, security, and filtering lines the MSP actually sells.
With Sync 365
Custom licences can use managed users, filtered licences, minimums, exclusions, and customer rules. One configured count can drive several related recurring items through their billing profiles into supported PSA records.[2]
With Gradient MSP Reconcile
Gradient MSP Reconcile can ingest bespoke positive whole-number usage through imports or a self-hosted integration. The MSP prepares and maintains that source workflow.[12][14]
Why it matters
A Microsoft seat count can be correct while the surrounding managed-service invoice is still wrong. Keeping related lines tied to one reviewed quantity reduces that drift.
Use ordered additions and deductions when the billable number does not exist in any single source system.
With Sync 365
Calculated custom licences can combine Microsoft licences, subscriptions, all users, custom licences, and fixed quantities. Rules can apply filters, configured duplicate removal, included-seat deductions, and a zero floor before mapping the result to the PSA.[3]
With Gradient MSP Reconcile
Gradient MSP Reconcile supports imported or integrated usage quantities; its PowerShell SDK leaves vendor retrieval and transformation logic to the MSP rather than documenting a native add-and-subtract recurring expression builder.[12][14]
Why it matters
Finance gets an explainable recurring result for rules that otherwise tend to live in spreadsheet formulas, custom scripts, or month-end adjustments.
Keep one tenant while producing separate location, department, franchise, group, or entity-specific billing populations.
With Sync 365
Sync 365 can include or exclude users by Microsoft and Entra attributes, map each filtered population to the relevant PSA record, and use a separate AutoMap destination for each filter group.[4][1]
With Gradient MSP Reconcile
Gradient MSP Reconcile is designed around vendor/customer/service mappings. The reviewed documentation does not describe Microsoft or Entra attributes directly splitting one tenant into several PSA billing destinations.[10][7]
Why it matters
The tenant-wide total is often wrong for a multi-site or multi-entity agreement. Billing populations should reflect the customer structure that finance actually invoices.
Built around real MSP billing
Sync 365 customer stories show custom recurring rules and split-tenant billing working in live MSP operations.
Custom recurring billing
“Everyone can do 365 licensing. It’s the custom stuff I need.”
Chris F, Operations Director · Cleva Group
Read the Cleva Group storyOne tenant, many billing records
“There’s no way we would be able to service a customer like that manually.”
Sean Stuart, Operations Manager · IT Global
Read the IT Global storyCustomer-specific examples, not typical or guaranteed results.
Best fit
Choose around the system that should own the billing logic, the source data that determines quantity, and the amount of mapping or custom engineering your team wants to maintain.
Choose Sync 365 when
Sync 365 fits when an MSP wants Microsoft, Azure, and Entra data to keep producing customer-specific recurring quantities while ConnectWise, Autotask, or HaloPSA remains responsible for invoicing.[1][2][3][4][5][6]
Choose the alternative when
Gradient MSP Reconcile fits an MSP whose main billing problem spans many vendors and distributors and whose team wants a shared process for reviewing mismatches and writing approved changes to the PSA. It is most efficient when connected integrations cover the vendor stack.[7][8][16][9][11][12]
Use a real customer in the demo
Use one real customer to compare Sync 365 with Gradient MSP Reconcile: a new annual Microsoft subscription, Azure usage, a managed-user bundle, an overage calculation, one filtered site, and the final PSA record. Count every setup, file export or upload, review, approval, exception, and update step that repeats each month.
How Sync 365 fits
The PSA stays in control of invoicing. Sync 365 owns the reusable mapping, quantity and review logic that prepares supported billing records.
Bring Microsoft 365, Azure, managed-user and supported PSA data into one billing workflow.
Use AutoMap, billing profiles, minimums, exclusions, filters and calculated custom quantities.
Check pending mappings, calculated quantities, billing changes and configured Azure approvals.
Update supported PSA billing records while the PSA remains the invoicing system of record.
Frequently asked questions
Sync 365 automates recurring Microsoft, Azure, managed-user, custom, calculated, and split-billing logic before updating a supported PSA. Gradient MSP Reconcile primarily compares vendor and distributor data with PSA records for review, approval, and write-back; its Microsoft add-on also automates Microsoft quantity, cost, and price synchronisation.[1][2][3][4][5][6][7][8][9]
Sync 365 is built around Microsoft-specific recurring billing automation, including AutoMap, Azure workflows, custom and calculated quantities, and attribute-based splits. Gradient MSP Reconcile's Microsoft add-on automates quantity, cost, and price synchronisation, while the wider Reconcile workflow remains centred on comparing vendor data with PSA records and reviewing mismatches.[1][5][2][3][4][7][8][9]
Sync 365 provides custom and calculated licence workflows for managed-user services, minimums, filters, additions, deductions, bundles, and overage. Gradient MSP Reconcile supports integrated or imported usage; test the same customer rule to see whether the calculation is native, prepared upstream, or maintained by the MSP before review and PSA write-back.[2][3][4][12][14]
Sync 365 and Gradient MSP Reconcile may solve different layers of the same operation. Test whether Microsoft-derived recurring logic belongs in Sync 365 while Gradient handles wider vendor reconciliation. Whichever design you choose, document the system of record and ensure two automations do not update the same customer quantity.[6][7]
Not for every vendor. Gradient MSP Reconcile can sync supported sources through connected integrations without a recurring file upload. In a file-based workflow, an operator must export and upload the latest vendor usage data; Gradient recommends an on-demand usage report where possible. For an MSP billing Azure directly with Microsoft, one documented route uses a Partner Center invoice-reconciliation CSV.[11][12][13][15]
Compare with your own billing data
Bring one real Microsoft and Azure customer workflow to compare Sync 365 with Gradient MSP Reconcile. Follow new-subscription routing, custom or calculated quantities, review, approval, exceptions, and the final PSA update end to end.
This buyer guide compares documented workflows rather than awarding a generic feature score. A capability not found in the public Gradient MSP Reconcile material reviewed is labelled as such, not presented as proof that no private or newer capability exists. Product information was reviewed on. Confirm plan, region, integration and workflow details with each vendor before buying.