Germany’s e-invoicing transition is no longer a distant deadline. From January 2027, many B2B suppliers must issue structured electronic invoices.
But what if your ERP or business application already runs on Oracle Database? Do you really need another technology stack just to generate an XML invoice?
With PL/FACTUR 0.25.0, the answer is no.
Here is a complete, one-line-item XRechnung 3.0.2 example using UBL 2.1 and synthetic test data:
set serveroutput on
declare
l_xml clob;
begin
pl_factur.Init(pl_factur.c_profile_xrechnung_ubl);
pl_factur.SetInvoice(
p_invoice_id=>’DEMO-XR-001′,
p_issue_date=>date ‘2026-10-18′,
p_invoice_type_code=>pl_factur.c_invoice_type_commercial,
p_currency_code=>’EUR’,
p_buyer_reference=>’DEMO-BUYER’,
p_business_process_type=>
‘urn:fdc:peppol.eu:2017:poacc:billing:01:1.0′);
pl_factur.SetSeller(
p_name=>’Demo Supplier GmbH’,
p_country_code=>’DE’, p_vat_id=>’DE123456789′,
p_electronic_address=>’1234567890128′,
p_electronic_address_scheme=>’0088′,
p_address_line1=>’Example Strasse 1′,
p_city=>’Berlin’, p_postcode=>’10115′,
p_contact_point=>’Accounts Receivable’,
p_contact_phone=>’+4930123456′,
p_contact_email=>’’);
pl_factur.SetBuyer(
p_name=>’Demo Buyer GmbH’, p_country_code=>’DE’,
p_electronic_address=>’1234567890128′,
p_electronic_address_scheme=>’0088′,
p_address_line1=>’Example Strasse 2′,
p_city=>’Berlin’, p_postcode=>’10115′);
pl_factur.SetPayment(
p_means_code=>’58’,
p_payment_account_id=>’DE89370400440532013000′,
p_due_date=>date ‘2026-11-10′,
p_remittance_information=>’DEMO-XR-001′);
pl_factur.AddLine(
p_line_id=>’1′, p_item_name=>’Software service’,
p_quantity=>1, p_unit_code=>’C62′,
p_net_unit_price=>100.50,
p_vat_category_code=>’S’, p_vat_rate=>19,
p_line_net_amount=>100.50);
pl_factur.AddVatBreakdown(‘S’, 100.50, 19.10, 19);
pl_factur.SetTotals(100.50, 100.50, 119.60, 119.60,
p_tax_total=>19.10);
l_xml := pl_factur.GetXML;
dbms_output.put_line(dbms_lob.substr(l_xml, 32000, 1));
dbms_lob.freetemporary(l_xml);
end;
/
That’s it. GetXML runs PL/FACTUR’s profile-specific validation and returns the XRechnung UBL invoice as an XML CLOB.
Independent validation: PASS.
We uploaded the generated XML to an online e-invoice validator. The result: “Gültige E-Rechnung” — EN 16931 / XRechnung (UBL Invoice), 0 errors, 0 warnings.
And this is just one of several e-invoice formats and profiles supported by PL/FACTUR 0.25.0.
The same PL/SQL interface supports XRechnung CII, general EN 16931 UBL, Peppol BIS Billing UBL, and Factur-X / ZUGFeRD hybrid PDF/A-3 invoices.
PL/FACTUR handles invoice data, XML and built-in validation. Portal delivery, Peppol network access and final independent conformity checks are separate steps.
No separate invoice-generation server. No manual XML construction. Just Oracle PL/SQL.
Explore PL/FACTUR:
#XRechnung #ZUGFeRD #EInvoicing #Oracle #PLSQL #EN16931
