How to Batch-Generate Documents in Salesforce: List Views and Reports (2026)

Salesforce batch document generation is the simultaneous creation of multiple documents from multiple Salesforce records using a single generation action. Each record in the batch produces its own unique document, populated with that record’s specific field values, related record data, and line items.

The process is asynchronous. When you trigger salesforce batch document generation from a list view, the tool queues the job and processes it in the background. Your browser does not lock or wait. The documents generate in parallel, and each finished document is automatically attached to its corresponding Salesforce record as a Salesforce File — typically as a PDF. For a full guide on the PDF generation step, see how to generate PDFs from Salesforce.

The template used for batch generation is identical to the one used for single-record generation. There is no separate batch template. The same document template you use to generate a contract from a single Opportunity record is the template used to generate contracts for 200 Opportunities in a batch run.

Salesforce batch document generation is the right approach whenever you need to produce the same document type for more than one record at a time. The efficiency gain compounds with volume: generating 10 documents manually might be acceptable, but generating 100 or 300 manually is not.

Generating documents in batch from a Salesforce list view is the most common way teams trigger salesforce batch document generation manually. It requires no admin setup beyond the initial template configuration any user with the document generation permission can run a batch job from any list view.

Report-based salesforce batch document generation is useful when the records you need to process do not map cleanly to a single list view. Salesforce reports can cross objects, apply complex filter logic, and aggregate records from multiple sources in ways that list views cannot replicate.

The process for report-based batch generation is similar to list view batch generation with one additional step: the document generation tool reads the report output to identify the record IDs to process, then runs the batch using those IDs as the source list.

A common example is generating renewal notices using a report that shows all Opportunities with a Close Date in the next 30 days and a Stage of Negotiation or higher. The report pulls those specific records across any number of accounts, and the batch generation tool processes them all in one run.

Automating salesforce batch document generation with a scheduled Salesforce Flow removes the manual trigger entirely. The Flow runs at a set time, identifies the records to process, and triggers the batch generation job without any user action.

A scheduled Flow for monthly invoice generation works like this: the Flow fires on the first of each month, queries all active account records with a billing status of Active, loops through the results, and calls the document generation action for each record. The tool processes the generation asynchronously and attaches the invoice to each account record by the time the team starts work.

For record-triggered batch scenarios, a Flow can also fire when a group of records is updated simultaneously. When a sales manager closes 20 Opportunities at once by updating Stage to Closed Won in a list view, a record-triggered Flow fires for each one and generates the corresponding contract document automatically.

Salesforce batch document generation processes jobs asynchronously using Apex Batch, which means document generation does not count against your synchronous governor limits and does not block user activity while running.

Performance depends on three factors: template complexity, the number of related records being queried per document, and the total batch size. A simple invoice template with minimal related data generates faster than a complex contract template with multiple related objects and conditional sections.

For very large batches, the document generation tool typically splits the job into smaller Apex Batch chunks of 50–100 records each. These chunks process in parallel, which keeps the total processing time within acceptable limits even for batches of several hundred records.

Following these four practices ensures your salesforce batch document generation workflows run cleanly at scale and produce consistent output across every record in the batch.

Test the template before running a large batch. Generate a single test document from a representative record before triggering a batch run. Any merge field errors, blank fields, or formatting issues that appear on the test document will appear on every record in the batch. Fix template issues before running at scale.

Use descriptive file naming with merge fields. Configure a file naming convention that includes identifying information from the record, such as Account Name and document date. A batch of 200 invoices named Invoice_AccountName_Date.pdf is usable. A batch of 200 files named Invoice.pdf is not.

Monitor the first batch run of a new template. After setting up a new template for batch use, watch the first production batch run and spot-check 5–10 generated documents across different record types. This catches edge cases that did not appear in testing.

Schedule large batch jobs for off-peak hours. For batch runs exceeding 100 records, schedule the Flow to run overnight or early in the morning. This avoids any potential impact on user-facing Salesforce performance during business hours and ensures the documents are ready for the team when they start work.