Skip to content
Demiton

Aligning Labour Data

Labour data is one of the most important sources of project cost information. Labour records originate in field systems and must eventually be reflected in financial systems. Without alignment infrastructure, these records frequently diverge.

Common problems include:

  • inconsistent project codes between systems
  • missing or mismatched worker mappings
  • incorrect cost category assignments

This guide explains how to build a labour alignment workflow in Demiton.

Labour data sources

Labour entries typically originate from field execution systems. Examples include Assignar site diaries, timesheet platforms, and payroll exports. Each source may structure labour data differently — the alignment workflow normalizes them into a canonical form.

Step 1: Retrieve labour records

FETCH → assignar.site_diaries

The Assignar adapter retrieves raw site diary records. These may contain embedded labour information across multiple workers and projects.

Step 2: Extract labour entries

TRANSFORM → extract_labour_entries

This step converts raw site diary records into LabourEntry business objects. Each entry includes:

  • worker
  • project
  • date
  • hours
  • cost category

Step 3: Validate project mapping

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

GOVERN → validate_project_mapping

This step checks that each project code exists in the ERP and follows the canonical naming convention. Invalid records are written to an exception dataset for manual review.

Step 4: Map worker identities

Workers appear differently across systems. A mapping layer ensures labour entries reference the correct canonical worker identity:

Assignar Worker ID → PayCat Employee ID → ERP Resource

The platform resolves these mappings using the worker identity graph. Unmapped workers are flagged as exceptions.

Step 5: Post labour costs

PUSH → business_central.project_ledger

Once records are validated and normalized, they are written to the ERP project ledger. All PUSH operations support dry_run: true for validation before production writes.

Continuous alignment

Labour alignment is typically executed on a schedule — hourly ingestion from field systems, daily financial posting, and payroll reconciliation pipelines. See Scheduled Pipelines for configuration.

Outcome

When labour alignment is in place:

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

This provides reliable financial insight throughout project execution.

Next steps