Documentation for integrations covering lookup, validation, sending, receiving, webhooks and audit output. Describes the recommended deployment approach, security rules and integration scenarios.
Available endpoints may differ by environment and deployment type. Production keys belong on the server, not in the browser. The public frontend must not call private production routes directly.
Private API keys belong on the server, not in browser JS. Sending and retries should use an Idempotency-Key.
Endpoints account not only for sending, but also receiving, approvals, response codes, evidence packs and the archive flow.
An integrator needs a short quickstart, payload examples, retry rules, webhooks and a clear distinction between test and prod mode.
For enterprise clients, a fully automated flow matters: the system accepts a feed, validates it, converts it, sends it, and returns the final artifacts back into the archive or ERP.
Integration accounts for a JSON/XML feed, batch processing and secure channels like SFTP. The Interface Control Document can take the form of an OpenAPI/Swagger spec supplemented with mapping and retry rules.
On error, the system should return a detailed reason, rule ID, XML node and a recommended fix. The source system remains the fix source, and Slovak e-Invoicing Centre returns the result via webhook.
Enterprise clients often need to get back the final XML and PDF, have a portal to review processed invoices, and prepare their own branded PDF template.
Contract for the feed, mapping, error catalog, versioning and checklist for enterprise teams.
Delivery lifecycle, callback payloads, signature model, retries and event ordering.
Return of the final XML/PDF, custom template bundle and archive handoff into the client's internal system.
Promotion checklist, test payloads, idempotency guardrails and cutover rules before going live.
Rule IDs, severity, XML path, remediation hints and an owner model for enterprise triage.
Naming conventions, manifests, ACK files, partial retry and traceability for corporate feeds.
EU data residency, audit logs, retention and the enterprise operating model for technical review.
SSO, lifecycle and role governance for corporate tenants and integration teams.
Pay-as-you-go API, plans for accountants, and enterprise middleware in one commercial model.
Separation of admin, accountant and developer permissions, including API keys and audit roles.
Priority list of systems for the Slovak market with compatibility status. Import already works with POHODA XML, KROS exports, Money/MRP CSV and ISDOC; more direct connectors are added over time.
Technical baseline for edge headers, CORS, payload controls, auth and enterprise hardening.
Status page, webhook delivery log, correlation IDs and incident reporting for enterprise support.
e-Discovery bundle for clients who need an XML/PDF/log export for a given period.
Rules, PO matching, disputes and smart intake for more advanced automation scenarios.
Factur-X, clearance and roaming as a multi-country direction for further integrations.
Partner lookup in the form 0245:2020123456. Output: registration, name, supported documents, readiness status and recommended channel.
XML validation returns rule_id, the severity of the issue, and a fix recommendation. In a local overview it should always be clearly marked that this is not a production result.
Excel, CSV or prepared exports as input, and a ZIP with ready XML or a batch report as output. Suitable for a gradual transition without a new ERP.
Preparation and sending of a document via a connected certified partner, with emphasis on Idempotency-Key, transmission ID, evidence and subsequent response events.
Overview of ACK, NACK, rejection and other events, including their business meaning and a processing timeline.
Bundle for audit or internal review: payload, validation summary, response events, rule version and processing timeline.
The examples below serve as a sandbox or server-side integration pattern. The production URL, authorization and available endpoints depend on the chosen deployment.
The transport layer confirmed delivery to the network or recipient.
Transport or business rejection. Typically opens the remediation flow.
Conditional acceptance, timeout, or a workflow data conflict.
The document was closed out and marked for archiving with an evidence pack.
The final XML and PDF are ready to be returned to the client's internal archive or billing system.
Low-trust input should go through human review, not autonomous sending.
Peppol ID, tax ID, IBAN and partner identifiers need to be validated before a batch.
An ACK does not mean business acceptance. The workflow should wait for the next response event.
For a partner who isn't ready, return a recommended channel, not just a "partner not found" message.