Chrona, A Konfigure8 productDOCSWebsite
Account and billingGlossarySupport

Export hours and staffing reports

Export approved time through Integration Studio: a Format defines the file; an action selects source schedulers, delivery and timing.

View as Markdown
Page tools
View as Markdown
On this pageSet up a FormatChoose how hours-balance entries reach payrollOvertimePremium ratesOn-call duties and call-insSelect the sourceCheck and exportCorrect an earlier exportChoose deliveryBuild a web receiverConnect the receiver to Power Automate

Files carry hours, categories and times, never rates or money. Payroll calculates pay using its own rates; Chrona’s rates estimate roster costs only. Staffing reports use worked time, excluding hours-balance payouts.

Set up a Format

Start from a supplied recipe or define your columns. Each recipe has its delivery guide in Send hours to your payroll system. Confirm the target system’s import version before use. A matching preview does not prove that the target accepts the file: test the import in the target’s test account.

Setting Purpose
Columns Field, fixed text or Combine. Combine joins and optionally formats values; it runs no formulas.
Code maps Translate Chrona values into confirmed earnings, cost-center or other target codes.
Format values Reusable company/client values with text or digits-only rules, length and required status. Columns and Combine parts can read them. Missing required values block export and are named.
Lines before the rows Text-file preamble: fixed text or Combine using Format values or column headers.

Confirm each code’s meaning or deliberately choose Not exported. Unmapped hour categories block Save, as do missing fixed-width column widths. Statutory formats also block export for missing required codes or report inputs.

Use the CMS PBJ or PpUGV recipe for the corresponding report. Custom XML columns do not create an arbitrary statutory schema. Generic JSON and XML formats retain Chrona’s document structure.

An agent can help with setup through Chrona’s MCP server. format_recipe explains how to read your specification locally. generate_configuration prepares requests for the Format, confirmed codes and export action. The MCP server does not receive your payroll sample, signing secret or private callback URL, and does not write to Dataverse.

Choose how hours-balance entries reach payroll

Each Format controls this through its Hour category code map. Confirm a payroll code or choose Not exported for each applicable category. A missing code leaves the decision unresolved. A Format that sends only a total still needs this map; the map does not need an output column.

Hours balance change is a signed adjustment from the posted Accrual and Adjustment entries. Hours added to the bank have a negative export value; hours removed from the bank have a positive value. Hours balance payout and Minus balance are separate. Paid leave and public holiday credits are also separate from worked hours.

For example, 44 worked hours and a 6-hour bank credit produce 44 worked hours and a −6 balance-change line if that category is mapped. If the Format excludes the balance change, it sends the 44 worked hours. Confirm how your payroll system processes these codes and signed values. Keep payout lines separate from the balance change so the same payout is not counted twice.

The export check needs the approved period’s saved hours-balance calculation and the complete accounting source for whole-worker balance and credit entries. Use an action that includes the required sources, or explicitly exclude those categories. Excluding them does not resolve missing inputs needed to classify worked hours or overtime.

Overtime

Map each agreement Overtime rule’s hour category to a pay code in Integration Studio. Overtime uses approved time against published shifts; each hour counts once. It takes the last hours worked: for Friday 16:00–Saturday 02:00 with overtime after 8 hours a day, the two Saturday hours are overtime.

Within each period, from day to roster period, After a set number of hours counts first. Then:

Basis, in order Hours counted
Beyond the rostered shift Daily hours beyond published shifts. With no published shift that day, all work is beyond roster.
Days in a row in the week The named consecutive day, such as the seventh, and later days of that run. An hour already held by a higher-rate daily Overtime rule keeps that rate.
Past full-time weekly hours Weekly unplanned hours above full time, less next week’s shortfall. Next-week paid leave and holiday credits count. Planned hours are excluded.

When the export period ends before the next week is over, the export sends those hours as overtime, marked provisional, and the check before export lists them. Export again after that week settles them. The export carries hours and hour categories, not rates or money.

An Overtime rule with Days counts only on those days, by the day an entry starts, so Sunday overtime is a category of its own.

Premium rates

Map each agreement premium rate’s hour category to a pay code. Approved hours move from Regular to that category according to the rule:

Rule Hours moved
Days and times Hours within those days and times.
Whole night shifts Entire night shift.
Whole shifts that start between Entire shift starting within the selected days and times.
Whole shifts that finish between Entire shift finishing within them.

Shift start/end use published times: early clock-ins or late clock-outs do not change the shift’s classification. Work without a published shift uses its own times. Public holidays use the site’s holiday calendar.

A premium rate’s category holds the whole hour, so map it to a pay code that pays the hour with its premium, such as 150% of the rate. Those hours are not in Regular: a code that pays only the extra, such as a supplement or a differential paid on top of the hour, leaves the hour’s base pay out.

A premium rate set to Adds on top under With other rates is different: its hours stay in Regular, in an Overtime rule’s category or in the premium rate that holds them, and its own category repeats them as a supplement line. Map it to a code that pays only the extra, such as a night differential. The file’s total hours count each hour once, and a Format that sends only total hours leaves the supplement out and names it on the preview’s Left out line.

Except supplements, each hour has one category. The highest-paying premium or overtime rate wins, using the worker’s hourly rate or the role’s Standard hourly rate. Premium wins a tie with overtime. An overtime hour retained by a premium still counts as overtime once; weekly rules do not count it again.

Rates include pay loading: of the rate adds loading percentage points; of the rate with loadings multiplies the loaded rate. With no worker rate to compare a percentage and an amount, the percentage wins and the export check names the worker and day.

Example: comparing a premium and overtime rate

With 25% loading, a 150% premium of the rate with loadings is 187.5%. Overtime at 160% of the rate is 185%. The premium holds the hour.

A pay loading has no category of its own. Add the Employment type column or code map to the Format, so each row carries the worker’s employment type on that day, and your payroll system applies the loading. Call-ins and duties keep their own categories.

On-call duties and call-ins

For worker steps, see Record on-call work.

A voided approved call-in is excluded; if previously exported, Export again identifies removed time.

Hour category Time exported
On call at the workplace Worked time on the duty.
On call from home Published duty hours, without clocking. Not working time or overtime; Formats without an Hour category map exclude it and show hours under Left out.
Call-in Work in each call-in.
Call-in travel On-site call-in travel, both ways.

Each duty and call-in has its own row with start, end and start day. Payroll prices daily allowances, rounds call-ins and applies minimums; Chrona prices no on-call allowance. Workplace-duty time, call-ins and travel count toward overtime, each hour once.

Each call-in says where it was worked, On site or Remotely. The worker or planner chooses when they record it; a call-in on a duty at the workplace is always On site. An on-site call-in runs from setting off to getting back, and its travel is part of its times. The Centers for Medicare & Medicaid Services (CMS) Payroll-Based Journal (PBJ) report leaves on call from home out, and remote call-ins too: PBJ counts hours worked onsite only (CMS PBJ Manual v2.8, section 2.2). It reports time on call at the workplace and the work minutes of each on-site call-in, without the travel.

On-call field Value
Start with UTC offset, End with UTC offset Site time and Coordinated Universal Time (UTC) offset, such as 2026-10-09T22:00:00-04:00, allowing payroll to split at midnight.
Where worked onSite or remote; map to payroll codes.
Travel (minutes) Call-in travel.
Duty type onCallAtWorkplace or onCallFromHome; map to payroll codes.

If the export cuts a pay period, choose Not exported for Hours balance change, Paid leave credit and Public holiday credit. Chrona does not split these whole-period amounts between days. To include them, use a Format whose export period contains the complete pay period.

Select the source

Select individual schedulers, or all schedulers at a site. A site source includes schedulers added to that site later.

To include a worker’s Hours balance payout, set their Home group on a source scheduler: on that scheduler’s board, select Workers. A payout is excluded when the worker has no Home group or that group’s scheduler is outside the action’s sources. Worked time can still be included. Check this setup before approving the file for payroll.

A pay-period Format needs compatible Mobile pay periods for the workers who contribute time or accounting entries to that period. An unused scheduler member without Mobile enrollment does not block the export. Selecting fewer workers does not bypass a period conflict.

You need access to every source scheduler to run the action or read its history and files. Saved exports also retain their original source scope. A Workforce Admin can pass this check. Changing the Format or action requires Change settings on every scheduler it affects.

Check and export

Check the period, included workers and codes before export. Unapproved time stays out of the file. A worker without a Payroll ID is also excluded. Resolve blocking report errors. Review warnings about missing payroll IDs, excluded employment types and overlapping actions before continuing.

To resolve missing or returned time first, see Submit your timesheet and fix a missed clock-in.

The check names these blocking errors:

  • An enabled overtime, premium rate or pay loading rule missing a required Agreement rules value.
  • A fixed-width column without a width, or a value exceeding it. The Format editor identifies the column.
  • A site without a time zone.

The Format preview shows no file until missing site time zones and rule values are set; it names each rule’s first missing value.

Export lists what the file leaves out: hours with no code, values sent with a blank code, and workers with no Payroll ID. You confirm the list, or go back and fix it. An automatic export stops instead, and the Auto Task Log shows the failed run. Open the export action and check the period: its check lines name the same hours, values and workers.

The export runs in parts. A finished export keeps its file and the Format and source data used to build it. A download returns that saved file.

Correct an earlier export

Review History before exporting the period again. The correction comparison identifies changed source time, payouts, hours-balance amounts, credits and calculation inputs. It does not calculate a payroll adjustment.

Export again creates the next numbered export for the whole period. Read the Format’s correction note and complete the target system’s replacement procedure first. Do not assume that importing another file replaces the earlier import.

Choose delivery

Method Result
Download You download the saved file and import it into the target system.
Web address Chrona sends the saved file to your HTTPS receiver with a signature. Your receiver forwards it to the target.
API Your application reads exports through its own authorized Dataverse access.

A successful web response means that your receiver accepted the export. It does not prove that payroll imported it. Keep the receiving system’s result with your integration records.

Automatic exports use the existing Chrona Scheduled tasks flow. An approval-based action also needs a fallback time. A scheduled time is the earliest due time; the hourly flow and unfinished work can delay processing. See Auto Task Log.

Build a web receiver

Use the receiver URL approved for your action. Create its signing secret through the export settings operation and store the returned secret immediately; Chrona returns a newly generated secret once. Do not place the secret or a signed callback URL in chat, an MCP request, a shared plan or an ordinary log.

The receiver gets this JSON structure:

{
  "version": 1,
  "exportId": "<export id>",
  "actionId": "<action id>",
  "fileName": "<file name>",
  "mime": "<content type>",
  "sha256": "<file SHA-256>",
  "contentBase64": "<file bytes as base64>"
}

The X-Chrona-Export-Id and Idempotency-Key headers contain exportId. X-Chrona-Signature contains sha256= followed by the hexadecimal HMAC-SHA256 of the exact UTF-8 request body. Decode the stored base64 signing secret before using it as the HMAC key.

The receiver must:

  1. Read the original body bytes. Verify the HMAC with a constant-time comparison before accepting the file. Do not parse and serialize the JSON before signature verification.
  2. Check the expected action, file size and safe file name. Decode contentBase64 and compare its SHA-256 with sha256.
  3. Save the export durably under a unique exportId before returning success. If that ID already exists, require the same file hash and acknowledge it without another import. Reject an ID reused with different content.
  4. Record delivery to the destination separately. Use the same export ID for destination duplicate checks. An uncertain destination result needs reconciliation before retrying an operation that could duplicate payment or email.
  5. Return a 2xx response only after durable acceptance. Keep the request within ten seconds; continue longer work from the saved record.

Chrona retries the same export ID and file after a failed response. A receiver can therefore see the same request again after it already accepted it. Retry reuses the saved export; Export again creates a new numbered export. Changing the receiver address does not redirect an existing export to another destination.

Connect the receiver to Power Automate

Use your verified receiver to start a flow with When an HTTP request is received. Keep the flow’s authentication settings consistent with the receiver’s identity. Microsoft supports tenant and specified-user restrictions on this trigger. Chrona’s signature is separate from Microsoft Entra bearer-token authentication; a signature alone does not satisfy a tenant-restricted trigger. See HTTP trigger authentication.

After signature verification and durable duplicate checking, route the saved file through the appropriate connector:

Destination Flow action and inputs
SFTP server Use the SFTP-SSH connector to create the file in the approved folder. Supply the saved file name and decoded file bytes.
SharePoint folder Use SharePoint — Create file with the selected site, folder, saved file name and decoded bytes.
Payroll mailbox Use Office 365 Outlook — Send an email (V2) with the approved recipients and the saved file as an attachment. Reconcile an uncertain send before sending again.
TechnologyOne or another payroll system Use the import endpoint, connector or file-transfer process approved for your installation. Match the confirmed Format and record the target’s import result. A generic webhook is not proof of a supported vendor import.

If the flow cannot verify the exact body signature and reserve the export ID durably, put those operations in the receiver before the flow. A secret trigger URL is not a substitute for the Chrona signature check.

Test an invalid signature, the same export sent twice, a response lost after acceptance and a destination failure before enabling automatic delivery. Confirm that each case creates at most one destination import.

Search documentation

Browse documentation

Choose documentation

Connect your agent to Chrona

Connect Chrona MCP for documentation, setup guidance and configuration recipes.

Server address

https://mcp.chrona365.com/mcp

Streamable HTTP; authentication: None.

In Copilot Studio, after importing Chrona, add the Chrona Scheduler connector to your agent alongside Microsoft’s Dataverse tools.

Your agent needs separately authorized Dataverse tools to apply changes. Connecting Chrona MCP alone does not grant access to your environment.

Ask AI

How can we help?

Ask about Chrona’s setup, features or terminology. Answers link to the documentation they use.

Answers use public documentation. Check the linked sources.