Serbia E-Invoicing Requirements: 2026 SEF Guide

Serbia e-invoicing requirements in 2026 are an active operating workflow, not a future mandate. Serbia's System of Electronic Invoicing, usually called SEF or eFaktura, has been introduced in phases since May 1, 2022, private-sector B2B issuance and storage have applied since January 1, 2023, and for tax periods starting after March 31, 2026 some retail transactions also require an electronic invoice, but only after a fiscal receipt has been issued first. In other words, Serbia SEF requirements now affect how you issue, receive, store, and evidence transactions across the full finance process.

The Ministry of Finance of the Republic of Serbia sets out the rollout dates clearly in its Serbia Ministry of Finance FAQ on SEF rollout dates: public-sector entities had to receive and store e-invoices from May 1, 2022, public-to-public and private-to-public issuance also started on May 1, 2022, private-sector receipt started on July 1, 2022, and private-to-private issuance and storage started on January 1, 2023. That means a live 2026 Serbia eFaktura guide has to treat SEF as the system that connects document exchange to the controls that follow it, not as a one-line legal summary.

At a high level, the current in-scope relationships are:

• Public-sector receipt and storage through SEF
• Public-to-public issuance through SEF
• Private-to-public issuance through SEF
• Private-sector receipt of in-scope electronic invoices
• Private-to-private issuance and storage through SEF

For finance teams, that is the real 2026 position: you are managing one connected workflow across issuance, receipt, storage, and transaction evidence, with a newer retail branch that starts from the fiscal receipt and then moves into SEF where the post-March 31, 2026 rules require it.

Who Must Issue, Receive, and Store Through SEF

For most in-scope transactions in Serbia, the standard SEF workflow is straightforward: the supplier issues the e-invoice through SEF, the customer receives it in SEF, and both sides rely on that platform record as part of their retention and audit trail. That is the main operating model in any practical Serbia SEF compliance guide. The retail and fiscalization scenarios are exception branches, not the default path.

A finance team should think about SEF as a live invoice workflow, not just a transmission step. Compliance usually means all of the following happen in the right order:

• The seller creates and submits the invoice in the required structured format.
• The buyer receives the invoice through the correct SEF channel.
• AP or accounting checks the invoice status in SEF so the document is not treated as valid just because someone emailed a PDF copy.
• The commercial content is reviewed, including supplier, amounts, VAT treatment, dates, references, and any supporting delivery or contract evidence.
• The stored SEF record is maintained as part of the business's invoice documentation.

Issuers are responsible for getting the invoice into SEF correctly. In practice, that means your sales, billing, or accounting team cannot rely on a locally generated PDF as the compliance event. The in-scope invoice has to be created and routed through the platform in the required data structure so the recipient can receive it there. If your ERP or billing process creates the commercial invoice first, your real control point is whether that document is then converted and submitted into the SEF flow properly.

Receivers have their own part of the obligation. AP teams are not finished when an invoice appears in the inbox or when a vendor says it was sent. They need to confirm the invoice arrived in SEF, review its status, and check whether the tax and commercial data match what the business actually received or ordered. In day-to-day work, that means your payable process should key off the SEF record and its status, then reconcile that record to purchase orders, goods receipts, service confirmations, or contract terms.

Storage and retention also matter. A compliant process is broader than issuing and receiving because the business must be able to preserve the invoice record it relied on. For finance teams, that means keeping the SEF-side record aligned with your accounting file, supporting documents, and approval trail. If an auditor or tax reviewer asks what document supported the booking, payment, or VAT position, your team should be able to point to the SEF invoice and the related evidence without gaps.

At the routing layer, UBL 2.1 RS CIUS is the practical format rule behind the process. In plain English, it is the structured e-invoice model Serbia uses so invoice data can move through SEF in a standardized way rather than as a free-form attachment. Your team does not need to be technical to care about it. It affects whether invoice fields land correctly, whether mandatory data is present, and whether your system-to-system process is dependable.

That is where an information intermediary can become operationally relevant. An intermediary sits between your internal system and SEF to help transmit, receive, and synchronize invoice data. For some businesses, that means the finance team never logs every invoice manually into the platform because the intermediary or ERP connection handles the exchange. Even then, the accounting control does not disappear. Your team still needs clear ownership for submission success, receipt confirmation, status monitoring, exception handling, and record retention.

The easiest way to separate the main rule from the exception is this: the normal path is SEF-first for in-scope invoicing between relevant parties, while retail fiscalization cases follow a different logic tied to fiscal receipts and special post-March 31, 2026 treatment. If your transaction is a standard B2B or public-sector invoice flow, start with the assumption that issuing, receiving, validating, and storing through SEF is the core process your finance team must manage.

What Changed for Retail Transactions After March 31, 2026

The key retail changes come from Serbia's December 2025 amendments, and they apply for tax periods starting after March 31, 2026. That is the live date this article uses for Serbia e-invoicing requirements. In practice, many businesses will treat April 1, 2026 as the operational switch point, but your internal rule should follow your tax period.

The biggest change is that some transactions that still start as ordinary retail sales can now also trigger an SEF obligation. That matters because teams often assume a point-of-sale transaction ends with retail documentation. After the March 31, 2026 cutoff, that assumption can be wrong.

Two retail cases need special attention, and a quick decision aid helps:

• Ordinary retail sale: fiscal receipt only.
• Retail sale or advance payment to a corporate card holder: fiscal receipt first, then SEF invoice.
• Retail sale to a public sector entity that requests an e-invoice within seven days: fiscal receipt first, then SEF invoice.

The detailed branches are:

• Retail sale to a corporate card holder: if you sell at retail to a business customer paying with a corporate card, Serbia corporate cardholder e-invoice rules can require an SEF e-invoice in addition to the retail documentation already issued. The same logic also applies to an advance payment received for that retail sale.
• Retail sale to a public sector entity: if the buyer is a public sector entity, an e-invoice can still become mandatory after the sale if that entity submits a request within seven days of the retail transaction. In plain English, the sale may look like normal retail on day one, but the SEF obligation can appear shortly afterward.

The sequencing rule is just as important as the scope rule. In these retail scenarios, the e-invoice must not be issued before the fiscal receipt. Your live process therefore has to be fiscal receipt first, e-invoice second. That is the practical core of Serbia fiscal receipt and e-invoice rules: fiscalization happens first at the retail touchpoint, then SEF follows if the transaction falls into one of these exception cases.

This is why the retail amendment is not a side note. It is the point where fiscalization and SEF meet, and most operational mistakes happen in that handoff: the cashier issues the fiscal receipt, but finance never receives the trigger to create the follow-up e-invoice, or issues it in the wrong order, or misses the Serbia public sector e-invoice request 7 days window. Your controls need to connect the POS event, the buyer type, the payment method, and the downstream SEF action.

That workflow sensitivity is why Serbia needs process design across systems, similar to North Macedonia's split between e-Faktura and fiscalization, where the compliance risk also sits in the boundary between invoice rules and retail reporting.

Where Internal Invoices, VAT Records, and Delivery Evidence Fit

In practice, the outward-facing SEF invoice is only one part of Serbia's e-invoicing requirements. For some transactions, the full record set also includes an internal invoice, VAT-supporting records, and logistics evidence that sits beside the exchanged e-invoice or fiscal receipt. That is why your team should think in terms of a document chain, not a single invoice file.

A practical Serbia internal invoice SEF workflow usually has three layers:

• The document exchanged with the counterparty, such as a SEF invoice or, where applicable, a fiscal receipt.
• The internal tax document your team may also need for VAT purposes in specific scenarios, especially where the outward document does not fully support the VAT treatment on its own.
• The accounting and evidence layer, including supporting VAT records, receipt or delivery proof, and any related documentation needed to justify timing, deductions, or adjustments.

This article gives you that practical map, not a replacement for a dedicated internal-invoice explainer. If you need the deeper branch on when Serbia internal invoices trigger inside SEF, use that article alongside this workflow view.

This matters for input VAT and recordkeeping because Serbia VAT records in SEF are only part of the picture. Your AP or accounting team often needs to connect the invoice or fiscal receipt to goods-receipt evidence, the internal posting logic, and the tax period in which the transaction is recognized. Looking at those documents together helps you answer the real review questions: what is the primary source document, is an internal invoice also required, what supports the VAT position, and is the file complete enough for audit review?

Delivery evidence is a good example of why the wider chain matters. A SEF invoice may show the billing event, but the audit trail can still depend on movement-of-goods evidence when timing, acceptance, or fulfillment needs to be demonstrated. If your process involves shipment controls or proof of handover, how Serbia's eOtpremnica rules affect the wider document chain is directly relevant even if the starting question was only about e-invoicing requirements.

One timing point is easy to miss in 2026: the preliminary VAT return rollout was delayed to tax periods starting after December 31, 2026. That means the post-March 31, 2026 retail changes do not make every VAT-linked automation step live at the same time. For now, finance teams should separate current source-document obligations from later-stage preliminary VAT return functionality and build controls around the evidence they actually need today.

---

The Finance-Team Checklist for Issuing, Receiving, and Reviewing

Use this Serbia invoice review checklist as a set of Serbia SEF operational checks and Serbia finance workflow controls for each transaction, not just at month end.

• Classify the event first. Decide whether it is a standard SEF invoice, a retail sale documented only by a fiscal receipt, a retail sale that later also needs a SEF invoice, or an internal-invoice/VAT record case.

• Control the sequence. For tax periods starting after March 31, 2026, if a retail sale involves a corporate card holder or a public sector entity that requests an electronic invoice within seven days, confirm the fiscal receipt was issued first and the SEF invoice followed. Log the supply date, receipt timestamp, SEF issue date, and any advance payment date together.

• Match the document chain. Link the fiscal receipt, SEF invoice, proof of delivery or service completion, and any internal invoice or VAT adjustment record under one transaction reference before posting.

• Check the issuing side. Confirm the buyer, document type, tax treatment, currency, totals, and whether the counterparty belongs in SEF. For retail edge cases, confirm the team is not creating a SEF invoice where only a fiscal receipt is needed.

• Check the receiving side. Verify the SEF invoice matches what was purchased or received. If a fiscal receipt also exists, decide which document is the operative accounting document and keep the other as linked support.

• Review status and exceptions. Check rejections, corrections, credit notes, duplicates, and final acceptance before anything feeds the ledger or VAT file.

• Treat internal invoices as their own lane. When Serbian VAT requires an internal invoice or VAT record, verify the trigger, tax point, tax base, and linked support before the VAT return is finalized.

• Require support for non-routine VAT positions. Keep the delivery note, acceptance record, contract, order, return evidence, cancellation trail, correction notice, or other proof that explains the tax treatment.

• Assign ownership by step. Billing or sales operations own issuance sequence. AP owns receipt matching and duplicate prevention. Tax or accounting owns internal-invoice and VAT-evidence review. The controller owns the monthly exception log and sign-off.

• Test retrieval from an auditor's viewpoint. For any sample transaction, your team should be able to pull the full chain quickly: fiscal receipt, SEF invoice, internal invoice if applicable, proof of supply, payment evidence, adjustment history, and reviewer sign-off.

---

When SEF Access Is Enough, and When You Need Stronger Document Controls

For some teams, direct SEF access is enough. If your invoice volume is low, your counterparties follow a narrow set of patterns, and your reviewers can comfortably match SEF records to supporting documents inside an existing AP or accounting routine, the government system may cover the legal submission and retrieval layer you need. In that setup, the harder work is still real, but manageable: checking values, confirming supporting evidence, and keeping records organized for VAT and audit purposes.

The pressure rises when the workflow stops being uniform. The SEF portal covers the mandated exchange layer, but many finance teams also deal with supplier PDFs, fiscal receipts, credit notes, delivery evidence, internal VAT records, and other files that sit around the SEF transaction rather than inside it. Once those documents arrive in different formats and from different channels, the operational problem becomes intake consistency: can your team classify them the same way every time, extract the same key fields every time, and retain the same evidence trail every time?

That is usually where delays and control gaps appear. SEF may confirm that an invoice exists in the mandated environment, but your team may still need to compare it to a receipt, link it to a delivery document, identify whether a credit note changes the booking, or pull supporting values into a VAT working file. If reviewers are manually opening files one by one, retyping fields into spreadsheets, or relying on inconsistent naming and folder habits, the bottleneck is not Serbia's e-invoicing system itself. It is the document-handling process wrapped around it.

A tool like Invoice Data Extraction is most useful when your Serbia workflow has to connect one retail or B2B event across multiple records. It can help teams standardize supplier PDFs, fiscal receipts, credit notes, and supporting VAT documents into Excel, CSV, or JSON; apply prompt-based rules so buyer type, dates, totals, and document references land in a consistent structure; and preserve source file and page references so reviewers can trace one chain from the fiscal receipt to the later SEF invoice, any internal VAT record, and the supporting evidence. That makes it easier to review corporate-card and public-sector edge cases without losing the document trail, which is why AI invoice data extraction for mixed invoice and receipt workflows can support the document layer around Serbia's mandatory systems while SEF and fiscalization remain the compliance platforms.

If you are deciding whether to add that extra layer, start with the friction you already see:

1. Standardize document intake first if files arrive by email, portal download, scan, and mobile photo, and no one is classifying them consistently.
2. Standardize field extraction rules next if reviewers keep correcting invoice numbers, dates, VAT amounts, credit-note handling, or supplier names in spreadsheets.
3. Standardize review evidence next if your AP team or controller cannot quickly trace a booked value back to the exact file and page that supported it.
4. Standardize role-based outputs next if accountants need clean export files for bookkeeping, AP needs payment-review data, and controllers need structured records for reconciliation or VAT support.

If your Serbia workflow is stable and light, SEF access plus disciplined review may be enough. If you keep seeing format variation, approval delays, or weak audit trails around invoices and related records, the first thing to formalize is the way your team captures, reviews, and retains the transaction file around each invoice.