Shift-to-paid-invoice record chain: the IDs that join a placement, timesheet versions, pay line and client invoice

Short answer

A staffing firm joins its shift-to-paid-invoice records by anchoring every hop on the placement: assignment to time record, time record to client sign-off, sign-off to invoice line, and time record to pay line. Where a system stores the firm's own placement number, the hop is a clean one-to-many join. Where it stores only its own record number, or only the worker's employee number, matching falls back to name and week, and that fallback fails on precisely the rows that matter: corrected, split and overlapping weeks.

Visual briefFull-size diagram
A vertical chain of six records, placement, timesheet version 1, client approval, invoice line, timesheet version 2 and pay line, clicks together on the placement ID; the link from version 2 back to the invoice shows as broken in orange and is then repaired in green.
Illustrative. Every record should point back to the placement; the corrected timesheet is the one that loses its way to the invoice.

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.

HopFrom, toCardinalityCarries the anchor?When it fails
1Placement to time recordOne placement, many weekly time records, each with versionsAlways, inside the firm's own systemRarely; only if versions are overwritten
2Time record to client sign-offOne firm time record, one VMS record per submissionOnly if the integration maps itResubmissions create new VMS numbers
3Client sign-off to invoice lineMany approved records, one consolidated invoiceThrough the VMS number, not the placementLater corrections are not reprocessed
4Time record to pay lineOne approved version, one pay line per periodOnly if payroll stores itTwo 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

StepRecordKey it carriesKey that points backSystem
AssignmentPlacementPlacement IDCandidate and client job IDsBullhorn
Hours enteredTimesheet version 1Timesheet ID, version, statusPlacement IDBullhorn
Client sign-offVMS timesheetVMS record numberPlacement ID only if mappedBeeline
BillingInvoice lineInvoice number and lineVMS record numberBeeline
CorrectionTimesheet version 2Timesheet ID, version, statusPlacement IDBullhorn
PayPay statement linePay period, employee numberPlacement or timesheet ID only if storedADP

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.

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:

  1. Both timesheet versions survive. Ask whether corrections create a new version or overwrite the old one, and since when.
  2. 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.
  3. 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.

  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

What if the firm's payroll lines carry only an employee number?

Then pay lines join to placements through the associate and the pay period, which works when an associate has one placement a week and fails when they have two. Note how often associates hold overlapping placements; that share is the size of the weak link.

Does every client bill through a VMS?

No. Many staffing firms invoice some clients from their own billing tool and others through the client's VMS. Each route has its own keys, so describe them separately.

Can a partner confirm that the placement ID is on the invoice line?

Only by asking the billing lead. You do not need to see an invoice. 'Yes for VMS clients, no for direct-billed clients' is a complete answer.

Sources

  1. bullhorn.github.io/rest-api-docs/entityref.html
  2. webapps.beeline.com/beelinetms/!_HelpMenu_Beeline/CS_Reprocess_T…
  3. developers.adp.com/guides/api-guides
  4. 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