Fill PDF Forms from Excel or CSV

If you have one PDF form and a spreadsheet of records, Doqlo can help you generate completed PDFs from that data. Each row in the spreadsheet becomes one output PDF.

You can prepare the data in Excel, Google Sheets, Airtable, or another spreadsheet tool. Doqlo imports CSV, so export the final table as CSV before uploading it to Bulk Fill.

What this workflow does

This workflow starts with one reusable PDF form or stable PDF layout. The PDF supplies the structure. The spreadsheet supplies the changing values. Doqlo Bulk Fill combines them so you can create repeated completed PDFs without typing the same form by hand for every record.

A practical setup has four parts:

• one PDF that should stay structurally the same for every output
• one CSV table exported from your spreadsheet or system
• one row for each completed PDF you want to produce
• one column for each value that may need to appear on the PDF

After the PDF and CSV are loaded, you map spreadsheet columns to supported native PDF form fields, overlay Fields placed visually on the page, or a combination of both. Preview representative rows, export a test PDF, and confirm the result before exporting the full batch.

When to fill PDF forms from Excel or CSV

Filling PDF forms from spreadsheet data is useful when the same document structure needs to be completed many times. It is strongest when the data already lives in rows and columns and the PDF layout does not need to change per person, customer, vendor, or record.

Common examples include:

• HR forms and onboarding packets
• training certificates and education documents
• internal request or approval forms
• compliance forms that use the same layout for each record
• notices, letters, and recurring communications
• invoices or packing slips with stable layouts
• forms produced from roster, customer, vendor, or employee data

For one-off manual filling, a PDF editor may be enough.

Prepare spreadsheet data

Clean spreadsheet structure matters more than the spreadsheet tool. Whether the data starts in Excel, Google Sheets, Airtable, or an internal export, the final CSV should have predictable columns and one record per row.

Each row should represent one completed PDF. Each column should represent one value you may want to place into the PDF.

Use clear labels in your working spreadsheet so your team can review the data easily. In Doqlo's CSV import, mappings are based on column position, and every CSV row is treated as data. A visible header row can help you check whether fields are mapped to the expected columns, but it is not automatically converted into Doqlo field names. Many teams keep the header row during setup so the preview or test export shows column labels in mapped fields. For production output, you can keep that row intentionally or exclude it by manually selecting the rows you want to produce.

Before exporting CSV, remove anything that is not part of the record table:

• extra notes above or below the table
• merged cells
• blank title rows
• summary rows
• columns that are not needed for the PDF
• stray empty rows from earlier edits

Format values the way they should appear in the finished PDF. Dates, IDs, currency, names, and addresses should already be readable before you upload the CSV.

After a mapping is configured, avoid changing the CSV column order unless you plan to review the mapping again. Stable columns make repeatable output safer.

Export Excel or Google Sheets data as CSV

Doqlo uses CSV as the import format because it is portable and predictable. Keep working in the spreadsheet tool your team prefers, then export the final data as CSV when you are ready to run the fill workflow.

In practice:

• Excel can save or export a worksheet as CSV.
• Google Sheets can download the current sheet as CSV.
• Airtable and many internal systems can export CSV.
• Doqlo Bulk Fill imports the resulting CSV file.

Upload the CSV export, not the live spreadsheet workspace. If your team keeps maintaining the data in a spreadsheet tool, treat CSV as the handoff format for each fill run.

Upload the PDF and CSV to Doqlo

Open Bulk Fill and start with the PDF that should be reused for every output. The PDF can be a fillable form with supported native fields, or it can be another stable PDF layout.

Then upload the CSV. The CSV provides the row data that drives preview and export.

The right fill method depends on the PDF:

• If the PDF already has supported native AcroForm fields, Doqlo can map CSV columns to those existing fields.
• If the PDF is flat or does not have usable native fields, overlay Fields can place mapped text visually on the stable layout.
• Some workflows use native fields for the main form values and overlays for extra content the original PDF did not provide.

The PDF should stay structurally consistent across rows. If the layout needs to change for different records, prepare a stable layout first or split the work into separate workflows.

Map columns to PDF fields

Field mapping connects a CSV column to a destination on the PDF. That destination may be an existing native PDF form field or an overlay position that you place visually.

For supported native AcroForm PDFs, native field mapping writes row values into existing PDF fields. The current supported native field scope includes text fields, checkboxes, single-select dropdowns, and radio groups on supported non-XFA PDFs.

For flat PDFs or PDFs without the fields you need, overlay Fields are the visual path. You place the Field on the PDF, map it to a CSV column, and preview rows to confirm the value appears in the right place.

Doqlo does not automatically infer every mapping from arbitrary PDFs. Review each mapping before full export, especially if the CSV column order has changed since the mapping was created.

Preview rows before exporting

Preview is where you catch mistakes before they become a full batch of wrong PDFs.

Do not preview only the first row. Choose representative rows that test the shape of the data:

• a normal row
• a row with long text
• a row with blank cells
• a row with dates or currency
• a row with unusual names, IDs, addresses, or option values
• a row near the end of the CSV

Check that values appear in the right fields, long text still fits, blanks are acceptable, and dates or amounts look the way you expect. If you use native dropdowns, radio groups, or checkboxes, review row output and any warnings before trusting the batch.

Export a test PDF before exporting the full batch. Open it the way a recipient, internal reviewer, or downstream system would. The test PDF is the last low-cost place to catch mapping, formatting, and layout issues.

Export completed PDFs

After preview and test export look correct, export the batch. Each selected CSV row can produce one completed PDF from the same PDF form or stable layout.

For batch output, Doqlo delivers the completed PDFs as an export package.

If your CSV includes a header row, decide how to use it. You may keep it during setup to produce a mapping-check PDF that shows column labels in mapped fields. For the final batch, you may keep it intentionally or exclude it by manually selecting only the rows you want to produce.

After the batch starts downloading, spot-check a few completed PDFs before sending files onward.

Common mistakes to avoid

• Uploading a CSV that still has extra title, note, or summary rows
• Forgetting to decide whether a header row should be included as a mapping check or excluded from the final batch
• Using unclear working spreadsheet labels and then struggling to review the mapping
• Changing CSV column order after mapping fields
• Expecting Doqlo to import a live spreadsheet workspace instead of a CSV export
• Expecting spreadsheet data to stay synchronized after CSV upload
• Using a PDF whose layout changes from row to row
• Trying to use native form fill on XFA PDFs without preparing a stable overlay workflow
• Skipping preview or test export before the full batch

Safest habit: export CSV, keep column order stable, preview representative rows, and test one output PDF first.

Limitations

Doqlo Bulk Fill is built for repeated PDF output from CSV data. If you only need to fill one PDF manually, a PDF editor may be enough.

Doqlo currently imports CSV, not direct live spreadsheet connections. Keep your working source wherever your team prefers, then export CSV when you are ready to run the workflow.

If the PDF is XFA, it may need to be flattened or otherwise prepared before it fits a standard Bulk Fill workflow. Doqlo native form mapping is scoped to supported non-XFA AcroForm fields.

If the layout changes per row, Doqlo is best after the layout is made stable. Bulk Fill expects one reusable PDF structure and row-specific values inside that structure.

Doqlo does not automatically infer every mapping from arbitrary PDFs. You should preview rows and export a test PDF before the full batch.

Next steps

If your spreadsheet and PDF are ready, start with a small Bulk Fill test. Upload the PDF, upload the CSV, map a few fields, preview representative rows, and export a test PDF before running the full batch.

For broader context, read PDF Mail Merge, the Bulk Fill Overview, and Prepare your CSV.