If you are evaluating an AI vendor for a Berlin, Munich, or Frankfurt B2B company, the questionnaire your CFO sends back almost always opens with the same three lines: "Does the vendor invoice in EUR? Do they handle VAT reverse charge correctly for cross-border B2B services? Can I export a per-transaction EUR ledger that reconciles against their monthly invoice?" The privacy and DPA questions — covered in our EU AI Vendor Compliance Checklist — only arrive once finance signs off on the invoicing stack.
This post walks through what changes when the vendor issues EUR-denominated invoices instead of USD or CNY, when the EU VAT reverse charge applies to cross-border B2B AI services, what fields the Berlin Finanzamt and a typical auditor will look for on a compliant EU invoice, and how TokenBridge ships each of those items out of the box. It is written for the buyer-side finance, procurement, and accounts-payable teams, not for vendor engineering. Where TokenBridge is the working example on a given item, we link to the page where the evidence actually lives: the EUR pricing table and the invoice download surface.
Why EUR billing is the first compliance question
The CFO's question is rarely about FX as such — it is about audit-trail integrity. A USD invoice from a non-EU vendor gets converted to EUR twice: once by Stripe or the buyer's card issuer at the moment of payment, and again by the buyer's accounting system at month end. Two FX rates, two sets of journals, and a reconciliation gap that the auditor will eventually open.
A EUR-denominated invoice collapses that to a single line item. The wallet is funded in EUR, the vendor's invoices are issued in EUR, and the per-transaction usage ledger — the record finance actually audits against the top-up — is also in EUR. There is no FX exposure on the buyer side, no bank-rate adjustment at month end, and no question of which FX rate to apply. See the EUR pricing table for the published rates per million tokens per model, and the invoices page for the per-charge line items that flow back to finance.
The second reason EUR billing matters: the EU VAT Directive treats the currency of the invoice as part of the audit trail. An invoice issued in a non-EUR currency forces the buyer to declare the EUR equivalent at the ECB reference rate of the supply date, which is a second manual step the auditor will check. An invoice issued in EUR removes that step.
VAT reverse charge for intra-community B2B AI services
When a B2B customer in, say, Germany buys a cross-border B2B service from a vendor established in another EU member state (or — under specific conditions — from a vendor established outside the EU with an EU VAT registration), the supplier does not charge German VAT. Instead, the customer self-accounts for the VAT via the reverse charge mechanism, declared on their next German VAT return (Umsatzsteuervoranmeldung).
The legal basis is Article 196 of the EU VAT Directive, which Germany implements in § 13b UStG (and § 25 UStG for the supplementary invoice requirements). The mechanism is not optional — if the conditions are met, reverse charge applies automatically. The seller still must issue a valid VAT invoice, and that invoice must carry the reverse-charge note.
What the buyer-side invoice must contain for reverse charge to be valid:
- The VAT identification numbers of both the supplier and the customer (the buyer's German USt-IdNr. or DE-VAT-ID).
- An explicit statement that the reverse charge applies — usually a line reading "Reverse charge — recipient liable for VAT under Article 196 of Council Directive 2006/112/EC" (or the equivalent German reference, § 13b UStG).
- The supply date and the invoice date.
- The net amount in EUR, the VAT rate that would have applied (e.g. 19%), the VAT amount (zero under reverse charge), and the gross amount in EUR.
A vendor that issues an EUR invoice but does not validate the customer's VAT ID, or that omits the reverse-charge note, produces an invoice the buyer's auditor will reject. The validation step is not a "nice to have" — VIES (the EU VAT Information Exchange System) or an equivalent check at signup is the only way for the seller to know reverse charge applies to a given customer in a given month.
EU entity invoicing requirements
A compliant EU invoice carries a defined set of mandatory fields. The list below is the minimum your auditor and the Berlin Finanzamt will check for on a B2B AI services invoice; missing any of them makes the invoice non-deductible in the eyes of the buyer-side auditor:
- Supplier: full legal name, full address, supplier's VAT ID (member state prefix, e.g. DE for Germany).
- Customer: full legal name, full address, customer's VAT ID.
- Invoice number: unique, sequential, no gaps.
- Invoice date: the date the invoice was issued.
- Supply date: the date the service was supplied (or the billing period it covers).
- Description of supply: a clear description of the service — for AI services this should name the billing period and reference the underlying usage.
- Net amount, VAT rate, VAT amount, gross amount — all in EUR, with the VAT rate and VAT amount broken out even when reverse charge applies (the VAT amount is zero, but the line must be present).
- Reverse-charge note when applicable (see previous section).
The German § 14 UStG and § 14b UStG set the same fields, with the additional requirement that the invoice be issued by the 15th of the calendar month following the supply. A late invoice does not invalidate the tax treatment, but it does create a reconciliation gap the auditor will pick up at year end.
For TokenBridge customers, every wallet top-up produces a Stripe-issued EU-format invoice with all of the above fields populated, and the invoices page lets the buyer download the per-charge line items that reconcile against the wallet top-up. Finance does not need to chase the vendor for a usage breakdown — it is on the same surface as the invoice.
How TokenBridge resolves it
Concretely, the invoice stack ships as follows:
- EUR billing on every charge. Wallet top-ups are EUR-denominated; there is no USD or CNY line item anywhere on the buyer-side books. See the pricing table for the published EUR-per-million-tokens rates per model.
- VAT reverse charge applied automatically. When the buyer enters a valid EU VAT ID at signup, the monthly invoice carries the reverse-charge note and the seller's VAT ID line; when the buyer is not VAT-registered, the invoice carries the standard German VAT line. The VAT ID validation is run at signup and re-checked before each monthly invoice is issued.
- EU-format invoices from Stripe. Each successful top-up produces a Stripe-issued EU-format invoice with all of the mandatory fields listed above. Invoices are downloadable from the invoices page and are also emailed on issue.
- Per-transaction EUR ledger. Every wallet credit is itemised at /dashboard with date, amount in EUR, and the VAT line. Finance can reconcile the monthly top-up against the per-charge ledger without going back to the vendor.
- Data residency aligned to invoicing. Because the invoices are issued in EUR by an EU-registered entity, they pair cleanly with the data residency and DPA controls — your DPO and your CFO are reading from the same vendor record.
Procurement checklist (invoicing-specific)
Drop these items into the invoicing section of your standard vendor-evaluation form. "No" or "TBD" on any of them is a flag your CFO will catch.
- [ ] Vendor issues EUR invoices, no FX line on the buyer side.
- [ ] Vendor validates the buyer's VAT ID (VIES or equivalent) at signup and re-checks before each invoice.
- [ ] Invoice carries the reverse-charge note ("Reverse charge — recipient liable for VAT under Article 196") when the buyer is VAT-registered cross-border.
- [ ] Mandatory fields present: both VAT IDs, invoice number, supply date, invoice date, description of supply, net + VAT + gross in EUR.
- [ ] Invoices issued by the 15th of the calendar month following the supply (per § 14 UStG).
- [ ] Per-transaction EUR ledger downloadable for finance reconciliation, with date, amount, and VAT line per row.
- [ ] Refund / credit-note flow documented before signing — see the Refund Policy for the TokenBridge flow.
- [ ] DPA available without an NDA, aligned to the invoicing entity — see the full DPA text.
Final note for Berlin/Frankfurt readers
If you are running this checklist against a vendor that is not yet passing on EUR billing, VAT reverse charge, or the per-transaction ledger, raise it before signing — most vendors will fix it on a 30-day notice. If you are evaluating TokenBridge specifically, the Trust & Compliance hub is the page to start from for the privacy side, and the pricing table and invoices page are the surfaces to verify the invoice stack against this checklist directly. For procurement follow-up before a sales call, the contact form reaches the operator team within one business day.
Ready to verify? Read the Trust & Compliance hub · See pricing