Share via

Learn how to read the line items in your Partner Center reconciliation files

  • Article

Appropriate roles: Billing admin

Download reconciliation files from Partner Center to view charges for each billing period. Check the charges for each customer's subscriptions and the events that affect them, such as adding licenses mid-term. For detailed invoice information, refer to read your bill.

Understand reconciliation file fields

Here are the reconciliation files and what they show:

Reconciliation file field Includes
Legacy license-based Costs and quantities of legacy Office and Dynamics products for a billing period
Legacy usage-based Costs and usage of legacy Azure products for a billing period
New commerce daily rated usage Daily usage and charges for new commerce (Azure plan) usage-based products for a billing period
New commerce invoice reconciliation Aggregated costs, quantities, and usage for all new commerce products for a billing period

Understand charge types in reconciliation files or line items

Learn about the different types of charges in reconciliation data in the ChargeType attribute.

Fix date formatting issues in reconciliation files

Reconciliation line items might have formatting issues if the en-us locale isn't used.

To address the formatting issues, follow these steps:

  1. Open the reconciliation file (in .csv format) in Microsoft Excel.
  2. Select the first column in the file.
  3. Open the "Convert Text to Columns Wizard".
  4. Select Data on the ribbon, then select Text to Columns.
  5. Choose Delimited file type, then select Next.
  6. Check Comma as the delimiter (if Tab is already selected, you can leave this option selected) then select Next.
  7. Choose Date:MDY for the column data format, then select Next.
  8. Select Text for all amount columns, then select Finish.

Download reconciliation files programmatically

To ensure accurate financial auditing and reporting, it's crucial to have detailed reconciliation files. These files often contain large amounts of transactional data, which can be challenging to download directly from the portal.

To make this process smoother, use the billed invoice reconciliation API. This method helps you retrieve detailed invoice data efficiently, even for large files.

How do I migrate to the newer APIs (API v2)?

When you plan to migrate to a newer version of an API, such as API v2 for reconciliation, it involves a structured approach to ensure minimal disruption to your current workflows. Here’s a detailed breakdown:

Review your current workflow

  • Understand API v2 changes: Before making any changes, thoroughly review the documentation provided in the announcement for API v2. Look for new features, deprecated endpoints or fields, changes in data structures, and any breaking changes that might affect your existing integrations.

  • Assess compatibility: Evaluate how your current system interacts with the older API version and identify which parts of your workflow are affected with this migration.

  • Impact analysis: Determine the impact of migrating to API v2 on your business processes and assess whether any downstream systems need to be updated to accommodate the new API responses.

Make necessary adjustments

  • Update codebase: Modify your code to align with the new API requirements. These updates might involve changing API endpoints, modifying parameters, and handling new response formats and error codes. Ensure any authentication mechanisms are compatible with API v2.

  • Test side by side: To ensure everything works as expected, run your updated workflows in the same production environment. Test edge cases and error handling to make sure your system can gracefully handle unexpected responses.

  • Data mapping and transformation: If the data structure changed, update your data mapping logic. Ensure your system can still process the data correctly if certain fields are renamed or removed.

  • Ensure backward compatibility: Implement mechanisms to switch between API versions as needed so you can still access historical data.

Refer to detailed guidelines

  • Follow migration documentation: The announcement or migration guide likely contains specific instructions, examples, and best practices for transitioning to API v2. Pay close attention to migration timelines, deprecation deadlines for switching to the new APIs. All billing API documentation is available here.

  • Leverage support resources: Check the sample code in the documentation that can simplify the migration process.

Key considerations

  • Plan downtime: Plan downtime and start migration during off-peak hours to minimize the impact on your users.

  • Use version control: Use version control systems to track changes made during the migration process. This practice helps you roll back if necessary.

  • Ensure security: Implement new authentication or authorization mechanisms introduced in API v2.

By following these steps, you can ensure a smooth and efficient migration to API v2, minimizing disruptions and taking full advantage of the new features and improvements.

Where do I download the file asynchronously?

To improve the download experience and boost efficiency, the Partner Center now processes new commerce reconciliation files asynchronously. To download a file:

  1. Sign in to Partner Center and select the Billing workspace.

  2. Go to the Billing overview (NCE) task menu > Billing | Billing Overview (NCE) page

  3. Choose your desired year and currency (if multiple currencies are available) at the upper right corner.

  4. Select the invoice number.

  5. Find the reconciliation file on the side panel.

  6. Select Download report. A notification appears at the top of the page indicating the file is being processed.

  7. Navigate to the Reports (NCE) page to track the progress of your download. You can monitor the status of your request in the status column of the request line item.

Understanding the status of your requests is key to efficient workflow management. Here's a clear and concise breakdown of each status and the actions you can take:

Status definitions

  • Queued: Your request is submitted and is waiting in line to be processed.

  • Processing: The system is actively working on your request, gathering and compiling the necessary data.

  • Completed: Your report is ready and available for download. You can access it immediately and proceed with your tasks.

  • Failed: An error occurred during the report generation due to technical issues or invalid input. Try submitting the request again or contact support for help.

  • No data found: The system couldn't find relevant data based on your criteria. Review and adjust your criteria and try again.

Actionable steps based on status

  • Queued: Your request is in the system and should be processed in due course. No further action is needed.

  • Processing: While you wait, ensure that you're prepared to utilize the report once it's ready. During this step, set aside time for analysis or preparing any necessary follow-up actions.

  • Completed: Download the report promptly and proceed with your analysis or tasks.

  • Failed: Review the input parameters of your request and ensure they're correct. If the problem persists, contact the support team.

  • No data found: Adjust the parameters to better align with available data and try again.

By understanding these statuses and the recommended actions, manage your requests and ensure timely access to the information you need.

If your file exceeds the row limit in Excel

If you can't open your .csv file in Microsoft Excel because it exceeds Excel's row limit, you have these options to open the file:

  • Open a reconciliation file in an Excel Power Query: Power Query allows you to import and transform data from .csv files without facing the constraint of Excel's row limit. It's useful for large datasets that require data cleaning and manipulation before analysis.
  • Open a reconciliation file in Power BI: Power BI is a powerful tool for handling large datasets. It provides robust visualization and reporting capabilities, making it ideal for comprehensive data analysis.

Open a reconciliation file in Excel Power Query

  1. Download the reconciliation file from Partner Center.

  2. Open a new blank workbook in Microsoft Excel.

  3. Navigate to Data tab, then select Get Data > From File > From Text/CSV, and import the .csv (Comma-Separated Values) reconciliation file.

  4. After a while, you can see a window with the file preview.

  5. In that window, select the Load dropdown menu > Load To.

    Screenshot of the File preview window, with the dropdown next to Load open, and the selection Load To inside the drop-down selected.

  6. In the Import Data dialog box, select the options as indicated in the following screenshot.

    Screenshot of the Import Data window, with two items highlighted: Only Create Connections and Add this data to the Data Model.

  7. Select OK to start the loading process. Wait until it's complete.

  8. See the file name and number of rows on the right side. Double-click this area to open the Power Query Editor.

    Screenshot of the Queries & Connections window, with a sample of a report called Test Recon Data highlighted.

  9. As you scroll down, you see that new rows are added dynamically.

    Tip

    Fix data loading problems caused by line breaks:

    • Go to the Advanced Editor under the Home tab.
    • Search for the Csv.Document function.
    • Add the QuoteStyle argument (if missing) and set it to QuoteStyle.Csv.
    • Save your changes and reload the query.

  10. To search for specific line item, use the filter option as shown in the screenshot. Additionally, aggregate line items or perform calculations with the "Group By" or "Statistics" features.

    Screenshot of Excel Power Query Editor, with two highlighted items, Group By and Statistics.

  11. For instance, to find the number of billable days in the charge cycle, use the Custom Column feature to calculate the duration between the charge start and end dates. Power Query also provides a range of features for different computations.

    Screenshot of Excel Power Query Editor. In the menu bar, Add Column is highlighted.

  12. After applying the required filters in the Power Query, transfer the data to Excel by following these steps.

    Screenshot of Excel Power Query Editor. In the spreadsheet, the CreditReasonCode drop-down is open. The menu item: Copy Entire Table is highlighted.

Open a reconciliation file in Power BI

To open a reconciliation file in Power BI:

  1. Download the reconciliation file as you normally would.
  2. Download, install, and open an instance of Microsoft Power BI.
  3. Select Get data on the Power BI Home tab.
  4. Choose Text/CSV from the list of Common data sources.
  5. Open your reconciliation file when prompted.

Negative amount displayed

Some reconciliation line items show negative charges for the following reasons:

  • To reflect changes in your subscription due to cancellations, upgrades, or license modifications.
  • To account for credits received from service level agreement (SLA) violations, Azure platform migration, or price adjustments.

Understand these negative amounts by referring to the ChargeType attribute in the reconciliation line items. For instance, if the ChargeType is "customerCredit," it indicates a refund due to SLA violations, Azure credit, or price adjustments.

How is the total cost calculated for new commerce license-based purchases?

To determine costs of a license-based subscription, always use the EffectiveUnitPrice, not the UnitPrice. Here's why and how it works:

The EffectiveUnitPrice reflects your final cost per unit after accounting for:

  • Promotions: Discounts or special offers applied to reduce pricing.

  • Tiered pricing: Volume-based pricing where prices increase or decrease as quantities change.

  • Adjustments such as partner earned credit: Credits earned through managed services that lower costs.

  • Prorated billing adjustments: Costs might be adjusted based on the number of days billed within a charge cycle. The number of days billed is counted from when a billing event occurs until the end of the charge cycle. For example, if a billing event occurs on the 10th day of a 30-day charge cycle, you're billed for remaining 20 days.

Note

The subscription's UnitPrice remains fixed for the entire billing term. Changes in the UnitPrice within the reconciliation line items might occur but don't affect the actual costs. Always use EffectiveUnitPrice for precise cost calculations.

Why does my invoice reconciliation data show a recurring charge for a product without daily charges?

If you see recurring charges for products like Azure savings plans or reservations without daily usage fees, here's what's happening—and how to stay in control:

Key points to understand

  • Fixed price commitment: You're billed a fixed amount each month, regardless of usage. For example, A USD 100/month Azure savings plan bills USD 100 every month, even if you use zero hours of the service.

  • No extra charges until the limit is exceeded: Extra costs apply only if usage surpasses your commitment. Once your usage surpasses the agreed limit, the pay-as-you-go rate applies. For example, if your plan covers 100 hours of virtual machine usage and you use 120 hours, you're charged pay-as-you-go rates for the extra 20 hours.

  • Visible recurring charges: Azure savings plans and reservations are commitment-based. You're billed the agreed amount monthly to reserve capacity, ensuring availability and discounted rates. Extra charges apply only when usage exceeds the agreed limit. For example, if you agree to pay USD 100 per month for a service, this amount is billed every month regardless of usage. Extra charges apply only when usage exceeds the agreed limit.

To effectively monitor your costs, make sure to regularly review how your Azure reservation or savings plan is linked to your Azure subscription. Take control of your Azure costs today by regularly reviewing your subscription links and usage limits!

How do you find the Azure subscription ID for a product?

Finding the Azure subscription ID for a product can be done through several methods, depending on whether you're dealing with pay-as-you-go resources, Azure reservations, or Azure savings plans. Here are the steps to identify your Azure subscription ID for each type of resource:

1. Pay-as-you-go resource

Find the subscription ID for pay-as-you-go Azure resources by cross-referencing information from your invoice reconciliation files and daily rated usage files.

Steps:

  • Step 1: Find the SubscriptionId in your invoice reconciliation files or line items.

  • Step 2: Match this SubscriptionId with the corresponding SubscriptionId in your daily rated usage files or line items.

  • Step 3: Once matched, look at the EntitlementId from the same line in your daily rated usage file. This EntitlementId corresponds to your Azure subscription ID.

2. Azure reservation

For Azure reservations, you need to use the ReservationOrderId to identify the associated subscription.

Steps:

  • Step 1: Find the ReservationOrderId in your invoice reconciliation files or line items where the TermAndBillingCycle mentions "Reservation."

  • Step 2: Cross-reference this ReservationOrderId with the ReservationOrderId property within the AdditionalInfo section of your daily rated usage files line items.

  • Step 3: Once matched, look at the EntitlementId from the same line in your daily rated usage file. This EntitlementId corresponds to your Azure subscription ID.

3. Azure savings plan

For Azure savings plans, the process is similar to Azure reservations but involves matching the ReservationOrderId with the BenefitOrderId.

Steps:

  • Step 1: Find the ReservationOrderId in your invoice reconciliation files or line items where the TermAndBillingCycle includes "Savings Plan."

  • Step 2: Cross-reference this ReservationOrderId with the BenefitOrderId on your daily rated usage files or line items.

  • Step 3: Once matched, look at the EntitlementId from the same line in your daily rated usage file. This EntitlementId corresponds to your Azure subscription ID.

To organize the steps, here's a table summarizing the process:

Product type Step 1: Find in invoice reconciliation Step 2: Cross-Reference in daily rated usage Step 3: Identify Subscription ID
Pay-as-you-go resources SubscriptionId Match SubscriptionId Use EntitlementId from same line
Azure reservations ReservationOrderId Match "ReservationOrderId" in AdditionalInfo Use EntitlementId from same line
Azure savings plans ReservationOrderId Match BenefitOrderId Use EntitlementId from same line

Tip

Organizing resources:

To effectively manage and organize resources across multiple subscriptions, especially when they share the same name, consider using resource groups or tags. These tools help you achieve several goals:

  • Link products with their respective subscriptions.
  • Streamline billing reports to improve operational clarity.
  • Provide better visibility into which resources belong to each subscription.
  • Remember that while subscription names can be changed and aren't unique, Subscription IDs are globally unique and permanent identifiers for each subscription.

Note

Find your Azure subscription ID without searching through reconciliation files by using either the Azure portal or Azure CLI. To learn more, see the guide on getting subscription and tenant IDs.

By following these steps, billing administrators can track and manage resources across different Azure subscriptions. This approach ensures accurate reporting and cost management.

How to identify Azure credits in invoice reconciliation and daily rated usage data

Tracking Azure credits accurately is essential for effective reconciliation and credit management. This process helps you identify Azure credits in both invoice reconciliation and daily rated usage files or line items, ensuring clarity and precision.

1. Identify credits in invoice reconciliation files or line items

To find and manage credits within your invoice reconciliation files or line items, use the following steps:

  • Filter for credit line items: In the invoice data, use the ChargeType field and filter for "customerCredit" line items. These line items represent credits applied to your account.

  • Understand the credit reason: Check the CreditReasonCode field to identify the type of credit (for example, Azure credit). This reason helps you understand why the credit was issued.

  • Look for negative amounts: Credits typically appear as negative values in the Subtotal and Total fields, reflecting a reduction in your overall costs.

  • Group and sum for accuracy: To calculate the total credit amount precisely, group the "customerCredit" line items by these fields:

    • ProductId
    • SKUId
    • AvailabilityId
    • OrderDate
    • CustomerId

    After grouping, sum the Total field to determine the aggregate credit amount.

  • Verify consistency: Ensure the BillableQuantity matches for both charge and credit line items. This step confirms that the credit matches the original charge, maintaining accuracy in your credit tracking.

2. Identify Azure credits in daily rated usage files or line items

Daily rated usage files or line items offer detailed insights into resource consumption and can help track certain credits. Here’s how to identify them:

  • Filter for credit-related line items: Use these fields to isolate credit line items:

    • CreditType (for example, "Azure credit offer")

    • CreditPercentage set to 100 (indicating a full credit)
      This filtering narrows down the data to credit-specific line items.

  • Group and sum for accuracy: To calculate the total credit amount precisely, group the CreditPercentage = 100 line items by these fields:

    • ProductId
    • SKUId
    • AvailabilityId
    • CustomerId

    After grouping, sum the BillingPreTaxTotal field to determine the aggregate credit amount. This calculation gives you the total pretax credit amount.

Note

Not all Azure credits appear in daily rated usage files or line items. For a complete picture, always cross-reference with invoice reconciliation files or line items.

Summary for tracking Azure credits

Data source Key fields to filter Fields to analyze Action steps
Invoice reconciliation ProductId, SKUId, AvailabilityId, OrderDate, CustomerId, ChargeType, CreditReasonCode Subtotal,Total Filter forcustomerCredit, group by relevant fields, sumTotal, verifyBillableQuantity.
Daily rated usage ProductId, SKUId, AvailabilityId, CustomerId, CreditType,CreditPercentage BillingPreTaxTotal Filter for credits, sumBillingPreTaxTotal, cross-reference with invoice data.

Important

  • Consistency between charge and credit :

    • Always verify that the BillableQuantity matches between charge and credit line items.
    • This confirmation ensures that credits are applied correctly and avoids over-reporting or under-reporting.

  • Edge cases: Account for multiple credits per product or customer and credits spanning billing periods. Check dates for correct application within the billing period.

  • Best practice: Rely on invoice reconciliation files or line items as the authoritative source for credit tracking, using daily rated usage reconciliation for more granularities when applicable.

By following these steps, you can effectively track and manage Azure credits, ensuring a clear and accurate understanding of your credit reconciliation.

How to separate Azure and non-Azure charges in reconciliation files or line items

To accurately separate Azure and non-Azure charges, whether you're using APIs or downloading files from the Partner Center portal, follow these steps:

1. Using APIs to separate Azure charges

If you're using APIs to retrieve billing data, you can filter and identify Azure or non-Azure charges by focusing on the ProductCategory attribute.

Steps:

  • Find the "ProductCategory" attribute:

    • This key field in the API response categorizes each charge. For Azure-related charges, this attribute has the value "Azure".

  • Filter for "Azure":

    • Filter the API response where ProductCategory is "Azure".

  • Filter for "non-Azure":

    • Filter the API response where ProductCategory is other than "Azure".

  • Extract monthly costs:

    • Once filtered, calculate the total monthly costs for Azure or other products by summing up the relevant fields (Subtotal or Total).

2. Using files downloaded from the Partner Center portal

If you're working with files (.csv) downloaded from the Partner Center portal, you can manually or programmatically separate Azure charges.

Steps:

  • Download the billing file:

    • Go to the Partner Center > Billing workspace in the Partner Center portal and download the invoice reconciliation file.

  • Associate product categories:

    • Map the product category using the steps outlined in the section.
    • Cross-reference with the document when the product types are unclear. Ensure that all product types are correctly mapped.

  • Filter for "Azure":

    • Filter the API response where ProductCategory is "Azure".

  • Filter for "non-Azure":

    • Filter the API response where ProductCategory is other than "Azure".

  • Extract monthly costs:

    • Once filtered, calculate the total monthly costs for Azure or other products by summing up the relevant fields (Subtotal or Total).

By following these methods, whether through APIs or downloaded files—you can effectively separate Azure and non-Azure charges from product types and manage your costs.

How do you reconcile telco pay-as-you-go charges?

Reconciling telco pay-as-you-go charges involves comparing your daily rated usage line items with your monthly invoice reconciliation line items to ensure that all charges are accurate and accounted for. Let's break down the reconciliation process:

Step 1: Understand reconciliation files or line items

The reconciliation process relies on two sets of data:

  1. Daily rated usage files or line items:

    • Captures charges and usage on a daily basis.

    • Key fields:

      • BillingPreTaxTotal: The total charge before tax for the day.
      • Quantity: An approximation of the usage (for example, number of calls).
      • AdditionalInfo.NumMin: The actual call minutes used for the day.
      • EffectiveUnitPrice: The calculated price per unit (for example, per minute).

  2. Invoice reconciliation files or line items:

    • Aggregates charges and usage over the billing period.

    • Key fields:

      • Subtotal: The total charge before tax for the billing period.
      • BillableQuantity: The total billable usage (for example, total call minutes).
      • ChargeStartDate and ChargeEndDate: The charge cycle covered by the billing period of the invoice.

Step 2: Reconciliation process

1. Verify daily charges

  • To verify daily charges, use the BillingPreTaxTotal field in the daily rated usage reconciliation.

  • To confirm the actual call minutes used, cross-check the NumMin value in the AdditionalInfo field.

  • The Quantity field represents an approximation, so rely on NumMin for exact usage.

2. Aggregate daily usage and charges

  • Sum up the BillingPreTaxTotal values from the daily rated usage data to calculate the total charges for the billing period.

  • Sum up the NumMin values to calculate the total call minutes for the billing period.

3. Compare with invoice reconciliation

  • Compare the aggregated totals from the daily rated data with the corresponding fields in the monthly invoice reconciliation:

    • Charges: Ensure the sum of BillingPreTaxTotal matches the Subtotal in the invoice reconciliation.
    • Usage: Ensure the sum of NumMin matches the BillableQuantity in the invoice reconciliation.

4. Match product and SKU details

  • Use the ProductId and SkuId fields to match the daily usage data with the invoice data.

  • This step ensures that charges and usage are reconciled for each specific product or service.

5. Check call types

  • Break down the usage and charges by call type (for example, domestic, international, toll-free) to ensure accuracy.

  • Verify that the total call minutes and charges for each call type align between the daily data and the invoice.

Step 3: Example

Daily rated usage reconciliation line items:

CustomerName ProductId SkuId ProductName UsageDate ChargeType UnitPrice Quantity UnitType BillingPreTaxTotal BillingCurrency AdditionalInfo EffectiveUnitPrice
Constoso CFQ7TTC0JL2N 1 Microsoft 365 International Calling Plan - Outbound US 9/17/2021 New 1 0.1524 Per Call 0.15 USD { "NumMin": 0.2} 0.984251969
Constoso CFQ7TTC0JL2S 1 Microsoft 365 Audio Conferencing - Outbound US 9/18/2021 New 1 6.6275 Per Call 6.623381835 USD { "NumMin": 24.1} 0.999378625
Constoso CFQ7TTC0JL2S 1 Microsoft 365 Audio Conferencing - Outbound US 9/21/2021 New 1 2.97 Per Call 2.968154515 USD { "NumMin": 10.8} 0.999378625
Constoso CFQ7TTC0JL2S 1 Microsoft 365 Audio Conferencing - Outbound US 9/22/2021 New 1 0.0585 Per Call 0.05846365 USD { "NumMin": 0.3} 0.999378625
Constoso CFQ7TTC0JL2S 1 Microsoft 365 Audio Conferencing - Outbound US 9/23/2021 New 1 0.4485 Per Call 0.447924684 USD { "NumMin": 2.3} 0.998717244
Constoso CFQ7TTC0JL2S 1 Microsoft 365 Audio Conferencing - Outbound US 9/24/2021 New 1 0.0975 Per Call 0.097374931 USD { "NumMin": 0.5} 0.998717244
Constoso CFQ7TTC0JL2S 1 Microsoft 365 Audio Conferencing - Outbound US 9/29/2021 New 1 0.156 Per Call 0.15579989 USD { "NumMin": 0.8} 0.998717244
Constoso CFQ7TTC0JL2S 1 Microsoft 365 International Calling Plan - Outbound US 9/29/2021 New 1 0.2114 Per Call 0.211128825 USD { "NumMin": 1.4} 0.998717244
Constoso CFQ7TTC0JL2S 1 Microsoft 365 Audio Conferencing - Outbound US 9/30/2021 New 1 0.178 Per Call 0.177771669 USD { "NumMin": 8.9} 0.998717244
Total 10.89 49.3

Invoice reconciliation line items:

CustomerName ProductId SkuId ProductName ChargeType UnitPrice Quantity Subtotal TaxTotal Total Currency ChargeStartDate ChargeEndDate EffectiveUnitPrice BillableQuantity
Contoso CFQ7TTC0JL2N 1 Microsoft 365 International Calling Plan - Outbound US new 0.381 1 0.36 0 0.36 USD 9/1/2021 9/30/2021 0.225 1.6
Contoso CFQ7TTC0JL2S 1 Microsoft 365 Audio Conferencing - Outbound US new 0.352836167 1 10.53 0 10.53 USD 9/1/2021 9/30/2021 0.220755 47.7
Total 10.89 49.3

Reconciliation between the daily rated usage and invoice files or line items

  • Products: Each product (ProductId: CFQ7TTC0JL2N and SkuId: 1 or ProductId: CFQ7TTC0JL2S and SkuId: 1) is matched correctly.

  • For CFQ7TTC0JL2N:

    • Charges: The sum of BillingPreTaxTotal (0.36) matches the Subtotal in the invoice (0.36).
    • Usage: The sum of NumMin (1.6) matches the BillableQuantity in the invoice reconciliation (1.6).

  • For CFQ7TTC0JL2S:

    • Charges: The sum of BillingPreTaxTotal (10.53) matches the Subtotal in the invoice reconciliation (10.53).
    • Usage: The sum of NumMin (47.7) matches the BillableQuantity in the invoice reconciliation (47.7).

  • For both products:

    • Charges: The sum of BillingPreTaxTotal (10.89) matches the Subtotal in the invoice (10.89).
    • Usage: The sum of NumMin (49.3) matches the BillableQuantity in the invoice reconciliation (49.3).

Tip

  • Use NumMin for exact usage. The Quantity field in the daily rated usage is an approximation.

  • Ensure that free talk time allowances are accounted for, as exceeding these minutes result in extra charges.

  • Perform regular checks to catch any discrepancies early and avoid billing disputes.

  • Familiarize yourself with how charges are calculated, including any rounding rules, to better understand your bill.

By following these steps, you can effectively reconcile telco pay-as-you-go charges and ensure accurate billing.

How to find tiered pricing in the reconciliation files or line items

Understanding tiered pricing in reconciliation data and analyzing it effectively is essential for optimizing costs and maximizing value from your usage.

Let's delve into this concept and explore how you can use it to your advantage.

Tiered pricing

Think of tiered pricing as a staircase where each step represents a different usage level. As you use more, the cost per unit decreases, encouraging higher consumption.

Key fields

To find the tiered pricing in your reconciliation files or line items, look at the following fields and ensure you're optimizing your usage to benefit from the best rates.

  1. Unit price: This price is the initial rate per unit for the first tier. It's like the standard price before any discounts.

  2. Effective unit price: This price shows the actual rate you pay per unit after accounting for your total usage and tier discounts, reflecting the actual price after adjustments.

  3. Price adjustment description: Details about any modifications applied to your total cost, including:

    • Partner-earned credits: Rewards offered to partners for meeting specific criteria after providing managed service to their customers.
    • Volume-based discounts: Reduced rates for higher usage.
    • Promotional discounts: Special offers that lower the overall cost.
    • Other price modifications: Other adjustments affecting the final price.

Calculate your final cost

To determine your final cost, consider the EffectiveUnitprice and any adjustments noted in the PriceAdjustmentDescription.

Example

Imagine you used 150 units in a billing period with the following pricing tiers:

  • Tier 1: 0–100 units at USD 10/unit

  • Tier 2: 101–200 units at USD 9/unit

  • Unit price: USD 10

  • Partner earned credit (PEC): 15%

  • Effective unit price: USD 7.65

      Tier 2 unit price: USD 9
  PEC: USD 9 x 15% = USD 1.35
  Effective unit price = USD 9 – USD 1.35 = USD 7.65

  • Price adjustment description: "Partner earned credit 15%; Tier discount 10%"

Tip

Optimize usage for better pricing

  • Monitor usage: To approach higher tiers, regularly track your resource usage.

  • Plan strategically: If you're near a higher tier, consider increasing usage slightly for significant savings.

By addressing each aspect of tiered pricing systematically, you can make informed decisions to maximize cost efficiency and align your usage with optimal pricing tiers.

Understand ReservationOrderId prefixes

Efficient management of Azure reservations starts with understanding the ReservationOrderId prefixes. Understanding prefixes helps you identify the origin of your Azure reservations, allowing you to organize and optimize your resources more effectively. Here's what each prefix means:

  • PCTest: This prefix is for reservations acquired through the Partner Center for testing purposes. It's useful for distinguishing between test environments and production setups.

  • RIOderId: Reservations bought from the Partner Center for production use have this prefix. Identifying these reservations is crucial for managing live environments and ensuring proper resource allocation.

  • No prefix: If there's no prefix, the reservation was purchased using the cost management portal or API. This approach is ideal for segregating reservations made outside the Partner Center.

By familiarizing yourself with these prefixes, you can streamline your reservation management process and make informed decisions.

Related content