AI API Invoice Reimbursement in China: A Practical Guide

For most engineering teams in China, getting reimbursed for AI API spend is harder than actually using the API. Invoices are in USD, the billing entity is a foreign company, and your finance department has no idea which cost center it belongs to. These three friction points block a surprising amount of legitimate usage. This guide walks through the full reimbursement workflow for the six platforms that come up most often — OpenAI, Anthropic, and Google on the overseas side, plus DeepSeek, Zhipu AI, and Aliyun Qwen domestically — with specific steps at each stage.

Overseas Platforms: What Invoices Look Like and Where to Find Them

All three major overseas platforms support self-service invoice downloads. The main challenge is knowing where to look.

OpenAI: Log in to platform.openai.com and go to Settings → Billing → Usage. A PDF invoice generates at the end of each billing cycle, issued under OpenAI, L.L.C. It includes a VAT/Tax ID field — US billing doesn't add VAT by default, but EU users will see it itemized. Download path: Billing → Invoices → select month → Download PDF.

Anthropic: The console is at console.anthropic.com. Go to Settings → Billing for monthly invoices issued under Anthropic, PBC. One important limitation: Anthropic doesn't currently support adding a Chinese company name to the invoice. Your options are to use an English billing name or attach a payment summary memo alongside the bank statement when submitting for reimbursement.

Google (Gemini API via Google Cloud): If you're calling the Gemini series through GCP, billing runs through the standard Google Cloud system. Path: Cloud Console → Billing → Documents. GCP lets you add a company name and tax ID to your account, so both will appear on the downloaded invoice — a cleaner paper trail than the other two.

Once you have the PDFs, you'll typically need to attach: - A bank or credit card statement confirming the actual payment - A currency conversion note (use the month-end rate published by the People's Bank of China) - A brief expense memo explaining what the spend was for

Domestic Platforms: Getting a Proper VAT Fapiao

Domestic platforms have a structural advantage here — they can issue Chinese VAT invoices (增值税发票) that finance departments recognize immediately. The process is straightforward, but there are details worth knowing for each platform.

DeepSeek (深度求索): After topping up on platform.deepseek.com, enterprise users can request an invoice under 费用中心 → 发票管理. DeepSeek issues VAT special invoices (增值税专用发票) at 6%, with your full company name and tax ID on the header. Minimum invoice amount is ¥100. Expect 3–5 business days, delivered as a PDF by email or as a physical copy by mail.

Zhipu AI (GLM series): Available at open.bigmodel.cn under 财务中心 → 发票申请. Also issues 6% VAT special invoices. The billing entity is 北京智谱华章科技有限公司 — double-check that you've entered the correct tax ID before submitting. A rejected invoice means starting over and delays the whole reimbursement cycle.

Aliyun (Qwen 3 / Tongyi Qianwen API): Runs through Aliyun's unified billing system at billing.aliyun.com. You can combine Qwen API charges with other Alibaba Cloud products on a single invoice, which is convenient for teams already running infrastructure on Aliyun. 6% VAT applies, invoices can be split, and the per-invoice cap is ¥1 million.

Platform	Invoice Type	VAT Rate	Minimum Amount	Processing Time
DeepSeek	VAT Special Invoice	6%	¥100	3–5 business days
Zhipu GLM	VAT Special Invoice	6%	¥100	5 business days
Aliyun Qwen	VAT Special / General	6%	¥1	1–3 business days
OpenAI	Foreign Commercial Invoice	No VAT	None	Auto-generated after billing cycle
Anthropic	Foreign Commercial Invoice	No VAT	None	Auto-generated after billing cycle
Google Cloud	Foreign Commercial Invoice	Region-dependent	None	Generated after monthly close

Account Classification: Three Approaches Finance Will Accept

This is where most reimbursements stall. There's no single mandated account code for AI API spend in China, but three categories have become standard practice.

Technology Service Fee (recommended for most cases): API calls are essentially purchased compute and model inference — a service, not a product. Booking it under 技术服务费 or 信息技术服务费 maps to 管理费用/技术服务费 or 研发费用/外购服务 on the chart of accounts. If your company claims R&D super-deductions (加计扣除), check with finance upfront whether API costs qualify to go into the R&D expense sub-ledger.

Software License / Subscription Fee: Companies that treat all SaaS and API subscriptions consistently sometimes use 软件使用费 instead. This works fine, but verify the tax treatment: if the vendor's invoice is categorized under 信息技术服务, input VAT is deductible in the normal way. If it's categorized as 软件产品, different rules apply.

Business Entertainment or Miscellaneous (avoid): When teams don't know where to put something, it sometimes ends up here by default. Don't. Business entertainment costs are only 60% deductible for corporate income tax purposes and are subject to caps. It costs you money for no reason.

For overseas payments, you'll also need to handle foreign exchange gains and losses. Record the expense at the spot rate on the payment date. If there's an unpaid balance at period end, revalue it at the closing rate and post the difference to 财务费用/汇兑损益. In practice, most teams settle monthly and the FX impact is minimal — but it can't be left off the books entirely.

Tax Withholding on Overseas Payments

Payments to OpenAI, Anthropic, and Google from a Chinese entity are technically subject to withholding obligations — this is a point that trips up a lot of teams.

Under current rules, payments for technology services to overseas companies are subject to withholding VAT (6%) and withholding corporate income tax (10% standard rate, reduced rates available under applicable tax treaties). In practice, the common scenario — paying by corporate card or via wire transfer — has no automatic withholding mechanism. Many small and mid-sized companies simply haven't filed proactively.

Practical guidance: For larger amounts (a single payment or annual cumulative total exceeding USD 50,000 equivalent), consult your tax authority and file through the foreign exchange management system at the time of payment. For smaller, high-frequency API charges, the cleanest solution is to use a domestic platform or an intermediary that can issue Chinese invoices — it sidesteps the withholding question entirely.

The Document Checklist That Gets Reimbursements Through First Time

Domestic platforms: VAT special invoice (original PDF or physical copy) + payment/top-up confirmation screenshot + one- or two-sentence expense description

Overseas platforms: Invoice PDF + bank or credit card statement with the corresponding charge highlighted + PBOC month-end exchange rate screenshot + expense memo + (for larger amounts) a brief note on tax treatment

The expense memo doesn't need to be formal. Finance just needs three things: who received the money, what business purpose it served, and which project or department it belongs to. Traceability is the goal, not length.

---

The most direct way to reduce this overhead is to use an API provider that issues compliant Chinese invoices in the first place. My team uses XycAi (https://www.xyc.ai) — a single OpenAI-compatible endpoint covering 200+ models including GPT-5.5, Claude Opus, and Gemini, starting from 14% of official list prices. XycAi holds a licensed LLM algorithm filing and issues fully compliant domestic invoices, which means the entire overseas invoice workflow described above simply doesn't apply. It also supports one-command setup for Claude Code, Codex, and Gemini CLI, which saves you the separate conversation with finance about why you're wiring money to a foreign company.