Adobe PDF Invoice and Statement Batch Generator

Overview

This flow produces branded customer invoices/statements at scale on a monthly schedule. It reads *due* billing records from a Dataverse table, merges each record into a branded HTML statement, archives the statement to SharePoint under a year/customer folder, emails each customer their statement (HTML body plus an .html attachment), marks the source record Generated, and posts a run summary to a Microsoft Teams channel and to the finance distribution list.

Why it matters: Monthly statement runs are repetitive and error-prone. Templated batch generation makes them consistent, archived, idempotent, and entirely hands-off.

Build status: Built — FlowLibs demo, ships Off. Flow Checker: 0 errors / 0 warnings.

Adobe PDF Services substitution: The brief called for Adobe PDF Services CreateDocumentFromTemplate (Document Generation). That operation's template input is a contentOnly multipart file-upload parameter that cannot be authored through the API / workflow-table deployment path FlowLibs uses, so Adobe document-generation ideas are built with an in-flow branded-HTML compose (action Compose_Statement_HTML), yielding a fully-bound, 0-error flow. To emit a real PDF when going live, either keep the HTML and add a converter step (Word Online GetFilePDF, or an Encodian/Plumsail HTML-to-PDF action), or add the Adobe CreateDocumentFromTemplate action by hand in the designer.

Use Case

Finance issues recurring monthly invoices/statements and wants them produced, filed, and sent automatically from CRM data — with no manual mail-merge. Each customer receives their statement by email; a copy is archived to SharePoint for audit; the billing record is stamped so the next run skips it; and finance gets a one-line confirmation in Teams and by email.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords UpdateRecord
SharePoint	shared_sharepointonline	CreateFile
Office 365 Outlook	shared_office365	SendEmailV2
Microsoft Teams	shared_teams	PostMessageToConversation

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Which records are due

Change Initialize_Due_Status (default Pending) or edit the List_Due_Invoices filter to add date/segment criteria (e.g. and flowlibs_duedate le ...).

Branding

Set flowlibs_CompanyName; adjust the inline CSS/colours in Compose_Statement_HTML (header colour #0f4c81).

Line items

Populate flowlibs_lineitems with a JSON array [{desc,qty,unit,amount}]; the Select action renders them into the statement table.

Real PDF output

Add a Word Online GetFilePDF (or Encodian/Plumsail HTML-to-PDF) step after Compose_Statement_HTML, or re-add the Adobe CreateDocumentFromTemplate action by hand.

Archive layout

Edit Archive_Statement_To_SharePoint folderPath (currently <libraryPath>/<yyyy>/<customer>).

Schedule

Open Monthly_Statement_Run and set the exact day-of-month / time. Turn the flow On to go live after authorizing the four connections and setting env-var values.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@concat('flowlibs_status eq ''', variables('varDueStatus'), '''')

@concat('<tr><td>', coalesce(item()?['desc'],''), '</td><td>', string(coalesce(item()?['qty'],0)), '...</tr>')

@concat(variables('varLibraryPath'), '/', formatDateTime(utcNow(),'yyyy'), '/', coalesce(items('Apply_To_Each_Record')?['flowlibs_customername'],'Unknown'))

[{"Name":"....html","ContentBytes":"@base64(outputs('Compose_Statement_HTML'))"}]

Update_Invoice_Record -> Row Item = @outputs('Compose_Invoice_Update')

Customize & download