Document Center

All Products

Document Center

DataWorks:Overdue payments

Last Updated:Mar 17, 2026

DataWorks has specific billing rules and overdue payment policies for its pay-as-you-go products. This topic describes these rules and policies.

Limitations

The billing rules and overdue payment policies described in this topic apply only to DataWorks pay-as-you-go products.

Billing and overdue payments

The following tables describe the billing rules and overdue payment policies for pay-as-you-go products.

Billed object	Billing cycle	Billing details	Overdue payment details
Serverless resource group (pay-as-you-go)	Daily	Each day, a bill is generated for the previous day's CU usage. The corresponding balance is frozen mid-month. The actual fee is deducted after the final bill is generated at the beginning of the next month. For more information about pricing, see Billing for Serverless resource groups.	Your account has an overdue payment for less than 360 hours You have a 360-hour grace period. Renewal reminders are sent at the 192nd, 288th, and 336th hours after your payment becomes overdue. Renew your service promptly. Your account has an overdue payment for more than 360 hours The service is suspended. You cannot start new instances. Instances that are already running can continue until they finish. Topping up your account after a payment is overdue The service is not suspended if you top up your account within 360 hours after the payment becomes overdue.
Number of scheduled instances	Daily	Each day, a bill is generated based on the number of successfully run instances from the previous day. The corresponding balance is frozen mid-month. The actual fee is deducted after the final bill is generated at the beginning of the next month. For more information about pricing, see Billing for task scheduling.	Your account has an overdue payment for less than 360 hours You have a 360-hour grace period. Renewal reminders are sent at the 192nd, 288th, and 336th hours after your payment becomes overdue. Renew your service promptly. Your account has an overdue payment for more than 360 hours The service is suspended. You cannot start new instances. Instances that are already running can continue until they finish. Topping up your account after a payment is overdue The service is not suspended if you top up your account within 360 hours after the payment becomes overdue.
Resource Group for Public Data Service	Hourly	Each hour, a bill is generated for the previous hour's usage. The corresponding balance is frozen mid-month. The actual fee is deducted after the final bill is generated at the beginning of the next month. For more information about pricing, see Billing for shared resource groups for DataService Studio.	Your account has an overdue payment for less than 360 hours You have a 360-hour grace period. Renewal reminders are sent at the 192nd, 288th, and 336th hours after your payment becomes overdue. Renew your service promptly. Your account has an overdue payment for more than 360 hours The service is suspended. You cannot call the published APIs. Topping up your account after a payment is overdue The service is not suspended if you top up your account within 360 hours after the payment becomes overdue.
Data Integration Internet traffic	Hourly	Each hour, a bill is generated for the previous hour's usage. The corresponding balance is frozen mid-month. The actual fee is deducted after the final bill is generated at the beginning of the next month. For more information about pricing, see Billing for Internet traffic.	Your account has an overdue payment for less than 360 hours You have a 360-hour grace period. Renewal reminders are sent at the 192nd, 288th, and 336th hours after your payment becomes overdue. Renew your service promptly. Your account has an overdue payment for more than 360 hours The service is suspended. You cannot start new instances. Instances that are already running can continue until they finish. Topping up your account after a payment is overdue The service is not suspended if you top up your account within 360 hours after the payment becomes overdue.
Data Quality instance	Daily	Each day, a bill is generated based on the number of successfully run instances from the previous day. The corresponding balance is frozen mid-month. The actual fee is deducted after the final bill is generated at the beginning of the next month. For more information about pricing, see Billing for Data Quality instances. Note A rule is considered successfully run and is billed even if alerts are reported or workflows are blocked due to data quality issues. The pay-as-you-go billing method has a daily limit of 10,000 Data Quality check instances. After the limit is reached, subsequent rule instances stop running. If you require a higher daily limit for scheduled instances, submit a ticket for consultation.	Your account has an overdue payment for less than 24 hours You have a 24-hour grace period. Renewal reminders are sent at the 12th and 23rd hours after your payment becomes overdue. Renew your service promptly. Your account has an overdue payment for more than 24 hours The service is suspended. You cannot start new Data Quality check instances. Started rule instances are not affected. Topping up your account after a payment is overdue The service is not suspended if you top up your account within 24 hours after the payment becomes overdue.
Intelligent baseline instance	Daily	Each day, a bill is generated based on the number of enabled baseline instances from the previous day. The corresponding balance is frozen mid-month. The actual fee is deducted after the final bill is generated at the beginning of the next month. For more information about pricing, see Billing for intelligent baseline instances. Note An hourly baseline for an hourly task is billed as one baseline instance. The pay-as-you-go billing method has a limit of 100 enabled baselines. After the limit is reached, no more baseline instances can be generated. If you require a larger number of baseline instances, submit a ticket for consultation.	Your account has an overdue payment for less than 24 hours You have a 24-hour grace period. Renewal reminders are sent at the 12th and 23rd hours after your payment becomes overdue. Renew your service promptly. Your account has an overdue payment for more than 24 hours The service is suspended. You cannot generate new baseline instances. Started baseline instances are not affected. Topping up your account after a payment is overdue The service is not suspended if you top up your account within 24 hours after the payment becomes overdue.
Alert text messages and phone calls	Daily	Not applicable	Not applicable
OpenAPI calls	Daily	Not applicable	If your account has an overdue payment, the service is immediately suspended. To avoid business interruptions, renew your service promptly.

References