What is a Scope?

What exactly is a “Scope”?

A scope is a detailed description of exactly what data will move from your HR system (source) to your payroll system (target). It clearly specifies:

• Included Fields: Exactly which fields/data elements will cross the bridge.
• Field Transformation: How fields in your source system transform into fields in your target system.
• Field Mapping: Which values in your source system should become which values in your target system.

Example of a simple Scope definition

In the table, you see clearly illustrated examples of how data moves from your source system to your target system. Let's assume the source system is your HRM system, the target is your payroll system. Each row in the table represents an individual data field and how it's transformed or mapped:

1. 1

   Employee Number → Employee ID

   • The “Employee Number” from your HR system directly matches the “Employee ID” in your payroll system without any changes.
2. 2

   First Name + Last Name → Full Name

   • Your HR system has two separate fields, “First Name” and “Last Name.”
   • In your payroll system, these two fields are combined (concatenated) into one single field called “Full Name.”
3. 3

   Annual Salary → Monthly Salary

   • The “Annual Salary” field in the HR system is converted to “Monthly Salary” in the payroll system.
   • The logic applied is dividing the Annual Salary by 12.
4. 4

   Department Name → Cost Center Name

   • “Department Name” in the HR system corresponds to “Cost Center Name” in the payroll system.
   • For example, “Department B” becomes “Cost Center 2.” This shows a clear mapping where a field may change labels or naming between the two systems.

Why is a scope important?

At BrynQ, we know you're busy. It might seem tempting to speed through the setup of your data integration, especially when dealing with complex HR and payroll processes. But there's one crucial step you absolutely can't afford to overlook: defining a clear scope.

Here's why this step is so important:

1. 1

   🔎 Accuracy and Completeness

   Your scope defines exactly what data moves from your HR system (source) into your payroll system (target). If the scope is incomplete or unclear, you risk sending incorrect or incomplete information. Imagine running payroll without essential fields like salary information or employee ID numbers—it's simply impossible!

2. 2

   🚧 Preventing Critical Errors

   Every field you leave out of your scope won't reach your target system. This isn't just inconvenient—it can have serious consequences. Missing critical fields like an employee's salary, contract details, or cost center assignments leads directly to payroll errors, compliance issues, and extra work later.

3. 3

   💡 Ensuring Smooth Transformations

   Your scope clearly explains how fields in your HR system translate to fields in your payroll system. If this mapping isn't precise, your data can become messy or unusable. Imagine employees getting paid incorrectly due to misalignment between “Annual Salary” and “Monthly Salary”—not good for your reputation or employee satisfaction!

4. 4

   ⏱ Saving You Time and Money

   Spending a little extra attention now to define your scope clearly will significantly reduce problems later. A properly defined scope means less time fixing errors and fewer issues during payroll runs. Ultimately, it saves you time, money, and a lot of headaches.

“If it's not clearly listed in your scope, it won't appear in your target system.”