Serbia Electronic Delivery Note Requirements Guide

Serbia electronic delivery note requirements determine when a business must issue, receive, and confirm an electronic record of a goods movement through the national eOtpremnica system. As of April 1, 2026, this is a live Serbia-specific workflow, not a generic delivery-note explainer or a draft-law summary: public-sector send and receive obligations, along with obligations tied to excise-goods movements, began on January 1, 2026, while full private-sector send and receive obligations begin on October 1, 2027, according to Serbia Ministry of Finance's rollout summary for the electronic delivery note system. Paper-form fallback rules tied to e-delivery notes also apply from April 1, 2026.

In business terms, an electronic delivery note records who is sending the goods, who is receiving them, what is moving, when transport starts, and where loading and unloading happen, then connects that movement to receipt confirmation. This Serbia electronic delivery note guide is narrower: it focuses on the live trigger points behind Serbia electronic delivery note requirements and the operational consequences for dispatch, receipt, and proof of movement.

That matters because Serbia eOtpremnica requirements are not limited to ordinary outbound shipments. The framework also covers internal e-delivery notes in certain situations, e-receipt notes that document what was physically accepted, and specific import/export and multi-delivery scenarios. For finance teams, controllers, warehouse-adjacent AP staff, and advisors, the practical question is not just whether goods moved, but whether that movement created the right eOtpremnica evidence for receiving controls, exception handling, and later invoice verification. If you want a refresher on what a delivery note should include, use that guide after the Serbia-specific scope is clear.

---

Who Must Use eOtpremnica Now, and What Changes in 2027

The practical scope test is what kind of movement are you handling, and who is on the receiving side of it?

Already live from January 1, 2026:
If your movement involves public-sector entities or excise goods, you should treat eOtpremnica as a current-process issue.

• A public-sector sender must send electronic delivery notes for in-scope movements.
• A public-sector recipient must receive them.
• A private-sector supplier delivering to a public-sector recipient is already inside the live regime.
• Excise-goods movements are also already in scope, even if the business itself is private sector.

A private business can still have an immediate obligation today if it supplies the public sector or moves excise goods.

The timeline is easier to operationalize in three buckets:

• In scope now: public-sector send/receive flows, private-sector deliveries to public-sector recipients, and excise-goods movements from January 1, 2026.
• Fallback rules live now: paper-form contingency handling from April 1, 2026 when the electronic workflow cannot be used temporarily.
• Broader private-sector rollout later: wider private-sector send-and-receive obligations from October 1, 2027.

The role split is just as important as the dates:

• Sender: issues the eOtpremnica and populates the shipment, recipient, and transport data before movement starts.
• Recipient: uses the e-receipt note stage to confirm receipt, reject it, or record deviations.
• Carrier or transport operator: needs the movement data and handoff details aligned with the actual route, especially when fallback paper handling, multiple vehicles, or multiple carriers are involved.

If your business handles ordinary non-excise goods between private-sector counterparties only, the broader obligation still sits later on the timeline. For many businesses, October 1, 2027 is the deadline to review:

• dispatch and proof-of-shipment procedures,
• customer and recipient master data,
• receiving and discrepancy logging,
• carrier handoff procedures,
• invoice-match exception rules for ordinary private-sector flows.

If you ship to a public-sector recipient or handle excise goods, you likely need action now. If you operate only in ordinary private-to-private, non-excise flows, you are mainly preparing for October 1, 2027 while still understanding the paper-form fallback rules that took effect on April 1, 2026.

How Internal E-Delivery Notes and E-Receipt Notes Work

A Serbia internal e-delivery note is not just a warehouse transfer memo. The amended rulebook clarified that internal e-delivery notes are required for some movements that are not standard outward sales, including movements of goods that do not constitute a supply under VAT rules, business samples, and certain promotional materials or low-value gifts.

The same update also clarified cases where there is no obligation to send an e-delivery note, including goods that are not intended to be delivered, such as fuel in the transport vehicle's tank or tools used to install delivered goods, and goods moved for analysis under documents issued by a competent authority. That matters because teams often overgeneralize and assume every internal movement needs the same document treatment.

The workflow is easier to manage if you separate dispatch evidence from receipt evidence:

1. The sender issues the internal e-delivery note and records the goods, origin, destination, and transport arrangement.
2. The recipient uses the e-receipt note stage to confirm receipt, reject it, or record deviations between dispatched and received quantities.
3. The system applies automatic handling if a required e-receipt action is not taken within the legal deadlines.

That receipt stage is where the movement stops being "what dispatch says left" and becomes "what receiving says arrived." If part of the shipment arrived short, damaged, or with another discrepancy, the e-receipt note is the structured place for that difference to surface. Receipt confirmation needs a clear owner because the system does not treat it as optional cleanup.

This is where Serbia internal e-delivery note workflows start to matter beyond formal compliance. The internal e-delivery note shows what dispatch says left Site A. The e-receipt note shows what receiving says arrived at Site B. That distinction gives businesses better evidence for shortage claims, damaged-goods disputes, and later invoice verification.

Special Cases That Need Extra Attention

Excise goods belong in your first scope workshop, not your cleanup list. Serbia excise goods delivery note obligations are part of the early rollout from January 1, 2026, not the wider October 1, 2027 expansion. The February 2026 rulebook update also added new excise categories in the e-delivery note workflow, including nicotine products and petroleum derivatives. If excise goods are involved, assume the movement deserves early process design, not later remediation.

Import and export goods movements use different location logic. The same rulebook update says that for imports, the sender should state the place where it acquired the right to dispose of the goods as the dispatch address and place of loading. For exports, the delivery address and unloading place should reflect the planned delivery point or the place where the goods are expected to cross Serbia's state border. That is more specific than simply copying a warehouse address into every field.

Logistics, customs, and finance teams need one answer to a basic question: what exact event are we evidencing here, legal control over the goods, physical loading, final domestic delivery, or border crossing? If each team answers that differently, the movement record becomes harder to use later in receiving controls or invoice checks.

Estimated quantities and multi-stop trips need a pre-agreed exception workflow. The amended rulebook allows an e-delivery note to show an estimated quantity when the same vehicle is making multiple deliveries and the exact quantity for each recipient is not known before departure. In that case, the recipient sends an e-receipt note with the exact quantity actually received. The same update also makes loading and unloading places mandatory when more than one transport vehicle or more than one carrier is involved in the delivery.

These are the scenarios where teams should write down the workflow before the vehicle leaves:

• Which recipient or delivery point is covered by each eOtpremnica.
• Whether quantities are fixed or estimated at departure.
• Who owns the loading and unloading data when the route changes hands.
• Who confirms the final received quantity.
• How shortages, over-deliveries, or route changes are escalated.

Businesses handling excise goods, import/export flows, or one-vehicle multi-stop deliveries should test those cases explicitly. They are exactly where dispatch evidence, receipt evidence, and finance records drift apart fastest.

---

Why EOtpremnica Matters for Receiving Controls and Invoice Verification

Any Serbia electronic delivery note guide that stops at shipping obligations misses the finance-control value. Once an in-scope movement is documented through eOtpremnica and followed by ePrijemnica, the e-receipt note, you have evidence of what was dispatched, what was physically received, and whether the two actually matched. That matters to controllers and AP teams because invoice approval should rest on receipt evidence, not just on a supplier invoice or a warehouse message saying the truck arrived.

In practice, the e-delivery note becomes the expected-quantity record, while the e-receipt note becomes the received-quantity record. That gives you a stronger base for goods receipt controls and invoice verification: compare the supplier invoice to the dispatched quantities, the confirmed received quantities, and any recorded discrepancies before posting or approving payment. That comparison is even clearer when the team also maps Serbia's wider SEF invoicing requirements, because the invoice side and the goods-movement side do not always follow the same trigger sequence. If a supplier bills 1,000 units but the receipt note shows only 960 accepted, AP has a documented reason to hold part of the invoice, request a credit note, or route the difference for investigation.

This is where Serbia's workflow becomes useful beyond legal compliance. Short deliveries, over-deliveries, damaged goods, and returns should not live only in email threads or handwritten receiving notes. The receipt workflow creates a traceable exception record, which gives finance a better basis for resolving mismatches between stock records, receiving confirmations, and supplier billing.

The same logic helps with month-end cleanup. Teams working on matching delivery notes to supplier invoices can use eOtpremnica and ePrijemnica as the proof set behind their matching process. Teams responsible for handling goods received not invoiced balances can use dispatch and receipt timestamps to decide whether a GRNI balance reflects goods genuinely received before invoicing, a billing delay, or a shipment that was only partially accepted.

Finance teams should review a few control points in their own process:

• Who checks that the invoice quantity matches the accepted quantity in the receipt note, not just the quantity on the dispatch note.
• How shortages, excess quantities, and returns are coded and escalated before invoice approval.
• Whether AP can see when receipt evidence is still pending or unresolved.
• How GRNI, blocked invoices, and supplier disputes are traced back to the original dispatch and receipt records.
• Where the audit trail sits so an internal reviewer, external auditor, or tax reviewer can follow the chain from shipment to receipt to payment decision.