Expensify

Expensify structures expense management around a single dominant object: the expense report. Employees create reports, attach individual expenses, submit them for manager approval, and receive reimbursement once approved. The platform also exposes policies, employees, and domain-level objects, but these contain configuration data rather than activity data suitable for performance tracking. This integration focuses exclusively on reports, which carry the attribution fields, timestamps, and compliance flags necessary to produce attributable KPIs. Five indicators were retained, selected against three criteria: ability to attribute to a named owner via email, resistance to gaming, and balance between leading and lagging indicators.

Submission discipline and compliance

Submission Rate counts the number of expense reports a given employee submits within the measurement period. It is the primary activity indicator for each submitter: an employee who accumulates unreported expenses creates forecasting gaps for finance teams and introduces reimbursement delays that fall back on themselves. Policy Violation Rate measures the proportion of that employee's submitted reports that contain at least one policy exception — an expense that exceeds the allowed amount, falls into a restricted category, or lacks a required receipt.

These two indicators are designed to be read together precisely because each constrains the interpretation of the other. Submission Rate alone carries a latent gaming risk: an employee aware that the KPI measures submission volume could artificially increase frequency by submitting one expense per report rather than batching logically. Policy Violation Rate neutralizes this strategy — splitting legitimate expenses into micro-reports does not reduce violations, and splitting them carelessly increases the ratio. Conversely, an employee who reduces their Submission Rate to keep their Violation Rate low is signaling a different problem: delayed reporting. The combination holds both failure modes visible simultaneously.

Approval throughput and manager behavior

Approval Cycle Time measures the average number of days between a report's submission date and its approval date, attributed to the approving manager. It is a lagging indicator of approval throughput: a persistently high value signals that the manager is a bottleneck in the expense process, regardless of whether the delay stems from workload, inconsistent review habits, or organizational approval chains that require multiple sign-offs. Rejection Rate measures the proportion of submitted reports that the same manager sends back to the submitter.

The interaction between these two indicators is diagnostic in both directions. A high Rejection Rate combined with a low Approval Cycle Time describes a manager who reviews quickly but returns reports frequently — a pattern consistent with strict enforcement of policy rules, possibly at the cost of upstream clarity. A high Rejection Rate combined with a high Approval Cycle Time describes a different situation: slow reviews that ultimately reject, which maximizes process friction for the submitter and delays reimbursement by the full cycle duration. A low Rejection Rate combined with a high Approval Cycle Time is the most common bottleneck signature: the manager approves nearly everything but does so slowly, acting as a passive queue rather than an active control point. These three combinations are not distinguishable from either indicator alone.

End-to-end process efficiency

Reimbursement Cycle Time measures the average number of days between a report's submission date and the date the submitter was reimbursed, attributed to the submitter. It is the end-to-end measure of the expense process and the indicator most directly felt by employees: delays in reimbursement generate dissatisfaction that is disproportionate to the financial amounts involved, and sustained delays are a known driver of expense policy non-compliance.

Reimbursement Cycle Time aggregates both manager approval latency and finance processing time downstream of approval. This means it is partially outside any submitter's direct control, which limits its use as an individual performance indicator while preserving its value as a systemic health indicator. When Reimbursement Cycle Time is rising for a specific employee, the decomposition into Approval Cycle Time reveals whether the bottleneck sits at the manager level or at the finance operations level — a distinction that determines the appropriate corrective action entirely.

Scope and limits of the integration

Expensify records timestamps, amounts, and policy flags, but does not capture the quality of the business rationale behind any expense. A report with zero violations may describe a well-justified expense or a routine one below the threshold that triggers policy checks; the API data does not distinguish between the two. Total spend submitted per user was explicitly excluded from this integration: expense levels are driven by business activity, travel patterns, and project type rather than by individual contribution decisions, making spend volume an unreliable proxy for individual performance in any OKR context.

The reliability of all five indicators depends directly on how employees and managers use the platform. Submission Rate is meaningful only when employees submit expenses promptly rather than batching months of activity at fiscal year end. Violation Rate is meaningful only when expense policies are current, clearly communicated, and enforced consistently. Approval Cycle Time reflects actual manager review behavior only when the approval workflow in Expensify mirrors the actual organizational process rather than routing around it through side channels. These KPIs measure process adherence as much as they measure individual performance — the two are inseparable in an expense management context.