Request a demo

Payroll and HR

Setting Staff KPIs That Teams Actually Use

How to set a few staff and team KPIs that people understand, can influence and review monthly, with worked examples for finance, sales support and operations teams.

By Flux Editorial TeamPublished 4 min read

Illustrative example with fictional data.

Most KPI frameworks fail quietly. Targets are set in January with real energy, filed in a shared drive, and next mentioned at appraisal time, when nobody can remember what they were. A KPI only works if the person it measures can see it, influence it and talks about it every month.

Four tests for a KPI worth keeping

Before a KPI goes on anyone's list, it has to pass four tests:

  1. They can move it. A credit controller can influence overdue debt. They can't influence total sales. Measure people on what their own work changes.
  2. It's measured from records, not opinions. "Invoices sent within 2 working days of delivery" can be counted. "Good attitude to billing" can't.
  3. It's reviewed monthly. A KPI reviewed once a year is a memory test, not a management tool.
  4. There are only a few. Three to five per person. Twelve KPIs means none of them matter.

Team KPIs and individual KPIs

Use both, and connect them. A team KPI keeps everyone pulling in one direction. An individual KPI shows each person how their part contributes.

Level Example: finance team at a logistics company in Ikeja
Team 90% of invoices paid within terms by the end of the quarter
Billing officer Invoices raised within 2 working days of delivery
Credit controller Overdue over 30 days reduced from ₦1.1m to under ₦500,000
Accountant Month-end reconciliations completed by the 5th working day

If every individual hits their KPI and the team KPI still misses, the KPIs measure the wrong things.

Examples by function

These are starting points to adapt, not targets to copy. Set the numbers from your own last six months, not from what sounds ambitious.

Finance

  • Days to issue an invoice after delivery or service.
  • Percentage of invoices approved first time, without being returned to the raiser.
  • Value overdue by more than 30 days.
  • Month-end close completed by a set working day. Our month-end checklist helps define "completed".

Sales support and customer service

  • Customer queries resolved within 2 working days.
  • Statements sent to every account customer by the 5th of the month.
  • Customer records complete, with billing contact, TIN and RC number, for every new customer.

Operations

  • Payment vouchers raised with complete supporting documents, so fewer are returned.
  • Deliveries completed on the scheduled date.
  • Petty cash or diesel spend within the monthly budget for the depot.

HR and payroll

  • Payroll approved by a set date each month.
  • Payroll corrections needed after the run, aiming for zero.
  • New joiners with a complete record (bank, RSA PIN, TIN) before their first payday.

Set a baseline before a target

A target with no baseline is a guess. For each KPI:

  • record where you are today;
  • decide where you want to be in a quarter;
  • agree how it's measured and where the number comes from.

Example. Chiamaka Obi, finance manager, set the billing officer's KPI like this:
KPI Average days from delivery to invoice
Baseline (last 3 months) 5.8 working days
Q1 2027 target 3 working days
Measured from Delivery date vs invoice date in the system
Reviewed First Monday of each month, 15 minutes

The monthly review isn't an appraisal. It's a short conversation:

  • What moved?
  • What got in the way?
  • What does the person need?

Make the numbers visible

A KPI people can't see is a KPI they can't act on. The person measured should be able to check their number any day of the month, not only at the review. Three practical rules:

  • One place. Keep KPIs where the work happens, not in a separate deck that HR updates quarterly.
  • Same source as the work. If invoice dates come from the billing system, the KPI should read them from there. Hand-copied numbers drift, and arguments about the number replace conversations about the work.
  • Team view as well as individual view. A depot manager in Trans-Amadi should see the team's diesel spend against budget, not only their own approvals.

When a KPI goes red

Red is information, not a verdict. When a number misses two months running, ask in this order:

  1. Is the measure right? Perhaps deliveries are logged late, not invoiced late.
  2. Is the target right? A baseline taken in a quiet quarter makes December look like failure.
  3. Is something blocking the person? Missing purchase orders, slow approvals, a system nobody was trained on.
  4. Only then: is it about performance?

Most red KPIs in growing businesses turn out to be process problems wearing a person's name.

Common mistakes

  • Copying a KPI library. Generic lists produce generic targets. Start from the problems your business actually has.
  • Tying every KPI to pay. It encourages gaming. Link pay to a small number of outcomes, and use the rest for coaching.
  • Measuring activity. "Calls made" goes up while "issues resolved" stays flat.
  • Never retiring a KPI. When a measure has been green for six months, replace it with the next problem.

For the wider picture of which numbers owners should watch, see management visibility without extra manual reporting.

How Flux helps

Flux HR & Self-service includes staff KPIs:

  • targets and performance tracked for individuals and for teams;
  • KPIs kept alongside each employee's record and the directory, not in a separate spreadsheet.

Many finance KPIs, such as invoices returned in approval, overdue balances and approval times, come from records Flux already keeps, so the number can be read from the system instead of rebuilt by hand.

From the blog