Romanian tax law has a rule that bites quietly. If you buy from a supplier while it is listed in ANAF's register of inactive taxpayers, you can't deduct the expense or the VAT on that purchase (Fiscal Code, art. 11(7); there are exceptions for forced execution and certain insolvency cases). If the supplier only had its VAT registration cancelled on one of the grounds in art. 316(11), it's a different mechanism (art. 11(9)): you lose the VAT deduction, not the expense, from the day after the cancellation is entered in ANAF's register. When the supplier is reactivated or re-registered, the deduction can be recovered.
The rule is simple. The timing isn't. A supplier is fine when you sign, and inactive three months later. Most companies check once, at onboarding.
Not tax advice. Check the details with your accountant. I also built a hosted version of what follows; it's linked at the end.
Do it yourself: ANAF's public API
ANAF exposes a free, keyless endpoint. One call checks up to 100 CUIs (company tax IDs) for a given date:
curl -X POST https://webservicesp.anaf.ro/api/PlatitorTvaRest/v9/tva \
-H "Content-Type: application/json" \
-d '[{"cui": 160796, "data": "2026-11-17"}]'
The answer (trimmed) has Romanian field names, which is what you'll be searching for when something breaks:
{
"found": [{
"date_generale": { "cui": 160796, "denumire": "AUTOMOBILE-DACIA SA", "stare_inregistrare": "..." },
"inregistrare_scop_Tva": { "scpTVA": true, "perioade_TVA": [ ... ] },
"inregistrare_RTVAI": { "statusTvaIncasare": false },
"stare_inactiv": { "statusInactivi": false, "dataInactivare": "", "dataReactivare": "", "dataRadiere": "" },
"inregistrare_SplitTVA": { "statusSplitTVA": false }
}],
"notFound": []
}
scpTVA is VAT registration, statusInactivi is the inactive flag, dataRadiere is the deregistration date. If you're a developer with 20 suppliers, a cron job and this call get you most of the way.
The part that's actually hard: the diff
The API gives you today's picture. What you want is "tell me only when something changed", and that's where a 30-line script starts to grow:
- A failed check is not a change. ANAF does time out or return errors from time to time. If you compare an error with last week's snapshot, every supplier "changed". The rule I settled on: an error keeps the old snapshot and emits nothing. If more than 20% of the checks in a run fail, the run doesn't overwrite the saved state at all.
- Compare normalized snapshots, not raw responses. Whitespace in addresses changes, field order changes. I keep only the fields that matter, trimmed, and hash their sorted-key JSON (SHA-256):
const s: Snapshot = {
found: true,
inactive: row.inactive,
vatRegistered: row.vatRegistered,
cashAccountingVat: row.cashAccountingVat,
splitVat: row.splitVat,
deregisteredOn: row.deregisteredOn,
};
// sole traders (PFA, II, IF) are natural persons: status only, no name/address stored
if (row.redacted || row.isNaturalPersonEntity !== false) return s;
s.name = text(row.name); // whitespace-collapsed, trimmed
// later: stableHash(s) = sha256 of the canonical, sorted-key JSON
- "Not found" needs confirmation. A company that existed last week and is "not found" today is usually a glitch. I only report it after two runs in a row.
- Rate limits. At most 100 CUIs per request and roughly one request per second, with retries and backoff. 5,000 suppliers is 50 requests, about a minute.
- A dated record. Every check is a row with a timestamp, which is useful when someone later asks "did you verify this supplier at the time?"
What a change looks like
On the first run every supplier is a baseline. After that, only changed suppliers come out (illustrative example):
{
"cui": "12345678",
"name": "EXAMPLE SRL",
"status": "OK",
"inactive": true,
"inactiveSince": "2026-11-10",
"vatRegistered": false,
"monitorStatus": "CHANGED",
"changes": [
{ "type": "BECAME_INACTIVE", "field": "inactive", "from": false, "to": true },
{ "type": "VAT_CANCELLED", "field": "vatRegistered", "from": true, "to": false }
],
"checkedAt": "2026-11-17T06:00:12Z"
}
The hosted version
I packaged all of the above as an Apify Actor, Romania Supplier Monitor. It's free during launch; the planned price is $2 per 1,000 companies checked, and Apify announces price changes at least 14 days ahead. Paste your CUIs, set mode to monitor with a monitorId, turn on "Only output changes", schedule it weekly and add an email, Slack or webhook integration. Or call it and get the changed rows back in one request:
curl -X POST "https://api.apify.com/v2/acts/nocturntools~ro-supplier-monitor/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"cuis": ["RO14399840", "1590082", "160796"], "mode": "monitor", "monitorId": "suppliers-main", "onlyChanges": true}'
Where your data lives: runs, datasets and the monitor state (a key-value store you can export as JSON) are in your Apify account, not mine. I don't see your supplier list, and you can delete or take the data with you at any time.
Limits
- Official public sources only. Nothing that needs a login.
- Sole traders are natural persons: their names and addresses are redacted (GDPR), their tax status is still shown.
- It reports what ANAF's register says and when it changes. It doesn't decide what's deductible.
Two companion Actors use the same CUI list: balance-sheet risk flags and court cases from portal.just.ro. They're on the Nocturn Tools page.
Unofficial. Not affiliated with or endorsed by ANAF or the Romanian Ministry of Justice.
Top comments (0)