Offer-to-onboarding record chain: the identifiers that carry one hire from offer version to signed letter to HR record

Short answer

A company connects offer-to-onboarding records by following one hire through the identifier each system hands to the next: the application ID and offer version in the applicant tracking system (here Greenhouse), the signing package ID in the e-signature tool (Docusign), and the employee ID in the HR system (Workday). The chain holds where one system writes the previous system's key, usually the application ID, onto its own record. It breaks where a person retypes the accepted terms instead, which is also where the accepted offer and the HR record start to disagree.

Visual briefFull-size diagram
A vertical chain of four records, Greenhouse application, offer version 2, Docusign envelope and Workday hire, drops into place link by link; the link between envelope and hire is highlighted as missing a key and then repaired with the application ID written by the integration.
Illustrative hire at a fictional logistics company. Three hand-offs carry a key; the fourth relied on retyping until the integration was switched on.

This page is part of the offer-to-onboarding guide, which covers the metadata a partner can collect. Here the job is to name each hand-off, its key, and where it snaps.

One hire, four hand-offs (Illustrative)

A fictional 520-person regional logistics company hires a warehouse operations supervisor. The offer is approved with an April 7 start. The candidate needs two more weeks to leave a current job, so the recruiter moves the start date to April 21. Every name, date and value below is invented.

StepRecordKey carried forwardSystem
1. Candidate reaches offer stageApplication on the supervisor openingApplication IDGreenhouse
2. Offer drafted and approvedOffer version 1, start April 7Offer ID and version numberGreenhouse
3. Start date movedOffer version 2, start April 21; version 1 voided with its approvalsSame application ID, version number goes upGreenhouse
4. Version 2 re-approvedApproval on version 2Offer versionGreenhouse
5. Offer letter sent and signedSigning package with sent, opened and signed eventsPackage ID; application ID in a custom field, if configuredDocusign
6. Hire record createdNew starter record with start date and positionEmployee ID; recruiting reference only if the integration writes oneWorkday
7. Start date correctedChange from April 7 to April 21Old value, new value, who, whenWorkday

Illustrative. The keys describe how each join would be made, not a tested export.

The identifiers and what each one proves

Application ID. Created when the candidate applies and constant through every offer version. It is the one key that can, in principle, travel the whole chain.

Offer ID and version number. The applicant tracking system treats certain field edits as a new version: per its help center, the earlier offer and its approvals become void, and prior versions stay on file while a later one exists. Its developer reference lists a start-date change among the edits that add a fresh offer row with a higher version number. So the trail in steps 2 to 4 usually survives, and it proves which terms were approved last.

Envelope ID. The e-signature platform's API returns a signing package's audit events by its ID, which proves when the letter went out, was opened and was signed. It proves nothing about which HR record the letter belongs to unless someone wrote the application ID onto it.

Employee ID. Created in the HR system at hire. Its auditing logs the prior value, the replacement value, the person behind a user-made change and a timestamp, in a history reviewers can read but not edit. That makes step 7 provable: the correction is a dated change, not a silent overwrite.

Where the hire chain snaps

Hand-offHow it breaksWhat the record shows afterward
Version to versionRarely; Greenhouse keeps the trailClean, unless offers were made outside the system
Offer to signed letterLetter generated from a template with no application IDA signed letter that matches a candidate only by name
Signed letter to HR recordRecord keyed by hand from the wrong offer versionThe HR record disagrees with what the candidate signed
Hire to correctionChange made by deleting and re-creating the workerThe correction is invisible

In the Illustrative company, the hand-off from signed letter to HR record is the weak link. A coordinator keyed the new starter from an approval email for version 1, so the record began with April 7. The signed letter said April 21. Nothing tied the two, because neither carried the other's key.

  1. From a known date: an exact key. Once the company switched on its recruiting integration, new starters arrived in the HR system with the application ID in a reference field. From that year, offer and HR record join exactly, and the signed letter joins too if the same ID was written to a custom field on it.
  2. Before that date: an inferred join. Earlier hires can often be matched inside the company on candidate name, opening and start month. That is an inference built on personal data, done by the company, and it should be described as inferred.

The answer a partner needs is usually one sentence from the HRIS analyst, such as "exact from 2022, when the integration went live." That year becomes the start of the joined history.

When the hire record disagrees with the signed offer

The unresolved case is the one the weak link produces: an accepted offer that differs from the HR record. In the Illustrative hire, payroll and benefits enrollment were set up for April 7, and the error surfaced when the first payroll run treated the supervisor as already working. Workday's change history records the correction from April 7 to April 21, with who made it and when.

That correction is valuable precisely because it is recorded. A history of mismatches and fixes shows how a company's HR data drifts from what candidates were promised, and how quickly it notices. The missing-context comparison reads a case like this from one system and then from three, and the completeness checklist scores whether the keys were kept.

Owners, sponsor and unknowns

The talent acquisition operations lead owns the Greenhouse keys, whoever manages Docusign templates owns the envelope field, and the HRIS analyst owns the Workday side and the integration. Offer and hire records are personnel data, so the sponsor is senior: the CHRO or head of people with the CFO or general counsel. The CEO is the person who can authorize a licensing discussion and sign.

The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

Unknown until SourceX reviews it: whether candidate notices and employee agreements allow licensing, how records would be de-identified, and how many hires join exactly. Partners never ask for or handle raw records and sign the Channel Partner Agreement first. For each system, see Greenhouse hiring records, Docusign envelope archives and Workday history after a migration; for onboarding material itself, see onboarding and training records and assessing original onboarding materials.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client can say which year its application ID started reaching Workday, register as a partner, check the company against who qualifies and read the terms before introducing its sponsor.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Which identifier matters most in this chain?

The Greenhouse application ID. It is created first, stays constant across offer versions, and can be written onto the envelope and the hire record. If it reaches Workday, most of the chain can be joined exactly.

Can a partner check whether the integration writes the application ID?

Only by asking. The HRIS analyst usually knows whether a recruiting reference field is filled on new hires and from which year. Partners never open hire records to check.

Does an inferred join on name and start month count?

It counts as inferred, not exact, and it relies on personal data the company must handle itself. Describe it as inferred and leave any matching to the company and SourceX's review.

Sources

  1. support.greenhouse.io/hc/en-us/articles/201093394-Create-a-new-off…
  2. harvestdocs.greenhouse.io/reference/get_v3-offers
  3. developers.docusign.com/docs/esign-rest-api/reference/envelopes/enve…
  4. doc.workday.com/admin-guide/en-us/manage-workday/tenant-conf…
  5. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment