Reports
Reports
The Reports page collects every fiscal report your devices have produced and lets you trigger new ones on demand. Romanian fiscal law defines a small, fixed catalogue of reports — X, Z, Memorie Fiscală and Jurnal Electronic — and the page gives each one its own tab with the columns and detail view that report needs.
Understand the four report types
Open the Reports page
Open Reports from the Portal sidebar. The page has three parts:
- A filter row at the top (device, ANAF status for the JE tab, date range).
- A Trigger Report button to send an X or Z command to a device.
- Four tabs — X Reports, Z Reports, MF Reports, JE Reports — each with its own table.
Click any row in any tab to open the report detail modal.
Filter reports
The filter row applies across the active tab:
- Device — single device or All devices.
- ANAF Status — visible only on the JE Reports tab; filters by
Accepted,Pending,RejectedorError, or All statuses. - Date range —
From/To. The page enforces start ≤ end and prevents future end dates.
Filters refresh the active tab as you change them.
View X reports
X reports list one row per snapshot with:
- Date — when the snapshot was taken.
- Device — which AMEF produced it.
- Sales, Refunds, Net — totals in RON.
- Receipts — number of receipts covered by the snapshot.
Opening a row shows the full totals, the VAT breakdown by rate (Rate, Base, VAT amount), the receipt count and the device that produced the report.
View Z reports
Z reports add the two columns that matter for fiscal reconciliation:
- Reset # — the device's monotonically increasing Z counter; useful when you have to prove a missing day to an inspector.
- Period — the fiscal day covered by this Z (
periodStart – periodEnd).
The detail modal shows the totals, the VAT breakdown, the period and the reset counter.
View MF reports
MF entries describe periodic fiscal memory archives:
- Archive Date — when the archive was created.
- Device — which AMEF it belongs to.
- Expires At — when this archive becomes invalid for tax-authority purposes.
The detail modal shows the archive date, the device and the expiry date.
View JE reports
JE rows track the daily electronic journal that the device hands to ANAF:
- Date — the report date the JE covers.
- Device — the AMEF that produced the journal.
- ANAF Status —
Accepted,Pending,RejectedorError, colour-coded. - Submitted —
Yesif the journal has been transmitted,Nootherwise.
The detail modal includes the P7B signature and the full XML content of the journal as ANAF received it. Treat both as evidentiary: they are exactly what was submitted, and they are what an inspector will ask to see.
Trigger a report
X and Z reports can be triggered remotely from the Portal — there is no need to walk to the cash register and press a key.
Click Trigger Report
The button sits next to the filter row. It opens the Trigger Report modal.
Pick the device
Use the Device picker. Devices that are currently offline are still listed — the command will be queued and run when the device reconnects.
Choose the report type
Select X Report for a non-fiscal snapshot, or Z Report to close the day fiscally.
Send
Click the confirm button. The Portal sends the report command to the device.
- If the device is online, the report prints on the AMEF and a new row appears in the matching tab as soon as it is confirmed.
- If the device is offline, the modal returns an offline warning: the command has been queued and will execute the moment the controller app on the tablet reconnects.
Access reports programmatically
To pull report data into your own dashboards or accounting pipelines, use the reports API rather than scraping CSV — see the API integration walkthrough and create a key on the API keys page.
Next steps
Receipts
Browse every fiscal receipt issued by your devices, drill into the line items and VAT breakdown, issue receipts manually from the Portal and print fiscal reversal (storno) receipts when something has to be undone.
API keys
Create, scope and revoke the API keys that POS partners and external systems use to talk to the e-bon API — and learn where webhooks fit in alongside them.