Skip to content

Glossary

Terms used across this documentation and in the API’s own field names. The industry vocabulary is the part most integrators have to learn; the software is the easy half.

A recruitment business using Recruso. Also the tenant — every record in the system belongs to exactly one agency, and your credentials are bound to one. See Multi-tenancy.

Per-tenant configurable lists your agency owns — job categories, shifts, activity types and so on. Distinct from reference data, which is global and read-only. See Reference data and agency lookups.

Per-tenant operational configuration rather than vocabulary: bank holidays, rate types, AWR alert rules, document templates, and the sequences that allocate worker and invoice numbers.

UK legislation giving agency workers equal treatment with comparable direct employees after a qualifying period of work. Certain absences break that qualifying period, and agencies configure their own thresholds per absence reason — sickness, maternity, paternity, adoption, jury service, unpaid leave.

A worker assigned to a client’s site for a given date and time. Carries its own pay and charge rates, has a status, and can recur. Not yet published by the API.

A physical office or operational unit of an agency. Clients and workers sit under a branch, and a Recruso user’s accessible branches further narrow what your integration can see.

What the agency bills the client per hour or day. Contrast pay rate; the gap between them is the margin.

A company that engages the agency to supply workers. Belongs to one branch, and operates one or more sites.

The machine-to-machine access token your integration uses, obtained by exchanging an API app’s client id and secret. It belongs to the app rather than to a person, and it is the only token this API accepts. See Authentication.

The evidence a worker must hold to be placed — right-to-work documents, qualifications, certifications. Configured per agency.

A unit within a branch that work is booked against, for internal cost attribution. Cost centres are branch-scoped, and can also be linked to sites and site contacts.

An adjustment against an invoice — for over-billing, cancellation and similar. Belongs to one invoice. Not yet published by the API.

The web application at developer.recruso.co.uk where an agency creates API apps, mints and rotates their credentials — a client id and secret issued as a pair — and sets an app’s IP allow-list. Access comes with a Recruso CRM licence and the appropriate role. It is the only place API credentials are issued; this API does not expose them.

A bill to a client, generated from completed plans. Can cover several plans within one week. Not yet published by the API.

A document UK agencies must give a worker before they agree to terms, setting out pay, deductions and who pays them. Templated separately for PAYE and subcontractor workers, because the content differs.

A prospective client — a company the agency is pursuing but has not yet converted.

Charge rate minus pay rate. The agency’s gross return on a placement.

Pay As You Earn — the UK system where the employer deducts income tax and National Insurance before paying the worker. A PAYE worker is on the agency’s own payroll, as opposed to being paid through an umbrella company or supplied by a subcontractor.

What the worker is paid per hour or day. Contrast charge rate.

A worker’s bookings at one site grouped within a single week, with hours, adjustments and holiday taken. The unit the financial side of the product acts on: completing a plan snapshots the agreed hours and rates and produces both payroll and invoice values, which are then legally authoritative and never recalculated. Not yet published by the API.

Platform-wide controlled vocabularies, identical for every agency and read-only — titles, genders, nationalities, NI categories, payment methods and similar. Every vocabulary can be listed and fetched by id through the API; none can be written. See Reference data and agency lookups.

The weekly head record that a week’s daily plan rows point at. The weekly rate lives here rather than on the individual days.

Holiday pay included in the hourly rate as it is earned, rather than accrued and paid when leave is taken. Configured per agency.

A worker’s legal entitlement to work in the UK. Verified through Home Office checks; a share code may be recorded against the worker.

External systems Recruso integrates with — Sage Payroll and Staffology for payroll, Sage Accounts for invoicing. Not exposed through this API.

A client location where work is actually performed. Defines rates per skill, assessment requirements and contacts, and is what a worker’s suitable, not suitable, assessed and banned lists refer to. Belongs to one client.

Deletion that retains the record rather than destroying it. Existing references keep resolving and the value stops being offered for new use. The name usually stays reserved, which is why re-using it can be rejected. Some resources support an explicit restore.

A third-party company supplying workers to the agency. Has its own workers and documents, and is invoiced separately.

The record of what a worker actually worked in a week, confirming the plan before payroll and invoicing run. Not yet published by the API.

An intermediary that employs the worker and handles their payroll, so the agency pays the umbrella rather than the worker. One of the engagement models alongside PAYE and subcontractor supply.

The date a work week ends, and the anchor everything weekly is grouped by. Each agency defines its own week, so this is not a calendar week. See The recruitment week.

An individual the agency places into work. Registered against one branch of one agency; a person working for two agencies exists as two unrelated worker records. See Workers.

A worker’s human-facing reference, allocated from the agency’s own sequence at creation. Distinct from the worker id, which is what the API endpoints take.

A worker’s opt-out from the Working Time Directive’s maximum weekly hours. Recorded on the worker.