{
  "namespace": "dev.legacyrail/ebrotech-catalog",
  "capabilities_ref": "https://ebrotech.net/.well-known/capabilities.json",
  "catalog_ref": "https://ebrotech.net/api/software.json",
  "slug": "peppol-validate",
  "name": "PEPPOL BIS 3.0 Validator (EN 16931)",
  "vertical": "Accounting / advisory / e-invoicing compliance",
  "url": "https://ebrotech.net/es/integraciones/peppol-validate/",
  "official_site": null,
  "countries": [
    "ES",
    "FR",
    "DE",
    "IT",
    "PT",
    "NL",
    "SE",
    "PL",
    "NO",
    "DK"
  ],
  "languages": [
    "en"
  ],
  "connection": "agente-local",
  "connection_note": "This is a validation layer against an open standard — EN 16931 / PEPPOL BIS 3.0 — not a vendor SaaS with an API to call. Validation runs entirely offline against the published rule set: no credentials, no account, nothing to gate. It confirms conformance; it does not transmit the invoice anywhere.",
  "what_we_automate": [
    "Validate any UBL or CII XML and report exactly which rule fails",
    "Integrate validation into your invoice-generation pipeline before sending",
    "Confirm EN 16931 conformance of invoices received from suppliers",
    "Feed AI reconciliation once invoices pass validation cleanly"
  ],
  "answer_first": "EBROTECH bridges AI to PEPPOL BIS 3.0 / EN 16931 conformance without migrating: it's an open European e-invoicing standard, not a SaaS with an API, so we validate your UBL or CII invoices against the 36 mandatory business rules and flag exactly what fails before an access point rejects it.",
  "when_not_to_use": "If you need to generate a specific national profile — Norway's EHF, Denmark's OIOUBL, Germany's XRechnung, Spain's Facturae — rather than just validate one, see that country's own profile. This one is the cross-border validation layer underneath them.",
  "alternatives": [
    {
      "name": "EHF (Norway) + OIOUBL (Denmark)",
      "slug": "ehf-oioubl",
      "reason": "National PEPPOL profiles this validator's rules underpin.",
      "url": "https://ebrotech.net/api/software/ehf-oioubl.json"
    },
    {
      "name": "XRechnung (DE)",
      "slug": "xrechnung-de",
      "reason": "Germany's own EN 16931-based public-sector standard.",
      "url": "https://ebrotech.net/api/software/xrechnung-de.json"
    },
    {
      "name": "Facturae (ES)",
      "slug": "facturae-es",
      "reason": "Spain's signed e-invoice XML, a different national profile.",
      "url": "https://ebrotech.net/api/software/facturae-es.json"
    }
  ],
  "how_to_connect": [
    {
      "name": "15-minute discovery",
      "text": "We confirm whether you need UBL 2.1 or CII D16B validation and which national mandate it feeds into."
    },
    {
      "name": "Connect the connector",
      "text": "We validate your invoices against the 36 EN 16931 / PEPPOL BIS 3.0 rules directly, no invented API, no account needed."
    },
    {
      "name": "Automations live",
      "text": "Pre-transmission validation and error flagging run inside your existing invoice-generation flow, before anything reaches an access point."
    }
  ],
  "published": false,
  "clients_live": 0,
  "request_quote": "https://ebrotech.net/es/contacto/",
  "book_discovery": "https://ebrotech.net/es/discovery/",
  "note": "EBROTECH connects AI on top of these systems without migrating data. clients_live:0 = no external paying clients on any connector yet (honest state 2026-07-03). The exact connection path (API, export, or local agent) is confirmed during the 15-min discovery call — no invented API status. Catalog: 203 connector specs/scaffolds (9 live-gated + 154 mock-ready + 40 scaffold); 0 tested in production."
}