MyRapidi
MyRapidi

Search our Wiki

Aimsio Dayforce Labor Metrics and Employee Pay Adjustments

Aimsio, a SQL database hosted on Azure, is where the customer manages Jobs, Assets, and field-collected Forms (timesheets, BOLs, crew supervisor entries). This data needs to reach Dayforce so that field-recorded time and pay events are reflected in payroll, without manual re-entry.

Flows

SourceTargetAction
Aimsio JobsDayforce Labor MetricsAdd
Aimsio AssetDayforce Labor MetricsAdd
Aimsio Form Timesheet EntriesDayforce EmployeePayAdjustmentsAdd
West Aimsio Form TimesheetDayforce EmployeePayAdjustmentsAdd
West Aimsio Form BOLDayforce EmployeePayAdjustmentsAdd
West Aimsio CREW Supervisor Form TimesheetDayforce EmployeePayAdjustmentsAdd

All four Pay Adjustment flows write to the same Dayforce object (EmployeePayAdjustments), even though they come from different Aimsio form types and business units.

Why Labor Metrics Has to Run First

Looking at the schema (see Schema Structure & Field Management), EmployeePayAdjustments carries a LaborMetrics array made up of LaborMetricsTypeXRefCode / LaborMetricsCodeXRefCode pairs. Dayforce needs each referenced Labor Metric (for example, a job code) to already exist before it can be attached to a Pay Adjustment, the same way an Item needs to exist before it can appear on an Order.

That's why the integration is sequenced in two layers:

  1. Reference data layer — Aimsio Jobs and Aimsio Assets are synced into Dayforce as LaborMetrics, populating LaborMetricsTypeXRefCode and LaborMetricsCodeXRefCode.
  2. Transactional layer — Aimsio timesheet and form data is synced into Dayforce as EmployeePayAdjustments, with each record's embedded LaborMetrics array referencing metrics created in step 1.

Example Field Mapping

A representative mapping from an Aimsio timesheet entry to EmployeePayAdjustments:

Dayforce FieldSourced From (Aimsio)
EmployeePayAdjustXRefCodeAimsio timesheet entry unique ID
EmployeeXRefCodeAimsio employee/worker reference
PayAdjustmentCodeXRefCodeAimsio pay code / entry type
PayAdjustmentDateDate worked on the Aimsio form
HoursHours recorded on the Aimsio form
JobXRefCodeAimsio Job reference
LaborMetrics[].LaborMetricsCodeXRefCodeAimsio Job or Asset code, already synced as a Labor Metric

The exact field-by-field mapping varies slightly by form type (standard timesheet vs. BOL vs. crew supervisor timesheet), since each Aimsio form captures a slightly different shape of data, but all of them resolve to the same EmployeePayAdjustments target structure.

Result

Field-recorded time and pay events in Aimsio reach Dayforce automatically, with Labor Metrics guaranteed to be in place ahead of any Pay Adjustment that references them, avoiding orphaned or failed adjustment records in Dayforce.