County Payroll Automation Built to Scale with Windmill
County payroll automation with BambooHR and Windmill: how one Idaho county generates its three pension reporting files every payroll run. See the workflow.
County payroll automation doesn't have to start as a large, multi-system project. For one county, a focused one-way workflow reads payroll data from BambooHR, generates the three files the Idaho pension reporting system requires in Windmill, and hands them off. It went live in November 2026. The county now runs payroll on a modern HR system and stays compliant with the state system, without hours of manual reformatting every payroll.
A county government was moving payroll operations into BambooHR while still needing to produce three files for an Idaho pension reporting system after each payroll run. The reporting requirement was not optional: without the files, the payroll migration could not move into production.
If the workflow worked for the first county, the same setup could be adapted for other counties with the same reporting requirement.
This is a useful pattern for human resources teams that are adopting a modern HR platform while keeping a required government or payroll reporting process outside that platform.
The challenge
The county had already invested time in configuring BambooHR. Employee records, year-to-date information, and some time entries were in place, but the first planned live payroll had been delayed because the reporting workflow was not ready.
Three constraints shaped the implementation:
The output had to match a defined reporting format. The workflow needed to generate three files for each payroll run, not just move a generic employee export.
The delivery window was short. The first build needed to be ready in about one week, with testing before the next intended live payroll.
A sandbox was unavailable. The team had requested a separate BambooHR test environment, but waiting for access would have pushed the project further out.
The safest response was not to write back into BambooHR. The integration was designed as a one-way read from BambooHR and a write of generated files to the reporting destination. BambooHR's API supports authenticated access to employee data and report generation (see the BambooHR API documentation), which makes that direction practical for a controlled export workflow.
The solution
The implementation used Windmill, an open-source platform for running scripts and workflows, as the workflow layer. Windmill supports schedules, webhooks, and on-demand runs for scripts and flows (Windmill triggers documentation), so the same core logic can support a test run, a scheduled payroll process, or a manual rerun when an operator needs to validate an output.
The architecture was intentionally narrow:
Read the source data. Connect to BambooHR with an appropriately permissioned account and retrieve the payroll fields required for the reports.
Transform the data. Normalize field names, dates, identifiers, and payroll values into the structure expected by the pension reporting system.
Generate three files. Produce the required report files as separate, reviewable outputs for each payroll run.
Keep the source system read-only. Do not modify employee or payroll records in BambooHR as part of the reporting workflow.
Validate before go-live. Upload test files to the reporting system, correct any formatting or mapping errors, and repeat the process until the files pass validation.
Document the rerun path. Make it clear how an operator can run the workflow again, inspect its outputs, and recover when a payroll run changes.
Windmill's BambooHR integration also gives scripts, flows, and apps reusable access to employee, time-off, timesheet, and report data. That makes it a reasonable foundation for an implementation that may later be adapted to more than one county.
Results
The workflow went live in November 2026 with the county's first payroll run on BambooHR. What changed:
The county moved payroll onto a modern HRIS (BambooHR) and still meets the Idaho pension reporting requirement.
Staff no longer spend hours reformatting payroll data by hand for every payroll run. The three files are generated for them.
BambooHR stays read-only: a one-way export, three report files, and no writes back to employee records.
A repeatable county template: once the mapping and file-generation logic are proven, later county rollouts should need configuration changes rather than a completely new design.
That only works if the first deployment is documented carefully, including field mappings, validation steps, exception handling, and the exact files the reporting system requires.
What made this county payroll automation reusable
The reusable asset was not just a Windmill script. It was a small implementation package containing:
a permissioned BambooHR connection;
a canonical field map;
report-generation logic for each required file;
validation fixtures and example outputs;
an operator checklist for each payroll run;
a documented process for county-specific changes.
That distinction matters. Copying code without preserving the mapping and validation process creates a new support burden for every rollout. Packaging the workflow, tests, and operating instructions together makes the next implementation faster without hiding the differences that still need review.
Key takeaway
A county payroll automation project can become a scalable service when the first implementation is kept narrow, read-only at the source, and validated against the required reporting output. Windmill provides the execution layer, BambooHR provides the source data, and a documented three-file validation process creates the foundation for repeatable county deployments.
Facing a similar reporting handoff?
Getting a new HR system live while a state reporting format sits outside it usually stalls at the field mapping and file validation step. If your HR or payroll team is facing a similar handoff, book a free consulting call and we'll map the source fields, output requirements, validation steps, and rollout plan with you.
A Google Ads agency for home-services firms swapped fragile Zapier lookups for Make + Airtable lead-to-revenue matching across four CRMs. See how it works.
Restaurant automation for a nine-location group: AI review replies, one daily sales report, and an OpenTable rollout. See what to automate first and why.
A compounding supplier moved 7,000 formulas into a structured Airtable library with automated PDFs, then added member analytics across Xano, Stripe, and Retool.