Serbia SEF Electronic Invoicing for SAP: Scope and Integration

Status: Live electronic invoicing and VAT-recording regime. Verified on: 10 July 2026. Serbia’s Sistem elektronskih faktura, or SEF, is the state platform through which regulated structured invoices are sent, received, processed and retained.

The current consolidated Electronic Invoicing Law covers transactions between public-sector entities, between private-sector entities, and between public and private sectors. The December 2025 amendments generally apply to VAT periods beginning after 31 March 2026, with the exception specified in that amending law. A 2026 implementation must therefore use the current law, rulebook, tax categories and technical package rather than an older rollout summary.

Who must use SEF

• Private sector: Serbian VAT payers, other than public-sector entities, for covered transactions with other private-sector entities.
• Public/private flows: covered transactions and payment requests between public and private-sector entities, in both directions.
• Public sector: covered transactions between public-sector entities.
• Foreign businesses: the Serbian VAT tax representative of a foreign person is included for the transactions specified by the law.
• Voluntary users: certain business-income or corporate-income taxpayers outside the public/private definitions may register, after which the applicable SEF rules must be assessed.

The law also contains transaction-level exclusions. These include much retail turnover already governed by fiscalisation, subject to current exceptions for specified corporate-card sales and certain public-sector requests; defined defence or security procurement; certain electricity transactions other than final consumption; supplies without consideration; and other narrowly described cases. Do not encode “all Serbian invoices” as one rule. Build a scope matrix by company status, VAT status, counterparty, transaction and fiscalisation treatment.

Structured format and connection options

SEF exchanges structured electronic invoices. Serbia publishes a domestic Core Invoice Usage Specification aligned with SRPS EN 16931-1 and official UBL 2.1 examples and validation services. The Serbian CIUS and tax categories—not a generic EN 16931 or Peppol mapping—are the implementation baseline.

Users can work in the SEF portal, connect directly through the public API, or use an authorised information intermediary where permitted. Direct API access requires an authorised user to generate and activate an API key. The official API specification, updated on 2 July 2026, covers invoice upload and sending, retrieval, cancellation and storno, incoming-invoice acceptance and rejection, status-change queries, notifications and VAT-recording operations. API credentials and production authorisation must be governed separately from ordinary SAP user access.

Lifecycle, corrections and VAT records

1. SAP determines whether the legal entity and transaction are in scope and creates the correct invoice, advance invoice, credit document or other source object.
2. The integration maps the source to the current Serbian UBL/CIUS rules and submits it through the approved SEF route.
3. SEF identifiers and statuses are written back to an auditable integration record. A technical submission response is not the same as the buyer’s later acceptance or rejection.
4. Incoming invoices are retrieved and matched to procurement and accounting. Acceptance, rejection and deadline controls are handled as explicit business steps.
5. Cancellation, storno and corrective documents follow the applicable SEF operation; the original record and status history remain preserved.

Electronic VAT recording in SEF is related to, but not identical with, electronic invoicing. The law and API distinguish individual and aggregate VAT calculations, adjustments, prior-tax records and cases in which the tax obligation is not already represented by an SEF invoice with VAT. SAP tax reporting design must identify which values come from SEF invoices, which require separate VAT records, and how corrections move through both ledgers. Do not assume that sending an invoice completes every SEF VAT obligation.

For service interruption, preserve an outbound queue, message hash, business key and last confirmed SEF state. Apply the current official notice and technical procedure, then reconcile status changes after restoration. Repeatedly creating new fiscal documents after an ambiguous timeout is not a safe contingency strategy.

What this means for SAP

• Govern PIB, company and public-sector identifiers, VAT-period status, tax categories, bank accounts and unit codes.
• Use the current Serbian CIUS and SEF validation package in regression tests.
• Model outgoing, incoming, accepted, rejected, cancelled, storno and corrected states without overwriting history.
• Keep invoice exchange, VAT recording and input-tax reconciliation as connected but separately controlled processes.
• Test B2B, B2G, G2B, advances, reverse charge, retail boundaries, credit documents and period-end corrections.

S4FN delivery classification: S4FN implementation service and, where required, a custom SEF integration. The SAP landscape, existing local functions, transaction scope and selected SEF access route are assessed before architecture is confirmed. This page does not present SEF as a generic SAP standard interface.

Primary sources

• Serbian Ministry of Finance — SEF portal, current notices and technical material
• Serbian Ministry of Finance — Consolidated Electronic Invoicing Law
• Serbian Ministry of Finance — Current SEF API specification
• Serbian Ministry of Finance — Domestic EN 16931 usage specification

Review note: Serbian law, rulebooks, SEF releases, tax categories and API operations are actively maintained. Confirm the current legal scope and production package with the Ministry of Finance and Serbian tax counsel before go-live. This page is implementation guidance, not legal or tax advice.