Run reports and download evidence
Use the E-invoicing reports to reconcile invoices to submissions, find open rejections, and prove what was sent.
Before you begin
- Reports are under E-invoicing > Reports. All except Event log need only
einvoicing.view. Event log needseinvoicing.audit. - Dates default to the current month. Reports with a period have From and To fields. Every report can be exported to CSV.
The reports
| Report | Answers |
|---|---|
| Submission monitor (R040) | One row per e-invoice with its latest state. Totals show semantic documents (superseded excluded), attempts and a count per state |
| Reject analysis | Rejections and validation failures grouped by origin, code, field and profile version, with open counts and the age of the oldest |
| Unknown and deadline queue | Everything still owed an answer, with age, deadline and whether it is at risk. No date filter |
| Invoice-to-provider bridge | Every posted or reversed invoice and credit note against its submissions and attempts |
| Credential health | Expiry and last health check of every credential. Never the secret |
| Archive integrity | Every stored payload's hash recomputed from its bytes, with the retention policies |
| Event log | Accepted, rejected, status-unknown and inbound-validated events and when they were published |
Reconcile invoices to submissions
- Open Invoice-to-provider bridge and set the period.
- Check that each posted invoice and credit note appears once, with its total, submission count and attempts.
- Look at the Flag column. Missing means a posted invoice has no submission, for example one posted before E-invoicing was on. Duplicate identity means two live submissions share an invoice and profile and should never happen.
- Compare the totals with Sales: invoice value, semantic submissions, attempts, missing and duplicates.
One invoice has one semantic submission. Retries are attempts, never counted as more invoices. A reversed unsent invoice shows as superseded.
A "missing" flag cannot be fixed from this report, and there is no button to hand an older invoice over. The system interface can do it; ask your administrator.
Download evidence
- Open a submission and go to Payloads.
- Click Download on a row (request, response, callback, inbound or rendering). The file is named
<kind>-<id>.xml. - Compute the SHA-256 of the file and compare it with the value on screen and in the download's header. They are equal.
Downloading needs einvoicing.operate or einvoicing.audit. A user with only view access sees the table but no button: "Downloading e-invoice evidence needs the auditor or operator role."
For an Issued submission click Issued rendering with QR for an HTML page of the seller, buyer, lines, totals, QR, e-invoice number, legal state, UUID and payload hash. It is made once and reused. The same submission can also be produced as a PDF/A-3 with the XML embedded. An invoice that has not been legally issued has no rendering: "Only an invoice that has been legally issued has an issued rendering."
What happens next
Nothing is changed by reports. Archive integrity turns red if a stored payload no longer matches its hash, which is the signal to call your administrator.
Good to know
- Events carry ids and hashes, never payloads or secrets.
- Retention policies are records only; no automatic deletion exists.
- The audit trail records configuration, credential, onboarding, submission and inbound actions with the person, never a secret.