QuickBooks

QuickBooks Online exposes a broad set of accounting entities: Invoice, Bill, Payment, Customer, Vendor, Employee, TimeActivity, PurchaseOrder, and roughly twenty others. This integration covers two object types: TimeActivity, which records work performed by individual employees, and the Invoice-Payment pair, which tracks the cash collection cycle at the company level. The remaining entities, whether expense reports, journal entries, or balance sheet accounts, were set aside because they either lack reliable per-user attribution or measure financial position rather than individual contribution. Four KPIs were retained, selected against three criteria: ability to attribute to an owner, resistance to gaming, and balance between leading and lagging indicators.

Time contribution: reading individual output before revenue is recognized

Hours Logged measures the total volume of time recorded by each employee across all activities in the period. Billable Hours Ratio measures what fraction of that time was designated billable, as opposed to internal or non-chargeable work. These two indicators are the only KPIs in this integration with direct per-individual attribution, made possible by the EmployeeRef field on the TimeActivity entity.

The two indicators must be read together. Hours Logged in isolation carries a padding risk: an employee can log time against low-value internal tasks to meet a volume target without generating any client value. Billable Hours Ratio neutralizes this risk by exposing the proportion of effort that translates into client-facing output. Conversely, a high Billable Hours Ratio combined with a low Hours Logged volume may signal under-recording rather than outstanding efficiency. The combination reveals whether high utilization reflects genuine client work or a narrow base of activity.

Cash collection: company-level indicators of financial cycle health

Days to Payment measures the average number of days between an invoice due date and the date payment is received. Revenue Collected measures the total cash amount received in the period. Unlike the time activity indicators, these two KPIs carry no per-individual attribution: they reflect the collective performance of the finance and accounts receivable function, and in some cases the payment behavior of customers themselves.

Days to Payment is the more diagnostic of the two. A lengthening trend signals deterioration in collection discipline, customer payment behavior, or both — and it typically precedes a cash flow constraint before that constraint becomes visible in bank balances. Revenue Collected confirms cash actually received rather than revenue invoiced, a distinction that matters in periods where billing activity is high but payment follow-through is slow. The two indicators are most useful as team or company-level key results, where the absence of individual attribution is an analytical constraint rather than a failure of the integration.

Scope and limits of the integration

QuickBooks is a recording system for financial transactions, not a workflow tool with native user-level performance attribution. The consequence is structural: most of the platform's accounting entities — invoices, bills, payments, journal entries — do not carry a reliable field identifying which individual team member performed the work. The four KPIs retained here represent the practical ceiling of what can be attributed reliably without requiring custom field conventions or external mapping tables.

Time activity data is only as complete as the logging discipline of employees. If time recording is inconsistent — entries created in batches, logged retroactively, or omitted entirely — Hours Logged and Billable Hours Ratio will reflect recording behavior as much as actual work. Similarly, Days to Payment depends on invoices being created with accurate due dates and payments being matched to invoices in a timely manner. The quality of these indicators is a direct function of the accounting hygiene the team applies to the tool.