Tools for Slovak e-invoicing without language mixing
A single English entry point for validation, viewing, partner readiness, receive-side control and integration handoff. Some tools are still Slovak-first internally, but this hub explains the workflow in English and routes users deliberately.
Start here
These tools help identify whether a document, partner or internal process is ready before any production delivery is attempted.
PEPPOL validator
Upload UBL XML and inspect structure, business rules and remediation hints before handoff.
Open validator → ViewerPEPPOL viewer
Read XML invoices in a human-readable layout for review, approval and accounting discussion.
Open viewer → ReadinessReadiness checker
Check Peppol ID, ERP export, receive-side readiness, validation gaps and action plan.
Run readiness check → LookupPartner lookup
Check whether a counterparty appears ready before relying on a live network process.
Open lookup →Which tool should I use?
The same company may need different tools at different stages. Start with the smallest useful control, then move toward workflow and integration only when the evidence is clear.
| Situation | Use this first | Status | Reason |
|---|---|---|---|
| You have one XML file | PEPPOL validator + viewer | Ready | Confirms whether the document can be read, explained and corrected. |
| You are not sure partners are ready | Partner lookup + readiness checker | Core | Prevents blind send-and-fail workflows. |
| You handle many clients | Accountant dashboard + readiness audit | Workflow | Turns one-off checks into a multi-client operational view. |
| You receive e-invoices | Inbox + message intelligence + audit trail | Workflow | Received documents need exceptions, responses and evidence, not only viewing. |
| You integrate ERP/API | Developer docs + ICD + webhook contract | Core | Defines data contracts, statuses, retries and artifact return before automation. |
When one document is not enough
Real e-invoicing operations need batch checks, receive-side handling, responses and evidence.
Batch validator
Process multiple documents and separate common rule issues from one-off exceptions.
Open batch validator → InboxInvoice inbox
Receive-side workflow for documents, exceptions and accounting actions.
Open inbox layer → ResponsesMessage intelligence
Decode status messages and failures without forcing business users into XML detective work.
Decode responses → AuditAudit trail and evidence
Keep document events, decisions and artifacts traceable for accounting and internal control.
Open audit layer →For accountants, ERP teams and API handoff
These areas matter when the workflow grows from a free check into a managed operating model.
Accountant dashboard
Track many clients, readiness gaps and exception queues from one operational view.
Open dashboard → DeveloperDeveloper documentation
API, mapping, events, batch feeds and system integration entry points.
Open docs → ContractICD and OpenAPI
Technical contracts for feed formats, rule IDs, error catalog and versioning.
Open ICD → OnboardingGuided onboarding
Discuss whether your workflow belongs in manual tools, accounting operations, API or certified AP handoff.
Discuss onboarding →Language and readiness status
This English page is a reviewed routing layer. Some destination tools still use Slovak-first UI or shared product modules; they are linked deliberately because the workflow is real, not because every destination is already final translated content.
Guide, tools hub and error entry points
These pages are maintained as English-facing content and avoid mixed Slovak/English navigation.
Validator, viewer and readiness tools
Product utilities may use shared UI while the English hub explains when and why to use them.
Full EN tool interfaces
The next step is deeper 1:1 content and interface review for the most-used tools before DE/PL/HU expansion.