Atlas Billing and Invoice Anatomy

Parent: Atlas Billing Mechanics and Cost Visibility · Published reference · snapshot 2026-10-19 · skill mongodb-operations-expert/references/atlas-billing-mechanics-and-cost-visibility.md · viability 4.65 / 5 (research)

↓ Facts as markdown all context files

Atlas bills at the organization level and posts usage charges the day after they are incurred, itemized on a pending (current) invoice and past invoices. Each invoice page has Payment Details, Total Usage and By Deployment charts, Summary by Project and Summary by Service tables, and a Usage Details line-item layer (dates, quantity in server hours, project, cloud provider, SKU rate, amount). This pack draws on 6 source pages across 2 hosts (MongoDB Atlas billing docs, the Admin API invoice reference, a community forum thread and a OneUptime blog) and covers definitions, structure, mechanism, parameters, how-to, examples, measures and problems.

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

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. [source]
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. [source]
Understand MongoDB Atlas billing components, set up cost alerts, query invoices via the API, and apply cost-saving strategies for your clusters. [source]

Structure and components

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. [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. [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. [source]
Return All Line Items for One Invoice by Invoice ID [source] — Admin API operation
Usage charges for the Embedding and Reranking API appear in the Summary by Service section of your invoice under AI Model APIs. [source]
Usage charges for Automated Embedding appear in the Summary by Service section of your invoice under Automated Embedding. [source]
While invoices vary depending on consumption and feature usage, you can see how you incur costs for all of the possible Atlas services listed in the Summary by Service section. [source]
Return All Invoices for One Organization [source] — Admin API operation
Return One Invoice as CSV for One Organization [source] — Admin API operation
The Premium Features section of your Atlas bill includes additional features such as Advanced Security, Database Auditing, and Online Archive, with the costs based on usage, subscription, or resource consumption. [source]
Return All Pending Invoices for One Organization [source] — Admin API operation
Return All Invoice Reports for One Invoice [source] — Admin API operation
Breaks down your total costs by the types of Atlas services you use across all your projects. [source]

How it works

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). [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. [source]
Atlas distributes your support charges proportionally across the cloud providers that host your usage. If your usage spans multiple cloud providers, your invoice lists a separate support line item for each provider, such as AWS Support, Google Cloud Support, and Microsoft Azure Support. If you don't have usage on a cloud provider, no support line item appears for that provider. Support usage that isn't associated with a cloud provider, such as usage for Atlas Embedding and Reranking API, appears under Other Atlas Usage. [source]
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. [source]
How Atlas collects each support charge depends on your active payment methods. If you pay Atlas directly, Atlas charges all of your support line items. If you have a marketplace commitment with a cloud provider, Atlas routes that provider's support charges to the corresponding marketplace. If you have a combination of payment methods, Atlas routes each provider's support charges accordingly. For example, if you have an AWS Marketplace commitment and pay for your other usage directly, Atlas routes your AWS support charges to AWS Marketplace and charges your Google Cloud and Microsoft Azure supp [source]
Atlas billing covers compute, storage, backup, and data transfer charged hourly. Use the Admin API to retrieve invoices and break down costs by project, set spending alerts to catch overruns early, pause non-production clusters during off-hours, and use the Performance Advisor to right-size clusters that are over-provisioned. Online Archive is the most effective way to reduce storage costs for time-series or archival workloads. [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. [source]
MongoDB Atlas bills hourly for compute, storage, data transfer, and additional services such as Atlas Search and online archive. Understanding the billing model and using Atlas cost management tools helps prevent budget surprises and supports FinOps practices. [source]
Atlas includes the cost of default storage in the cluster's hourly rate. However, if you customize storage capacity, Atlas charges for the full amount of storage without deducting the cost of the default storage capacity. If you enable Cluster Auto-Scaling, Atlas charges you based on the actual storage usage after you apply auto-scaling. [source]
Atlas calculates your support minimum once per month for your entire organization, separately from these per-provider charges. If your support usage for the month is below your minimum, Atlas bills the difference to your primary payment method at the end of the month. If you have multiple commitments, one commitment is designated as your primary payment method. Most customers have a single commitment and aren't affected by this designation. [source]
If you enable the Atlas BI Connector, Atlas charges as a daily uplift on the cluster's cost, which you can view in the cluster console. The daily rate follows sustained-usage pricing, meaning it is charged only up to a monthly maximum. [source]
Atlas charges dedicated clusters on an hourly basis and you pay only for the time your cluster is active. The cost depends on factors like the region, cloud provider, and usage (CPU, memory and storage). This estimated price of your cluster is available when you create or edit a cluster. [source]
For Cloud Backups, Atlas charges for storage of data in your replica set, configuration server, and network transfer during snapshot restoration. If you enable Continuous Cloud Backups, Atlas charges you according to the continuous cloud backup rates. [source]
Atlas bills for Automated Embedding service based on your usage. The charges apply per token. [source]
Atlas charges for support based on the selected support tier. Pricing details are available through the UI on the support plan page. [source]

Parameters and configuration

Sum of all positive invoice line items contained in this invoice. This parameter expresses its value in cents (100ths of one US Dollar). [source] — Admin API invoice field
Returns one invoice that MongoDB issued to the specified organization. A unique 24-hexadecimal digit string identifies the invoice. You can choose to receive this invoice in JSON or CSV format. If you have a cross-organization setup, you can query for a linked invoice if you have the Organization Billing Admin or Organization Owner role. To compute the total owed amount of the invoice - sum up total owed amount of each payment included into the invoice. To compute payment's owed amount - use formula totalBilledCents * unitPrice + salesTax - startingBalanceCents. [source] — Admin API invoice field
Human-readable description of the service that this line item provided. This Stock Keeping Unit (SKU) could be the instance type, a support charge, advanced security, or another service. [source] — Admin API invoice field
Sum of sales tax applied to this invoice. This parameter expresses its value in cents (100ths of one US Dollar). [source] — Admin API invoice field
INVOICED: MongoDB issued an invoice that included this line item. [source] — Admin API invoice field
Sum of services that the specified organization consumed in the period covered in this invoice. This parameter expresses its value in cents (100ths of one US Dollar). [source] — Admin API invoice field
Sum that the specified organization paid toward this invoice. This parameter expresses its value in cents (100ths of one US Dollar). [source] — Admin API invoice field
Sum that MongoDB credited the specified organization toward this invoice. This parameter expresses its value in cents (100ths of one US Dollar). [source] — Admin API invoice field
Date and time when MongoDB Cloud finished the billing period that this invoice covers. This parameter expresses its value in the ISO 8601 timestamp format in UTC. [source] — Admin API invoice field
Sum that the specified organization paid toward the associated invoice. This parameter expresses its value in cents (100ths of one US Dollar). [source] — Admin API invoice field
Date and time when MongoDB Cloud began the billing period that this invoice covers. This parameter expresses its value in the ISO 8601 timestamp format in UTC. [source] — Admin API invoice field
Sum that the specified organization owed to MongoDB when MongoDB issued this invoice. This parameter expresses its value in US Dollars. [source] — Admin API invoice field
Unique 24-hexadecimal digit string that identifies the invoice submitted to the specified organization. Charges typically post the next day. [source] — Admin API invoice field
Sum by which MongoDB discounted this line item. MongoDB Cloud expresses this value in cents (100ths of one US Dollar). The resource returns this parameter when a discount applies. [source] — Admin API invoice field
Sum of the cost set for this line item. MongoDB Cloud expresses this value in cents (100ths of one US Dollar) and calculates this value as unitPriceDollars * quantity * 100. [source] — Admin API invoice field
Value per unit for this line item expressed in US Dollars. [source] — Admin API invoice field
List that contains the invoices for organizations linked to the paying organization. [source] — Admin API invoice field
FAILED_AUTHENTICATION: Strong Customer Authentication has failed. Confirm that your payment method is authenticated. [source] — Admin API invoice field
PARTIAL_PAID: Customer paid for part of this line item. [source] — Admin API invoice field
List that contains payments that MongoDB returned to the organization for this invoice. [source] — Admin API invoice field
PENDING: Invoice includes charges for the current billing cycle. [source] — Admin API invoice field
The unit price applied to amountBilledCents to compute total payment amount. This value is represented as a decimal string. [source] — Admin API invoice field
Date and time when MongoDB Cloud created this invoice. This parameter expresses its value in the ISO 8601 timestamp format in UTC. [source] — Admin API invoice field
List that contains individual services included in this invoice. [source] — Admin API invoice field
One service included in this invoice. [source] — Admin API invoice field
List that contains funds transferred to MongoDB to cover the specified service noted in this invoice. [source] — Admin API invoice field
Funds transferred to MongoDB to cover the specified service in this invoice. [source] — Admin API invoice field
Unique 24-hexadecimal digit string that identifies this payment toward the associated invoice. [source] — Admin API invoice field
One payment that MongoDB returned to the organization for this invoice. [source] — Admin API invoice field
Code identifying the cloud provider this line item's usage is attributed to. Values map as follows: AWS is Amazon Web Services, GCP is Google Cloud, AZURE is Microsoft Azure, and ATLAS is other Atlas usage not tied to a specific cloud provider. [source] — Admin API invoice field
Date and time when MongoDB Cloud created this line item. This parameter expresses its value in the ISO 8601 timestamp format in UTC. [source] — Admin API invoice field
Date and time when when MongoDB Cloud finished charging for this line item. This parameter expresses its value in the ISO 8601 timestamp format in UTC. [source] — Admin API invoice field
Unique 24-hexadecimal digit string that identifies the project associated to this line item. [source] — Admin API invoice field
Comment that applies to this line item. [source] — Admin API invoice field
Percentage by which MongoDB discounted this line item. The resource returns this parameter when a discount applies. [source] — Admin API invoice field
Number of units included for the line item. These can be expressions of storage (GB), time (hours), or other units. [source] — Admin API invoice field
Date and time when MongoDB Cloud began charging for this line item. This parameter expresses its value in the ISO 8601 timestamp format in UTC. [source] — Admin API invoice field
Human-readable label that identifies the Atlas App Services application associated with this line item. [source] — Admin API invoice field
A map of key-value pairs corresponding to the tags associated with the line item resource. [source] — Admin API invoice field
Element used to express what quantity this line item measures. This value can be elements of time, storage capacity, and the like. [source] — Admin API invoice field
Lower bound for usage amount range in current SKU tier. [source] — Admin API invoice field
Upper bound for usage amount range in current SKU tier. [source] — Admin API invoice field
FORGIVEN: Customer initiated payment which MongoDB later forgave. [source] — Admin API invoice field
Values are NEW, FORGIVEN, FAILED, PAID, PARTIAL_PAID, CANCELLED, INVOICED, FAILED_AUTHENTICATION, PROCESSING, PENDING_REVERSAL, or REFUNDED. [source] — Admin API invoice field
Sum of the funds returned to the specified organization expressed in cents (100th of US Dollar). [source] — Admin API invoice field
Values are PENDING, CLOSED, FORGIVEN, FAILED, PAID, FREE, PREPAID, or INVOICED. [source] — Admin API invoice field

How-to and procedures

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. [source]

Examples and snippets

{ "amountBilledCents": 42, "amountPaidCents": 42, "created": "2026-05-04T09:42:00Z", "creditsCents": 42, "endDate": "2026-05-04T09:42:00Z", "id": "<object-id>", "lineItems": [ { "cloudProvider": "AWS", "clusterName": "string", "created": "2026-05-04T09:42:00Z", "discountCents": 42, "endDate": "2026-05-04T09:42:00Z", "groupId": "<object-id>", "groupName": "string", "note": "string", "percentDiscount": 42.0, "quantity": 42.0, "sku": "string", "startDate": "2026-05-04T09:42:00Z", "stitchAppName": "string", "tags": { "additionalProperty1": [ "string" ], "additionalPropert [source]
```bash — `# Get line items for a specific invoice` … [source]
```bash — `curl -s -u "${PUBLIC_KEY}:${PRIVATE_KEY}" --digest \` … [source]
```bash — `PUBLIC_KEY="your-public-key"` … [source]
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId} [source]
curl --include --header "Authorization: Bearer ${ACCESS_TOKEN}" \ --header "Accept: application/vnd.atlas.2025-03-12+json" \ -X GET "https://cloud.mongodb.com/api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}?pretty=true" [source]
curl --user "${PUBLIC_KEY}:${PRIVATE_KEY}" \ --digest --include \ --header "Accept: application/vnd.atlas.2025-03-12+json" \ -X GET "https://cloud.mongodb.com/api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}?pretty=true" [source]
Invoice Number,<object-id>, Billing Period,"June 1, 2024 - July 1, 2024", Organization Name,Test 2, Organization ID,<object-id>, [source]
```text — `Compute: Charged per cluster tier (M10, M30, M50, etc.) per hour` … [source]
Date,Usage Date,Description,Note,Organization Name,Organization ID,Project,Project ID,SKU,Region,Cluster,Replica Set,Config Server,Application,Unit,Unit Price,Quantity,Discount Percent,Amount [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. [source]
Dedicated Atlas clusters (M10+) are provisioned with a minimum of 3 instances running as a replica set, which equates to 72 server hours per calendar day. Billing is based on those dedicated instances running as requested, not on the number of hours they are actually used. [source]

Problems, failure modes and limitations

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. [source]
Atlas bills Charts based on the data you transfer from the Charts web server to web browser clients, with the first 1 GB per month free, and additional data transfers beyond this limit at a fixed rate. [source]
How the charge for mongodb atlas is 72hrs per day? [source]

Related concepts

Usage Details — is a part of Atlas Billing and Invoice Anatomy
cents — is a measure of Atlas Billing and Invoice Anatomy
SKU — is a part of Atlas Billing and Invoice Anatomy
invoice list — is a part of Atlas Billing and Invoice Anatomy
CSV invoice export — is a instance of Atlas Billing and Invoice Anatomy
Admin API invoice — is a instance of Atlas Billing and Invoice Anatomy
billing day — is a related of Atlas Billing and Invoice Anatomy
Payment Details — is a part of Atlas Billing and Invoice Anatomy
Flex cluster cap — is a related of Atlas Billing and Invoice Anatomy
invoice status — is a part of Atlas Billing and Invoice Anatomy
Premium Features — is a part of Atlas Billing and Invoice Anatomy
Billed Usage — is a part of Atlas Billing and Invoice Anatomy
AI Model APIs — is a related of Atlas Billing and Invoice Anatomy
Summary By Project — is a part of Atlas Billing and Invoice Anatomy
server hours — is a measure of Atlas Billing and Invoice Anatomy
metering cadence — is a measure of Atlas Billing and Invoice Anatomy
support line — is a related of Atlas Billing and Invoice Anatomy
Organization Billing Viewer — is a part of Atlas Billing and Invoice Anatomy
billing profile — is a part of Atlas Billing and Invoice Anatomy
taxes — is a related of Atlas Billing and Invoice Anatomy

Children

Atlas Admin API invoice endpoints (frontier, viability 3.05 / 5, below research gate)
Billing incidents and refunds (frontier, viability 2.30 / 5, below research gate)

Frontier under this node: Atlas Admin API invoice endpoints (3.05), Billing incidents and refunds (2.30)

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