Generating Monthly Account Statements as PDF Documents

The Problem With Statement Generation at Scale

For a small customer base, exporting a CSV and formatting it manually is slow but survivable. At a few hundred customers it becomes a dedicated task. At a few thousand it becomes a bottleneck that blocks the billing cycle.

SSRS and Crystal Reports were the standard answer for a long time. They still work, but the output looks like it was built in 2008, difficult to theme, expensive to maintain, and disconnected from the visual design the rest of the product has adopted. Updating a report definition requires a specialist, and the output rarely matches the brand without significant effort.

Third-party statement generation APIs solve the appearance problem but introduce new ones. Per-document pricing scales directly against customer growth, which means your infrastructure costs rise every time the business succeeds. There is also a network dependency: if the API is unavailable during the billing run, the entire cycle stalls.

The performance dimension is non-trivial. A SaaS platform generating usage summaries for 10,000 customers on the 1st of the month, a telecom system producing itemized call records, a property manager distributing rent ledgers to hundreds of tenants, all of these have a window in which the run must complete. An approach that isn't designed for throughput will miss it.

Customers, meanwhile, expect a branded document that looks like it belongs to the product they pay for, not a raw data export with a logo dropped on top.

This IronPDF example demonstrates how modern .NET applications can automatically generate a branded PDF document from an HTML file and deliver it to customers at scale. Using the IronPDF C# PDF library, developers can convert HTML into reliable PDF files inside a .NET project without relying on external services. The approach shown here works across multiple platforms, integrates easily with Visual Studio, and uses the familiar NuGet library for PDF distribution model that .NET developers already trust.

The Solution: Batch PDF Generation With the IronPDF C# PDF Library

IronPDF lets .NET applications generate branded PDF statements from HTML and CSS templates in a batch loop or background job. Each customer's data populates the same template, ChromePdfRenderer produces the PDF, and the application delivers it by email or posts it to a self-service portal.

There is no SSRS installation to maintain, no Crystal Reports license to renew, and no per-document fee that grows with your customer count. IronPDF runs inside your existing .NET application as a single NuGet package with no external processes. The HTML template is owned by your team, styled with the same CSS that powers the rest of the product, and updated on your own schedule.

using IronPdf;

using IronPdf;

How It Works in Practice: Using IronPDF in your .NET Projects

using IronPdf;

var renderer = new ChromePdfRenderer();

renderer.RenderingOptions.PaperSize = IronPdf.Rendering.PdfPaperSize.A4;

renderer.RenderingOptions.MarginTop = 20;

renderer.RenderingOptions.MarginBottom = 20;

foreach (var customer in activeCustomers)

{
    string html = $@"
        <h1>Account Statement — {customer.StatementPeriod}</h1>
        <p><strong>Account:</strong> {customer.AccountNumber}</p>
        <p><strong>Name:</strong> {customer.FullName}</p>
        <hr/>
        <h2>Charges This Period</h2>
        {customer.LineItemsHtml}
        <p><strong>Closing Balance:</strong> {customer.ClosingBalance:C}</p>";

    PdfDocument statement = renderer.RenderHtmlAsPdf(html);
    await DeliverStatementAsync(customer, statement);
}

using IronPdf;

var renderer = new ChromePdfRenderer();

renderer.RenderingOptions.PaperSize = IronPdf.Rendering.PdfPaperSize.A4;

renderer.RenderingOptions.MarginTop = 20;

renderer.RenderingOptions.MarginBottom = 20;

foreach (var customer in activeCustomers)

{
    string html = $@"
        <h1>Account Statement — {customer.StatementPeriod}</h1>
        <p><strong>Account:</strong> {customer.AccountNumber}</p>
        <p><strong>Name:</strong> {customer.FullName}</p>
        <hr/>
        <h2>Charges This Period</h2>
        {customer.LineItemsHtml}
        <p><strong>Closing Balance:</strong> {customer.ClosingBalance:C}</p>";

    PdfDocument statement = renderer.RenderHtmlAsPdf(html);
    await DeliverStatementAsync(customer, statement);
}

using System.Net.Mail;
using System.IO;

async Task DeliverStatementAsync(CustomerRecord customer, PdfDocument statement)
{
    var pdfBytes = statement.BinaryData;
    // Store in blob storage for portal download
    await _blobClient.UploadAsync(
        $"statements/{customer.AccountNumber}/{customer.StatementPeriod}.pdf",
        new BinaryData(pdfBytes)
    );

    // Email to customer
    using var stream = new MemoryStream(pdfBytes);
    using var attachment = new Attachment(stream,
        $"Statement-{customer.StatementPeriod}.pdf", "application/pdf");
    var message = new MailMessage("billing@yourcompany.com", customer.Email)
    {
        Subject = $"Your {customer.StatementPeriod} Statement",
        Body = $"Dear {customer.FullName}, your statement for {customer.StatementPeriod} is attached."
    };

    message.Attachments.Add(attachment);

    using var smtp = new SmtpClient("smtp.yourprovider.com");

    await smtp.SendMailAsync(message);
}

using System.Net.Mail;
using System.IO;

async Task DeliverStatementAsync(CustomerRecord customer, PdfDocument statement)
{
    var pdfBytes = statement.BinaryData;
    // Store in blob storage for portal download
    await _blobClient.UploadAsync(
        $"statements/{customer.AccountNumber}/{customer.StatementPeriod}.pdf",
        new BinaryData(pdfBytes)
    );

    // Email to customer
    using var stream = new MemoryStream(pdfBytes);
    using var attachment = new Attachment(stream,
        $"Statement-{customer.StatementPeriod}.pdf", "application/pdf");
    var message = new MailMessage("billing@yourcompany.com", customer.Email)
    {
        Subject = $"Your {customer.StatementPeriod} Statement",
        Body = $"Dear {customer.FullName}, your statement for {customer.StatementPeriod} is attached."
    };

    message.Attachments.Add(attachment);

    using var smtp = new SmtpClient("smtp.yourprovider.com");

    await smtp.SendMailAsync(message);
}

Real-World Benefits

Scale. IronPDF renders each statement in milliseconds. A billing run for 5,000 customers completes in minutes when parallelized across cores, well within a typical overnight billing window.

Brand consistency. Every statement carries the same logo, color scheme, typography, and layout. There is no risk of a mismatched export or a statement that looks different because it was generated by a different team member.

Customer self-service. Statements stored in blob storage are available for portal download immediately after the billing run completes. Customers retrieve current and past periods on their own, support ticket volume for "can you resend my statement" drops accordingly.

Compliance and archiving. IronPDF supports PDF/A output, the ISO-standardized format for long-term document archival. For financial institutions and regulated industries, PDF/A statements satisfy record-keeping requirements without a separate archiving step. Switching it on is a single rendering option.

Template reuse. The HTML and CSS template is maintained by your team alongside the rest of the application code. Updating it takes the same skills used to update any other view — no report designer, no proprietary definition format.

No per-document costs. The rendering runs in-process. There are no API calls to a statement vendor, no metered usage to track, and no line item on your infrastructure bill that scales with customer growth.

Closing

Monthly statement generation looks like a solved problem until you try to do it at scale with consistent branding and reliable delivery. The tools that were standard a decade ago produce output that no longer fits how products look, and the SaaS alternatives trade one set of constraints for another.

A batch loop powered by IronPDF replaces all of that with an HTML template, a renderer, and a delivery step, all running inside the application your team already owns and operates. IronPDF covers the full lifecycle of PDF work in C# — from rendering and generating documents to saving, streaming, and manipulating them — all from the same library at ironpdf.com. If you're building or redesigning a statement pipeline, start your free 30-day trial and run a complete billing cycle against your own data before committing.