PEPPOL Slovakia — DXC Authority, DXC + POSAM Access Points

Slovakia joined PEPPOL in 2018 with a PEPPOL Authority hosted by DXC Technology Slovakia (Bratislava). The Slovak network is built on two live Access Points (DXC, POSAM) and is used for B2G via slovensko.sk (eFaktúra) as well as for cross-border B2B flows, particularly automotive (Volkswagen, Kia, Stellantis, JLR).

History — from 2018 joining to BIS Billing 3.0

Slovakia made a strategic choice in 2018: entrust the PEPPOL Authority function to a private operator (DXC Technology Slovakia) rather than a public agency. This model, shared notably with Ireland (DPER), enables a quick start without creating a dedicated public body. The downside is commercial dependency, which forced MIRRI SR to formalise a 2021-2026 framework contract with DXC to secure the mission.

text peppol-sk-timeline.txt

2014       | OpenPEPPOL AISBL founded, transition from the LSP CIP-ICT
           | project 2008-2012. Brussels-based, multilateral governance.
           |
2017       | First Slovak Access Points accredited by OpenPEPPOL,
           | under host PEPPOL Authorities (DE / AT initially).
           |
2018       | Slovakia is granted its own PEPPOL Authority: DXC
           | Technology Slovakia (Bratislava) — national equivalent
           | of SE (DIGG), FR (DGFiP), DE (KoSIT) authorities.
           |
2019       | POSAM joins the network as an operational Access Point,
           | alongside DXC. Coverage of the Slovak market.
           |
2020       | PEPPOL BIS Billing 3.0 profile stabilised, used for
           | the eFaktúra slovensko.sk integration. ICD 0143 (IČO)
           | confirmed as the primary routing identifier.
           |
2023       | B2G eFaktúra mandate in force — slovensko.sk becomes
           | the largest PEPPOL consumer on the Slovak side,
           | operating as a receiver Access Point for the State.
           |
2024-2025  | Cross-border flow growth: Czechia, Austria, Germany
           | (Volkswagen Bratislava → Wolfsburg headquarters via
           | PEPPOL AS4). Poland driven by neighbouring KSeF.
           |
2026       | PEPPOL 5-corner model + PEPPOL CTC discussions —
           | Slovakia observer thanks to its FRSR pilot.

Governance — PEPPOL Authority + OpenPEPPOL

Three governance layers interact:

OpenPEPPOL AISBL (Brussels) — owns the BIS specifications, the profiles, the central SML. Multilateral governance (78 Authorities in 2026).
Slovak PEPPOL Authority = DXC Technology Slovakia — national relay: accreditation of Slovak Access Points, national usage policy, liaison with MIRRI SR for B2G flows.
Access Points (DXC, POSAM) — technical operators, provide the AS4 interface and the SMP, sign end-customer contracts (company / authority).

Technical schema — AS4, SMP, SML

PEPPOL Slovakia follows the standard 4-corner model: sender → sender AP (C2) → receiver AP (C3) → final receiver (C4). Routing relies on the SML → SMP → AS4 endpoint lookup:

text peppol-as4-message.http

POST /as4 HTTP/1.1
Host: ap.dxc.sk
Content-Type: multipart/related; boundary="MIMEBoundary"; type="application/soap+xml"

--MIMEBoundary
Content-Type: application/soap+xml; charset=UTF-8

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
               xmlns:eb="http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/">
  <soap:Header>
    <eb:Messaging>
      <eb:UserMessage>
        <eb:MessageInfo>
          <eb:Timestamp>2026-06-15T10:14:00Z</eb:Timestamp>
          <eb:MessageId>uuid:8f4d-2026-0091@dxc.sk</eb:MessageId>
        </eb:MessageInfo>
        <eb:PartyInfo>
          <eb:From>
            <eb:PartyId type="urn:fdc:peppol.eu:2017:identifiers:ap">
              POP000123
            </eb:PartyId>
          </eb:From>
          <eb:To>
            <eb:PartyId type="urn:fdc:peppol.eu:2017:identifiers:ap">
              POP000456
            </eb:PartyId>
          </eb:To>
        </eb:PartyInfo>
        <eb:CollaborationInfo>
          <eb:Service>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</eb:Service>
          <eb:Action>busdox-docid-qns::Invoice</eb:Action>
        </eb:CollaborationInfo>
      </eb:UserMessage>
    </eb:Messaging>
  </soap:Header>
  <soap:Body/>
</soap:Envelope>

Slovak Access Points

Access Point	HQ	Specialty	Target customer
DXC Technology Slovakia	Bratislava	Authority + corporate AP	Large enterprises, State, public sector
POSAM s.r.o.	Bratislava	Managed services AP + ERP integration	SMEs, mid-market, healthcare
Comarch Slovakia	Bratislava (PL subsidiary)	AP via Comarch EDI	Retail, manufacturing
Pagero Slovakia	Cross-border (SE HQ)	Cross-border AP, multi-country hub	Multinationals, automotive
SovaNET	Bratislava	Local VAN + PEPPOL bridge	Local SMEs

Adoption — B2G mandatory, B2B voluntary

~6M B2G invoices/year via slovensko.sk eFaktúra (2024) — almost all routed via PEPPOL BIS 3.0.
~3M B2B PEPPOL invoices/year estimated (actual volume not published, DXC + POSAM + Comarch + Pagero aggregation) — mostly cross-border to Austria, Germany, Czechia, Poland.
Flagship sectors: automotive (VW Bratislava, Kia Žilina, Stellantis Trnava, JLR Nitra), electronics (Foxconn, Samsung Galanta), pharma (Zentiva, GSK), retail (Lidl, Kaufland, Tesco SK).
#1 cross-border: Germany — automotive manufacturer flows (payment Wolfsburg → SK suppliers), followed by Austria, Czechia, Poland.

Common pitfalls

Confusing PEPPOL with eFaktúra. eFaktúra = B2G service on the Slovak State side (slovensko.sk). PEPPOL = interoperable transport network used BY eFaktúra. eFaktúra receives through its PEPPOL endpoint, but the PEPPOL network itself is much broader than B2G alone.
Choosing an AP without SK coverage. All EU PEPPOL APs can technically send to slovensko.sk, but in practice support for Schematron rejections (Slovak rules) varies. Prefer an AP with a Bratislava presence if Slovak B2G volumes are significant.
ICD 0143 vs 9914. ICD 0143 = IČO (national). ICD 9914 = intra-EU community VAT (originally IT VAT, then extended). BIS Billing 3.0 mainly uses 0143 for the SK part and 9914 for VAT.
Believing PEPPOL = signature. PEPPOL AS4 uses a transport-level WS-Security signature, but that is not an eIDAS qualified electronic signature. For invoices requiring a qualified signature (rare in SK B2B), separate handling is required.
Ignoring the SMP. To receive PEPPOL invoices, a recipient must be published in an SMP with the supported profiles. A company not published cannot receive even if the sender attempts delivery.

Foundations

Standards

Flagship messages

Tools