Serbia SEF UBL 2.1 Format: XML Requirements & Validation Rules

Master Serbia's SEF electronic invoicing requirements. Learn about UBL 2.1 XML standards, validation rules, and mandatory fields to ensure full compliance with the Poreska Uprava. This guide gives the answer first, then explains mandate scope, required invoice data, technical format, penalties, official authority context, and practical compliance steps for businesses preparing or reviewing their local e-invoicing workflow.

What is the Serbia SEF E-Invoicing Mandate?

the Serbia SEF E-Invoicing Mandate is as of January 1, 2023, for B2G transactions and January 1, 2024, for all B2B transactions, Serbia has mandated the use of the Sistem Elektronskih Faktura (SEF).

As of January 1, 2023, for B2G transactions and January 1, 2024, for all B2B transactions, Serbia has mandated the use of the Sistem Elektronskih Faktura (SEF). Under the supervision of the Poreska Uprava (Tax Administration), all VAT-registered businesses must issue, receive, and archive invoices in a specific electronic format. Failure to comply can result in severe financial penalties reaching up to RSD 2,000,000 (~€17,000) for legal entities and RSD 150,000 for responsible individuals.

Which XML Format is Required for Serbia SEF?

The technical backbone of the Serbian e-invoicing system is the UBL 2.

The technical backbone of the Serbian e-invoicing system is the UBL 2.1 (Universal Business Language) standard, specifically following the EN 16931-3-2 specification. This XML-based format ensures that data is structured in a way that the government portal (SEF) can automatically validate and process tax information. Using standardized invoicing software is critical to ensure that every XML file generated meets the precise schema requirements set by the Ministry of Finance.

Key Technical Specifications of the Serbian UBL Profile

Unlike standard UBL 2.1, the Serbian implementation includes specific national extensions and mandatory fields that must be populated for a successful upload to the SEF portal. These include:

• Syntax: UBL 2.1 (ISO/IEC 19845:2015).
• Customization ID: Must follow the specific Serbian prefix (urn:cen.eu:en16931:2017#compliant#en16931.rs:711).
• Character Encoding: UTF-8 is the mandatory encoding to support Serbian Cyrillic and Latin characters.
• Validation: Invoices must pass both XSD (XML Schema Definition) and Schematron validation rules.

Mandatory Data Fields in the Serbian XML Invoice

To avoid rejection by the SEF portal, your XML files must contain the following data archetypes.

To avoid rejection by the SEF portal, your XML files must contain the following data archetypes. Modern accounting tools typically automate these mappings, but manual API integrations must ensure these tags are present:

Handling VAT (PDV) and Tax Rates

In Serbia, the standard VAT rate is 20% (PDV), while the reduced rate is 10%. The XML must clearly define the cac:TaxCategory. If a transaction is exempt from VAT, the XML must include a specific reference to the article of the Serbian Law on VAT that justifies the exemption. This is often handled through a dedicated 'Invoice Note' or a 'Tax Exemption Reason Code' within the UBL structure.

How to Connect to the SEF Portal?

Businesses have two primary routes for complying with the Serbian mandate. First, smaller entities can manually upload XML files to the official Poreska Uprava web interface.

Businesses have two primary routes for complying with the Serbian mandate. First, smaller entities can manually upload XML files to the official Poreska Uprava web interface. However, for most businesses, the preferred method is via the SEF API.

Integrating your systems directly with the SEF API allows for real-time invoice transmission. To do this, your software must support compliance features such as secure authentication using API keys and the ability to poll the portal for status updates (e.g., Sent, Approved, Rejected).

Common Validation Pitfalls and Errors

When migrating to the UBL 2.

When migrating to the UBL 2.1 format in Serbia, technical teams often encounter several common errors that result in rejected documents:

• Incorrect PIB Format: The Tax Identification Number (PIB) must be exactly 9 digits. Any deviation leads to immediate rejection.
• JBKJS Missing: For B2G transactions, the unique identifier for public sector entities (JBKJS) is mandatory.
• Rounding Discrepancies: The total sum at the document level must exactly match the sum of individual line items, often calculated to two or four decimal places.
• Duplicate Invoice Numbers: The SEF system prevents the re-use of an invoice ID within the same fiscal year for the same supplier.

Why Compliance Automation Matters

Managing the transition to UBL 2.

Managing the transition to UBL 2.1 XML manually is a high-risk strategy. Given that penalties for non-compliance start at RSD 150,000 and can escalate to millions, ensuring your invoicing software is automatically updated with the latest Schematron rules from the Poreska Uprava is essential. Beyond avoiding fines, digitizing the invoice flow through SEF improves cash flow by reducing the time spent on manual reconciliation and disputes.

Key Deadlines to Remember

Key Deadlines to Remember includes: January 1, 2023: All B2G (Business-to-Government) invoices must be electronic via SEF. July 1, 2022: G2B (Government-to-Business) entities started issuing e-invoices.

• January 1, 2023: All B2G (Business-to-Government) invoices must be electronic via SEF.
• July 1, 2022: G2B (Government-to-Business) entities started issuing e-invoices.
• January 1, 2024: Full B2B mandate. All VAT-registered businesses must issue and receive e-invoices.

Frequently Asked Questions

1. Is a digital signature required for Serbian e-invoices?

While the SEF system secures the authenticity of the documents, invoices sent via the API are typically authenticated via the system's electronic keys. Invoices uploaded manually are signed via the portal credentials.

While the SEF system secures the authenticity of the documents, invoices sent via the API are typically authenticated via the system's electronic keys. Invoices uploaded manually are signed via the portal credentials.

2. What happens if I send an invoice in PDF format instead of XML?

PDFs are no longer legally valid for VAT purposes in the B2B or B2G sectors in Serbia. While you may send a PDF visualization to a client for convenience, only the UBL 2.

PDFs are no longer legally valid for VAT purposes in the B2B or B2G sectors in Serbia. While you may send a PDF visualization to a client for convenience, only the UBL 2.1 XML registered on the SEF portal is recognized by the Poreska Uprava.

3. Do I need to archive electronic invoices?

Yes, e-invoices must be archived for 10 years. The SEF portal provides a central archive, but it is highly recommended that businesses maintain their own compliant digital storage for redundancy and internal audit purposes.

Yes, e-invoices must be archived for 10 years. The SEF portal provides a central archive, but it is highly recommended that businesses maintain their own compliant digital storage for redundancy and internal audit purposes.

4. Are non-VAT registered businesses required to use SEF?

Currently, the mandate primarily targets VAT-registered entities (obveznici PDV-a). However, public sector entities must use it regardless of VAT status.

Currently, the mandate primarily targets VAT-registered entities (obveznici PDV-a). However, public sector entities must use it regardless of VAT status. Non-VAT businesses can opt-in voluntarily.

5. What is the penalty for failing to issue an e-invoice?

Legal entities can be fined up to RSD 2,000,000. Additionally, the responsible person within the company can face fines up to RSD 150,000.

Legal entities can be fined up to RSD 2,000,000. Additionally, the responsible person within the company can face fines up to RSD 150,000. Consistent non-compliance may also trigger more frequent tax audits from the Poreska Uprava.

6. Can I use the OIOUBL or PEPPOL standard instead of UBL 2.1?

Serbia's SEF is based on the EN 16931-3-2 standard, which is a specific subset of UBL 2. 1.

Serbia's SEF is based on the EN 16931-3-2 standard, which is a specific subset of UBL 2.1. While it shares many similarities with PEPPOL, you must ensure your XML generator follows the specific Serbian national extensions (Serbia-specific Schematron).