e-Faktura API

Overview

The Merot e-Faktura API lets any software — accounting packages, ERPs, web shops, in-house invoicing tools — issue, receive and archive UJP e-Faktura (e-invoice) documents, without implementing UJP’s JSON, JWS signing, rate limits, status handling, storno/correction rules, the incoming-invoice deadline or the 10-year archive yourselves.

Under North Macedonia’s e-Faktura law, e-Faktura is voluntary from 1 October 2026 and becomes mandatory for VAT payers from 1 April 2027, then for all legal entities and budget users by 1 January 2028.

What it covers

• Issue every UJP document type the codebook supports — invoices, credit/debit notes, advances, storno and correction — with full field validation before anything reaches UJP.
• Receive an inbox of incoming e-invoices, with the 10th-of-next-month accept/reject deadline tracked for you.
• Archive every sent and received document — original JSON, signed JWS, PDF rendering and status trail — for the legally required 10 years.
• Webhooks for every status change, so you don’t have to poll.
• Sandbox against UJP’s own test system, or Merot’s simulator when you don’t have a test token yet.

Signing

A qualified electronic signature has to be created on the certificate holder’s own device — this API never holds your signing key. Two modes are supported: Merot Bridge (a desktop app for Windows, macOS and Linux) or an SDK signing worker you run on your own server. See Signing: Mode A vs Mode B.

Who it’s for

• Software vendors embedding e-Faktura for many client companies.
• Businesses running their own web shops, distributors or in-house ERPs.
• Accounting firms issuing and receiving on behalf of clients.

Pricing

Per-document monthly plans, plus a per-document vendor plan for software vendors serving many client companies. See e-Faktura API pricing. Sandbox developer accounts are free; any production use needs a paid plan — Merot has no free trials or free plans.