Status: pilot/test. No general statutory production go-live date was verified as of 10 July 2026. Scope and dates remain subject to final enacted law and UJP production rules.
North Macedonia E-Invoicing Integration for SAP
North Macedonia e-Faktura is moving through UJP testing and preparation for mandatory use. For SAP teams, the main work is not just sending a JSON payload; it is keeping SAP source documents, tax indicators, digital certificate handling, status evidence, inbound AP, cancellation, and exception handling under control.
S4FN can help SAP organizations prepare an SAP-aligned e-Faktura document process connected to UJP through a secure integration layer, while keeping the authority model centralized and without legal intermediaries. The exact integration method, deployment model, and delivery scope are confirmed with you during technical review.
At a glance
- What it is: Centralized e-invoicing via UJP (Public Revenue Office), no intermediaries
- Planned/expected scope: VAT-registered businesses, subject to final enacted law, dates and UJP production rules
- Authority: UJP (Public Revenue Office)
- SAP scope: SD, FI, tax indicators, digital certificates + Basis connectivity
- Key risk: Mandatory dates not yet final; UJP testing active as of July 2026
Evaluating North Macedonia e-Faktura for your SAP landscape? Pilot / testing phase
Answers to the questions most evaluation emails ask before you write one.
Landscapes assessed
SAP ECC and SAP S/4HANA; release, edition, installed components and country scenario are reviewed before any support commitment
Delivery model
Confirmed per product and landscape: an on-stack S4FN Add-on, a side-by-side S4FN extension on SAP BTP, or SAP Integration Suite connectivity
Commercial scope
Confirmed in the written proposal by country, legal entities, systems and usage scope
Engagement sequence
Scope review → landscape fit check → written implementation proposal
Get pricing and a 20-minute technical call
Quick Overview
| Area | What to know |
|---|---|
| Authority platform | e-Faktura, operated by the Public Revenue Office (UJP). |
| Rollout status as of July 2026 | UJP testing is active, including API testing, expanded functions, tax indicators, and web application testing. |
| SAP impact | UJP JSON mapping, tax indicator mapping, digital certificate parameters, status storage, cancellation, inbound AP accept/reject, and VAT reconciliation. |
| Where S4FN fits | Reviewing e-Faktura readiness against SAP source documents and reporting workflow, and shaping an SAP-aligned integration approach. Exact deployment and delivery scope to be confirmed during technical review. |
| Important caveat | An internal integration layer is a technical layer only. It is not a legal clearance intermediary in UJP’s centralized model. |
On This Page
- General SAP integration flow
- North Macedonia scope to validate
- Implementation workstream
- SAP readiness checklist
- FAQ
General SAP Integration Flow
A common target pattern keeps SAP as the source of truth and uses an integration layer as the managed technical route for UJP connectivity, security, monitoring, retry behavior, and response handling. The specific components and topology are confirmed per landscape during technical review.
- SAP ERP / S/4HANA: creates billing, FI, credit note, cancellation, and inbound AP source documents.
- Compliance workflow: validates source data, builds the UJP JSON, maps tax indicators, controls status logic, and stores evidence.
- Integration layer: routes payloads securely, with certificate/signing support patterns, credential isolation, monitoring, retry design, and endpoint separation.
- UJP e-Faktura: validates documents, returns status responses, and supports PDF/payload download, cancellation, incoming invoice search, accept, and reject functions where in scope.
- Status return: accepted, rejected, pending, cancelled, identifier, PDF/payload, response reasons, and audit files return to SAP.
North Macedonia Scope to Validate
UJP describes e-Faktura as a state, centralized system where companies communicate directly with UJP. A customer may still use an internal integration layer such as SAP Integration Suite or SAP BTP, but that layer is controlled by the taxpayer and does not create a separate legal intermediary.
| Decision point | SAP design implication |
|---|---|
| Potential rollout and transaction scope | Track final legislation, UJP onboarding rules, production endpoint readiness, penalties, and covered document types. |
| API versus web application | High-volume SAP environments should prepare API integration; portal use should be controlled as fallback or transitional processing. |
| Digital certificate model | Define certificate ownership, renewal, e-UJP user responsibility, serial/configuration control, and incident handling. |
| VAT/DDV reporting | Reconcile UJP tax indicators and invoice totals with SAP tax codes, accounting, VAT return, and statutory reporting requirements. |
Implementation Workstream
- Confirm regulatory status: mandatory dates, transaction coverage, production onboarding, penalties, and latest UJP technical guidance.
- Run an SAP fit-gap: company codes, document variants, tax indicators, customers/suppliers, payment references, certificates, inbound AP, and user roles.
- Design the integration route: SAP endpoint, integration flow, signing-support pattern, credentials, logging, retry, alerts, and test/prod separation.
- Configure the mapping: UJP JSON fields, tax indicators, status model, cancellation rules, evidence objects, and exception handling.
- Test realistic scenarios: standard VAT, reduced VAT, exempt, non-taxable, reverse charge, export, credit/debit, cancellation, inbound download, accept/reject, and VAT reconciliation.
- Prepare operations: finance cockpit use, rejected-document ownership, release-note monitoring, support triage, fallback procedure, and first-submission controls.
SAP Readiness Checklist
| SAP area | Review before build |
|---|---|
| Company code | North Macedonia legal entities, tax registration, EDB/VAT data, address, local numbering, delegated sender or signer identity. |
| Business partner | Customer and supplier tax IDs, legal names, addresses, foreign buyer rules, branch/subsidiary needs, and B2G/B2B/B2C classification. |
| Tax and payment | VAT/DDV indicators, exemptions, reverse charge, exports, due date, payment type, payment description, references, rounding. |
| Document lifecycle | Invoices, credit notes, debit notes, returns, cancellations, intercompany, advances, manual FI invoices, inbound AP. |
| Operations | Submit, resubmit, status check, PDF/payload display, accept/reject, cancel, background jobs, error queue ownership, and UJP update monitoring. |
FAQ
Is North Macedonia e-Faktura mandatory?
Official materials show active testing and preparation for mandatory implementation (as of July 2026). Final scope, dates, penalties, and production onboarding should be validated against current law and UJP guidance before go-live decisions.
Does North Macedonia use legal intermediaries?
UJP describes e-Faktura as centralized and without intermediaries. An internal integration layer can still be used for technical connectivity, but it is not a legal clearance intermediary.
What is the eID?
UJP materials state that a successfully validated digitally signed invoice receives a unique identifier. SAP should store this identifier with the invoice, response, status history, and audit evidence.
Does e-Faktura replace VAT reporting?
No. e-Faktura creates structured invoice-level data, but VAT return, accounting, tax code, and local statutory reporting obligations still require separate review and reconciliation.
DRC Sprint Country Compliance Pack
North Macedonia e-Faktura: connect requirements to SAP delivery
This pack connects e-Faktura readiness requirements to system evidence, architecture decisions, implementation work and operational controls.
What the pack connects
- 01Mandate controlsScope, scenarios, deadlines and exceptions
- 02SAP evidence checksRelease, component, configuration, data and process evidence
- 03Delivery assetsDecision records, test scenarios, work packages and operating controls
North Macedonia e-Faktura focus: pilot and mandate scope, UJP interface readiness, document mapping, authentication, response handling and rollout gates.
Discuss Your North Macedonia SAP Readiness
Review invoice flows, UJP onboarding assumptions, tax indicator mapping, digital certificate handling, integration readiness, and VAT control alignment while the model remains in pilot and testing. For the wider compliance picture, see the country and mandate coverage hub.
Disclaimer: This page summarizes public regulatory and technical information available as of July 2026. North Macedonia e-Faktura requirements, legal scope, deadlines, penalties, digital signature rules, API specifications, VAT reporting obligations, and production onboarding steps should be validated with UJP, official legal sources, and local advisors before implementation or go-live.
Primary Sources and Verification
Verified on: 10 July 2026. Pilot and test materials do not by themselves establish a general statutory production obligation.