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.
EmployeePayAdjustments), even though they come from different Aimsio form types and business units.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:
LaborMetrics, populating LaborMetricsTypeXRefCode and LaborMetricsCodeXRefCode.EmployeePayAdjustments, with each record's embedded LaborMetrics array referencing metrics created in step 1.A representative mapping from an Aimsio timesheet entry to EmployeePayAdjustments:
EmployeePayAdjustments target structure.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.
Comment Editor X