HR-system connections are not generally available and are disabled by default. Complete the connection exercises only when FTE Tree and your organization have agreed to a pilot and confirmed that the connection is enabled for that pilot. A provider name in documentation does not mean every customer can enable it.

Start with the options available to your organization

Most teams should skip the connection exercises and use Import records and check what changed. A missing HR-system connection page is expected when the feature has not been enabled for your organization.

Your instructor can also use prepared examples for a guided review without entering credentials or connecting a real provider. That review teaches the decisions involved; it does not confirm that your organization has an enabled connection.

Review the prepared connection example

Your instructor provides the connection details, a successful test result, a completed update, and a failed update with a readable error. For an enabled practice connection:

  1. Open its administration page and confirm the provider and organization.
  2. Review who may manage the connection and which employee information it covers.
  3. Inspect the credential-entry instructions. Credentials are entered only by the authorized administrator through the protected form.
  4. Find the connection test result and the most recent completed update.
  5. Open the update history and compare its affected records and dates with the expected practice employees.

Saving credentials alone does not prove that the connection works. A successful test does not prove that the first complete information update has finished. Check those outcomes separately.

Decide where a correction belongs

Prepared situation What to do Expected outcome
FTE Tree manages Avery’s pay Use the permitted Compensation form or reviewed import The local pay record changes from the intended date
The connected HR system manages Avery’s pay Correct the information in that system and review the next completed update FTE Tree reflects the provider’s corrected amount and dates
The connection test fails Read the failure and have the authorized administrator correct the connection setup A new test succeeds before relying on updates
A pay update fails after the test succeeded Inspect the failed update and its affected records The failure is resolved and a complete update is confirmed; saving the connection again is not proof

A field managed by another system may be read-only in FTE Tree. Do not create a second local record to work around that restriction.

Review a change in who maintains pay

Use this prepared example: FTE Tree maintains Avery’s pay through June 30, 2027. The agreed HR system should take over beginning July 1, 2027.

At the connection’s review step, check the current and next system, affected assignments, start date, and prepared pay information from the next system. The form may call that prepared information the Target baseline. It must contain the expected people, amounts, and dates before the change is completed.

The intended result is one responsible system for each date: FTE Tree through June 30, then the connected system from July 1. An unsuccessful preparation or update should be resolved before relying on the handover. Review the saved history afterward rather than assuming the same system managed pay for the entire year.

Check your understanding

Explain why a connected field can be read-only, why a successful credential save is not a successful update, and where you would correct Avery’s pay on either side of July 1.