Declarabiliteit per practitioner
This screen sets the care already billed for each practitioner against the hours that practitioner is rostered for. So you see not only whether billing is being left behind — the Analytics screen shows that for the practice as a whole — but with whom. The screen is intended for practice owners and administrators with billing access.
Overview
| Route | /analytics/declarabiliteit |
| Audience | Practice owner, management |
| Required permission | billing.read |
The table shows one row per practitioner, with four columns: Declared, Still to declare, Rostered and Declarabiliteit. The period is the same one the Analytics screen uses: a period chosen there is ready here, and the other way round.
How it works
Hours count per practitioner here
The Analytics screen counts a session once, for the session's own duration. This screen counts that same session once per practitioner in it, each time for its full duration. A one-hour group session run by two practitioners cost both of them an hour of their own roster; halving those hours would short-change both.
The consequence is that these columns do not add up to the Analytics screen's. In a practice that runs group sessions or co-treatment, the sum of the declared hours here is higher than the declared hour total in the chart — by exactly the co-treatment. Neither figure is wrong; they count different things.
What counts as declared
Declared and still-to-declare mean exactly what they mean on the Analytics screen, so the two screens cannot disagree. A consult no billing can follow — an appointment type that is not billable, an archived client, a client who was not present — counts in neither column.
Still-to-declare deliberately sits beside declared. A low declarabiliteit caused by care nobody has billed yet looks, in a single figure, exactly like a low declarabiliteit caused by an empty agenda, while the two call for completely different action.
What rostered hours are
The rostered hours are the working hours recorded in Scrivio for that practitioner, for every day in the chosen period:
| Absence | Applied — leave or an adjusted roster counts as entered. |
| Blocks marked "in house" | Counted. It is time the practice pays for, even though no client may be booked into it. |
| Booked appointments | Are not subtracted. The denominator is the time someone is at work, not the time that was still free. |
Practitioners without working hours
If no working-hours roster has been recorded for a practitioner, the Rostered column reads No werkuren configured and Declarabiliteit stays empty. That is deliberate: a roster nobody has filled in is not the same as zero hours, and 0 % would read as a practitioner who declared nothing. Fill in the working hours under Organisation › Users (or in their own profile) and the row fills in by itself.
Who appears in the table
Every enabled practitioner of the organisation gets a row, including one who delivered no care in the period — that is the point of an overview with a denominator. In addition, anyone carrying hours in this period gets a row, even if the behandelaar designation has since been removed. That way a colleague who has left the practice cannot quietly take their declared hours out of the overview.
Choosing the period
The Start date and End date fields choose the period the table is computed over. It defaults to the last three months.
| Field | Required | Description |
|---|---|---|
| Start date | Yes | First day of the period. |
| End date | Yes | Last day of the period. Must be on or after the start date. |
While the end date falls before the start date, the table is not updated. Above the table you can read which period the figures shown were computed over.
The period chosen here is the one the Analytics screen uses, so the two can be read side by side.
Back to billing insight
The Back to billing insight link takes you to the Analytics screen: the same question for the practice as a whole, plotted over time. From there, View declarabiliteit per behandelaar brings you back here.