With FilePreserve you select the records an auditor asked about, run the file merge, and get one combined PDF; files that were already archived are detected and pulled back in automatically, so there is no separate restore step first.

The problem with a separate archive vendor

When archiving and document merging are two unrelated tools, a merge cannot see a file once it has been archived. Someone logs into the archive vendor's own console, restores the file by hand, and only then retries the merge, often under audit time pressure. FilePreserve is built so that the archive and the merge tool are the same system.

How retrieval works in FilePreserve

  1. Add the "Audit Ready File Merge" Quick Action to the record page layouts where you need it (a one-time admin step).
  2. Pick whichever records you need, across any related list.
  3. Run the merge. It combines every file tied to those records, not only files attached directly to one record, into a single PDF.
  4. Archived files are flagged and rehydrated automatically the moment you select them. The file is read back from your S3 bucket and checked against its stored checksum.

What to confirm before an audit

Run a small test first: archive a few files, then run a merge that includes both live and archived files and check the PDF. Setup takes roughly 20 to 30 minutes for a Salesforce admin, most of it the one-time AWS step. See the setup guide.

What this does not do

FilePreserve helps you assemble a complete packet faster. It is not a compliance certification and does not decide what an auditor should receive. That judgment stays with your team.

Related

This guide describes how FilePreserve works and is not legal or compliance advice. Reviewed against the FilePreserve product documentation. Have a question? hello@filepreserve.com.