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. A row of four cards picks the report, each saying what it is for; the page opens on the first one, Integrity — SQL checks that list what is missing or wrong compared with a source system. The three others generate a document on demand: the Audit report, the Implementation report and the Technical report. The status statistics are on the Statistics dashboard; free analyses — any field, grouping, chart or dashboard — are built in the Explorer.

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

At a glance​

ReportsIntegrityCompare with JDE, integrateAudit reportKey figures of a periodImplementation reportHow this instance worksTechnical reportDeveloper documentationChecksInvoices missing in NomaUBLmissing in the target · jde-sql · can integrateAmount differencesdifferences · jde-sqlStuck invoicesdirect query · db-nomaublInvoices missing in NomaUBLShow SQL📅 1 – 31 Oct 2026 ▾Run3 anomaly(ies)1 248 source / 1 245 target · 640 msCOMPANYDOCDCTAMOUNTJOB☑0000110871RI1 200,00482211☑0000110872RI540,00482211☐0000220114RI2 980,00482260Integrate selection (2)Opens on Integrityfirst of the four cardsChecks listmode · connector · actionDefined in SettingsIntegrity reportsPeriod + Rundefault period of the viewResult bannercount, source / target, timeIntegratechecks with an action

Integrity​

The Integrity card lists on the left the SQL checks defined under Configuration → System → Integrity reports— each with its description, mode (missing in the target, differences or direct query), connector and can integrate when it carries an action. Pick a check, a period (the default period of the Reports › Integrity view) and Run. A banner gives the outcome — No anomaly or the count of anomalies, the source and target counts and the duration — and Show SQL unfolds the queries. 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 cards generate a document, in PDF or Markdown, rather than a grid:

CardDocumentPage
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​

  • Run the integrity checks after each night batch. A clean result means NomaUBL holds everything the source system invoiced; set Reports › Integrity to Yesterday under Default periods to make it the opening period.
  • Read the status statistics on the Statistics dashboard. It holds the detail table by activity, status and reason, compared with the previous period.
  • 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.
  • Keep the reports with the release. The implementation and technical reports describe the instance and the release as they are; generate them after an upgrade and file them with the hand-over documents.