Slovenia Reverse Charge Invoice Requirements Under Article 76a

The Slovenia reverse charge invoice requirements under ZDDV-1 Article 76a mean that, for certain domestic supplies, including construction-related work and other listed sectors, the supplier issues the invoice without charging Slovenian VAT and the recipient becomes liable for VAT instead. In practice, a Slovenia reverse charge invoice should not be treated like a normal domestic VAT invoice with a different label. It is a different processing path: no Slovenian VAT charged by the supplier, a clear reverse-charge indication on the invoice, verification of the recipient's VAT ID, and then entry into the Article 76a reporting workflow.

For an AP or accounting team, the operational sequence is simple: scope decision first, invoice review second, PD-O reporting third. First, confirm the transaction falls within the domestic Slovenia Article 76a reverse charge mechanism. Second, review the invoice for the essentials, especially that the supplier has not charged Slovenian VAT, the invoice includes a reverse-charge note, and the buyer details support the VAT treatment. Third, make sure the transaction is routed into PD-O in eDavki by the last working day of the following month. If the recipient VAT ID or reported amount later turns out to be wrong, the correction also runs through that same PD-O workflow rather than being handled as a standalone invoice note with no reporting follow-up.

This guide focuses on the domestic Article 76a mechanism in Slovenia and the invoice and PD-O workflow that follow from it.

When Article 76a Applies, Especially in Construction

Article 76a is a domestic, listed-supplies reverse-charge rule, not a catch-all for every Slovenian invoice with unusual VAT treatment. In practice, you should only move a transaction into the Article 76a workflow when three points are true: the supply is taxable in Slovenia, the supply falls within the categories covered by Article 76a, and the recipient is the Slovenian VAT-identified taxable person that becomes liable for the VAT.

A practical way to decide is to run this sequence:

1. Confirm the supply is domestic in Slovenia. If the transaction is really an import, an intra-EU acquisition, or a cross-border service handled under a different reverse-charge rule, do not treat it as Article 76a.
2. Confirm the supply is inside Article 76a scope. The clearest and most common English-language examples usually involve construction-related work tied to immovable property, such as building work, repairs, cleaning, maintenance, reconstruction, and demolition. That is why a typical Slovenia construction reverse charge invoice often comes from a subcontractor, site contractor, installer, or maintenance provider working on a specific project or property.
3. Confirm the recipient is the liable party under this mechanism. Article 76a is built around the customer becoming the VAT payer, so the workflow only fits when the buyer is the right Slovenian VAT-identified taxable person for that domestic supply.

Construction is the easiest place to see the rule in action because project work naturally creates the patterns AP teams recognize: subcontracting chains, site-specific scopes of work, and service descriptions tied to a building, plant, office fit-out, or other immovable property. A concrete frame subcontract, demolition before refurbishment, facade repair, or building-systems installation can all point toward Slovenia Article 76a construction services when the supplier is invoicing a Slovenian VAT-identified business on a domestic job. If your team handles other jurisdictions too, the same operational mindset shows up in our guide to construction reverse-charge invoice checks.

At the same time, the rule is broader than construction services alone. One official non-construction example is an opted-to-tax real estate sale where the buyer accounts for VAT under Article 76a. So the test is not "is this a construction company invoice?" but "is this one of the domestic supplies that Article 76a actually names?" If the invoice sits outside familiar construction work, confirm the category against official Article 76a guidance before you post it.

That distinction matters because over-application creates filing errors. A supplier can operate in construction and still issue invoices that do not belong in the Article 76a flow, such as charges outside the listed domestic scope or transactions governed by a different VAT rule. The safest AP habit is simple: do not force a transaction into the Slovenia reverse charge invoice workflow just because no VAT is shown or the fact pattern feels unusual. The Slovenia Article 76a invoice requirements only become relevant after you have confirmed that the underlying domestic supply really sits inside Article 76a.

How Article 76a Differs From Other Slovenia Reverse Charge Cases

A lot of English guidance treats every Slovenia reverse charge invoice as if it followed one rule. That is the mistake finance teams need to avoid. A Slovenia Article 76a reverse charge case is a domestic mechanism for specific supplies made in Slovenia, most commonly construction-related work, between VAT-identified parties in Slovenia. A separate reverse-charge mechanism can apply when the supplier is not established in Slovenia and the Slovenian customer becomes the VAT payer for that reason. Both situations may be described as reverse charge, but they are not interchangeable.

The trigger is different. Under Article 76a, the first question is whether the supply itself falls into the domestic Article 76a scope. In the foreign-supplier scenario, the first question is whether the supplier is non-established in Slovenia and whether the transaction falls under that separate rule. A domestic construction subcontractor invoice and an invoice from a non-established foreign supplier can both arrive without Slovenian VAT charged, but the reason is different, so the workflow must be different too.

That distinction matters at document-review level. For a Slovenia reverse charge invoice under Article 76a, AP should validate the domestic scope, confirm both VAT IDs, check the reverse-charge wording, and route the document into the Article 76a invoice review and PD-O workflow. For a foreign-supplier case, your review starts with supplier establishment, VAT status, and the separate Slovenia reverse-charge rule for non-established suppliers. Do not copy Article 76a wording, coding, or PD-O assumptions across just because the invoice also says reverse charge.

If your team handles several jurisdictions, Germany's multi-scenario reverse-charge invoice rules show the same operational problem in another VAT system. The practical rule here is simple: if this is a domestic Article 76a supply, keep following the workflow in this guide; if it is a non-established foreign supplier case, stop and confirm the separate Slovenian mechanism before posting the invoice or sending it down an Article 76a reporting path.

What the Invoice Should Say and What AP Should Validate

For Slovenia reverse charge invoice requirements under Article 76a, AP should treat the document as a normal B2B invoice plus a reverse-charge control. In practical terms, the invoice still needs the ordinary data points described in SPOT invoicing guidance: invoice date, unique invoice number, supplier name and address, customer name and address, supplier VAT identification number, the customer's VAT identification number, a clear description of the goods or services, the supply date if different from the invoice date, and the taxable amount.

The extra Article 76a layer is the liability signal. Slovenia reverse charge invoice wording should make it clear that the buyer is liable for VAT, not the supplier. In practice, that means the document should contain a clear reverse-charge indication and a reference that points to Article 76a or otherwise shows that the supply is subject to reverse charge. Many teams look for wording along the lines of "reverse charge, Article 76a ZDDV-1, VAT payable by recipient." Treat that as an illustrative example rather than mandatory text. Your exact wording should follow your official invoicing guidance or advisor-approved standard. For a straightforward Article 76a invoice, Slovenian VAT should not be charged in the normal way. If the supplier mixes Article 76a items with ordinary VATable items on one invoice, those lines should be separated clearly rather than blended into one undifferentiated total.

Before booking, use this Slovenia Article 76a invoice requirements checklist:

• Scope check: The description of the supply should actually fit an Article 76a-type transaction, such as qualifying construction-related work or another listed domestic reverse-charge case, not a generic service description that leaves the VAT treatment unclear.
• VAT ID check: The recipient's VAT identification number matters because Article 76a works only when the customer is the kind of Slovenian VAT-identified taxable person that can be liable for the tax. Verify the number, not just its presence, using the FURS taxpayer lists.
• VAT treatment check: If the invoice shows Slovenian VAT as though it were an ordinary domestic taxable supply, stop and review. Under reverse charge, the supplier normally omits domestic VAT from the charge and the customer accounts for it.
• Wording check: The invoice should explicitly indicate reverse charge. Missing or vague wording is a common reason invoices get routed incorrectly.
• Document type check: Confirm whether you are looking at an invoice, an advance invoice, a credit note, or a correction document. A correction should not be booked as a fresh invoice just because the supplier reused the same project description.
• PD-O data check: Make sure the document contains the fields that will matter later for reporting and reconciliation: invoice number, invoice date, supply date, supplier and customer names, both VAT IDs, taxable amount, and a usable description of the work, property, or project.

Keep self-invoicing separate in your controls. Slovenian invoicing rules allow self-invoicing, but if the buyer issues the invoice on the supplier's behalf, the document should make that clear so nobody mistakes it for a standard supplier-issued invoice.

For higher-volume teams, the main risk is usually not one missing phrase but inconsistent capture across dozens or hundreds of invoices: supplier names entered three different ways, invoice dates in mixed formats, VAT IDs truncated, and credit notes posted as invoices. That is where invoice data extraction for VAT review becomes useful. Invoice Data Extraction can pull supplier and customer details, invoice dates, VAT IDs, document type, taxable amounts, and reverse-charge wording into a structured XLSX, CSV, or JSON output for review and export, with source-file and page references for verification before posting or filing.

Who Files PD-O, When It Is Due, and How Corrections Work

PD-O is the report that sits behind Slovenia's Article 76a reverse-charge workflow, and the non-obvious rule is this: the supplier files PD-O even though the recipient is the party liable for VAT. That filing obligation comes from Article 92a, which requires taxable persons in Slovenia to report Article 76a supplies for the calendar month in which those supplies were made, and to use the same monthly reporting track when prior-period data needs correction.

From an operations standpoint, the Slovenia PD-O filing deadline is simple: the report is submitted electronically through eDavki by the last working day of the month following the reporting month. The official PD-O filing instructions for Article 76a supplies make clear that PD-O is filed in eDavki, follows that deadline, and can attract fines if filing is late, missing, or inaccurate. If your AP team needs a Slovenia PD-O report guide, treat that deadline as a hard close-calendar control, not a soft tax follow-up item.

Corrections also need a disciplined workflow. If a prior-period Article 76a transaction was reported with the wrong value, the wrong VAT ID, or should not have been reported at all, the fix is routed through PD-O in the month when the correction is made, rather than handled outside the Article 76a reporting process. In practice, that means invoice capture, VAT ID validation, and monthly PD-O preparation have to reconcile cleanly, much like reverse-charge wording and DDV-04 reporting must line up in North Macedonia. If they do not, you risk late, incomplete, or inaccurate reporting, and that is where sanctions start to become a real month-end compliance problem.

---

A Month-End Checklist for Slovenia Article 76a Workflows

For month end, the safest way to handle Slovenia reverse charge invoice requirements is to run one short control sequence across the whole batch. This is most useful when you are reviewing construction-heavy or subcontractor-heavy invoices, but the same checklist applies to any domestic Slovenia reverse charge invoice that may fall under Article 76a.

1. Move unresolved invoices into an exception queue before filing. If Article 76a status, VAT ID status, wording, or document type is still unclear at month end, keep the invoice out of the filing population until someone with tax responsibility signs off. Close control starts with excluding uncertainty, not forcing it through.

2. Separate current-period supplies from corrections. Do not mix prior-period fixes, credit notes, or amended Article 76a invoices into the live-period population without labeling them. Put corrections in a separate queue, link each one to the original invoice, and record which period is being corrected before it flows into the same PD-O process.

3. Reconcile the reviewed batch to the PD-O working file. Compare the invoices approved under Article 76a against the reporting population and related VAT outputs. Look for duplicates, held invoices, items posted without Article 76a review, and invoices reviewed as Article 76a that never made it into the filing pack.

4. Check filing-pack completeness for every line. Make sure the team can trace invoice number, invoice date, supplier name, supplier VAT ID, recipient VAT ID, taxable amount, expected reporting period, and any correction flag from the review file into the PD-O support pack. If those fields do not reconcile cleanly, the batch is not filing-ready.

5. Keep an audit trail from invoice review to filing output. Retain the invoice image, the validation result, any exception note, the PD-O support extract, and evidence of who approved the treatment. The period is filing-ready only when every reported line can be traced back to a reviewed invoice and every excluded item has a documented reason.