MCM - Update ingest-usage-detals-overview for Sharon

Author: bandersmsft

articles/cost-management-billing/automate/automation-ingest-usage-details-overview.md

@@ -4,7 +4,7 @@ titleSuffix: Microsoft Cost Management
 description: This article explains how to use cost details records to correlate meter-based charges with the specific resources responsible for the charges. Then you can properly reconcile your bill.
 author: bandersmsft
 ms.author: banders
-ms.date: 04/15/2024
+ms.date: 05/30/2024
 ms.topic: conceptual
 ms.service: cost-management-billing
 ms.subservice: cost-management
@@ -47,28 +47,42 @@ To learn more about Marketplace orders (also known as external services), see [U
 
 Azure resource providers emit usage and charges to the billing system and populate the Additional Info field of the usage records. Occasionally, resource providers might emit usage for a given day and stamp the records with different datacenters in the Additional Info field of the cost records. It can cause multiple records for a meter or resource to be present in your cost file for a single day. In that situation, you aren't overcharged. The multiple records represent the full cost of the meter for the resource on that day.
 
-### Pricing behavior in cost details
+### Pricing behavior in cost and usage details
 
-The cost details file exposes multiple price points. They're outlined as follows.
+The cost and usage details file exposes multiple price points. They're outlined as follows.
 
-**PAYGPrice:** It's the market price, also referred to as retail or list price, for a given product or service.
-  - In all consumption usage records, `PayGPrice` reflects the market price of the meter, regardless of the benefit plan such as reservations or savings plan.
-  - Purchases and refunds have the market price for that transaction.
+**PAYGPrice:** - The market price, also referred to as retail or list price, for a given product or service.
+  - In all consumption usage records, `PayGPrice` reflects the market price of the meter, regardless of any benefit plan, such as reservations or savings plan, applied on that line item.
+  - Purchases and refunds reflect the market price for that transaction.
 
-When you deal with benefit-related records, where the `PricingModel` is `Reservations` or `SavingsPlan`, *PayGPrice* reflects the market price of the meter.
+In benefit-related records, where the `PricingModel` is `Reservations` or `SavingsPlan`, *PayGPrice* reflects the market price of the original meter, displaying what the price would have been without the application of a benefit.
 
-**UnitPrice:** It's the price for a given product or service inclusive of any negotiated discount that you might have on top of the market price (PayG price column) for your contract.
-  - In all consumption usage records, `UnitPrice` reflects the negotiated meter price that you have on your contract, regardless of the benefit plan such as reservations or savings plan.
-  - Purchases and refunds have the negotiated price for that transaction.
+**UnitPrice:** - The price for a given product or service inclusive of any negotiated discount that is applied on top of the `PaygPrice` based on your contract.
+  - In all consumption usage records, `UnitPrice` reflects the negotiated meter price based on your contract, regardless of any benefit plan such as reservations or savings plan, applied on that line item.
+  - Purchases and refunds reflect the negotiated price for that transaction.
 
-**EffectivePrice** It's the price for a given product or service that represents the actual rate that you end up paying per unit. It's the price that should be used with the quantity to do `price * quantity` calculations to reconcile charges. The price considers the following scenarios:
+**EffectivePrice** - The actual rate that you end up paying per unit for a given product or service. It's the price that should be used with the quantity to calculate charges (`price * quantity`) and reconcile them. The price considers the following scenarios:
   - Tiered pricing: For example: USD 10 for the first 100 units, USD 8 for the next 100 units.
   - Reservation/savings plan actual cost record: In the actual cost report, the effective price for a usage record is 0 because the resource, for example VM, is covered by prepaid commitment. The effective price for a purchase record shows the price of the purchase transaction.
   - Reservation/savings plan amortized cost record: In the amortized cost report, the effective price for a usage record is the prorated hourly price of the reservation/savings plan.
 
-**Quantity:** It's the number of units used by the given product or service for a given day. It aligns to the unit of measure used in actual resource usage.
+**Quantity:** - The number of units consumed per day by the given product or service. It relates to the unit of measure (UOM) used in actual resource usage.
 
-If you want to reconcile costs with your price sheet or invoice, note the following information about unit of measure.
+## Reconcile charges
+
+When you reconcile costs with your price sheet or invoice, the price points and quantity in cost and usage details file might differ in scale and granularity from these other documents.
+
+For customers with an Enterprise Agreement, the cost and usage details might have a UOM (for example, per day vs per month) that is different from the invoice or price sheet. Cost and usage details is presented at a daily granularity, while the invoice is aggregated at a monthly, quarterly or a different custom billing period grain.
+
+The following example illustrates how the same monthly total cost is represented differently across multiple reports for the same resource. This example considers a sample month of 31 days, and the invoice is generated every month.
+
+| **Report** | **Unit of measure** | **Unit price** | **Total monthly quantity** | **Total month cost** | **Daily quantity** | **Daily cost** |
+| --- | --- | --- | --- | --- | --- | --- | 
+| Invoice | 1/day | 100 | 31 | 3100 | N/A | N/A | 
+| Cost and usage details | 1/month | 3100 | 1 | 3100 | 0.032257961<sup> 1 </sup>| 100 | 
+| Price sheet | 1/day | 100 | N/A | N/A | N/A | N/A |
+
+<sup> 1 </sup> Since the total monthly quantity is 1 unit, the daily quantity is estimated to be 1/31 = 0.03225796
 
 **Price Sheet unit of measure behavior** - The prices shown on the price sheet are the prices that you receive from Azure. They're scaled to a specific unit of measure.
 
@@ -110,7 +124,7 @@ If you have charges that you don't recognize, there are several things you can d
 - Find people responsible for the resource and engage with them
 - Analyze the audit logs
 - Analyze user permissions to the resource's parent scope
-- Create an [Azure support request](https://go.microsoft.com/fwlink/?linkid=2083458) to help identify the charges
+- To help identify the charges, create an [Azure support request](https://go.microsoft.com/fwlink/?linkid=2083458) 
 
 For more information, see [Analyze unexpected charges](../understand/analyze-unexpected-charges.md).