eFaktura workflow
Prepare the invoice once. Keep validation, signing and status in the same flow.
Smetko connects the business document to the evolving UJP eFaktura process, while qualified-certificate signing remains on the user's machine through Smetko Potpis.
How the work moves
From business document to returned status
- 01
Prepare the outgoing invoice from the connected sales and partner record.
- 02
Validate the payload and resolve missing business data before submission.
- 03
Sign locally with the qualified certificate through Smetko Potpis.
- 04
Submit through the configured UJP flow and retain the returned status in Smetko.
Smetko Potpis
The signing key stays with the user.
Smetko prepares the canonical payload. Potpis performs the qualified-certificate operation locally and gives Smetko only the signature and certificate serial needed for forwarding.
See Smetko PotpisCurrent official context
The national process is still being tested and refined.
UJP announced a third testing phase in June 2026, including a web test application. Smetko follows the official materials and does not present an unconfirmed mandate date as settled fact.
Read the official UJP testing announcementPrepare your invoicing workflow for what comes next.
See Smetko Potpis or book a demo of the connected invoice and signing flow.