Ireland's eInvoicing Deadline Is Not a Big-Company Problem. It Lands on You in 2028.

The eInvoicing changes Revenue has set out for Ireland are being read as a large-corporate story, and that reading is wrong. It is wrong in a way that will cost small suppliers real money, because the first obligation to arrive does not care how big you are.

Revenue confirmed phase one of its VAT Modernisation programme on 10 February 2026. The notice says that from 1 November 2028, VAT-registered large corporates must issue eInvoices and report a subset of that data to Revenue for domestic business-to-business transactions. Fine. That is a few hundred companies. Then comes the sentence underneath it: "From the same date, all businesses in Ireland must be able to receive structured eInvoices" ^[1].

All businesses. Not large ones. Not a category with a threshold attached.

I was reading that notice on the morning it went out, expecting a timeline I could file for later. That second line is the one that changes the job, and almost nobody has repeated it.

The obligation nobody has been told about

Think about what an invoice is in your business today. Somebody generates a document, attaches it to an email, and a person at the other end opens it and types the numbers into their system. Every part of that depends on a human being present.

A structured eInvoice removes the human. It is a data file, not a document, read by one system directly from another. Revenue's implementation paper puts it formally: eInvoicing is "the electronic transmission of structured invoices through an end-to-end digital process" ^[2].

That is why the receiving obligation exists at all. An end-to-end digital process only works if both ends are digital. If your largest customer switches to issuing structured eInvoices in November 2028 and your business has no way to accept one, the chain breaks at your door. Not at theirs.

All of this sits on the business-to-business side of your trade. If you sell to consumers and to firms, those two sets of buyers already carry different obligations for you, and eInvoicing adds one more line to that list.

A PDF is not an eInvoice, and Revenue has said so in writing

This is the point where most business owners assume they are already covered, because their accounting software emails a tidy PDF and has done for years.

Revenue addressed that directly. The February notice states that in-scope businesses must issue eInvoices "in a structured electronic format (for example, XML) that complies with European Standard EN16931", and adds that "unstructured formats such as PDFs or scanned paper documents do not meet the eInvoicing requirement" ^[1]. The October 2025 implementation paper repeats the warning twice ^[2].

A PDF is a picture of an invoice. A structured eInvoice is the invoice itself, in a form a machine can act on without guessing.

The practical consequence for a small supplier is unglamorous and specific. Your invoice does not get rejected with a polite explanation. It gets ignored by an automated process that was never looking for an email attachment, while you assume it is sitting in a payment run.

Three dates, and only one of them is about big companies

Revenue has set out a phased rollout rather than a single switch. The phases matter because most coverage has collapsed them into one headline.

Date	Who it applies to	What changes
1 November 2028	Every business in Ireland	Must be able to receive structured eInvoices
1 November 2028	VAT-registered large corporates	Must issue eInvoices and report data to Revenue on domestic B2B sales
1 November 2029	All VAT-registered businesses trading B2B across EU borders	Domestic issuing and real-time reporting obligation extends to them
1 July 2030	All EU cross-border B2B transactions	Full ViDA requirements apply across every Member State

November 2028: both halves of the same date

Two obligations arrive together, and they are not the same size. The issuing half is narrow: Revenue defines a phase one large corporate as a VAT-registered business whose tax affairs are managed by its Large Corporates Division and which is established or has a fixed establishment in Ireland ^[1]. A small population, already staffed for this kind of change.

The receiving half reaches the whole economy at once, and it is the cheapest to satisfy if you start early. Revenue is blunt that it applies regardless of whether you issue anything yourself: even if your business is not required to issue eInvoices under the phased rollout, you will need the capability to receive them in the required structured format ^[2].

November 2029: the intra-EU line

Phase two extends the domestic issuing and reporting obligation to all VAT-registered businesses engaged in cross-border EU trade, the ones benefiting from the 0% VAT arrangement on those supplies ^[2]. If you sell goods or services to a business in another Member State, this is your date, and the year of domestic practice before July 2030 is deliberate.

July 2030: the EU line

From 1 July 2030 the EU's VAT in the Digital Age package applies in full. The European Commission's own summary puts it plainly: digital reporting requirements affect cross-border B2B transactions from that date ^[3]. ViDA was adopted on 11 March 2025 and entered into force that April, and the Commission notes that Member States have been free to introduce mandatory eInvoicing since then ^[3]. Ireland, by Revenue's own admission, has been one of very few Member States not yet operating or rolling out a mandate ^[2].

The part of this that is already live

There is a version of this running in Ireland today, and it has been running since 2019.

Under the EU eInvoicing directive, Irish public bodies had to be able to receive and process structured electronic invoices. The Office of Government Procurement, Ireland's PEPPOL authority, put a framework in place for exactly that, built on the PEPPOL network and the EN 16931 standard ^[4]. Revenue is now working with the OGP, expecting a significant expansion in use of that same network as businesses adopt eInvoicing more widely ^[2].

Consider a fabrication workshop in Meath making handrails and stair balustrades, most of its work invoiced to two building contractors and a county council. Nothing about that business is digital-first, and nothing about it needs to be. It is still one procurement policy change away from being asked for an invoice in a format its bookkeeping package has never produced.

That is the shape of the failure, and it matters that it is not dramatic. Nobody rings. The invoice does not bounce. It never enters the system it was meant to enter, and the first anyone notices is a payment run coming and going without it. You are then arguing about a file format rather than about the work, and the money is late regardless of who is right.

Where your website actually comes into this

Honest answer first, because this is the part vendors will blur over the next two years: your hosting does not fix eInvoicing, and neither does your website. The obligation lands in your accounting and invoicing systems, and the fix comes from your software provider, your accountant, or an access point on the PEPPOL network.

One place it does touch the site, and this is worth knowing now rather than in 2028. If your website issues anything that behaves like an invoice, a shop emailing a receipt to a business customer, a booking system raising a charge, a plugin generating a PDF at checkout, that is a second invoicing pipeline running in your business. Somebody has to decide whether it feeds the same accounting system as everything else. Two pipelines that never meet is how a supplier ends up compliant on paper and non-compliant in practice.

Which is an argument for building on something you can extend. A site on full WordPress can take an integration nobody anticipated three years earlier, because the plugin ecosystem is open and the database is yours. A closed builder gives you whatever its vendor decides to ship, on their timetable. If you want to see the alternative before committing to anything, you can describe your business and watch a full WordPress site get built in under a minute.

The same pattern produced the card network rules your website already has to meet before it can take a payment. These obligations arrive from outside your business, on somebody else's schedule, and land on whatever you happen to have built.

What none of this settles

Three honest limits, because the confident version of this article would be less useful.

Revenue has not yet published the detailed technical specifications, and has committed to doing so well in advance of each phase ^[2]. Anyone selling you a finished eInvoicing product today is ahead of the guidance, not ahead of the curve. Wait for the spec.

Dates move. The July 2030 end has EU legislation behind it, so the direction is not in doubt, but the Irish phase dates are policy rather than commencement orders.

The benefit numbers need a caveat too. Revenue cites EU estimates of up to roughly €11bn a year in reduced VAT fraud and something over €4bn a year in lower compliance costs across the bloc ^[2]. Those are modelled figures, spread across 27 economies over a decade. Whether a five-person fabrication shop sees any of it is a different question.

If you already run a full accounting suite

Worth saying plainly. If your business already runs on a major accounting or ERP platform with a maintained Irish tax module, this is genuinely not your problem to solve. That vendor will ship eInvoicing and PEPPOL connectivity as an update, the way they have shipped every VAT rate change before it, and your job is to install it and verify it works. Paying for a separate specialist tool there is money spent on a problem your licence already covers.

The businesses who need to think about this are the ones invoicing from a spreadsheet, a Word template, or a low-cost package that may or may not still be maintained by 2028.

Four moves that make November 2028 a non-event

Verify who issues your invoices. Write down every system in your business that produces something a customer treats as an invoice, including the website. Most owners find two. Some find four.

Ask your software provider one question. "What is your plan for EN 16931 structured eInvoicing and PEPPOL in Ireland?" A clear answer with a rough timeline is fine. No answer at all is your signal to start looking.

Confirm the receiving side, not just the sending side. The November 2028 obligation is about accepting eInvoices. Ask specifically whether your package can ingest one, because sending and receiving are separate capabilities and vendors quote the first far more readily than the second.

Put a reminder in for spring 2028. Revenue will publish specifications and write to affected businesses before each phase ^[1]. A calendar note beats finding out from a customer.

I have got the timing wrong on this type of thing before. We treated a compliance deadline three years out as a problem for later, then found the real work was the systems inventory, which took months of asking people what they actually used. The deadline was never the hard part.

Conclusion

Most regulatory changes reach small businesses through a customer rather than through a letter. Somebody larger up the chain adopts the new process, and everyone supplying them either matches it or falls out of it. That is what November 2028 sets up, and it is why the receiving obligation matters more to a small supplier than the issuing one.

None of this needs solving in 2026. It needs knowing about in 2026, so that when your accountant or your software provider raises it, you are having a short conversation rather than a surprised one. Write down what issues your invoices. That is the whole first step.

Frequently Asked Questions

Does eInvoicing apply to my small business or only to large companies?

Both, at different times and in different ways. From 1 November 2028 only VAT-registered large corporates, meaning businesses managed by Revenue's Large Corporates Division with an establishment in Ireland, must issue structured eInvoices and report the data to Revenue. From that same date, Revenue states that all businesses in Ireland must be able to receive structured eInvoices. Issuing extends to all VAT-registered businesses trading B2B across EU borders from November 2029, and full EU requirements apply from July 2030.

Is the PDF invoice my accounting software emails an eInvoice?

No. Revenue's February 2026 notice states that unstructured formats such as PDFs or scanned paper documents do not meet the eInvoicing requirement. A compliant eInvoice is a structured data file, for example XML, complying with European Standard EN 16931 and processed automatically by the receiving system. A PDF is built to be read by a person, which is the step eInvoicing removes.

What is PEPPOL and do I need to join it?

PEPPOL is the network used to exchange structured electronic documents between organisations across Europe. Irish public bodies have used it for supplier invoices since 2019 under a framework run by the Office of Government Procurement, Ireland's PEPPOL authority, and Revenue has said the new system will use existing infrastructure including PEPPOL. Most small businesses will not join it directly. Their accounting software or an access point provider connects on their behalf, in the same way you do not connect to the card networks yourself.

Do I have to buy new invoicing software?

Not yet, and buying now would be premature. Revenue has committed to publishing detailed technical specifications well in advance of each phase, and those do not exist in final form at the time of writing. The sensible step today is to ask your current provider what their plan is for EN 16931 and PEPPOL support in Ireland, and to treat a vague answer as information about your supplier rather than about the deadline.

Does eInvoicing change how much VAT I pay?

No. Revenue is explicit that the changes relate solely to invoicing and reporting processes, and that tax rates, payment requirements and liability calculations are unchanged. What changes is the format your invoices take, and the fact that a subset of the transaction data reaches Revenue close to real time rather than in a periodic return. For businesses in scope, the monthly VIES return is expected to fall away under the same package.

What happens if my business cannot receive an eInvoice in 2028?

The practical risk is commercial before it is regulatory. A customer that has moved to structured eInvoicing runs an automated accounts process, and a supplier who cannot participate becomes an exception somebody has to handle manually. Exceptions get deprioritised, and late payment follows. The obligation comes through Revenue's VAT modernisation programme with the EU's ViDA directive behind it, and the detailed Irish rules and penalties are still to be published. The first cost most small suppliers feel would be a slower payment cycle rather than an enforcement action.

Sources