Querying Expenditure Details
You can view and export customer expenditure details.
Procedure
- Sign in to Huawei Cloud as a partner.
- In the drop-down list of your account name, click Partner Center to go to the Partner Center.
- On the top navigation, select Sales > Customer Business > Customer Expenditure.
- Click the Expenditure Details tab.
- Set search options to search for expenditure details.
Search options include billing cycle, customer name, partner name, account manager, order/transaction ID, resource ID, resource name, product type, association type, billing mode, bill type, and region.
Click the eye icon next to a header to show or hide the complete content in the column. The content is hidden by default. For example, you can click the eye icon next to Customer Name/Account to show or hide the complete content of customer names.
- In the expenditure details list, you can view information of Spent On, Product, Order No., Total Expenditure, and Status.
- You can select Hide 0 Expenditures for Amount Due to exclude related data from the list.
You can search for expenditure details by month. To view expenditure details generated more than 18 months ago, contact your ecosystem manager.
- In the expenditure details list, you can view information of Spent On, Product, Order No., Total Expenditure, and Status.
- Export expenditure details.
- Export selected records.
Click Export > Export Selected, specify the transaction time, and click Export.
A message is displayed indicating that the export task has been created.
- A maximum of 5,000,000 records can be exported at a time.
- When using the export function of Partner Center, please note that any sensitive information, such as customer names, mobile numbers, and email addresses, will be anonymized.
- View export history.
- Choose Export > View Export to switch to the Export History page.
- Click Download in the Operation column to download and view the exported expenditure details.
- Export selected records.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.