With Lattice Compensation, admins can sync employee pay data from an HRIS to use in compensation cycles. Learn more in Auto-sync Compensation Default Attributes with an HRIS.
When syncing compensation default attributes to your HRIS, admins have the flexibility to link the Lattice Compensation default attribute to a native or custom field in an HRIS. The ability to sync to a native HRIS field is dependent on the integration permissions of your specific HRIS: below are some guidelines on recommended alignments between Lattice and your HRIS.
Note: Before attempting to sync an HRIS attribute into Lattice, ensure that the equivalent attribute is set up and up-to-date in the HRIS.
View by HRIS integration:
ADP
When syncing ADP attribute Pay Amount to Lattice default attribute Base pay amount, only annualized pay can be synced, regardless of the employee’s pay type (salary or hourly).
Lattice default attribute | ADP native attribute | ADP attribute name in Lattice | Required for Comp Cycles? |
Base pay amount | Employment > Regular Pay > Annual Salary | Pay Amount | Yes |
Currency | Employment > Regular Pay > Pay > Currency | Currency | Yes |
Pay effective date | Employment > Regular Pay > Effective date | Pay effective date | Yes |
Pay type | Employment > Regular Pay > Regular Pay Rate | Pay type | Yes |
Bonus amount | set up as a custom (number) field in ADP | [custom ADP attribute] | No - optional |
Variable pay amount | set up as a custom (number) field in ADP | [custom ADP attribute] | No - optional |
BambooHR
Lattice default attribute | BambooHR native attribute | BambooHR attribute name in Lattice | Required for Comp Cycles? |
Base pay amount | Job > Compensation > Pay Rate | Pay rate | Yes |
Currency | Current Code in Job > Compensation > Pay Rate | Pay Rate: Currency | Yes |
Pay effective date | Job > Compensation > Effective Date | Compensation: Date | Yes |
Pay type | Job > Compensation > Pay Type | Pay type | Yes |
Bonus amount | Job > Bonus > Amount | Bonus: Amount | No - optional |
Variable pay amount |
Job > Commission > Amount OR set up as a custom (number) field in BambooHR |
Commission: Amount OR [custom BambooHR attribute] |
No - optional |
Gusto
Gusto only supports USD today. Linking Lattice’s Currency field to “Gusto default currency (USD)” will allow you to auto-assign all employees to USD.
Lattice default attribute | Gusto native attribute | Gusto attribute name in Lattice | Required for Comp Cycles? |
Base pay amount | Job & Pay > Compensation > Wage | Compensation rate | Yes |
Currency | N/A - Gusto only supports USD | Gusto default currency (USD) | Yes |
Pay effective date | Job & Pay > Compensation > View compensation history > Effective Date | Compensation effective date | Yes |
Pay type | Job & Pay > Compensation > Per (options: hour, month, week, year) | Payment unit | Yes |
Bonus amount | set up as a custom (number) field in Gusto | [custom Gusto attribute] |
No - optional |
Variable pay amount | set up as a custom (number) field in Gusto | [custom Gusto attribute] |
No - optional |
Humaans
Humaans requires a custom integration. Read more about integrating Humaans with Lattice here.
Namely
Base pay amount in Lattice will be reflected as an annual salary if pay type = salary and as an hourly rate if pay type = hourly.
Lattice default attribute | Namely native attribute | Namely attribute name in Lattice | Required for Comp Cycles? |
Base pay amount | Compensation > Salary > Wage | Salary: Computed (pay amount according to wage type) | Yes |
Currency | Compensation > Salary > Wage | Salary: Currency type | Yes |
Pay effective date | Compensation > Salary > Wage Start Date | Salary: Date | Yes |
Pay type | Compensation > Salary > Wage Type | Wage type | Yes |
Bonus amount | set up as a custom (number) field in Namely | [custom Namely attribute] | No - optional |
Variable pay amount | set up as a custom (number) field in Namely | [custom Namely attribute] | No - optional |
Personio
Lattice default attribute | Personio native attribute | Personio attribute name in Lattice |
Base pay amount | set up as a custom (number) field in Personio | [custom Personio attribute] |
Currency | set up as a custom (text) field in Personio | [custom Personio attribute] |
Pay effective date | set up as a custom (date) field in Personio | [custom Personio attribute] |
Pay type | set up as a custom (text) field in Personio | [custom Personio attribute] |
Bonus amount | set up as a custom (number) field in Personio | [custom Personio attribute] |
Variable pay amount | set up as a custom (number) field in Personio | [custom Personio attribute] |
Rippling
Compensation attributes can only be synced as custom attributes from Rippling.
Note: Custom attributes with the type text do not appear as an attribute you can sync within Lattice. Attributes should be changed to select.
Lattice default attribute | Rippling native attribute | Rippling attribute name in Lattice |
Base pay amount | set up as a custom (number) field in Rippling | [custom Rippling attribute] |
Currency | set up as a custom (choice) field in Rippling | [custom Rippling attribute] |
Pay effective date | set up as a custom (date) field in Rippling | [custom Rippling attribute] |
Pay type | set up as a custom (choice) field in Rippling | [custom Rippling attribute] |
Bonus amount | set up as a custom (number) field in Rippling | [custom Rippling attribute] |
Variable pay amount | set up as a custom (number) field in Rippling | [custom Rippling attribute] |
TriNet
TriNet requires a custom integration. Read more about integrating TriNet with Lattice here.
UKG
Lattice default attribute | UKG native attribute | UKG attribute name in Lattice |
Base pay amount | set up as a custom (number) field in UKG | [custom UKG attribute] |
Currency | set up as a custom (text) field in UKG | [custom UKG attribute] |
Pay effective date | set up as a custom (date) field in UKG | [custom UKG attribute] |
Pay type | set up as a custom (text) field in UKG | [custom UKG attribute] |
Bonus amount | set up as a custom (number) field in UKG | [custom UKG attribute] |
Variable pay amount | set up as a custom (number) field in UKG | [custom UKG attribute] |
Workday
Workday requires a custom integration. Read more about integrating Workday with Lattice here.
Zenefits
Base pay amount in Lattice will be reflected as an annual salary if pay type = salary and as an hourly rate if pay type = hourly.
Zenefits only supports USD today. Linking Lattice’s Currency field to “Zenefits default currency (USD)” will allow you to auto-assign all employees to USD.
Lattice default attribute | Zenefits native attribute | Zenefits attribute name in Lattice | Required for Comp Cycles? |
Base pay amount |
Employment & Compensation > Annual Salary or Employment & Compensation > Compensation Type > Hourly rate |
Computed Pay Amount (pay amount according to Compensation Type) | Yes |
Currency | N/A - Zenefits only supports USD | Zenefits default currency (USD) | Yes |
Pay effective date | set up as a custom (date) field in Zenefits | [custom Zenefits attribute] | Yes |
Pay type | Employment & Compensation > Compensation Type | Compensation type | Yes |
Bonus amount | set up as a custom (number) field in Zenefits | [custom Zenefits attribute] | No - optional |
Variable pay amount | set up as a custom (number) field in Zenefits | [custom Zenefits attribute] | No - optional |