{
  "namespace": "dev.legacyrail/ebrotech-catalog",
  "capabilities_ref": "https://ebrotech.net/.well-known/capabilities.json",
  "catalog_ref": "https://ebrotech.net/api/software.json",
  "slug": "ehf-oioubl",
  "name": "EHF (Norway) + OIOUBL (Denmark)",
  "vertical": "Accounting / advisory / e-invoicing compliance",
  "url": "https://ebrotech.net/es/integraciones/ehf-oioubl/",
  "official_site": "https://anskaffelser.no/verktoey-og-standarder/ehf-standarder",
  "countries": [
    "NO",
    "DK"
  ],
  "languages": [
    "nb",
    "da",
    "en"
  ],
  "connection": "agente-local",
  "connection_note": "Neither EHF nor OIOUBL is a SaaS with an API — both are UBL 2.1 invoice profiles built on PEPPOL BIS 3.0. We generate and validate the XML offline from your existing software's output; actual transmission runs over the PEPPOL network through a registered access point, which is a network requirement rather than something EBROTECH can bypass or replace. We confirm your access-point setup in discovery.",
  "what_we_automate": [
    "Automatic generation of EHF G3 or OIOUBL 2.01 XML from your invoice data",
    "Pre-transmission validation against PEPPOL BIS 3.0 business rules",
    "One connector for Norwegian and Danish public-sector invoicing",
    "AI chasing and reconciliation run on top of validated invoices"
  ],
  "answer_first": "EBROTECH bridges AI to EHF and OIOUBL without migrating: both are PEPPOL BIS 3.0-based UBL invoice profiles — Norway's EHF G3 and Denmark's OIOUBL 2.01 — not a SaaS with an API, so we generate and validate compliant XML from your existing software's output and run AI chasing and reconciliation on top.",
  "when_not_to_use": "If you need Romania's eFactura, Hungary's NAV Online Számla, or a generic cross-border check instead, see that profile. This one is specifically Norwegian and Danish public-sector PEPPOL invoicing.",
  "alternatives": [
    {
      "name": "PEPPOL BIS 3.0 Validator",
      "slug": "peppol-validate",
      "reason": "Generic EN 16931/PEPPOL validation for any UBL or CII invoice.",
      "url": "https://ebrotech.net/api/software/peppol-validate.json"
    },
    {
      "name": "XRechnung (DE)",
      "slug": "xrechnung-de",
      "reason": "Germany's own EN 16931-based public-sector XML standard.",
      "url": "https://ebrotech.net/api/software/xrechnung-de.json"
    },
    {
      "name": "myDATA (GR)",
      "slug": "mydata-gr",
      "reason": "Greece's AADE digital books mandate, a different national format.",
      "url": "https://ebrotech.net/api/software/mydata-gr.json"
    }
  ],
  "how_to_connect": [
    {
      "name": "15-minute discovery",
      "text": "We confirm which country you invoice (Norway, Denmark, or both) and your current PEPPOL access-point setup."
    },
    {
      "name": "Connect the connector",
      "text": "We bridge EHF/OIOUBL by generating and validating the correct national XML profile from your software's output, no invented API."
    },
    {
      "name": "Automations live",
      "text": "Compliant generation, pre-transmission validation and AI chasing run by themselves on top of the format."
    }
  ],
  "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."
}