Approved time
Unapproved time stays out of the file.
Integration Studio turns approved time into the file your payroll imports, in its own codes. Chrona exports hours, hour categories and times, never rates or money: your payroll calculates pay. Each file is saved, and History compares a period before you send it again.

From approved timesheets to a file your payroll imports, in four steps.
Start from a supplied recipe, or define your columns: a field, fixed text or Combine.
Code maps translate Chrona's values into your payroll's codes. Not exported leaves a value out on purpose.
Pick its schedulers or a whole site, how it is delivered and when it runs.
Check the period, the workers and the codes, then export. The finished file is saved.
An export takes only what payroll should get, and shows what is missing before it runs.
Unapproved time stays out of the file.
A worker without a Payroll ID is left out, with a warning.
A missing code stays unresolved until you confirm it or choose Not exported.
Balance changes, payouts and credits are separate lines, so nothing counts twice.
A statutory format can block the export while required codes or inputs are missing.
No rates or amounts: the file carries hours, hour categories and times.
A finished export keeps its file, and the Format and source data used to build it.
History shows what changed before Export again makes the next numbered export.
Without
Someone copies hours from the roster into payroll, code by code.
With
Approved time leaves Chrona already mapped to your payroll's codes.
Result
Each export keeps its file and its sources, and History compares a period before you send it again.
History compares the period with its earlier export: changed source time, payouts, hours-balance amounts, credits and calculation inputs. Export again makes the next numbered export for the whole period. It calculates no payroll adjustment: follow your payroll’s replacement steps first.
Start a Format from the recipe for your payroll, then map your codes.
Your approved hours as an ADP paydata batch. A new export replaces the old one.
Your approved hours, ready for Paylocity's Time Import.
Your approved hours as a Paycom payroll import file.
Your approved hours as a Paychex Flex import file.
The staffing file nursing homes send to CMS each quarter.
Your approved hours as Employment Hero timesheets.
Recipes, columns, Combine and code maps.
How balance changes, payouts and credits reach payroll.
The delivery guide for each recipe, system by system.
History, Export again and the replacement steps.
The signed request, its checks and duplicate handling.
No. Chrona exports approved time: hours, hour categories and times. Your payroll calculates pay from its own rates. The rates in Chrona only estimate the roster’s cost.
Chrona ships recipes for ADP Workforce Now, Paylocity, Paycom, Paychex Flex and Employment Hero, and for the CMS Payroll-Based Journal (PBJ). For another payroll, define your columns and map Chrona's values to its codes. Confirm the target's import version, and test the import in its test account before you rely on it.
It stays unresolved. Set a code only after you confirm its meaning, or choose Not exported to leave a value out on purpose. A statutory format can block the export while required codes are missing.
Each Format's Hour category map decides. Balance changes, payouts and paid leave and public holiday credits are separate categories: confirm a payroll code or choose Not exported for each. Keep payouts apart from balance changes, so the same hours are not paid twice.
Yes. An export action can run at a set time on the Chrona Scheduled tasks flow, and send the saved file to your HTTPS receiver with a signature. A Power Automate flow can pass it on to an SFTP server, a SharePoint folder or a payroll mailbox.
Review History first: it shows changed source time, payouts, balance amounts and credits. Export again makes the next numbered export for the whole period. Follow your payroll’s replacement steps, as another import may not replace the earlier one.
Yes. Chrona's Model Context Protocol (MCP) server explains how to read your payroll specification and prepares the Format, the confirmed codes and the export action. It never receives your payroll sample or signing secret, and does not write to Dataverse.
Download from the Chrona Portal and roster your first five workers free, in your own Power Apps.