HR Document Automation: Letters From a Spreadsheet
By Josh ·
The request on your desk is an employment verification letter. Last week it was a promotion letter. Next Monday it is twelve offer letters and an onboarding packet. HR document automation is the name for treating all of them as the same job.
What is document automation for HR? One row of employee data from an HRIS or a spreadsheet, merged into a letter or a packet, rendered as a PDF, then filed or sent. Document automation for human resources is that pattern applied to the whole pile.
The field-level versions live on their own pages: an employment verification letter template plus a filled sample, and offer letters in bulk from a hiring spreadsheet. This page is the category view.
What HR document automation covers
These are all the same merge, with different stationery:
- Offer letters
- Employment verification letters
- Salary or compensation adjustment letters
- Promotion letters
- Onboarding packets (often several PDFs from the same row)
- Policy acknowledgment letters
The letterhead stays put. The row changes. Buying a separate product for verification letters and another for promotions is the expensive way to rename mail merge.
Payslips, tax forms, and anything a payroll engine is already producing should stay in that engine. A merge tool will print the numbers you give it. It will not calculate them.
What document automation for human resources needs from the export
Each row is one person. Put every value that changes on the page in its own column.
- Full legal name, work email, and the personal email if the person has not started yet
- Job title, department, location, employment type
- Dates the letter cares about: start, effective, end, offer expiry
- Compensation figures, stored the way they should print ($118,000). Word's merge reads the underlying cell, so a 118000 behind a currency format arrives in the letter as 118000.
- Signatory name and title
- For outward letters, the recipient block: name, organization, address
- An email column, so each PDF can travel with the data that produced it, and a filename stem (
raman-priya-offer) so the zip is notDocument-17.pdf
Pull this from the HRIS as a CSV or .xlsx when the letter type is not one the HRIS already prints.
Keep pay data out of tools you have not signed
Before any of this leaves the building, ask whether the vendor has a data processing agreement (DPA) with your company, and whether the file you are about to upload is in scope. A compensation column is what turns a document vendor into a payroll leak. If the answer is no, do not upload the sheet "just to try the rebuild."
Spot-check before anyone is copied
The longest name on the sheet, the highest number, and one odd row: a contractor, a hyphenated surname. Open those PDFs and read them against the cells. Layouts break at the edges.
Four routes for document automation for HR
Word mail merge
Word is already on most HR machines, and a .docx letter merges from a spreadsheet without installing anything else. What you get is one long file with every letter in it, not a named PDF per person. The offer letters from a spreadsheet post has the click path, the macro that splits the file, and the cases where a handful of letters, once, is the whole job.
The free Google route
When the employee roster is in Google Sheets, Autocrat merges a tagged Google Doc into a separate PDF per row and can mail each file from an address column. You pay for that by retyping the signed-off letterhead into Docs, and a heavy run can stop on an Apps Script quota with some letters out and some not. The offer letters from a spreadsheet post has the click path. The verification letter post uses the same route for a different letter.
The HRIS you already pay for
Most HRIS products generate offer letters from the employee record, with templates, preview, and signature attached. Products such as BambooHR and Rippling sit in this category. If the company already lives in one of these, use it for the letter types it already produces. Do not buy or upgrade an HRIS just to print documents. Export the roster and use one of the other routes on this page, for the letter types it does not generate.
Document-generation tools
PandaDoc belongs here when the letter has to come back signed. Bulk send puts the merge and the countersignature in one product.
The letter becomes a form. Each value sits in a tagged field, so layout choices stop at the edges of those fields, and a letterhead with a crest or a scanned signature flattens into a background the fields sit on top of.
SheetRender is our product.
Upload the letter HR already sends (PDF, image, or HTML; a Word file needs a PDF export first) and the roster as CSV, .xlsx, or a connected Google Sheet. A model rebuilds the layout and wires your columns to it. Each person gets a separate PDF, named from a column you choose. Point the send at an email column and that row's file goes to that inbox. From the Starter plan up, a batch can be scheduled to run by itself (hourly through monthly), so a weekly pile of verification letters does not need someone watching it.
Reconstructing the template sends column headers and a handful of sample rows, plus the example letter, to the model that draws the page. If compensation is on the sheet, those sample rows include pay next to names. Hand that sentence to whoever owns data policy before anything is uploaded.
On the free plan you get 50 documents a month, two templates, files kept 30 days, no scheduled runs, and a "Made with SheetRender" line at the bottom of every page from the first one. Two templates is offer plus verification, and that footer should never appear on a compensation letter. Starter is $19 monthly for 1,500 documents with the footer off, when I last checked. The HR documents use-case page has the fuller workflow.
When a merge is the wrong tool
Documents that need an employee signature or a countersignature need an e-signature product, layered on top or instead. The offer-letter post walks through DocuSign and Dropbox Sign bulk send for that case. Policy acknowledgments are usually in this bucket too.
Wording on compensation letters, and anything adjacent to termination or a change in status, should go through whoever handles employment law in the country of hire. A merge reproduces whatever you uploaded. It is not a lawyer.
Employment verification letters need employer letterhead and a signer in HR or payroll. The verification letter template covers who signs, what stays off the page, and the filled-in sample.
Which letter are you sending?
- Offer letters. Follow the bulk offer letters from a spreadsheet post. If you need a countersigned copy back, that same post has the click paths for DocuSign and Dropbox Sign.
- Employment verification letters. Start from the employment verification letter template and use the merge notes there when the requests arrive in a pile.
- Promotion letters and pay adjustments. If the HRIS already prints these from the employee record, stay there. If you already send a designed PDF, use SheetRender on this page.
- Onboarding packets. Several PDFs from the same row. Keep them in the HRIS when it already issues the packet. Otherwise run a second template over the same columns, or merge only the letter type the HRIS will not print.
Keep the roster right, pick a merge that names files after people, and Thursday's verification letter is the same job as September's offer round. Edit a cell when a start date slips. Do not edit the PDF.