ERP Consultant for Recruitment

Recruitment workflows as a process map

Recruitment agencies run two very different revenue models, often side by side, and the back office has to support both. In words, the process maps look like this:

• Permanent recruitment: client terms agreed -> job order -> sourcing and shortlist in the ATS -> interviews -> offer accepted -> placement confirmed with salary and fee -> invoice -> payment -> guarantee period tracked -> rebate or replacement if the candidate leaves.
• Contract or temporary staffing: client terms and rate card -> assignment created with pay and bill rates -> contractor onboarding and compliance checks -> weekly or monthly timesheets -> client approval -> client invoice -> contractor payment through payroll, a limited company or an intermediary, depending on the country -> margin reported.

Retained search adds staged fees at agreed milestones. Some agencies also run fixed-term or statement-of-work arrangements.

When I map processes for an agency, the key question at each step is where the data lives. Placements normally start in the ATS, but rates, timesheets, invoices and payments may sit in four other places. That is where errors and delays come from.

Common pain points in recruitment back offices

The problems I see in recruitment agencies are rarely about the ATS itself. They sit between the front office and finance:

• Timesheets chased by email. Contractors submit late, clients approve inconsistently and the payroll cutoff becomes a weekly fire drill.
• Rates rekeyed. Pay and bill rates agreed in the ATS are typed again into payroll and invoicing, and rate changes are missed.
• Margin known too late. Gross margin per assignment, client and consultant is calculated in spreadsheets after month end.
• Rebates handled manually. When a permanent candidate leaves within the guarantee period, credit notes depend on someone remembering the terms.
• Commission disputes. Consultant commission is calculated from data that finance and sales do not agree on.
• Cash flow strain. Contractors are paid before clients pay, so slow invoicing directly hurts working capital.

Each of these needs a clear rule before it needs software: who approves a timesheet, which rate applies to overtime, how a rebate is calculated. Once the rules are written, the right platform can enforce them.

Recommended ERP modules for recruitment agencies

An agency's systems usually combine an ATS with a finance and back office layer. The modules that matter most are:

• Client and contract management: terms of business, fee percentages, rate cards and guarantee periods per client.
• Placements and assignments: records created from the ATS with start dates, rates, consultant split and status.
• Timesheets: contractor submission, client approval portal, rate types and period cutoffs.
• Billing: placement invoices, weekly or consolidated contract invoices, credit notes and rebates.
• Contractor payments: payroll export or contractor payables, depending on how contractors are engaged.
• Accounting: receivables, multi-currency where needed, and accruals for approved but unbilled time.
• Commission: consultant splits and thresholds calculated from finalized placement data.
• Reporting: gross margin by assignment, client, consultant and desk, plus debtor days and contractor headcount.

Contractor engagement, employment status and payroll rules differ by country, so those requirements should be confirmed with your legal and payroll advisors. I capture them as requirements and test platforms against them. For broader finance automation, see ERP for finance automation.

Implementation checklist for recruitment agencies

Before configuring any back office system, I make sure these items are documented and agreed:

1. Every revenue type in use: permanent, contract, retained, fixed-term and any statement-of-work model.
2. Fee rules for permanent placements, including the salary basis and any minimum fee.
3. Guarantee, rebate and replacement terms per client, and how credit notes are triggered.
4. Pay and bill rate structures, including overtime, shifts, expenses and statutory on-costs.
5. Timesheet submission, approval and cutoff rules, and what happens with late or disputed timesheets.
6. How contractors are paid in each country you operate in, confirmed with advisors.
7. Commission rules and the data they depend on.
8. Opening data: active assignments with rates, open placements in guarantee, unpaid invoices and accrued time.

UAT should run full timesheet cycles for a handful of real assignments, including a rate change, an overtime week and a rejected timesheet, plus a permanent placement that triggers a rebate. I write those UAT scenarios so the first live payroll and billing run is not the real test.

Integrations, migration and growth

The ATS is the front-office system of record for candidates, vacancies and placements. Finance needs a reliable feed of placements and rates from it, timesheets from a portal, and payments to payroll or contractor payables. I design the integration so placement data flows one way into finance, approved timesheets drive both billing and pay, and changes made in finance never silently overwrite the ATS.

Migration focuses on active assignments, placements still in their guarantee period, rate cards, open invoices and contractor balances. Historical placements can usually stay in the ATS for reporting.

Recruitment is also a sales business. Client acquisition benefits from the same CRM discipline and lead generation approach that works for other service firms, as described in the services firm case study. For agencies placing into specialist sectors, the IT services and professional services pages describe how your clients run their businesses. Contact me to map your placement-to-cash process.