This page is the key map for that chain. It is part of the shift-to-paid-invoice records guide, which covers the metadata packet and the case of a revision that reached payroll only.
Four hops anchored on one placement number
Think of the chain as one anchor and four hops. The anchor is the placement: one worker, one client job, one pay rate and one bill rate, under a number the firm controls. Each hop below either carries that number forward or swaps it for a local one.
| Hop | From, to | Cardinality | Carries the anchor? | When it fails |
|---|---|---|---|---|
| 1 | Placement to time record | One placement, many weekly time records, each with versions | Always, inside the firm's own system | Rarely; only if versions are overwritten |
| 2 | Time record to client sign-off | One firm time record, one VMS record per submission | Only if the integration maps it | Resubmissions create new VMS numbers |
| 3 | Client sign-off to invoice line | Many approved records, one consolidated invoice | Through the VMS number, not the placement | Later corrections are not reprocessed |
| 4 | Time record to pay line | One approved version, one pay line per period | Only if payroll stores it | Two placements in one pay period |
Hop 1 is the firm's home ground and almost always holds. Hops 2 and 4 are integration questions: someone configured, or did not configure, a field that carries the placement number into the client's vendor management system and into payroll. Hop 3 sits entirely on the client side, so it holds only as well as the client's own records do.
The useful measure is a match rate. Ask the integration owner roughly what share of pay lines and invoice lines can be tied to a placement without using names. "Nearly all, since the 2021 integration" and "we match by hand at month end" describe very different archives, and both are honest packet entries.
The Illustrative week used throughout this cluster shows why the hops matter. A fictional healthcare staffing firm's nurse has version 1 of the week's time record at 36 hours, signed off by the client and invoiced, then version 2 at 40 hours after a missed clock-out is fixed, which payroll pays. Hop 1 holds for both versions. Hop 3 holds for version 1 only. Nothing hops from version 2 to the invoice.
Step, record, key and system
| Step | Record | Key it carries | Key that points back | System |
|---|---|---|---|---|
| Assignment | Placement | Placement ID | Candidate and client job IDs | Bullhorn |
| Hours entered | Timesheet version 1 | Timesheet ID, version, status | Placement ID | Bullhorn |
| Client sign-off | VMS timesheet | VMS record number | Placement ID only if mapped | Beeline |
| Billing | Invoice line | Invoice number and line | VMS record number | Beeline |
| Correction | Timesheet version 2 | Timesheet ID, version, status | Placement ID | Bullhorn |
| Pay | Pay statement line | Pay period, employee number | Placement or timesheet ID only if stored | ADP |
Read the fourth column. The Bullhorn rows always point to the placement: its entity reference describes a Timesheet with a required placement link, hours, pay and bill figures, and a status of Draft, Submitted, Approved, Completed or Rejected. Placements themselves cannot be modified directly; changes go through a PlacementChangeRequest approved separately, which gives rate changes their own trail if the firm uses it. The Beeline and ADP rows point back only if somebody mapped the firm's IDs into them. ADP lists a Pay Statements API for Workforce Now, so pay data is retrievable in principle, but whether the pay line stores a placement or timesheet ID is unknown until asked. That is the question the whole chain turns on.
The link that breaks: version 2 never reaches the invoice
Timesheet version 2 points to the placement and feeds payroll. Nothing points from version 2 to the invoice line, because the invoice was built from version 1 and then locked. Beeline's help explains why the invoice did not follow: once a timesheet has been invoiced and its status is locked, it can only be adjusted by reprocessing it. Nobody reprocessed it.
So the chain splits after the invoice line. One branch runs placement, version 1, client approval, invoice. The other runs placement, version 2, pay line. Both branches are internally consistent. The difference between them, 4 hours paid and never billed, worth $272 at the main guide's $68 bill rate, is invisible unless something links version 2 back to the invoice line.
Three weaker links tend to sit alongside the main one:
- Pay line to placement. If ADP stores only the employee number and pay period, an associate with two placements in one week cannot be split cleanly.
- Overwritten versions. If the firm's timesheet tool replaces version 1 with version 2 rather than keeping both, the correction disappears and the split is undetectable.
- Rate changes in place. If rates are edited on the placement rather than through an approved change request, a pay or bill difference can look like an error when it was an agreed change.
Repairing the chain: what the firm needs to have kept
The chain can be rebuilt for every week in the archive if three things are true. Ask about each, and record the answer and the years it covers:
- Both timesheet versions survive. Ask whether corrections create a new version or overwrite the old one, and since when.
- The placement ID reaches at least two of the three systems. Ask the integration owner whether Beeline and ADP records carry it, or only their own numbers.
- Reprocessing is logged. Ask the billing lead whether a reprocessed VMS timesheet keeps a reference to the original.
If all three hold, every paid-but-unbilled week can be found by matching pay-line hours against invoice-line hours per placement. If the ID lives only in Bullhorn, matching falls back to associate name and week, with the weaknesses described at the top of this page. The firm's own export history matters too; Bullhorn data exports covers what usually survives a system change.
Who owns each key, and who signs off
The systems or integration owner knows which IDs are mapped where. Branch operations knows how timesheets are corrected. The billing lead knows the VMS side, and the payroll manager knows ADP. The person who can open a licensing discussion is the owner, CEO or CFO, because the records include worker pay data and client contract terms.
Partners never ask for or handle raw client records. You record which keys exist, where, since when and who owns them: no names, rates or hours for real people. Before introducing, confirm 50+ full-time employees at peak (contractors excluded), a 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. Sign the Channel Partner Agreement first.
What stays unknown until SourceX reviews it: whether worker and client details can be de-identified to a buyer's standard, how client MSAs and VMS terms limit use, buyer interest, and what the firm would be paid. Why joined records are worth more than single exports is covered in cross-system data value; data quality due diligence and AI agents in ERP work give wider context. To see what each export says alone, read the before-and-after page; to score the chain, use the completeness checklist. Naming Bullhorn, Beeline and ADP does not imply a SourceX connector. More record locations are under systems.
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 staffing firm can say which systems carry the placement ID and whether it keeps every timesheet version, register as a partner, check who qualifies, and read the terms before you introduce its owner or CFO.