North Macedonia E-Invoicing (e-Faktura): SAP Implementation Considerations

North Macedonia e-Faktura is moving through active UJP testing. For SAP teams, waiting for final enforcement pressure is risky because the groundwork takes time: master data, tax indicators, digital certificates, connectivity, status storage, inbound AP, cancellation logic, and user procedures.

Executive Snapshot

Question	Practical answer for SAP teams
What is live now?	UJP testing is active during 2026, including API testing, expanded document functions, tax indicator testing, and web application testing (as of July 2026).
Authority model	UJP describes e-Faktura as a state, centralized system where companies communicate directly with UJP without legal intermediaries.
What is the SAP risk?	Building too late, or building against moving pilot assumptions without controlled mapping, certificate handling, status storage, and regression testing.
Where S4FN fits	Reviewing e-Faktura readiness against SAP source documents and reporting workflow. Exact deployment, integration method, and delivery scope to be confirmed during technical review.
Best next step	Start readiness now and finalize production details as official UJP scope and API specifications firm up.

In This Article

• Regulatory view
• Why this is an SAP lifecycle problem
• Preparation checklist
• FAQ

Regulatory View

The Ministry of Finance and UJP launched the e-Faktura pilot in January 2026. Later UJP testing phases added API functions for downloading, accepting, rejecting, and cancelling documents, plus tax indicator testing and web application testing.

Official materials point toward mandatory implementation and gradual full rollout. SAP teams should still validate the final legal scope, dates, penalties, production endpoint details, onboarding rules, and transaction coverage against current UJP and legal sources before go-live decisions.

e-Faktura also does not replace VAT/DDV reporting. SAP tax codes, UJP tax indicators, accounting entries, invoice totals, and statutory reporting controls still need to reconcile.

Why This Is an SAP Lifecycle Problem

A North Macedonia invoice is not complete from an SAP control perspective just because a payload was sent. The company must know whether UJP validated it, which identifier was assigned, whether the recipient accepted or rejected it, whether cancellation is still allowed, and whether the authority evidence matches SAP billing, FI, tax, and reporting data.

• Source data: invoice type, document date, customer/supplier data, values, VAT/DDV, currency, payment, and references must be mapped correctly.
• Security: certificate ownership, configuration values, signing responsibility, renewal, and environment separation need clear controls.
• Lifecycle: accepted, rejected, pending, cancelled, and failed states require user action paths.
• Inbound AP: incoming invoice IDs, payloads, PDFs, acceptance, rejection, and optional AP posting controls need a business process.

Preparation Checklist

• Confirm North Macedonia company codes, branches, tax registrations, and invoice processes.
• List invoice types, credit/debit documents, returns, cancellation scenarios, intercompany, exports, B2G/B2B/B2C, and inbound AP requirements.
• Clean customer and supplier tax IDs, legal names, addresses, domestic/foreign buyer rules, and classifications.
• Map SAP tax codes to the UJP tax indicators currently available in testing.
• Define certificate ownership, digital signing procedure, serial registration, renewal responsibility, and incident contacts.
• Design where the authority identifier, status, rejection reason, cancellation reference, payload, PDF, and logs will be stored.
• Prepare test scenarios for standard VAT, reduced VAT, exempt, non-taxable, reverse charge, exports, rejection, cancellation, inbound download, and accepted-invoice corrections.

How S4FN Can Help

S4FN can support North Macedonia e-Faktura readiness through a regulatory scope review and SAP fit-gap: which SAP documents fall in scope, how invoice data maps to the required format, and how status and evidence return to SAP. How the delivered workflow builds, validates, and tracks documents is described on the North Macedonia e-invoicing integration for SAP page. The exact integration method, deployment model, and delivery scope are confirmed during technical review. For the wider compliance picture, see the country and mandate coverage hub.

FAQ

Is North Macedonia e-Faktura already live?

Testing is live. UJP launched pilot testing in January 2026, expanded API and tax indicator testing in mid-2026, and introduced web application testing during 2026. Mandatory production scope and dates should be confirmed against current UJP sources.

Are test invoices legally valid?

UJP states that test invoices use real registry data but do not have legal or tax effect during the test phase.

What is the main SAP risk?

The main risk is building too late, or building against assumptions that change. SAP teams should prepare data, mapping, signing, status storage, and monitoring while keeping legal scope and API specifications under change control.

Should SAP teams rely only on the web application?

The web application is useful for testing and lower-volume scenarios. SAP-driven companies should still evaluate API or SAP-native integration to avoid duplicate entry, inconsistent status tracking, and weak source-document traceability.

Disclaimer

This article summarizes public information available as of July 2026 and is written for SAP implementation planning. North Macedonia e-Faktura legal scope, deadlines, penalties, digital signature rules, API specifications, production onboarding, VAT reporting, and local statutory requirements should be validated with official UJP materials and local tax or legal advisors before implementation.

Primary Sources and Verification

Verified on: 10 July 2026. Pilot and test materials do not by themselves establish a general statutory production obligation.

• UJP — e-Faktura pilot information
• UJP — e-Faktura testing information