This article applies to Aiwyn Practice. The Billing report area, including Billing Performance and Employee Performance, is available only to firms using Aiwyn Practice.
This article explains what the key Billing metrics measure and how to interpret them. The Collections report area is available to all firms; see How Collections report metrics are defined.
Realization Rate measures how much of the standard value of billed time became revenue
Realization Rate is the percentage of the standard value of your billed time that became revenue after WIP adjustments. It is Realized Revenue divided by Standard Billable Value, times 100.
Standard Billable Value is the value each time entry received when it was logged: hours multiplied by the rate card rate in effect on the logged date. Aiwyn looks for the staff member's own rate for that task type first, then the rate for their staff type. If the task type has a custom hourly rate, that rate is used instead. A later change to the rate card does not change the value of time already logged.
Write-downs push Realization Rate below 100%. Write-ups push it above 100%. Aiwyn does not cap the rate: when an invoice bills more than the WIP value, such as a fixed fee larger than the time on the job, the difference is recorded as a negative write-off and the realization on that work is above 100%.
Billing Effective Rate measures what each billable hour earns
Billing Effective Rate is the average dollars earned per billable hour, weighted by hours logged. It is Realized Revenue, excluding expenses, divided by billable hours. Because the hours are weighted, a large engagement affects the result in proportion to its hours.
Realization Rate tells you how much of the value of your time turns into revenue. Billing Effective Rate tells you what that revenue works out to per hour.
Both rates are based on the invoice transaction date. When you filter by date, they describe work invoiced in that period, not work logged in it.
The two rates can move in opposite directions
A firm can hold Realization Rate steady and still see Billing Effective Rate fall. That happens when billed work shifts toward lower-rate staff or lower-rate service lines. A firm can also hold Billing Effective Rate flat while Realization Rate drops, if write-downs increase on higher-rate work.
So the two numbers point to different causes. A falling Realization Rate points to write-downs. A falling Billing Effective Rate points to pricing or staffing mix.
This is why the Employee Performance report plots both on one chart. Earning Efficiency is a dual-axis line chart of Realization Rate and Billing Effective Rate over time. Reading the two lines together shows whether a change in margin came from write-downs or from pricing.
The same metric name can give different numbers on Billing Performance and Employee Performance
Realization Rate appears on both Billing Performance and Employee Performance, but it is not calculated the same way:
- On Billing Performance, Realization Rate counts time only.
- On Employee Performance, it counts time and expenses. The tile describes revenue “after WIP or expense adjustments.”
- Progress WIP is excluded on both.
For the same filters, the two reports can show different Realization Rates, and neither is wrong. Compare Realization Rate within one report rather than across the two.
On both reports, Billing Effective Rate uses realized revenue from time WIP on posted invoices, divided by the billable hours attached to those records. Expense amounts and expense adjustments are excluded.
Hours totals differ between the reports. Billing Performance counts submitted time entries only; an entry is considered submitted once it has been approved or posted. Employee Performance also includes draft and operational entries in its general hours totals. Those broader totals do not feed Billing Effective Rate: the rate uses billable hours tied to time WIP on posted invoices, so draft or operational hours do not change it. See Aiwyn KPI glossary for the other metrics that appear on more than one report.
Median Days to Bill measures the time from logged work to a sent invoice
Median Days to Bill is on Billing Performance. It is the median number of days from WIP logged date to invoice transaction date. The days are counted for each WIP record, and the median is taken across all records in the filtered data. Only invoices that have been sent count. Draft invoices are excluded.
Median Days to Bill responds to the invoice transaction date when you use the Date filter, so it describes invoices sent in the period you select.
The WIP Aging Summary shows all unbilled WIP, aged from the WIP logged date to today, regardless of the Date filter. See Aging buckets used in Aiwyn reports for the bucket boundaries.
Related
- Aiwyn KPI glossary
- Billing performance report reference
- Employee performance report reference
- Aging buckets used in Aiwyn reports
- How Collections report metrics are defined