Approved time only
Time that is not approved stays out of the file, and the check before export says who it belongs to.
Auto Schedule, a constraint solver built on Timefold, builds the roster; Integration Studio sends the approved hours to Paylocity's Pay Entry as a Time Import batch, in your earning codes and cost centers.
Approved time leaves Chrona in your payroll’s own codes.
Time that is not approved stays out of the file, and the check before export says who it belongs to.
Each Overtime rule of your agreement is its own hour category. Map it to your payroll's overtime code.
Each call-in and each on-call duty is a row of its own, so payroll can round each one and price any on-call allowance.
The file carries hours and hour categories. Your payroll calculates pay from its own rates.
In Integration Studio, start a Format from Paylocity and map your earning codes and Cost Center 1.
Send a sample file and Paylocity's Payroll Data Converter Setup form to your Paylocity representative, once.
Pick the schedulers, when it runs and how the file is delivered.
In Pay Entry, add a batch of type TimeImprt, upload the file and review the status report.
A CSV file with a header and one row per worker and earning code.
A new import makes a new batch. Before you import a period again, correct or remove the earlier Time Import batch in Pay Entry, or the hours can count twice.
Set up your export, match your codes and fix a past period, step by step.
What Chrona checks before it sends your hours, and what payroll gets.
No. The file carries approved hours and hour categories, never rates or money. Paylocity calculates pay from its own rates.
Workers with approved time and a Payroll ID. A worker without a Payroll ID is left out, and the check before export lists them.
Yes. Import one file in a test company or in a payroll you have not submitted, and check the totals before you rely on it.
Download from the Chrona Portal and roster your first five workers free, in your own Power Apps.