Noma UBL
E-invoicing

Look a customer up in the INSEE registry by name, SIREN or SIRET and check that it is reachable on the PPF directory (annuaire, the public e-invoicing directory). When enabled, the addressing code of each invoice is checked before it is sent — with a warning, or by blocking the send when the recipient is not found.

Technical rejections (owned by IT) and business refusals (owned by customer services) are counted separately on the dashboard, each opening its filtered list. On an addressing rejection — ADR_ERR, REJ_ADR, DEST_INC — Fix buyer corrects SIREN, SIRET, VAT number or electronic address, revalidates on the spot and resends to the PA.

A form laid out like a printed invoice creates a new invoice from scratch, or edits or copies an existing one; NomaUBL produces the UBL on save.

The archived source spool and the generated UBL side by side, for every captured document. Every submission, rejection and fix is a dated entry in the append-only history.

Notification rules fire on a status or rejection reason and can run a chain of SQL or API connector calls — on JD Edwards or any other ERP — alongside the e-mail and portal alert. Seller actions are wired the same way.

Every invoice of the period aggregated on the lines of the French CA3 form — sales / purchases × France / intra-EU / outside EU × VAT rate — with drill-down to the invoices, and Excel or CA3-formatted PDF export. Invoices refused by the buyer (210) or rejected by the platform (213) are left out by default, as they call for a credit note.

The XSL editor maps source fields to UBL business terms (BT codes) through a form. AI Auto-Map proposes a mapping from a sample XML (and optionally its PDF); you review it and save.

When the source is missing data the invoice needs — a customer’s VAT number, a label from a reference table — enrichment rules fetch it through a SQL or API connector before the UBL is generated.

Roles grant pages, actions and a data scope — the companies a role is restricted to, plus row filters. Single sign-on through OIDC (Microsoft Entra, Okta, Keycloak, Google Workspace…).

Revenue excl. VAT net of credit notes, VAT, number of invoices and the transmission rate, each compared with the matching earlier period; twelve months of amounts by state; what needs a decision, in amounts; the split per company and transaction type and, for sales, the last e-reporting declaration and the next one due. Sales or purchases, exported as PDF.

Five stages — to correct, decision needed, processing, at the platform, completed — with their counts and change; open invoices by waiting time; the most frequent reasons; the detail by activity, status and reason per transaction type. Every figure opens the invoices behind it; Excel and PDF exports.

Pick fields from invoices, archived documents, lifecycle events, validation findings, lines, VAT breakdown and notifications; show them as a table, a pivot with subtotals and shares, or a chart. Calculated fields such as the age of an invoice; every cell opens the rows behind it.

Ready-made analyses and dashboards for Operations, Month end and Audit period, copied and adapted with Save as, shared with everyone or kept private. Exported to Excel or PDF, and sent by e-mail on a schedule by a daily digest.

The audit report explains a period to accounting and auditors; the implementation report documents your instance from its configuration; the technical report documents the release. PDF or Markdown, in French or English.

Integration errors, processing log, failures and server log in one Diagnostics page. The Failures view lists validation findings, PA rejections, send and import failures, processing and job failures with one shape — unresolved only by default — and opens the invoice, file or job behind each row.

An invoice that failed validation can be reprocessed in full from its archived source once the data is corrected in the ERP: enrichment queried again, UBL regenerated, validated and sent. The status history is kept; bulk reprocess runs as one background batch.

EN 16931 basic, EN 16931 or France extended (CTC): each document chooses its rule set, which drives the required UBL fields, the validation packs, the XSL editor mapping and the reference pages.

UBL stays the pivot: the validated UBL can be converted to CII D16B with the shipped stylesheet, or to a national format with your own, then downloaded from the invoice window or sent through the platform connector.

The e-directory finds a company in INSEE, its PPF directory lines and its Peppol participants. The same search is available as a REST endpoint for your other systems.

E-invoicing and e-reporting settings can be defined per company — issuer, frequency, PA connection — on top of a shared default, and roles restrict each user to their companies.

Move configuration from test to production item by item — templates with their XSL, RTF and Schematron files, PDF templates, rules, connectors — with a preview, a field-by-field diff and a version snapshot before every write.

A JDE SQL connector comes with prebuilt queries: user-defined code values to fill a list, the companies with their names, and putting an invoice’s receivable lines on hold to stop dunning letters from an invoice action. Schemas are placeholders, so the same query runs on every JDE environment.

Every scheduled job run is recorded with its duration and outcome, behind a History action. A retention job bounds the logs and histories per store, with a count-only dry run before anything is deleted.