4th Sight logo
← Back to articles

Cleaning ATS and Finance Data Before Using AI

A practical guide for recruitment CFOs on cleaning ATS and finance data before applying AI, with examples from timesheets, payroll and billing.

Cleaning ATS and Finance Data Before Using AI

Most recruitment CFOs we speak to are being asked the same question by their boards: what is our AI plan? The honest answer, in many cases, is that AI cannot do much useful work yet because the underlying data is not in a fit state.

Before any model can produce reliable insight on margins, pay and bill discrepancies or contractor profitability, the data coming out of your ATS, CRM, timesheet, payroll, billing and accounting systems needs to agree. That rarely happens by accident.

Why this matters for recruitment businesses

Recruitment is a high-volume, low-margin business with thousands of small transactions every week. A single contractor placement can touch the ATS, a timesheet portal, a payroll system, a billing system and the general ledger, often with different reference numbers in each.

If AI is pointed at this data without preparation, it will confidently produce wrong answers. A model cannot tell you why gross margin dropped last week if half the timesheets are still sitting unapproved and the rate card in the ATS does not match the rate on the invoice.

For a CFO, the risk is not that AI fails quietly. The risk is that it produces plausible commentary on numbers that are themselves wrong, and the board acts on it.

What causes the problem?

The root cause is almost always the same: disconnected systems that were chosen at different times for different reasons.

A typical recruitment business runs an ATS or CRM for candidate and client records, a separate timesheet platform, a payroll system or bureau, a billing engine and an accounting package such as Xero, NetSuite or Business Central. Each system has its own view of a contractor, a client and a placement.

Common data issues include:

  • Client and candidate records duplicated across the ATS and accounting system
  • Placement IDs that do not flow through to invoices or payroll runs
  • Rate cards held in the ATS but overridden manually at billing
  • Missing purchase order references on invoices
  • Timesheet hours that do not reconcile between the portal and payroll
  • Cost centres and brand codes applied inconsistently

None of these are exotic problems. They are the everyday reality of a back office that has grown faster than its systems.

The impact on finance and back-office teams

The operational cost is significant. Finance teams spend the first two weeks of every month rebuilding the same spreadsheets, joining exports from the ATS, timesheet system and accounting ledger to produce a margin report that should be available on day one.

Credit control teams chase invoices without knowing which are genuinely disputed and which are simply missing a PO reference. Payroll teams pay contractors on time, as they must, but billing issues are only spotted weeks later when the cash does not arrive.

Commission calculations, which depend on data from several systems, become a monthly negotiation rather than a calculation. Board packs are assembled manually from multiple exports, and by the time they land, the numbers are already out of date.

This is the environment into which AI is being introduced. It is not a good starting point.

How a trusted data foundation helps

The first step is not AI. It is building a single, reconciled view of the data that finance and operations both trust.

That means bringing ATS, CRM, timesheet, payroll, billing and accounting data into one place, with consistent identifiers for clients, candidates, placements and brands. It means agreeing which system is the source of truth for each field, and enforcing that consistently.

Once the data foundation is in place, recurring checks can run automatically. Timesheets approved but not invoiced. Invoices raised at a rate that does not match the agreed terms. Candidates paid for hours that have not been billed. Margin by consultant, by client and by contract type, refreshed daily rather than monthly.

This is unglamorous work, but it is what makes everything else possible, including AI.

Where automation and AI-assisted insight can add value

With a clean data layer in place, automation and AI start to earn their keep.

Automation handles the repetitive reconciliation work: matching timesheets to invoices, flagging rate mismatches, identifying missing PO references, and producing exception reports rather than full data dumps. The finance team reviews exceptions, not every transaction.

AI-assisted insight then sits on top. It can summarise why margin moved week on week, highlight clients whose effective margin has drifted from the contracted rate, and generate first-draft commentary for management accounts. It works because the underlying numbers are reliable.

What AI should not do, at this stage, is replace finance judgement on contentious items, sign off commission calculations, or write to the ledger without human review. Used carefully, it removes preparation work and gives the team time to focus on decisions.

Practical examples

Timesheet to invoice reconciliation

A contractor submits 40 hours on the timesheet portal. The hours are approved, exported to payroll and the contractor is paid. The invoice to the client, however, is raised for 38 hours because of a manual adjustment that was never documented. With a clean data foundation, this two-hour gap is flagged the same day, not at month-end.

Rate card drift

The ATS holds a charge rate of £450 per day. The invoice is raised at £440 because an old rate was copied across when the contract was extended. A simple automated check between ATS and billing data catches this before it becomes a quarter of lost margin.

Commission calculations

Consultant commission depends on placements from the ATS, billed revenue from the accounting system and cash received from the debtors ledger. When these three sources disagree, commission becomes a dispute. A reconciled data set removes the argument.

How 4thSight helps

4thSight is built specifically for recruitment finance and back-office teams. It connects to the ATS, CRM, timesheet, payroll, billing and accounting systems already in use, and creates a reconciled data layer that finance can rely on.

From there, 4thSight automates the recurring checks that most teams currently run in spreadsheets, including timesheet to invoice matching, rate card validation, margin analysis and debtor reporting. AI-assisted commentary is layered on top, so the team gets explanations alongside the numbers rather than another export to interpret.

The platform is designed to be used by finance and back-office users directly, without depending on a development team for every change.

Conclusion

AI will only be as good as the data underneath it. For recruitment CFOs, the practical priority is not picking a model, but cleaning and connecting the data flowing out of the ATS, timesheet, payroll, billing and accounting systems.

Get that foundation right, and automation and AI insight become genuinely useful. Skip it, and the board gets confident answers to the wrong questions.

If you would like to see how a reconciled data layer could look across your own systems, the team at 4thSight is happy to talk it through.