← All guides · Freelancers & business
Selling digital services to EU businesses: invoicing remote work across borders
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Convert an invoice free
Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.
Short answer
Digital services are the cross-border freelancer economy's core product, and their B2B invoicing shape is remarkably stable: the client is a business in another member state, the lines typically run under reverse charge (category AE at 0%), both VAT identifiers appear on the invoice, and the deliverable files — UBL XML and Factur-X PDF — travel by the client's channel, Peppol included. What varies is only the client's mandate position, which the acceptance checker computes per invoice.
What defines digital-services B2B invoicing?
Digital services (software, design, development, marketing, content, consulting delivered remotely) sold to EU business clients are the classic case in this product's worked examples — translation, design, training, support — because the converter's audience is 'freelancers and small firms invoicing EU clients'. Their invoices concentrate the cross-border rule pair: the seller's VAT identifier required on cross-border B2B invoices, and the buyer's identifier required when lines use reverse charge (AE).
Why digital services lead the structured transition
Digital sellers feel mandates first for a structural reason: their client base is borderless by default. A design studio's clients sit in six countries by accident of marketing, not by export strategy — so the mandate map is not a future market-entry question but a description of this month's billing run. Belgium's Peppol clients, Poland's phasing clients and Germany's structured-ready clients are already in the run; the only choice is whether the run's process treats that as normal.
The digital workflow also adapts cheapest: no stock, no shipping documents, no customs layer — the invoice is the trade's entire paperwork. When the paperwork's form changes, the change is total but shallow: one process, learned once, covers every border the services cross. Digital sellers who convert early therefore bank a disproportionate advantage: total compliance at hobbyist cost.
The standard shape: AE lines and the identifier pair
For B2B services supplied cross-border within the EU, reverse charge is the standard treatment this product's examples use: lines at category AE, rate 0%, the tax breakdown showing the AE group with its taxable total and zero tax, the payable equal to the net. The buyer's VAT identifier evidences their business status and self-accounting; the seller's identifier anchors the supply's origin. Validation enforces the pair — an invoice missing either is stopped before it can embarrass anyone.
Sellers should fix this shape in a template per client pattern, with the accountant's confirmation for their own circumstances recorded once. Deviations — a domestic client, a consumer sale (outside this shape entirely; consumers are not the reverse-charge world), a supply with a special treatment — are then conscious exceptions, not improvisations. The template carries the rule; the invoice carries the exception only when the facts demand it.
Subscriptions, retainers and recurring billing
Digital services bill repeatedly: monthly retainers, subscription periods, milestone series. Recurrence is where structured discipline pays compound interest — the client record, the template and the line pattern are built once and reused, so the marginal cost of each month's validated invoice approaches the cost of pressing convert. Line names carrying the period ('Support retainer — November 2026') keep approvals frictionless month after month, because the client's approver matches the line to the recurring budget line without thought.
Bulk conversion serves the multi-client version of the same rhythm: the month's retainers across all clients in one job, exceptions listed, exports to the ledger in the same motion. What never scales is the artisanal alternative — hand-built PDFs with drifting formats — because its cost per invoice never falls. Digital businesses understand marginal cost instinctively; invoicing should enjoy the same economics as the product it bills for.
Marketplaces, platforms and the B2C boundary
Digital sellers often meet clients through platforms and marketplaces, which insert their own invoicing machinery — sometimes issuing documents, sometimes self-billing (389) in the seller's name, sometimes merely introducing parties who then invoice directly. Identify which model each channel uses at onboarding: where the platform issues or self-bills, your job is verification of documents in your name; where you invoice directly, the full discipline of these guides applies unchanged.
Keep the B2B/B2C boundary bright. The reverse-charge shape presumes a business buyer with a VAT identifier; a consumer buyer is a different tax world that this product's B2B-focused guidance does not price or judge. Sellers with mixed audiences should segment their invoicing by audience first and apply each segment's rules separately — the cost of blurring the boundary is paid in treatments applied where they never belonged.
Currency, language and other remote-work details
Remote sellers price in the client's currency or their own — the invoice must pick one supported code (EUR, USD, GBP, CHF, PLN, SEK, DKK, CZK, HUF, RON, BGN, HRK, NOK) and hold every figure in it. Descriptions can speak the client's language where that aids approval; the structured fields (categories, codes, identifiers) are language-neutral by design, which is rather the point of codes: a Polish system and a Portuguese accountant read a line's category identically.
Finally, keep the commercial paperwork as borderless as the services: contracts and onboarding forms that capture the invoicing facts (identifiers, Peppol ID, channel, terms) as a matter of course for every new client, wherever they sit. The digital seller's office is a set of forms and defaults; make the invoicing form one of the good ones, and the whole EU becomes a domestic market with better scenery.
Digital-services invoicing in 5 steps
- Segment your clients: B2B with VAT identifiers (the reverse-charge world) versus B2C (different rules — keep the boundary bright).
- Template the standard shape per pattern: AE lines at 0% for cross-border B2B services, identifiers from the records, totals derived.
- Onboard through a form that captures identifiers, Peppol ID, channel and terms for every new client, wherever they are.
- Run recurring billing as a rhythm: period-named lines, bulk conversion for multi-client runs, exports to the ledger.
- Know each platform channel's model — direct invoicing, platform-issued documents, or self-billing (389) — and verify what carries your name.
Worked example: a SaaS consultant's six-country month
A SaaS implementation consultant bills six EU business clients in November 2026: retainers of EUR 1,800.00 to EUR 5,200.00, all cross-border B2B services, all category AE. One bulk run converts the six: five pass untouched; one — a new client's first invoice — stops because their VAT identifier was never captured by the sales call. The identifier is collected the same day (the onboarding form is amended that afternoon to make the field mandatory), the invoice re-runs clean, and the six go out by their channels — two by guided Peppol send, four as the UBL/Factur-X pair.
December's run contains no new lesson, which is the system working: the November exception permanently improved the form that feeds it. Digital businesses call this a feedback loop; in invoicing it is called growing up, and it compounds at the same rate.
Frequently asked questions
Are digital services always reverse-charged cross-border?
B2B services within the EU typically are — that is the shape this product's examples use — but the treatment of your supplies is your accountant's call for your facts. The template encodes the decision once it is made.
I sell through a marketplace — who invoices?
It depends on the channel's model: some platforms issue or self-bill (389) in your name; some merely introduce the parties. Establish the model at onboarding, and verify any document that carries your name.
Can I invoice EU consumers the same way?
No — the reverse-charge shape presumes a business buyer with a VAT identifier. B2C is a different tax world; segment your audiences and take advice for the consumer side separately.
Which currency should I bill in?
The one your contract states — one supported ISO code per invoice, all figures in it. EUR covers most EU B2B relationships; the validator also accepts USD, GBP, CHF, PLN, SEK, DKK, CZK, HUF, RON, BGN, HRK and NOK.
Do recurring retainers need fresh validation each month?
Each invoice is its own document and validates on conversion — which, with records and templates in place, takes moments. Recurrence is an argument for the discipline, not an exemption from it.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- Reverse charge VAT on e-invoices: category AE, 0%, and the identifier rule
- Freelancers invoicing EU clients: the e-invoicing playbook
- Bulk invoice conversion: turning a whole billing run into validated e-invoices
- Multi-currency e-invoices: currency codes, totals and what validation checks
- Self-billed invoices (type code 389): when the buyer issues your invoice