Skip to content
QuantumKnowledge Base

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

    Browse guides

    Approvals & Disclosures
    Getting started
    Welcome to Quantum Approvals & DisclosuresKey terms in Quantum Approvals & DisclosuresManage your personal settingsSign in to Quantum: MFA and SSO
    Submitting disclosures
    Complete and submit a disclosureSubmit requests with multiple recipientsFind and track your disclosuresCollaborate on a requestAI Agent: Submissions Support — guide for submitters
    Reviewing and approving
    Review and act on a requestReview requests with multiple recipientsCreate, manage, and complete tasksUnderstanding AI-generated risk information
    Campaigns
    Create a disclosure campaignFind campaigns and check progress
    Administration
    Start here: Set up and administer your Quantum workspaceConfigure task types and automatic task templatesConfigure automated approver collaboration
    Users, access & security
    Configure and troubleshoot single sign-onAdd and maintain usersBulk import users and resolve import errorsCreate and maintain organizational units and membershipsManage roles, capabilities, and access policiesReview organizational membership approvalsInvestigate audit events, live access, and routing
    Forms & approval workflows
    Find forms and understand their configurationUnderstand approval phases, steps, and routingConfigure final-decision notificationsConfigure approver groups and routing tablesBuild an approval workflowConfigure AI risk scoring and routingAI Agent: Submissions Support — administrator guide
    Reference data & spending rules
    Configure per-request and cumulative spend limitsManage people and organizations (party data)Configure reusable dropdown options (value sets)Configure fair market value (FMV) rates
    Email & languages
    Manage email templates, reminders, and deliveryManage languages and localization
    Integrations & data extracts
    Moving from Lextegrity to Quantum data extractsQuantum data extracts: Format and delivery guideConfigure HR data sync and SFTP intake
    Insights & reporting
    Insights: Overview of dashboards and form analysisExport data from Insights
    • Home
    • Approvals & Disclosures
    • Administration
    • Integrations & data extracts

    Configure HR data sync and SFTP intake

    Map HR files, validate a run, and prepare automated inbound delivery.

    Written by Matt Kuo

    Updated at November 15th, 2026

    Contact Us

    If you still have questions or prefer to get help directly from an agent, please submit a request.
    We’ll get back to you as soon as possible.

    Please fill out the contact form below and we will reply as soon as possible.

    • Approvals & Disclosures
      Getting started Submitting disclosures Reviewing and approving Campaigns Administration Insights & reporting
    + More

    Table of Contents

    Create an HR mapping Match a reissued employee ID Map relationships and login behavior Choose unattended-file handling Validate a controlled run Prepare automated SFTP intake Troubleshooting

    Who this is for: administrators and integration owners who maintain employee data.

    Use Data management → HR Sync to describe your HR file and validate synchronization runs. Use SFTP for automated inbound delivery. This process is different from the Users bulk-account importer and from outbound Quantum reporting extracts.

    Create an HR mapping

    1. Open HR Sync → Mappings → New mapping. Enter Mapping name and choose Source system.
    2. Set the file's Delimiter, Encoding, and whether it has a header row.
    3. Add a representative Sample file. The screen explains that this sample is read in the browser to show columns, only the first 20 rows are read, and only column names are saved with the mapping.
    4. Map each required destination field to the correct source column. At least Email or Employee ID is needed to match rows. Review names, employment information, geography, and identifiers used downstream.
    5. Where available, use Suggest with AI after adding a sample, then review each suggestion. A suggestion is not confirmation that the mapping is correct.
    6. Use the field's Adjust value control where a transformation is needed.
    7. Validate the mapping in Preview. Review how the configuration transforms the rows from your sample file. Compare the previewed values with the expected output, including adjusted values and identifiers. Use the gaps or warnings flagged on the page to identify missing or incorrect mappings, update the configuration, and check Preview again before saving. Preview uses a sample; it does not import people or replace validation of a complete run.
    HR mapping preview with fictional employee names, example.com emails, current employee IDs and previous employee IDs.
    Preview shows the transformed sample rows before import. Check current and previous employee IDs against your expected output. All people and addresses in this example are fictional.

    Match a reissued employee ID

    If your HR system changes employee IDs, map the optional Previous employee ID as well as the new Employee ID. This can identify the existing person instead of treating the new identifier as a different employee.

    Previous employee ID field mapped to the previous_employee_id source column.
    Map Previous employee ID to the column containing the former identifier. Keep Employee ID mapped to the current identifier.

    Example: the existing person has ID EMP-1042. The next file supplies EMP-8801 as Employee ID and EMP-1042 as Previous employee ID. If the previous ID identifies one existing person and the other identity checks are consistent, Quantum updates that person and replaces the employee ID.

    If the previous ID matches nobody or more than one person, normal matching rules apply. Conflicting identity evidence still needs resolution. Do not use this field to force a match to a different person.

    1. Map Employee ID to the current identifier and Previous employee ID to the former identifier.
    2. Validate the transformed sample in Preview.
    3. Run a controlled file and inspect the proposed match before committing.
    4. Confirm the existing person was updated, relationships remain appropriate and the identifier change appears in the audit log.

    Files without this optional mapping continue to use the existing matching process. The separate Users bulk importer has its own supported file format.

    Map relationships and login behavior

    Each person successfully imported from the CSV is represented by a party in Quantum. The Login access configuration determines whether a user account (login) is also created alongside that party. A party record alone does not give someone access to sign in.

    • Manager and HR partner can be matched by employee ID or email. Select the intended matching mode and source column.
    • Review Login active and Party active as separate mappings. They serve different purposes; do not treat the party's active status as a substitute for login eligibility.

    Under Login access → Create logins for, choose the intended population:

    Option Result for imported people
    Every row Create a user account alongside each imported party, subject to validation.
    No rows Import parties without creating user accounts for them.
    Only rows where Login active is Yes Create user accounts only for rows whose mapped Login active value is Yes. Other imported people remain parties without a newly created login.

    For conditional creation, map Login active to the source column that determines eligibility and use Adjust value as needed. For example, if the sample maps one person's eligibility to Yes and another's to No, both should be imported as parties, but only the Yes row should create a login. Check both outcomes in Preview and in a controlled run.

    Conditional login creation and warnings for unmapped Email and Login active fields
    Conditional login creation uses the Login active mapping. This unsaved example highlights missing Email and Login active mappings that must be configured before use.
    • Review Send an invitation email to new password-based logins separately from the choice of which rows create accounts.
    • Sign-in method is decided by the tenant's SSO domain rules, not by a column in the HR file.

    Choose unattended-file handling

    The mapping offers Apply confident rows and park the rest or Hold the whole run for review. Choose the behavior approved by the HR-data owner. The screen states that this applies when files arrive automatically; it does not affect a file you upload and commit yourself.

    Check the Preview, then select Save mapping. Confirm the mapping appears under HR Sync → Mappings.

    Validate a controlled run

    1. Open HR Sync → Upload file. Check the selected mapping and choose one CSV file under Validate an HR file. Nothing changes until you review the rows and commit the run. The uploaded rows are stored with the run until the run is removed.
    2. Review validation results and proposed changes before using any commit or apply control.
    3. Resolve rows needing review and verify the resulting run state in Recent runs.
    4. After the run is committed, spot-check the resulting parties, manager relationships, and downstream unit membership. Verify that user accounts were created only for the intended population. For conditional login creation, include both a row whose mapped Login active value is Yes and a row whose value is No, and confirm the expected outcome for each. Validation alone is not proof that changes were committed.

    Prepare automated SFTP intake

    HR Sync → SFTP shows Intakes, Logins, PGP keys, and Activity. Select New intake to connect a folder to a saved mapping. This test workspace has no intakes yet.
    HR Sync → SFTP shows Intakes, Logins, PGP keys, and Activity. Select New intake to connect a folder to a saved mapping. This test workspace has no intakes yet.
    1. Open HR Sync → SFTP → Intakes and read How intakes work. Expand More detail for additional guidance.
    2. Use New intake to associate an intake folder with the intended mapping. Files dropped there become HR sync runs using that mapping.
    3. Use the authorized SFTP → Logins process to register the approved SSH public key. Each login sees the tenant's intake folders and a results folder.
    4. Give your integration owner the connection details displayed in your workspace: host, port, username, host-key fingerprint, and allow-list addresses. Do not copy staging connection details into production.
    5. Where file encryption is required, coordinate SFTP → PGP keys. Partners encrypt to the public key; during rotation keep the old key active until the transition is complete.
    6. Send a controlled test file and inspect SFTP → Activity, the resulting run, and any review work before enabling the routine feed.
    New intake associates a folder with a saved mapping and offers file-pattern, encryption, and results-file controls. This unsaved dialog illustrates inbound HR intake, not outbound reporting extracts.
    New intake associates a folder with a saved mapping and offers file-pattern, encryption, and results-file controls. This unsaved dialog illustrates inbound HR intake, not outbound reporting extracts.

    Troubleshooting

    • No mapping available: save and verify a mapping before validating a file or configuring intake.
    • Unexpected account creation: check Create logins for and the mapped Login active values. These control the population for account creation; SSO domain rules control sign-in method.
    • Manager not resolved: check matching mode and identifiers on both the employee and manager rows.
    • File not processed: confirm the intake folder, connection identity, key, and activity results.

    For outbound reporting, use Quantum data extracts: Format and delivery guide.

    hr sync sftp intake field mapping employee data

    Was this article helpful?

    Yes
    No
    Give feedback about this article

    Related articles

    • Bulk import users and resolve import errors→
    • Add and maintain users→
    • Manage people and organizations (party data)→

    © 2026 Case IQ

    Expand