e‑Invoice Gateway Self‑Hosted (Enterprise)

Maximum control, security, and integrations aligned with your IT policies.

In Brief

e‑Faktura Gateway Self‑Hosted (Enterprise) enables companies to automatically prepare, sign, submit, and track their e‑invoices to the Public Revenue Office (UJP) - regardless of which ERP they use.

The solution acts as a secure integration layer (Gateway) that converts your invoices into a UJP‑compliant structure, submits them via API, receives the EUID and status from UJP, and maintains a complete audit trail - all within your controlled environment.

With the Self‑Hosted model, the entire process runs inside your systems and under your IT policies.

Architecture & Product Stack

Self‑Hosted (Enterprise) uses the same LSM e‑Invoice product stack that powers all solutions in the portfolio: LSM e‑Invoice App, LSM API Connector, and LSM Reusables, running on top of Business Central (On‑Prem or Online under another CSP) as the runtime environment. All communication with UJP is executed on this foundation.

The architecture follows the five‑layer model:

UJP e‑Faktura Platform - the national centralized platform for clearance and validation.
LSM API Connector (Connectivity Layer) - authentication, certificates, HTTPS, JSON, retry logic.
LSM e‑Invoice App (Transformation Layer) - transforms invoices to UJP‑compliant structures, submits them, stores EUID.
Business Central Runtime (Gateway Layer) - the BC execution environment used by Gateway, ensuring full isolation and control.
Customer Operational Layer - dashboards, logs, statuses, archives, and daily operations.

This model ensures stability, security, and future‑readiness, with minimal changes required when UJP expands its API capabilities (status/inbound).

Who is this for?

Self‑Hosted (Enterprise) is the right choice if your organization:

Has strict IT and security governance (firewall rules, own SSO/Entra ID, CAB processes, restricted external access).
Uses complex or international ERP systems: SAP ECC/S4HANA, Oracle E‑Business Suite/Fusion, Dynamics 365 Finance & Operations, or custom/industry ERPs.
Already has a Microsoft Entra ID / Azure tenant under another CSP (e.g., Microsoft 365/Azure with a non‑LSM CSP). In this case, the project is classified as Self‑Hosted due to lifecycle and governance rules.
Uses Business Central but does not want a Built‑In implementation (IT policies, processes, integrations, or licensing require a Gateway model, even if BC already exists).

Why Self‑Hosted?

Full ownership of infrastructure and control
Highest security level (no shared runtime environments)
Broadest integration options (API, SQL, Dataverse, middleware - on your terms)
Enterprise governance (aligned with group CAB, compliance, and audit requirements)
Ready for the national e‑Faktura timeline - pilot from 01.01.2026 and expected mandatory adoption from Q3 2026 (phased)

Scope of Delivery

1) Installation in your infrastructure

Deployment of the LSM e‑Invoice App, LSM API Connector, and LSM Reusables, configuration of UJP test/prod, and alignment with your certificates and network policies.

2) Excel Templates (default – always included)

This is the standard input method in the Self‑Hosted package: structured templates (Invoice + Credit Memo), built‑in validations, fastest time‑to‑production, and lowest IT effort.

3) UJP Submission & Response
Automatic submission to UJP (JSON), reception and storage of EUID, status/message, timestamp, and QR link, with full audit trail and logs.

4) Training & Launch Support
Role‑based training (Operations + Admin) and a 60‑day launch support add‑on, combined with your selected SLA tier.

Integrations note: Advanced integrations (API, SQL staging for BC On‑Prem, Dataverse, middleware) are not part of the standard scope and are handled as separate projects/agreements.

Daily operation with the e‑Faktura Gateway

1) Data input

By default: the user uploads Excel files (Invoices / Credit Memos) into the Gateway.
With integrations (outside standard scope): depending on the agreed level, the Gateway automatically retrieves data from the ERP (API / SQL / Dataverse).

2) Validation & preparation

Validation of mandatory fields, alignment with UJP structures, and e‑invoice VAT logic. If needed, reference documents could be attached.

3) Submission to UJP (JSON)

Secure API connection to test/prod.

4) Storing UJP results

EUID, status/message, timestamp, QR link - stored on the document.

5) Logs & corrections

Full audit trail with options for resubmission/corrections.

6) Inbound (purchase) invoices

Until UJP publishes inbound/status APIs, use the UJP portal/desktop; once available, automated retrieval will be enabled.

Key Benefits

Strongest model for security, control, and compliance
No changes required in your existing ERP
Integrations on your IT terms - not limited by partner hosting models
Ready for the 2026 milestones and future UJP API extensions (status/inbound) without re‑implementing the process

Assumptions & Prerequisites

Your infrastructure or a 3rd‑party cloud
Valid UJP certificate(s) and access to test/prod onboarding steps
ERP → Excel exports (default)
Additional integrations are contracted separately
SLA Core or higher (Core / Plus / Prime / Prime+)

What’s not included

Development in SAP/Oracle/F&O and middleware (PI/PO, SOA, MuleSoft) beyond defined integrations
Business Central custom development unrelated to e‑Invoicing
ERP reorganization
Power BI and advanced reporting (available as add‑ons)

Contact

I'm always looking for new and exciting opportunities. Let's connect.

info@mysite.com

123-456-7890