Connect your ERP system to the Peppol network.
In one day.
We are the only digital postman in Slovakia offering a simple “socket” into the Peppol network for ERP systems. The ERP connects to Connector and no longer has to compose the solution endpoint by endpoint.
Connect your ERP system to the Peppol network in one day
how it works
Under the hood, everything is managed by our Enterprise API.
For Connector, we combined the most common integration steps into one flow. The ERP no longer has to compose the solution API call by API call: it sends a document to Connector and gets a clear result. Technically, it is still Enterprise API: validation, repairs, immediate send, outbox, status, inbound invoices, and evidence. Flow details are in the Connector documentation.
How it works
Enterprise API stays under the hood, ERP gets one managed flow
| Step | Flow part | Enterprise API separately | Connector flow |
|---|---|---|---|
| 01 | Receiver check | separate call and decision inside the ERP | Connector runs it in the right order |
| 02 | Document check | separate pre-send check, errors, and blocking states | one answer on whether the invoice can be sent |
| 03 | Repairs | custom logic for safe fixes and exceptions | repair report for developers and the ERP |
| 04 | Sending | separate send and retry handling | delivery through the same infrastructure |
| 05 | Outbox | custom queue, scheduling, and bulk sending inside the ERP | stage now and send later |
| 06 | Status and inbound | status, events, received invoices, and acknowledgements separately | one readable result for the ERP |
| 07 | Evidence | download envelope, history, and delivery evidence | the same documents stay available through the full API |
The ERP sends a document to Connector. Under the hood, Connector calls the Enterprise API steps and returns one clear result for sending, outbox, status, inbound documents, and evidence.
POST /api/v1/connector/sendPOST /api/v1/connector/outboxtest connection in one day
You can get the first test connection running in one day.
Once access is approved and data is prepared, our managed flow significantly shortens the path from an ERP system to the Peppol network.
Send prepares the invoice, checks the rules, returns a repair report, and only then releases the document for delivery.
Status, inbound invoices, and evidence can be read by the ERP through simple periodic requests. Acknowledging a received invoice stays separate so retry handling remains under the integrator's control.
Stage invoices now, send later: the outbox stores prepared documents, returns a repair report, and supports safe later or bulk sending.
POST /api/v1/connector/outbox
{
"items": [{
"externalId": "FA-2026-001",
"scheduledFor": "2026-06-04T08:00:00Z",
"payload": {
"receiverPeppolId": "0208:12345678",
"document": {
"invoiceNumber": "FA-2026-001",
"items": [{ "description": "Services", "quantity": 1, "unitPrice": 100 }]
}
}
}]
}without losing quality
Simpler for the integrator, same infrastructure underneath.
Connector covers roughly 90% of a common ERP integration on top of Enterprise API. It is not a cheaper version: the same validation, permissions, limits, audit, and evidence remain under it. When more detail is needed, you can move to the full Enterprise API.
Same authentication
Existing keys, permissions, limits, and firm isolation are reused.
One input instead of composing API calls
The ERP calls Connector. Connector runs the Enterprise API steps in the right order and returns one result.
No mandatory webhooks at the start
The ERP can start by periodically reading document status and inbound invoices.
Move to Enterprise API
When more detail is needed, the same document, login, and evidence remain available.
what is in the flow
Several services run behind the input, so the ERP does not have to compose them manually.
Connector is not just a new API call. It is an entry point into a managed flow that assembles the common Peppol integration work for the ERP system: preparation, validation, invoice queueing, sending, status, inbound documents, acknowledgement, and evidence.
ERP invoice
The ERP sends invoice data or ready UBL XML into one input.
Validation
Connector checks e-invoice rules before the document is sent.
Error repair
Shows safe fixes and clearly marks what the ERP must correct.
Peppol delivery
Finds the receiver and sends the invoice through the right delivery route.
Invoice outbox
The ERP can stage invoices now and send them later, individually or in bulk.
Inbound invoices
The ERP can fetch newly received invoices through simple reads.
Status and evidence
Same document, event history, and delivery evidence.
advantages over Enterprise API
Same infrastructure, less integration work.
Enterprise API remains for integrators who want to control every technical step. Connector is for ERP systems that want to safely send and receive Peppol invoices without composing the solution API call by API call.
| Difference | Enterprise API | ePošťák Connector |
|---|---|---|
| Number of calls | 10+ calls depending on what the ERP needs to compose | one main flow for sending and simple result reading |
| Implementation time | several weeks for a full Peppol integration | ERP connection in one day |
| Integrator responsibility | ERP handles step order, errors, retries, queueing, and status | Connector manages the flow and returns one response |
| Invoice lifecycle | pre-send check, send, outbox, status, inbox, ack, and evidence are composed separately | full invoice lifecycle in one managed Connector flow |
| Quality under the hood | permissions, limits, audit, validation, and evidence | same core, shorter integration surface |
| When detail is needed | full access to each technical step | same documents and keys, possible move to the full Enterprise API |
Not a SAPI replacement
Connector is ePošťák's fast path for ERP integration. SAPI remains available when the integrator needs the standardized Financial Administration contract.
Move to Enterprise API
If the simple connector is not enough, the integrator can move to detailed Enterprise API calls without changing keys or losing document history.
test connection
What are you waiting for? Try ePošťák Connect today.
If you build ERP or accounting software, we connect you to Peppol through Connector while Enterprise API, audit, limits, permissions, and delivery evidence keep running underneath.