Note on Availability: SAP SuccessFactors Write-Back is an add-on product and is set up with the help of our team. Reach out to your account team if you'd like to learn more.
Your new hires already give you their details during onboarding: contact information, addresses, emergency contacts, bank details and more. With SAP SuccessFactors Write-Back, your Enboarder forms send that data straight into SAP SuccessFactors Employee Central, so nobody has to re-key it. 🙌
Write-back works in two ways: your forms can create a brand-new employee in Employee Central, or update an employee who already exists.
Before you begin: You'll need a SuccessFactors administrator with the Manage Integration Tools and Manage Permission Roles permissions. The SuccessFactors setup takes around 20–30 minutes. We recommend setting up and testing in your SuccessFactors sandbox first. Nothing goes live until you approve it.
Write-back builds on our standard SAP SuccessFactors Integration, which sends new hires from SuccessFactors into Enboarder.
Create or update: which do I need?
You choose Create or Update on each form.
Update is for people who already exist in SuccessFactors, for example new hires launched into Enboarder from SuccessFactors. Enboarder finds them by their office email address and updates the fields you've mapped.
Create is for people who don't exist in SuccessFactors yet, for example new hires who come from your ATS, SuccessFactors Recruiting or a CSV upload. Submitting the form creates their profile and employee record in Employee Central.
How Update works
You add a Form Module to your workflow, choose Update, and map its fields to SuccessFactors fields.
The employee fills in and submits the form.
Enboarder finds the employee in SuccessFactors using their office email address and updates their Employee Central record with the mapped values.
The result is recorded in the form's activity log.
Important:
The employee profile in Enboarder must have an office email address. If your workflow only captures a personal email at first, use an Update Value module to update the profile to the office email before the write-back form is sent.
Write-back happens when the form is submitted. Editing a form after it's been submitted doesn't send the changes again.
How Create works
Our team turns on Create for your account during setup.
You add a Form Module to your workflow and choose Create. That form becomes the point where the employee is created in SuccessFactors.
The form can add extra data (such as a user ID) or override data already in the workflow (such as a job code or department from your CSV). Data from the form always takes priority over workflow CSV data.
When the form is submitted, Enboarder checks whether the employee already exists, using their email or a unique ID from your CSV or ATS. If there's no match, it creates the employee.
The manager relationship is set automatically from the manager's email address, so the new employee is created under the right person. The manager must be an active employee in SuccessFactors.
The new SuccessFactors employee ID comes back to Enboarder as a token, so you can include it in emails to payroll or other teams.
The result is recorded in the form's activity log.
What Create sets up in Employee Central: the user account, person record and personal information, the employment record, job details (through a position assignment, if you use Position Management), email, phone and address, and bank details (where Employee Central holds your banking data).
What Create doesn't do:
It doesn't capture tax or superannuation/pension data. That lives in your payroll system and is collected through your payroll onboarding process.
It doesn't give the new employee login access or send welcome emails. Your identity management system handles this, so a newly created employee can't sign in to SuccessFactors straight away. Set that expectation in any comms you send.
Good to know:
Create is all-or-nothing. If any part of the record fails, nothing is saved.
For bulk intakes, employees are created one at a time, so one problem doesn't stop the whole batch.
Create works on mobile as well as desktop.
What data can be written back?
Data | Examples |
Personal information | First, middle, last and preferred name, salutation, gender, marital status |
Business and personal email, email type, primary flag | |
Phone | Number, country code, phone type, extension |
Address | Address lines, city, state/province, postal code, country |
National ID | ID number, ID type, issuing country |
Work permit | Permit type, issuing country, issue and expiry date |
Emergency contacts | Name, relationship, address, country, mobile number, primary flag |
Bank details | Bank and account details (routing number/BSB and BIC are taken from the SuccessFactors bank record) |
Attachments | Files uploaded in the form, attached to the employee's person record |
Dropdowns in your forms can use picklists from SuccessFactors, including dependent picklists (for example Country → State → City), so the values your new hires choose always match your SuccessFactors setup.
Our team activates the fields available to your account during setup. Only activated fields appear when you map a form. Want to add a field? Contact your account team.
Not included: compensation and payroll history, performance reviews and goals, time-off and leave balances, or anything outside the fields your SuccessFactors admin grants access to.
Step 1: Set up SuccessFactors
Your SuccessFactors admin will need to complete these steps and share five values with you: API Server URL, Company ID, API User ID, API Key (Client ID) and Client Secret (Private Key).
1.1 Find your API Server URL
Look up your data center on SAP's List of SAP SuccessFactors API Servers page, filtered to your environment (usually Production).
TIP: If you log in at https://hcm12.successfactors.com, your API server is likely https://api12.successfactors.com.
1.2 Find your Company ID
Click your profile image (top right), select Show Version Information, and copy the Company ID.
1.3 Create an API user
Go to Admin Center → Manage Users and create a dedicated user, e.g. ENBOARDER_API. Set the status to Active. The password isn't used for authentication, but should still be strong.
1.4 Register an OAuth2 client
Go to Admin Center → Manage OAuth2 Client Applications → Register Client Application.
Enter Application Name: Enboarder, and Application URL: https://app.enboarder.com.
Click Generate X.509 Certificate, enter any Common Name, and click Generate.
Download Certificate.pem. Open it in a text editor and copy the text between BEGIN ENCRYPTED PRIVATE KEY and END ENCRYPTED PRIVATE KEY. This is your Client Secret.
Click Register. Then go back to Manage OAuth2 Client Applications, click Edit on the Enboarder application and copy the API Key. This is your Client ID.
Please store the Client Secret securely, as it gives access to your SuccessFactors data.
1.5 Set up role-based permissions
Go to Admin Center → Manage Permission Roles → Create New, and name the role Enboarder Integration.
Set the Target Population to All Active Employees, or narrow it to a specific group (e.g. new hires only, or one country).
Grant Read + Write access to: Personal Information, Email Information, Phone Information, Address Information, National ID Information, Emergency Contacts, Employment Information and Job Information.
If they're in scope for you, also grant: Payment Information and Attachments (Read, Write, Create, Delete), Work Permit and User Management.
Grant read-only access to Foundation Objects, Picklists and Position.
Turn on field-level permissions for each field you plan to write back.
Click Grant This Role, select your API user and confirm.
TIP: Field-level permissions are the most commonly missed step. If a field isn't permitted, SuccessFactors can accept the update but quietly skip that field. Commonly missed fields include date of birth, gender, nationality, national ID, phone number, email address and bank account details.
Step 2: Connect Enboarder
Log in as an admin and navigate to Settings → Apps & Integration → App center.
Click the SAP SuccessFactors tile. If you see two tiles with the same name, choose the native one (the tile without the HRIS crown label).
Click Add Integration. In the Outbound section, enter the five values from Step 1: API Server URL, Company ID, API User ID, API Key (Client ID) and Client Secret (Private Key).
Save. Enboarder will test the connection and run a permission check to see which SuccessFactors data it can access, and let you know about any gaps.
Fix any gaps with your SuccessFactors admin. Once all checks pass, the tile shows as active. ✅
Step 3: Add in your form fields
Navigate to the Form you wish to use to write-back data to SuccessFactors
Click the + icon
Select the System as SuccessFactors and choose whether you wish to push to the Sandbox or Production account
Select the Create or Update function. Choose Create if the employee doesn't exist in SuccessFactors yet, or Update if they do.
Select all of the fields that you wish to have data write-back from
Rename the labels and re-order the fields as needed
TIP: Test a Create form against your sandbox or a non-production hire before using it in a live workflow, as it creates a real employee record.
Step 4: Map your form fields
Click the Form Settings dropdown at the bottom of the form and turn on Write back to HRIS.
For each form field, choose the matching SuccessFactors field. Fields are shown as Entity - Property.
Save your mapping.
Click Test mapping, enter a test employee's email and click Fetch employee. You'll see the mapped fields with their current SuccessFactors values. Make a change, submit, and check the success or failure message.
Note - Test mapping sends a real update to the SuccessFactors record you choose. Use your sandbox or a dedicated test employee.
What happens if a sync fails or SuccessFactors is unavailable?
Temporary problems retry automatically. If SuccessFactors is down, times out, is limiting requests, or returns a server error, Enboarder retries on its own, in the same way as webhook retries. You don't need to do anything.
Data problems need a fix. Enboarder won't retry these on its own:
The employee can't be found in SuccessFactors from the email given.
SuccessFactors rejects a value, or a required field is missing.
Correct the data, then trigger a manual retry from the workflow's audit page.
How you'll know something failed:
Failed integrations appear in the integration notification centre.
An email is sent to your integration error stakeholder.
The form's activity log shows the result: Updated, Partly updated or Failed for an update, and Created (with the new employee ID and start date) or Not created for a create. A warning names any section that failed and links to the integration logs for that submission.
The workflow audit page shows whether the form was a create or an update, and compares the mapped fields with the data actually sent.
If any field in a section fails, that whole section isn't updated. A create is all-or-nothing, so if it fails, no record is saved.
Troubleshooting
Check the activity log: open the submitted form's activity log to see the result, and click Show what was sent to see the fields and values sent to SuccessFactors, grouped by section.
Success example:
Failure example:
Check the integration logs: go to Settings → Integrations → Integration logs to view the full API response.
Data looks synced but isn't there? This is usually a missing field-level permission in SuccessFactors. Check the role from Step 1.5, then retest with a test employee.
Change waiting in SuccessFactors? Updates to things like job information, bank details, date of birth or legal name may go into a pending approval state, depending on your SuccessFactors workflow setup. Talk to your SuccessFactors admin about whether the API user should be exempt from those workflows.
Employee not found? Check the employee profile in Enboarder has the same office email address as in SuccessFactors.
Employee not created? Check whether the employee already exists in SuccessFactors. Enboarder won't create a duplicate.
Manager not found? Check the manager's email address matches an active employee in SuccessFactors.
Position not found? Check the position exists and is active in SuccessFactors for the employee's start date.
FAQs
Can write-back create new employees in SuccessFactors?
Yes. Choose Create on your form to create the employee's profile and employee record in Employee Central. See How Create works above.
Can a newly created employee log in to SuccessFactors right away?
No. Login access is set up by your identity management system, which can take anywhere from a few minutes to overnight depending on how it's configured. Check the timing with your IT team.
What happens if SuccessFactors is down when a form is submitted?
Enboarder retries automatically. If the problem is with the data rather than the connection, the failure appears in the integration notification centre, your integration error stakeholder is emailed, and you can retry from the workflow audit page once it's fixed.
Does Enboarder need access to compensation data?
No. Enboarder does not require access to compensation, performance or time-off data.
Can we limit which employees Enboarder can update?
Yes. Narrow the Target Population on the Enboarder Integration permission role in SuccessFactors.
Is the connection secure?
Yes. Enboarder connects using OAuth2 with a certificate (SAML bearer assertion), with no user login involved. All communication uses HTTPS/TLS 1.2+, and the private key is stored encrypted at rest.
Do I need the inbound integration too?
The inbound integration launches new hires from SuccessFactors into Enboarder, and write-back sends their data back. Both are set up on the same native SAP SuccessFactors tile. If you use Create, your new hires can come from another source, such as your ATS or a CSV upload.
Got questions? Click on the '?' button at the top right of any Enboarder page to start a chat with us. Alternatively, email us! support@enboarder.com ✌









