OpenAI API Billing: Budgets, Invoices, Usage and Payment

OpenAI API Billing vs ChatGPT Billing

OpenAI maintains separate billing systems for the API Platform and for ChatGPT products. API billing — including credits, invoices, project budgets and usage — is managed through the API Platform interface. ChatGPT subscription billing is managed separately. Make sure you are in the correct interface before reviewing or modifying billing settings.

This page covers API Platform billing administration. For credits expiry and prepaid billing, see the OpenAI API Credits guide.

Organization Billing and Permissions

OpenAI API billing is organized at the organization level. Organization Owners have full access to billing settings, payment methods, usage limits and member management.

Organization Owners can:

• Add, update or remove payment methods
• View and export billing history and invoices
• Set and adjust project budgets
• Manage organization usage limits and billing arrangements
• Invite and assign roles to members

Reader-level members and general project members may not have access to billing settings. If billing data is not visible, verify the organization, project, role and active filters in the current session before assuming there is a problem.

Prepaid vs Monthly Billing Arrangements

OpenAI's current prepaid-billing documentation describes the following arrangements:

• Prepaid billing — new accounts currently start on prepaid billing; credits are purchased upfront and usage is deducted from the balance; purchased credits expire after one year
• Monthly billing — some existing accounts may remain on a monthly billing arrangement and can also purchase prepaid credits. Check the organization Billing page for the account's current billing setup.
• Enterprise billing — governed by a separate contract with negotiated payment terms; invoices are issued separately from self-serve accounts

The billing arrangement determines whether an account uses prepaid credits or monthly invoicing. Check the current billing arrangement in the organization Billing page.

Project Budgets Are Soft Thresholds

OpenAI's current API Platform documentation describes project budgets as soft spending thresholds used for monitoring and alerting. API requests continue after the monthly project budget is exceeded; the budget is not a hard spending cap that blocks requests automatically.

Key points about project budgets:

• Project budgets are monitored per calendar month in UTC
• Alerts can be set at configurable thresholds (e.g., 50%, 75%, 100%)
• Budget alerts notify the configured recipients but do not stop API requests
• Requests that continue after a budget alert generate charges against the account balance
• Project budgets do not replace application-level spending controls

To prevent runaway spend, implement application-side controls: hard request limits per key, key rotation procedures, queue-based throttling, and real-time cost monitoring. Use the AI API Cost Benchmark to turn usage assumptions into an estimated monthly budget.

Organization Limits vs Project Budgets

OpenAI accounts have several independent limits that are distinct from project budgets:

• Organization limits and prepaid-credit ceilings — API rate limits and the maximum prepaid balance are separate from project budgets. Check the current organization Limits and Billing pages rather than assuming one limit controls the others.
• Rate limits — RPM (requests per minute) and TPM (tokens per minute) enforced at the API layer; unrelated to spending
• Project monthly budget — soft monitoring threshold per project; alerts but does not block
• Prepaid credit balance — available credits for self-serve accounts; usage stops with an insufficient_quota error when exhausted
• Application-side spending boundary — developer-defined hard cap implemented in the calling code; the only guaranteed way to stop at a set budget

Do not treat these as interchangeable. Each limit controls a different dimension of usage.

Where to Manage Payment Methods

OpenAI's billing settings documentation describes the following for payment method management:

• Payment methods are managed in the API Platform billing settings
• An account must pass necessary verification before a payment method can be added or changed
• An outstanding balance, past-due invoice or recent payment failure may prevent removal of the current payment method
• Do not attempt to remove a payment method as a way to avoid an outstanding balance
• The current active payment method is used for auto recharge, manual purchases or postpaid billing as applicable

Billing History, Receipts and Invoices

OpenAI's API Platform billing settings provide access to billing history and receipts. The available documents depend on the account type:

• Prepaid accounts — purchase receipts are available for each credit purchase; invoices are not issued per request or per month
• Monthly postpaid accounts — monthly billing summaries are available; document types may vary by billing arrangement
• Enterprise accounts — formal invoices are issued according to the contract terms and payment schedule

The invoice total for a given period may not match a granular usage export because invoice line items are grouped and may include adjustments, credits or contract-specific pricing.

Who Receives API Invoices

OpenAI's current documentation indicates that API invoices are issued for Enterprise accounts under their contract terms. Self-serve accounts on prepaid or monthly billing do not receive per-month invoices in the same format as Enterprise customers.

Do not assume that every API account receives monthly invoices. For detailed usage records, use the Usage Dashboard export instead.

When Enterprise API Invoices Are Issued

For Enterprise accounts, OpenAI's current documentation indicates:

• Invoices are issued according to the billing terms in the Enterprise order form
• Billing periods typically follow the calendar month
• OpenAI says Enterprise API invoices are typically issued within two weeks after the billing cycle ends.
• Payment terms (e.g., net-30) are specified in the Enterprise agreement

For detailed monthly cost data, including line-item breakdowns, the Usage Dashboard export serves as the granular record. OpenAI's documentation notes that for Enterprise invoices issued from April 1, 2026 onward, detailed API cost breakdowns have moved to the Usage Dashboard export process.

Exporting Monthly Usage and Cost Data

OpenAI's Usage Dashboard export documentation describes two export types:

• Cost export — provides aggregated spend data grouped by line item; available for full-month or month-to-date ranges; useful for spend reconciliation against invoice totals
• Activity export — provides granular usage data that can be filtered by project, user, API key, model, batch or service tier; useful for investigating usage patterns and debugging cost anomalies

The Usage Dashboard export is not a per-request-ID billing system. It provides aggregated usage and spend data. Application-level request logs are needed for individual request-level reconciliation.

To export:

• Navigate to the Usage Dashboard in the API Platform
• Select the target organization and project
• Choose the calendar-month or custom UTC date range
• Select Cost or Activity export format
• Download the CSV and note the export timestamp

Invoice Total vs Detailed Cost Export

If an invoice total does not reconcile with a Cost export, first confirm that both records use the same organization, UTC calendar-month period, project scope and export settings. Use Cost data grouped by line item for monthly spend reconciliation. For Enterprise invoices issued from April 1, 2026 onward, detailed API cost breakdowns are provided through the Usage Dashboard export rather than the invoice itself.

Use the Cost export as the granular record and the invoice as the formal billing document. Compare the two by matching the billing period and noting any differences attributable to pricing, credits or adjustments.

Updating Billing Information, Tax ID and VAT ID

OpenAI's billing information documentation describes how to update billing details:

• Billing information, Tax ID and VAT ID can be updated in the API Platform billing settings
• Updates typically apply to future invoices only; past invoices are not automatically revised
• To request correction of a past invoice, contact OpenAI support with the invoice number and evidence
• An invalid or unverifiable Tax ID may be removed, and applicable taxes may be applied
• Always verify the current required fields in the billing settings before submitting

Payment Failure and Past-Due Checks

If a payment fails or an account becomes past due:

• OpenAI may restrict API access until the outstanding balance is resolved
• Auto recharge may be paused for failed payments; verify the payment method and retry
• An outstanding balance may block the ability to remove or replace the current payment method
• Contact OpenAI support with the organization ID and evidence to dispute or resolve a billing discrepancy
• Never send API keys, full card numbers or CVV in a support ticket

Billing Reconciliation Checklist

• ✓Confirm you are in the API Platform billing interface, not ChatGPT billing
• ✓Confirm the correct organization is selected
• ✓Confirm the correct project and clear any active project filters
• ✓Define the calendar-month or custom UTC range for the reconciliation period
• ✓Export Cost data for spend reconciliation against the invoice total
• ✓Export Activity data for usage investigation and anomaly detection
• ✓Compare prepaid credit deductions with any additional billed usage
• ✓Distinguish project budget alerts from actual charges — budget alerts do not block requests
• ✓Check payment method status and verify no past-due balances
• ✓Compare invoice totals with the matching monthly Cost export
• ✓Save pricing documents and export timestamps for record keeping
• ✓Escalate discrepancies with organization ID and evidence; never send API keys

Support Escalation Package

Before opening a support ticket for billing issues, prepare the following:

• Organization ID
• Project ID, if applicable
• Billing month and UTC date range
• Invoice number, if available
• Cost export CSV for the disputed period
• Activity export CSV for usage investigation
• Payment transaction date and last four digits of the payment method only if strictly necessary
• Exact disputed amount
• Screenshots with secrets, full card numbers and authorization headers removed

Never include in a support request:

• Full API key
• Authorization header
• Full card number or CVV
• Unredacted billing records or customer data

Official Sources Reviewed

The information on this page is based on OpenAI's official documentation reviewed as of June 25, 2026. OpenAI's billing setup may change; always verify current terms in the API Platform billing settings.

• OpenAI Help: Managing billing settings on ChatGPT Web and Platform
• OpenAI Help: Managing your work in the API Platform with projects
• OpenAI Help: When can I expect to receive my OpenAI API invoice
• OpenAI Help: How do I export monthly usage details from the API Usage Dashboard
• OpenAI Help: Updating billing information, Tax ID and VAT ID
• OpenAI Help: How can I change the billing details on my invoice
• OpenAI Help: How can I delete or remove my payment method
• OpenAI Help: How do I add, change or remove members on my OpenAI API account
• OpenAI Help: How can I set up prepaid billing

Related Guides

Frequently Asked Questions