Anyone who has assembled a loan application, an audit pack or a set of year-end accounts knows the shape of the job. Eleven documents from six sources: bank statements as PDFs, a spreadsheet of transactions, a scanned certificate, two letters and a valuation. The recipient wants one file, in order, that they can read without opening five applications.
Sort out the spreadsheets first
Spreadsheets are the part that goes wrong most often, because what is on screen and what prints are different things. A workbook that looks clean in a window frequently produces forty pages with columns split across page boundaries.
Before converting anything, do four things in the spreadsheet itself: set the print area to the range that matters, set orientation and scaling so each table fits one page width, repeat header rows on every page, and hide working columns the recipient does not need. Then run it through an Excel converter to produce a fixed-layout version that will look the same on every machine.
The alternative — sending the workbook itself — means the recipient sees your formulas, your hidden sheets and any comment anyone left in a cell. That is occasionally what you want and usually not.
Assemble in a deliberate order
Once every component is a fixed-format document, combining them with merge PDF is mechanical. The order is not. A reviewer reads a pack top to bottom and forms a view in the first two pages.
| Position | Content |
|---|---|
| 1 | Cover page: what this is, whose, what period, date prepared |
| 2 | Contents with page numbers |
| 3 | Summary figures — the numbers being claimed |
| 4+ | Supporting evidence, in the order the summary references it |
| Last | Appendices and anything supplementary |
Add page numbers after merging, not before. Numbers applied to the individual documents will conflict, and a pack where the contents page does not match the actual pagination is worse than one with no contents page.
Checks before it goes out
- Every figure in the summary traces to a page in the pack. If it does not, either the evidence is missing or the figure is wrong.
- Dates are consistent. Mixed date formats across documents from different countries are a genuine source of misreading — 03/04 is not the same day everywhere.
- Currency is stated. On every table, not just the first one.
- Scans are legible at 100%. If you cannot read an account number, neither can the reviewer.
- Nothing is in the file that should not be. Other clients’ data, internal notes, draft watermarks.
Redaction is not a black rectangle
Drawing a filled shape over an account number hides it visually and leaves the text underneath in the file, recoverable by anyone who selects and copies it. This is a recurring and entirely avoidable disclosure failure. Use a redaction function that removes the underlying content, or flatten the document so there is no text layer left to extract.
Keep the originals separate
The assembled pack is a deliverable, not a record. Keep the source files — original statements, the live workbook, the unmodified scans — in their own folder, unchanged. When a reviewer asks a question three months later, you need the working spreadsheet with its formulas, not the printed page you sent them.
Build it once as a template
The same pack gets assembled repeatedly with different numbers. Save the cover page, the contents structure and the section order as a reusable skeleton. The second time takes a fraction of the first, and the consistency between submissions is itself worth something to whoever is reading them.