Skip to content

Systems and records

Staffing back office reconciliation data: do hours, approvals and invoices agree?

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

Build each task around one billed line and one question: does it agree with the approved hours and the rate in force on each work date? Freeze the chain from rate card version and timesheet entries through approval, billable charge and invoice line, screen out worker and client identity, and score answers against the credit, rebill or written acceptance that closed the case, never a status field.

Provenance trail

Staffing back office

This page covers staffing back office reconciliation data: do hours, approvals and invoices agree.Illustrative

Key takeaways

  • One packet tests one billed line against approved hours and the rate card version in force on each work date.
  • Every hop from rate card to invoice line must link by identifier, or the case can be studied but not scored.
  • Effective-dated rates, earn codes, workweek boundaries and backup approvers are what generic invoice examples miss.
  • The gold outcome is a linked credit, rebill or written acceptance; a status field is never proof.
  • Worker, approver and client identity are tokenized, free-text comments are reviewed, and VMS-originated records stay out unless terms allow.

How do you construct a task reconciling timesheets, approvals and invoices?

Build each task around one billed line and one question: does this invoice line agree with the approved time and the rate in force for those dates, and if not, what corrected it? Freeze the evidence chain from placement and rate card version through timesheet entries, approval, billable charge and invoice line, then score the answer against what actually closed the case, such as a credit, a rebill or written client acceptance.

Staffing back office reconciliation data is valuable for AI work because it records real decisions made under specific rules: which earn code applied, which rate card version governed, who approved, and how an error was fixed. A generic accounts payable example rarely captures that chain. A staffing firm's pay and bill history often does, provided the links between records survive the export.

The packet described here is designed so an evaluator can test an AI system on a bounded reconciliation question and so a privacy reviewer can see, field by field, what was removed or tokenized. Every example on this page is illustrative. Field names are taken from Bullhorn's published REST API entity reference as one concrete example of a staffing pay and bill model; other platforms use different names for similar objects.

A case is usable only when every hop from the worked hours to the billed line can be followed by identifier, not by matching names or amounts. If one hop breaks, the case can still be studied, but it cannot be scored, because nobody can show which input produced the line.

Bullhorn's documentation describes the chain clearly. Billable charges are generated when timesheets or expense sheets are approved, grouped for invoice generation and carried onto invoice statements sent to the client. Each billable charge points back to the timesheet and placement that produced it, and each invoice statement lists the billable charges it includes.

  • Before building any packet, run a link audit on a sample: pick a few dozen invoice lines at random and try to walk each one back to its rate card version and approval. The share that walks back cleanly is a better guide to the usable volume than any record count.
  • Keep the internal record IDs as join keys during preparation, then replace them with stable tokens in the delivered packet.
  • Record which system originated each timesheet entry; Bullhorn's time and labor system type values include sources such as a VMS, clock, mobile and IVR, and the origin affects who controls the record.
Which records have to link before a case is usable?
LinkExample fields (Bullhorn names)What it provesBreak to watch for
Placement to rate cardPlacementRateCardVersion effectiveDate and effectiveEndDateWhich rate applied on each work dateRate change mid-week with no version split
Timesheet to entriesTimesheetEntry applicableFrom, applicableTo, earnCode, quantity, billRateHours by day and pay typeEntries voided and replaced by a new version
Entries to approvalTimesheet approvingClientContact, approvedDate; entry approval statusWho accepted the hours and whenBackup approver or approval recorded outside the system
Timesheet to chargeBillableCharge timesheet, placement, periodEndDate, transactionTypeWhich approved hours became a chargeCharge on hold with an unexplained comment
Charge to invoice lineInvoiceStatement billableCharges, lineItems; line quantity, rate, subtotalWhat the client was billedLines summarized so one line covers many charges
Invoice to correctionInvoiceStatement creditOfInvoiceStatement, rebillFromInvoices, isCreditedHow an error was resolvedCorrection issued as a manual journal outside billing

Which staffing constraints would a generic invoice example miss?

The constraint a generic example misses most often is time: rates, earn codes and approvals are effective-dated, so a line can be correct for one day of a week and wrong for the next. A reconciliation task that ignores the rate card version in force on each work date will mark correct invoices as errors and miss real ones.

Overtime is the second. Under the federal recordkeeping rule at 29 CFR 516.2, employers keep hours worked each workday and total hours each workweek, where a workweek is a fixed and regularly recurring period of seven consecutive workdays. A staffing firm's workweek may not match the client's billing week, and the split decides which hours carry an overtime earn code.

Third, the invoice structure itself imposes rules. In the Peppol BIS Billing 3.0 specification for electronic invoices, an invoice must carry a buyer reference or a purchase order reference, and when both an invoice period and a line period are present, the line period must fall within the invoice period. A task built from a firm that bills under such rules should keep the reference fields, because a missing purchase order number is a real reason invoices are rejected.

  • Effective-dated rate card versions, including retroactive rate changes agreed after the work was done.
  • Earn codes for regular, overtime and holiday time, and the workweek definition that assigns them.
  • Primary and backup approvers, and approvals given by email that never reached the system.
  • Holds on billable charges, with the comment explaining the hold.
  • Summarized invoice lines that combine many workers or days, which hide which input was wrong.
  • Purchase order and buyer references required by the client or the invoicing standard.

The privacy reviewed back office reconciliation task packet

The asset is a packet definition: a bounded question, a frozen evidence bundle, a closed set of allowed answers and a privacy screen that runs before any record enters the set. It is written so a scorer compares an AI system's answer with a verified resolution, not with a reviewer's opinion.

  • Grade A: gold outcome present, rate card version and approval both linked by identifier.
  • Grade B: gold outcome present, one link inferred from dates rather than identifiers.
  • Grade C: no closed outcome; analysis only, never used to score.
  • Split evaluation and training sets by client and by period so the same placement never appears on both sides.
The privacy reviewed back office reconciliation task packet
ComponentContentRuleWho confirms it
QuestionDoes invoice line L agree with approved time and the rate in force for its work dates?One billed line per packetBilling lead
Evidence bundleRate card versions, timesheet and entries with versions, approval record, billable charge, invoice statement and linesFrozen at packet creation; every document datedPay and bill administrator
Allowed answersAgrees; disagrees with a named input; cannot determine from the evidenceA disagree answer must cite the field and the date that conflictBilling lead
Gold outcomeCredit note, rebill, adjustment or written client acceptanceOnly cases closed in the billing systemAccounts receivable lead
Privacy screenWorker, approver and client names, contact details, pay rates and bank fieldsFails closed: no screen result, no packetPrivacy reviewer
TokenizationStable tokens for worker, client, approver and placementSame token for the same entity across all packetsData preparer
Rights screenClient contract and VMS program terms for each record's originVMS-originated records excluded unless terms permitContract owner and counsel
Exclusion logCount and reason for every case left outExcluded cases counted, never silently droppedProject lead

Status fields versus correcting documents: what proves a billed line was right

The record that proves the outcome is the correcting document, not a status field. An invoice marked finalized, a charge marked invoiced or a timesheet marked approved shows where a record sat in a workflow; it does not show that the amount was right. A correct answer is one that matches what the firm later did about the line.

Bullhorn's invoice statement model shows why this matters. A credit invoice points to the original through creditOfInvoiceStatement, the original records creditedByInvoiceStatement and isCredited, and rebills are linked through rebillFromInvoices and rebillToInvoices. The Peppol specification follows the same pattern for electronic invoices: a credit note or negative invoice refers to one or more preceding invoices by number and issue date. Those links are the evidence a scorer needs.

Treat a plausible final message from a model, such as a statement that the invoice is reconciled, as an answer to be checked, never as the outcome. The packet's gold outcome comes only from the billing system's correcting records or written acceptance filed with the case.

  • Strong proof: a credit or rebill linked to the original invoice, with the corrected line and its new rate or quantity.
  • Acceptable proof: written client acceptance of the original line, filed against the invoice.
  • Weak proof: payment in full with no dispute; clients sometimes pay lines they never checked.
  • Not proof: a status value, an approval timestamp or a note saying the issue was resolved.

Illustrative case: overtime billed at the old rate after a rate card change

This case is illustrative. It describes a hypothetical light industrial placement and uses counts and dates only; no rates or amounts are shown. The starting state is one invoice covering a two-week billing period for one worker, with a single overtime line.

The evidence bundle holds two rate card versions for the placement, one ending on the Wednesday of week two and a new version starting on Thursday after a client-approved rate increase. The worker logged 46 hours in week two, 6 of them overtime, all on Thursday and Friday. The timesheet was approved by the backup approver on Monday. The billable charge for overtime used the earlier rate card version for all 6 hours.

The applicable rule is that each hour is billed at the rate version in force on its work date. The correct decision is that the line disagrees with the rate card in force on Thursday and Friday. The outcome check is a credit and rebill: the billing system holds a credit invoice linked to the original and a rebill whose overtime line uses the new version. The task scores an answer as correct only if it names the rate card version and the work dates that conflict.

  • Counterexample: in a second illustrative case the timesheet shows approved status, but one entry was voided and replaced in a later timesheet version; the original line was correct for the replaced quantity, and an answer that flags it from the approval status alone is wrong.
  • Edge case: if the client agreed the rate increase by email after invoicing, the rate card version may have been back-dated; the packet must keep the version's added date as well as its effective date.

Screening worker, client and rate data before a packet leaves the firm

Screen every packet for worker identity, client identity, approver identity and pay information before it leaves the firm. Timesheets are employment records: Department of Labor Fact Sheet 21 explains that FLSA records include identifying information about the employee and data about hours worked and wages earned, and that records on which wage computations are based, such as time cards, are kept for two years while payroll records are kept for at least three. Retention obligations stay with the original records; the packet is a separate, minimized copy.

At a glance

Screening worker, client and rate data before a packet leaves the firm

Replace names and contact details with stable tokens, drop pay rates unless the task needs them, and keep bill rates only as relative changes when the question is about which version applied. NIST's report on de-identification of personal information notes that privacy protection improves as more aggressive de-identification is used, but less utility remains, so decide which fields the question needs before redacting, not after.

Free text is where most risk hides. Timesheet entry comments and hold comments on billable charges can mention injuries, absences, disputes or client staff by name. Review each comment field on a sample before deciding whether to keep, rewrite or drop it.

  • Always remove: worker and approver names, emails, phone numbers, addresses, tax and bank details.
  • Tokenize: worker, client, approver, placement and job order identifiers.
  • Review case by case: entry comments, hold comments and invoice notes.
  • Keep: dates, earn codes, quantities, rate card version identifiers and correction links.

Cases that should never become packets

Some reconciliation cases are better left out of any packet, however instructive they are. The general rule is that a case whose closure depends on facts outside the billing system, or whose records the firm does not control, cannot be scored or shared safely.

Leaving a case out is not a loss of information if the exclusion is logged. The count of excluded cases by reason tells a reviewer how representative the remaining packets are, and a high share of cases excluded for missing links is itself a finding about the firm's billing process. If most corrections happen by manual journal, for example, the packets will overstate how often errors are caught inside the billing system, and the dataset description should say so plainly.

  • Open disputes, collections matters or cases involving a wage claim by the worker.
  • Time captured inside a client's VMS, where the program agreement may give the client control of the record.
  • Placements under client contracts with confidentiality clauses that cover billing detail.
  • Clients or placements so small that tokenization still identifies them, for example a single worker at a single site.
  • Cases where the correction was made by manual journal outside the billing system, so no linked correcting record exists.

Reconciled pay and bill histories and a SourceX assessment

A staffing firm with several years of linked pay and bill history holds an unusual record of real reconciliation decisions. Through SourceX, a firm can license selected histories with sourcing and qualification, rights review, contracting, preparation, delivery and payment all coordinated for it.

Worker and client identifiers are removed by SourceX through approved processing routes, and nothing is delivered until the firm has approved scope and terms and signed. Checking whether a firm qualifies takes a short company assessment with no timesheet upload.

Frequently asked questions

How do you reconcile timesheets to invoices in a staffing firm?

Take one invoice line, find the billable charge and timesheet behind it, check each entry's hours and earn code against the rate card version in force on its work date, and confirm the approval. Then compare with the invoice line's quantity and rate. A line is reconciled only when every hop is linked by identifier.

Why do timesheets, approvals and invoices disagree?

Common causes are a rate change mid-period without a new rate card version, a timesheet edited after approval, overtime assigned under the wrong workweek, and summarized invoice lines that combine several inputs. Each leaves a different trace in the records, which is why a packet keeps every version.

Is an approved timesheet proof that the invoice is correct?

No. Approval shows that a client contact accepted the hours at a point in time. The invoice can still apply the wrong rate or earn code, and entries can be voided and replaced later. Correctness is proven by the correcting records or written acceptance.

Can staffing firms share timesheet data for AI training?

Only after a rights and privacy review. Timesheets contain worker identity and pay information, and records captured in a client's VMS may be controlled by the client under the program agreement. Counsel should review the contracts, and the shared copy should be minimized and tokenized.

What makes a reconciliation case unusable for evaluation?

A missing link between hours and the billed line, no closed outcome, or a correction made outside the billing system. Such cases can be studied but should not be used to score a model.

Sources

  • Bullhorn documents billable charges as created when timesheets or expense sheets are approved, grouped into bill masters for invoice generation and carried onto invoice statements, each linked to its timesheet and placement. Source
  • Bullhorn's Timesheet entity records the approving and backup approving client contacts, the approval date and an approval status of draft, submitted, approved, completed or rejected. Source
  • Bullhorn's TimesheetEntry entity records the dates covered, earn code, quantity, bill rate, timesheet version, voiding entry and the originating time system, with values including VMS, clock, mobile and IVR. Source
  • Bullhorn's InvoiceStatement entity links included billable charges and line items, and records credits and rebills through fields such as creditOfInvoiceStatement, isCredited, rebillFromInvoices and rebillToInvoices. Source
  • 29 CFR 516.2 requires records of hours worked each workday and total hours each workweek, defining a workweek as a fixed and regularly recurring period of seven consecutive workdays. Source
  • Peppol BIS Billing 3.0 lists rules that an invoice shall have a buyer reference or purchase order reference and that an invoice line period shall be within the invoice period. Source
  • In Peppol BIS Billing 3.0, a credit note or negative invoice can refer to one or more preceding invoices by invoice number and issue date. Source
  • Department of Labor Fact Sheet 21 says FLSA records include identifying employee information and hours and wages data, with time cards kept two years and payroll records at least three. Source
  • NIST IR 8053 notes that more aggressive de-identification improves privacy protection but leaves less utility in the resulting data. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies