# Elastic Billing transition > Source-anchored research for Elastic Billing transition. Run status: COMPLETED. Parent: [Atlas Billing Mechanics and Cost Visibility](https://llms-explorer.com/tree/atlas-billing-mechanics-and-cost-visibility/) · 5 facets · 8 facts · page: https://llms-explorer.com/tree/elastic-billing-transition/ ## Definitions - The Elastic Billing Enabled indicator means the feature is enabled; it does not by itself confirm that Elastic Billing is active. Atlas identifies the transition through credit usage and the organization activity-feed event Active Invoicing Period initiated; the billing overview payment-method section reflects the change. (high confidence) (verified as of 2026-10-18) — [source](https://www.mongodb.com/docs/atlas/billing/subscriptions/) ## How it works - Atlas distinguishes Elastic Billing being enabled from an active Elastic Billing subscription: the indicator means only that the feature is enabled. When the organization runs out of credits, Atlas says it automatically transitions to Elastic Billing; the billing FAQ says Atlas use can continue without interruption and usage beyond credits is invoiced monthly. (high confidence) (verified as of 2026-10-18) — [source](https://www.mongodb.com/docs/atlas/billing/subscriptions/) - For a Monthly Commitment subscription, Atlas charges the prorated monthly commitment when usage is below that commitment at month end; unused credits can cover later overages during the subscription term. (medium confidence) (verified as of 2026-10-18) — [source](https://www.mongodb.com/docs/atlas/billing/subscriptions/) ## Problems, failure modes and limitations - Google Cloud Marketplace's SKU catalog lists historical Atlas Pro overage entries named `MongoDB Atlas - Elastic Billing Subscription - Deprecated Overage Atlas Credits` dated 2020-09-28 and `MongoDB Atlas - Elastic Billing Subscription Overage Atlas Credits` dated 2020-11-26. These catalog records establish historical SKU labels only; they do not show that either SKU is currently active. (low confidence) (verified as of 2026-10-13) — [source](https://cloud.google.com/skus/sku-groups/google-cloud-marketplace) ## Comparisons and alternatives - Google Cloud Marketplace's SKU catalog lists separate MongoDB Atlas Elastic Billing subscription-credit and overage-credit SKUs, including a deprecated overage SKU. The catalog rows carry dates from 2020 through 2021, so they document historical SKU labels rather than current transition behavior. (low confidence) — [source](https://cloud.google.com/skus/sku-groups/google-cloud-marketplace) ## Facts and statements - For a Monthly Commitment subscription, Atlas bills usage beyond the credits if the credits run out before expiration and Elastic Billing is enabled. Atlas says this transition can produce two tax invoices for the same billing period; the cloud invoice shows an Atlas Elastic Invoice and the final Atlas Monthly Commit payment. The Available Credits view and the Activity Feed event `Active Invoicing Period initiated` help confirm the transition. (medium confidence) (verified as of 2026-10-18) — [source](https://www.mongodb.com/docs/atlas/billing/subscriptions/) - For Google Cloud Monthly Commitment subscriptions, Atlas says that after cumulative usage exceeds the total commitment, the account moves to Elastic Billing for the rest of the commitment. Google Cloud bills the monthly minimum plus the full value of usage after the total commitment is exhausted. (low confidence) (verified as of 2026-10-18) — [source](https://www.mongodb.com/docs/atlas/billing/subscriptions/) - Google Cloud Monthly Commitment billing has a separate overage shape: after cumulative usage exceeds the total commitment, Atlas bills full monthly usage for the rest of the commitment in addition to the monthly minimum. MongoDB's example shows a $1,000 minimum plus $4,000 usage producing a $5,000 Google Cloud charge after a $12,000 annual commitment is exhausted. (low confidence) (verified as of 2026-10-18) — [source](https://www.mongodb.com/docs/atlas/billing/subscriptions/)