A retrocalculation is the recalculation a payroll engine runs when a prior pay period has to be corrected. Retrocalculations are triggered by backdated salary changes, corrected hire or termination...
FAQs
Is AI field mapping enough to integrate HR with global payroll?
No. Field mapping is one of three parts of an HR-to-payroll integration. The other two parts are validation, meaning the values the payroll system accepts, and transformation, meaning how source...
What is the difference between an iPaaS and a context layer for payroll?
An iPaaS such as Workato, Boomi or Tray.ai is a general-purpose integration tool that moves data between any two systems without built-in payroll knowledge. A context layer such as datascalehr is...
What is destination-driven extraction in payroll integration?
Destination-driven extraction means the payroll system's template decides what data is pulled from the HR system, in what shape and in what order. Most integration tools build an output file from...
Why is HR-to-payroll integration a four-dimensional problem?
HR-to-payroll integration has to solve time, structure, vocabulary and destination at the same time. Time means matching effective-dated HR records to pay periods, including retros, future-dated...
Does datascalehr’s AI hallucinate payroll data?
No. datascalehr is predictive, not generative. KMod™ selects a transformation from a finite set of valid mappings and never invents a data value. When a large language model is used, the model...
Will the integration break when a payroll provider changes its file format?
No. datascalehr reads data by meaning rather than by fixed column position, so a changed file format does not stop the integration. datascalehr flags only the new or changed elements for a payroll...
How long does payroll integration take per country?
With datascalehr, payroll integration takes under an hour per country. KMod™ has learned from more than 4 million validated mapping decisions across 180 countries, so KMod™ predicts most mappings...
Does the local payroll provider need an API?
No. Most local payroll providers have no API and deliver flat files, CSV files, fixed-width files or Excel exports. datascalehr learns the structure of whatever file arrives, so datascalehr connects...
How is datascalehr different from a unified payroll API like Merge or Finch?
Unified payroll APIs are built mainly to read standard HR and payroll fields out of common systems. Global payroll also needs write-back, where corrected pay data returns to a local provider with...
How is a context layer different from an iPaaS like Boomi or Workato?
An iPaaS moves data between systems without payroll knowledge, so an integration team configures every mapping by hand and rebuilds connectors when formats change. A context layer understands what...
Do I need developers to build payroll connectors?
No. Payroll mapping decisions call for payroll knowledge, which payroll specialists already have. A payroll specialist uploads a sample file, reviews the field mappings datascalehr predicts and...