Bulgaria SAF-T

What it does

SAF-T (BG) export — three variants

Monthly (chart of accounts, customers, suppliers, VAT tax table, GeneralLedgerEntries and SourceDocuments — sales invoices, purchase invoices, payments), annual (fixed-asset register) and on-demand audit file, all in the published NRA SAF-T schema (a Bulgarian profile of OECD SAF-T 2.0; schema v1.0.2, effective 1 April 2026). The XML namespace and version are emitted per the NRA pattern and are overridable on the company SAF-T settings.

Period export model

Pick a variant and date range; Odoo collects the posted invoices, vendor bills, journal entries and payments, builds the file, stores it as a downloadable attachment and records the document and GL-line counts.

Real EIK / EGN / VAT validation

The official check-digit algorithms for the Bulgarian EIK / Bulstat (nine- and thirteen-digit unified identification code), the EGN (ten-digit personal number, with embedded-date plausibility) and the BG VAT number, applied on company and partner.

Phase & threshold engine

Classifies the company into Phase 1 (net sales above BGN 300,000,000 or NRA payments above BGN 3,500,000), Phase 2, 3 or 4, and flags each document whose date falls inside an active mandatory reporting period.

SAF-T (BG) business-rule validation

A Bulgaria rule set layered on the shared engine's EN 16931-style core: company EIK / VAT, customer EIK, BGN / EUR currency, VAT codes VS / VR / VZ / VE / VN and credit-note referencing, surfaced before export.

Editable NRA defaults

The SoftwareValidationNumber and phase thresholds are held on the company record. Nothing is bundled or sent anywhere except the file you generate and submit yourself.