E-Invoicing for PL/SQL Programmers: What Actually Makes an Invoice Electronic?

For a PL/SQL developer, an invoice often starts with familiar ingredients: Oracle data, a report layout and a PDF BLOB.

But an electronic invoice is not simply a PDF sent by email.

A real e-invoice contains structured invoice data that software can validate and process automatically. In Europe, the common foundation is EN 16931, which defines the semantic model of a core electronic invoice. The standard supports structured syntaxes including UBL 2.1 and UN/CEFACT CII.

Structured XML is the important part

The XML contains the actual invoice data:

  • seller and buyer;
  • invoice number and dates;
  • line items;
  • quantities and prices;
  • taxes and VAT categories;
  • totals;
  • currencies;
  • payment information.

Unlike a visual PDF, this information can be imported directly into accounting, ERP or government systems.

For a PL/SQL programmer, this is conceptually straightforward:

Oracle tables
     ↓
PL/SQL invoice model
     ↓
UBL or CII XML

But creating XML is only the beginning. A valid e-invoice must also satisfy semantic rules, code lists, calculations and national requirements.

PDF/A and hybrid invoices

Some e-invoice formats combine structured XML with a human-readable PDF.

Factur-X / ZUGFeRD is the best-known example. The invoice is a PDF/A-3 document containing embedded structured XML. The PDF is the visual representation for people; the XML is the machine-readable invoice.

Conceptually:

PDF/A-3
 ├── visual invoice
 └── embedded invoice.xml

This is useful because the same document works for both humans and automated systems.

However, PDF/A is not required for every e-invoice. Formats such as XRechnung can be exchanged as structured XML without a PDF visual layer.

What about digital signatures?

A digital signature is a separate concern.

The e-invoice standard defines the invoice data and validation rules. A digital signature can additionally provide:

  • authenticity — who signed it;
  • integrity — whether it was modified;
  • trusted time — when the signed document existed.

Depending on the country, industry and business process, signatures may be required, optional or handled elsewhere in the delivery infrastructure.

For PDF-based workflows this may mean PAdES; XML workflows may use XAdES or another signing mechanism.

So it is useful to keep the concepts separate:

Invoice data      → EN 16931 / XML
Visual document   → PDF / PDF/A
Signature         → PAdES / XAdES
Transport         → email / API / Peppol / eDelivery

National formats add another layer

European interoperability does not mean every country uses exactly the same invoice format.

Examples include Factur-X / ZUGFeRD, XRechnung, Peppol-based implementations and country-specific CIUS rules.

These typically build on the European semantic model but add profiles, business rules, identifiers or delivery requirements.

For developers, this means e-invoicing is not just an XML serialization problem. It is a combination of data modelling, validation, document packaging, signatures and delivery.

Where PL/ products fit

The PL/ product family is designed to keep these workflows close to Oracle and PL/SQL:

PL/PDF for PDF and PDF/A generation, PL/FACTUR for structured Factur-X / ZUGFeRD invoice processing and packaging, and PL/SIGN / PL/XSIGN for standards-based digital signatures and timestamps.

Explore the PL/ products:
https://plslash.com/products/

#Oracle #PLSQL #EInvoicing #EN16931 #FacturX #ZUGFeRD #XRechnung #PDF #PDFa #PAdES #XAdES #OracleAPEX

PLslash
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.