Use cases

Monthly client statements from Excel to PDF, the whole batch at once

Short answer: A client statement run is the same workbook shape repeated once per client, which is exactly the job a batch is for. With CrazySmartPDF’s Windows desktop app you point it at the folder of statement workbooks and it renders every one in a single pass, keeping each line’s row whole, resizing or slicing wide tables so they stay readable, and writing a run log plus a per-file health report that flags any page that came out blank or clipped. It does all of this on your machine, so the client financials never leave your PC. It flags a suspect page for you to review; it does not rewrite your workbook, and it does not mail-merge one data sheet into per-client copies, so if you generate the statements from a template, run that generation step first, then batch the outputs.

Why the statement run is painful by hand

How CrazySmartPDF fits the run

One honest caveat for confidential runs

CrazySmartPDF renders the sheet’s full data range and ignores the print area when deciding what to keep, which is what stops it silently dropping a column. The flip side matters for statements: in the current batch path there is no per-file notice, so if you used a narrow print area to hide scratch, backup or personal columns, those get rendered into the PDF too. A per-file batch notice is a planned addition but is not shipped yet, so for now, before a confidential batch, make sure each workbook contains only what the client should see rather than relying on a print area to hide the rest. In the desktop or web pre-send review of a single file, CrazySmartPDF does tell you when it included data from beyond a set print area; that notice is the review UI, not the batch console.

Getting started

Point the desktop app at a copy of your statements folder, run it once, and read the run log and the per-file report. It is free to run on your own files, with no trial clock. See how it works.

What it does not do

It does not turn one data sheet into per-client statements, that is a template or mail-merge step you run first. It renders and lays out the resulting workbooks. The native apps need Windows with Excel 2016+; a Mac user would use the single-file web tool instead.