Placement guarantee disputes across ATS, CRM and accounting: a system map of records and linking keys

Short answer

Reconstructing a placement guarantee dispute takes five joins across usually three or four systems: the placement to its job order and fee terms, the placement to any correction of its start date, the client's claim to the placement, the evidence that the role changed to that claim, and the decision to the credit note or replacement placement. The ATS typically holds the first two, a CRM or shared inbox holds the claim and the change evidence, and accounting holds the credit.

Visual briefFull-size diagram
Four systems drawn as nodes around one joined case: the ATS, the email inbox, the CRM and accounting, with linking keys (placement ID, case reference and credit memo reference) traveling along the connections to join a single dispute.
Illustrative map for a fictional staffing firm; real systems and keys differ by firm.

This system map belongs to the placement guarantee hub. The worked placement guarantee dispute tells one story; this page shows the plumbing that lets anyone tell such a story from records.

Where each piece of a dispute is kept

A placement guarantee dispute is assembled from records nobody designed to sit together. Four systems are common.

The ATS holds the job order, with requirements and often the fee, and the placement, with the start date and, in many firms, the guarantee period. Where change requests are used, it also holds the history of edits made after a placement was approved.

The email inbox holds most of what happens after the start: the hiring manager's note that the job has changed, the notice that the hire is leaving, the first message disputing the fee.

The CRM or ticketing tool, where one is used for client service, holds the claim as a case with a reference, an owner and a status.

Accounting holds the outcome: a credit note, a refund, or the invoice for a replacement placement at no fee.

The linking keys, system by system

SystemRecordLinking keyOwner
ATSJob order with fee and guarantee termsJob order IDAccount manager
ATSPlacement with start datePlacement ID, carrying the job order IDBack office
ATSChange request on the placementPlacement ID on the requestBack office
Email inboxRole-change and resignation messagesPlacement ID or candidate name typed in the textRecruiter or account manager
CRMPlacement guarantee claim caseCase reference, with the placement ID if enteredAccount management lead
CRMDecision memoCase referenceOperations director
AccountingCredit note or refundCredit memo reference citing the placementFinance controller
ATSReplacement placementNew placement ID, linked to the original if notedRecruiter

Two keys do most of the work: the placement ID and the claim's case reference. Every other join is only as good as the habit of typing one of them into the next system.

Five joins and how each one fails

JoinConnectsWhat usually breaks it
TermsPlacement to job order and fee termsGuarantee wording kept only in a signed PDF, not in fields
StartPlacement to its correctionsStart date overwritten by a direct edit, with no request
ClaimClient's claim to the placementClaims handled by phone or email with no case opened
ChangeEvidence of the role change to the claimNotes that name the candidate but not the placement
OutcomeDecision to credit or replacementCredit booked as a lump discount on a later invoice

The start join deserves extra attention because the guarantee window is counted from the start date. In Bullhorn, for example, the vendor's support blog flags a wrong start date as a frequent slip and makes approved change requests the route for later edits, and its knowledge base describes a list view of those requests. For the map, that means the start join is a separate record with its own key (the placement ID on each request), not a property of the placement itself. Where it is missing, the map should say "final value only" for that hop. The Bullhorn data export page covers what else sits in placement history.

One claim traced through four systems (Illustrative)

Fictional, written for this page. A 240-person finance and accounting staffing firm places a controller with a manufacturing client under a 60-day replacement guarantee.

StepSystemRecordKey carried forward
OrderATSJob order JO-4471, controller, fee and 60-day replacement termsJO-4471
StartATSPlacement PL-9032 created from JO-4471PL-9032
CorrectionATSChange request moves the start date two weeks later, approved by back officePL-9032
ChangeEmail inboxClient asks the controller to also run payroll; recruiter replies citing PL-9032PL-9032 typed in the subject line
ClaimCRMCase C-2218 opened when the controller leaves on day 52C-2218, with PL-9032 entered
DecisionCRMMemo: replacement owed, payroll duties noted for the new searchC-2218
OutcomeATS and accountingReplacement placement PL-9177 at no fee; zero-value invoice cites PL-9032PL-9177 linked to PL-9032

Every hop in this case carries a key, which is why it can be read end to end. The corrected start date matters too: counted from the original date, the departure would have fallen on day 66, outside the 60-day window. Many real firms will not have every hop. A common picture is solid ATS and accounting joins with a patchy middle, and that is still worth describing honestly. The same promise, event, claim and outcome pattern shows up in carrier invoices on the freight audit exceptions page.

Questions for the back office and finance

Ask these at metadata level and write down the answers, not examples.

  1. Are guarantee periods and remedies stored as placement or job order fields, or only in client agreements?
  2. Since which year have start-date corrections gone through change requests?
  3. Is there a case type or tag for placement guarantee claims, and does it record the placement ID?
  4. Do recruiters put the placement ID in emails or notes about changes after the start?
  5. Do credit notes and refunds name the placement they relate to?
  6. Are replacement placements linked to the original in the ATS?
  7. When does access to any earlier ATS end, and was its change history imported?

Qualification and open items

The records are the firm's own operating records, but client agreements carry confidentiality terms and the placed person's details are personal data; who owns candidate data at a staffing agency explains those layers, and staffing firm ATS data licensing covers the wider question. The operations director sponsors; the CEO, or the owner-CEO in an owner-run firm, approves and signs, often with the CFO advising.

An introduced firm needs 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 90% of the data is in English. Join quality, de-identification, client consent, buyer interest and any offer stay unknown until SourceX reviews the opportunity. To write the answers into a handoff, use the placement guarantee brief template.

Next step

Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the answers show that placement IDs travel from the ATS into claims and credit notes for several years, register as a partner, check the firm against who qualifies and read the program terms before you introduce its operations director.

  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 rewardYour 25% of the actual supplier payout. 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

Does a firm need Bullhorn for this map to apply?

No. Bullhorn is used here because its public support pages describe placement change requests. Any ATS has some version of job orders and placements; the questions are whether corrections keep a history and whether other systems carry the placement's identifier.

What if claims were handled entirely by phone?

Then the claim join is missing for those years, and only the credit note, if it names the placement, shows a dispute happened. Record that as a gap; it does not need fixing for an introduction.

Should the consultant test the joins on real data?

No. The consultant asks how the systems are used and records the answers. Any testing is done later by the firm itself, if it decides to proceed and SourceX's review asks for it.

Sources

  1. bullhorn.com/customer-blog/support-tip-requesting-placeme…
  2. kb.bullhorn.com/ats/Content/BHATS/Topics/changeRequestList.htm
  3. 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 90% 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