Part of the Recruitment Software Guide
Recruitment 30 July 2026 12 min read

Recruitment CRM and Back Office Integration: UK Guide

Most recruitment agencies run their CRM in one system and their back office in another. Placement data is re-keyed. Timesheets sit in a separate platform. Invoices are generated manually or semi-manually. Compliance documents are scattered. The result is late invoices, and margins nobody can see. The legal risk also grows, and the Joint and Several Liability rules of April 2026 made that worse. This guide explains what back office means in recruitment, compares the main platforms, and covers the integration options available to UK agencies.

17.7 hrs
Lost to manual admin per vacancy (Totaljobs, 2025)
21.5%
Revenue leakage from billing errors and missed billable hours
~£17K
Annual lost productivity per recruiter from admin tasks

What "back office" actually means in recruitment

The back office handles everything that happens after the placement is made. In a permanent recruitment agency, this is relatively simple: generate an invoice, track the fee, done. In a contract or temp agency, it is a continuous operational cycle that runs for the full duration of every placement.

The core functions are:

  • Timesheets: Capturing hours worked by contractors and temps, getting client approval, handling disputes over hours, managing different rate types (standard, overtime, weekend).
  • Pay and bill: Calculating gross pay for workers, calculating the invoice amount for clients, managing the margin between the two.
  • Invoicing: Generating client invoices from approved timesheets, handling different billing formats per client, consolidating multiple placements onto single invoices, credit control.
  • Payroll: Running PAYE for temps on the agency's books, processing payments to umbrella companies and PSCs, handling holiday pay and pension auto-enrolment.
  • Compliance: Right-to-work checks, AWR (Agency Workers Regulations) tracking, IR35 status determination records, umbrella company due diligence, GDPR.
  • Margin tracking: Real-time visibility of margins per placement, per client, per consultant, per contract type.

The work runs in a chain. Somebody makes the placement in the CRM or ATS. The contractor works. The timesheet goes in. The client approves it. The back office works out the pay and the bill. The worker is paid. The client is invoiced. The margin is recorded. The break comes between the CRM and the back office. Data that somebody typed once must be typed again, or moved to another system.

The real cost of running two disconnected systems

The gap between front office and back office is not just an inconvenience. It has measurable costs that compound over time.

Re-keying data

Placement details entered in the CRM (worker name, client, rates, contract dates, payment terms) must be manually re-entered into the back-office system. This is the single biggest source of errors. Typical manual data entry error rates run between 1% and 5%. For an agency processing hundreds of timesheets weekly, even 1% means several incorrect invoices or pay calculations every week. Each manual payroll error costs about £230 to correct.

Delayed invoicing and cash flow pressure

If timesheets sit in one system waiting to be entered into another, invoices go out late. Agencies typically wait 30 to 60 days for client payment while paying workers weekly or fortnightly. A late invoice makes that gap wider. The agency then runs short of cash. It cannot take on new work, or pay its contractors.

Margin invisibility

With data split across systems, real-time margin tracking is impossible. Agency owners cannot see margin per placement, per client, or per consultant without manually reconciling data from both systems. Decisions about which clients to prioritise, which consultants are performing, and which contract types are profitable are made on incomplete information or gut feel.

Compliance gaps

IR35 status determinations, AWR milestones, and right-to-work expiry dates stored in the CRM may not be visible to the back-office team processing pay. Compliance documents uploaded to one system are invisible in the other. This fragmentation creates real regulatory exposure, particularly under the new JSL rules.

What that costs in time. A UK recruiter loses 17.7 hours on each vacancy to admin done by hand. That is about 850 hours each year, for each recruiter. That is about £17,000 of lost work each year, for each recruiter. 61% of recruiters name typing data in as the main cause. Those figures come from Totaljobs, in August 2025.

Connect with us about recruitment software · · Replies within 24 hours

What changed in April 2026: JSL and why it makes integration urgent

From 6 April 2026 a recruitment agency is liable, with the others, for unpaid PAYE tax and National Insurance. That applies to any umbrella company it works with that does not pay. The legislation was implemented through a new Chapter 11 of Part 2 ITEPA 2003.

How the liability chain works

  1. If an umbrella company fails to pay correct PAYE or NICs to HMRC, HMRC first pursues the umbrella company.
  2. If the umbrella cannot or will not pay, HMRC transfers the liability to the recruitment agency.
  3. If the agency cannot pay, liability transfers to the end-client.
No statutory defence for due diligence. Unlike some compliance regimes, checks on umbrella companies do not give you a legal defence under JSL. Even rigorous auditing cannot fully protect agencies from inherited tax liabilities. Spot checks and accreditations alone are no longer enough. Real-time compliance tracking is now essential.

What this means for back-office software

A back-office system must now give you live audit trails of tax calculations and payments through umbrella supply chains. They need three things. A record of each umbrella company and its compliance. A warning when a worker is paid through an umbrella you have not approved. A view of whether the umbrella deductions match the PAYE and NICs you expect.

Agencies running disconnected CRM and back-office systems face higher JSL risk because compliance data is fragmented across platforms. HMRC may ask for an audit trail. Pulling that from two or three separate systems is much harder, and their records often disagree. One joined system gives you one report.

The sector has answered by cutting its supplier lists. Agencies now work with fewer umbrella companies. Their Preferred Supplier Lists are shorter, and hold only providers that are fully accredited. This consolidation is expected to continue through 2026 and 2027.

IR35 and the back-office workflow

IR35 determinations have a direct impact on how the back office processes pay and invoicing. Some work falls inside IR35. Whoever pays the fee, which may be the agency, must then take Income Tax and employee NICs through PAYE. They must also account for employer NICs. Outside IR35, the contractor invoices the agency and manages their own tax.

From April 2026, updated small company thresholds mean about 14,000 companies previously classified as medium are now reclassified as small. For contractors working with these newly reclassified companies, responsibility for IR35 status determination shifts back to the contractor. That creates a record you must keep. The agency must know which clients count as small, and which as medium, because the rules differ.

Integration requirement: IR35 determinations made or stored in the CRM must flow through to the back-office system to ensure correct payroll treatment. Status Determination Statements need to be stored and linked to the correct placement in both systems. Rate calculations differ for inside versus outside IR35 engagements, and the back-office system must handle both correctly without manual switching.

Agencies are also seeing more Statements of Work and project-based engagements structured for outside IR35 status. These require different invoicing and payment workflows compared to standard time-and-materials contracts, adding another layer of complexity that disconnected systems handle poorly.

Back-office platforms compared: what each one actually does

The UK recruitment back-office market includes dedicated platforms, integrated modules within larger CRM suites, and outsourced services with technology layers. Here is what the main options offer. For a broader look at the CRM side of this picture, see our Bullhorn alternatives comparison.

ETZ

ETZ focuses on paperless timesheet capture, automated invoicing, and compliance management. It claims to turn a timesheet into an invoice in 60 seconds and can process 1,000 invoices in a single batch. It shows late timesheets as they happen, and chases them by text or email in one click. It guarantees AWR compliance, and meets GDPR. It handles contracts through ETZSign. It connects to Xero and QuickBooks. ETZ also offers a Startup 20/20 product for smaller agencies at reduced cost. Pricing is quote-based, but ETZ claims to save agencies up to 85% on processing costs.

Evertime

Evertime offers two products. Evertime SaaS is a self-service cloud platform for agencies that want to run their own back office. Evertime PRO is a flexible managed service where agencies choose their level of pay and bill support, from partial to fully managed. Used by 250+ agencies managing 17,500+ contractors monthly. Pricing is monthly per-contractor, with lower per-contractor cost at higher volumes. Evertime has a partnership with Eclipse Software for CRM connectivity and integrates with a range of third-party CRM and accounting platforms.

Flo

Flo combines back-office outsourcing and software for temporary recruitment agencies. It has three products. Dataflo, a CRM for temp recruitment. Workflo, a back office run for you, which covers timesheets, payroll, credit control and bookkeeping. Fullflo, a CRM and back office together for a new agency, paid on success with no set-up fee. Flo is sector-specific, with configurations for healthcare, education, construction, hospitality, and IT. One predictable monthly cost with no hidden fees.

Primo Time

Built by Accentra with 30 years of experience in UK contracting and recruitment payroll. Primo Time is an all-in-one cloud platform for pay and bill, PAYE, and financial ledgers. It holds its own ledger, called Primo Books. It connects to your bank, and matches receipts by itself. It pays umbrella companies and PSCs. It also connects to Xero. The multi-agency interface makes it a good fit for back-office service providers managing multiple agencies. Pricing is quote-based.

Finity

Finity is a unified payroll ecosystem designed for high-volume processing: thousands of weekly timesheets. Features include automated timesheet management, approval, and invoicing, margin reporting, worker payments, and accounting software integration. Pricing is volume-based and pay-per-usage with no charge for inactive workers. Take a business with 2,500 payslips and 3,000 timesheets each week. It pays £1.50 for the first 500 payslips. It pays £1.24 for the next 1,500, and £0.69 for the last 500. A free Compliance Hub and 14-day free trial are available.

Bullhorn Back Office

Part of the Bullhorn One suite, this adds onboarding, time and expense tracking, invoicing, and payroll integration to the core Bullhorn CRM/ATS. Bullhorn claims over $24 billion invoiced through the platform annually. The main advantage is native integration with the most widely used recruitment CRM in the UK. Cost is the main drawback. The CRM alone runs at about $99 to $315 for each user each month. The back-office parts cost more. Setting it up costs $1,000 to more than $50,000. Multi-year contracts are typical, and reviewers report 20% renewal price increases.

Vincere Pay and Bill

The pay and bill part of Vincere, now Access Vincere Evo, covers six things. Timesheets handled by the system. Invoicing. Payments to workers. Invoices joined into one. Retainers billed in stages. Reports on temp recruitment. Core CRM starts from £69 per user per month, with the pay and bill module priced additionally on a quote basis. Since the Access Group acquisition, support quality has declined according to reviews, with customer service now AI-first and no human support on weekends.

Platform Pricing Timesheets Pay and Bill CRM Integration Best For
ETZ Quote-based Yes (paperless) Yes API (various CRMs) Mid-sized agencies wanting automation
Evertime Per-contractor/month Yes (cloud) Yes (self-service or managed) Eclipse partnership, third-party APIs Agencies wanting flexible managed service
Flo Fixed monthly (success-based for startups) Yes (via Workflo) Yes (outsourced) Dataflo CRM included or standalone Temp agencies, startups, healthcare/education
Primo Time Quote-based Yes Yes (with financial ledger) Xero API, multi-agency interface Multi-entity operations, back-office providers
Finity From £0.69-£1.50 per payslip (volume-based) Yes (high volume) Yes Accounting software integration High-volume temp agencies
Bullhorn Back Office $99-315/user/month + modules + implementation Yes Yes (native) Native (Bullhorn CRM required) Agencies already on Bullhorn CRM
Vincere Pay and Bill From £69/user/month + pay and bill module Yes Yes (native) Native (Vincere CRM required) Mixed perm/temp agencies on Vincere

Connect with us about recruitment software · · Replies within 24 hours

The three integration models

There are three broad approaches to connecting (or replacing) disconnected CRM and back-office systems. Each has trade-offs depending on agency size, budget, and how much operational control the agency wants to retain.

Model 1: All-in-one platform

Bullhorn One, Vincere with Pay and Bill, Eclipse, and Flo's Fullflo package all offer CRM and back office in a single system. The advantage is native data flow: placements, timesheets, invoices, and compliance records live in one database. The disadvantage is vendor lock-in. If the CRM is strong but the back office is weak (or vice versa), the agency is stuck with both. Pricing tends to be higher, and switching costs are significant because the entire operation depends on one vendor.

Model 2: Best-of-breed with API integration

The agency runs its preferred CRM (Bullhorn, Firefish, Mercury, JobAdder) alongside a dedicated back-office platform (ETZ, Evertime, Primo Time, Finity) connected via API. This gives the agency the best tool for each function, but the integration depends on what APIs the vendors expose. Many CRM and back-office vendors do not offer direct integrations with each other. An API may exist, and you still often pay somebody to build the connection. Both vendors then keep changing their software, so you keep paying to hold the connection together. For more on the broader integration landscape in recruitment, including job board connectivity, see our separate guide.

Model 3: Outsourced back office with CRM connector

Companies such as 3R, Flo Workflo, KUDO and New Millennia run the whole back office for you. Their software then connects to the CRM of the agency. The agency focuses on sales and candidate management while the outsourcer handles timesheets, payroll, invoicing, and credit control. 3R, for example, funds 100% of invoice value and offers 24-hour contractor payment from approved timesheets. This model suits startups and small agencies that lack the volume or staff to justify running their own back-office operation. The trade-off is less operational control and dependency on the outsourcer's processes and timelines.

What a properly integrated system looks like

An agency can choose one platform for everything, the best tool for each job, or an outside service. The aim is the same in each case. Data moves without anybody typing it again, and the compliance facts are visible wherever they are needed.

A properly integrated system handles the following without manual intervention:

  • Placement data flows automatically to back office. A consultant makes a placement in the CRM. It holds the client, the candidate, the rates, the contract type, the start date and the IR35 status. All of that reaches the back office with nobody typing it again.
  • Timesheets link back to CRM placements. When a contractor submits a timesheet, it is automatically matched to the correct placement, with the correct rates, in the correct billing period.
  • Invoices generate from approved timesheets without re-keying. Client approval triggers invoice generation using the rates and billing format already stored in the system.
  • Compliance documents are visible across both systems. Right-to-work checks, IR35 determinations, AWR milestone dates, and umbrella company due diligence records are accessible to both front-office consultants and back-office processors.
  • Real-time margin reporting. Margins per placement, per client, per consultant, and per contract type are visible without running manual reconciliations across two databases.
  • Audit trail for JSL compliance. Every tax calculation, umbrella payment, and PAYE deduction is logged and traceable from placement through to payment.

Why the join between two systems is always weak

Every model above ends at the same problem. Two systems must agree on one placement, and neither was built to.

The CRM holds a placement in its form. The back office holds a different record, with its own identifier. The connection between them is a translation, and somebody must keep paying for it, because both vendors keep changing. The margin nobody can see, and the audit trail that spans two systems, both come from that.

A shared foundation removes the translation. A client, a candidate, a placement, a timesheet and an invoice are declared once, with permanent identifiers, and every system reads the same forms. The pay run and the placement are then the same data, not two records that must be matched.

Your agency still owns its own system. We explain how a whole sector shares one foundation in bespoke software for a whole sector. We describe that market in what does an interoperable software market look like.

When off-the-shelf integration is not enough

The platforms listed above cover the majority of standard recruitment back-office workflows. But standard has limits.

Vendor APIs often expose only a subset of the data an agency needs to move between systems. A CRM might let you pull placement records via API, but not push compliance documents or rate amendments back. A back-office platform might accept timesheet data via API, but require manual setup of billing rules for each new client. The integration exists on paper but breaks down in the detail.

Agencies also accumulate operational logic over years that does not map to any vendor's standard workflow. Rate calculations that factor in client-specific rules. Invoicing formats that differ by sector or contract type. Compliance checks triggered by specific combinations of worker status, client classification, and contract structure. These requirements sit in spreadsheets, in people's heads, or in workarounds bolted onto existing systems.

This is where bespoke integration, or a bespoke system built from scratch, becomes the practical option. A custom integration layer can connect any two systems using their APIs (and where APIs fall short, direct database connections or file-based data exchange). A system built for you puts the exact way your agency works into the software. There is then no gap between how you work and what a vendor platform allows.

When a system of your own makes sense. Your agency has grown past its systems. The link between CRM and back office fails in the detail. You now spend more time working around the software than working with it. A system built to the way you work may cost less over three years. Compare it with the licences, the set-up and the upkeep of two or three ready-made platforms that never fully join.

Connect with us about recruitment software · · Replies within 24 hours

Sources and further reading

You can see this in a working system. The ESRE live recruitment demo opens with no login, and it shows the work in this guide. Sign in as payroll and see the placement data flow to back office, or as consultant and close the placement. It is a working system, not a screenshot.