Recognize PrismHR exports
Payroll register and report exports are detected from their column headers, such as Emp ID, Pay Type and Hours/Units. You can also choose PrismHR yourself.
Export a PrismHR payroll register as CSV or Excel. WagePilot recognizes the columns, combines pay-code lines into one row per worker and job, and reviews the result. Or connect PrismHR directly (read-only) to sync pay runs on a schedule. Nothing is written back.
No. PrismHR continues to calculate and run payroll. WagePilot reviews the project export as the public-works compliance layer before reporting.
PEOs and payroll bureaus already run client payroll in PrismHR. Start with the register export you produce today. There is nothing to migrate and no parallel payroll to run.
Payroll register and report exports are detected from their column headers, such as Emp ID, Pay Type and Hours/Units. You can also choose PrismHR yourself.
Regular, overtime, double-time and fringe lines are combined per worker, week, project and classification. Pay codes WagePilot cannot map are flagged. Their amounts are never guessed.
Compare each worker's classification, base rate and fringe with the wage determination you supply.
See missing fields, arithmetic discrepancies, wage shortfalls and classification questions, each with the source rows behind it.
Use the payroll register (compact format) or a report export that lists the pay type, hours, rate and pay for each employee.
Choose PrismHR or let WagePilot detect it, then add project context and the applicable wage determination.
Confirm unmapped pay codes, verify the source records and work through each open check.
Carry the corrected payroll into the WH-347, state form or portal the project requires.
Validation boundaryWagePilot reads PrismHR file exports (CSV or XLSX) and can also connect to PrismHR through its API with a read-only web service user. It never writes changes back. Column mappings come from PrismHR's public report documentation and should be confirmed against your own export.
Use a WH-347, CSV, XLSX, or payroll export.
Rules handle arithmetic; contextual review handles ambiguity.
Clean entries disappear into the background.
What did WagePilot find?Why was it flagged?What evidence did it use?
You are shown the reasoning—not asked to trust a black box.The agent does the work. You keep the authority.
Recurring certified payroll for your own workforce.
Multiple projects and subcontractor review.
Higher project and submission volume.
No. The launch workflow starts with a PDF, CSV, or XLSX export. Your payroll system remains the source.
No. The diagnostic does not file anything. Material decisions and regulated submissions remain with you.
The item is surfaced with review limitations, supporting evidence, and a recommended next action for human review.
Yes. Findings show the source, supplied rule evidence, calculation where applicable, review limitations, and next action.
Code performs deterministic comparisons against wage rules you supply. The MVP does not automatically identify the legally applicable determination.
Files are held only while the review runs and are deleted when it finishes. PDF files are sent to OpenAI for structured extraction and the temporary uploaded file is deleted after processing. Unless your organization turns on the optional, encrypted keeping of originals in Settings, WagePilot does not keep payroll files.
Yes. Start with one payroll and one project without creating an account or entering a credit card.
The initial diagnostic runs a narrow supplied-rules review. California, Illinois, and New York pages describe their reporting workflows, but WagePilot does not claim complete 50-state rules or filing support.
Get a useful initial review before choosing a plan. No credit card required.