For finance
A clean close is the hardest work nobody sees.
Finance succeeds when nothing happens: the filing accepted, the audit query answered in a day, the close done on the third instead of the ninth. Those are events, and events can be recognised.
Get this wrong and it backfires
The trap: measuring hours
Finance teams are measured on hours more than almost any other function, because the work is periodic and the periods are brutal. Ranking on hours rewards the person who stays latest during close, which is often the person whose reconciliation took longest because it was set up worst. It also tells the person who automated their part of the close and went home at six that they did something wrong.
The other free number is volume: invoices raised, journals posted, and it has the same problem in a different coat. The work that actually distinguishes a strong finance team is the absence of rework: the filing that was accepted first time, the invoice that was collected rather than chased, the audit query that was answered the same day because the file was already in order. All of those are countable. None of them is hours.
What a reward looks like
What a finance board looks like here
Rank on outcomes with a date attached: the close completed and which working day it landed on, filings accepted first time, invoices collected inside terms, audit queries answered within the day. Show hours nowhere. Weight first-time acceptance above volume, because a corrected filing costs more than it saves.
Team level by default. A month-end close is a relay, and the honest unit is the team that ran it; a personal ranking during close mostly measures who was handed the messiest ledger.
Rewarding the month that went right
The best month a finance team has is the one where nothing was late, nothing was corrected and nobody noticed. That month currently produces no recognition at all. Send the close as an event with the day it landed, and a rule can pay out for day three what it would not pay for day nine. Send the accepted filing, and the correction that never had to happen becomes a card.
The Services deck has cards that describe this team better than any we could write for it: keeping the estimate, flagging the overrun at sixty per cent rather than a hundred and ten, logging the time honestly. They were written for consultancies and they are about exactly this kind of discipline.
Peer recognition covers the rest: the colleague who caught the error before it posted, the one who explained the variance in a sentence. Capped daily.
Getting it in
Accounting platforms, billing systems and filing tools can send us a message when a status changes, and most close-management tools can too. Send the record id and the status it reached, the owner’s email so the credit lands on a person, and the date if there is one. The same status twice counts once, so a re-sync is safe.
An afternoon for whoever administers the system. The free tier covers ten people indefinitely if you want to see it working first.
Questions
The ones that come up
What should you measure a finance team on?
Deadlines met and rework avoided: the close done early, filings accepted first time, invoices collected inside terms, audit queries answered promptly. Not hours, which reward the slowest reconciliation.
Is a leaderboard appropriate for an accounting team at all?
At team level, as a record of the months that went right, yes. Nobody is ranked on how late they stayed. What gets recognised is the filing that did not need correcting, which today is recognised by nobody.
Our close is a team effort. Who gets the credit?
The team, by default. Send the close as one event credited to the team, and send the individual steps, such as the reconciliation and the filing, as events credited to whoever did them, if you want both views.
Rank what this team actually does.
Free for your first 50 people. No card, no sales call.