First-time setup

Until you enter an EDB, the app opens on the Settings screen. Once you save it, the app opens on Outgoing.

Taxpayer and environment

1. In Environment, choose Test while you try out the app. Documents sent to the test environment have no legal effect. While the test environment is selected, a blue box above the page reminds you of this; it goes away when you switch to production.
2. In EDB, enter the tax number (EDB) of the company that issues invoices (13 digits).
3. In eUJP ID, enter the identifier you have in the UJP e-Faktura system.
4. Leave Serial number format and Manual serial number empty or as they are. You only need them if UJP doesn’t recognise the certificate (see Common problems).

Production is meant for real invoices, but the UJP production addresses haven’t been verified yet. Use it once we confirm them.

Certificate

5. In Signing certificate, choose where the certificate is read from: a file, a USB token or macOS Keychain. The details are in Certificate and unlocking.
6. Press Save settings.

Unlock

7. Click Certificate at the bottom left of the menu. In the window that opens, enter your PIN or password and press Unlock.
8. Press Test signature. If it says the signature is valid, everything is ready.

At the top, next to the logo, you always see which environment you’re working in. At the bottom left, below the menu, you see which EDB is set, whether the certificate is unlocked, and the difference between your clock and the UJP clock.

Language

Change the language from the selector below the app name: Macedonian, English, Albanian, Serbian or Turkish. The change applies immediately, without a restart. Data that UJP returns, such as status names and code list entries, stays as UJP has it.

Where settings and documents are stored

Everything is in one local SQLite database: on Windows %APPDATA%\mk.rid.efakt\efakt.db, on macOS ~/Library/Application Support/mk.rid.efakt/efakt.db, on Linux ~/.config/mk.rid.efakt/efakt.db. It holds the companies and their settings, and every document the app has read from or sent to UJP: statuses, content, PDFs, history, acceptances and rejections. When UJP doesn’t respond, the app shows the locally stored documents. The CLI uses the same database. The PIN and password aren’t stored anywhere.