Salesforce document generation: the complete guide

Salesforce document generation is the making of a finished document, such as a quote, a contract, an invoice or a service report, from the data in Salesforce records, using a template that says where each value goes. The template is designed once. Each time someone, or an automation, asks for a document, the values of one record fill it and the result is saved as a file, usually a PDF and sometimes an editable Word file.

It matters because these documents are what customers see. A quote with a wrong total, a contract with last year’s clause or a service report with no signature costs time and trust. Making them from the record, not by copying values into a desktop file, keeps them correct and consistent, and leaves a copy where the team can find it.

This guide names the documents people make, every route Salesforce offers today, the questions to ask before you choose a tool, and how Docable answers each one.

The documents people generate from Salesforce

Most documents start from one record and pull in its related records.

Document	The record it usually starts from
Quote	Quote, with its quote line items
Proposal	Opportunity or Quote
Order form	Order or Quote
Contract or service agreement	Contract, Account or Opportunity
Invoice and statement	Order, Account or a custom invoice object
Letter	Contact, Account or Case
Certificate	Asset, Work Order or a custom object
Service report and other field documents	Work Order, Work Order Line Item or Service Appointment
Case summary	Case
Account summary	Account

How documents get made in Salesforce today

Built into Salesforce

Quote templates and quote PDFs (Sales Cloud). An administrator defines the look of the company’s quote PDFs with quote templates, and sales reps choose a template when they create a quote PDF [1, 2]. In the template editor you drag in sections for Quote fields or fields from related objects, a Text/Image Field for terms or a logo, and a list for a table such as Quote Line Items [2]. Save and Preview shows the rich text and images you added, with other data simulated [2]. Reps can create quote PDFs and email them to customers [1].

Service Reports (Field Service). A service report summarises a work order or service appointment in a PDF that customers and team members can sign [3]. Service report templates control what appears, and each template has four subtemplates for work orders, work order line items and the service appointments on each [3]. Users make a report with the Create Service Report button, and it appears in the record’s Service Report related list [3]. The Create Service Report action can’t be triggered from a flow [4].

Document Builder (Field Service). Document Builder is Salesforce’s Field Service solution for richly formatted, branded PDF service documents [5]. Templates are built by dragging seven standard components (Grid, Image, Image Gallery, Page Numbers, Related Record Table, Rich Text and Signature), and you can show fields from a record and its parent or grandparent records [5]. You can view documents and collect signatures in the Field Service mobile app, and generate PDFs on mobile or desktop [5]. Each user gets either Service Reports or Document Builder, not both [6]. Salesforce lists Document Builder’s output as PDF, its objects as a limited set of standard objects such as Quote, Service Appointment and Work Order, and its processing as synchronous only, with no batch support [10]. It comes with Revenue Cloud Growth, Revenue Cloud Advanced and Field Service [10]. The Create Service Document action generates a document from a work order, work order line item or service appointment [7].

Salesforce Document Generation. Salesforce Document Generation generates documents on the platform from templates built in Microsoft Word (.docx) or PowerPoint (.pptx), with data from Salesforce objects or any JSON source; documents can be converted to PDF, and several PDFs merged into one [8]. It supports batch processing and server-side generation [8]. Designing templates needs the DocGen Designer permission set licence [8]. Salesforce says Omnistudio isn’t required for token replacement, and is required only if you map token data with Omnistudio Data Mappers [9]. Its comparison lists the outputs as PDF, DOCX and PPTX, all standard and custom objects, no offline or mobile support, and licences included with Industries, Revenue Cloud Advanced and Revenue Cloud Billing SKUs and the Revenue Events Starter Pack for Sales and Service Cloud [10].

Visualforce pages rendered as PDF. A developer can turn a Visualforce page into a downloadable, printable PDF by adding renderAs="pdf" to the page, or render it from Apex with PageReference.getContentAsPDF() [11]. Visualforce PDF rendering supports a limited set of fonts, and Salesforce advises checking the PDF’s formatting before production [11]. The template is the Visualforce page itself, written by a developer.

Email templates with merge fields. Lightning email templates with merge fields send emails that include field data from records [12].

Add-on apps from the AppExchange

Many teams add a document generation app from the AppExchange. These apps typically give you a template designer, often built around Word templates with merge tags, buttons on record pages, a Flow action or Apex call for automation, bulk runs, and e-signature options. They differ in the ways that matter: some make documents inside Salesforce, and others send record data to the vendor’s own service to make the file; many are priced per user, some with document quotas. See how Docable compares for a sourced, dated comparison.

What to look for

Eleven questions to put to any tool, built-in or added. Under each is how Docable answers it.

1. What is the editor like?

Some tools give you a page that works like Word. Others give you a template full of merge syntax, or code.

Docable’s editor runs inside Salesforce. You type on the page, and type @ to place a Salesforce field in the sentence. No merge codes, no desktop files. It has headings, styles, tables, headers and footers, page numbers, contents, footnotes and watermarks. See the editor.

2. How does data get on the page?

Check fields from the record and its parents, tables of related records, totals and conditions.

In Docable you add any field from the record, its parents up to five levels up, or any related list, limited to what you are allowed to see. Tables of related records can be filtered, sorted and grouped with subtotals. Totals, averages and calculations sit on the page, and any paragraph, row, column, section or picture can show only when a rule says so. A template can also ask the person a question as they make the document. See data and logic and Put Salesforce data in a document.

3. What files come out?

A PDF is right for most documents. A contract often needs an editable Word file for the last-minute change.

One Docable template makes a PDF, an editable Word file or both. Each document’s data is read once, then both files are made from that snapshot, so the values, numbers, row order and conditions match. The Word file opens, changes and saves in Word. Docable makes no Excel or PowerPoint files. See Choose PDF, Word or both.

4. Where is the document made?

Ask whether the document is made inside your org, as the person who asks, or whether record data goes to a vendor’s servers.

Docable’s own code makes every PDF and Word file inside your Salesforce org, as the person who asks, with their permissions and sharing. There is no callout to make a document and there are no Docable servers. Nothing is copied anywhere else unless your administrator connects a storage destination, a data provider or AI. See security and data flow.

5. How is it started?

People make documents from a button. Automations make them from Flow, Apex, an API or a schedule, often for thousands of records.

Docable runs from a button on the record page or a list, the Salesforce and Field Service mobile apps, a Flow, a schedule, Apex, REST, an Experience Cloud site, Claude or an Agentforce agent. A bulk run makes one document for each record in the background, with no fixed cap on the number of records; the real limits are your org’s File storage, its daily allowances and time. See Generate a document from a record, Make documents for many records, Flow and Schedule a run.

6. How is a template checked before it goes live?

A preview with made-up data is not a check. Look for proofs on real records, approval and versions.

In Docable you preview the template on any record, and Validate lists anything to fix. Docable then makes the exact PDF and Word file for a real record as proofs. A second person approves it first, unless you switch that off, and a person makes that exact version live. Every version is kept, so you can compare and roll back. See proof and approval.

7. How is branding handled?

With dozens of templates, a logo or address change should be one change.

A Docable Brand Kit holds logos, colours, fonts, letterhead, standard wording, document numbers, signatories and bank details. You set it once and every template that uses it follows. A change to bank details, the remit-to address or a signature always needs a second approver. See Brand Kits.

8. What can AI do, and what can it see?

AI that drafts a template saves hours. Ask what it is sent and what it is allowed to do.

In Docable you describe the document and AI drafts it with your Salesforce fields and Brand Kit, then opens it in the editor for you to finish. There are four ways in: Build with AI, the assistant in the editor, Claude through Docable’s MCP server, and your own Agentforce agents. AI sees your words, the template and the names of fields you can see, never record values or the files Docable makes. It can’t approve, activate or share a template. AI needs Einstein generative AI in your org; without it, everything else works. See the AI template builder and Make your first document with AI.

9. Does it work in the field?

Technicians work where there is no signal. Ask what happens on the phone then.

In the Field Service mobile app with no signal, the technician previews the document, answers its questions, signs and taps Submit. The document is made and filed on the record when the phone syncs. Signatures are stored as Salesforce Digital Signatures, and photos taken on the job before Submit appear in the document. The Salesforce mobile app works while connected. See Docable for Field Service and Field service documents in Salesforce: the complete guide.

10. Can you bring the templates you already have?

Docable imports a Word file without AI. Merge fields from Word mail merge and merge tags from other document tools connect to your Salesforce fields, and a tag that matches no field becomes a placeholder to connect. Docable never guesses a field. A PDF or a scan is rebuilt with Claude for a person to check. See Bring a Word template into Docable and switching to Docable.

11. How is it priced?

Prices are per org, per user or per document, and AI and storage can cost extra.

Docable is one price per production org, for any number of people and documents, with every sandbox included. There is no per-user or per-document fee. Salesforce charges for its AI separately. See pricing.

A worked example

One quotation, followed from a sales rep’s opportunity to a PDF for the customer and an editable Word file. It uses the ForgeFlow sample from the quotation recipe.

1. Start the template. In the Docable app the author opens Templates, chooses New and picks a way in: Describe it with AI, a quick start, a copy or a blank page. Every way opens the same editor. With AI, the author describes the quotation, chooses the record it is for and the Brand Kit, leaves the output on PDF and Word, and chooses Create draft. Here the author starts from the Branded quotation quick start with the ForgeFlow kit.
2. Write it like Word. The template is built on Quote. The title prints the opportunity’s name, and a table has a row for each quote line, with a picture and a lead time. Totals, a deposit and a cost chart sit on the page. Questions asked when generating cover the issue date, a customer reference, the deposit rate, whether to invite acceptance and whether to include charts.
3. Leave room to sign. With Invite acceptance ticked, an acceptance table with Accepted by, Position, Signature and Date prints for the customer. For an e-signature tool, a Signature anchor marks where it places its field.
4. Prove it. The author chooses Validate and fixes what it lists, then Preview on the quote FF-Q-0284, and Make PDF and Word proofs. They open both proofs and check the values and every warning.
5. Approve and activate. A second person approves the proofs and activates the version. The badge reads Active.
6. Make it. On the quote, the rep opens Generate a document, chooses the template, ticks PDF and Word (DOCX), answers the questions and chooses Make PDF and Word. Both files are kept on the quote as Salesforce Files, and the Generation Runs tab shows the run as Made.
7. Send and edit. The rep sends the PDF to the customer to sign. The Word file opens in Word for the last change, and saves as a real Word document.

Questions

Does Salesforce have built-in document generation?

Yes, in several places: quote templates and quote PDFs, Field Service Service Reports and Document Builder, Salesforce Document Generation, and Visualforce pages rendered as PDF by developers.

Can Salesforce generate a PDF from a record?

Yes. A rep can create a quote PDF from a quote, a technician a service report from a work order, and a developer can render a Visualforce page as a PDF. Docable makes a PDF from any standard or custom object.

Can Salesforce create Word documents?

Salesforce lists DOCX among Salesforce Document Generation’s outputs, and PDF as Document Builder’s. Docable makes an editable Word file from the same template as the PDF.

How do I generate a document from a Flow?

Salesforce says the Create Service Report action can’t be triggered from a flow. Docable adds a Generate Docable document action to Flow Builder, which works in screen, record-triggered, scheduled and autolaunched Flows. See Generate documents from Flow.

What is the difference between Service Reports and Document Builder?

Both make Field Service documents. Service Reports use service report templates with fields, sections and related lists. Document Builder builds richly formatted, branded PDF service documents from standard components. Each user is given one or the other.

Can documents be made offline in the Field Service app?

Salesforce lists offline and mobile support, with signatures, for Document Builder. With Docable, the technician previews, answers, signs and taps Submit with no signal, and the document is made and filed on the record when the phone syncs.

Do I need Omnistudio for Salesforce Document Generation?

Salesforce says Omnistudio isn’t required for token replacement, only for mapping token data with Omnistudio Data Mappers. Docable needs neither a DocGen licence nor Omnistudio.

Does the data leave Salesforce?

With Docable, not to make documents. Docable’s own code makes every document inside your org, as the person who asks. Nothing is copied anywhere else unless your administrator connects a storage destination, a data provider or AI, and the AI never sees your records’ values.

Can AI build the template?

Yes, with Docable: in Build with AI, the assistant in the editor, Claude through Docable’s MCP server, or an Agentforce agent. A person checks the draft and makes it live; AI can’t approve.

Can I make documents for thousands of records at once?

Salesforce lists batch processing for Salesforce Document Generation and synchronous processing only for Document Builder. Docable makes one document or thousands in the background, from a list, a Flow, a schedule, Apex or REST, with one combined PDF if you want it.

Do I need a developer?

Visualforce templates are code. With Docable an administrator builds templates in the editor and adds the action to the page layout.

Is Docable on the AppExchange?

Not yet. Docable is in the Salesforce partner programme and on its way to the AppExchange. Join the waitlist to hear first.

Sources

1. Salesforce Help, Create and Email Quote PDFs, https://help.salesforce.com/s/articleView?id=sales.quotes_create_pdf.htm&language=en_US&type=5, read 26 October 2026.
2. Salesforce Help, Create, Preview, and Activate Quote Templates, https://help.salesforce.com/s/articleView?id=sales.quotes_template_create.htm&language=en_US&type=5, read 26 October 2026.
3. Salesforce Help, Create Field Service Report Templates, https://help.salesforce.com/s/articleView?id=service.fs_customer_reports_settings.htm&language=en_US&type=5, read 26 October 2026.
4. Salesforce Developers, Create Service Report Actions, https://developer.salesforce.com/docs/platform/api-action/guide/actions-obj-create-service-report.html, read 26 October 2026.
5. Salesforce Help, Document Builder, https://help.salesforce.com/s/articleView?id=service.fs_document_builder_about.htm&language=en_US&type=5, read 26 October 2026.
6. Salesforce Help, Set Up Document Builder: Licensing and Enablement, https://help.salesforce.com/s/articleView?id=service.fs_document_builder_set_up.htm&language=en_US&type=5, read 26 October 2026.
7. Salesforce Developers, Create Service Document Actions, https://developer.salesforce.com/docs/platform/api-action/guide/actions-obj-create-service-document.html, read 26 October 2026.
8. Salesforce Help, Salesforce Document Generation, https://help.salesforce.com/s/articleView?id=ind.sf_docgen_overview_one.htm&language=en_US&type=5, read 26 October 2026.
9. Salesforce Help, Omnistudio Requirement for Salesforce Document Generation, https://help.salesforce.com/s/articleView?id=ind.sf_docgen_requirements_two.htm&language=en_US&type=5, read 26 October 2026.
10. Salesforce Help, Understand Document Builder and Document Generation in Salesforce, https://help.salesforce.com/s/articleView?id=ind.sf_docgen_understand_doc_builder_and_doc_generation.htm&language=en_US&type=5, read 26 October 2026.
11. Salesforce Developers, Render a Visualforce Page as a PDF File, https://developer.salesforce.com/docs/platform/salesforce-pages-developers-guide/guide/pages-output-pdf-renderas.html, read 26 October 2026.
12. Salesforce Help, Email Templates in Lightning Experience, https://help.salesforce.com/s/articleView?id=sales.email_templates_lightning_parent.htm&language=en_US&type=5, read 26 October 2026.