Spendesk

Spendesk exposes several object types: settlements (card payments and expense claims), payables (supplier invoices), members, suppliers, cost centers, and expense categories. This integration focuses on settlements and payables, the two objects that carry direct individual attribution and generate actionable financial performance signals. Members and cost-center objects are structural references used for attribution and filtering; they do not produce standalone KPIs. Five KPIs were retained, selected against three criteria: ability to attribute to an identified owner, resistance to gaming, and balance between leading indicators of process discipline and lagging indicators of financial outcome.

Spend activity and budget adherence

Settlements Count measures how many individual payment transactions a member initiates during a period, covering both corporate card payments and expense claim submissions. Total Spend Amount measures the aggregate monetary value of those same transactions. These two indicators serve different diagnostic functions despite sharing the same population of records. A member with a high Settlements Count and a low Total Spend Amount is making many small-ticket purchases, a pattern common in operational roles with frequent per-diems or transport expenses. A member with a low count but a high amount is concentrating spend in fewer, larger transactions. Identifying which pattern applies matters for budget monitoring: frequent small transactions are harder to review line by line, while infrequent large transactions warrant closer approval scrutiny. Reading the two indicators together reveals the structural shape of each member's spending behavior, which no aggregate alone provides.

Compliance and audit readiness

Receipt Attachment Rate measures the proportion of a member's settlements that have a receipt document attached at the time of submission. This indicator occupies an unusual position in the KPI set: it is a leading indicator of audit risk rather than a measure of financial magnitude. A persistently low rate for a given member predicts two downstream consequences — blocked reimbursements that create friction for the employee, and gaps in the audit trail that expose the company during accounting reviews or external audits. The indicator is directly actionable by the individual, since the behavior that drives it (attaching a receipt at point of payment) is within their control. It is also resistant to gaming when receipt validation is system-enforced rather than self-declared, because the system records whether a file was attached, not whether the employee claims to have one.

Process velocity: approver responsiveness and invoice discipline

Submission to Approval Time measures the average number of days between an expense submission and the first approval decision, attributed to the approver rather than the submitter. On-Time Payable Submission Rate measures the proportion of supplier invoices submitted before their due date, attributed to the finance team member handling the payable. These two KPIs address different stages of the financial process but share a common structural role: they surface bottlenecks that distort month-end close timing. A high Submission to Approval Time attributable to a specific approver identifies an individual constraint in the reimbursement chain, not a systemic one. A low On-Time Payable Submission Rate on a given team member's payables creates cash-flow distortion by compressing the payment window between receipt and due date. The tension between these two indicators is asymmetric: approval delays affect employees, while late payable submissions affect suppliers and cash management. Both degrade the accuracy of financial reporting in different ways, and both are correctable through individual behavior rather than process redesign.

Scope and limits of the integration

Spendesk captures transactional data generated within its own platform, which means the integration is blind to spending that occurs outside of it: wire transfers processed directly in a banking interface, informal petty cash, or purchases on accounts not connected to Spendesk. The KPIs measure process compliance and spend volume, not the quality of business decisions behind the expenditure. A member with a high Total Spend Amount and a high Receipt Attachment Rate is fully compliant and visible in the data — but the appropriateness of that spending relative to business objectives is not something any spend management platform can assess. Similarly, Submission to Approval Time captures the administrative responsiveness of approvers, not the quality of their judgment: an approver who processes quickly but approves everything is indistinguishable from one who processes quickly and applies genuine scrutiny. The reliability of all five KPIs depends on consistent and complete use of Spendesk by the entire team; partial adoption — where some members use personal cards and submit reimbursements outside the tool — creates blind spots that make individual comparisons misleading.