Skip to content
Zenocta Solutions

Digital Transformation22 Nov 2026 · 3 min read

E-Invoicing and Revenue-Ready Invoicing Software: What to Ask Your Developer

A plain guide for Irish businesses commissioning invoicing software: structured formats, record keeping, accountant sign-off and how to stay flexible as rules change.

ZEBy , Editorial Team

Dark Zenocta social card with the Zenocta Solutions logo

Invoices used to be a PDF attached to an email. Increasingly, governments across the EU want them as structured data that software can read, check and report. If you are about to commission invoicing or billing software, a few questions now can save a painful rebuild later. This guide covers what to ask, without pretending the rules are simpler than they are.

General information, not legal advice. Rules change and apply differently to each business, so confirm your own position with a solicitor, your accountant or the relevant authority.

What an e-invoice is

An e-invoice is an invoice issued, sent and received in a structured electronic format, so a computer can process it without someone re-typing the details. A PDF looks like an invoice to a human but is only an image of one to a machine. The European standard for the core data model is EN 16931.

What we can say about the rules today

Ireland transposed Directive 2014/55/EU on electronic invoicing in public procurement through S.I. 258/2019, under which public bodies must be able to receive and process invoices that comply with EN 16931. Public-sector e-invoicing in Ireland has commonly run over the Peppol network. Separately, the EU adopted the VAT in the Digital Age package in 2025, and Revenue has said it is preparing. We saw conflicting commercial sources on domestic dates, and no official Irish instrument we could confirm, so we are not quoting any. Check Revenue's e-invoicing pages for the current timetable.

Questions to ask your developer

  1. Is the invoice stored as structured data? The PDF should be generated from the data, not the other way round.
  2. Which formats can it produce? Ask how a new format would be added and roughly what that involves.
  3. Can it connect to our accounting package? Check whether the package has an API before you commit.
  4. How are changes audited? Issued invoices should not be silently editable. Corrections should be credit notes with a trail.
  5. How long are records kept and how are they exported? Your accountant should be able to pull what they need.
  6. How are VAT rates and rules handled? They should live in configuration, not scattered through the code.

Design choices that keep you flexible

  • Separate the data model from the output formats.
  • Keep sequential numbering and dates under strict control.
  • Store customer tax details in dedicated fields.
  • Log every status change, such as sent, paid or credited.
  • Write automated tests for tax calculations with examples your accountant supplies.

Bring your accountant in early

Your accountant knows your VAT position, the records you must keep and what your software has to produce. Ask them to review the written requirements before the build and to test the first working version. We build to the published requirements and check them with you and your accountant. We do not give tax advice, and rules change, so we recommend a regular review.

Think about ongoing updates

An invoicing tool is not finished at launch. Formats and guidance evolve, and updates are best agreed up front, with hosting and support billed separately from the build. Our e-invoicing service page lists what we provide. To discuss your requirements, use contact or read about pricing.

Try it live

Open the real thing: demos run in a new tab with sample data, apps link to their own page.

Frequently asked questions

  • 01Is a PDF invoice an e-invoice?

    Not in the structured sense. An e-invoice carries the invoice data in a machine-readable format. A PDF can be generated from that data but on its own is just a document image.

  • 02Will the software meet current Revenue rules?

    We build to the published requirements and confirm them with you and your accountant. Rules change, so a regular review process is sensible, and it is not a substitute for tax advice.

  • 03Can invoicing software connect to my accounting package?

    Where the package offers an API, usually yes. We check this before we quote, because it affects the design.

0% read ·

Get new guides in your inbox

Practical notes on billing, payroll, apps and AI for growing businesses, written from what we build. No spam.

We email occasional guides. Unsubscribe any time: reply to any email or write to contact@zenocta.com.

Ready to build something real?

Website and app development from ₹8,888. Book a free consultation and get a scoped, fixed-price proposal within 24 hours.