Payroll exports

Approved hours, ready for payroll.

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.

  • Approved time only
  • Your payroll codes
  • Every file saved
A clinic receptionist in scrubs checking the day on a tablet at the front desk
A Format's Hour category code map: Hours balance payout to PAYOUT and Paid leave credit to LEAVE, both confirmed; Hours balance change not exported; Public holiday credit unresolved.

How it works

From approved timesheets to a file your payroll imports, in four steps.

  1. Set up a Format

    Start from a supplied recipe, or define your columns: a field, fixed text or Combine.

  2. Confirm your codes

    Code maps translate Chrona's values into your payroll's codes. Not exported leaves a value out on purpose.

  3. Add an export action

    Pick its schedulers or a whole site, how it is delivered and when it runs.

  4. Check and export

    Check the period, the workers and the codes, then export. The finished file is saved.

What every export checks

An export takes only what payroll should get, and shows what is missing before it runs.

Approved time

Unapproved time stays out of the file.

Payroll IDs

A worker without a Payroll ID is left out, with a warning.

Codes

A missing code stays unresolved until you confirm it or choose Not exported.

Hours balance

Balance changes, payouts and credits are separate lines, so nothing counts twice.

Statutory reports

A statutory format can block the export while required codes or inputs are missing.

No money

No rates or amounts: the file carries hours, hour categories and times.

Saved files

A finished export keeps its file, and the Format and source data used to build it.

Corrections

History shows what changed before Export again makes the next numbered export.

Then, send it

  • Download the saved file and import it into your payroll.
  • Or send it to your HTTPS receiver, signed, and pass it on with Power Automate.
  • Or let your own application read exports through its own Dataverse access.
  • A web response means your receiver accepted the file, not that payroll imported it.
  • Automatic exports run on the Chrona Scheduled tasks flow.

Without and with Integration Studio

  1. Without

    Hours typed in again

    Someone copies hours from the roster into payroll, code by code.

  2. With

    Hours in your codes

    Approved time leaves Chrona already mapped to your payroll's codes.

  3. Result

    A file you can trace

    Each export keeps its file and its sources, and History compares a period before you send it again.

Send a period again, and see what changed.

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.

An export's History: export 2, made with Export again, shows changed source time and payouts against export 1; both files are saved.

Pick your payroll system or report

Start a Format from the recipe for your payroll, then map your codes.

All integrations

How-⁠to guides

Questions

Does Chrona calculate pay?

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.

Which payroll systems does it work with?

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.

What happens to a code I have not set?

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.

How do hours-balance entries reach payroll?

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.

Can the file be sent automatically?

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.

What if I need to correct a period?

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.

Can my AI agent set it up?

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.

Send your next pay period in your payroll's codes.

Download from the Chrona Portal and roster your first five workers free, in your own Power Apps.