UJP JSON payload
Macedonian-spec compliant. All required fields (partners, addresses, line items, VAT, currency).
UJP is rolling out e-Faktura in phases. Merot Finance is built around the published API model: certificate, JSON payload, JWS signature, testing, status, and a digital trail for every invoice.
Macedonian-spec compliant. All required fields (partners, addresses, line items, VAT, currency).
Upload your .p12/.pfx certificate once. Every invoice is signed automatically.
No manual upload once API exchange is active. API call, delivery confirmation, and status sync.
See the PDF invoice and UJP payload before test or production sending. One-click corrections.
Pending → Accepted/Rejected. History per invoice. Rejection messages straight from UJP.
By tax ID (EDB) → company name, address, VAT status, primary activity auto-filled.
.p12/.pfx with password. Encrypted, stored under Settings → e-Faktura.
As usual — partner, line items, VAT. The system fills the e-Faktura fields automatically.
PDF + UJP payload preview. Validate before sending a test or production e-Faktura.
Email with PDF, UJP status, and optional payment link (Monri/Stripe).
Yes. UJP officially started pilot testing in 2026 and is moving the system toward phased implementation. Merot Finance follows the UJP technical model: API, JSON payload, JWS signature, certificate, and document status.
A qualified digital certificate from an accredited Macedonian CA (KIBS or Macedonian Telekom). .p12 or .pfx format.
The exact error message (field, line item, reason) is shown. Fix and send again — no new invoice number needed.
Yes — foreign customers can be invoiced with a standard PDF invoice and applicable UJP tax indicators where required.
Yes — status syncs from the UJP API and is saved on the invoice, with history for accepted, rejected, and cancelled documents.
Yes — every send attempt, signature, and status change is retained for 10 years. Excel export for audits.
Ask about demo, pricing or a specific workflow. This is the same Merot contact form.