Aligning Labour Data

Labour data is one of the most important sources of project cost information.

However, labour records often originate in field systems and must eventually be recorded inside financial systems.

Without alignment infrastructure, these records frequently diverge.

Common problems include:

• inconsistent project codes
• missing worker mappings
• incorrect cost categories

This guide explains how to maintain labour alignment using Demiton workflows.

Labour Data Sources

Labour entries typically originate from field execution systems.

Examples include:

• Assignar site diaries
• timesheet systems
• payroll exports

Each source may structure labour data differently.

The goal of the alignment workflow is to normalize these records.

Step 1: Retrieve Labour Records

The first step retrieves labour entries from the field system.

Example:

FETCH → assignar.site_diaries

The adapter retrieves raw site diary records.

These records may contain embedded labour information.

Step 2: Extract Labour Entries

Next, a transformation step extracts labour records from the dataset.

Example:

TRANSFORM → extract_labour_entries

This step converts raw records into LabourEntry constructs.

Each entry includes fields such as:

• worker
• project
• date
• hours
• cost category

Step 3: Validate Project Mapping

Before writing labour records to the ERP, project identifiers must be validated.

Example validation checks:

• project exists in ERP
• project code matches canonical structure

Invalid records should be stored in an exception dataset.

Step 4: Map Worker Identities

Workers may appear differently across systems.

For example:

Assignar Worker ID → Payroll Employee ID → ERP Resource

A mapping layer ensures that labour entries reference the correct canonical worker.

Step 5: Post Labour Costs

Once records are validated and normalized, they can be written to the ERP.

Example:

PUSH → business_central.project_ledger

This records labour costs against the appropriate project.

Continuous Alignment

Labour alignment is typically executed on a schedule.

Common execution patterns include:

• hourly ingestion from field systems
• daily financial posting
• payroll reconciliation pipelines

These workflows ensure labour costs remain aligned throughout the project lifecycle.

Outcome

When labour alignment is implemented correctly:

• project costs remain consistent across systems
• payroll reconciliation becomes easier
• project variance becomes visible earlier

This provides more reliable financial insight during project execution.

---