Systematic Management of Cloud Costs and Multi‑Cloud Billing Solutions

Background : Public cloud has become a core infrastructure resource, and its cost share is increasing year by year. Managing multi‑cloud costs is challenging due to multiple vendors, products, discounts, packages, and varied bill formats, making cost visualization across departments, projects, and resource types exponentially difficult.

Key Problems :

High difficulty in management and monitoring – each cloud vendor has its own console and billing system, preventing unified, daily cost monitoring.

Inconsistent bill dimensions – different vendors use different billing units and product structures.

Cost allocation – bills cannot be split to specific business or project, causing delayed cost awareness.

Complex pricing – diverse discount policies and vouchers make precise cost calculation hard.

Lack of a comprehensive view – no unified dashboard for cross‑vendor cost comparison.

Solution Overview : Leveraging the Resource Cost Center (RCC) as a unified entry, a multi‑cloud electronic billing system was built to standardize bill ingestion, automate reconciliation, and close the payment loop.

RCC Capabilities include systematic billing, automated data matching, difference handling, one‑click payment submission, automated financial report generation, and real‑time cost forecasting.

Multi‑Cloud Electronic Billing System provides a unified standard for ingesting billing data from various clouds, delivering a consolidated view and detailed cost breakdown for internal analysis and external reconciliation.

Standardized Bill API defines a common data structure with fields such as instanceId (string, required), model (string, required, e.g., "c5.4xlarge 16 32768"), billMethod (string, required, e.g., "包年/包月/按需"), billType (integer, required, 1 for prepaid, 2 for postpaid), orderType (string, required), unit (string, required), currency (string, required, e.g., "CNY" or "USD"), region (string, required), price (string, required), priceUnit (string, required), discount (integer, required), foldUP (integer, optional), resourceTypeDesc (string, required), serviceTypeDesc (string, required), billTypeDesc (string, required), configurationChange (json, required, e.g., {"startTime":"变更开始时间","endTime":"变更结束时间","configurationBefore":"变更前型号配置","configurationAfter":"变更后型号配置"} ), billChange (json, required, e.g., {"startTime":"变更开始时间","endTime":"变更结束时间","billBefore":"变更前计费","billAfter":"变更后计费"} ), usage (integer, required), duration (integer, required), timeUnit (string, required, e.g., "秒", "分钟", "小时", "天", "月", "年"), size (integer, optional), unsubscribe (json, required), renew (json, required), cycle (integer, optional), realCost (string, required), discountCost (string, required), vouchersCost (string, optional), specialCost (string, optional), cost (string, required), formula (string, required, e.g., "300GB * 0.0018元/GB * 0.25折 * 1折上折 * 13.6456h"), startTime (string, required), endTime (string, required), projectId (string, optional), tagInfos (json, required), accountName (string, required), date (string, required, format YYYY‑MM‑DD), month (string, required), financialUnit (string, required), orderNumber (string, required), instanceName (string, required), discountName (string, optional), config (string, required).

Tagging Strategy : A unified tag key projectid is used, with the value being the iQIYI project ID. This enables cost allocation to projects, business lines, and basic services.

Automation & Workflow : The system supports daily T+1 bill delivery, automated reconciliation, one‑click payment submission via OA integration, and real‑time cost analysis. Visual dashboards illustrate hybrid‑cloud cost trends, allocation, and forecasting.

Future Roadmap : Plans include cost forecasting, budget management with alerts, cost responsibility enforcement, daily automated reconciliation, AI‑generated optimization suggestions, and AIGC‑driven custom report generation.