Sign inGet started

What's covered vs deferred

An honest map of the e-invoicing boundary. TaxLens produces a conformance-validated EN 16931 document and serializes it to UBL 2.1 / PEPPOL BIS 3.0 today. Government transmission, national clearance formats, and live VAT-ID checks are deliberately deferred — here's exactly where the line is.

What's produced today

From a booking, TaxLens generates and validates:

  • EN 16931 semantic document — the country-agnostic invoice model, with a built-in pre-check for the mandatory Business Terms and per-rate reconciliation.
  • UBL 2.1 / PEPPOL BIS Billing 3.0 XML — structurally correct by construction. The runtime gate is the mandatory EN 16931 / PEPPOL pre-check; XSD conformance is verified in our test suite, not validated at request time.
  • Multiple VAT rates and multi-line folios (room + fees) — see Multi-rate VAT invoices.
  • EU cross-border B2B reverse charge (category AE) on the OTA commission line — see Reverse charge.
  • Fiscal issuance with gapless numbering, credit notes (381), and self-billed invoices (389), all immutable — see Fiscal numbering & immutability.
  • Tax-inclusive pricing and multi-currency settlement — see Inclusive pricing & currency.
Markets served directly today
Where EN 16931 / PEPPOL BIS 3.0 is itself the accepted format — Belgium, Germany, and the PEPPOL-aligned markets (Singapore, Australia/NZ, Japan, UK) — our output is the right document. Those need a PEPPOL Access Point to transmit, which is the roadmap, not a different format.

What's not built yet

Each of these is a deliberate, clean follow-up — not a hidden limitation:

  • Clearance & transmission. Delivering the invoice over the PEPPOL network (an Access Point) or to a government clearance platform (Italy's SdI, Poland's KSeF, etc.) is not built. TaxLens makes the document; it does not yet send it or capture a clearance acknowledgement.
  • Full PEPPOL Schematron / code-list validation. The pre-check covers the mandatory structure and business rules, but not the complete XSLT2 PEPPOL Schematron and full code lists. A green pre-check is strong, but not a guarantee an Access Point accepts.
  • National clearance formats. FatturaPA (Italy), Factur-X / Chorus PPF (France), KSeF FA(3) (Poland), VeriFactu / Facturae (Spain), CFDI (Mexico), IRN / MyInvois (India/Malaysia), ZATCA (Saudi Arabia), NF-e (Brazil) — these national schemas with government clearance are roadmap, reusing the same canonical document.
  • Live VAT-ID validation (VIES). Reverse charge currently trusts the caller-supplied VAT id structurally; live VIES lookups are deferred.
  • Digital signatures, PDF / Factur-X, QR codes, and the TOMS margin scheme.
Plan for the boundary
If you operate in a clearance country (IT, FR, PL, ES, SA, IN, MX, BR), treat the TaxLens UBL as the validated source document and pair it with a certified transmitter / format converter until the national format and transmission land. See Limitations.

See what you've issued

The issued-document list is read-only and live. Run it to see your organization's invoices, credit notes, and self-billed documents — each with its fiscal number, type, and status:

GET/v1/invoices
Sign in to run

Lists issued fiscal documents for your active organization (read-only).

Sign in to run this against the live API. Read-only — nothing is saved.

Browse the same data with filters in the Invoices dashboard, and read the full API in E-invoicing (API).

Next

For the broader product boundary and open questions, see Limitations and FAQ. To revisit how the pieces fit together, start at The invoice lifecycle.

PreviousFiscal numbering & immutabilityNext Hotels & hotel groups