Slovenia Potni Nalog Explained: 2026 Guide

A Slovenia potni nalog is a formal business travel order and expense-settlement document. It records who traveled, why the trip happened, when and where it took place, how the traveler got there, and which costs can be reimbursed. In practice, it is usually issued before travel and then completed after the trip with receipts, mileage details, and any per-diem calculation needed for review, payment, and archiving.

That is why translating potni nalog as a generic expense report is only partly right. A standard business travel expense report is usually retrospective: the employee travels first and claims later. A potni nalog combines two functions in one record. It authorizes the trip before departure, then becomes the settlement file used to check allowances, supporting evidence, and reimbursement.

For finance, payroll, and HR teams, that difference matters. The document does not just describe spending. It anchors the control chain around the trip itself: approval, travel details, expense evidence, calculation of reimbursable amounts, review, payout, and retention. If the form is incomplete, the problem is not merely administrative. Reimbursement can be delayed, payroll treatment can become unclear, and the supporting file may not stand up well in an internal or external review.

Which fields a valid potni nalog should contain

Potni nalog layouts differ across employers, payroll software, and public-sector templates, but the underlying structure is recognizably consistent. A compliant form needs enough information to show who was authorized to travel, what trip was approved, how the trip actually happened, and how the final reimbursement was calculated.

The core planning fields usually include:

• traveler name or employee identifier
• employer or entity details
• purpose of travel
• destination or route
• departure and return dates and times
• approved means of transport

That first block establishes the trip before it happens. If a private car will be used, many organizations document that authorization explicitly because it affects later kilometrina claims. If the traveler received an advance, the form should capture that as well so the final settlement can net the advance against reimbursable expenses.

The second block is completed after travel. That is where the potni nalog stops being a simple travel order and becomes a settlement record. The completed form normally includes actual travel times, expense lines, mileage details where relevant, any per-diem calculation, attached receipts, and the final amount owed to or recoverable from the traveler.

Approvals also matter. Some employers still use signatures on paper forms, while others rely on electronic approvals inside HR or finance systems. Either way, the point is the same: the file should show who approved the trip and who accepted the completed claim for reimbursement. A digital form can still function as a potni nalog if it preserves the same key fields, approval trail, and supporting evidence.

It should not be confused with student-employment paperwork such as Slovenia's student work referral document, which supports a different hiring and payment workflow from a business-travel order.

How dnevnica and kilometrina work in Slovenia

The two terms English-language readers usually need decoded are dnevnica and kilometrina. Dnevnica is the per-diem allowance tied to business travel. Kilometrina is mileage reimbursement when an employee is authorized to use a private vehicle for the trip. Both appear straightforward until a reader starts comparing sources and finds different numbers presented as if they describe the same rule.

The first distinction is between public-sector schedules and private-sector tax treatment. GOV.SI guidance on Slovenian travel allowances lists 2026 public-sector domestic per-diem amounts at EUR 26.99 for trips over 12 hours, EUR 13.46 for trips over 8 to 12 hours, and EUR 7.38 for trips from 6 to 8 hours. Those figures are explicitly tied to the public-sector schedule for 1 January 2026 through 31 December 2026. They are useful reference points, but they should not be mistaken for the single universal table that governs every Slovenian employer.

That is where many English summaries become misleading. Private-sector discussions often frame travel reimbursements through non-taxable norms and employment-tax treatment, not through the exact public-sector schedule. The practical question is therefore not "What is the Slovenian per-diem rate?" but "Which regime applies to this employer and this trip?" Finance and payroll teams need that answer before they can decide whether a claimed amount is reimbursable, non-taxable, or partly taxable.

Meal treatment adds another layer. If meals are provided during the trip, the per-diem allowance may need to be reduced under the applicable rules. Partial-day logic matters as well because shorter domestic trips can fall into different allowance bands. Foreign travel should be treated as a separate rule set rather than an extension of the domestic table: the reviewer needs the destination-specific schedule, the relevant currency logic, and the correct effective date for that trip.

Kilometrina should also be handled as a documented reimbursement topic, not as a standalone number lifted from a blog post. A defensible mileage claim usually depends on prior authorization to use a private vehicle, a route that makes sense for the stated business purpose, and a distance basis the reviewer can understand. In practice, the potni nalog should let a reviewer see why the car was used, which route was taken, and how the mileage figure was derived.

Which receipts, tax checks, and supporting evidence belong with the claim

The completed potni nalog is only one part of the reimbursement file. Reviewers usually expect the document to be backed by the evidence that explains the trip and supports the amounts claimed: accommodation invoices, transport tickets, toll slips, parking receipts, and any other records the employer's travel policy or tax treatment requires.

Those attachments should reconcile with the form itself. Dates should line up with the authorized trip window. Destinations and route evidence should make sense against the stated purpose of travel. Claimed transport, lodging, and incidental costs should be traceable to actual documents rather than reconstructed from memory. If the file does not reconcile internally, the reviewer has to decide whether the issue is clerical, policy-related, or serious enough to affect reimbursement.

Tax treatment is why this support package matters so much. When a reimbursement fits within the applicable rules and non-taxable norms, it can usually be handled as a travel reimbursement. When the amount exceeds those norms or the support is too weak to justify the treatment, the excess may have to be treated as taxable income through payroll. Meal treatment matters here as well, because per-diem amounts may need to be reduced when meals were already provided as part of the trip.

The accounting side should not be ignored either. Receipts attached to a travel file may still raise separate recordkeeping and invoice-validity questions, especially for accommodation or transport documents that feed into expense and tax records. That is why related controls such as Slovenia fiscal verification of invoices and Slovenia VAT records requirements can become relevant when the supporting documents around a potni nalog also have to stand up as accounting evidence.

How a potni nalog moves from approval to reimbursement

Operationally, the document usually follows a predictable path. First, the employer authorizes the trip and issues the travel order. Then the travel takes place. Afterward, the employee completes the settlement portion of the form and submits it with receipts, mileage support, and any explanation needed for exceptions. Many employers expect that submission to happen promptly after return so receipts, meal treatment, and payroll cutoffs can still be checked against fresh evidence. A reviewer then checks the file, confirms the calculations, resolves any advance payment, and passes the approved outcome into reimbursement or payroll handling.

Each step has its own control question. Before travel, the key issue is whether the trip, destination, dates, and transport method were properly approved. After travel, the reviewer checks whether the completed form matches the evidence, whether meal adjustments or mileage calculations are reasonable, and whether any claimed amount falls outside the non-taxable treatment the employer expects to apply.

The handoff structure varies by organization. In some businesses, HR initiates the travel order while finance or accounting reviews the completed claim. In others, payroll is deeply involved because allowances and taxable excesses need to be reflected correctly in the pay run. That is why the potni nalog often connects to the broader payroll reconciliation process, not just to reimbursement approval in isolation.

What matters most is that the file remains reviewable from start to finish. A potni nalog works well when a third party can see the authorization, the trip details, the support package, the calculation logic, and the final payment treatment without having to guess how the pieces fit together.

Electronic potni nalog workflows, controls, and retention

An electronic potni nalog can work just as well as a paper one if it preserves the substance of the record. The key requirements are not nostalgia for paper forms but evidentiary integrity: the same trip fields, the same approval trail, the same timestamps, the same attached support, and a clear record of how the settlement was completed.

That is why digital approvals and signatures matter in practical rather than cosmetic terms. A reviewer needs to see who approved the trip, when that approval happened, what version of the claim was reviewed, and which receipts or route evidence were part of the final file. If those elements are preserved, the organization can run the process electronically without losing control over reimbursement review.

Structured capture becomes especially useful once travel orders and attachments start moving across systems. Teams that digitize this area usually want searchable fields for traveler name, dates, destination, allowance calculations, and linked receipts so the file can be reviewed, posted, and retrieved consistently inside broader financial document automation workflows. In that context, Invoice Data Extraction can help with the supporting-document side of the process by extracting structured data from receipts and expense claims into Excel, CSV, or JSON for downstream review and recordkeeping.

Retention is the last control layer. Many organizations keep the completed potni nalog package for around ten years under broader accounting-document retention practice, although the governing policy should follow the rules that apply to the employer's records. Whatever the exact retention schedule, the practical standard is the same: the completed travel order, approvals, and supporting receipts should remain traceable and retrievable for as long as the organization may need to justify the reimbursement.