Writing agreed placement terms into every billing system
A work order confirms a rate, a start date, an approver and a rule for overtime. Those facts are then retyped into the placement record, into the pay and bill system and often into a branch spreadsheet nobody admits to. A digit that differs between two of them does not fail loudly. It shows up weeks later as a rate discrepancy on an invoice, and by then the portal has already generated the document, so the correction is a credit or debit memo rather than an edit.
The parser reads the resume, then somebody corrects the employment dates it merged, which is most of the time it was supposed to save.
Resumes arrive in every format that has ever existed, including scans with no text layer and designed templates in two columns that get read in the wrong order. Parsing is nearly always a third-party component, and its characteristic failure is employment history: dates written as ranges with words in them produce merged employers and wrong tenure.
- SAP Fieldglass
- Bullhorn
- QuickBooks Online
When this is the wrong thing to build
Pick something else if one system holds rates and everything downstream reads from it. Where a portal owns the rate and your back office owns payroll the two will drift, and this only helps if somebody will treat the portal as the winner in a disagreement.
The constraint that shapes it
This is the sector where the boundary is sharpest, and it is worth stating plainly: rejection is the regulated act, not enrichment. More on how this sector works.
One change of state, written everywhere it belongs, once. Read what this shape is, or start from one of these.
- Keeping a status change from being typed four times
- Closing a matter in every system that still holds it
- Retiring old equipment from every record naming it
- Writing one client change into every system that holds it
- Writing one staffing change into every system that grants access
- Keeping an endorsement change from being typed twice
- Why does the bill rate on the invoice differ from the rate card?
- How do I stop rekeying placement rates into the back office?
- What happens when a client changes a rate mid assignment?
- How is overtime billed when the multiplier differs between systems?
- Who owns the rate when the portal and the ATS disagree?
Back to recruiting and staffing, or see how this is priced and scoped.