Free tier

← All guides · Freelancers & business

What to ask a new EU client before your first invoice: the supplier's onboarding questions

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

Before your first invoice to an EU client, ask: (1) your legal name and full billing address exactly as registered; (2) your VAT identifier; (3) your Peppol ID, if you have one; (4) how you receive structured invoices — Peppol, a platform, a portal; (5) for Poland, Germany and Spain, whether you are above the mandate size threshold; (6) any specification you require (CIUS-PT, XRechnung); (7) who in finance owns invoicing questions; (8) your payment terms and due-date convention. Each answer retires a known failure.

Why an onboarding question list?

Every field the validator demands and every channel the mandate table names corresponds to a fact about the client that only the client can supply: identifiers (BT-31/BT-48 discipline), addressing (Peppol ID), phase position (buyer size in the checker's computation), and channel (Peppol, KSeF, PDP/PPF, SdI, XRechnung/ZUGFeRD per the mandate table). Onboarding questions are how those facts move from the client's finance team into your client record while the relationship is at its most cooperative.

The identity questions: name, address, VAT identifier

A structured invoice's party block is compared as data, so 'close enough' names and addresses — trading names instead of legal names, a head-office address instead of the billing entity's — become mismatches in the client's system. Ask for the billing entity exactly as registered and the address exactly as it should appear, and record the answer verbatim. The VAT identifier question belongs in the same breath: copied from the client's own documents, it is the evidence field for cross-border treatment and the trigger-checked value in BR-CO-26 and BR-AE-02.

Ask even when the client is domestic and the rules do not force the question. Records built complete serve every future case — the client's expansion, your first cross-border invoice to their group, a change in their structure — and asking signals a supplier whose paperwork will never be the problem in the relationship. Finance teams remember that signal; it is given in the first week and spent for years.

The channel questions: Peppol ID, platform, portal

How an invoice should arrive is the client's fact to state. For Peppol clients: their Peppol ID, recorded character-for-character. For platform countries: the route their process uses (their KSeF arrangements in Poland, their SdI details in Italy, their PDP/PPF position in France). For document-model clients (Germany): which artefact they ingest — the XML, the hybrid, or both. One question, four possible shapes of answer, each recorded as the client's delivery instruction in their record.

Ask it as a logistics question, not a compliance quiz: 'So our invoices book straight into your system, how do you take structured invoices?' Clients answer logistics gladly — it is their process, described with pride by the people who built it. The supplier who asks is filed mentally under 'easy to pay', which is the only supplier taxonomy that has ever mattered.

The position questions: size class and specification

For clients in Poland, Germany and Spain, ask the size question directly: 'For e-invoicing phases, are you above the [KSeF/EUR 800k/EUR 8M] threshold?' Their answer sets the phase date in your records and the checker's verdicts until it changes. Polish clients will know their February-versus-April position; German clients their 2027-versus-2028; Spanish clients their 2027-versus-2028. If the contact does not know, the question routes itself to their finance team — which is itself a useful introduction.

Public-sector and large-enterprise clients may add a specification: CIUS-PT in Portugal, an XRechnung expectation in Germany, a Peppol BIS requirement anywhere. Ask 'is there a specification or supplier guide we should invoice against?' and record the answer (and the document, if one exists) in the client file. Country rule packs then have something concrete to check against, and the first invoice arrives already speaking the client's dialect.

The commercial questions: terms, contacts, references

Payment terms and due-date conventions belong to onboarding too: the agreed days, any reference the client needs on the invoice to route approval (a purchase order number, a cost centre — stated in their answer, placed in your invoice practice for them), and the finance contact who owns invoicing questions when something must be resolved. These are not EN 16931 validations; they are the difference between an invoice that is valid and an invoice that is payable without correspondence.

Capture the answers where invoices are made — the client record — not in the email thread where they were given. Email is where onboarding answers go to be lost; records are where they go to work. The ten minutes spent transcribing them is the cheapest insurance in the entire invoicing process, bought once and claimed on every invoice thereafter.

Turning answers into the client record

The question list's output is a record with fields: legal name; billing address; country; VAT identifier; size class (where phased); Peppol ID (where held); channel and route; specification (where any); payment terms; finance contact. Mark the record complete only when every applicable field is filled — the completeness gate that makes 'ready to invoice' a status rather than a hope. Monitored clients then keep the position fields (country, size) working over time as verdicts recompute.

Revisit the record on events, not on a schedule: the client merges, moves country, changes platform, or crosses a size threshold. Each event is a two-minute record update that prevents a class of invoice failures. Suppliers who run this discipline stop experiencing e-invoicing as a sequence of surprises — the questions were all asked, once, at the start, when asking was easy.

The onboarding questions in 5 groups

  1. Identity: legal billing name and full address exactly as registered — plus the VAT identifier, copied from their documents.
  2. Channel: 'How do you receive structured invoices?' — Peppol ID for network clients; platform/portal route for platform clients; preferred artefact for document-model clients.
  3. Position: for PL/DE/ES clients, which side of the mandate size threshold they sit on — and their phase date.
  4. Specification: any CIUS, profile or supplier guide to invoice against (CIUS-PT, XRechnung, Peppol BIS) — filed in the record.
  5. Commercials: payment terms and due-date convention, any PO/reference they need on invoices, and the finance contact who owns invoicing questions.

Worked example: one onboarding call, a year of clean invoices

A studio's onboarding call with a Belgian agency takes twelve minutes. Answers recorded: legal name and Brussels billing address; VAT identifier copied from the agency's own invoice footer; Peppol ID confirmed by their finance lead; channel — Peppol, via their access point; terms 30 days; finance contact named. The studio's record is marked complete the same day.

Twelve monthly invoices follow — EUR 2,400.00 reverse-charge conversions, validated, sent through Qvalia to the recorded Peppol ID — without a single invoicing email beyond the invoices themselves. The call's twelve minutes amortise to one minute per invoice and falling. Every supplier has this call available at the start of every relationship; the only question the mandate era asks is whether it happens before the first invoice or after the first rejection.

Frequently asked questions

What if the client doesn't know their Peppol ID or size class?

The question routes itself: ask who in finance would know, and record the answer when it comes. An unanswered field keeps the record 'incomplete' — a visible, chaseable state — instead of an invisible gap discovered by a rejection.

Isn't this a lot to ask a new client?

It is one short conversation or a one-page form, framed as logistics ('so our invoices book straight into your system'). Clients experience it as professionalism; finance teams in mandate countries answer these questions weekly.

Do I need to ask domestic clients too?

Yes — the same record serves future cross-border work, group changes and mandate formalisation. Complete records are a single standard, not a per-country improvisation.

What if a client's answers change?

Update the record on the event (merger, platform change, threshold crossed) and let monitored clients recompute the verdicts. Records are living documents with a change habit, not stone tablets.

Where should the answers live?

In the client record your invoicing actually uses — the same place conversions and monitored clients read from. Not in email, not in a notebook, not in one person's memory.

Keep going

Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides

Related guides

← Back