# Send hours to your payroll system

> **Set up with an AI agent:** Connect Chrona MCP for documentation, setup guidance and configuration recipes. Server: https://mcp.chrona365.com/mcp (Streamable HTTP; authentication: None). Your agent needs separately authorized Dataverse tools to apply changes. In Copilot Studio, after importing Chrona, add the Chrona Scheduler connector to your agent alongside Microsoft’s Dataverse tools. [Connection guide](https://chrona365.com/workforce/install-with-an-agent).

Choose your payroll or reporting recipe below for Format setup, code maps, import and corrections. For shared checks, delivery and **Export again**, see [Export hours and staffing reports](https://chrona365.com/docs/workforce/exports).

Before you rely on a recipe, import one file in the system's test company or in a payroll you have not submitted, and check the totals.

## Send hours to ADP Workforce Now

Automatic Data Processing (ADP) Workforce Now takes the file as a paydata batch.

1. In **Integration Studio**, select **New format** and start from **ADP Workforce Now**.
2. Under **Format values**, enter your company code in **Co Code**. The export is blocked until it is set.
3. Map the **Earnings code** map: ADP's own codes are **R** for Regular and **O** for overtime, which the recipe suggests. Confirm a code for each other hour category you send, or choose **Not exported**.
4. Map the **Department** map from each site to its ADP department.

The file has a header and one row per worker and earnings code: **Co Code**, **Batch ID**, **File #** (the worker's **Payroll ID**), **Temp Dept**, **Hours 3 Code** and **Hours 3 Amount**. Import it as a paydata batch.

Correct a period: 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.

## Send hours to Paylocity

Paylocity reads the file through a **Payroll Data converter** that Paylocity sets up for your company.

1. In **Integration Studio**, start a Format from **Paylocity**. The file has a header and the columns **Employee ID** (the worker's **Payroll ID**, the same as their Paylocity employee ID), **Earnings Code**, **Hours** and **Cost Center 1**, one row per worker and earnings code. Hours are decimal, such as `7.50`.
2. Map the **Earnings code** map to your Paylocity earning codes, exactly as they appear on Paylocity's earnings codes report. Paylocity earning codes have 5 characters at most.
3. Map the **Cost Center 1** map from each site. **Cost Center 1** is optional: a site with no code sends the column empty. Cost center codes have 10 characters at most, and no code can contain `&`.
4. Download a sample file. Fill in Paylocity's **Payroll Data Converter Setup** form with the column letter of each field (A: Employee ID, B: earning code, C: hours, D: Cost Center 1), and send it with the sample to your Paylocity representative. Tell Paylocity that the file has a header row. Paylocity asks for 7 calendar days.

Import: in Paylocity, select **Payroll** > **Pay Entry**, the check date and the batch type **TimeImprt**, then **Add Batch**. Select **Create New** (or **Merge Into Existing**), **Upload** the file and **Import**. Review the **Status Report**, check **Batch Totals** and submit payroll.

Correct a period: a new import makes a new batch. Before you import the period again, correct or remove the earlier Time Import batch in **Pay Entry**, or the hours can count twice.

## Send hours to Paycom

Paycom reads the file as a **TAI02** payroll transaction import, through a Secure File Transfer Protocol (SFTP) data set template that your Paycom specialist sets up.

1. In **Integration Studio**, start a Format from **Paycom**. The file has no header and the fields **Employee ID** (the worker's **Payroll ID**: their Paycom employee code), **Earning Code**, **Hours**, **Temporary Rate** (always empty) and **Distributed Department Code**, one row per worker and earning code.
2. Map the **Earning code** map to your Paycom earning codes.
3. Map the **Department code** map from each site, or leave the site with no code to use the worker's home department.
4. Paycom accepts no quotation marks in the file. Use payroll IDs and codes with no commas, so that no value needs them.

Import: put the file on your Paycom SFTP folder (download it, or use a **Web address** action with a flow that writes to SFTP). In Paycom, select **Process Payroll**, the **Data Sets** tab, **New Data Set** and **SFTP File Import**. Select the TAI02 template and the file, then process payroll as usual.

Correct a period: before you import the period again, remove the earlier import's data set in **Process Payroll**, or the hours can count twice.

## Send hours to Paychex Flex

Paychex Flex reads the file as a **Standard Payroll Import** (SPI). Ask Paychex client support to turn on the SPI setting for your company.

1. In **Integration Studio**, start a Format from **Paychex Flex**. The file has a header and the sixteen SPI columns in their order. Chrona fills **Worker ID** (the worker's **Payroll ID**, 10 characters at most), **Pay Component** and **Hours**, and **Labor Assignment** when you map it. The columns for rates, amounts, units, the line date, the check sequence and tax overrides stay empty.
2. Under **Format values**, enter your Paychex company number in **Client ID**, 8 characters at most. The export is blocked until it is set.
3. Map the **Pay component** map to your pay component names, exactly as they appear in Paychex Flex (Company Settings, Pay Items). The names are case sensitive.
4. If you use Paychex Labor Distribution, map the **Labor assignment** map from each site. Otherwise leave it with no codes.

Import: in Paychex Flex, open the current payroll in the **Payroll Center**, select **More Options** > **Import Payroll Data**, select the file and **Import**. Then **Review & Submit**. If one pay item of a check fails, Paychex rejects the whole check.

Correct a period: before you import the period again, remove the earlier import's hours from the open payroll, or they can count twice. After the payroll is submitted, correct it in Paychex Flex.

## Send hours to Employment Hero

1. In **Integration Studio**, start a Format from **Employment Hero**. The file has a header and one timesheet row for each part a worker works: **Employee Code** (the worker's **Payroll ID**), **Date**, **Start**, **End**, **Unpaid Break** and **Location**. A split shift, such as 09:00 to 11:00 and 17:00 to 20:00, has two rows, because Employment Hero takes one timesheet entry per line.
2. Map the **Location** map from each site to its Employment Hero location.
3. In Australian Employment Hero Payroll, open **Manage Employees > Import Timesheets**, select **Custom file upload**, then map the CSV columns and import as the vendor's [timesheet import guide](https://support.yourpayroll.com.au/hc/en-au/articles/17404878791439-How-do-I-import-timesheets) describes. Check the imported hours before using the file in payroll.

The recipe has no **Hour category** map, so the file holds worked time: see [On-call duties and call-ins](https://chrona365.com/docs/workforce/exports#on-call-duties-and-call-ins) for what that means for a duty from home.

Correct a period: set the timesheets back to draft in Employment Hero before you import the period again.

## Send hours to DATEV LODAS

1. In **Integration Studio**, start a Format from **DATEV LODAS**. A Format covers one month.
2. Under **Format values**, enter the **Beraternummer** (adviser number, 4 to 7 digits) and the **Mandantennummer** (client number, 1 to 5 digits). Your tax adviser gives you both. The export is blocked until both are set.
3. Map the **Lohnart** map to your LODAS wage types and the **Kostenstelle** map from each site.
4. Check the first file with your tax adviser, then import it with LODAS's ASCII import.

The file is semicolon-separated text in Windows-1252 with a decimal comma, in three parts. The Format's **Lines before the rows** write the first two:

- **[Allgemein]**: `Ziel=LODAS`, the adviser number, the client number, the separator, the decimal comma and the date format.
- **[Satzbeschreibung]**: record 1, LODAS's standard postings (`u_lod_bwd_buchung_standard`), with the fields of each row. Each column header is the LODAS field name.
- **[Bewegungsdaten]**: one row per worker and Lohnart: the **Personalnummer** (the worker's **Payroll ID**), the first day of the month, the hours, Bearbeitungsschlüssel 1 (hours), the **Lohnart** and the **Kostenstelle**. Each call-in and each duty is a row of its own.

Correct a period: a second import for the same month adds to the first. Delete the earlier import (Bewegungsdaten) in LODAS before you import the new file, or the hours double.

## Send a CMS PBJ file

1. Start a Format from **CMS PBJ** for Centers for Medicare & Medicaid Services (CMS) Payroll-Based Journal (PBJ) XML, per facility and federal fiscal quarter.
2. Map each role's PBJ job title code, each employment type's pay type code, and each site's CMS facility ID and state code. Missing codes block export.
3. Upload the file in the Internet Quality Improvement and Evaluation System (iQIES).

Correct a quarter: upload the new file in iQIES before the deadline, 45 days after the quarter ends; CMS takes no file after it. Then check the Final File Validation Report in iQIES, which can take up to 24 hours.

## Send a PpUGV report

1. Start a Format from **PpUGV** for the Institut für das Entgeltsystem im Krankenhaus (InEK) worksheet under the Pflegepersonaluntergrenzen-Verordnung (PpUGV). Each calendar quarter has day and night rows per ward and month.
2. Map the ward's **Pflegesensitiver Bereich** (area types), **Fachabteilungsschlüssel**, each site's **Standortnummer** and each role's **Berufsgruppe**. Missing codes block export.

Correct a quarter: InEK prefills the annual report (Jahresmeldung) from the quarterly reports sent. Correct the prefilled data in the annual report until 30 June of the next year, or within the extension period you request.

---
Product: Workforce Scheduler
Language: English
Canonical: https://chrona365.com/docs/workforce/payroll-systems
