# Bullhorn export missing context: before and after | SourceX

Canonical: https://refer.sourcex.si/guides/shift-to-paid-invoice-missing-context
Last updated: 2026-11-04

A single-system export loses the disagreement. In a staffing firm, the firm's own system of record, the client's vendor management system and payroll each keep a slightly different true account of the same week, and none of them alone reveals that the accounts differ. One shows corrected hours with no idea what the client was charged; one shows charged hours with no sign of a correction; one shows a paycheck with no reason behind it. Only the connected chain shows the correction, who signed off each version, and who quietly absorbed the difference.

This page reads one Illustrative week three ways and then joined. It is part of the [shift-to-paid-invoice records guide](/guides/chain-shift-to-paid-invoice), which covers the full metadata packet.

## Before: one forklift operator's week, told three ways

The case is Illustrative and differs from the main guide's example on purpose. A fictional 380-person light industrial staffing firm places a forklift operator at a client's regional distribution center. The client manages contingent labor through Beeline. Pay rate $24 an hour, bill rate $34 an hour. Every value here is invented.

The operator works four weekday shifts and, at the site lead's request, an extra 6-hour Saturday shift to clear a backlog of inbound trailers. The Saturday hours are written on the site's paper sign-in sheet and nowhere else, until the firm's on-site coordinator keys them into the firm's system the following week. Here is how that week looks to each system on its own.

**The firm's front-office system.** One assignment, one week, 38 hours on the current version, with a note: "Sat shift added per site lead." Nothing in it says what the client was charged, or that a 32-hour version came first, unless the firm keeps prior versions.

**The client's labor portal.** 32 hours, approved by the site lead on day 3 and rolled onto that week's consolidated bill at $1,088. Status: locked. To anyone reading this alone, the week was routine.

**Payroll.** A pay statement: 38 hours, $912 gross. No client, no version, no reason. The operator was paid correctly, and the statement looks complete.

Each account is internally consistent. A reviewer reading any single one would sign the week off as clean, and would be wrong about what happened.

## After: the week joined on the placement

| Question | Front-office export | Client portal export | Payroll export | Connected chain |
|---|---|---|---|---|
| Hours worked that week | 38, after correction | 32 | 38 | 38, Saturday added on day 9 |
| Was the timesheet approved? | Yes, version 2 | Yes, version 1 | Not recorded | Both versions approved, by different people |
| What was the associate paid? | Not held | Not held | $912 | $912 |
| What was the client billed? | Not held | $1,088 | Not held | $1,088 for 32 hours |
| Why do the hours differ? | Saturday shift note | Nothing | Nothing | Extra shift requested by the site lead, keyed after invoicing |
| Who absorbed the gap? | Unknown | Unknown | Unknown | The firm: 6 hours paid, never billed, $204 at the $34 bill rate |

Joined, the week has a clear sequence: the client approved 32 hours and was invoiced; the coordinator keyed the Saturday shift; the branch approved 38 hours; payroll paid 38; nobody reopened the client's approved week. Beeline's own help page explains why the bill stayed at 32: once an entry has been invoiced and locked, the only route to adjust it is a reprocess. The hub's example reaches the same split through a missed clock-out; the cause differs, the shape of the gap does not.

A buyer training a system on staffing back-office work learns nothing about corrections from the client portal alone, and nothing from the pay statement alone. The disagreement, which is the actual work, exists only when the records are joined.

## What each export loses, and where that context lives

| Context | Lost from | Where it usually lives |
|---|---|---|
| That a correction happened | Client portal and payroll | Front-office version history, if the earlier version is kept |
| Who approved each version | Payroll | The client portal for the site lead's sign-off; the front office for the branch's |
| What the client was actually charged | Front office and payroll | The consolidated bill line in the client portal |
| What the operator was actually paid | Front office and client portal | The pay statement |
| Why the hours changed | Client portal and payroll | The coordinator's note or the paper sign-in sheet |
| Whether the client bill was ever adjusted | All three on their own | The portal's reprocess history, if logged |
| Who absorbed the difference | All three on their own | Only the joined chain, or a controller's paid-but-unbilled report |

The last two rows are the ones no single system answers. A firm whose controller keeps a paid-but-unbilled report has, in effect, already built part of the join, and that report is worth naming in a description even though nobody should ask to see it.

## Why the front-office export is the most tempting and still incomplete

The front-office system (Bullhorn, in this example) is the export a firm reaches for first, because it is the system of record. Bullhorn's entity reference describes a time entry with a required link to its placement, hours, pay and bill figures, and an approval status, so that one file can look like it holds everything.

It holds what the firm intended. It does not hold what happened outside it: the hours the client actually approved in its own VMS, the invoice that went out, or the pay run that settled the week. ADP's developer portal lists a Pay Statements API for Workforce Now, so pay data can be pulled in principle, but that says nothing about whether pay lines carry the placement or timesheet ID that would let them join. The keys that make the join possible are laid out on [the record chain page](/guides/shift-to-paid-invoice-record-linkage), and [front-office data exports](/systems/bullhorn-data-export) covers what tends to survive a system change.

Multiply one week by a few hundred associates and a year of weeks, and the firm has a real reconciliation question for its controller. The same pattern of a record that only makes sense next to its exception appears in [accounts payable exception handling](/data-types/accounts-payable-exception-handling-process) and in the firm's own [invoice history exports](/systems/bill-com-export-invoice-history). The general point is covered in [what data is missing from AI training](/questions/what-data-is-missing-from-ai-training).

## Describing the missing context, and who can authorize it

You can describe all of this without seeing a timesheet. Ask four people one question each:

- **Branch operations:** do corrections create a new timesheet version, or overwrite the old one?
- **Billing lead:** which clients are billed through their own labor portal, and is a reopened week logged?
- **Payroll manager:** does the pay line carry a placement or timesheet ID, or only the employee number?
- **Controller:** is there a report of hours paid but not billed, and since when?

Partners never ask for or handle raw client records. Record counts, years and owners; no names, rates or hours for real people. The sponsor for a licensing discussion is the owner, CEO or CFO, because the records include worker pay and client contract terms.

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, how VMS terms limit reuse, buyer interest, and what the firm would be paid. To score the chain, use the [completeness checklist](/resources/shift-to-paid-invoice-completeness-checklist). Naming vendor tools here does not imply a SourceX connector. More record locations are under [systems](/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 where each version of a corrected week lives and whether its controller tracks paid-but-unbilled hours, [register as a partner](/register), check [who qualifies](/who-qualifies), and read the [terms](/terms) before you introduce its owner or CFO.

## Sources

- https://bullhorn.github.io/rest-api-docs/entityref.html
- https://webapps.beeline.com/beelinetms/!_HelpMenu_Beeline/CS_Reprocess_Timesheet_or_Expense.pdf
- https://developers.adp.com/guides/api-guides
- https://refer.sourcex.si/terms
