WaveFlow for Slovenian SMBs: AI for DDV and FURS

Slovenian SMB owners and finance teams pick WaveFlow because it automates invoice extraction, DDV preparation, and FURS eSlog 2.0 XML export with local Gemma 4 inference — so invoices never touch US cloud APIs and the audit trail survives a FURS inspection.

The standard pitch sells AI accounting as 'replace your računovodja' — wrong. For Slovenian SMBs the legally signed-off accountant stays; WaveFlow replaces the 14 hours/month of manual invoice keying and DDV-O assembly that sits between the s.p. owner and that accountant, not the accountant themselves.

If you run a normirani s.p., a navadni s.p., or a small d.o.o. in Slovenia, the bottleneck is not your računovodja. It is the 80 to 300 supplier PDFs sitting in your inbox every month, the DDV-O period that always lands on a Friday, and the reverse-charge line you booked last quarter that you cannot defend if FURS asks why. WaveFlow exists to remove that work — invoice extraction, DDV preparation, and FURS eSlog 2.0 XML export — without sending a single invoice PDF to a US cloud API.

This page is for SMB owners and finance teams who already searched for 'AI računovodstvo' or 'AI za DDV' and bounced off vendors that either (a) wanted €200+/month per seat, (b) processed your data in us-east-1, or (c) produced outputs your accountant refused to sign. WaveFlow runs on local Gemma 4 inference, bills pay-per-use via WaveCredits, and keeps a citation-backed audit trail your računovodski servis will actually accept.

The problem

I am retyping 80 to 300 supplier invoices a month into Minimax or Pantheon because every OCR tool I have tried still misses Slovenian VAT IDs, reverse-charge markers, and eSlog line items.

WaveFlow extracts supplier name, davčna številka, net/VAT/gross, reverse-charge flags, and full line items from Slovenian and EU invoices into a structured record you import directly into your accounting system.

Every DDV-O and RIP-O period I am assembling samoobdavčitev and EU B2B reverse-charge entries from scratch, and the generic AI tools silently mis-classify them.

WaveFlow groups extracted invoices by VAT treatment (domestic 22%/9.5%/5%, EU B2B reverse-charge, samoobdavčitev, oproščene) and produces a DDV-O draft your accountant reviews instead of rebuilds.

When FURS asks why an invoice was booked to a specific account, I have screenshots and email threads, not citations.

Every WaveFlow field links back to the exact page and bounding box of the source PDF, so the audit trail is the document itself — defensible in an inspection.

Reconciling NLB, SKB, or NKBM TRR statements against invoices takes hours because payment references rarely match invoice numbers.

WaveFlow matches bank line items to invoices using amount, supplier, date window, and reference fragments — flagging only the residue for human matching.

I do not want to push invoice PDFs containing customer PII through ChatGPT or US-hosted SaaS, and I cannot answer my accountant when she asks where that data was processed.

WaveFlow Public runs inference on EU-hosted Gemma 4; WaveFlow Enterprise runs the same product inside your perimeter or on a WaveNode appliance — in both cases, the answer to 'where did the data go' is one jurisdiction, in writing.

Why WaveFlow fits

Native eSlog 2.0 XML export — the same schema FURS eDavki consumes — so DDV-O submissions do not need a second format conversion step.
Handles the three Slovenian legal forms (normirani s.p., navadni s.p., d.o.o.) with the right VAT and bookkeeping treatment per entity, not a one-size-fits-all US accounting template.
Pay-per-use via WaveCredits (100 credits / $1) — no €200/month seat, no annual contract. An s.p. processing 40 invoices a month pays for 40 invoices a month.
Citation-backed extraction: every booked value points to the page and region of the source PDF, which is what a certified računovodski servis needs to sign off.
GDPR and ZVOP-2 posture is explicit — Public tier processes on EU infrastructure, Enterprise tier processes inside your perimeter, and neither sends invoice PII to US cloud LLM APIs.
Bank reconciliation against NLB, SKB, NKBM, and other SEPA TRR statements — not just US bank feeds.

In production

A Ljubljana-based IT consultancy d.o.o. with ~120 supplier invoices/month, mixed domestic and EU B2B, filing DDV-O monthly through an external računovodski servis.

Invoice keying time dropped from roughly 14 hours/month to under 2 hours of review. The accountant kept sign-off authority but stopped retyping; DDV-O drafts now arrive structured by VAT treatment.

A normirani s.p. consultant invoicing EU clients with reverse-charge and 40–60 incoming supplier invoices/month, previously using a US cloud OCR tool until raising it with their accountant.

Moved processing to WaveFlow Public on EU infrastructure. Monthly cost dropped below €15 in credits; reverse-charge classification stopped landing in the wrong DDV-O row.

A small manufacturing d.o.o. with two finance staff, Pantheon as the system of record, and a FURS inspection looking back 24 months at booking decisions.

Re-ran the prior period's invoices through WaveFlow to produce per-invoice citation trails. Inspection questions resolved in days because each booked value pointed back to its source PDF region.

When this is the right call

Pick WaveFlow Public if you process roughly 20+ supplier invoices/month and want pay-per-use credits with EU-hosted inference and no monthly seat.
Pick WaveFlow Enterprise if you are a d.o.o. with internal compliance or sector rules (regulated industry, public-sector supplier, defence subcontractor) that require processing inside your own perimeter.
Stay with manual keying only if your invoice volume is under ~10/month — the credit cost is trivial either way, but the ROI is sharper above 20.
Run hybrid (WaveFlow extraction + računovodski servis sign-off) if your accountant is the legal filer — this is the default and the contrarian point of this page.
Do not pick WaveFlow if you want a tool that files DDV-O without a human accountant in the loop. That is not what this product does and not what Slovenian law assumes.

Frequently asked

Does WaveFlow replace our računovodski servis?

No, and it is not designed to. Your accountant remains the legal signatory on DDV-O and annual filings. WaveFlow replaces the manual invoice keying, classification, and DDV-O assembly that sits between you and your accountant — so they review structured data instead of retyping PDFs.

Can WaveFlow export directly to eDavki in eSlog 2.0 XML?

Yes. WaveFlow produces eSlog 2.0-compliant XML for invoice records and DDV-O drafts. Your accountant or finance team submits through eDavki as they do today; the difference is the data is already structured, classified, and citation-linked to the source PDF.

Where exactly is our invoice data processed?

On the Public tier, WaveFlow runs on EU-hosted infrastructure with Gemma 4 inference — no invoice PII is sent to US cloud LLM APIs. On the Enterprise tier, the same product is deployed inside your own perimeter, on Hetzner EU, or on a sealed WaveNode appliance. In both cases, the data-processing jurisdiction is documented for your GDPR and ZVOP-2 records.

What does it actually cost for an s.p. with ~60 invoices a month?

Billing is pay-per-use via WaveCredits (100 credits / $1). A typical s.p. workload of 60 invoices/month with DDV-O assembly lands in single-digit to low double-digit euros per month. There is no seat fee, no minimum, and no annual contract — if you skip a month, you pay zero.

Will my accountant accept WaveFlow output as a basis for signing DDV-O?

That is the design constraint. Every extracted field is linked to the exact page and region of the source PDF, which is the citation evidence a certified računovodski servis needs to defend a booking in a FURS inspection. We have built the audit trail around what accountants actually sign off on, not around what AI tools usually show.

How long does it take to start?

Public tier: minutes. Create an account at waveflow.wavenetic.com, top up credits, upload your first batch of invoices, and review the extracted output. Enterprise tier (perimeter or WaveNode deployment): typically 2–6 weeks depending on your accounting system integration (Minimax, Vasco, Pantheon, SAOP) and SSO requirements.

The takeaway

After reading, the reader can decide (a) whether their invoice volume justifies WaveFlow credits this quarter, (b) whether to run hybrid AI+računovodski servis or full AI handoff, and (c) how to keep FURS audit defensibility while routing zero invoice data through US clouds.