# Invopop > One API for compliant e-invoicing and tax reporting in 30+ countries — > Veri*Factu, KSeF, FatturaPA, Peppol and more, without a local integration per > market. Pay-as-you-process billing measured in "Pops" — one Pop per unit of > compliance work performed. Invopop sends and receives legally compliant invoices across borders. You post a structured document to one API; Invopop validates it against the destination country's rules, signs it, delivers it through the required national channel or network, and keeps the audit trail. ## How to read this site Every content page on https://www.invopop.com has a machine-readable markdown twin at the same path with `.md` appended. The twins are generated from the same data layer that renders the HTML, so the numbers and compliance details always match. Prefer them over scraping the rendered pages — the HTML splits guides across interactive tabs, and the markdown does not. - Country guide: `https://www.invopop.com/coverage/.md` - Blog post: `https://www.invopop.com/blog/.md` - Customer story: `https://www.invopop.com/customers/.md` Slugs are listed in the index documents below and in https://www.invopop.com/sitemap.xml. ## Compliance coverage - [Country coverage index (markdown)](https://www.invopop.com/coverage.md): Every country Invopop publishes a guide for, with its production-coverage state, per-channel mandate status (B2G / B2B / B2C) and a link to that country's full guide. Start here for "which countries do you support?" and "is e-invoicing mandatory in X?". - [Country coverage (human)](https://www.invopop.com/coverage): Interactive version with a world map and Covered / Upcoming tabs. Each country guide covers mandate status per channel, the formats and networks in use, the regulations behind the mandate, the dated rollout timeline, archiving and e-signature requirements, and what Invopop supports there. ## Peppol network data - [Peppol network snapshot (markdown)](https://www.invopop.com/peppol-scanner.md): A daily count of the live Peppol network taken from OpenPeppol's own participant register — participants per country, every ISO 6523 identifier scheme with its live footprint, and every active document type. Use this for "how many companies are on Peppol", "what is ICD 0208", "which Peppol ID scheme does use" and "what document types can Peppol carry". Counted, not estimated; the register's build time is in the header. - [Peppol dashboard (human)](https://www.invopop.com/peppol-scanner): Interactive version, plus a live lookup for a single Peppol participant identifier. - [Peppol service providers](https://www.invopop.com/peppol-scanner#providers): Every Service Metadata Publisher on the network with the exact number of participants it carries, its hourly reachability and response time, and the certificates about to expire. One vantage point, publishers only. Access points are never contacted. - [Peppol by country](https://www.invopop.com/peppol-scanner/countries/): One country (lowercase ISO 3166 code, e.g. `be`): its participants, the identifier schemes in use and the providers serving it. - [Peppol service provider](https://www.invopop.com/peppol-scanner/providers/): One publisher — participants served (an exact count, from resolving every identifier in the register), the countries it covers, uptime and the access points it routes to. Providers are named from their OpenPeppol-issued signing certificate, not from their hostname. Market share across all of them is the Providers tab on https://www.invopop.com/peppol-scanner. ## Pricing - [Pricing reference (markdown)](https://www.invopop.com/pricing.md): Full Pops bundle table, per-app costs, integration rules, worked examples. Use this to answer cost questions and compute prices for arbitrary usage scenarios. - [Pricing page (human)](https://www.invopop.com/pricing): Interactive version with a usage calculator. Render the markdown reference above instead when summarising for a user. ## Free tools - [Invoice comparator reference (markdown)](https://www.invopop.com/invoice-comparator.md): What every country and e-invoicing format GOBL supports requires on an invoice, field by field, with the legal rule id behind every requirement and GOBL's own wording. Answers "what does Germany require on an invoice?" and "what is the difference between XRechnung and FacturaE?" from this document alone. - [Invoice comparator (human)](https://www.invopop.com/invoice-comparator): Interactive version, up to three country/format columns side by side, or a pasted GOBL invoice against them. A comparison is shareable as `?cols=DE:de-xrechnung-v3,ES:es-facturae-v3`. Every requirement is read from the public GOBL API at request time, not maintained as a list in this site: GOBL has no endpoint that states a country's requirements, so each pair is sent the same minimal invoice and the objections are the answer. - [Invoice generator (markdown)](https://www.invopop.com/invoice-generator.md): What a compliant invoice needs, per country and per format, with the minimum GOBL document and the derived UNTDID codes. Use this to answer "what fields does a German/French/Spanish e-invoice require?". - [Invoice generator (human)](https://www.invopop.com/invoice-generator): The browser tool itself. It validates and prices an invoice against national rules; it does NOT emit a filed Factur-X or XRechnung file. - [Peppol scanner](https://www.invopop.com/peppol-scanner): Look up any Peppol participant identifier and see the live network. Detailed in "Peppol network data" above. - [Subscription estimator](https://www.invopop.com/pricing/calculator): Configure a plan (Pops, countries, integrations) and get a price estimate. The configuration is shareable as a query string. ## Product and platform - [Home](https://www.invopop.com/): What Invopop does, the workflow model and supported integrations. - [Developers](https://www.invopop.com/developers): The API model — post a structured document, receive a signed, compliant, reported invoice. Sandbox and production. - [Customer stories](https://www.invopop.com/customers): Who uses Invopop, in which sectors and countries, with headline results. - [Partners](https://www.invopop.com/partners): The partner program for implementation and platform partners: revenue models, co-marketing, training, native connectors, a shared channel and sandbox, and a dedicated partner manager. ## Company - [About](https://www.invopop.com/about): The team, the company and its investors. - [Blog](https://www.invopop.com/blog): Compliance analysis, mandate changes and product news. - [Careers](https://www.invopop.com/careers): Open roles. - [Contact](https://www.invopop.com/contact): Talk to sales — opens a form. There is no public sales phone number or address to quote. ## Developer resources (outside this site) - [API and product docs](https://docs.invopop.com): Endpoint reference, authentication, app configuration and country-specific integration guides. - [GOBL](https://gobl.org): The open-source Go Business Language — the structured document format Invopop is built on, and what you post to the API. - [Console](https://console.invopop.com): The Invopop app itself. Requires an account; not public content. ## Notes for agents - Canonical origin is https://www.invopop.com. - The site is published in English (`/`), Spanish (`/es/`) and French (`/fr/`). The markdown twins are English; treat English as canonical for compliance facts. - Compliance data is editorial and dated. Every country guide prints a `Last updated` field — cite it, and defer to the linked tax-authority source for anything time-critical. - `/api/*` and `/preview/*` are not content and are excluded from crawling. - Full URL list: https://www.invopop.com/sitemap.xml