Xero

Xero exposes a broad set of objects across two distinct APIs: the Accounting API covers invoices, contacts, bank transactions, expense receipts, and accounts, while the Projects API covers projects, tasks, and time entries. This integration focuses on the two object types that support direct, per-user attribution: receipts for expense management and time entries for project work. Invoice-level indicators, despite their strategic value, were excluded because the standard Accounting API schema does not expose a creator user identifier on invoice records. Six KPIs were retained, selected against three criteria: ability to attribute to a named owner by email, resistance to gaming, and balance between leading and lagging indicators.

Time tracking: billability and individual workload

Two KPIs are drawn from time entries in the Projects API. Total Hours Logged measures the full volume of time recorded per user, regardless of whether that time is billable to a client. Billable Hours Logged restricts this count to time entries associated with billable tasks. Both are leading indicators: they capture activity in real time and precede the revenue outcomes they ultimately generate.

These two indicators must be read together. Billable Hours Logged in isolation can obscure the actual workload carried by an individual: a consultant logging 60 billable hours has a very different operational reality depending on whether their total hours are 65 or 95. The implicit ratio — billable hours divided by total hours — is what management typically calls the billability rate, and it is precisely the gap between these two numbers that reveals over-servicing, administrative overhead, or unbilled rework. Neither KPI alone surfaces this signal; both together make it legible without requiring an explicitly computed ratio field.

Total Hours Logged also carries an under-reporting risk. In tools where time tracking is voluntary or asynchronous, users who log fewer hours may simply be less diligent about entries rather than less productive. For this reason, a low Total Hours Logged value should be interpreted cautiously: it may reflect light workload, disciplined time management, or systematic under-entry. The KPI gains interpretive strength when combined with project-level budget utilization, which provides an external reference point against which the declared hours can be validated.

Project efficiency: budget hours utilization

Budget Hours Utilization measures the ratio of actual hours logged by a user to the estimated hours allocated to them across projects. It is a lagging indicator: it can only be calculated after time entries are recorded against a project with defined estimates. This KPI serves as the efficiency counterpart to the time-tracking indicators.

A utilization rate below 100% may indicate either efficient delivery or under-engagement on the project scope. A rate above 100% reveals over-servicing: more time spent than estimated, which in a fixed-price context translates directly into margin erosion. When read alongside Billable Hours Logged, the two indicators together distinguish between the problem of billing enough and the problem of scoping correctly. A team member logging high billable hours against low budget utilization is delivering efficiently; the same high billing against over-budget utilization may signal a scoping or estimation problem rather than individual underperformance.

Expense management: submission volume and financial control

Three KPIs cover the receipt object. Expense Claims Submitted counts the number of expense receipts filed by each user in a given period. Expense Amount sums the total value of those claims. Expense Approval Delay measures the average number of days between the submission of an expense and its payment.

Expense Claims Submitted and Expense Amount are paired indicators that serve different diagnostic purposes. Submission count is a leading signal of operational discipline: a team that submits expenses promptly creates less end-of-period accounting pressure and generates cleaner cash flow data. Expense Amount is a lagging financial control indicator. The two in combination reveal spending patterns that neither exposes alone: a high count with a low total amount suggests frequent, small-value expenses — characteristic of travel-heavy roles — while a low count with a high total suggests infrequent but significant expense events, which warrants closer per-claim scrutiny.

Expense Approval Delay introduces a process efficiency dimension. A long average delay between submission and payment is not primarily an individual performance problem — it is typically a bottleneck in the approval chain. Tracking this metric attributed to the submitter enables identification of systematic patterns: whether delays are concentrated on a specific approver's workflow, whether certain expense categories face repeated queries, or whether a period-end surge in submissions creates artificial queue growth. The metric is attributed to the submitter for aggregation purposes, but its managerial interpretation is upstream: it is read as a signal about process health rather than individual effort.

Scope and limits of the integration

Xero does not expose a creator user identifier on invoice records in the standard Accounting API schema. This means that revenue-generation indicators — invoices issued, invoice value, days sales outstanding — cannot be attributed to individual users and are therefore absent from this integration. These are precisely the indicators that finance leaders most commonly associate with Xero, and their absence is a structural constraint of the API design, not an analytical choice. Organizations that need invoice-level user attribution may require a custom field or a workaround that falls outside the scope of this integration.

Time entry KPIs depend entirely on consistent use of Xero Projects by the team. In organizations where time is tracked in a separate system and only summarized in Xero, or where time entries are entered in bulk at week's end rather than daily, the leading-indicator value of these KPIs is diminished: they become retrospective records rather than real-time activity signals. Similarly, expense KPIs reflect only what is submitted through Xero Receipts; expenses settled through corporate cards, reimbursed outside the tool, or simply not filed are invisible to this integration. The reliability of all six KPIs depends directly on the team's discipline in recording activity within Xero at the time it occurs.