Integrations · QuickBooks Online
One record here. One ledger there.
The books stay in QuickBooks. Issued invoices post one way from the job record, after a dry run you can read: no double entry, and no second ledger to reconcile.
Thorbis ↔ QuickBooks Online
- Issued invoicespost one way →
- Customersmatched, not duplicated
- The dry runread before anything posts
- Chart of accountsstays in QuickBooks
The data contract
What moves, and which way.
Issued invoices, one way
When an invoice is issued in Thorbis, it posts to QuickBooks, after a dry run you read first. One direction, on purpose: the books never write back into the jobs.
Customers, matched
Thorbis customers are matched against QuickBooks names so nothing posts under a duplicate. Matching is shown in the dry run, not discovered at reconciliation.
The books, untouched
Chart of accounts, ledgers, payroll, and tax filings stay exactly where the accountant keeps them. We will not sell a replacement until Money is the product.
The stance
The books stay in one place.
Suites advertise two-way sync and then sell you the reconciliation problem it creates. Here the jobs are the record, the books are the ledger, and the posting crosses once, read by a person before it lands. The whole QuickBooks stance, on its own page →
Wired, not welded
A connection you can unplug.
Every integration is a stated contract: what flows, which way, and what happens when you turn it off. No integration holds your data hostage.
The connection model
Connect. Normalize. Then automate.
Connect
Authorize the account and choose what moves. Admin access in both systems, granted once, visible always.
Normalize
External records land in their Thorbis homes: a customer is a customer, an invoice is an invoice, no bespoke shapes.
Automate
Only after the first records are verified by a person. The connection has an owner before it has automation.
A system of record
Every field has one home that wins. The books stay QuickBooks's; the jobs stay Thorbis's. Nothing is mastered in two places.
A sync owner
One named person reads the sync health and the exception queue. A connection nobody owns is an outage nobody notices.
An exception path
Records that do not match cleanly go to human review, never silently overwritten, never silently dropped.
Go-live
Staged, so the books stay clean.
01
Connect a test slice
A test account or a limited data set, never the whole company on day one.
02
Verify the mapping
Fields, permissions, and record categories checked against what you expect.
03
Run one real workflow
A single invoice, a single payment, followed to its destination and read.
04
Watch, then widen
Sync health reviewed after launch, the exception owner named, then the volume.
Asked before connecting
Straight answers.
Why one way, when other systems advertise two-way sync?
Because two masters is how books drift. Jobs are mastered here, money records are mastered in QuickBooks, and the posting crosses in one direction after a person has read the dry run. Boring is the feature.
Do I have to move my books to switch?
No. The bridge is the point: QuickBooks stays, Thorbis runs the field, and your accountant's month does not change shape. See switching from QuickBooks for the field-side migration.
What happens when a posting does not match?
It stops. Mismatches land in the exception queue for a person, and the invoice does not post until it is resolved. We do not invent categories to make a row fit.
Other integrations
Start
No double entry. No drift.
Connect the books, read the dry run, and let issued invoices post themselves: one way, with an exception queue instead of surprises.
Waitlist open. One email when your invite is ready, nothing else.
Coming from a suite? We’ll extract your records.
Rather talk first? Email the team.