Approved hours and costs, posted straight into QuickBooks.
Approved billable hours, priced on the same rate ladder as our own invoicing and written into QuickBooks Online as a draft invoice — never approved, emailed or paid.
Connected once, scoped per organisation
A connection belongs to your organisation and nothing else. Tenant isolation is enforced by composite foreign keys in the database, so a cross-tenant read is an error rather than a code-review question.
Incremental, cursor-tracked syncs
Syncs resume from where the last one stopped rather than replaying from the beginning, and every run is recorded with its outcome, so a failed sync is visible instead of silent.
Scoped credentials, revocable
Access is held as a scoped credential you can rotate or revoke, and every use of it lands on the same hash-chained audit trail as the rest of the account.
How it works
Approved billable hours, priced on the same rate ladder as our own invoicing and written into QuickBooks Online as a draft invoice — never approved, emailed or paid. The connection is scoped to your organisation, holds a credential you can rotate or revoke, and records every sync with its outcome, so a run that fails is visible rather than silent.
Syncs run incrementally and resume from the last cursor rather than replaying from the start. Every access lands on the same hash-chained audit trail as the rest of the account, so who connected QuickBooks, and when, is a matter of record.
QuickBooks connects to WorkMonitor through a first-party connector maintained in this codebase. Approved billable hours, priced on the same rate ladder as our own invoicing and written into QuickBooks Online as a draft invoice — never approved, emailed or paid.
Four steps, once
- 01Open Settings → Integrations and choose the connector.
- 02Authorise the connection and pick the scope it may read.
- 03Run the first sync, then review what it brought across.
- 04Set the schedule, and watch the sync history for failures.
What you get either way
Connected once, scoped per organisation
A connection belongs to your organisation and nothing else. Tenant isolation is enforced by composite foreign keys in the database, so a cross-tenant read is an error rather than a code-review question.
Incremental, cursor-tracked syncs
Syncs resume from where the last one stopped rather than replaying from the beginning, and every run is recorded with its outcome, so a failed sync is visible instead of silent.
Scoped credentials, revocable
Access is held as a scoped credential you can rotate or revoke, and every use of it lands on the same hash-chained audit trail as the rest of the account.