Convert XML to PDF Using XSLT and IronPDF

E-invoicing and machine-readable invoice formats

Here the pipeline pays off most. Standards like UBL, Factur-X, and ZUGFeRD carry invoices as XML data, not as documents anyone can read. A stylesheet turns that XML into a formatted invoice, and IronPDF produces the PDF a person actually receives.

Regulated data feeds in finance, government, and healthcare

These industries exchange structured XML: tax filings, financial statements, clinical documents, regulatory submissions. Each schema maps to a compliant printed layout through its own stylesheet, with the transformation logic kept out of your C#.

Product catalogs and price lists

A catalog feed in XML becomes a formatted brochure or table through a stylesheet, with styling handled by familiar HTML and CSS rather than a proprietary PDF language.

One source, many document variants

Because presentation lives in the template, one XML source can produce several outputs (customer invoice, internal copy, localized version) by swapping stylesheets. No data changes, no recompiling.

Parameterized and conditional documents

Pass runtime values into the transform with XsltArgumentList, so one template can branch on currency, region, or draft status before rendering:

var args = new XsltArgumentList();
args.AddParam("currency", "", "AUD");

using var writer = new StringWriter();
using (var reader = XmlReader.Create("invoice.xml"))
{
    transform.Transform(reader, args, writer);
}

var args = new XsltArgumentList();
args.AddParam("currency", "", "AUD");

using var writer = new StringWriter();
using (var reader = XmlReader.Create("invoice.xml"))
{
    transform.Transform(reader, args, writer);
}

Imports System.Xml
Imports System.Xml.Xsl
Imports System.IO

Dim args As New XsltArgumentList()
args.AddParam("currency", "", "AUD")

Using writer As New StringWriter()
    Using reader As XmlReader = XmlReader.Create("invoice.xml")
        transform.Transform(reader, args, writer)
    End Using
End Using

When not to use this

For a simple XML structure or a one-off conversion, the XSLT layer is overhead; parse the XML and build the HTML directly. The stylesheet approach proves its worth in systems handling varied schemas or needing maintainable, reusable transformation logic.

Why the split is the point

The pipeline's strength is that separation. IronPDF gives you pixel-accurate rendering on the last step, but the flexibility, multiple formats, conditional layouts, schema independence, all comes from keeping the transform in XSLT rather than in code.