Electronic invoice in Cyprus
Understand Cyprus’s voluntary e-invoicing framework, public-sector reception requirements, Peppol standards and the impact of ViDA from 2030.
Cyprus has no e-invoicing mandate — not for suppliers to the public sector, not for domestic B2B, and not for B2C. What exists is the receiver-side obligation required by EU law: public authorities must be able to receive and process e-invoices conforming to EN 16931. Suppliers are not obliged to send them.
That makes Cyprus the mirror image of the countries elsewhere on this site. There is no clearance, no reporting platform, no national accreditation and no local presence requirement. For a certified Peppol Access Point it is one of the easiest markets in Europe to serve — and the single date that matters is not Cypriot at all. It is 1 July 2030.
A short timeline, because Cyprus has done the minimum the EU required and stopped there.
The reception obligation under Directive 2014/55/EU took effect for central public bodies.
The Cypriot law transposing Directive 2014/55/EU was adopted.
Local government, public academic institutions and semi-governmental organisations came into the reception obligation. See B2G.
Structured e-invoicing and digital reporting become mandatory for cross-border B2B transactions within the EU. This is EU law rather than a Cypriot initiative — but it is the date that will change how Cypriot businesses invoice.
Member states operating domestic real-time transaction reporting must align those systems with the EU model. Cyprus has no such system, so unless one is introduced, this deadline is inapplicable to it.
There is no announced Cypriot B2B mandate — no published date, no formal public consultation and no EU derogation request. The Ministry of Finance and the Tax Department have stated intentions in the direction of ViDA, and the EU country profile mentions a long-term ambition to intensify work on mandatory B2B and B2C e-invoicing. Any roadmap showing a specific Cypriot date is speculation.
This is the one obligation Cyprus actually has, and it is worth stating precisely because it is routinely misread. The EU country profile records the B2G mandate as no — meaning businesses are not required to send e-invoices to the public sector. It does not remove the duty on contracting authorities to receive and process EN 16931-compliant e-invoices. Those are two different obligations pointing in opposite directions.
One honest caveat about maturity: e-invoices in the Cypriot public sector are currently processed manually. That is not tax clearance and not automated continuous control — and it means the benefit a supplier gets from sending electronically is interoperability, not faster payment through automation.
No mandate in either. Domestic B2B e-invoicing is voluntary by agreement between the parties, and no official date for a mandatory domestic B2B regime has been published. B2C is the same: ordinary VAT, receipt and accounting obligations apply, but no structured e-invoice is required.
Companies may therefore use Peppol, EDI, PDF, email or any other channel they agree on, provided the general VAT invoice requirements are met — and, for an electronic invoice, provided authenticity of origin, integrity of content and legibility are ensured with the recipient's acceptance.
For exports outside the EU there is likewise no Cypriot e-invoicing mandate. Ordinary VAT, customs and export documentation rules apply. Peppol may be used where a counterparty supports or requires it — but it is a commercial choice, not a Cypriot compliance channel.
Cyprus is best described as an interoperability and post-audit model. Peppol and gov.cy are used as infrastructure channels, not as a system of prior tax authorisation.
For domestic B2B and B2C there is no continuous transaction control of any kind. For intra-EU B2B the future regime will be set by ViDA from 2030 — an EU model, not a Cypriot clearance system.
Cyprus has implemented EN 16931 for public procurement and has not introduced a national CIUS or any local extensions on top of the European standard. The country follows the Peppol BIS Billing 3.0 CIUS. For a provider already sending to other EU public sectors, this is as close to zero additional work as a country gets.
For B2G a standalone PDF is not an EN 16931 e-invoice, because the standard presupposes structured machine-readable XML. A PDF can accompany the invoice as a visualisation or attachment, but it does not replace the structured XML in the B2G process.
For B2B and B2C, where no mandate exists, a PDF or email invoice remains perfectly usable under the general VAT rules — with the recipient's acceptance and with authenticity of origin, integrity of content and legibility ensured.
The relevant scheme for identifying Cypriot participants in Peppol is EAS 9928 — Cyprus VAT number. General schemes such as 0088 (GLN) may also be used where the parties agree, but no separate mandatory Cypriot EAS based on the companies register was identified.
Because the VAT number is the address, validating it before registering a participant is worth building into onboarding — the Tax Department publishes a VAT number validation service, linked under Resources.
Peppol is not the only permitted channel, but it is the key interoperable one for B2G. Suppliers may send through the national platform or through a Peppol Access Point, and according to the EU country profile all public bodies — including local government, public academic institutions and semi-governmental organisations — are connected to Peppol Access Points.
No dedicated Cyprus Peppol Authority was identified in the official sources. OpenPeppol states that it acts as the Peppol Authority in jurisdictions where no separate national authority exists — which is the position that applies here.
Because Cyprus has no domestic mandate, ViDA is not one date among several — it is the date. From 1 July 2030 the digital reporting requirements apply to relevant cross-border B2B transactions inside the EU, based on structured e-invoicing. By 1 January 2035 member states with existing domestic real-time transaction reporting obligations must align those systems with the EU model and standards.
Two practical consequences for a Cypriot business. First, the 2035 alignment deadline is currently inapplicable to Cyprus, since there is no domestic real-time system to align — unless one is introduced before then. Second, nothing about ViDA makes a paper or PDF invoice invalid for domestic Cypriot VAT deduction today.
The useful way to think about the intervening years: a Cypriot company that adopts Peppol now for its public-sector and willing B2B counterparties is not gaining a compliance benefit — it is doing the 2030 migration early, at its own pace, rather than under a deadline shared with every other business in the union.
Nothing beyond Peppol certification. No indication of a separate Cypriot accreditation comparable to the Slovak digitálny poštár, the Colombian Proveedor Tecnológico or Australian Peppol accreditation was found in the official sources. The model rests on Peppol Access Points and gov.cy, not on locally licensed operators.
One narrow exception in practice: a supplier that chooses to use the gov.cy portal rather than Peppol may need portal credentials or authorisation. That is a portal access matter for the supplier — it is not a licensing requirement on the Access Point.
VAT books and records in Cyprus must generally be retained for at least six years. Because there is no clearance platform holding a copy of anything, the whole burden sits with the business — there is no state archive to fall back on and no validation response to retrieve later.
Six years also comfortably outlasts the gap to ViDA. An archive designed now for structured invoices will still be the one in use when 2030 arrives.
Because Cyprus has no supplier-side e-invoicing mandate, no dedicated penalty scale for failing to issue an e-invoice was identified. Stating one would be inventing it.
In B2G it is operational and contractual rather than fiscal. If a particular public buyer or tender requires an e-invoice, failing to provide one can mean the invoice being rejected, payment being delayed, or a breach of contract terms. That risk attaches to the contract, not to the tax code.
The general regime is unaffected. Under the Cyprus VAT rules published for the One Stop Shop, for example, a late or unsubmitted VAT return carries €100, and late payment carries an additional 10% of the VAT due. These are reporting and payment sanctions — they have nothing to do with any e-invoicing clearance obligation.
An electronic invoice is not currently the only lawful basis for deducting input VAT in Cyprus. With no domestic B2B mandate, the right to deduct depends on holding a correct VAT invoice and meeting the substantive conditions for deduction — not on whether that invoice happened to be a structured e-invoice.
Once ViDA applies to intra-EU B2B from 1 July 2030, the structured e-invoice becomes part of the mandatory EU invoicing and reporting workflow for those transactions. That is a future regime. It does not mean a paper or PDF invoice is invalid for domestic Cypriot VAT deduction today.
Cyprus needs no national module. What it needs is a properly certified Access Point and a plan for 2030:
9928 with the Cyprus VAT number, and 0088 GLN where counterparties use itCyprus has done what Directive 2014/55/EU required and no more. Public authorities have been able to receive EN 16931 e-invoices since 2019 and 2020; suppliers have never been required to send them; and there is no domestic B2B or B2C mandate, no clearance, no reporting platform and no announced date.
Technically it is as plain as Europe gets: EN 16931 with no national CIUS, Peppol BIS Billing 3.0 in practice, EAS 9928 on the Cyprus VAT number, and no accreditation, local entity or mailbox required of a service provider.
Which makes the planning question a different one from most countries. The work is not compliance — it is adoption. Public-sector delivery through Peppol today, and the intra-EU B2B side ready before 1 July 2030, when ViDA stops making it optional.