Why this post exists#
You pay 20 US dollars a month for Claude Pro. Another 20 for ChatGPT Plus. Maybe 20 for Cursor on top. At some point you stop guessing what that means on your Einnahmen-Überschuss-Rechnung.
Three numbers matter for any German freelancer or sole trader who subscribes to AI tools: what you can deduct, how the VAT works on US-based subscriptions, and what the invoice must actually contain to be accepted by the tax office. None of this is unique to AI tools. All of it has sharp edges that most vendor marketing pages ignore.
This post maps the rules to concrete tools: Claude Pro, ChatGPT Plus, Cursor Pro, GitHub Copilot, Microsoft 365 Copilot. All rules cited with paragraphs and URLs. Verified April 2026.
This is not tax advice. It is a map of the rules as they stand. For decisions about your specific case, talk to a Steuerberater.
The base rule: §4 Abs. 4 EStG#
The entire question "can I deduct this" has a two-sentence answer in German tax law:
"Betriebsausgaben sind die Aufwendungen, die durch den Betrieb veranlasst sind."
Translation: expenses are business expenses when caused by the business. Source: §4 EStG.
If you use Claude Pro to write blog posts for your freelance web development business, the 20 dollars a month is caused by the business. Deductible. Same for Cursor, ChatGPT Plus, Notion AI, DeepL Pro, and any other SaaS you can plausibly tie to your work.
The complications start with two facts: most of these tools are billed by US entities, and many people also use them privately.
The private-use problem#
If your Claude Pro subscription is 100 percent business, you deduct 100 percent. If it is fifty-fifty, the split matters. German tax case law has a clean rule here.
The Bundesfinanzhof threw out the blanket ban on deducting mixed-use costs in 2009 (Grosser Senat 1/06). Since then, mixed-use expenses can be split proportionally, or deducted fully if private use stays at or below roughly ten percent. This is the same principle that has covered computers and software for two decades (BFH VI R 135/01).
In practice for AI subscriptions:
- Private use under 10 percent: full deduction, no split needed.
- Between 10 and 90 percent: split by plausible criteria (time, projects, usage counts). Document it.
- Private use above 90 percent: not deductible at all.
There is no BFH ruling or BMF letter specifically on AI subscriptions as of April 2026. The analogous rulings on computers and internet access are what practitioners use. The Accountable blog on AI as a business expense is a good practitioner summary.
For solo freelancers whose entire business runs through a machine, treating Claude Pro or ChatGPT Plus as 100 percent business is usually defensible. Keep a separate free account for personal use if you want cleaner boundaries.
Reverse charge: the main trap on US subscriptions#
Most AI vendors are based in the US or Ireland. That changes how VAT works. You are not just paying the sticker price, you are buying a service that crosses a border.
The mechanism is called reverse charge. It sits in §13b UStG. Short version: when a non-EU business delivers a service to a German business customer, the VAT liability flips. The seller does not charge VAT. The buyer declares and pays the German VAT themselves, then usually claims it right back as input tax (Vorsteuer).
For a regular VAT-registered freelancer on Regelbesteuerung, this is a zero-sum paperwork exercise. You declare 19 percent owed, you claim 19 percent back. Net effect on your wallet: nothing. But the paperwork must be correct, or the deduction fails.
What you actually do#
To get reverse charge to work, you need to do three things:
-
Enter your USt-IdNr in the vendor's billing account. Claude: Settings > Billing > Tax/VAT ID. OpenAI: Billing information via Stripe. Cursor: account billing page. GitHub: profile billing. Without this, the vendor will charge you foreign VAT that you cannot recover.
-
Get an invoice, not a receipt. A Stripe receipt is not the same thing as an invoice under §14 UStG. Kleinbetragsrechnungen under 250 euros have lighter requirements, but the reverse-charge exception does not apply to the simplified form. For reverse charge you need the full catalogue including both VAT IDs and the "Steuerschuldnerschaft des Leistungsempfängers" line (§14a UStG).
-
Book it correctly. Your bookkeeping software (sevDesk, Lexware Office, DATEV) needs to mark the expense as §13b reverse charge. The VAT return shows the owed VAT in one field and the input tax in another. For most tools this is a manual tax code, not automatic.
Vendor by vendor#
Claude (Anthropic): Billed from Anthropic PBC in San Francisco. US entity, not the Anthropic Ireland Ltd that has existed on paper since March 2024. Anthropic runs EU sales through Stripe using the One-Stop-Shop mechanism for non-EU providers. Without a VAT ID on file you pay 19 percent German VAT collected via OSS. With a VAT ID on file, you get a zero-VAT invoice and book reverse charge yourself. Procedure and paths: Anthropic tax FAQ.
ChatGPT Plus and Business (OpenAI): Billed from OpenAI Ireland Limited in Dublin (VAT IE4143435AH). This is an EU entity, so the mechanism is different. With a VAT ID on file, you get an intra-community invoice with reverse-charge note under §14a UStG. Without a VAT ID, you pay Irish or German VAT. Some users have reported that the VAT ID field has been buggy and unavailable without support contact. Reference: OpenAI EU Terms.
Cursor (Anysphere): US entity. Since around February 2026, Cursor's Stripe setup has started charging VAT on EU subscriptions. Community reports show mixed behavior: VAT ID field exists, invoices may or may not show the reverse charge note correctly. The Cursor forum thread on EU VAT is the best public tracker. Practical approach: enter your VAT ID, review the first invoice carefully, and if the reverse-charge line is missing, treat the subscription under §13b Abs. 2 Nr. 1 UStG for a non-EU service and declare the German VAT yourself.
GitHub Copilot Individual: Microsoft runs a unified EU VAT registration under OSS (the VAT number GitHub uses is EU528001391). For personal accounts, GitHub issues "receipts," not proper §14 UStG invoices. This is a known issue and creates friction with Steuerberater. Workaround: in the personal account billing settings, enter your business name as the company and your USt-IdNr. The receipt then carries your tax data. GitHub Enterprise and Business accounts produce proper invoices. Discussion thread: GitHub community on Copilot invoices.
Microsoft 365 Copilot: Billed through Microsoft Ireland Operations Limited, same pattern as OpenAI. EU intra-community service with reverse charge when a VAT ID is present. Microsoft announced an EU price adjustment for 1 July 2026 (approximately 7 percent reduction) on its official pricing page.
The Kleinunternehmer trap#
If you run under the Kleinunternehmer rule (§19 UStG), you charge no VAT to your own customers. Most people assume that means VAT on purchases does not concern them. For AI subscriptions from abroad, that is wrong.
The Kleinunternehmerregelung was restructured on 1 January 2025. The new limits are 25,000 euros net in the previous year and 100,000 euros in the current year (BMF Schreiben 18 March 2025). Sales are now VAT-exempt rather than "VAT not collected," which is a legal difference that matters for cross-border work. Overshooting the 100k in-year limit means immediate switch to regular VAT treatment, not next year.
Here is the part most people miss: reverse charge under §13b still applies to Kleinunternehmer. If you buy a Claude Pro subscription from Anthropic PBC and you have a USt-IdNr on file, you owe 19 percent German VAT on that subscription. A regularly VAT-registered freelancer offsets this against input tax and the net effect is zero. A Kleinunternehmer cannot claim input tax. You pay the 19 percent and it stays paid.
For Claude Pro at 20 USD a month, that's roughly 3.60 euros of extra cost per month you cannot recover. Across a Claude + ChatGPT + Cursor stack that is 11 to 15 euros per month of hidden VAT a Kleinunternehmer eats on top of the sticker price.
What to do: if you have already hit the point where you subscribe to multiple US-based AI tools, the Kleinunternehmer status deserves a calculation. Depending on your other reclaimable input taxes (equipment, co-working, hosting), you may be better off opting for regular VAT treatment. This is a conversation with a Steuerberater, not a snap decision.
Kleinunternehmer also need to apply for a USt-IdNr separately from their Steuernummer if they have not already, because the VAT ID is what unlocks the reverse-charge flow with vendors. The application is free at the Bundeszentralamt für Steuern.
What a compliant invoice looks like#
For a subscription to count as a deductible expense backed by a proper invoice, the document needs the §14 UStG catalogue:
- Vendor name and address
- Vendor VAT ID or tax number
- Customer name and address
- Issue date
- Sequential invoice number
- Service description and quantity
- Date of service performance
- Amount, broken down by VAT rate
- VAT rate and amount, or note on exemption or reverse charge
- On reverse-charge invoices: "Steuerschuldnerschaft des Leistungsempfängers"
A receipt that lacks the customer name, address, or the reverse-charge line is technically defective. The IHK Stuttgart rules on invoice requirements are the clearest summary. In practice, tax offices are pragmatic about small amounts from well-known vendors, but large items or repeated defects will draw questions.
This is why hitting "Add company details" in your vendor account matters. A Claude Pro invoice issued to a full business name and USt-IdNr with a reverse-charge line is uncontroversial. An invoice addressed only to "John Smith, johnsmith@gmail.com" with no VAT details is not.
Currency and documentation#
US vendors bill in USD. German bookkeeping is in EUR. The VAT law uses the exchange rate on the date of service (Leistungstag), not the payment date. The Bundesfinanzministerium publishes a monthly average rate that is the standard reference; the Bundesbank daily rate is acceptable if applied consistently. Bookkeeping software handles this automatically.
The small difference between the rate on the invoice date and the rate when your card actually cleared shows up as a currency gain or loss in your books. For small subscriptions this is a rounding item. For large annual payments it can be visible.
GoBD: 8 years, digital originals#
Digital invoices must be kept in digital original form. No printouts substitute. They must be unchangeable (revisionssicher) and machine-readable. The d.velop compliance summary covers what that means technically.
The retention period changed on 1 January 2025. The Fourth Bureaucracy Relief Act (BEG IV) shortened the rule from 10 years to 8 years for invoices and booking documents (d.velop on the new retention rules). The 10-year period still applies to main accounting books, inventories, and opening balances. The period starts at the end of the calendar year of invoice issue. An invoice dated 27 September 2025 must be kept until 31 December 2033.
Every mainstream German bookkeeping tool (Lexware Office, sevDesk, DATEV Unternehmen Online) stores receipts GoBD-compliant by default when you upload them through the app. The common mistake is relying on Gmail as your archive: a deleted message or a provider migration breaks the retention chain.
E-invoicing: what changed 1 January 2025#
Separate topic, same ballpark. The E-Rechnungspflicht came into force on 1 January 2025 (BMF FAQ on e-invoicing).
For most freelancers the rule currently reads as follows:
- Every German business (including Kleinunternehmer) must be able to receive e-invoices in the EN 16931 format (XRechnung, ZUGFeRD 2.x).
- Issuing e-invoices is optional in 2025 and 2026. From 2027, paper invoices are only allowed if your prior-year revenue was at or below 800,000 euros. From 2028, e-invoice issuing is mandatory.
- Kleinunternehmer are exempt from the issuing requirement long-term, but still need to receive.
Foreign AI vendors without a German establishment are not bound by German rules, so none of this currently affects Claude Pro or ChatGPT Plus billing. You will still get a standard PDF or Stripe-hosted invoice. E-invoicing matters mainly for your own outbound invoices to German B2B customers.
Recommended bookkeeping setup#
The sustainable setup for a solo freelancer with a US-heavy AI stack:
- Pick one bookkeeping tool that handles reverse charge explicitly. sevDesk has a dedicated help article on reverse charge for non-EU services. Lexware Office supports it through manual tax codes. DATEV Unternehmen Online is the default if you work with a Steuerberater.
- Add your USt-IdNr everywhere. Every AI vendor account, every subscription. This is a ten-minute task that pays off every month.
- Download invoices monthly, not at year-end. Stripe-hosted invoices sometimes expire. Dead URLs mean missing receipts.
- Mark reverse-charge transactions immediately. Automatic detection of US SaaS as §13b is not reliable in any tool as of April 2026. A ten-second decision in the moment beats a two-hour cleanup in March.
- Keep one business credit card. Separating business from private cards is the single biggest quality-of-life improvement for any freelancer's bookkeeping.
What changes in 2027 and beyond#
Two things are worth watching. First, the e-invoicing mandate expands in 2027 and completes in 2028. Second, vendor VAT setups are actively moving: Anthropic has an Irish entity on paper that is not yet billing, Cursor shifted its Stripe Tax approach in February 2026, Microsoft is repricing EU subscriptions mid-2026. Any of these can flip a US reverse-charge case into an EU intra-community case, which changes which paragraph applies and what the invoice must show.
The practical consequence is small: keep reviewing the first invoice from each vendor each January to confirm nothing has structurally moved. If a vendor switches from US to EU entity, your bookkeeping tax code needs to switch from §13b Abs. 2 Nr. 1 to §14a (intra-community).
Bottom line#
For a solo freelancer on Regelbesteuerung, AI subscriptions from US vendors are straightforward paperwork: add the VAT ID, confirm reverse charge, book it as §13b, reclaim the input tax in the same return. Net cost is the sticker price, no surprises.
For Kleinunternehmer, the calculation is different and deserves a specific review. The hidden VAT cost on a multi-tool AI stack can be significant enough to reconsider the regime.
For everyone, the binding rule is the invoice. Without proper §14-compliant documents, no deduction holds up to a Betriebsprüfung, even if the expense is genuinely business-caused.
Get the VAT ID into every vendor account. Get the invoices archived. Book reverse charge cleanly. The rest is the ordinary discipline that any business expense has always required.
Reminder: This post maps the rules, not your specific situation. Talk to a Steuerberater before making decisions that depend on your regime, income level, or business structure.
Sources#
All sources verified April 2026.
Statutes and official documents
- §4 EStG — business expenses
- §13b UStG — reverse charge
- §14 UStG — invoice requirements
- §14a UStG — invoices for intra-community and reverse-charge cases
- §19 UStG — Kleinunternehmer
- BMF letter 18 March 2025 — Kleinunternehmer special rules
- BMF FAQ on e-invoicing
Industry guidance
- IHK Stuttgart — Kleinunternehmer rule
- IHK Stuttgart — mandatory invoice fields
- Haufe — foreign-currency invoice rules
- Haufe — Kleinunternehmer 2025 changes
- Accountable blog — AI as a business expense
- buchhaltung-effizient.de — reverse-charge trap for Kleinunternehmer
- d.velop — GoBD retention periods
- d.velop — GoBD-compliant archiving
- sevDesk — reverse charge for non-EU services
Vendor documentation
