SSRS and Word templates are the two print paths Dataverse already gives you. Both still fail the same load test.
SSRS can render a real invoice. The cost is that the layout lives in a report project. Move a line, add a logo, put a chart on the statement: that is a dataset, a deploy, often a partner release. I have lost count of the times a client asked for a small visual change and the answer was a change request. Adding a chart is always a problem.
Word templates look kinder. A user opens Word, maps a field, done. That holds for a letter. It does not hold for a statement with repeating lines, conditionals, or anything that has to look the same every month. Nested tables break. Charts are a hack. Pixel-perfect PDF is a different product. And a lot of Word ISVs then render outside the tenant, which is a second conversation.
The load-bearing bit is this: customer-facing documents are not content. They are part of the system. If the invoice layout is still code, the business cannot carry it. If it is a Word merge, the document cannot carry the data.
I built an in-tenant engine for that gap, template as a Dataverse record, PDF in the customer’s Azure. Details and the public rate card: https://simplesmoothsafe.com/docgen
I’ll be at PPCC in October. If you are still shipping invoices on SSRS or fighting Word templates, that is the conversation I want.