B2G PEPPOL — public e-invoicing since 2019

In Cyprus, e-invoicing is mandatory only in the public sphere (B2G — business to government). Since April 2019, every public buyer must be able to receive an electronic invoice compliant with the European standard EN 16931, transmitted over the PEPPOL network (Pan-European Public Procurement OnLine — the EU's standardised exchange rail). There is no B2B e-invoice mandate to date: between private companies, adoption remains voluntary.

History — from Directive 2014/55/EU to Law N.158(I)/2019

The Cypriot story of public e-invoicing is above all one of disciplined EU-law transposition, with no national gold-plating. Directive 2014/55/EU required every member state to ensure, by 18 April 2019 at the latest, that its contracting authorities could receive and process electronic invoices compliant with the common EN 16931 standard. Cyprus transposed this obligation through Law N.158(I)/2019, without adding a universal issuance mandate or an Italian-style clearance platform.

2014       | Directive 2014/55/EU — the EU requires every contracting authority
           | to be able to RECEIVE an electronic invoice compliant with the
           | European standard EN 16931. Transposition deadline: 18 April 2019.
           |
2017       | EN 16931 is published by CEN. Cyprus, like every member state,
           | must align with this common semantic model.
           |
2019       | Law N.158(I)/2019 — the Cypriot transposition. Every public buyer
           | (government, local authorities, hospitals, universities) must accept
           | an EN 16931 invoice. Effective date pinned to 18 April 2019.
           |
2019-2020  | The Treasury of the Republic (Γενικό Λογιστήριο) operates a central
           | PEPPOL access point and a receiving portal. Cyprus joins OpenPEPPOL
           | as a de facto PEPPOL Authority through the Treasury.
           |
2023-2026  | No B2B mandate. B2G e-invoicing remains mandatory on the receive
           | side; e-invoice issuance by public suppliers spreads but is not
           | legally imposed on all. ViDA alignment in preparation.

That choice reflects the country's size (~920,000 inhabitants) and the priority placed on European interoperability rather than a proprietary system. Instead of building a national platform, Cyprus plugged directly into the pan-European PEPPOL infrastructure, already battle-tested.

Governance — Treasury + DITS

Two actors structure the setup. The Treasury of the Republic (Γενικό Λογιστήριο της Δημοκρατίας) operates the state's central PEPPOL access point and the receiving portal for invoices addressed to the public sector; it acts as a de facto PEPPOL Authority for the government perimeter. The Department of Information Technology Services (DITS) provides the technical backbone (hosting, integration with FIMAS, the state financial system).

Supplier registration and onboarding go through a certified PEPPOL access point — either the Treasury's, or a third-party private operator (Pagero, Tradeshift, Storecove, etc.) declared in the SMP. The model stays "4-corner": sender → access point → access point → receiver, with no mandatory passage through a central tax platform.

Schema — PEPPOL BIS Billing 3.0 + EN 16931

The accepted format is the PEPPOL BIS Billing 3.0 profile, which implements EN 16931 semantics in UBL 2.1 syntax. In practice, an invoice is an XML document signed by the sending access point and routed over AS4. The routing address uses the Cyprus VAT number under the PEPPOL identifier scheme ICD 9933.

<?xml version="1.0" encoding="UTF-8"?>
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2">
  <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>
  <cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>
  <cbc:ID>INV-2026-00412</cbc:ID>
  <cbc:IssueDate>2026-06-16</cbc:IssueDate>
  <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
  <cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>

  <cac:AccountingSupplierParty>
    <cac:Party>
      <cbc:EndpointID schemeID="9933">CY10123456X</cbc:EndpointID>
      <cac:PartyTaxScheme>
        <cbc:CompanyID>CY10123456X</cbc:CompanyID>
        <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
      </cac:PartyTaxScheme>
      <cac:PartyLegalEntity>
        <cbc:RegistrationName>Limassol Trading Ltd</cbc:RegistrationName>
        <cbc:CompanyID>HE123456</cbc:CompanyID>
      </cac:PartyLegalEntity>
    </cac:Party>
  </cac:AccountingSupplierParty>

  <cac:AccountingCustomerParty>
    <cac:Party>
      <cbc:EndpointID schemeID="9933">CY10987654Y</cbc:EndpointID>
      <cac:PartyLegalEntity>
        <cbc:RegistrationName>Treasury of the Republic of Cyprus</cbc:RegistrationName>
      </cac:PartyLegalEntity>
    </cac:Party>
  </cac:AccountingCustomerParty>

  <cac:TaxTotal>
    <cbc:TaxAmount currencyID="EUR">190.00</cbc:TaxAmount>
  </cac:TaxTotal>
  <cac:LegalMonetaryTotal>
    <cbc:TaxExclusiveAmount currencyID="EUR">1000.00</cbc:TaxExclusiveAmount>
    <cbc:TaxInclusiveAmount currencyID="EUR">1190.00</cbc:TaxInclusiveAmount>
    <cbc:PayableAmount currencyID="EUR">1190.00</cbc:PayableAmount>
  </cac:LegalMonetaryTotal>
</Invoice>

Cyprus vs Mediterranean neighbours

Cyprus sits at the opposite end from the continuous transaction control (CTC) model adopted by Italy and Greece, staying on a minimal B2G setup.

Adoption — B2G mandatory, B2B voluntary

• B2G on receipt: mandatory. Every Cypriot contracting authority must accept an EN 16931 invoice since April 2019. This is a receive-capability obligation, not a universal issuance mandate.
• B2B: voluntary. No law mandates e-invoicing between private companies. Large groups (retail, pharma, shipping) use it for efficiency, via EDIFACT/EANCOM or PEPPOL, but with no legal compulsion.
• Retention: invoices (paper or electronic) must be kept for 6 years under VAT Law N.95(I)/2000 and Registrar of Companies bookkeeping obligations.
• Digital maturity: Cyprus ranks among the member states with still-low B2B e-invoice adoption, but with fully operational PEPPOL infrastructure on the public side.

Common pitfalls

• Believing a B2B mandate exists. There is none in Cyprus. Sending a B2B invoice "because it's mandatory" is a scoping error — it is mandatory only towards the public sector, and only on the buyer's receive side.
• Confusing receipt and issuance. The directive requires the public buyer to be able to receive EN 16931. It does not require every supplier to issue that format; a supplier may, depending on the contract, stay on other channels as long as the buyer accepts them.
• Wrong identifier scheme. The Cypriot PEPPOL address relies on ICD 9933 (CY VAT). Using the Registrar of Companies number (HE…) as the PEPPOL endpoint breaks routing.
• Forgetting the CustomizationID. Without the urn:cen.eu:en16931:2017#compliant#…billing:3.0 identifier, the public receiver rejects the document as non-compliant with PEPPOL BIS.

Cross-links

• Cyprus hub — full view
• VAT (ΦΠΑ) regimes — 19 / 9 / 5 / 0%
• TIC + CY VAT + Registrar of Companies
• Tax Department — TAXISnet + Ariadni
• ViDA — Cyprus alignment 2030
• EUR-Lex — Directive 2014/55/EU
• OpenPEPPOL — network and specifications
• Treasury of the Republic of Cyprus