Legal issuers & tax registrations

A legal issuer is the legal entity whose name goes on your invoices as the seller. Configure it once, register its tax IDs, and TaxLens uses it to issue compliant fiscal documents.

What a legal issuer is

When TaxLens issues an invoice, that document must name a seller — a real legal entity with a legal name, a registered address, and a tax identity. That entity is a legal issuer. It's the party that appears as the supplier on the EN 16931 invoice and that owns the gapless fiscal numbering sequence the document draws from.

Most hotels and property managers have one issuer (the operating company). You can create several — for example a different legal entity per country or per brand — and choose which one issues each invoice. A separate supplier issuer represents the host/owner party for self-billed (389) invoices, where a platform issues in the supplier's name.

Note

A legal issuer is org-scoped: it belongs to your organization and is never shared with others. Tax registrations scope through their issuer.

Creating a legal issuer

1
Open organization settings as an admin
Legal issuers live in Settings, under the organization's legal configuration. Creating and editing issuers is organization-admin gated.
2
Add the issuer's identity
Provide the entity's legal details:
3
Save
The issuer is created active. You can edit it later, add tax registrations, and set it as a default.

Field	Type	Description
legal_namerequired	string	The entity's registered legal name — the seller name on the invoice.
country_coderequired	string (ISO 3166)	The issuer's country, e.g. ES, FR, US.
trading_name	string	An optional brand / trading name shown alongside the legal name.
registered_address	object	The issuer's registered address (street, city, postal code, country).
default_currency	string (ISO 4217)	Optional default invoicing currency for this issuer.
eas_endpoint_id / eas_scheme_code	string	Optional electronic-address routing identifiers used for PEPPOL delivery.

Issuance is a fiscal action

Because issued invoices are immutable legal records, configuring the issuers that produce them — and running issuance itself — is restricted to organization admins. Members can't create or edit issuers.

Adding tax registrations

A legal issuer carries one or more tax registrations — the tax identities it invoices under. The most common is a VAT registration, but the same shape holds other scheme types (GST, etc.). Each registration records the scheme, the country it was issued in, and the identifier value.

Field	Type	Description
schemerequired	string	The registration type, e.g. "VAT".
valuerequired	string	The registration number itself, e.g. the VAT identifier.
country_coderequired	string (ISO 3166)	The country that issued the registration.
scheme_icd / valid_from / valid_to	string	Optional scheme identifier code and a validity window for the registration.

Detail

A correct VAT registration on the issuer is what lets TaxLens render the seller's VAT ID on the invoice. For cross-border B2B scenarios, also see Reverse charge — there the buyer's VAT identity matters, supplied per calculation.

Org default and per-property defaults

You don't want to specify an issuer on every single booking, so TaxLens resolves a default in two layers:

Organization default issuer. Set a default_legal_issuer_id on the organization's legal profile. If a booking doesn't name an issuer, this one is used.
Per-property defaults. A managed property can carry its own default_legal_issuer_id (the seller) and default_supplier_legal_issuer_id (the host/owner for self-billing). When a booking references that property, its issuer defaults fill in before the org-level fallback.

So the resolution order for a booking is: explicit issuer on the booking → the property's issuer default → the organization default. Setting or changing a non-null property issuer default is fiscal configuration and is org-admin gated.

Note

Changing a default affects future documents only. Already-issued invoices freeze the seller party they were issued with and never change retroactively.

Next, configure where you operate in Create your first property, or read the full issuance flow in the invoice lifecycle.

From the API

The legal-issuer family lives under /v1/legal-issuers. Reads are reachable with an API key, so you can fetch the issuers and tax registrations an integration needs before issuing:

GET /v1/legal-issuers — list your organization's issuers (pass include_inactive=true to include soft-deleted ones).
GET /v1/legal-issuers/{id} — fetch a single issuer.
GET /v1/legal-issuers/{id}/tax-registrations — list that issuer's tax registrations.

Provisioning is dashboard / interactive-session only

Creating, updating, and deleting issuers and their tax registrations (POST /v1/legal-issuers, PATCH /v1/legal-issuers/{id}, DELETE /v1/legal-issuers/{id}, and the POST / DELETE tax-registration sub-resources) require an interactive organization-admin session — they reject API-key authentication with a 403. Provision issuers from the dashboard, then reference them by ID over the API.

Full request and response shapes are in the API Reference under E-invoicing.