Atlas Billing Mechanics and Cost Visibility

Parent: MongoDB Atlas Cost Optimization · Published reference · snapshot 2026-10-19 · skill mongodb-operations-expert/references/atlas-billing-mechanics-and-cost-visibility.md

Also known as: Billing and Cost Chargeback, Azure Marketplace Atlas Billing, GCP Marketplace Atlas Billing, Atlas GCP EDP Credits

↓ Facts as markdown all context files

Source-anchored research for Atlas Billing Mechanics and Cost Visibility. Run status: COMPLETED.

These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.

Definitions

Service accounts (client ID/secret) are the authentication method shown in MongoDB's Go SDK billing examples; API key pairs also work (OpenCost). Cross-org billing: linked invoices are visible only to Organization Billing Admin or Owner of the paying organization. (medium confidence) [source]
If a subscription activation code is not added within the first 30 days of use, MongoDB charges the account's credit card, and card charges are non-refundable. (low confidence) (verified as of 2026-10-18) [source]

Structure and components

Usage Details is the line-item layer: dates used and billed, quantity (server hours), project, hosting cloud provider, SKU rate, and amount. Usage not tied to a cloud provider appears under 'Other Atlas Usage'. It can be downloaded as CSV. (medium confidence) [source]
Credits applied to an invoice appear in the CSV as a row whose Description contains 'Credit' with a negative Amount; filter that row out to get the pre-credit subtotal. (low confidence) [source]
Invoices list credits as a payment method; CSV exports contain a row whose Description contains 'Credit' with a negative Amount (filter it out to compute the subtotal, or use it to see when credits ran out). Invoice status PREPAID means the prepaid subscription covered the invoice with credits. (low confidence) [source]

How it works

Billing lag: usage at the end of a billing period can land on the next period's invoice (e.g. Oct 31 usage processed in November). Data transfer, private endpoint and backup costs can post days later because of cloud provider reporting lag. The invoice schema notes charges typically post the next day. (medium confidence) [source]
Tags in invoice CSVs and Admin API responses reflect the tag configuration at the moment of generation or the call. Changing tags mid-cycle makes the invoice show only the latest configuration, so retag history is not preserved in billing data. (medium confidence) [source]
When a subscription expires, Atlas charges remaining usage to the payment method on file, reverts paid support plans to Basic, risks suspension if the payment method declines, and bills unpaid charges on the next subscription activation. Deployments must be terminated to stop charges. (low confidence) (verified as of 2026-10-18) [source]
Reactivating Developer or self-serve Pro after cancelling bills support retroactively from when a non-Basic plan was last active, up to 90 days back; the forum example showed a confirmation prompt adding ~$705.48 of prior charges to the pending invoice. Exceptions: Developer to self-serve Pro, and self-serve Pro to subscription-tied Pro. (high confidence) [source]
Dollar-threshold conditions take a USD amount. The 'current bill' conditions (single project, organization) are organization-only, count the monthly total, and reset when the current pending invoice closes. 'Amount billed yesterday' ignores credits applied for that day and applies to both organizations and projects. (high confidence) (verified as of 2026-10-18) [source]
The credit-card-expiry alert triggers at the start of the month the card expires, and Atlas enables it automatically when a card is first added. (low confidence) [source]
Invoice tags reflect the tag configuration at the moment the CSV is generated or the API is called. If a team retags a resource mid-billing-cycle, the whole invoice shows only the latest tags. Showback and chargeback reports must therefore treat tags as a snapshot, not a history. (high confidence) [source]
Because Atlas fetches tags at export time, clusters deleted before the export appear untagged on the invoice. A customer request filed 2026-06-24 (CUSTOMER-I-10624) asks Atlas to record tags when the cost is incurred. Its status is Started with 5 votes. On 2026-07-15 MongoDB said it is evaluating priority, with no timeline. The requester has no reliable workaround and matches creation and deletion logs to line items by hand. (low confidence) (verified as of 2026-07-15) [source]

How-to and procedures

To create or modify tags a user needs the Project Owner role on the project or the Organization Owner role on its parent organization. Atlas records every tag add, change or delete in the Project Activity Feed. Tags can be managed from the Atlas UI, Admin API, Atlas CLI, or the Terraform provider. (medium confidence) [source]

Measurements and reference values

Dedicated clusters (M10+) run a minimum 3-node replica set, so an idle cluster bills 72 server hours per calendar day (3 x 24); billing follows provisioned instances, not actual use. Daily rows of 72 hours on an invoice are therefore normal. (medium confidence) [source]
A buyer-side advisory firm (Redress Compliance, unsourced estimates, sells negotiation services) claims a default 3-year Atlas Credits commit with 15-30% annual ramp; treat as unverified. (low confidence) (verified as of 2025-09-29) [source]
A MongoDB staff member (Andrew Davidson, 2024-01-05) stated Atlas Developer is priced starting at $49/month, billed at the greater of $49 or 20% of total monthly charges, and Atlas Pro starts at $799/month. (low confidence) (verified as of 2024-01-05) [source]
Third-party guidance says premium support typically costs up to 20% of monthly cluster spend, with negotiated rates for large enterprise deals; this is consistent with the 20% forum figure but is not an official MongoDB price. (medium confidence) (verified as of 2026-10-18) [source]
Granular database auditing, customer-key encryption at rest and LDAP are paid add-ons on Developer and Pro but included in Enterprise and Platinum; the billing docs say the 15% (KMS/LDAP) and 10% (auditing) cluster uplifts exclude Enterprise and Platinum customers. (medium confidence) (verified as of 2026-10-18) [source]
Atlas Flex clusters are the one built-in cost ceiling: priced at $8 to $30 per 30 days and capped at $30 per month, billed hourly, from 5 GB storage and 100 ops/sec base up to 500 ops/sec. (low confidence) (verified as of 2026-10-18) [source]

Problems, failure modes and limitations

Atlas billing alerts only notify. A MongoDB community moderator stated in April 2023 that no feature stops services when a billing threshold is reached and suggested a feature request; the current docs describe alert conditions only and list no spend-limit setting. (medium confidence) (verified as of 2026-10-18) [source]
The billing docs frame alerts as 'Billing Quota Management': they notify a designated person when a bill exceeds a USD limit or a credit card is about to expire. (medium confidence) [source]
The AWS page says a credit card cannot be added as backup payment while the AWS Marketplace subscription is active. (low confidence) [source]
Cluster labels will be deprecated in a future release, and MongoDB strongly recommends resource tags instead. (low confidence) (verified as of 2026-10-18) [source]

Comparisons and alternatives

Billed Usage can differ from Usage when a month's usage is below the subscription's monthly minimum, or when one month's billed usage encompasses usage from multiple months. (medium confidence) [source]
Gross-spend change alerts fire on a percentage increase versus the prior period (previous day, previous 7 days, previous 30 days). The organization variants are configured on the Organization Alerts page; the project variants (daily and weekly billing change) on the Project Alerts page. (medium confidence) (verified as of 2026-10-18) [source]

Facts and statements

Atlas charges for services at the organization level and posts charges the day after they are incurred. Viewing billing needs Organization Billing Viewer or higher; changing payment method or billing profile needs Organization Owner or Billing Admin. (medium confidence) [source]
The current (pending) invoice page has: header card (amount due, total usage cost, billing info, downloads as PDF usage summary, CSV usage summary, or CSV FOCUS report), Payment Details, Total Usage chart, By Deployment chart, Summary By Project table (excludes subscription charges), Summary by Service table, and Usage Details. (medium confidence) (verified as of 2026-10-18) [source]
Payment Details columns: payment method (prepaid/promotional credits, monthly commitment, marketplace, credit card, PayPal), Date, Payment status, Usage, Billed Usage, Total Cost, Amount Due, Actions (PDF, VIEW DETAILS, PAY NOW for YayPay customers, RETRY for failed payments). Total Cost = unit price x billed usage + taxes. (medium confidence) [source]
Metering cadence differs by service: dedicated clusters hourly, data transfer daily, BI Connector as a daily uplift capped at a monthly maximum, support minimum computed once monthly per org, Flex clusters capped at $30/month. Support appears as a separate line per cloud provider (AWS Support, Google Cloud Support, Microsoft Azure Support). (medium confidence) (verified as of 2026-10-18) [source]
If an org fails to pay an invoice for over 30 days, Atlas suspends the org and stops backups without terminating them. Over 60 days, Atlas locks the org and can terminate backups and deployments. (low confidence) (verified as of 2026-10-18) [source]
Under cross-organization billing, the paying org's invoice lists charges for all linked orgs, each linked org also gets its own monthly invoice, and an unmet monthly minimum is distributed across linked invoices in proportion to their usage. (low confidence) [source]
The Admin API exposes invoices at /api/atlas/v2/orgs/{ORG_ID}/invoices (list), /invoices/{INVOICE_ID} (single, JSON or CSV), and /invoices/pending. The list returns id, startDate, endDate, amountBilledCents; detail returns lineItems with sku, totalPriceCents (unit price x quantity x 100), groupId (project). Reading needs Organization Billing Viewer. (medium confidence) (verified as of 2026-10-18) [source]
Past invoices can be filtered by status (pending payment, $0.00 total, paid) and by date range; the Billing Cost Explorer retains up to 18 months of billing data. (medium confidence) (verified as of 2026-10-18) [source]
Cost Explorer is in the Billing section of the Atlas UI and is visible only to users with the Organization Owner, Billing Admin or Organization Billing Viewer role. (high confidence) [source]
Cost Explorer groups and filters usage by organization, project, cluster and service, showing a stacked-column Usage chart and a Usage By Month table. The organization filter requires cross-organization billing. (high confidence) [source]
The docs chart the past six months in Cost Explorer and allow access to billing data up to the past 18 months. The announcement blog describes 'up to 18 months' as the window. (medium confidence) (verified as of 2026-10-18) [source]
The Cost Explorer API is asynchronous: POST /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage (createOrgBillingCostExplorerUsageProcess) returns a 64-character token; GET .../costExplorer/usage/{token} (getOrgBillingCostExplorerUsage) returns results, or a 'processing' response telling the caller to retry later. (high confidence) [source]
The Cost Explorer query body requires startDate (inclusive) and endDate (exclusive), both of which must be the start of a month. Optional fields: organizations, projects, clusters (24-hex IDs), services (enum such as Clusters, Storage, Backup, Data Transfer, Support, Credits, AI Model APIs), groupBy (organizations|projects|clusters|services) and includePartialMatches (default false). A groupBy dimension needs at least one filter value for it. (medium confidence) (verified as of 2026-10-18) [source]
The Atlas CLI exposes the Cost Explorer API as `atlas api invoices createCostExplorerProcess --orgId <id> --file request.json` (autogenerated 1:1 from the Admin API; version 2023-01-01). (low confidence) (verified as of 2026-10-18) [source]
The 'Return All Pending Invoices for One Organization' endpoint returns line items whose results.lineItems.tags field reflects applied resource tags, so FinOps tools can break spend down by environment or team. Atlas's published Go SDK examples also list historical invoices (with linked invoices) and export to CSV or JSON. (high confidence) [source]
The Atlas FOCUS Data API (FOCUS 1.3, CSV only) works as list invoices (GET /orgs/{orgId}/associatedInvoices), request report (POST /orgs/{orgId}/invoices/{invoiceId}/reports), then retrieve (GET .../reports/{reportId}). States run PENDING, RUNNING, SUCCEEDED or FAILED. Poll no more than every 5 seconds. The download URL lasts 15 minutes and the report 7 days. Each request covers one invoice for one organization. (low confidence) (verified as of 2026-10-18) [source]
FOCUS reports cover usage-based costs only and exclude shortfall charges, tax line items and adjustments or refunds. Pending-month values are estimates, so re-pull after the month closes. BilledCost and EffectiveCost are already in billing currency; PricingCurrency* columns stay in Atlas Credits. (low confidence) (verified as of 2026-10-18) [source]
Third-party tools consume Atlas billing data with read-only billing credentials. DoiT uses a service account with Organization Billing Viewer, Read Only and Member roles, imports six months on connect and then updates hourly. The OpenCost plugin uses an org API key pair and says MongoDB detailed costs are only retrievable for the current month. (medium confidence) (verified as of 2026-10-18) [source]
Atlas subscription types are Elastic (monthly invoice for usage, no commitment), Prepaid (credits bought up front for a chosen term), Flex Commitment, Monthly Commitment and Marketplace. Purchase of commitments goes through MongoDB Sales; activation needs Organization Owner or Organization Billing Admin. (medium confidence) [source]
Flex Commitment: unused credits are charged in the last month of the term. Monthly Commitment: each month bills the greater of usage or the prorated monthly commitment, and unused credits carry forward to cover later overages in the term. (low confidence) [source]
Available credits are drawn down from the top item to the bottom in the order shown in the Available Credits table; upcoming credits appear grey and are not yet spent. Expired credits appear in the History table. (medium confidence) [source]
If a Monthly Commitment org runs out of credits it automatically transitions to Elastic Billing, and usage beyond credits is billed. The transition produces two tax invoices for the same billing period. The Elastic Billing indicator shows only that it is enabled, not that it is active. (low confidence) (verified as of 2026-10-18) [source]
On Google Cloud Monthly Commitment the monthly minimum is total commitment divided by months; once cumulative usage exceeds the total commitment, the account moves to elastic billing and pays the minimum plus elastic usage. (low confidence) (verified as of 2026-10-18) [source]
Direct Atlas pay as you go accepts credit card, PayPal and invoice with no minimum; the AWS Marketplace pay-as-you-go listing removed the earlier upfront-commitment requirement (page updated 2025-09-23). (low confidence) (verified as of 2025-09-23) [source]
Atlas support tiers are Basic (free), Developer, Pro and Enterprise; the plans page also lists Platinum. Initial Severity-1 response goals: Developer 8 hours, Pro 2 hours, Enterprise 30 minutes, Platinum 15 minutes (the docs say Enterprise 15 min to 2 hours). (medium confidence) (verified as of 2026-10-18) [source]
Neither the Atlas support docs nor the public Atlas support plans page publishes dollar or percentage prices; exact cost is shown in the Atlas UI (organization Support page, View plan) or via sales, and Enterprise is arranged by contacting MongoDB. (high confidence) (verified as of 2026-10-18) [source]
Only users with the Organization Owner role can change an organization's support plan. Developer has a 30-day free trial and auto-enrolls into paid Developer at the estimated cost afterwards. (medium confidence) [source]
Switching plans changes billing on the first day of the next month; canceling during a trial stops billing immediately; canceling outside a trial takes effect at month end with billing continuing until then. (low confidence) (verified as of 2026-10-18) [source]
On invoices, paid support appears as a monthly total in the Summary and as per-cloud-provider line items in Details, split proportionally to usage per provider; unattributed support lands under Other Atlas Usage. The support minimum is computed once per month for the whole organization. (low confidence) (verified as of 2026-10-18) [source]
Billing alerts are created from the Organization Alerts page by choosing Target = Billing. Conditions offered: Credit card is about to expire; Amount billed yesterday is above; Current bill for any single project is above; Current bill for the organization is above; Organization gross spend daily, weekly and monthly change is above. (high confidence) (verified as of 2026-10-18) [source]
Managing all organization alerts needs the Organization Owner role; Organization Billing Admin has limited authorization to manage billing alerts. Project alerts need Project Owner or Project Alerts Manager. (medium confidence) [source]
Billing alert recipients: by default Organization Owners and Billing Admins. If a Billing Email Address is set and 'Only send invoice emails to the Billing Email Address' is unchecked, alerts go to that address plus Owners and Billing Admins; if checked, to the billing address only. (medium confidence) (verified as of 2026-10-18) [source]
Billing alerts can be delivered through Atlas Organization roles, Atlas User, Email, Mobile (SMS), Slack, PagerDuty, Datadog, VictorOps, Opsgenie and Microsoft Teams. The 'send if condition lasts at least' and 'resend after' options are not available for billing alerts, which are event-based. (medium confidence) (verified as of 2026-10-18) [source]
Atlas self-serve marketplace listings on AWS, Google Cloud and Azure are Pay-as-You-Go subscriptions with no upfront commitment. (high confidence) [source]
Atlas usage and support costs bought through the AWS Marketplace are billed together to the customer's AWS account daily, with no payment minimum. (medium confidence) (verified as of 2025-09-23) [source]
For marketplace subscribers the invoice comes from the marketplace, not MongoDB. The subscriptions page says purchasers receive an invoice with an amount due through that marketplace, and no MongoDB tax invoice. (medium confidence) [source]
Before an Atlas organization can be linked to an AWS, Azure or GCP billing account, all outstanding or failed invoices in that organization must be resolved. (high confidence) [source]
Linking is per Atlas organization: after subscribing in the cloud console, the user picks an organization on the Atlas 'Select an Organization to Link' page. A disabled Link button means the organization is ineligible; a tooltip gives the reason. (high confidence) [source]
After linking, Payment Method stays empty until the cloud sync finishes, then shows the marketplace subscription. The Payment Method Edit button is disabled while the subscription is active; the only way to remove it is to unlink on the cloud side. (high confidence) [source]
Unlinking is done in the cloud console: AWS 'Cancel Subscription' on the agreement, Azure 'Cancel subscription' on the resource, GCP 'Cancel Purchase' on Your Orders. (high confidence) [source]
Cancelling the AWS subscription unlinks billing but does not delete Atlas resources or data, and the AWS page warns charges continue for them. Plan a replacement payment method in Atlas before cancelling. (low confidence) [source]
Azure linking lets the user add optional key-value tags on the Azure subscription at purchase time. (low confidence) [source]
Atlas docs for the three marketplace pages cover Subscriptions only. They do not describe private offers, marketplace contracts, cloud commitment drawdown, required cloud roles, or invoice frequency for Azure and GCP. (medium confidence) (verified as of 2026-10-18) [source]
Private-offer-only marketplace listings exist as a separate procurement path with fixed-term contract pricing (for example an AWS listing for MongoDB Enterprise Advanced on GovCloud, 12 months, no refunds). That listing is not Atlas Pay-as-You-Go. (low confidence) (verified as of 2026-10-18) [source]
Atlas resource tags are key-value pairs added to projects and clusters. Limits: 50 tags per cluster, keys and values up to 255 characters each, unique keys, and each tag value on at most 1,000 resources. Keys and values are case-sensitive, so environment and Environment are different keys. (high confidence) (verified as of 2026-10-18) [source]
In the invoice CSV, Atlas adds one column per tag key with the header Tag/<your key>, and the cell holds the tag value. The Admin API returns the tags in the results.lineItems.tags field of the Return All Pending Invoices for One Organization endpoint. (high confidence) [source]
Per the 2023 GA announcement (updated 2025-03), tags usually appear on invoice line items within 48 hours of being added. Line items not billed at the cluster level are not eligible for tags, and cluster-related line items with no tag stay untagged. These statements pre-date the current docs, which also mention project tags, so recheck eligibility before relying on them. (low confidence) (verified as of 2025-03-11) [source]
MongoDB's recommended tagging practice: use a standardized, case-sensitive format across all resource types, and use a consistent cost-allocation key such as cost-center or billing-unit. Also apply environment and application tags to every resource, use namespaces or prefixes for business units, enforce a mandatory-tag policy with regular checks for untagged deployments, and manage tags through the Admin API, Atlas CLI or Terraform provider. (high confidence) [source]
Atlas stores tag values in plain text. Billing can read them, and Atlas sends cluster tags to the Datadog and Prometheus integrations. Tags must not hold PII or PHI. (high confidence) [source]
The Atlas Architecture Center's FinOps path combines four mechanisms. Tags give cost allocation by department, project or cost center. The pending-invoices Admin API feeds external FinOps tools. Cross-organization billing gives one paying organization visibility across linked organizations. MongoDB Charts billing dashboards accept tag-based charts and filters. Cost Explorer groups only by organization, project, cluster and service, not by tag. (medium confidence) (verified as of 2026-10-18) [source]
The FinOps Framework defines allocation as apportioning costs to those responsible for them. Resource-level naming conventions and tags make that finer-grained. The strategy decides whether costs go to showback (to teams), chargeback (to finance) or cost-center allocation. Reports should surface spend not covered by the allocation metadata, and shared costs are split by a stated model (proportional, fixed or even). Tagging works better with automation and infrastructure as code. (medium confidence) [source]

Children

Atlas Billing and Invoice Anatomy
Atlas Cost Explorer and Billing Data API
Atlas Credits Prepaid Subscriptions and Overage
Atlas Support Plan Pricing
Billing Alerts and Budget Controls
Cloud Marketplace Billing for Atlas (AWS GCP Azure)
Resource Tags and Cost Allocation (Showback/Chargeback)
Admin API alert configurations for billing events
Atlas Admin API invoice endpoints (frontier, viability 3.05 / 5, below research gate)
Atlas Charts billing dashboards (frontier)
Billing incidents and refunds (frontier, viability 2.30 / 5, below research gate)
Credit expiry and History table (frontier)
Elastic Billing transition
Flex cluster spend ceiling
MongoDB Charts billing dashboards (frontier, viability 2.85 / 5, below research gate)
Project-level billing change alerts (frontier)
Retroactive support billing on reactivation (frontier)
Shared-cost splitting for Atlas projects (frontier, viability 2.95 / 5, below research gate)
Support line items per cloud provider on invoices (frontier)
Unlinking marketplace billing safely

← the whole tree · 3D view· how to read this page