Sync 365 vs Manual spreadsheets
Use Manual spreadsheets to investigate or independently check billing data once. Use Sync 365 to operate the recurring Microsoft mappings, calculations, filters, exceptions, and PSA updates that must keep working every billing cycle.
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 the jobs that determine billing accuracy: new-subscription mapping, custom and calculated quantities, split-tenant rules, Azure controls, and ownership of the final PSA record.
| What matters | Automates repeat billing workSync 365 | Manual spreadsheets | Why it matters |
|---|---|---|---|
| Primary billing job | Recurring billing workflowA focused Microsoft billing layer for licences, Azure, managed users, contacts, and custom recurring services while the supported PSA remains the invoicing system of record.[6][2][5] | One-off validationManual spreadsheets are a flexible one-off analysis and validation surface. They are not an operated recurring billing workflow; the MSP owns every refresh, formula, exception, approval, and PSA handoff.[7][8][9][10] | Start with the operational problem each product is designed to own before comparing individual features. |
| Recurring-cycle ownership | Shared workflow controlsSync 365 stores billing profiles, reusable AutoMap rules, customer-specific calculations, review states, and supported PSA destinations in the application workflow.[1][2][3][6] | Owner-led cycle checksManual spreadsheets can import and refresh data, calculate results, and show workbook changes. The MSP must still name an owner who verifies each refresh, formula, exception, version, and PSA handoff at every billing cutoff.[7][9][8][10] | A calculation tool may produce the right answer; recurring billing also needs someone accountable for proving the workflow ran and handling failures before invoices are issued. |
| New subscription mapping | Reusable AutoMap 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] | Maintained workbook logicFor a one-off review, Manual spreadsheets can refresh subscription data and apply maintained lookups or formulas. Making that recurring leaves the MSP responsible for refresh timing, failed inputs, exceptions, and the separate PSA import, integration, or handoff.[7][9] | A reusable mapping rule reduces the chance that a newly appearing subscription waits for another manual setup step before billing cutoff. |
| Custom recurring services | Linked recurring quantitiesA configured Microsoft or managed-user count can keep support, backup, antivirus, security, filtering, and other related recurring PSA lines aligned.[2] | Owner-maintained formulasManual spreadsheets can model a managed-user or recurring-service quantity for a one-off check. Using the workbook each cycle leaves its owner responsible for source freshness, customer exceptions, and every downstream PSA line.[7][8] | MSPs often sell a service bundle around each user, not only the underlying Microsoft licence. |
| Calculated quantities and overage | Configured calculation 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] | Flexible modelling toolManual spreadsheets are capable modelling and validation tools. Using them for recurring billing leaves finance responsible for formula correctness, source joins, deductions, duplicates, version selection, exception review, and the final PSA handoff.[7][10] | 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 | Configured 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] | Operator-maintained splitsManual spreadsheets can test a split by an imported attribute. Repeating that workflow means the operator must keep source fields, mutually exclusive populations, and PSA destinations current every cycle.[7][9] | One Microsoft tenant can represent several sites, departments, franchises, cost centres, or legal billing entities. |
| Azure consumption workflow | Reviewed Azure postingAzure consumption can move through billing profiles, markup, billing-period review, approval or configured auto-approval, and supported PSA posting.[5] | One-off Azure checkManual spreadsheets can inspect a particular Azure export or validate a markup calculation. Recurring billing still leaves finance responsible for choosing the period, controlling the workbook version, approving the result, reconciling exceptions, and entering the PSA quantity.[7][10] | Azure comparison should include data timing, markup, period review, approval, exception handling, and the final PSA record—not only ingestion. |
| PSA ownership and scope | Supported PSA updatesSync 365 supports ConnectWise Manage, Autotask PSA, and HaloPSA workflows while the PSA remains responsible for invoices.[6] | Separate PSA handoffManual spreadsheets sit outside the PSA and are best kept as an independent check. If they drive recurring billing, a separate import, integration, or human handoff must update the PSA, with its own validation and ownership.[7][8] | 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 Manual spreadsheets
Manual spreadsheets can test refreshed data against a maintained lookup or formula rule. Using that workbook every cycle leaves the team responsible for refresh timing, exceptions, and the separate PSA integration, import, or handoff.[7][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 rebuilding the mapping.
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 Manual spreadsheets
Manual spreadsheets can model a managed-user or recurring-service count for a one-off check. Making the workbook recurring leaves its owner responsible for source freshness, customer exceptions, and every downstream PSA line.[7][8]
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 Manual spreadsheets
Manual spreadsheets are capable one-off modelling and validation tools. If they produce the quantity each cycle, finance owns source joins, formula integrity, deductions, duplicates, version selection, exception review, and the final PSA handoff.[7][10]
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 Manual spreadsheets
Manual spreadsheets can test a split using an imported attribute. Repeating that workbook process leaves the operator responsible for source fields, mutually exclusive populations, and the correct PSA destinations every cycle.[7][9]
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
Separate the one-off work used to inspect billing from the recurring workflow that must calculate, review, and update it every billing cycle.
Choose Sync 365 when
Sync 365 fits when Microsoft and Entra data must produce customer-specific recurring quantities and the MSP wants ConnectWise, Autotask, or HaloPSA to remain responsible for invoicing.[1][2][3][4][6]
Choose the alternative when
Manual spreadsheets fit as a one-off audit, migration check, investigation, or independent validation layer. They should sit beside the recurring billing system, not become the system that must produce and hand off every monthly quantity.[7][8]
Use a real customer in the demo
Use one real customer to compare Sync 365 with Manual spreadsheets, then ask whether the work is a one-off check or must repeat at every billing cutoff. Keep Manual spreadsheets for the check; choose Sync 365 for the recurring mapping, calculation, review, and PSA-update path.
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
No. Manual spreadsheets are useful for one-off analysis and independent validation, but they leave the MSP responsible for refreshing sources, maintaining formulas, checking exceptions, and completing the PSA handoff. Sync 365 is built to operate those recurring Microsoft and Entra billing rules while keeping the supported PSA as the invoicing system of record.[1][2][3][4][6][7][8]
A workbook can refresh data and apply maintained lookup or formula rules automatically. The team still owns the source connection, refresh scheduling, exception path, downstream PSA integration or import, audit design, and ongoing maintenance. AutoMap packages commitment-term rules, billing-profile and PSA routing, and automatic or pending review in the Sync 365 workflow.[1][7][9]
Sync 365 provides custom and calculated licence workflows for managed-user services, minimums, filters, additions, deductions, bundles, and overage. Manual spreadsheets can model or independently verify the same quantity, but using them to produce it every cycle leaves the MSP responsible for sources, joins, formula integrity, version selection, exception review, and PSA handoff.[2][3][4][7][8][10]
Yes. Use Sync 365 for the recurring workflow and keep Manual spreadsheets for one-off modelling, migration validation, anomaly investigation, or independent checks. Do not have both update the same customer quantity; document the system of record and keep the workbook separate from the recurring PSA update path.[6][7][8]
Move recurring billing out of the workbook
Bring one recurring workbook and one real Microsoft tenant. See how Sync 365 can own the mappings, calculations, filters, review, and supported PSA updates, while Manual spreadsheets remain available for one-off validation.
Manual spreadsheets range from simple workbooks to governed Power Query models. This guide does not question whether Excel can import, calculate, filter, or refresh data. It compares a one-off review surface with ownership of a recurring billing workflow, including refreshes, exceptions, versions, approvals, and PSA handoffs. Product information was reviewed on. Confirm plan, region, integration and workflow details with each vendor before buying.