The business task: one shift, paid once and billed once
A staffing firm places an associate with a client. Every shift turns into hours, the hours turn into a paycheck, and the same hours turn into a line on the client's bill, often routed through the client's vendor management system. The question a controller cares about is simple to state and hard to answer: was every paid hour billed at the agreed rate, and did every correction land on both sides?
The graphic follows one week for one placement (Illustrative). Version 1 of the week, 36 hours, is signed off by the client on day 3 and billed at $2,448. A missed clock-out is then fixed, and version 2, 40 hours, is paid at $1,920. Version 2 never reaches the bill. The firm paid 4 hours it never charged for, worth $272 at the bill rate.
Each tool holds its own slice of that week. Bullhorn's API reference describes a time entry entity with a required link to its placement, hours, pay and bill figures, and an approval status. Beeline's help notes that once an entry has been invoiced and locked, the only way to adjust it is to reprocess it. ADP's developer portal lists a Pay Statements API for Workforce Now. Those three names describe where records commonly sit, not a SourceX connector.
What metadata can a referral partner collect about shift-to-paid-invoice without reading private content?
Build the packet around owners, because in a staffing firm each owner knows one system closely and the rest barely. A staffing systems integrator usually already knows who these people are.
| Owner | What to ask | What a good answer looks like (Illustrative) |
|---|---|---|
| Back-office or payroll manager | Which system pays associates, since when, how many pay runs a year? | Same payroll provider since 2017, weekly runs, about 1,900 associates paid at peak |
| Billing lead | Which clients are billed through their own procurement portal, which through the firm's invoices? | Six clients through a client-side portal, the rest invoiced from the firm's billing tool |
| Branch operations lead | Where are hours entered and corrected, and are earlier versions kept? | Front-office system since 2019; each correction creates a new version |
| Systems or integration owner | Which ID ties placement, hours, pay line and invoice line together? | Placement ID on hours and invoice; absent from pay lines |
| Controller | Is there a report of hours paid but not charged? | Monthly spreadsheet since 2022, kept by the controller |
| Owner or CFO | Any planned system change, acquisition or client portal exit? | One large client switching portals next year |
Then add one line per system in the same shape: object types (placements, hour versions, pay statements, invoice lines), years held, rough volume, the reference each record carries, and what nobody knows yet. Gaps are normal. "We do not know whether a reprocessed entry is logged against the original" is a better packet line than a guess.
The one question about corrections
Ask the controller a single thing about the version 2 case: when hours change after the client signed off, how does the firm learn whether the change reached the bill? Write down the answer in the firm's own words (a monthly report, a reprocess queue, nothing formal) and how many years it covers. Do not ask for the report.
Record counts and date ranges, never names, rates or hours for real people. For the firm's own invoice history, Bill.com invoice exports and front-office placement exports describe what usually survives a system change. Shift-level notes are a different record type, covered under shift handover logs.
Who signs off on an introduction, and does the firm qualify?
Pay and billing records carry worker compensation and client terms, so the CEO, usually the owner in an owner-run firm, is the one who can authorize a licensing discussion, often with the CFO as sponsor. A branch manager can describe the records but rarely can authorize licensing them.
Before you introduce, confirm:
- The firm has 50+ full-time employees at peak, contractors excluded, and a documented operating history. Temporary associates on assignment do not count; the headcount question for staffing firms explains why.
- The firm has rights to license the records. Client MSAs and portal terms may limit reuse of client-side data; note them, do not interpret them.
- A named decision-maker will take a first call.
- 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.
What stays unknown until SourceX reviews it: whether worker and client details can be de-identified to a buyer's standard, which years a buyer would want, how client contracts limit use, and what the firm would be paid. The staffing screening worksheet and the staffing industry page cover wider fit. For other record locations, start at the systems hub.
Go deeper on shift-to-paid-invoice records
- How to link placements, hours, pay and invoices across systems: a guide to the IDs that join front-office, client-portal and payroll records.
- Shift-to-paid-invoice completeness checklist: a checklist of the breaks that leave a staffing evidence trail incomplete.
- What a single-system export leaves out: a before-and-after read of the context lost when only one system is exported.
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 the firm can say which ID ties a week of hours to both the paycheck and the invoice, and since when, register as a partner, check the firm against who qualifies, and read the program terms; how referral payments work walks through the payment conditions in order.