Agencies, consultants and 3PLs · read this before you commit a client

Agency accounts don't exist yet.

Here is exactly what does.

You run compliance for other people's companies. V1 has no multi-client account and no grouped invoice — one workspace per client company is what there is. Each company can invite named Owners and Members, but one agency login still cannot switch across clients. You would find that out in an hour anyway, so here is the whole picture first.

Ask an expert Check my scope

Free. No card. A person answers.

A dotted cell means not built, with no date attached to it. It describes today, not an announcement.

What you can hand over

What you can delegate is the filing. Not the account structure.

The work itself is the same one a seller buys, at the same published price: €299 a year per country, per client company, before scheme and authority fees. We run a local entry point in 10 of the twenty-seven member states, and we say which streams we hold a documented source for rather than implying all of them.

  • Your registration prepared and submitted, for every stream you owe in that country
  • A written scope before anything is charged
  • The annual declaration, prepared and filed on that country’s calendar
  • Resubmission at no extra fee on a file we prepared
  • A person on the file when the register comes back
  • The dashboard, with the dates that follow

The country you cannot cover yourself is the one worth sending. See which 10 we run

The gap, in full

One account per client. Workable at three. Painful at twenty.

There is no way today to hold several client companies under one login and no single invoice across them. Each client is a separate workspace with its own named Owners and Members, quote and payment link. Here is each missing piece and what you do instead.

  1. No multi-client account

    You cannot switch between client companies from one login.

    Instead: one account per client company, created with the address you decide on. It works, and it does not scale past a handful.

  2. No cross-client permissions

    An agency administrator cannot grant one colleague access to clients A and C from a shared agency console.

    Instead: each client company invites named Owners or Members to its own workspace. Credentials are never shared, actions are auditable, but switching clients still requires separate accounts.

  3. No grouped invoicing

    There is no single invoice across your clients, and no consolidated view of what is owed.

    Instead: one written quote and one payment link per client company. Each names its countries line by line, so a client can drop one before paying.

  4. No online payment, no quote engine

    Nothing is charged in the product. There is no checkout to hand a client.

    Instead: a person writes the quote and sends the link. That is a real constraint on volume, and it is also why nothing is charged before a file has been read.

  5. No API, no automated filing

    You cannot push a client's data in, and files are not submitted to registers by machine.

    Instead: people prepare and submit each file. Several national portals have no interface to automate against, which is the reason rather than the excuse.

What is true at any number of clients: the producer number is issued by the register in your client's name. It is theirs, it does not sit with us, and it does not stop working if either of you leaves.

The question you actually have

We talk to whoever holds the account. Decide that before you open one.

You want to know whether we will go around you. The honest answer is mechanical rather than reassuring, and it is the only one the product can give today.

V1 has no notion of an agency parent account. There is one client company workspace with named Owners and Members.

Quotes, payment links and status updates live in that workspace. Immediate and digest emails follow each member's notification preferences. The software does not infer which member is the agency and which is the producer.

Anything beyond that is a commercial arrangement, not a feature. It belongs in writing between us before you commit a client — not on a marketing page, where we could write whatever reads best.

When multi-client gets built

The trigger is agencies asking. Not a date on a roadmap.

A company switcher, cross-client permissions and grouped billing are a separate product. The Owner/Member roles already delivered remain scoped to one client company.

  • It gets built when agencies accumulate

    Not in anticipation. The number of client companies you would put behind one login is the figure that decides it, and we would rather have yours than an estimate.

  • No date is attached to it

    We do not put dates on things we have not started. That rule is why the coverage page lists the member states we do not run with no opening date against any of them, and it applies to the product as much as to the map.

  • The data model already allows for it

    A company is modelled separately from a user, with a table between them. That is the multi-client account made possible without being shipped — it is not the same as it existing, and this page will say so until it does.

Tell us how many clients you would put on one login.

That number is the one that decides when multi-client gets built, and it is more useful to us than a form field. Write to a person, say what you run today and which countries you cannot cover, and you will get a straight answer about what fits and what does not.

Ask an expert Check my scope

Free. No card. A person answers.

The address is [email protected], in plain text, because a page that tells you what it does not have should not hide behind a form.

The countries named on this page come from published guidance. Last source review: 14–27 August 2026. Rules change — the scope check is reviewed by a person before any quote.