Compliance

ANAF reporting — the device archive and SPV submission

How the AMEF produces its signed ANAF monthly archive, how to export it live from the device with e-bon — Portal, API or the mobile app — and how to submit the ZIP through SPV.

Isometric illustration of XML and archive documents flowing through a P7B signature seal up to the ANAF cloud, with four submission status indicators below, in emerald, blue, and zinc tones

Romanian fiscal law requires every AMEF (electronic fiscal cash register) to keep a structured trail of every operation and every daily closing, and to make that trail available to ANAF. Both records live on the device: the Jurnal Electronic (JE) and the Memorie Fiscală (MF) are maintained by the AMEF firmware, and the AMEF itself produces the signed monthly ANAF archive — a ZIP containing the ANAF-format XML, .p7b signature, LDB and JE artefacts.

e-bon does not generate or store any ANAF documents in the cloud. It exports the archive live from the device over the cloud command relay; you download the ZIP and submit it through Spațiul Privat Virtual (SPV) at anaf.ro.

Understand the four report types

Report	What it is	Submitted to ANAF?
Raport X	Mid-shift snapshot of totals — read-only, does not close the day	No
Raport Z	End-of-day fiscal closing — irreversible, source of truth for the day	No (written into the device's fiscal memory; covered by the archive)
Jurnal Electronic (JE)	Per-operation journal of every fiscal event, recorded on the device	Yes — inside the device's monthly ANAF archive, via SPV
Memorie Fiscală (MF)	Per-closing record of every Z, kept in the device's fiscal memory	Yes — inside the device's monthly ANAF archive, via SPV

Raport X is operational only — useful for the cashier, never sent anywhere. Raport Z is the daily source of truth and feeds the MF. The JE captures the per-operation detail; the MF captures the per-closing summary. Both live on the AMEF — they are the legal record, and e-bon reads them live from the device whenever you need them (see Portal · Reports).

Export the ANAF monthly archive

The AMEF firmware assembles and signs the archive; e-bon fetches it from the device while it is online. Three equivalent ways:

Portal — open Reports → ANAF Export, pick the device and the month (plus the device storage target where offered), then Export & download. The browser saves the ZIP.
API — request the archive for a date range (requires the reports scope):
```
POST /api/v1/devices/{deviceId}/reports/anaf-export
```
```
{ "fromDate": "2026-06-01", "toDate": "2026-06-30", "storageTarget": "sdcard" }
```
The response carries export.filename, export.base64 and export.sizeBytes — decode the base64 payload and save it as a .zip. See the Reports API for the full contract.
Mobile app — the ANAF export screen on the device detail produces the same archive directly at the register.

storageTarget ("ramdisk" or "sdcard") selects where the device stages the archive and only matters on AMEFs that advertise both options. Check what the device supports with GET /api/v1/devices/{deviceId}/reports/capabilities (canExportANAFByDate, supportsAnafStorageRamDisk, supportsAnafStorageSdCard) — the Portal does this for you and shows a Not supported by this device notice where applicable.

Because the archive is read live, the device must be online (its controller app connected); otherwise the endpoint returns 503 with a connectivity code (E600/E601/E602). Exporting a large month can take a few minutes.

The archive is already signed by the AMEF's own fiscal certificate — there is nothing for you to sign and nothing for e-bon to keep. Every export reads the fiscal memory and journal exactly as they exist on the device at that moment.

Submit the archive in SPV

Close every fiscal day with a Z

Each day the device was used must end with a Z closure — at the register, from the app, or from the Portal Actions tab. The closures accumulate in the device's fiscal memory, and that is what the monthly archive covers.

Export the archive at month end

Use the Portal ANAF Export tab, the API endpoint or the app's ANAF export screen for the full calendar month, and download the ZIP.

Verify the download

Check that the ZIP covers the right month and the right device (fiscal serial). Do not edit, rename or repackage its contents — the AMEF's signature covers them byte-for-byte.

Submit the file in SPV

Log in to Spațiul Privat Virtual and upload the archive. ANAF returns a recipisă (receipt) once it accepts or rejects the file — keep it with your fiscal records.

e-bon does not track ANAF submission states — the submission happens in SPV, outside e-bon, and SPV is the system of record for acceptance. If ANAF rejects the archive, re-export a fresh one from the device and resubmit — see troubleshooting an ANAF rejection.

F4109 — ANAF inactivity declaration

When an AMEF emits zero receipts in a calendar month, you must file declaration F4109 with ANAF by the 20th of the following month.

GDPR Compliance

How e-bon (Crisposoft SRL) processes personal data under the GDPR — data controller, your rights, lawful processing purposes, and how to exercise them.