Reports

The Reports page reads everything live from the fiscal device. There are no stored report tables: the AMEF's fiscal memory (Memorie Fiscală, MF) and electronic journal (Jurnal Electronic, JE) are the legal record, so every read dispatches a command to the device through its controller app and shows you the device's own answer. That is also why the device must be online — an offline AMEF has nothing to answer with.

Pick an online device

The page opens with a single Device picker. Devices that cannot answer right now are listed but disabled, each with the reason — Offline, Not connected (controller app not on the WebSocket) or No controller assigned.

As soon as you pick a device, the page reads its reporting capabilities ("Checking what this device supports…"). Not every AMEF supports every operation, so the rest of the page adapts to what the driver reports:

• Operations the device cannot do show a Not supported by this device notice instead of controls.
• If the capability read itself fails, a Device unreachable alert shows the connectivity error.

Read the telemetry cards

For devices that support structured reads, two cards summarise the device's counters:

• Fiscal memory — the last Z number, plus Z closures used / capacity (for example 412 of 2500 Z closures used). The usage line turns to a warning colour when the fiscal memory is nearly full.
• Electronic journal — what the card shows depends on what the model honestly reports. Models with a numeric journal capacity (Custom) show lines remaining plus lines used / capacity. Datecs journals count documents, not lines, and their firmware reports no capacity, so the card shows the document count plus the device's fill state (Journal nearly full / Journal full). Models without journal counters (Tremol) show only the fill state.

Choose a range

Z History, Journal and the periodic print in Actions share one range picker with two modes:

• By date — From / To calendar dates (inclusive).
• By Z number — From Z / To Z closure numbers (inclusive).

Modes the device does not support are disabled, and the page pre-selects a mode the device can handle.

Read the Z history

The Z History tab is where past Z closures live. Pick a range and click Read from device — the Portal reads the rows from the device's fiscal memory and renders a table:

• Date — when the Z closure ran.
• Z # — the closure number.
• Gross total — the day's gross total, in RON.

The header shows the covered closure range (for example Z 401 – 430). An empty result means no Z closures fell inside the selected range.

Read the electronic journal

The Journal tab reads the electronic journal for the range and shows it exactly as the device recorded it: one verbatim text block per Z closure (labelled Z 401, Z 402, …) with the total line count in the header. This is the receipt-by-receipt paper trail an inspector reads — e-bon does not reformat it.

Export the ANAF archive

The ANAF Export tab downloads the device's signed monthly ANAF archive — the ZIP the AMEF firmware produces for the tax authority, which you then submit yourself in SPV.

Print X, run Z and print periodic reports

The Actions tab holds the three operations that produce output on the device's paper. Nothing appears in the Portal afterwards — there are no stored report rows; a success toast confirms the device finished.

• Print X report — prints the read-only intra-day totals snapshot. Safe to run any number of times.
• Run Z report — runs the end-of-day fiscal closure. The button opens a confirmation dialog first: "The Z report closes the fiscal day and resets daily counters. This cannot be undone."
• Print periodic report — prints a fiscal-memory report for the range selected above, on the device's paper.

Access reports programmatically

Everything this page does is available over the API (/api/v1/devices/{deviceId}/reports/*, reports scope) and the official SDK — see the Reports API reference and client.reports, and create a key on the API keys page.

Next steps

• Inspect the underlying transactions — see Receipts for the per-receipt drill-down.
• Manage the devices that answer these reads — see Devices.
• Submit the exported archive to ANAF — see ANAF reporting.