FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)

Parent: Atlas Cost Commitments, Cross-Org Billing and FinOps Tooling · Published reference · snapshot 2026-10-19 · skill mongodb-operations-expert/references/atlas-cost-commitments-cross-org-billing-and-finops-tooling.md

↓ Facts as markdown all context files

Atlas exposes billing to FinOps tooling as a FOCUS 1.3 cost and usage report (console CSV, or the asynchronous FOCUS Data API, GA 2026-08-19) and through the older Invoices API that Vantage uses, while native Atlas billing alerts supply USD budget thresholds and percentage-increase anomaly-style detection. The pack draws on 10 source URLs (MongoDB docs and GA note, DoiT, Vantage, the FOCUS v1.4 specification and a feedback-portal thread) and covers FOCUS columns and report lifecycle, alert conditions, vendor integrations and the spec's statement that anomaly detection is only a future FOCUS capability.

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

Atlas provides billing cost and usage data in FOCUS 1.3 format. Users get it from the Invoices page (choose 'CSV FOCUS Cost & Usage Report') or from the FOCUS Data API; MongoDB announced GA on 2026-08-19. [source]
FOCUS is a standards development organization (SDO) formed to establish an open, consensus-driven standard for billing data. In the absence of a broadly adopted standard, infrastructure and service providers have relied on proprietary billing schemas and inconsistent terminology, making cost data difficult to normalize and act upon across environments. This lack of conformance has forced FinOps practitioners to develop best-effort custom normalization schemes for each provider, in order to perform essential FinOps capabilities such as chargeback, cost allocation, budgeting and forecasting. [source] — FOCUS spec
The FOCUS Data API provides programmatic access to your FOCUS-formatted cost and usage data. [source]
The FinOps Open Cost and Usage Specification (FOCUS) establishes uniform requirements for technology billing datasets. MongoDB Atlas provides billing cost and usage data in the FOCUS 1.3 format. You can generate a FOCUS report from the Invoices page in the Atlas console or with the FOCUS Data API. [source]
Gain full FinOps visibility into MongoDB Atlas costs across organizations, projects, and SKUs with built-in analytics and AI-powered optimization insights. [source] — DoiT
The following alert conditions apply to Atlas billing. You can configure billing alerts from the Atlas UI at the organization level or the project level. [source]
You can use billing alerts to help manage your billing quotas. Billing alerts notify a designated person when a bill has exceeded a USD limit, or when a credit card is about to expire. [source]

Structure and components

The ContractApplied field identifies which Atlas credit covered usage (Prepaid, Promotional or Elastic); InvoiceIssuer distinguishes direct MongoDB billing from marketplace billing; Tags carries resource tags. These give commitment and allocation analysis without custom SKU mapping. [source]
The FOCUS Data API adds three endpoints to the Atlas Administration API. The first, List Invoices for an Organization (GET /api/atlas/v2/orgs/{orgId}/associatedInvoices), takes month and year filters and can include linked organizations for cross-org billing. All endpoints need Organization Billing Admin, Organization Owner or Organization Billing Viewer. [source]
Request a FOCUS Report requests generation of a FOCUS-formatted billing report. [source]
Work with standard industry terms: Use SubAccountName and other intuitive FOCUS terms instead of internal API terms such as groupName. [source]
Retrieve a FOCUS Report returns the status of that report and, when the report is ready, the URL to download it. [source]
View costs in billing currency: Access BilledCost and EffectiveCost directly in billing currency, without manual conversion. [source]
Identify credit types: See whether a credit is Prepaid, Promotional, or Elastic through the Contract Applied field. [source]
A set of properties that associate a charge with one or more contract commitments. Identifies the name of the Atlas Credit used to cover the consumed usage. [source]
Represents the amortized cost of a charge after applying all reduced rates and discounts. This field is denominated in pricing currency. [source]
The "price" of an Atlas Credit. Apply this rate to find the cost of an Atlas Credit in billing currency. [source]
List Invoices for an Organization lists the available invoices for an organization. [source]

How it works

FOCUS removes the manual conversion of Atlas Credit Units into billing currency: BilledCost and EffectiveCost are returned in billing currency, and PricingCurrency/x_PricingCurrencyRate expose the Atlas Credit rate. [source]
Atlas has native billing alerts in USD: the last daily amount billed (excluding credits applied) per org or project, and monthly totals per organization or per project that reset when the pending invoice closes. These work as budget thresholds. [source]
Atlas also has native percentage-increase spend alerts: org daily vs previous day, org weekly vs previous 7 days, org monthly vs previous 30 days, and project daily and weekly. This is a simple built-in anomaly-style detector. [source]
FOCUS data is invoice-scoped: it is retrieved per invoice (current or past billing period), so an ingestion pipeline polls invoices by month rather than streaming real-time spend. [source]
On the right, you’ll find an Agentic FinOps AI assistant. Ava isn’t just a chatbot; it’s a reasoning layer that interprets the same data visible on the dashboard. Ask questions like “Which projects or SKUs changed the most this month?” or “Where am I overspending on backups?”, and Ava will analyze cost trends, isolate anomalies, and suggest next best actions. [source] — DoiT
You can query data for the "Pending" (current) month. While Atlas associates usage with credits in real-time to offer cost estimates, these values are not final until the invoice closes. Re-pull data after the month closes to confirm final billing values. [source] — answers pending-invoice freshness
Asynchronous generation: Report generation doesn't block your request. The request endpoint returns a reportId immediately, and you poll the retrieve endpoint for the report state. [source]
Single-organization scope: Each request returns data for one organization. If you use cross-org billing, request one report for each invoiceId returned by the list endpoint. [source]
Raised if the organization or project's last daily amount billed exceeds your configured threshold. Atlas does not account for any credits applied for the previous day when calculating the billed amount. [source]
Raised if the monthly total for any project within the organization exceeds your configured threshold for all projects. When the current pending invoice closes, this alert resets. [source]
Raised if the monthly total for the organization exceeds your configured threshold. When the current pending invoice closes, this alert resets. [source]
Raised if the organization's daily gross spend has increased by more than your configured threshold percentage compared to the previous day. [source]
Raised if the organization's weekly gross spend has increased by more than your configured threshold percentage compared to the previous 7 days. [source]
Raised if the organization's monthly gross spend has increased by more than your configured threshold percentage compared to the previous 30 days. [source]
Raised if the project's daily billing has increased by more than your configured threshold percentage. [source]
Raised if the project's weekly billing has increased by more than your configured threshold percentage. [source]
Raised if the project's monthly billing has increased by more than your configured threshold percentage. [source]

Parameters and configuration

Atlas sends billing alerts to Organization Owners and Billing Admins by default; a billing email address can be added or used exclusively. [source]
If you have negotiated pricing with MongoDB, set a unit price multiplier to adjust the MongoDB Atlas costs shown in Vantage. Vantage multiplies MongoDB Atlas costs by the rate you enter. The default rate is 1.0 (no adjustment). For example, a rate of 0.8 reflects a 20% discount. [source] — Vantage
By default, Atlas sends billing alerts to the Organization Owners and Billing Admins. [source]
If you specify a billing email address and uncheck Only send invoice emails to the Billing Email Address, Atlas sends billing alerts to the billing email address, Organization Owners, and Billing Admins. [source]
The report is ready. The response includes downloadUrl and expiresAt. [source]
Atlas couldn't generate the report. The response includes failureReason. [source]
Date and time at which downloadUrl expires, in ISO 8601 format in UTC. Each download URL is valid for 15 minutes. The response includes this parameter only when state is SUCCEEDED. [source]
Each downloadUrl is valid for 15 minutes. To download a report after its URL expires, call this endpoint again with the same reportId. Atlas returns a new downloadUrl and a new expiresAt time. [source]
Time-limited download URL: When a report succeeds, the retrieve endpoint returns a downloadUrl that is valid for 15 minutes. Reports remain available for seven days. To learn how to refresh an expired URL, see Report Availability. [source]
All amounts billed are in USD. [source]
If you specify a billing email address and check the box for Only send invoice emails to the Billing Email Address, Atlas send billing alerts to the billing email address only. [source]

How-to and procedures

You can download the FOCUS cost and usage report for an invoice from the Invoices page in the Atlas console. Select CSV FOCUS Cost & Usage Report when you choose the invoice format. [source]
To consume your billing data programmatically in an industry-standard format, see Access the FOCUS Cost and Usage Report. [source]
Download the invoice as a PDF or CSV usage summary, or as a CSV FOCUS cost and usage report. [source]
Grant the Vantage Integration API key Project Read Only access. Then, click Invite to Project. Repeat this process for any other projects where you want to see resource-level costs. [source] — Vantage
To create an API key for Vantage to ingest costs, you must be an Organization Owner inside the MongoDB Atlas console. [source] — Vantage
How to get started: Retrieve FOCUS‑formatted billing data directly through the Atlas Admin API or download it from the Atlas billing UI. See the Atlas documentation for more information. [source] — GA announcement
Setting up MongoDB Intelligence takes only a few minutes — connect your Atlas organization, and Cloud Intelligence™ will automatically ingest cost and usage data. Follow the step-by-step guide in our Help Center article to enable the integration securely and start visualizing your MongoDB Atlas spend with zero manual exports. [source] — DoiT
To download the report, pass the returned reportId to the retrieve endpoint. [source]
Poll no more than once every five seconds. If a report takes longer to generate, increase the interval between requests exponentially. Most reports complete within seconds, but reports for large invoices can take a few minutes. [source]
You can configure it by navigating to your project’s Alerts setting (not Organizational Alerts), selecting Billing as the category, and choosing “Monthly pending invoice ($) total is…” as the condition/metric. This lets you set a threshold for the accumulated billed amount in the current calendar month. [source] — MongoDB admin reply, Jan 2026

Examples and snippets

GET /api/atlas/v2/orgs/{orgId}/associatedInvoices [source] — list endpoint
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/reports/{reportId} [source] — retrieve endpoint
Identify anomalous daily spending by subaccount [source] — FOCUS spec use case
Compare billed cost per subaccount to budget [source] — FOCUS spec use case

Problems, failure modes and limitations

FOCUS SaaS support is described by the spec as 'foundational' (columns for pricing currency, effective cost and contracted pricing in non-monetary units such as credits), so cross-vendor comparisons of Atlas data may still need vendor-specific handling. [source] — FOCUS spec
FOCUS v1.4 lists anomaly detection, forecasting and exchange-rate modeling only as capabilities future versions 'will consider'. FOCUS standardises the data shape, so anomaly detection and budgets stay tool-specific. [source] — FOCUS spec v1.4
Credits are not displayed for MongoDB Atlas costs in Vantage. The MongoDB Atlas provider API does not make credit information available for retrieval. [source] — Vantage
Future versions of FOCUS will consider including additional FinOps capabilities such as forecasting, exchange rate modeling, and anomaly detection, while continuing to support a broader range of billing and cost datasets — including internal infrastructure platforms and marketplace offerings. [source] — FOCUS spec v1.4
Daily alerts are useful for detecting sudden spikes, but they do not reflect how budgets are actually managed, which is usually on a monthly basis. [source] — feedback request, Dec 2025
Shortfall charges (Monthly/Flex commitment differences). [source]
MongoDB Atlas currently provides billing alerts based on daily usage (Daily amount billed ($) is above), but there is no equivalent alert based on monthly accumulated spend at the project level. [source] — feedback request, Dec 2025

Facts and statements

Vantage ingests Atlas costs through the Invoices API, not FOCUS, using an org API key with Organization Billing Viewer and Organization Read Only. Atlas credits do not appear in Vantage because the provider API does not expose credit information; per-cluster Active Resources need Project Read Only on each project. [source]
DoiT Cloud Intelligence added a MongoDB Intelligence module (announced 2025-11-07) that pulls Atlas cost and usage data automatically from a connected organization. Its changelog describes anomaly investigation through the Ava assistant, not a dedicated Atlas anomaly feature, and does not mention budgets. [source]
The PDF and CSV usage summaries present your invoice in MongoDB-specific formats. The FOCUS cost and usage report presents the same billing period in the standardized FOCUS format. You can download all three from the Invoices page in the Atlas console. [source]
Vantage integrates with your MongoDB account using the Invoices API. To see Active Resources for your MongoDB Atlas account, Vantage uses the Clusters API and the Projects API. [source] — Vantage
Third-party FinOps tooling such as DoiT connects each Atlas organization separately (one service account per org) and maps organization.id to a billing-account dimension; the page does not describe paying/linked org handling. [source]
Historically, Atlas billing data has been provided in MongoDB-specific formats. Atlas customers, particularly large enterprises and partners, need to expend manual effort to convert Atlas Credit Units (ACUs) into billing currency. [source]
Why it matters: This launch aligns Atlas billing data with a widely adopted cloud reporting standard, simplifying integration into unified FinOps reporting pipelines and eliminating the need for custom SKU mapping. It also introduces additional billing attributes for greater insight and transparency, enabling faster, clearer, and more consistent cross‑vendor spend monitoring and cost analysis. [source] — GA announcement
Hi, MongoDB Atlas already supports monthly billing alerts at the project level. Please see attached screenshot for details. [source] — MongoDB admin reply, Jan 2026

Related concepts

FOCUS — is a related of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
FOCUS report lifecycle — is a part of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
anomaly detection — is a synonym of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
budget — is a synonym of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
billing alerts — is a hyponym of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
FOCUS ingestion — is a synonym of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
FOCUS columns — is a part of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
FinOps Open Cost and Usage Specification — is a hyponym of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
FOCUS Cost and Usage Report — is a hyponym of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
spend change alert — is a hyponym of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
billing API roles — is a prerequisite of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
FOCUS Data API — is a hyponym of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
Vantage — is a instance of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
Vantage integration — is a instance of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
DoiT Cloud Intelligence — is a instance of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
Invoices API — is a part of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
forecasting — is a related of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
cost allocation — is a dependent of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)
Atlas GA announcement — is a measure of FinOps Tooling for Atlas (FOCUS Ingestion Anomaly Detection Budgets)

Children

Atlas Admin API billing alert configuration (frontier, viability 2.60 / 5, below research gate)
FOCUS column mapping for Atlas credits (frontier, viability 2.60 / 5, below research gate)
Cross-vendor FOCUS pipelines (BigQuery/Snowflake) (frontier, viability 2.60 / 5, below research gate)

Frontier under this node: Atlas Admin API billing alert configuration (2.60), Cross-vendor FOCUS pipelines (BigQuery/Snowflake) (2.60), FOCUS column mapping for Atlas credits (2.60)

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