How to Download OpenAI API Invoices: Token & VAT Guide (2026)

Last updated: April 2026 · ~7 min read

OpenAI API invoices look different from typical SaaS bills. Charges are usage-based, billed by token consumption per model, drawn from a prepaid credit balance or auto-recharge transaction, and issued by one of two separate billing entities depending on where your business is registered. Knowing how each piece works is the difference between a clean monthly reconciliation and a finance team chasing mystery charges across bank statements.

This guide covers OpenAI API billing - the developer and programmatic product accessed via platform.openai.com. It does not cover ChatGPT Plus, Team, or Enterprise subscriptions, which use a separate Stripe-based billing portal (see How to Download ChatGPT Plus Invoices). It also does not cover ChatGPT mobile app subscriptions purchased through Apple App Store or Google Play, which generate invoices in the platform of purchase.

---

TL;DR - Get any OpenAI API invoice in 4 steps

To download an OpenAI API invoice, the path is:

1. Sign in to platform.openai.com (the developer console - not chat.openai.com)

2. Open Settings → Organization → Billing

3. Click the Billing history tab

4. Click any invoice row → Download PDF

OpenAI generates invoices 24–48 hours after a billing cycle closes, or immediately when you purchase prepaid credits. The platform has no bulk download, no auto-email of PDFs, and no native multi-account aggregation - all three are operationally significant gaps.

The Tailride Chrome extension closes those gaps by extracting every OpenAI API invoice into structured PDF + CSV in a single run, and works alongside 30+ other vendor portals for finance teams running multi-vendor AI stacks. For accounting firms reconciling AI spend across multiple clients, Tailride for accounting firms handles the multi-client dimension on top.

---

Quick navigation: which path fits your situation

---

Where OpenAI API invoices actually live

OpenAI splits its product surface across two domains: chat.openai.com for the consumer ChatGPT product (Plus, Team, Enterprise plans) and platform.openai.com for the developer API. Billing is separate per domain, with separate portals, separate invoices, and separate billing entities. If you've landed in chat.openai.com → Settings → Subscription, you're looking at consumer subscription billing, which is a different document type covered in our ChatGPT Plus invoice guide.

For the API, the canonical billing path is:

• platform.openai.com/account/billing (older URL, still functional)

• platform.openai.com/settings/organization/billing (current preferred URL)

Both lead to the same Billing dashboard where four sections matter: Overview (current usage and balance), Payment methods (your card or invoice billing arrangement), Billing history (the invoice repository - what you came for), and Pricing (rate cards per model).

Permissions matter. OpenAI API organizations have role-based access: Owner, Admin, Reader. Only Owner and Admin can view Billing history and download invoices. If your role is Reader (a common default for engineering team members), you'll find the Billing menu item missing or the invoices unclickable. Request elevation from the org Owner if you need invoice access for finance work.

---

How to download a single OpenAI API invoice

For a one-off invoice retrieval:

1. Sign in to platform.openai.com with the account that owns or admins the OpenAI organization

2. Click your profile icon, then Settings → Organization → Billing

3. Click the Billing history tab

4. Locate the invoice row for the cycle you need; the row shows invoice number, billing period, and total amount

5. Click the row to open the detailed view - usage breakdown by model, prepaid credit consumption, total charged

6. Click Download PDF (sometimes labeled Download invoice) at the top right of the detail view

The downloaded file uses OpenAI's standard naming convention. For finance team workflows, rename immediately to a consistent format (OpenAI-API-Invoice-YYYY-MM.pdf) before filing - the default name embeds an invoice ID rather than a date, which makes folder navigation harder later.

Invoice generation timing:

• Cycle invoices (monthly billing): generated 24–48 hours after the billing cycle closes

• Prepaid credit purchases: generated immediately when the credit purchase transaction completes

• Auto-recharge events: generated immediately when the auto-recharge triggers

If an invoice you expect isn't visible 48 hours after the cycle closes, the most common explanation is that no chargeable activity occurred during that period - OpenAI doesn't generate zero-amount invoices.

---

Anatomy of an OpenAI API invoice

The OpenAI API invoice contains more granularity than typical SaaS bills. Understanding each section is what makes proper reconciliation possible.

Top section - billing entity. The invoice header shows which OpenAI legal entity issued the invoice - OpenAI LLC (Delaware-registered, US billing) or OpenAI Ireland Limited (Ireland-registered, EU billing). The entity address, registration number, and tax/VAT ID appear here. Below that, your business details: account holder name, organization name, and your VAT/tax ID if you've added one to the billing settings.

Line items section - usage by model. This is where OpenAI gets specific:

• Per-model charges break out by SKU: gpt-4-turbo, gpt-4o, gpt-3.5-turbo, text-embedding-3-large, dall-e-3, whisper-1, and others depending on what your application uses

• For chat and completion models, each line splits input tokens (what your application sends in prompts) from output tokens (what the model returns) - these are priced separately, often with output tokens 2–3× the input rate

• Fine-tuning charges appear as separate line items: training compute and inference on the fine-tuned model

• Container billing for hosted code execution (if used) shows as its own line - usually billed per second of compute

• Image generation (DALL-E) and audio API (Whisper, TTS) charges have their own pricing models, typically per-image or per-minute rather than per-token

Each line shows the unit rate, the quantity consumed, and the line total. The math should reconcile cleanly against your application's usage logs in platform.openai.com → Usage.

Adjustments section - credits and offsets. Below the line items, the invoice lists any prepaid credit consumption (drawing down your loaded balance) and any promotional credits applied. If you bought $500 in prepaid credits and consumed $87 of usage in the cycle, this section shows the $87 drawn against your balance.

Total section - the bottom line. Subtotal, VAT/tax line (if applicable to your billing entity - see below), and total amount due. Payment status confirms whether the charge succeeded against your card or invoice payment method.

For finance teams, the most valuable reconciliation column is the per-model token count. A single inefficient prompt template, used at scale across thousands of API calls per day, can shift cost dramatically - and the per-model breakdown is the only place that signal surfaces clearly.

---

OpenAI LLC vs OpenAI Ireland Limited - which one billed you?

OpenAI's billing is split across two legal entities, and which one issues your invoice depends on where your billing address is registered:

• OpenAI LLC - Delaware-registered US entity. Bills US-based businesses and most Rest-of-World accounts. No VAT applies.

• OpenAI Ireland Limited - Ireland-registered EU entity. Bills EU and UK-based businesses for EU-compliant invoicing.

The distinction matters for three reasons.

Bank statement disambiguation. Charges from OpenAI Ireland Limited may appear as OPENAI IRELAND LIMITED, OPENAI*CHATGPT SUBSCR, or OPENAI*CH on European bank statements. US charges typically show as OPENAI LLC or OPENAI OPCO (the operations entity for some flows). If you see OPENAI OPCO and can't match it to an invoice, check both your API and any consumer-product (ChatGPT Plus) accounts - OPCO often covers cross-product operations charges.

Tax reclaim and bookkeeping. EU and UK businesses reclaiming VAT need invoices showing the OpenAI Ireland Limited entity, your business VAT ID, and the reverse-charge notation. Invoices from OpenAI LLC do not satisfy EU VAT documentation requirements.

VAT treatment for EU/UK businesses. OpenAI Ireland Limited applies the reverse-charge mechanism for B2B digital services to EU and UK businesses with a valid VAT ID on file - the invoice shows the net amount with a reverse-charge notation, and your business self-accounts for VAT in your local tax return. To trigger this, add your VAT ID in Settings → Organization → Billing → Billing details; OpenAI validates it against the EU VIES system and applies reverse-charge to future invoices. Without a VAT ID, EU buyers see standard Irish VAT (23%) added to the invoice instead. OpenAI LLC does not apply VAT.

To verify which entity bills you, check the Billing details section of any past invoice or the Settings → Organization → Billing → Billing details page, where the active billing entity appears in the header.

---

Identifying OpenAI charges on your bank statement

OpenAI's billing model creates a structural mismatch between invoice amounts and bank charges that trips up most finance teams the first time they reconcile. Understanding the charge descriptors - and why the amounts don't map cleanly to invoices - is the first step.

Charge descriptors by entity and product

OpenAI uses several different merchant descriptors depending on the billing entity, product, and payment processor routing:

• OPENAI LLC - the standard descriptor for US-billed API charges. Most common for US and Rest-of-World accounts.

• OPENAI OPCO - OpenAI's operations co entity, used for some billing flows including cross-product charges. If you see OPENAI OPCO and can't match it to a specific invoice, check both your platform.openai.com Billing history and any ChatGPT consumer subscriptions under the same payment method - OPCO charges sometimes consolidate cross-product activity.

• OPENAI*CH or OPENAI*CHATGPT SUBSCR - descriptors common on European and UK bank statements, typically associated with OpenAI Ireland Limited charges. Despite the CHATGPT string in the descriptor, these can reflect API charges, not just consumer ChatGPT subscriptions.

• OPENAI IRELAND LIMITED - appears on some EU bank statements as the full legal entity name for charges routed through the Ireland entity.

Why amounts don't match cleanly:

• Prepaid credit purchases trigger a bank charge at the moment of purchase, generating an immediate invoice - but the credits don't appear as "usage" until you consume them

• Auto-recharge triggers a bank charge each time your balance falls below your configured threshold (typically $5–10), which can happen multiple times per month at scale

• Cycle invoices for invoice-billed customers (typically larger accounts) cover a billing period, which may span parts of two calendar months

This means a single calendar month can produce three charges (two prepaid credit top-ups plus one cycle invoice), and a $200 invoice on April 15 might cover usage from late March through mid-April.

Reconciliation workflow:

1. Pull your OpenAI billing history for the period in question

2. Match each invoice to a bank charge using the invoice number and transaction ID

3. For prepaid credit purchases, match the credit purchase invoice to the corresponding bank charge by amount and date

4. Track the running prepaid credit balance separately - it's a liability on your balance sheet until consumed

Distinguishing API from ChatGPT charges. If you hold both an API account and a ChatGPT Plus subscription under the same payment method, both can produce OPENAI* charges in the same month. API charges originate from platform.openai.com and appear as prepaid credit purchases or cycle invoices. ChatGPT Plus charges are a flat recurring subscription ($20/month) billed through chat.openai.com. When the descriptors overlap (especially OPENAI*CHATGPT SUBSCR on EU statements), cross-reference by amount: a $20.00 charge almost always maps to ChatGPT Plus; variable amounts map to API usage or top-ups.

For multi-vendor AI stacks (OpenAI plus Anthropic, Mistral, Replicate, GitHub, Stripe, AWS, etc.), this reconciliation effort multiplies per vendor. The Tailride Chrome extension handles the matching automatically by pulling structured invoice data with transaction IDs from every connected portal in a single workflow - the multi-vendor reality is exactly what extension-based extraction was built for.

---

What manual download doesn't give you (and where the Chrome extension fits)

OpenAI's billing portal handles single-invoice retrieval well, but three structural limitations show up the moment your AI spend scales beyond casual use:

Limitation 1: No bulk download. The Billing history tab requires opening each invoice individually and clicking Download PDF per record. There's no master checkbox, no date-range bulk export, no ZIP package. For a finance team pulling 12 months of historical invoices for an audit, that's 12+ individual download operations per OpenAI organization.

Limitation 2: No auto-email of PDFs. OpenAI sends notification emails when an invoice is ready, but the actual PDF must be downloaded from the portal. Unlike Stripe or Google Ads, there's no setting to forward the PDF to a finance inbox automatically. Finance teams that want invoices in their accountant's mailbox have to manually forward each one after downloading.

Limitation 3: No multi-organization aggregation. Businesses with multiple OpenAI organizations (typical for agencies, consultancies, or multi-product companies) must switch between orgs in the dropdown and run separate retrieval workflows for each. There's no native cross-org export.

The Tailride Chrome extension addresses all three. It runs inside your active platform.openai.com browser session - no password is ever entered into a third-party tool, no credentials are stored - and pulls every OpenAI API invoice in your billing history in a single bulk operation. Output is delivered as PDF files plus a structured CSV containing the invoice metadata (invoice number, billing entity, date, amount, VAT line, transaction ID), ready to import into QuickBooks, Xero, or any ERP with a CSV connector.

For finance teams running multi-vendor AI stacks, the same extension covers OpenAI alongside 30+ other AI and SaaS portals - Anthropic, Mistral, Replicate, GitHub, Stripe, Vercel, AWS, Google Cloud, and others - in one unified extraction queue. That's the typical reality for any AI startup or scale-up: OpenAI is one of many vendors, and invoice retrieval scales as a multi-portal problem rather than a single-vendor one.

---

Is manual download enough for your situation?

Solo developer running a personal project or small SaaS? Manual platform.openai.com download is sufficient. Pull the invoice once a month, file it, move on.

In-house finance team handling a single OpenAI organization? Manual works at low cycle counts but starts costing meaningful operator time when prepaid credit purchases trigger frequent invoices. Most teams in this profile install the Tailride Chrome extension once, set it to run weekly, and stop thinking about OpenAI invoice retrieval entirely.

Multi-product business with OpenAI + multiple other AI/SaaS vendors? This is where the extension stops being a convenience and becomes a recurring time saver. Tailride for finance teams consolidates Anthropic, Mistral, Replicate, OpenAI, and 30+ other vendor portals into one console with structured output across all of them.

Accounting firm reconciling AI spend across multiple clients? Each client has their own platform.openai.com login, their own billing entities to track (LLC vs Ireland Limited differ across clients), their own prepaid credit balance state. Tailride's multi-client AP automation console handles the cross-client orchestration; built specifically for accounting firms with 5+ clients running modern AI stacks.

How this scales: native portal vs continuous extraction

---

At scale: what manual OpenAI API invoice work actually costs

A single invoice download from platform.openai.com takes 2–3 minutes including authentication, navigation to Billing history, opening the detail view, downloading the PDF, and renaming for filing. At cycle volumes of 1–2 invoices per month, the math is trivial.

The cost compounds in two specific multi-vendor patterns. AI startup finance team profile: OpenAI plus Anthropic, Mistral or Cohere, Replicate, Vercel, Stripe, GitHub, AWS, Google Cloud - typically 8–12 vendor portals, each requiring its own retrieval workflow. At 2–3 minutes per portal per cycle, this aggregates to 60–90 minutes monthly of pure admin time. Accounting firm profile: 5–10 dropshipping or AI-startup clients each with 8+ vendor portals brings the recurring monthly load to 8–15 hours of operator time.

Manual platform.openai.com download vs Tailride extraction

Three routes by where invoices arrive

1. Browser-session extraction - the Tailride Chrome extension for invoices retrieved directly from platform.openai.com. Free Chrome extension, runs in your existing browser session, no credentials stored. Pulls every OpenAI API invoice plus invoices from 30+ other AI and SaaS vendor portals in one workflow.

2. Inbox-side extraction - for OpenAI billing notifications that route to a finance email address. AI inbox scanning reads Gmail, Outlook, and IMAP inboxes hourly; combined with extracting invoices from Gmail for vendors that deliver PDFs by email, it covers the email-side surface alongside the portal-side.

3. Multi-client console - Tailride's accounting console covers the multi-client dimension for firms reconciling AI spend across multiple client portfolios. Free trial available to test against a current client roster.

---

Common OpenAI API invoice problems

My invoice from last cycle hasn't appeared yet

OpenAI generates cycle invoices 24–48 hours after the billing cycle closes. If 48 hours have passed and there's still no invoice, the most likely explanation is that no chargeable activity occurred - OpenAI doesn't issue zero-amount invoices. For prepaid credit accounts, the cycle invoice may not appear if the cycle was funded entirely from existing credit balance.

My bank charge doesn't match any invoice amount

This is almost always the prepaid credit / auto-recharge mechanic. Bank charges for prepaid top-ups or auto-recharge events fund your balance - the corresponding invoice in Billing history matches the top-up amount. Cycle invoices show usage drawn against that prepaid balance, not new bank charges. Match each bank charge to a top-up invoice (same amount, same date) and each cycle invoice to the prepaid balance consumption.

VAT isn't appearing on my OpenAI Ireland Limited invoice

For VAT-registered EU/UK businesses with a valid VAT ID on file, the invoice correctly shows no VAT line - the reverse-charge mechanism applies and your business self-accounts for VAT in your tax return. If you expected VAT and don't have a VAT ID registered, check Settings → Organization → Billing → Billing details and add one. Without a VAT ID, EU buyers see standard Irish VAT (23%) added to the invoice.

I'm seeing charges but I haven't used the API recently

The most common cause is auto-recharge enabled on a low balance threshold. When your prepaid credit balance falls below the configured threshold (typically $5 or $10), OpenAI charges your card to top up the balance, even if no actual API usage triggered the top-up. Disable auto-recharge in Settings → Organization → Billing → Auto-recharge if you only want to fund credits manually.

What is the OPENAI OPCO charge on my credit card?

OPENAI OPCO is the operations co entity used for some OpenAI billing flows, typically appearing in cross-product or operational charges. If you see this charge and can't match it to a clear API invoice, check both your platform.openai.com Billing history and any consumer ChatGPT subscriptions you may have under the same payment method - OPCO charges sometimes consolidate cross-product activity.

I need an invoice for ChatGPT Plus, not the API

ChatGPT Plus uses a separate billing portal accessed via chat.openai.com → Settings → Subscription, with invoices issued via OpenAI's Stripe integration. The download workflow is different and is covered in How to Download ChatGPT Plus Invoices.

---

FAQ

Can I download all my OpenAI API invoices at once?

Not natively. The Billing history tab in platform.openai.com requires individual invoice downloads - there's no bulk export, no master checkbox, no date-range ZIP. For bulk retrieval, the Tailride Chrome extension pulls every OpenAI API invoice in your history in a single bulk run, with structured CSV output ready for accounting.

Can OpenAI email me PDF invoices automatically?

No. OpenAI sends a notification email when an invoice is ready, but the actual PDF must be downloaded from the portal. The notification email contains the invoice metadata but not the PDF attachment. To approximate auto-email behavior, the Tailride Chrome extension extracts invoices on a schedule and can route them to a designated finance inbox or accounting destination.

What's the difference between OpenAI API and ChatGPT billing?

They're entirely separate products with separate billing portals. OpenAI API is the developer/programmatic product accessed via platform.openai.com - usage-based, billed by token consumption. ChatGPT (Plus, Team, Enterprise) is the consumer product accessed via chat.openai.com - flat subscription pricing. See How to Download ChatGPT Plus Invoices for the consumer path or browse the broader OpenAI invoices and receipts hub for cross-product context.

Do I get an invoice for prepaid credit purchases?

Yes. Each prepaid credit purchase generates an immediate invoice in your Billing history, distinct from the cycle invoice that documents subsequent usage. For accounting purposes, prepaid credit purchases are typically posted to a balance-sheet asset account (prepaid expense) rather than directly to expenses, then drawn down monthly as the credit is consumed.

How does OpenAI container billing show on my invoice?

Container billing appears as a separate line item, typically billed per second of compute time used by hosted code execution. The line item shows the total compute seconds consumed and the per-second rate. For applications using container features heavily, this line can become a meaningful share of monthly spend - worth tracking separately in your accounting categorization.

My business is non-EU and non-US. Which OpenAI entity bills me?

OpenAI LLC bills most Rest-of-World businesses, with no VAT applied. Some jurisdictions may have local sales tax requirements that surface differently - consult your local tax advisor for jurisdiction-specific treatment. For EU and UK businesses, OpenAI Ireland Limited handles billing with VAT/reverse-charge logic.

Can I get an invoice with a different billing address than my account default?

Update your billing address in Settings → Organization → Billing → Billing details before the next cycle invoice generates. Already-issued invoices cannot be edited - for corrections, contact OpenAI support through the help center with the invoice number and the correction needed.

---

Related guides

• How to Download ChatGPT Plus Invoices - separate guide for consumer ChatGPT subscription billing

• OpenAI invoices and receipts hub - cross-product reference covering both API and ChatGPT invoicing

• Automated OpenAI API invoice extraction - for teams ready to move beyond manual workflows

• Invoice data extraction software - how AI-driven extraction works across vendor invoices

• Automated invoice capture software - broader guide to invoice capture across all vendor types

• Extract invoices from Gmail automatically - for finance teams whose vendor invoices arrive via email