← All projects

B2B portal

eOtpremnice

A portal for sending and receiving electronic delivery notes through an API key — no card reader and no ID card for every document.

Visit site ↗
eOtpremnice portal home screen with shortcuts for a new delivery note and receipt scanning

Problem

An electronic delivery note is filed with the state system, and access to that system runs through the qualified certificate held on a personal ID card. That means a card reader on the machine and that specific person present for every document. A company dispatching several times a day ties the whole process to one individual and their ID card — if they are out on site or off sick, dispatch stops. On top of that, every line item is retyped by hand, even though the goods have already gone through the fiscal register.

Solution

The company enters its own MFIN API key once and works through the portal from then on, without a reader and without an ID card for each document. A document is assembled in five steps, checked against the state validator before sending, and only then filed. Line items no longer have to be typed — scanning the QR code on the fiscal receipt pulls the items and quantities straight from the tax administration.

What was built

  • Company registration and entry of its own MFIN API key
  • User approval and licence issuing through the admin panel
  • Sending and receiving delivery notes and goods receipts
  • Five-step wizard — type, recipient, transport, items, review
  • Item import by scanning the QR code on a fiscal receipt
  • XML validation against the state validator before sending
  • Registers of drivers, vehicles and locations, so data is not re-entered
  • Switching between the demo and production MFIN environment
  • Support for excise goods
  • Overview of inbound and outbound documents with statuses and synchronisation

A delivery note carries quantities, not prices — but whether goods may leave at all depends on it. Which is why the most expensive part of that job was always that it hung on one person: whoever’s ID card sat in the reader.

The portal changes that by making the company, rather than a person, the holder of access. The API key lives in the system, encrypted, and belongs to the company. Anyone with an account can dispatch.

The second thing that is easy to overlook is item import. The goods have already passed through the fiscal register and are recorded exactly in the tax administration’s system — there is no reason for anyone to type them again. The QR code on the receipt is already there, printed. It only had to be read.

Result

Dispatch no longer depends on one person and their ID card — anyone with an account can do it. Items from a fiscal receipt arrive by scanning instead of retyping, and the validator check catches an error before sending, while it can still be fixed.

From the application

The items step, importing lines by scanning the QR code on a fiscal receipt
The QR code on a fiscal receipt points at the tax administration service, from which the portal pulls items and quantities itself.
Final step with document review and validity check
The check sends the XML to the state validator and creates nothing — an error shows while it can still be fixed.
Overview of inbound and outbound delivery notes and goods receipts with statuses
Inbound and outbound documents in one place, with status and synchronisation by period.
Admin panel, settings for a single user with licence and API key
The admin approves a company, sets the licence and picks the demo or production MFIN environment. The API key is stored encrypted.