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 has five tabs: a ready-made Status statistics pivot, Integrity — SQL checks that list what is missing or wrong compared with a source system —, and three documents generated on demand, the Audit report, the Implementation report and the Technical report. Free analyses — any field, grouping, chart or dashboard — are built in the Explorer, which replaces the former query tool.

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

At a glance​

ReportsStatus statisticsIntegrityAudit reportImplementation reportTechnical reportArchive date ▾Export ExcelACTIVITY · STATUS · REASONB2BB2BINTB2CB2G▾ Stores1 2408640257▾ 205 Paid1 180 · 95%▸ 213 Rejected60 · 5%REJ_ADR — code adressage44 · 73%REJ_SIRET — SIRET inconnu16 · 27%▸ Central318—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.

  • Choose the grouping. Chips above the report pick which levels build it — activity, status, rejection reason — in any combination (e.g. statistics per status only). Expansion, percentages and the Excel export all follow the chosen grouping.
  • Choose the measure. The Measure switch counts invoices (Invoice count, the default) or sums their tax-exclusive amount (Net amount, BT-109). Cells, subtotals and percentages follow the measure — a handful of invoices can carry most of the money. The Excel export follows the view, and its data sheet carries both figures.
  • 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.
  • Exclude reviewed errors leaves out the invoices already reviewed by customer service that still sit in an error status — the same toggle as on the Dashboard; reviewed invoices in other statuses stay counted.
  • Export Excel writes a workbook with two sheets: the report exactly as displayed, and the flat underlying data ready for your own pivot tables.

Integrity​

The Integrity tab runs the SQL checks defined under Configuration → System → Integrity reports: pick a check, a period (last 30 days by default) and Run. Every row of the result is one anomaly, shown in the standard grid (search, filters, columns, export). A check that carries an action lets you tick rows and Integrate the selection — see Integrity reports for the full walkthrough.

Audit, implementation and technical reports​

These three tabs generate a document, in PDF or Markdown, rather than a grid:

TabDocumentPage
Audit reportThe activity of a period — volumes, situation, backlog, lifecycle, errors, operations and consistency checks — for an internal review or an auditor.Audit report
Implementation reportThe documentation of the instance as it runs — architecture, built-in rules, documents and UBL mappings, platform settings, operations, security — for a hand-over file or an upgrade snapshot.Implementation report
Technical reportThe developer documentation of the release — data model, flows, configuration reference, status model, API — identical on every instance.Technical report

All three are also available from the command line, to schedule them or keep them with a release.

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.
  • Build the recurring extractions in the Explorer. A saved analysis keeps its fields, filters and view, can go into a dashboard and be sent by daily digest.
  • 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.