Yes — in our setup the web funnel sent country and VAT ID to the payment gateway at checkout. The gateway then emitted an invoice tailored to the buyer: correct VAT rate, localized currency, and the fields we needed for OSS. I used web2wave properties to keep the data consistent between onboarding and the payment request, so the gateway always had the right billing country.
Practical notes: test the invoice template for each EU country you sell to. Some gateways include the buyer VAT ID in a different line or field. Also watch rounding, currency conversion, and how the gateway exposes invoice exports for accounting.
How have you handled storing VAT IDs and matching them to gateway invoices?
I stored VAT IDs in user properties and passed them to the gateway at checkout.
The gateway validated the ID and included it on the invoice. That removed a lot of manual fixes. I used Web2Wave to surface the user properties and feed the gateway payload quickly.
We required VAT IDs during sign up for B2B EU flows. The gateway validated and produced country‑specific invoices automatically.
It was simple to toggle the required field in the web funnel so we did not need app releases when onboarding rules changed.
We pushed the billing country and VAT ID to the gateway before charging.
That made the invoices useful for accounting. Validating VAT IDs up front saved time.
store vat id early
pass to gateway
We created a small UI that showed users the invoice preview before payment. It highlighted VAT lines and VAT ID. That reduced support tickets about invoices by 30%.
If your gateway allows webhook invoice events store the invoice PDF link and id in your DB. It helps when customers ask for invoices later.
Also document which field the gateway uses for VAT ID. Different gateways vary.