Overview-Work 365

Work 365 is a Subscription management and Billing automation application. Work 365 is used by IT services and Software companies to manage the sale and invoicing of recurring revenue like cloud based subscriptions or Software licenses.

Work 365 Includes the following areas:

  1. Billing and Invoicing Automation
  2. Subscription Management
  3. Payments
  4. Self-Service

Work 365 is a Microsoft PowerApps Based application integrated with Dynamics 365 for Sales. The Dynamics 365 CRM Sales Enterprise license is required to use the integrated business functions and operations related to Sales. The business data for Customers, orders, subscriptions and billing all reside within the Dynamics tenant, and the integration, business logic reside within the Azure hosted SaaS components of Work 365. This provides our users with the highest level of security, and flexibility to leverage the PowerApps infrastructure with the SaaS capabilities of Work 365.

Below is a high level diagram representing the overall process and data flow:

Work 365 supports the billing of Recurring revenue through Product items that are setup in the Dynamics CRM catalog and that are sold through the sales process or purchased through an portal.

In addition Work 365 can be used for contract management and renewal of recurring revenue.

๐Ÿ“˜

Its is not necessary to use Sales quotes or orders to utilize the billing the and subscription management capabilities in Work 365.

Work 365 enables billing scenarios for your Sales motion.

๐Ÿ“˜

At the center of Work 365, is a Billing Contract; which encapsulates the relationship between the partner and the Customer.

A customer can have more than one Billing Contract and multiple Billing Contracts should be created if there are more than one relationship and/or the terms of the relationship are different.

For example, If Contoso Pharmaceuticals wishes to pay for Office 365 Business Essentials annually, but prefers to pay for Azure Consumption monthly; then two Billing Contracts will be created. In this case, if both subscriptions are payable at the same frequency (Annually, Monthly or Quarterly) then, a single Billing Contract can be used (assuming all other aspects remain the same).

A Billing Contract can have one or more Subscriptions โ€“ which is the actual service or product that the customer consumes and pays for on a recurring basis.

  • A subscription can License-Based, where the customer signs up for a unit based product (e.g.: Office 365, Dynamics 365, user or desktop-based anti-virus software, etc.).
  • Service-Based subscriptions are behaviorally like license based subscriptions but should be used to indicate a unit based service purchase (Support Services Basic, Support Services Advanced, etc.).
  • A Usage-Based subscription is used for Microsoft Azure; where the cost (and revenue) is not per user or seat but based on actual consumption by the Customer.

A License Change Log record is generated for every change in the quantity of a License or Service based subscription. The License Change Log is an audit of all the quantity changes for that subscription.

Usage Summary is a monthly summary of the consumption details against a subscription, whereas the Usage Details provide the information at a daily level.