# Cross-Organization Billing and Linked Invoices > Cross-organization billing is an Atlas subscription feature, bought through MongoDB Sales, that lets one paying organization settle a single invoice covering many linked organizations, each of which still receives its own monthly invoice with its usage and a proportional share of the subscription cost. The pack draws on 4 contributing sources (almost entirely MongoDB docs, plus one DoiT page) and covers definitions, linking prerequisites and limits (including the 250-organization cap), proration examples, unlinking, and how Charts billing ingestion and the Admin API handle linked invoices. Parent: [Atlas Cost Commitments, Cross-Org Billing and FinOps Tooling](https://llms-explorer.com/tree/atlas-cost-commitments-cross-org-billing-and-finops-tooling/) · 8 facets · 52 facts · page: https://llms-explorer.com/tree/cross-organization-billing-and-linked-invoices/ ## Definitions - Cross-organization billing is an Atlas subscription feature that enables you to share a billing subscription across many organizations and to pay a single invoice for them. After configuring a paying organization, you pay invoices for the paying organization that include a list of charges incurred for all linked organizations. — [source](https://www.mongodb.com/docs/atlas/billing) - Cross-organization billing shares one billing subscription across many organizations; the paying organization's invoice lists charges incurred by all linked organizations. — [source](https://www.mongodb.com/docs/atlas/billing) - You can unlink organizations from your paying organization. — [source](https://www.mongodb.com/docs/atlas/billing) ## Structure and components - Linked organizations are bound by the paying organization's subscription agreement: support level, subscription charges, discounts and payment terms. — [source](https://www.mongodb.com/docs/atlas/billing) - Linked organizations are subject to the subscription agreement of the paying organization, including the level of support, the charges associated with the subscription, discounts, and payment terms. — [source](https://www.mongodb.com/docs/atlas/billing) - The paying and linked organizations' combined charges — [source](https://www.mongodb.com/docs/atlas/billing) ## How it works - Daily subscription uplift is billed to each organization on its own usage. At period end an unmet monthly minimum is split across linked and paying organizations by usage share (docs example: $199 unmet split $132.70/$66.30 for 2/3 and 1/3 of charges). — [source](https://www.mongodb.com/docs/atlas/billing) - Each linked organization gets its own monthly invoice with its usage plus a percentage of the total subscription cost proportional to its usage; payment still flows only through the paying organization. — [source](https://www.mongodb.com/docs/atlas/billing) - You pay for all linked organization usage through the paying organization. To help you account for usage, each linked organization has its own monthly invoice. — [source](https://www.mongodb.com/docs/atlas/billing) - A percentage of your total cross-organization billing subscription cost proportional to that organization's usage. — [source](https://www.mongodb.com/docs/atlas/billing) - At the end of a paying organization's billing period, Atlas bills linked and paying organizations proportionally to their usage for the unmet monthly minimum, if there is one. — [source](https://www.mongodb.com/docs/atlas/billing) - When you unlink an organization, the change takes effect upon processing your next invoice. If you change your mind and want to re-link an organization before your next invoice, you can cancel the unlinking request before that invoice is processed. — [source](https://www.mongodb.com/docs/atlas/billing) - The organization will be unlinked upon generating your next invoice. For the current invoice period, the organization will continue to incur charges on the paying organization. After that, the organization will be unlinked and receive a separate invoice. — [source](https://www.mongodb.com/docs/atlas/billing) - Each day, Atlas bills linked and paying organizations for subscription uplift based on their own usage. — [source](https://www.mongodb.com/docs/atlas/billing) ## Parameters and configuration - Linking prerequisites: paying org has an Atlas subscription; Organization Billing Admin or Organization Owner on both orgs; linked org has the same minimums, uplifts and SLA as the paying org or no support plan (Atlas Basic). — [source](https://www.mongodb.com/docs/atlas/billing) - A paying organization can link at most 250 organizations (UI or Admin API); more requires contacting support. A paying organization cannot itself be a linked organization. The subscription enabling the feature is bought through MongoDB Sales. — [source](https://www.mongodb.com/docs/atlas/billing) - Enabling linked invoices on an existing Charts ingestion limits the dashboard to the last three months of each linked org's data; a new ingestion gets twelve months. Invoice updates are picked up only for invoices within three months; ingestion runs daily. — [source](https://www.mongodb.com/docs/charts/dashboards/manage-dashboards/billing-dashboards/) - To link an organization to a paying organization, you must have Organization Billing Admin or Organization Owner privileges for both organizations. — [source](https://www.mongodb.com/docs/atlas/billing) - If you enable linked invoices on an existing ingestion, the billing dashboard uses the last three months of each linked organization's billing data. If you enable linked invoices on a new ingestion, it uses the last twelve months of data. — [source](https://www.mongodb.com/docs/charts/dashboards/manage-dashboards/billing-dashboards/) - You can link a paying organization to a maximum of 250 other organizations, either manually through the Atlas UI or programatically via the Atlas Admin API. To link more than 250 organizations, contact support. — [source](https://www.mongodb.com/docs/atlas/billing) - For an organization to be linked to a paying organization, it must have the same minimums, uplifts, and SLA for their subscription plan as the paying organization or have no support plan (Atlas Basic). — [source](https://www.mongodb.com/docs/atlas/billing) - You can unlink or cancel unlinking from the Atlas Admin UI. You must have permissions to make changes to your linked organization's billing settings. To unlink a linked organization, follow these steps: — [source](https://www.mongodb.com/docs/atlas/billing) - List that contains the invoices for organizations linked to the paying organization. — [source](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2025-02-19/operation/operation-getorginvoice) *(Admin API invoice field linkedInvoices)* - 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. — [source](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2025-02-19/operation/operation-getorginvoice) - A paying organization must have an Atlas subscription. — [source](https://www.mongodb.com/docs/atlas/billing) - An organization without a subscription can join a paying organization with a subscription of any type. — [source](https://www.mongodb.com/docs/atlas/billing) ## How-to and procedures - Charts billing ingestion: for cross-org billing, enter the paying organization's ID and toggle ingestion of linked invoices. The API key pair needs Organization Billing Admin and Billing Viewer roles. — [source](https://www.mongodb.com/docs/charts/dashboards/manage-dashboards/billing-dashboards/) - To unlink all organizations from a paying organization and link them to another cross-organization configuration, contact support. — [source](https://www.mongodb.com/docs/atlas/billing) - Documented use case: keep separate organizations per team for authorization isolation while paying through one organization; a 250+ project company can create new organizations and link them to avoid project limits and keep one invoice source. — [source](https://www.mongodb.com/docs/atlas/billing) - If you want to cancel the unlinking request, navigate to the Linked Organizations tab. Click Cancel Unlinking next to the organization you want to cancel the unlinking process for. If you applied an activation code, you can apply that code to your paying organization or remove it to use elsewhere. — [source](https://www.mongodb.com/docs/atlas/billing) - A company with over 250 projects might create new organizations for new projects, then link all organizations to a paying organization to maintain a single source of invoicing. — [source](https://www.mongodb.com/docs/atlas/billing) - If you use cross-organization billing, specify the Organization ID for the paying organization. — [source](https://www.mongodb.com/docs/charts/dashboards/manage-dashboards/billing-dashboards/) - Enable or disable ingesting invoices from linked organizations. — [source](https://www.mongodb.com/docs/charts/dashboards/manage-dashboards/billing-dashboards/) - To purchase a subscription that enables cross-organization billing, contact MongoDB Sales. — [source](https://www.mongodb.com/docs/atlas/billing) - If you are configuring a new paying organization, click Start Linking. — [source](https://www.mongodb.com/docs/atlas/billing) - If your organization is already a paying organization, click Link More Organizations. — [source](https://www.mongodb.com/docs/atlas/billing) - The Linked Organizations tab displays your linked organizations. To link additional organizations, click Link More Organizations. — [source](https://www.mongodb.com/docs/atlas/billing) - To display linked organizations and their contributions to the Pending Invoice, view the payment details section of your organization's invoice. — [source](https://www.mongodb.com/docs/atlas/billing) - You can rename an organization to reach your desired cross-organization configuration. — [source](https://www.mongodb.com/docs/atlas/billing) - Click Unlink next to the organization you want to unlink. — [source](https://www.mongodb.com/docs/atlas/billing) ## Examples and snippets - Linked organization #1 incurs $400 in subscription uplift charges while linked organization #2 incurs $200 in subscription uplift charges. The paying organization has a monthly minimum of $799, so at the end of the month, the unmet $199 is proportionally distributed across invoices for linked organizations #1 and #2: — [source](https://www.mongodb.com/docs/atlas/billing) *(docs worked example)* - A paying organization has an Atlas Pro subscription and two linked organizations. The paying organization incurs no charges. — [source](https://www.mongodb.com/docs/atlas/billing) *(docs worked example)* - Atlas charges linked organization #1 $132.70 of the unmet $199 because it incurred 2/3 of the total charges. — [source](https://www.mongodb.com/docs/atlas/billing) *(docs worked example)* - Atlas charges linked organization #2 $66.30 of the unmet $199 because it incurred 1/3 of the total charges. — [source](https://www.mongodb.com/docs/atlas/billing) *(docs worked example)* - You still pay all charges through the paying organization. — [source](https://www.mongodb.com/docs/atlas/billing) *(docs worked example)* ## Problems, failure modes and limitations - Paying and linked organizations cannot have failed payments, an active self-serve support plan, an active self-serve marketplace subscription, or overlapping monthly commitment subscriptions. — [source](https://www.mongodb.com/docs/atlas/billing) - Querying a linked invoice through the Admin API requires Organization Billing Admin or Organization Owner, while the same endpoint's role table lists only Organization Billing Viewer, so the page is internally inconsistent about the role needed. — [source](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2025-02-19/operation/operation-getorginvoice) *(Admin API page inconsistent on required role)* - A paying organization can't already be a linked organization. — [source](https://www.mongodb.com/docs/atlas/billing) - At the end of the paying organization's billing period, simultaneous charges for daily subscription uplift and an unmet minimum could trigger daily maximum billing alerts. — [source](https://www.mongodb.com/docs/atlas/billing) - An organization with an existing subscription that includes support can only join a paying organization with the same level of support. — [source](https://www.mongodb.com/docs/atlas/billing) ## Facts and statements - 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](https://www.doit.com/platform/mongodb-intelligence/) *(third-party FinOps tool)* - If your organization uses cross-organizational billing, you can view billing data across all linked organizations. — [source](https://www.mongodb.com/docs/atlas/billing) ## Related concepts - paying organization — is a part of Cross-Organization Billing and Linked Invoices - linked organization — is a part of Cross-Organization Billing and Linked Invoices - linked invoice — is a hyponym of Cross-Organization Billing and Linked Invoices - unmet monthly minimum — is a measure of Cross-Organization Billing and Linked Invoices - unlink organization — is a part of Cross-Organization Billing and Linked Invoices - linking prerequisites — is a problem of Cross-Organization Billing and Linked Invoices - Organization Billing Admin — is a prerequisite of Cross-Organization Billing and Linked Invoices - subscription uplift — is a measure of Cross-Organization Billing and Linked Invoices - MongoDB Sales — is a related of Cross-Organization Billing and Linked Invoices - 250-organization limit — is a measure of Cross-Organization Billing and Linked Invoices - single invoice — is a synonym of Cross-Organization Billing and Linked Invoices - subscription agreement — is a part of Cross-Organization Billing and Linked Invoices - Charts billing ingestion — is a instance of Cross-Organization Billing and Linked Invoices - linking flow — is a part of Cross-Organization Billing and Linked Invoices - Pending Invoice — is a part of Cross-Organization Billing and Linked Invoices - unlinking takes effect — is a part of Cross-Organization Billing and Linked Invoices - authorization isolation — is a dependent of Cross-Organization Billing and Linked Invoices - DoiT MongoDB Intelligence — is a instance of Cross-Organization Billing and Linked Invoices - cross-organizational billing view — is a synonym of Cross-Organization Billing and Linked Invoices