This scorecard is part of the shift-to-paid-invoice records guide. The IDs it tests are laid out step by step on the record chain page.
Scoring: 2, 1 or 0 for each check
Each check scores 2 for pass, 1 for partial and 0 for fail; seven checks make 14. Pass means the condition holds across the whole period the person describes. Partial means it holds for some years, some branches or some clients, and they can say which. Fail means it does not hold or nobody knows. Mark a zero that comes from not knowing as "unknown"; a reviewer reads that differently from a known no.
Every check is a question you can ask without a file. Your notes hold years, rough counts, system names and owners, never associate names, rates or hours.
Seven checks on the pay and billing trail
| Check | Ask at metadata level | Pass | Partial | Fail |
|---|---|---|---|---|
| 1. Placement ID on every record | "Is the placement ID on the time entry, the pay line and the invoice line?" | On all three | On time entry and invoice only | Only on the time entry |
| 2. Correction order | "When hours change after client approval, which system is corrected first, and does the other follow?" | A defined step pushes the change to both | Defined for portal-billed clients only | No defined step |
| 3. Paid-but-unbilled report | "Is there a report of hours paid in one period and billed in another, or never billed?" | Regular report with history | Built ad hoc when someone asks | No report |
| 4. Earlier hours kept | "When approved hours are edited, does the earlier figure survive, or is it overwritten?" | Every version kept | Kept from a recent year | Overwritten |
| 5. Rate changes approved | "Are pay and bill rate changes made through an approval step, or edited in place?" | Approval step for all changes | For some placements or branches | Edited in place |
| 6. Reason recorded | "Does anyone record why hours changed: missed clock-out, client dispute, overtime approval?" | Reason code on each correction | Free-text notes, sometimes | Not recorded |
| 7. Invoice route known | "Is each client invoiced from its own vendor portal, the firm's billing tool, or both?" | Known per client, with dates | Known for current clients only | Unclear |
Check 1 decides whether the three systems join without guesswork. When the number lives in one tool only, a reviewer has to pair rows by worker and week, which is fine for steady assignments and unreliable for anyone who moved between clients mid-week.
Check 4 decides whether an edit is visible after the fact. In Bullhorn's published object model, each time entry belongs to a placement and moves through statuses (Draft, Submitted, Approved, Completed, Rejected). That tells you a status exists; it does not tell you whether a branch keeps the earlier approved hours when someone edits them. Only the branch operations lead knows the local habit.
Check 5 has a concrete reference point too. Bullhorn routes edits to an assignment through a separate change request that someone approves, rather than allowing direct edits. Firms that use the step get a dated approval for each rate move, so a margin shift can be told apart from a keying mistake.
Checks 2 and 3 under pressure: a disputed shift after the cutoff
These two checks carry the most weight, because they test what happens when the payroll cutoff and the billing cutoff disagree. The hub walks through one direction of that problem, a late fix that payroll pays and billing never sees. The scorecard is easier to apply if you can also picture the opposite direction.
Illustrative. A fictional warehouse client of a staffing firm approves a forklift operator's Saturday shift at 10 hours. The weekly invoice goes out and locks. On the following Wednesday the client's site supervisor disputes the shift: the operator left at hour 8. In a client portal such as Beeline, the vendor's help notes that an invoiced, locked entry changes only through a reprocess, so the billing lead runs one and the client receives a credit for 2 hours at a $31 bill rate, $62. Payroll closed on Monday and already paid all 10 hours at the $22 pay rate.
| Day | Event | Where it lands | What the other side knows |
|---|---|---|---|
| Saturday | Shift worked, 10 hours entered | Firm's time tool | Nothing yet |
| Monday | Client approval, payroll cutoff | Portal approval; pay run for 10 hours | Both agree at 10 |
| Tuesday | Weekly invoice issued and frozen | Client portal invoice | Both agree at 10 |
| Wednesday | Supervisor dispute, entry rerun | Credit memo for 2 hours | Payroll still shows 10 |
| Next pay run | No recovery step defined | Nothing | 2 hours paid, $62 credited away |
Check 2 asks whether a defined step would have sent the dispute back to payroll, as a recovery or a reviewed exception. Check 3 asks whether any report would show this week later, when someone wants to know why paid hours and billed hours drifted apart for that client.
Score check 3 with one question to the controller: "When billed hours fall after payroll has run, or paid hours rise after the invoice is frozen, how do you find out?" Pass if the answer names a standing report with history going back years. Partial if an analyst builds it on request. Fail if the answer is "the client tells us" or "we reconcile at year end if margins look off." The direction does not matter for scoring; what matters is whether either drift leaves a trace.
Illustrative: a 300-person light industrial staffing firm scores 6 of 14
Illustrative. A fictional 300-person light industrial staffing firm (internal staff only; temporary associates counted separately) answered the checks in one call with its integration owner and a follow-up with its controller.
| Check | Mark | Points | What they said |
|---|---|---|---|
| 1. Placement ID on every record | Fail | 0 | On time entries only; pay lines carry the employee number |
| 2. Correction order | Partial | 1 | Portal clients rerun when the branch remembers |
| 3. Paid-but-unbilled report | Fail | 0 | None |
| 4. Earlier hours kept | Pass | 2 | Every version kept since 2019 |
| 5. Rate changes approved | Partial | 1 | Approval step since 2022; edited in place before |
| 6. Reason recorded | Partial | 1 | Free-text notes on some corrections |
| 7. Invoice route known | Partial | 1 | Known for current clients; older clients unclear |
| Total | 6 of 14 | 6 | Corrections visible; whether they reached the invoice is not |
For the sponsor, in one sentence: the firm keeps every earlier set of hours, so edits can be seen, but pay lines do not carry the placement ID and nobody tracks paid-but-unbilled hours, so the gap can be found only by matching on name and week. That is a fair, specific description, and it tells SourceX where the work would be.
Shift-level notes are a different record type, covered under shift handover logs. Finance leads weighing what a new revenue line means for their audit can read audit considerations for a new revenue stream, and investors screening several staffing companies can add these seven questions to a portfolio review handoff checklist. The same exception-first pattern appears in accounts payable exception handling.
Who answers which check, and what stays open
The integration owner answers checks 1 and 7. Branch operations answers 4 and 6. The billing lead answers 2, the controller answers 3, and whoever approves rate changes answers 5. A licensing discussion needs the CEO (in an owner-run firm, usually the owner) to authorize it, because the records hold associate pay and client contract terms.
Confirm the baseline before introducing: 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.
The score does not tell you whether associate and client details can be de-identified, how client MSAs and portal terms limit use, whether any buyer wants these records, or what the firm would be paid. Those stay unknown until SourceX reviews the firm. ADP's developer portal lists a Pay Statements API for Workforce Now, but naming ADP, Bullhorn or Beeline here does not imply a SourceX connector. To see what each export says alone, read the before-and-after page. 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 you advise has scored all seven checks, fails included, and its owner or CFO will take the call, register as a partner, check who qualifies, and read the terms before you submit.