Use case

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

A statement run is the same workbook shape times every client. CrazySmartPDF batches the folder in one pass on Windows, keeps every row whole, and self-checks each file, all offline.

Free · your file is deleted after converting, never stored · desktop batch needs Excel 2016+ on Windows

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

  • It is a folder, not a file. A month of statements is dozens of near-identical workbooks. Doing them through Save as PDF, one file at a time with per-file page setup, is where the afternoon goes.
  • Rows split and columns clip. A statement with a page break through the middle of a line, or a right-hand column sliced off, is the kind of error a client notices first.
  • The data is confidential. Client balances are not something you want to upload to an online converter.

How CrazySmartPDF fits the run

  • One pass over the folder. The desktop app renders every statement workbook in the folder and hands back a run log, so you can see each file was produced.
  • Layout kept intact. Every row stays whole across page breaks, and a wide statement table is kept readable rather than shrunk to unreadable or cut off at the paper edge.
  • A self-check before it goes out. The per-file report flags any page that came out blank or clipped, so you can catch a bad statement before the client does. It flags the page; it does not auto-fix your file.
  • Offline on the native apps. The Windows add-in and desktop app convert locally and never modify your originals. The confidential balances stay on your machine. (The separate free web tool uploads then deletes, so for a strict no-upload rule use the desktop app.)

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.

No more fixing Excel page breaks by hand.

Free to use · your file is read, converted, then deleted — never stored.