Fichaloto

Blog Projects

Accounting for hours on a funded project, without reconstructing them at the end

9 min read

The timesheet built in March to account for last year almost always adds up. That is exactly the problem: it adds up too neatly.

What gets asked for, and what people think gets asked for

When the review of a publicly funded project comes round — a national agency, a regional call, a European programme — or an R&D tax credit gets checked, almost everyone prepares the same thing: a table with each person's hours by month. It is what the form asks for, so it looks like it is what is being asked.

What actually gets tested is four things, and only the first is in that table:

  • That the hours exist — who, on what day, how many and on what activity.
  • That they are consistent with the working day — that the person was working that day, and that nine logged hours do not sit on top of seven clocked ones, or land on a public holiday or approved leave.
  • That they are consistent with the cost — that the hourly rate comes from that person's real cost and not from a round number typed in by hand.
  • That they were not written afterwards — that the record is contemporaneous with the work and not a reconstruction built for the claim.

Why a perfect sheet raises more doubt than an imperfect one

An experienced auditor spots a reconstruction immediately, and not out of suspicion: out of statistics. Real hours are ugly. They have three-hour days and eleven-hour days, weeks broken by flu, a bank holiday in the middle and someone who joined in April. A table where everybody does exactly eight hours on the project every working day of the quarter does not look like any work that ever happened.

And the cross-check is easy to run. In Spain the working-time record has been compulsory since 2019 and has to be kept for four years, so the auditor has it available by law: three people and three weeks is enough to compare against the logged hours. If it does not match, what falls is not that week: it is the credibility of the whole table.

This is not about anyone lying. It is that reconstructing a year of work from memory inevitably produces a regular-looking document, and regularity is what stands out.

The three things that have to be running BEFORE

None of the three can be set up the day the letter arrives. All three are cheap if they are in place from the start:

  • People log hours in the week they work them, not at month end. With a short deadline and a reminder, weekly logging becomes routine; with a monthly one it becomes a memory exercise.
  • The funded project is a project in the system, with its code, its phases and its tasks, and not a label in a notes field. What has no structure cannot be grouped afterwards in any way that survives a question.
  • The working-time record and the logged hours live in the same place. If they sit in two different systems, the reconciliation will be done by hand, in a spreadsheet, once, in March — which is exactly the scenario we are describing.

What it looks like in Fichaloto

The working-time record and the logged hours are in the same database and are seen side by side, per person and per day. When someone logs nine hours on a day they clocked seven, that shows up that week, with time to ask what happened, and not eleven months later.

Every mark on the record is chained to the previous one with a fingerprint, so the series can be shown to be complete and untouched. Corrections — the missed clock-out — exist, because life is like that, but they are requested, approved by someone with permission and signed with their name and time. How the chain works.

The hourly cost comes from each person's record, so the rate that appears in the claim is the same one used all year to work out project margin. And everything exports by person, project and period, into files any spreadsheet opens, to attach as it is.

What Fichaloto does not do, and it is worth saying: it does not file the claim, it does not interpret the terms of the call and it does not replace your adviser. It gives you the data the claim is built from, in a state where it can be shown.

A note on people who are not on the project all day

The awkward case is the usual one: someone who spends half their day on the funded project and the other half on client work. The temptation is to split the month 50/50 and move on. That split is an estimate, and an estimate presented as a measurement is what costs most if anyone pulls the thread.

The alternative is not more work: it is logging each day what was done that day, even when it is uneven. Three hours on Tuesday and six on Thursday is defensible; four hours every single day of March is not.

Frequently asked questions

Does the working-time record count as evidence of project hours?

Not on its own: the record says that person worked, not what on. What gets claimed is the logged hours — who, on what day, how many and on what activity — and the record is what holds them up, because it shows those hours fit inside a working day that existed.

Can hours be logged to a project after the fact?

They can, and sometimes there is no choice. But the later it is done, the more it looks like a reconstruction and the less like a record. If it has to be done, it helps for there to be a trace of when each line was entered — something a system keeps and a spreadsheet does not.

What if logged hours do not match clocked hours?

It has to be explained, and there is almost always an explanation: a split shift recorded badly, a training day, travel. The problem is not the occasional mismatch but finding it when there is no longer anyone to ask. Seeing it on the same screen, in the same week, turns it into a two-minute conversation.

Do the hours have to be signed by each person?

It depends on the terms of each call; some ask for a signed declaration of dedication. What helps in every case is that the hours were logged by the person themselves and that there is a record of who approved them and when, rather than admin typing them up from an email.

All of this is built into Fichaloto. See how it works.

Keep reading