Which client is about
to miss the deadline.
One screen, your whole portfolio: which invoice isn't showing as transmitted in e-Factura, for which client, and how many working days are left. We file nothing on your behalf — we read, and we tell you.
The real screen, with demo data. CUIs are masked — we don't show yours to anyone either.
5 working days from issuance — or from the legal issuance deadline. Whichever expires first.
The day of issuance doesn't count. Neither do Saturdays, Sundays or public holidays.
Regulation (EEC, Euratom) 1182/71, incorporated by art. 10(7). We compute it exactly, Orthodox Easter included.
What it does
The deadline register
One row per client, working days left on a five-notch ruler. A compliant client gets no colour at all, so the eye falls only on what needs work. Stale or incomplete data is marked on a different axis from risk — a client can be both fine and unverified, and those two must never blur together.
Alerts before the deadline
A WhatsApp message with the client, invoice number, deadline and days remaining. Strictly factual, no upsell — partly because the law requires it, partly because an alert you don't trust is worth nothing.
Read-only by construction
We transmit nothing to ANAF on your behalf. The moment we file for you, we inherit the liability for ANAF's outages — and ANAF's outages are the whole reason this product exists. The submit route is blacklisted in code, with a test.
Built directly on the ANAF API, verified against the documentation and live probes rather than assumptions: 401 instead of 403, daily limits that arrive as HTTP 200, the typo in the error namespace. They're in the code because we hit them.
How we start
A €300 audit. You upload an export from your invoicing software, we spend 90 minutes on your real workflow, and you leave with a 2-page doc: which invoices are already at risk, where the hours go, what gets fixed first. Credited against the project if we go ahead. If we don't, the doc is yours.