Skip to main content

Reports

The Reports page is the analytical view of NomaUBL — it turns the invoice, archive, lifecycle and validation data into figures a team can read and export, without writing SQL. It opens on two tabs: a ready-made Status statistics pivot and a build-your-own Query tool. The page is designed to host further report tabs over time.

Open it from the sidebar — Reports. Access is granted per role (see Access below).

At a glance​

ReportsStatus statisticsQuery toolArchive date ▾Export ExcelACTIVITY · STATUS · REASONB2BB2BINTB2CB2G▾ ISC1 2408640257▾ 205 Paid1 180 · 95%▸ 213 Rejected60 · 5%REJ_ADR — code adressage44 · 73%REJ_SIRET — SIRET inconnu16 · 27%▸ VRAC318—54—Rows expand / collapse · subtotals at every level · counts and % · one click to Excel (report + flat data)

Status statistics​

The first tab is a ready-made pivot: invoice counts broken down by activity code → status → rejection reason, and split into columns by transaction type (B2B, B2BINT, B2C, B2G). Every level carries its count and a percentage of its parent — a reason as a share of its status, a status as a share of its activity, an activity as a share of the whole.

  • Expand / collapse any activity or status to drill down; subtotals are shown at every level.
  • A status that has a single rejection reason renders as one compact line rather than an extra nested row.
  • The period filter at the top offers the same three date bases as the Dashboard — Activity date, Document date or Archive date — so the report reconciles with the figures shown elsewhere.
  • Export Excel writes a workbook with two sheets: the report exactly as displayed, and the flat underlying data ready for your own pivot tables.

Query tool​

The second tab builds an extraction without SQL. Pick a dataset, choose the columns, narrow with filters, run — and optionally save the result as a named report.

DatasetWhat it covers
InvoicesThe e-invoicing rows — the same catalog as the E-Invoicing list.
Archived documentsEvery captured document — the E-Documents archive.
Lifecycle eventsOne row per status event recorded on the invoice lifecycle.
Validation errorsThe Integration Errors findings.
  • Columns — pick which columns to include from the dataset's catalog.
  • Filters — status, reason, action and transaction-type filters use searchable multi-select pickers fed by the reference lists; dates use range pickers; the period bar with its date-basis toggle leads the screen. A document-number filter performs an exact numeric lookup.
  • Results land in the standard grid with all its tooling: search, per-column filters, grouping, column show / hide and reorder, and CSV / Excel export.

Saved reports​

A query — its dataset, columns, filters, column layout and grouping — can be saved as a named report and restored in two clicks. The report library lives in its own config-reports.json file, so it is easy to back up and to promote from one server to another.

Access​

The Reports page is gated per role: grant the Reports page in the Navigation group on the Roles page. Without it, the sidebar entry is hidden.

Tips & best practices​

  • Start from Status statistics for the recurring read. It answers "how many invoices, in which status, and why rejected" without any setup — export the two-sheet workbook when a colleague wants to pivot the raw figures.
  • Save the queries your team re-runs. A named report keeps its columns, filters and layout, so a monthly extraction is two clicks rather than a rebuild — and config-reports.json travels with a deployment.
  • Match the date basis to the question. Archive date answers "what did we process", Document date "what did we issue", Activity date "what changed" — pick the one the audience expects before reading the counts.