Skip to main content

E-Directory

The E-Directory editor configures two complementary services NomaUBL uses to validate recipient information before producing an e-invoice:

  • PPF (Portail Public de Facturation) directory — verifies that the electronic addressing code carried by the document exists and is active in the public e-invoicing directory.
  • INSEE company search — looks up a company by business name, SIREN or SIRET to retrieve its official identification data (legal name, address, registration status…).

The two are typically chained: an INSEE search resolves the customer's identifiers, then the PPF directory check confirms that the addressing code on the document is valid for that customer.

The page applies regardless of source system — JD Edwards, SAP, NetSuite or a custom ERP — once the source is mapped to UBL.

The editor has two tabs:

  1. Directory — Enable Check toggle and INSEE search settings.
  2. Connector — pick the api-connector that holds the PPF transport, plus per-task endpoint name overrides.

Opening the editor​

  • Settings → e-directory template (the system-level resource).

At a glance​

DirectoryConnectorAPI connectorThe PPF directory's HTTP transport — auth, base URL, endpoints — lives in a reusable api-connector.CONNECTORppf-directory ▾edit under API ConnectorsPer-lookup endpoint overridesEndpoint name on ppf-directory for each lookup. Defaults shown apply when blank.Directory check | directory-checkDirectory check (SIREN) | directory-check-sirenDirectory check (SIRET) | directory-check-siretDirectory tab — previewENABLE CHECKY ▾queries the PPF before each invoiceINSEE SearchRESULTS PER PAGE10number of results per INSEE searchReusable api-connectorno inline auth or endpointsPer-lookup overridesSIREN-only / SIRET / genericEnable checkPPF directory query before sendINSEE Searchcompany lookup by SIREN/SIRET

Tab 1 — Directory​

Directory Check​

FieldValuesDescription
Enable CheckY / NWhen enabled, NomaUBL queries the PPF directory before sending each invoice to verify that the electronic addressing code on the document exists and is active in the public directory. Disable to skip the verification (useful for testing).
Recipient not foundWarn and send (default) / Block the send — invoice stops at validation failedWhat happens when the check does not find the recipient. Warn: the miss is recorded as a warning finding DIRECTORY_CHECK and the invoice is sent. Block: on an invoice meant for the platform, a definitive answer — not registered, or found but not reachable — or a missing electronic address (EndpointID) is a fatal finding; the invoice stops at validation failed (9905) and is not sent. A connector or network error only warns in both modes, and invoices configured not to be sent are never blocked.
FieldDefaultDescription
Results per page10Maximum number of results returned per INSEE search query. Increase to widen each result page; decrease to limit network payloads.

Peppol lookup​

Settings for the Peppol lookup of the E-Directory page, for servers on restricted networks (see Network flows).

FieldDefaultDescription
Resolve platform via SMPYY reads the provider's name and seat from its SMP certificate — HTTPS to each provider's SMP host. N stops at the SML answer: the Plateforme column shows the SMP host (e.g. smp.pennylane.com), with no call to wait for. Set N when the network does not allow HTTPS to the providers' SMP hosts.
Public DNS fallbackNN uses the server's resolver only. Y retries the SML lookups through 8.8.8.8 / 1.1.1.1 when that resolver gives no answer. Keep N when the network forbids external resolvers.

Tab 2 — Connector​

The PPF directory's HTTP transport — authentication flow, base URL, endpoints — lives in a reusable api-connector. This page references it by name only and never carries auth fields or HTTP endpoints inline. The bundled ppf-directory connector covers the standard flow; pick a custom connector when the directory exposes non-standard auth or routes through a tenant gateway.

API connector​

FieldDescription
ConnectorDropdown listing every api-connector template. The selected connector holds the directory's baseUrl, authType, credentials, token endpoint and the catalogue of HTTP endpoints. Edit the connector itself under API Connectors.

Per-lookup endpoint overrides​

When the api-connector exposes endpoint names different from the defaults, set an override below. Leave a field blank to use the default name shown.

FieldDefaultUsed by
Directory checkdirectory-checkThe generic directory check (when the document already carries the routing identifier).
Directory check (SIREN)directory-check-sirenLookup branch when only a SIREN is known.
Directory check (SIRET)directory-check-siretLookup branch when a SIRET is known.

Tips & best practices​

  • Keep Enable Check on in production. Sending an invoice with an inactive or unknown addressing code leads to a downstream rejection by the receiving Plateforme Agréée.
  • Use INSEE search to bootstrap customer records. A lookup by SIREN / SIRET avoids transcription mistakes and aligns NomaUBL's data with the official registry.
  • Edit timeouts and TLS settings on the api-connector itself. The HTTP-level parameters live on the API Connectors page, not here — same connector can serve several pages, so the timeout and SSL Verify flag are set once.
  • Never disable SSL Verify in production. It opens you to man-in-the-middle interception of credentials and document metadata. Set it on the api-connector, not here.
  • The PPF connector is bundled. A fresh installation already ships a ppf-directory connector pointing at the standard endpoints — pick it from the dropdown and you are done. Custom connectors are only needed for non-standard transports.