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 ADP Workforce Now as a paydata batch, in your earnings codes and departments.
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 ADP Workforce Now and enter your company code.
Confirm an earnings code for each hour category and a department for each site.
Pick the schedulers, when it runs and how the file is delivered.
Import the file in ADP Workforce Now as a paydata batch.
A CSV file with a header and one row per worker and earnings code.
Every export of a period has the same Batch ID, so ADP replaces the earlier batch with the new one. If the pay run is finalized, correct it in payroll.
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. ADP Workforce Now 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.