e-Faktura is North Macedonia's UJP e-invoicing system for electronic invoice exchange: a proprietary JSON format, signed as a JWS with a qualified certificate — not UBL/EN 16931.

When does e-Faktura become mandatory?

The law has not been adopted yet (October 2026), so the voluntary phase planned for 01.10.2026 did not start. The draft makes it mandatory for VAT payers from 01.04.2027, then phased in through 01.01.2028 for everyone; the dates may move.

Do I need a digital certificate?

Yes — a qualified electronic signature (QES) in your name. Merot Bridge keeps it on your own device and signs locally; the key never leaves.

Yes. Merot Bridge runs identically on Windows, macOS and Linux — most signing tools are Windows-only.

What happens when UJP changes the specification?

Merot absorbs the change behind the API. Your integration keeps working; breaking changes only ship in a new version, per the versioning policy.

Is there a free trial?

There are no free trials or free plans. There is a sandbox for testing, included with every account.

How long are invoices archived?

10 years, hosted in Frankfurt (EU) or in North Macedonia — your choice. UJP itself keeps them only 2 years.

Can I storno or correct an invoice?

Yes — with a storno/correction reason (docStorno 1/2) and a reference to the original EUID, fully built into the API.

Does pricing depend on the number of client companies?

Not per company — per document, across your whole account. The Vendor plan is built for exactly this: many client companies under one account.

Yes — official SDKs for TypeScript and C#, plus code samples in 4 more languages (cURL, Python, PHP, Java).

Available now · For developers and software houses

e-Faktura API for UJP — issue and receive e-invoices from any software

Build once, stay compliant. When UJP changes the e-Faktura specification, formats or rules, Merot absorbs the change behind a stable, versioned API — your integration keeps working.

Get started Get API keys

A sandbox is included for testing before production.

POST /v1/einvoicesexample · sandbox

curl https://api.efaktura.merot.com/v1/einvoices \
  -H "Authorization: Bearer $MEROT_API_KEY" \
  -H "Idempotency-Key: inv-2026-000481" \
  -H "Content-Type: application/json" \
  -d '{
  "clientReference": "inv-2026-000481",
  "documentType": "100",
  "buyer": {
    "taxNumber": "4012009123456",
    "name": "Купувач ДОО"
  }
}'

→ 202 Accepted

{
  "id": "einv_01J9Z4M2N3P4Q5R6S7T8U9V0",
  "status": "queued",
  "clientReference": "inv-2026-000481",
  "totals": {
    "net": "10000.00",
    "vat": "1800.00",
    "gross": "11800.00"
  }
}

Returns 202 immediately; poll GET /v1/einvoices/{id} or use webhooks until UJP assigns the euid and QR link.

Windows · macOS · Linux

10-year archive

Frankfurt or Macedonia — your choice

Support in MK / SQ / EN

How it works

Electronic invoicing (e-Faktura) over an API — from your software to UJP

01 · youYour softwarePOST /v1/einvoices with a simple JSON — header, parties, lines, VAT.

02Merot APIValidates against UJP's rules and the buyer registry before it goes any further.

03Merot BridgeSigns locally with your own qualified certificate — on Windows, macOS or Linux.

04UJPReceives it, queued against rate limits; we retry when needed — you don't track any of it.

05Archive + inboxEvery document, kept 10 years. Incoming invoices flow back into the same API.

An incoming invoice from your supplier? Accept or reject it before the 10th of next month — after that it is auto-accepted.

Benefits

Built to survive every UJP change

Build once, stay compliant

When UJP changes the specification, formats or rules, Merot absorbs the change behind one stable, versioned API. Breaking changes only ever land in a new API version — never unannounced.

Every document type

Every UJP e-invoice document type, including storno and correction (docStorno 1/2), with a reason code and a reference to the original.

Validation before UJP

A full UJP rule check and buyer-registry pre-flight, before the document ever leaves.

An inbox with deadlines

Incoming invoices in one place, with an alert ahead of the 10th-of-next-month deadline.

A 10-year archive

UJP itself keeps documents only 2 years; the law requires 10. Merot keeps them for 10, on every plan.

Webhooks, sandbox, 6 languages

Status and inbox events as webhooks, a sandbox against UJP's own test system, code samples in 6 languages.

Your certificate never leaves

Merot Bridge signs locally on your own device — on Windows, macOS AND Linux. Most tools are Windows-only.

Comparison

Build it yourself vs. Merot

Area	Build it yourself	With Merot
UJP JSON and document types	You track every UJP change yourself	Kept current behind one versioned API
Qualified signing (JWS)	Your own PKCS#11/token integration, per OS	Merot Bridge — ready on all three; the certificate never leaves your device
Rate limits & retries	Build your own queue and backoff logic	Handled for you
Storno / correction	Implement the docStorno rules yourself	Built in, with reason codes
Incoming-invoice deadlines	Track the 10th-of-month rule yourself	Inbox + deadline alerts
10-year archive	Build and maintain WORM storage	Included on every plan, hosted in Frankfurt or Macedonia, your choice

Regulation

According to the proposed e-invoicing law

The draft law (ENER, August 2026) has not been adopted, so the voluntary phase planned for 01.10.2026 did not start; the system is still in testing. The dates below follow the draft and may move during the government and parliamentary procedure.

01.10.2026

Voluntary phase (did not start)Planned in the draft, but the law was not adopted in time; no new date has been announced. Once it opens, registering means issuing exclusively through the system.

01.04.2027

Mandatory for VAT payersIncluding public enterprises and state/municipal-owned companies.

01.07.2027

Mandatory for non-VAT legal entitiesAny legal entity performing economic activity.

01.10.2027

Mandatory for budget usersBudget users, state/municipal non-profits, the central bank.

01.01.2028

Mandatory for everyoneAnyone performing transactions must issue and receive through the system.

Developer experience

Built for integrators

5-minute quickstart

Your first document in the sandbox, with a real code example.

A sandbox for testing

Test against a simulator or directly against UJP's own test system, without real documents.

Webhooks

einvoice.submitted/accepted/rejected, inbox.received and deadline alerts — signed, with retries.

OpenAPI + SDKs

A full OpenAPI specification; official SDKs for TypeScript and C#.

cURLNode.jsPythonPHPC#Java

Versioning →

e-Faktura API for UJP — issue and receive e-invoices from any software

Electronic invoicing (e-Faktura) over an API — from your software to UJP

Built to survive every UJP change

Build once, stay compliant

Every document type

Validation before UJP

An inbox with deadlines

A 10-year archive

Webhooks, sandbox, 6 languages

Your certificate never leaves

Build it yourself vs. Merot

According to the proposed e-invoicing law

Built for integrators

5-minute quickstart

A sandbox for testing

Webhooks

OpenAPI + SDKs

Per-document pricing, at any volume

Directly to the Merot team

Email

Contact form

Languages

Frequently asked questions

For context around e-Faktura

Get your API keys