Bill level
Last updated: 2025-11-19 11:01:03
Bill Level
When you download bills of all end customers (or resellers) in Partner Center, it supports downloading bills at four levels. The difference is as shown in the table below:
Bill Level | Description |
Resource ID bill | Resource ID bill files of all end customers (or resellers) are packed into a ZIP file. After decompression, there will be one bill in the CSV format for each end customer (or reseller). |
Resource ID bill (consolidated) | Resource ID bill data of all end customers (or resellers) are consolidated in a single CSV bill file. You can filter the Owner UIN column to distinguish different end customer data, or filter the Admin UIN column to distinguish different reseller data. |
Detailed bill | Detailed bill filesof all end customers (or resellers) are packed into a ZIP file. After decompression, there will be one bill in the CSV format for each end customer (or reseller). |
Detailed bill (consolidated and aggregated by month) | Detailed bill data of all end customers (or resellers) are consolidated in a single CSV bill file. Data of the same type are aggregated by specific rules. You can distinguish different end customer data by filtering the Owner UIN column or distinguish different reseller data by filtering the Admin UIN column. |
Note:
To help partners comprehensively analyze costs and income, the resource ID bill (consolidated) and detailed bill (consolidated and aggregated by month) from the reseller and distributor perspective include partner cost data such as "saving plan deduction amount, saving plan deduction rate, original price of saving plan deduction component, partner discount rate, post-discount total price (excluding tax), partner voucher expenditure, actual pre-tax amount, tax rate, tax deduction, cash expenditure (including tax)." Bills from the second-level reseller perspective do not include this data.
Resource ID bill and detailed bill do not include partner cost data.
Detailed Bill Aggregation Rules
Transaction type fields with values as "Hourly settlement, Daily settlement, Spot, Hourly RI fee, Hourly Savings Plan fee" are aggregated, and other types are not aggregated.
Data of these fields "payer UIN, owner UIN, operator UIN, admin UIN, billing mode, transaction type, product, subproduct, component type, component name, resource ID, resource name, region, AZ, project, component list price, Component Price Unit, customer component contract price, price attribute, customer discount rate, savings plan deduction rate, partner discount rate, tax rate" whose values are the same are aggregated into one data entry.
Calculation rules for other fields after aggregation
"For fields such as Original Price, Reserved Instance Deduction Duration, Reserved Instance Deduction Component Original Price, Total Amount Before Voucher, Customer Voucher Expenditure, Total Amount, Savings Plan Deduction Amount, Savings Plan Deduction Component Original Price, Post-Discount Total Amount (Pre-Tax), Partner Cash Coupon Expenditure, Pre-Tax Actual Amount, Tax Deduction, Cash Expenditure (Tax Inclusive)", the sum of values of these fields are calculated.
The "Component Usage and Usage Duration" fields in detailed bills are deleted. The sum of values of these two fields is displayed in new fields Component Usage Aggregation, Usage Duration Aggregation".
"Usage Start Time" is the earliest time among the original data aggregated to this data entry.
"Usage End Time" is the latest time among the original data aggregated to this data entry.
"Transaction ID and Transaction Time" are displayed as "-".
Other fields remain unchanged and consistent with the detailed bill before aggregation.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback