Overview


CSP Classic Subscription also known as Microsoft Azure (0145P) subscription can be used to configure various billing settings, Partner Center discounts as well as generate user based invoices and customer invoice reports.

This topic describes the following features in detail:

CSP Cost Settings


HCP has various billing settings at partner center levels and individual customer levels. These setting are used for cost calculations of services under

Partner Center Discount


Partner center discount: Discount that Microsoft passes to CSP partner on the overall contract/agreement level.

note

Note: All cost and usage price, we use the pre-tax cost of the rate card. Taxes are handled only under billing and reports.

Note: All cost and usage price, we use the pre-tax cost of the rate card. Taxes are handled only under billing and reports.

Billing Setting


HCP allows the setting of individual billing settings at a customer level.

CSP Customer Billing & Invoices


On partner onboarding a new CSP partner, your HCP account will fetch all associated customers and the invoices from last six months, with all the invoice billing line items.
Once the partner is correctly setup on HCP, every 12 hours HCP fetches all the (new) invoices for the partner and show it under

Types of billing invoices in Partner Center: (Ref: Billing Types)

Usage-based Invoice and customer invoice report generation


In HCP, the CA can see associated customer invoices and generate customer invoices against partner center invoices each month.

Generating invoice report


Note: Customer invoice report generation for Azure Plan (G-invoice) is not supported for now.

CSP Customer spending and Dashboard


CSP Usage and Cost Collection Implementation


Data

Day0

Day1

Day2

Day3

Day4

Day5

Day6

Day7

Day0

D0-1








Day1


D0







Day2



D1






Day3




D2





Day4





D3




Day5






D4



Day6







D5


Day7








D6









D0, D1, D2...are days.

Data

Day0

Day1

Day2

Day3

Day4

Day5

Day6

Day7

Day0

D0-1


D0-1






Day1


D0

D0






Day2



D1


D1




Day3




D2

D2




Day4





D3


D3


Day5






D4

D4


Day6







D5


Day7








D6










This allows us to reconcile each day’s data by revisiting the utilization; thus capturing most of the records that were not immediately available with MS usage and the billing service API.

note

Note: Usage collection is an API database extensive process. We wanted to reconcile with a gap of 1 day so that all backlog of job collection gets completed within time before we start reconciliation again after a gap of a day.

Note: Usage collection is an API database extensive process. We wanted to reconcile with a gap of 1 day so that all backlog of job collection gets completed within time before we start reconciliation again after a gap of a day.